SAP Knowledge Base Article - Preview

2489698 - Error "Action CREATE not possible for table BC_SYNCLOG" encountered on SWPM tool

Symptom


While performing a system copy import using the Software Provisioning Manager (SWPM) tool, the following error message occurs during step JMigmonJavaDump:

[SAPinst_dev.log]

ERROR 2017-03-22 22:49:58.770 (<domain name\user\name>) [D:/depot/bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/modlib/iaxxbjsmod.cpp:83] id=nw.syscopy.jmigmonRunFailed errno=CJS-30375
<html> <head> </head> <body> Execution of jMigMon tool '"C:\Program Files\sapinst_instdir\SOLMAN71\LM\COPY\SYB\SYSTEM\CENTRAL\AS\sapjvm_4\sapjvm_4\bin\java.exe" 
-classpath "C:\Program Files\sapinst_instdir\SOLMAN71\LM\COPY\SYB\SYSTEM\CENTRAL\AS\install\sltools\sharedlib\launcher.jar"
-showversion -Xmx1024m com.sap.engine.offline.OfflineToolStart com.sap.inst.jmigmon.jMigMon "\\<server>/sapmnt/<SID>/SYS/global/security/lib/tools;
F:\usr\sap\<SID>\SYS\global\syb\NTAMD64\sybjdbc\jconn3.jar;
C:/Program Files/sapinst_instdir/SOLMAN71/LM/COPY/SYB/SYSTEM/CENTRAL/AS/install/sltools/sharedlib" -mode import -sid <SID> -dsn jdbc/pool/<SID> -ssprops
\\<server>/sapmnt/<SID>/SYS/global/security/data/SecStore.properties -sskey \\<server>/sapmnt/<SID>/SYS/global/security/data/SecStore.key -importDirs I:\Export\JAVA\JDMP -suppressVerboseLog' aborts with return code 64.
<br>SOLUTION: Check 'C:/Program Files/sapinst_instdir/SOLMAN71/LM/COPY/SYB/SYSTEM/CENTRAL/AS/jmigmon.java.log' for more information. </body></html>
TRACE 2017-03-22 22:49:58.770 (<domain\username>) [JSExtension.hpp:1141] CallFunctionBase::call()
Member function 'Installer.invokeModuleCall() has thrown a module error. Rethrowing.
TRACE 2017-03-22 22:49:58.799 (<domain\username>) [D:/depot/bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/sapinst/CSiStepExecute.cpp:1078]
Module error
ERROR 2017-03-22 22:49:58.823 (<domain\username>) [D:/depot/bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/sapinst/CSiStepExecute.cpp:1114] id=controller.stepExecuted errno=FCO-00011
The step JMigmonJavaDump with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_JMigmon|ind|ind|ind|ind|jmigmon|0|JMigmonJavaDump was executed with status 
ERROR ( Last error reported by the step: <html> <head> </head> <body> Execution of jMigMon tool '"C:\Program Files\sapinst_instdir\SOLMAN71\LM\COPY\SYB\SYSTEM\CENTRAL\AS\sapjvm_4\sapjvm_4\bin\java.exe"
-classpath "C:\Program Files\sapinst_instdir\SOLMAN71\LM\COPY\SYB\SYSTEM\CENTRAL\AS\install\sltools\sharedlib\launcher.jar" -showversion -Xmx1024m com.sap.engine.offline.OfflineToolStart com.sap.inst.jmigmon.jMigMon
"\\<server>/sapmnt/<SID>/SYS/global/security/lib/tools;F:\usr\sap\<SID>\SYS\global\syb\NTAMD64\sybjdbc\jconn3.jar;C:/Program Files/sapinst_instdir/SOLMAN71/LM/COPY/SYB/SYSTEM/CENTRAL/AS/install/sltools/sharedlib" -mode import -sid <SID> -dsn jdbc/pool/<SID> -ssprops
\\<server>/sapmnt/<SID>/SYS/global/security/data/SecStore.properties -sskey \\<server>/sapmnt/<SID>/SYS/global/security/data/SecStore.key -importDirs I:\Export\JAVA\JDMP -suppressVerboseLog' aborts with return code 64.
<br>SOLUTION: Check 'C:/Program Files/sapinst_instdir/SOLMAN71/LM/COPY/SYB/SYSTEM/CENTRAL/AS/jmigmon.java.log' for more information. </body></html>).

[Jload.trc]

E R R O R ******* (DbTableModificationAnalyser dev DD.MM.YYYY HH:MM:SS)
HH:MM:SS YYYY-MM-SS dbs-Error: Stack trace: com.sap.dictionary.database.dbs.JddRuntimeException:
Action CREATE not possible for table BC_SYNCLOG.
Table exists in database with different structure.
primary keyaction = DROPorigin = PrimaryKey =
TableName : BC_SYNCLOG
null
null
Columnname = TIMESTMP
isDescending:false
Columnname = VMID
isDescending:false
target = null

E R R O R ******* (DbTableModificationAnalyser dev DD.MM.YYYY HH:MM:SS)
HH:MM:SS YYYY-MM-SS dbs-Error: Table BC_SYNCLOG could not be analysed


Read more...

Product

SAP Solution Manager 7.1

Keywords

migration , KBA , BC-INS-JCI , Java component inst. / jload jmigmon, jsizecheck , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.