• State Not Answered
  • Replies 1 reply
  • Subscribers 96 subscribers
  • Views 1215 views
  • Users 0 members are here
Options
Related

Issue during SAP transfer file import

saurabh g
over 2 years ago

Hi,

OneIM Version 8.2.1

We have to import some transport files in the SAP client to onboard any SAP system to One IM.

These SAPRepository.zip, SAPTable.zip, SAPTRANSPORT_70.ZIP, and SAPROLE.zip transport files are to be imported into the SAP system.
Customer tried to install Add-ON and it is not supported in their system. Customer SAP Version is 750  ECC 6.0 EHP8

Please find below the attached information.

Can anyone help me? Thanks

Parents
  • 0 over 2 years ago

    Steps to fix-

    One of the main and more time consuming steps during an installation/system copy is the execution of migration monitor (MigMon). This tool is responsible for triggering the R3load processes to perform the export/import of data from/to the database.

    In case of issues during this step, we can follow the same logic described in the previous section. First of all, let's check the step that failed:

    ERROR 2013-05-01 07:33:16.377 [sixxcstepexecute.cpp:995]
    FCO-00011 The step runMigrationMonitor with step key|

    Indeed, as per the log, we saw SAPinst faced an issue while trying to run the migmon. And, checking before that, it is possible to see the command line SAPinst calls to launch MigMon, followed by the a list of packages that were exported/imported with ERROR:

    WARNING 2013-06-21 16:08:55.226
    CJSlibModule::writeWarning_impl()
    Execution of the command "/sapbackup/DBI/sapinst_exe.25267.
    1371825687/jre/bin/java -classpath migmon.jar -showversion -Xmx1024m com
    .sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code
    103. Output:
    java version "1.6.0_45"
    Java(TM) SE Runtime Environment (build 6.1.051)
    SAP Java Server VM (build 6.1.051 23.5-b02, May 30 2013 00:33:03 -
    61_REL - optU - linux amd64 - 6 - bas2:197575 (mixed mode))
    ...
    Loading of 'SAP0000' import package: ERROR
    Loading of 'SAPUSER3_1' import package: ERROR

    Even though migmon is completely integrated into SAPinst as of NW 7.0, since it triggers R3load processes to perform the import/export, separate logs are created for these activities. The logs have the <package>.log naming convention.

    In this case, the relevant log files to be checked would be SAP000.log and SAPUSER3_1.log.

    Greeting,

    Rachel Gomez

Reply
  • 0 over 2 years ago

    Steps to fix-

    One of the main and more time consuming steps during an installation/system copy is the execution of migration monitor (MigMon). This tool is responsible for triggering the R3load processes to perform the export/import of data from/to the database.

    In case of issues during this step, we can follow the same logic described in the previous section. First of all, let's check the step that failed:

    ERROR 2013-05-01 07:33:16.377 [sixxcstepexecute.cpp:995]
    FCO-00011 The step runMigrationMonitor with step key|

    Indeed, as per the log, we saw SAPinst faced an issue while trying to run the migmon. And, checking before that, it is possible to see the command line SAPinst calls to launch MigMon, followed by the a list of packages that were exported/imported with ERROR:

    WARNING 2013-06-21 16:08:55.226
    CJSlibModule::writeWarning_impl()
    Execution of the command "/sapbackup/DBI/sapinst_exe.25267.
    1371825687/jre/bin/java -classpath migmon.jar -showversion -Xmx1024m com
    .sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code
    103. Output:
    java version "1.6.0_45"
    Java(TM) SE Runtime Environment (build 6.1.051)
    SAP Java Server VM (build 6.1.051 23.5-b02, May 30 2013 00:33:03 -
    61_REL - optU - linux amd64 - 6 - bas2:197575 (mixed mode))
    ...
    Loading of 'SAP0000' import package: ERROR
    Loading of 'SAPUSER3_1' import package: ERROR

    Even though migmon is completely integrated into SAPinst as of NW 7.0, since it triggers R3load processes to perform the import/export, separate logs are created for these activities. The logs have the <package>.log naming convention.

    In this case, the relevant log files to be checked would be SAP000.log and SAPUSER3_1.log.

    Greeting,

    Rachel Gomez

Children
No Data