topic Re: Qizx migration in Talend Data Catalog

Qizx migration

Anonymous — Tue, 06 Aug 2013 15:28:37 GMT

Hi all ,
How to migrate qizx data to MYSQL DB.

from.host=192.168.1.7
from.user=root
from.password=mysql
from.jndi.port=1199
to.host=192.168.1.14
to.user=admin
to.password=talend
to.jndi.port=1199
to.cluster.batch.size=500

Its not working.

Re: Qizx migration

Anonymous — Fri, 09 Aug 2013 10:10:16 GMT

Hi
Which version are you using? Have you read the user manual about how to migrate MDM projects from XML database to relation database?
https://help.talend.com/search/all?query=Migrating+MDM+instances&content-lang=en
If you have any error during the migration process, paste the log message of the MDM server.
Shong

Re: Qizx migration

Anonymous — Mon, 12 Aug 2013 06:11:24 GMT

Hi shong ,

Im using talend 5.1.1.(now i migrate 5.1.1(qizx) to 5.3.1(sql server))
migration property file
---------------------------
from.host=localhost
from.user=admin
from.password=talend
from.jndi.port=1099
to.host=169.254.43.192
to.user=admin
to.password=talend
to.jndi.port=1199

i got an error
-----------------------------------------------------------------------------------------------------------------------
Couldn't access server localhost
com.amalto.core.util.XtentisException: Error : unable to access the XML Server wrapper: Could not obtain connection to any of thes
e urls: localhost:2099 and discovery failed with error: javax.naming.CommunicationException: error setting options
at org.talend.mdm.db.migration.DBMigrationUtil.getXmlServerCtrlHome(Unknown Source)
at org.talend.mdm.db.migration.DBMigrationTool.doMigration(Unknown Source)
at org.talend.mdm.db.migration.DBMigrationTool.main(Unknown Source)
Caused by: javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:2099 and discovery fai
led with error: javax.naming.CommunicationException: error setting options ]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1562)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:634)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at org.talend.mdm.db.migration.DBMigrationUtil.getHome(Unknown Source)
... 3 more
Caused by: javax.naming.CommunicationException: Failed to connect to server localhost:2099 ]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:274)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1533)
... 7 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:2099
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:248)
... 8 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at java.net.Socket.connect(Socket.java:478)
at java.net.Socket.<init>(Socket.java:375)
at java.net.Socket.<init>(Socket.java:276)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:244)
... 8 more

Re: Qizx migration

Anonymous — Mon, 12 Aug 2013 09:18:11 GMT

Well... it seems there's a mismatch between:

.. Failed to connect to server localhost:2099 ..

and:

from.host=localhost
...
from.jndi.port=1099

Could you check your configuration?

Re: Qizx migration

Anonymous — Mon, 12 Aug 2013 12:26:42 GMT

Hi all,
I already gave 1099 it also throwed same error...

from.host=192.168.1.14
from.user=admin
from.password=talend
from.jndi.port=1199
to.host=192.168.1.24
to.user=admin
to.password=talend
to.jndi.port=1099
to.cluster.batch.size=500

we tried changing in binding file - C:\Talend\5.2.1\mdm\jboss-4.2.2.GA\server\default\conf but getting same error.
where can we change from.jndi.port and to.jndi.port so that they will stick to changes perminently?

Re: Qizx migration

Anonymous — Mon, 12 Aug 2013 13:12:00 GMT

Sorry to ask the obvious but you did configure the .14 machine on ports-01 and the .24 on the default port didn't you? Reminder: you change the ports binding in jboss-4.2.2.GA/server/default/conf/jboss-service.xml near the line 215. Comment out the whole <mbean> block to use the default (jndi = 1099).

Re: Qizx migration

Anonymous — Mon, 12 Aug 2013 18:17:14 GMT

Hi Ctoum,
Thanks for your quick reply. I have change the ports binding in jboss-4.2.2.GA/server/default/conf/jboss-service.xml in the line 215. Comment out the whole <mbean> block .But i got same above error.

Re: Qizx migration

Anonymous — Tue, 13 Aug 2013 10:07:06 GMT

Hi,
Can you try a fresh install and select the correct binding during installation?

Re: Qizx migration

Anonymous — Tue, 13 Aug 2013 17:48:38 GMT

Hi ,

I have tried Qizx to SqlServer Migration Process .While running the migration batch File i got the below error.
------------------------------------------------------------------------
java.lang.reflect.UndeclaredThrowableException
at com.sun.proxy.$Proxy3.existsDataModel(Unknown Source)
at org.talend.mdm.db.migration.DBMigrationTool.doMigration(DBMigrationTool.java:105)
at org.talend.mdm.db.migration.DBMigrationTool.main(DBMigrationTool.java:409)
Caused by: java.io.InvalidClassException: com.amalto.core.ejb.ObjectPOJO; local class incompatible: stream classdesc serialVersionUID = 6448
567774416868288, local class serialVersionUID = 3157316606545297572
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:604)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1620)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1620)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at org.jboss.invocation.MarshalledValue.get(MarshalledValue.java:91)
at org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(UnifiedInvokerProxy.java:195)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:112)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
... 3 more

Re: Qizx migration

Anonymous — Wed, 14 Aug 2013 14:41:37 GMT

Hi All,

Thanks for your suggestion, Migration tool is working fine across XML DB.But, I still having an issue. I have installed Talend 5.1.1 whose MDM is configured to MYSQL. I already have 5.3.1 whose MDM is configured to Qizx XML DB. I am trying to run the DBMigration tool, I am getting the following error:

C:\Talend\5.1.1\mdm\jboss-4.2.2.GA\bin\dbtools\migration>java -cp dbmigrationtool.jar;../../../client/jbossall-
client.jar org.talend.mdm.db.migration.DBMigrationTool dbmigration.properties
DB Migration from 192.168.1.201 to 192.168.1.143 starting ...
transfering collection CONF ...
transfering collection Inbox ...
transfering collection JCAAdapters ...
transfering collection MDMDomainObjects ...
transfering collection MDMItemImages ...
transfering collection MDMItemsTrash ...
transfering collection MDMMigration ... transfering collection PROVISIONING ...

To see the whole post, download it here
OriginalPost.pdf