Problem while Importing objects when Migrating from XI 3.0 to PI 7.1.

[former_member201987]

Hello Experts,

We are migrating from XI 3.0 to PI 7.1

We exported objects from IR & ID of XI 3.0 and tried importing them in PI 7.1. But we are getting the below error.

Details

ORA-00904: "ISDOUBLEFORMAT": invalid identifier

STACKTRACE:

com.sap.aii.utilxi.misc.api.BaseRuntimeException: ORA-00904: "ISDOUBLEFORMAT": invalid identifier

at com.sap.aii.ib.gui.tools.transport.ContentImportProgressDialog.executeConcurrentAction(ContentImportProgressDialog.java:438)

at com.sap.aii.utilxi.swing.toolkit.ConcurrentProgressDialog$ProgressDialogRunnable.run(ConcurrentProgressDialog.java:251)

at com.sap.aii.utilxi.misc.thread.ThreadPool$ThreadPoolThread.run(ThreadPool.java:392)

ORA-00904: "ISDOUBLEFORMAT": invalid identifier

STACKTRACE:

com.sap.aii.utilxi.sql.api.SQLResourceException: ORA-00904: "ISDOUBLEFORMAT": invalid identifier

at com.sap.aii.utilxi.sql.api.StatementWrapper.executeInsert(StatementWrapper.java:169)

at com.sap.aii.utilxi.sql.api.AbstractStatement.executeInsert(AbstractStatement.java:122)

at com.sap.aii.utilxi.sql.api.Table.insertSingle(Table.java:520)

at com.sap.aii.utilxi.sql.api.Table.insertSingle(Table.java:512)

at com.sap.aii.ib.server.transport.impl.service.TpInfoServiceImpl.persistTpInformation(TpInfoServiceImpl.java:94)

at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.persistSuccessfulImportInfo(TransportServiceImpl.java:1212)

at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importZippedStream(TransportServiceImpl.java:1008)

at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:668)

at com.sap.aii.ib.server.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:189)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)

at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)

at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)

at $Proxy1721_10000.importFromImportSource(Unknown Source)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)

at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)

at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)

at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)

at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)

at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)

ORA-00904: "ISDOUBLEFORMAT": invalid identifier

SERIALIZED STACKTRACE:

java.sql.SQLException

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)

at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)

at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)

at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)

at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1168)

at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3316)

at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3400)

at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeUpdate(BasicPreparedStatement.java:105)

at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectPreparedStatement.java:365)

at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonPreparedStatement.java:339)

at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeUpdate(PreparedStatementWrapper.java:279)

at com.sap.aii.utilxi.sql.api.StatementWrapper.executeInsert(StatementWrapper.java:166)

... 45 more

Please help!

Thanks in Advance

Suraj

Edited by: Suraj Sawarkar on Aug 7, 2009 11:47 AM

[Former Member]

Suraj,

In up gradation of XI 3.0 to PI 7.0, we need to apply a lot of support patches . hope you have applied all.

Regards ,

[Former Member]

Hi Suraj,

The problem is that the database tables are not updated. Please force deploy the SAPXIESR and SAPXITOOL SCA of 710 and then restart the system and please try. This should work

Thanks and Regards

Ananth

[Former Member]

Hi,

This problem is related to "Program error" of GUI and primary reason is Oracle database. See related note: 1042463 for similar issue with BI.

I suggest to patch PI7.1 (including DB patches) to latest level and then try again. Also this is more related to "User Interface/Programs".

Raise OSS call if issue persist. Also let us know which on which steps u encounter this error (be specific) and try to import only selective and very simple object first then we can conclude something.

Regards,

Gourav

[Former Member]

Hi suraj,

Please check the very useful blog by Naveen on migrating to PI 7.1 :

/people/community.user/blog/2008/12/29/pi71--reflections-and-analysis-of-upgrade

Regards,

[Former Member]

Hi Suraj,

Please check if you have done the setup of PI 7.1 SLD before doing this transport i.e. i mean the creation of business systems etc.

Also use File system to transport your objects. Transfer them in the form of a .tpz file.

Warm Regards,

Anshul

[former_member201987]

Hello Anshul,

The SLD setup is uptodate.

Yes, we are importing the .tpz files, still the problem is coming.

any inputs?

plz help

Thanks,

~Suraj

[Former Member]

Hi Suraj,

Is this problem solved?

I am from ESR Development, we have recieved some messages regarding the same problem.

Is this problem also associated to some message?

Please let me know.

Thanks,

Piyush