[new_otm]

Hi,

We have installed otm 55 cu3 on a development environment and we have been working with it.
Also we have installed otm 55 cu3 on a production environment.
On production environment we made a practice to put the environment’s database on production and we saw that this worked correctly.
Yesterday we have made a copy of the database of the development environment and we tried to put it in production environment but we have found a problem.
When we try to access to calendars or other otm elements like location we get this java error.
We have seen that the jdk of development environment is the version 1.4.2 but in production environment the version is 1.4.2-13. We don’t know how this version has been installed because we have used the same software for both installations.
Both installation have the same patches.

Does anyone can help us? We have the go-live next week and we have this problem on production environment.

Thanks in advance.

Generic_Remote_Exception java.rmi.UnmarshalException: Error deserializing return-value: java.io.InvalidClassException: glog.server.producer.ProducerXML; local class incompatible: stream classdesc serialVersionUID = -1863004151572480387, local class serialVersionUID = 2538677597816337420java.rmi.UnmarshalException: Error deserializing return-value: java.io.InvalidClassException: glog.server.producer.ProducerXML; local class incompatible: stream classdesc serialVersionUID = -1863004151572480387, local class serialVersionUID = 2538677597816337420 at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINAT ES_FROM_THE_REMOTE_SERVER(RMICall.java:110) at com.evermind.server.rmi.RMICall.throwRecordedExcep tion(RMICall.java:12 at com.evermind.server.rmi.RMIClientConnection.obtain RemoteMethodResponse(RMIClientConnection.java:472) at com.evermind.server.rmi.RMIClientConnection.invoke Method(RMIClientConnection.java:416) at com.evermind.server.rmi.RemoteInvocationHandler.in voke(RemoteInvocationHandler.java:63) at com.evermind.server.rmi.RecoverableRemoteInvocatio nHandler.invoke(RecoverableRemoteInvocationHandler .java:2 at com.evermind.server.ejb.StatelessSessionRemoteInvo cationHandler.invoke(StatelessSessionRemoteInvocat ionHandler.java:43) at __Proxy139.createMasterElementRemote(Unknown Source) at glog.webserver.util.Producer.createMasterElementRe mote(Producer.java:156) at glog.webserver.util.Producer.loadDocument(Producer .java:59) at glog.webserver.util.AbstractManagementServlet.getD ocument(AbstractManagementServlet.java:32 at glog.webserver.util.AbstractServletProducer.proces s(AbstractServletProducer.java:81) at glog.webserver.util.BaseServlet.service(BaseServle t.java:614) at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173) at glog.webserver.screenlayout.ClientSessionTracker.d oFilter(ClientSessionTracker.java:54) at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173) at glog.webserver.util.SetCharacterEncodingFilter.doF ilter(SetCharacterEncodingFilter.java:44) at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:17 at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:14 at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyo teHandler.java:199)at org.apache.jk.common.HandlerRequest.invoke(Handler Request.java:282) at org.apache.jk.common.ChannelSocket.invoke(ChannelS ocket.java:754) at org.apache.jk.common.ChannelSocket.processConnecti on(ChannelSocket.java:684) at org.apache.jk.common.ChannelSocket$SocketConnectio n.runIt(ChannelSocket.java:876) at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:534)

[nick.polites]

After you imported the database did you run your post database import scripts as per in the admin guide? Also be sure to update your contact email addresses and external systems so that test data does not go to your production customers.

Also I don't think anything above JDK 1.4.2_12 has been approved thus far for 5.5.

[new_otm]

Hi,
What we have done to change database from development environment to production environment is copy database files and paste.
Should we do something more if we use this method? Why do we need to change the mail addresses? we want to continue having data on production environment from the development database.

Thanks.

[nick.polites]

This is a typical problem for most new customers. You need to export and import the database and then follow all post database import scripts as packages become invalid in the copy.

Refer to the admin guide under "Creating Database Roles and Database Users" follow all steps after the import of the par file. Make sure to shut down your application and web servers while finishing all of the post import steps. Also make sure that your CU patch versions for the application are also the same on test and production.

If you do not update your email addresses to a dummy email address when someone tests an order in your test system the tender notifications will go to your production service providers and this is something you don't want happening. The same goes for your external systems.