SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
<br>
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
<br>
We are again getting error in following steps:
<br>
sapinst.log
<br>
<br>WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT  - 20090210_1447ifx1_r8
GC   - 200902_24)
I<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
<br>Loading of 'SAPNTAB' import package: OK
<br>Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28.<br>
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
<br>
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
<br>
ERROR 2009-09-30 23:25:28.914
FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
<br>
<br>import_monitor.log.
<br>****************************************************************************************************************************************************
<br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
<br>
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
<br>
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
<br>
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
<br>*************************************************************************************************************************************************
<br>SAPAPPL02.LOG
<br>**************************************************************************************************************************************************
<br>TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
<br>
(DB) INFO: TVV1 deleted/truncated #20091001110304
<br>
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
<br>
(DB) ERROR: DDL statement failed<br>
(ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
DbSlExecute: rc = 99<br>
  (SQL error -539)<br>
  error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
<br>
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
<br>
We are again getting error in following steps:
<br>
sapinst.log
<br>
<br>WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT  - 20090210_1447ifx1_r8
GC   - 200902_24)
I<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
<br>Loading of 'SAPNTAB' import package: OK
<br>Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28.<br>
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
<br>
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
<br>
ERROR 2009-09-30 23:25:28.914
FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
<br>
<br>import_monitor.log.
<br>****************************************************************************************************************************************************
<br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
<br>
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
<br>
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
<br>
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
<br>*************************************************************************************************************************************************
<br>SAPAPPL02.LOG
<br>**************************************************************************************************************************************************
<br>TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
<br>
(DB) INFO: TVV1 deleted/truncated #20091001110304
<br>
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
<br>
(DB) ERROR: DDL statement failed<br>
(ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
DbSlExecute: rc = 99<br>
  (SQL error -539)<br>
  error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Similar Messages

  • SAP ECC error:'Migration Monitor' exits with error code 103.

    Hi All,
    I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
    I am stuck at the import ABAP.Getting error
    ERROR 2008-08-08 16:10:53
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    1) imort_monitor.java.log-->contains
    java version "1.4.2_12"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
    Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
    Import Monitor jobs: running 1, waiting 0, completed 18, failed 0, total 19.
    Loading of 'SAPVIEW' import package: ERROR
    Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
    2)import_monitor.log
    ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPVIEW' import package is interrupted with R3load error.
    Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
    For mode details see 'SAPVIEW.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    INFO: 2008-08-08 16:10:52
    All import packages are processed.
    WARNING: 2008-08-08 16:10:52
    1 error(s) during processing of packages.
    INFO: 2008-08-08 16:10:52
    Import Monitor is stopped.
    3)SAPVIEW.log
      error message returned by DbSl:
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) ERROR: DDL statement failed
    (CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001"  ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001",  T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
    DbSlExecute: rc = 103
      (SQL error -942)
      error message returned by DbSl:
    (DB) INFO: disconnected from DB
    D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
    D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
    Only SAPDB: SAPSID srvice of SAP DB is only up.
    No other services of database are  up.And i am not able to up the other services also.
    Is it required to up the other services?
    If not?
    Why this error is occuring?
    Any help will be appreciated.
    Thanks&Regards
    Manisha das

    Hello Manisha,
    The one of the possible reasons for this is due to lack of H/W.
    Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
    If the issue is with H/W, then this should fix the issue.
    Hope it helps,
    Regards,
    Satish.

  • Solut Manager v4.0 install. error : CJS-30022 Program 'Migration Monitor

    Hi Experts
    I am trying to install Solution Manager 4.0. I am performing installation on Windows 2003 server.
    While installing SolMan, everything goes fine, until step # 17 while importingABAP monitor jobs, then it runs into below error messages.
    ERROR 2007-08-11 18:03:25
    CJS-30022 Program 'Migration Monitor'
    exits with error code 103.
    For details see log file(s) import_monitor.java.log, import_monitor.log.
    C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\sapinst.log
    FCO-00011 The step runMigrationMonitor
    with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|
    NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|
    NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    WARNING 2007-08-11 18:03:25
    Execution of the command "C:\java\bin\java.exe -classpath migmon.
    jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs
    "C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 1\EXP1;C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 2\EXP2;
    C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 3\EXP3;C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 4\EXP4" -installDir
    "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\HSM\SYS\exe\uc\NTI386\R3load.exe -tskFiles
    yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output:
    java version "1.4.2_15"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02)
    Java HotSpot(TM) Client VM (build 1.4.2_15-b02, mixed mode)
    Import Monitor jobs: running 1, waiting 9, completed 8, failed 0, total 18.
    Import Monitor jobs: running 2, waiting 8, completed 8, failed 0, total 18.
    Import Monitor jobs: running 3, waiting 7, completed 8, failed 0, total 18.
    Loading of 'SAPAPPL0' import package: ERROR
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 0, waiting 7, completed 8, failed 3, total 18
    Any suggesstions/ideas for this error
    Regards
    Rahul

    Check the logfile SAPAPPL0.log for errors...
    Markus

  • CJS-30022  Program 'Migration Monitor'

    Hi Experts
    I am trying to install Solution Manager 4.0. I am performing installation on Windows 2003 server.
    While installing SolMan, everything goes fine, until step # 17 while importingABAP monitor jobs, then it runs into below error messages.
    ERROR 2007-08-11 18:03:25
    CJS-30022  Program 'Migration Monitor'
    exits with error code 103.
    For details see log file(s) import_monitor.java.log, import_monitor.log.
    C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\sapinst.log
    FCO-00011  The step runMigrationMonitor
    with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|
    NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|
    NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    WARNING 2007-08-11 18:03:25
    Execution of the command "C:\java\bin\java.exe -classpath migmon.
    jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs
    "C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 1\EXP1;C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 2\EXP2;
    C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 3\EXP3;C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 4\EXP4" -installDir
    "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\HSM\SYS\exe\uc\NTI386\R3load.exe -tskFiles
    yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output:
    java version "1.4.2_15"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02)
    Java HotSpot(TM) Client VM (build 1.4.2_15-b02, mixed mode)
    Import Monitor jobs: running 1, waiting 9, completed 8, failed 0, total 18.
    Import Monitor jobs: running 2, waiting 8, completed 8, failed 0, total 18.
    Import Monitor jobs: running 3, waiting 7, completed 8, failed 0, total 18.
    Loading of 'SAPAPPL0' import package: ERROR
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 0, waiting 7, completed 8, failed 3, total 18
    Any suggesstions/ideas for this error
    Regards
    Rahul

    I just encountered this same error, except it was during an export of an ECC 6.0 Source system.  I searched SDN for an answer and then worked my counterpart in Japan.  My problem turned out to be the version of the R3Load.exe I was using.  It was the latest available on Marketplace.  I reverted back to the one that was delivered with kernel patch 102 and my export completed with no errors.  I made sure to do the same on the Target system so I did not get the errors during the import.
    Hope this helps...

  • Transport control program tp ended with error code 0212

    Hi all,
    I have created a two system landscape of development & production server. But while I am releasing any request from develpoment server a error is showing: " Transport control program tp ended with error code 0212 Errors: could not access file as supposed (see dev_tp or S".I have chosen development server as domain controller. TMS alert viewer error message also contains the following information------>command: TMS_MGR_READ_TRANSPORT_QUEUE
                                                                           service: transport service
                                                                           start : online
                                                                           Function: TMS_TP_SHOW_BUFFER
                                                                           message: TP_REPORTED_ERROR
    In import monitor it's showing : "tp finished: could not access file as supposed (see dev_tp or SLOG1113.K"
    Can you tell me how to resolve this issue?

    dev_tp contains:    
    This is R3trans.exe version 6.14 (release 700 - 09.04.10 - 11:26:00).
    unicode enabled version
    usage: R3trans.exe [<options>] <control_file>
    The control_file describes what R3trans has to do.
    The following options are possible:
    -c f1 f2 : Copy file f1 to f2 with character set conversion.
    -d       : DB connect. Test if SAP database is available.
    -i file  : Import from file without using a control file.
    -l file  : List the contents of file to the log file.
    -m file  : List the contents of file to allow tp to create a cofile.
    -t       : Test. All database changes are rolled back.
    -t4      : Trace level 4. Switch on developer trace.
    -u <int> : Unconditional modes. See below.
    -v       : Verbose. Write more details to the log file.
    -w file  : Log file. The default log file is 'trans.log'.
    -x       : DB connect without access on any SAP table.
    R3trans.exe finished (0012).
    & the slog file is not there in the trans/log directory

  • STMS: Transport control program tp ended with error code 0232

    Dear ERP Gurus,
    I just encountered problem with STMS in my PRD system. The import is just stuck up on "tp connecting to database". It won't continue unitl the system gives me this error message:
    Transport control program tp ended with error code 0232
    Errors: connect failed
    The tp System log says:
    ERROR: Connect to PRD failed (20090227135454, probably wrong environment)
    I have verified that the suggestion in SAP Note 165708 has already been implemented in our DEV, QAS, and PRD instances.
    Any idea why I am having this problem? Imports were running fine yesterday. Please help.
    Your prompt response is highly appreciated.
    Thanks a lot.
    Best Regards,
    Albert

    Hi Albert,
    First check import monitor and delete all requests from queue, which are still getting imported.
    And go to /usr/sap/trans/tmp and mv all those tmp files to other location.
    Then kill all OS jobs which are getting execute with tp.
    Check all jobs are runnig fine, related to transportation. If not reschedule the same.
    Then start importing.
    Before doing this just check whether your stms related RFCs are working fine.
    I think One of your RFC is getting struck. just try to change ip or hostname accordingly and try.
    Regards
    Nick Loy

  • Transport control program tp ended with error code 0249

    Hello guys,
          I am facing an when importing transport.  After I click import to the transport in STMS, before it runs, a message window is displayed immediately. This was working find until last week, any kind of transport is followed by the same error.
    Transport control program tp ended with error code 0249
    Message no. XT200
    Diagnosis
    An error occurred when executing a tp command.
      Command: IMPORT BWDK903312 BIW client200 U0 pf=
    sapbiw1a\s
      Return code: 0249
      Error text: connect failed due to DbSL load lib failure
    Has anyone faced this error while trying to import a transport? I have not found the same error in sdn (0249)
    help will be appreciated.
    thanks
    DGF

    Your are right, but which is the Basis forum?
    Business Process Expert 
    Database & OS Platforms  ABAP Development 
    Enterprise SOA  Portal 
    Emerging Technologies 
    SAP Solutions 
    Business Intelligence 
    Scripting Languages 
    SAP Business One  Industries 
    Community Discussions 
    SAP NetWeaver  Application Server  Integration and Certification Center (ICC) 

  • Transport Control program tp edded with error code 0247

    Hi Guys
    I have co setup TMS in a three system landscape, with the PRD server being the transport domain controller. The three systems are running on the HP -UX OS. The import queue of the PRD server remains empty. All the checks on the TMS configurations shows OK.
    When i try to add the transport request from Extras > Other Requets> ADD and enter the transport requet no. I receive this message:
    Transport Control program tp edded with error code 0247
    Errors: add buffer has problem with data- and/or cofile
    Can someone assist? I have got some challenges on linux. Are there steps i need to follow or is there something i need to do?
    Cheers,
    Daniel

    Daniel,
    Mostly this issue comes when you have some permission problem.
    Please check the permission of your /usr/sap/trans/bin and related directories.
    It is ideally sidadm.sapsys. Please give 775 to respective directories.
    If your Trans directory is mounted, please check if it is properly mounted or not.
    If it is not working, please check the log in TMS alert Viewer (Go to STMS  Monitor>TMS Alerts>TMS Alert Viewer)
    and paste the detailed log here.
    Regards,
    Sujit.

  • Transport control program tp ended with error code 0211

    Dear Experts,
    I have a problem in doing the import after the client export was successfully done.
    I am actaully tring to do a client import/export from the PRD server to DEV server.
    On PRD the client is 900 and on the DEV the client is 240.
    I have manually copied the transport requests created into the
    /usr/sap/trans/cofiles and /usr/sap/trans/data folders to the same on the DEV server.
    After coping them,
    I have tried to add these transport requests to the DEV server queue, i get the following error message
    Transport control program tp ended with error code 0211
    Message no. XT200
    Diagnosis
    An error occurred when executing a tp command.
      Command: ADDTOBUFFER RT2KT00014 RT1 pf=/usr/sap/trans/bin/T
      Return code: 0211
      Error text: no info about transport request found
      Request: RT2KT00014
    System Response
    The function terminates.
    Procedure
    Correct the error and execute the command again if necessary.
    After this I have tried to add the transports to the buffer at the OS level using the command
    ./tp pf=TPPARAM addtobuffer "RT2KT00014" RT1 U18 by going to the folder
    /usr/sap/trans/bin
    But it says that the tp is not found.
    I have also checked the permissions for the TRANS folder, it has full access i.e 777
    This is where i am struck, and the client has to be imported asap as the requirement for the SUPPORT TEAM is very urgent.
    We are on AIX, Oracle 10G and ECC6
    Thanks and regards
    Harry

    Dear Imtiaz,
    Thanks for your quick fire reply...
    The link helped me but it could not resolve my issue..
    Infact i found it my self that the transport requests had to be given full FILE PERMISSIONS at the OS level
    I logged in as ROOT
    and changed directory to /usr/sap/trans/cofile and gave the command
    chmod 777 RT00014.RT2 and
    chmod 777 RX00014.RT2
    and then went to STMS>SYSTEMS>Import View>Extras>Other requests--> Add ..
    Here i added the request nos and then it added up in the queue and then i started the import.
    Anyway thank you very for your reply..
    Awareded points to you.
    Thanks and regards
    Harry...

  • Transport control program tp ended with error code 0247

    Hi,
    Our landscape is such that any transport request once released, gets imported to Q system immediately. However there is another system (another box REG - regression testing) to which I would like to import a request but the transport queue of REG system does not show the request. So I tried to explicitly add it to the queue but I get the following error message, 'Transport control program tp ended with error code 0247.
    There doesn't seem to be a problem with data & CO files as the same request is in Q system and the changes are all transported successfully.
    This request is a transport of copy that contains some ABAP code. (changes to the relevant package can be saved only in local requests therefore transport of copy is recommended to transport the changes).
    The changes appear correctly in Q system but for REG system the request neither appears in the queue nor be added to it.
    Can someone advise where the problem is.
    Cheers,
    KC

    Hi
    When the REG system is not in the system landscape, probably you may not have Data & Co files in that system & you need to have those files separately in the REG system path & then import it.
    Do consult Basis team on this issue.
    Thanks,
    Murali.

  • Transport control program tp ended with error code 0203

    when i import queue and transport queue from dev to prd ,error show:
    Transport control program tp ended with error code 0203
    Message no. XT200
    Diagnosis
    An error occurred when executing a tp command.
      Command: IMPORT DEVK900298 P01 clientP01 U0 pf=/usr/sap/tra
      Return code: 0203
      Error text: wrong syntax in tp call
      Request: DEVK900298
    System Response
    The function terminates.
    Procedure
    Correct the error and execute the command again if necessary.

    Dear Allen,
    The transport control program tp collects all return codes that occur when a tp command is executed. From all of these single return codes, a combined return code is calculated that tp outputs as a result at the end the command. During an import, for example, all return codes for individual import steps are handled. If a special return code does not occur, then the combined return code at the end is the maximum of individual return codes that occur. In addition to the value of the return code, tp also gives a short description of this return code. You can display this short description using the command explainrc.
    Normally, all return codes that occur originate from individual transport steps. Since these individual return codes can only have the following values 0, 4, 6, 8, 12, 13, 14, 16, the combined return code also has one of these values. However, if a general error occurs, a single return code over 200 is generated. For example, this could arise if tp cannot establish a connection to the database. The maximum return code for all single transport steps is output in a separate message before specifying the combined returned code. In this case, the combined return code is always the return code of the general error message.
    <b>tp Commands:</b>
    tp addtobuffer <request> <sapsid>
    As of Release 4.6A, an explicit addtobuffer command leaves the position of the entry unchanged, if the relevant transport request is already in the buffer. Only the status of the entry is changed:
    Unconditional modes appearing in the command line are added to the unconditional modes in the buffer.
    All the steps of the entry are re-initialized.
    If the entry found is not an initial entry, the import step for the command file is set to *4000 .
    Before you call this command and its options, consider the effects of changing the import sequence.
    tp cleanbuffer <sapsid>
    This deletes successfully imported change requests from the list of requests that are marked for import into the SAP System <SAPSID>. This function is contained in the commands tp import all <sapsid> and tp put <sapsid> .
    tp delfrombuffer <request> <sapsid>
    If the specified request is marked for import into the specified SAP System, this flag is deleted from the import list.
    Before you call this command, consider the effects of changing the import sequence.
    As of Release 4.6A: If a transport request was only partially imported, you can delete this type of transport request from the buffer. However, if a deleted transport request is placed in the buffer (without having been initially or completely imported), the attributes of the old entry are reactivated. This means the return codes, the unconditional modes and tags of the deleted entry appear in the new entry.
    tp delstopmark <sapsid>
    If the list of requests marked for import into the specified SAP System contains a STOP mark, the mark is deleted.
    tp export <request>
    This exports the complete request from the source system. This command starts the export of a request from the operating system level. Only use this command in exceptional cases. The SAP System uses the command expwbo to release requests from CTS transactions.
    tp reformatbuffer <sapsid> [options]
    This automatically reformats the entire buffer.
    As of Release 4.5A, there are 2 different formats for buffer entries. (As of Release 4.5A, tp can work with both formats, and with a puffer containing heterogeneous entries. As of Release 4.6A, tp can work with 3 formats.)
    However, in certain cases entries with the old formatting have to be reformatted during the normal run of tp . In this case, the entire buffer is automatically reformatted.
    If you use the options downtorelease and Iagree for command reformatbuffer , you can format the buffer so that its formatting is compatible with an older release:
    Option downtorelease <Release>
    The command reformatbuffer with this option formats the buffer so that the formatting corresponds to the one used in an old release. This is necessary if tp writes buffer entries to the buffer of another system, but uses a buffer format that the transport control programs does not understand in this system.
    Since older formats cannot store the same amount of information as the newer ones, some information contained in the original buffer may not be stored in the unformatted buffer. This may lead to data loss.
    To avoid data loss, the original buffer is stored. In addition, you have the following functions:
    Displaying the unformatted buffer (using showbuffer <SID> )
    Displaying the original buffer (using showbuffer buffer=<SID>SAV )
    Accepting the unformatted buffer (using reformatbuffer and the option Iagree yes )
    Resetting the changes (using reformatpuffer and the option Iagree no )
    If you call reformatpuffer using downtorelease , tp displays in detail if information was lost by reformatting, and what that information was. tp also names the commands that is has to execute to accept or reject the changes.
    If you use the option downtorelease , you must also specify the option Iagree with yes or no . You cannot use the transport system until you decide to accept or reject the changes.
    Option Iagree
    Here are the following values for this option:
    yes ( true )
    Accept the change made by tp reformatbuffer <SID> downtorelease <rel>
    In this case, tp deleted the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
    no ( false )
    Reject the change made by tp reformatbuffer <SID> downtorelease <rel> In this case, tp copies the backup of the original buffer back and deletes the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
    tp setstopmark <sapsid>
    A special STOP mark is added to the list of requests registered for import into the specified SAP System. The commands tp import all <sapsid> and tp put <sapsid> only process the requests in front of this stop mark.
    If there is no stop mark, it is automatically generated by the commands
    tp import all <sapsid> and tp put <sapsid> .
    When all the requests in front of the stop mark have been imported successfully, at the end of all the calls the related marks and the mark itself are deleted.
    A STOP mark can only be placed at the end of the change requests that have already been marked. In addition, it can only be set if no other mark of the same kind already exists.
    tp showparams <sapsid>
    This tp function displays which values the individual parameters of the transport profile have for the current SAP System.
    tp verse <request>
    This creates versions of the objects in the specified request. This transport step is contained in command export .
    As of Release 4.5A, more actions that prepare the export are performed in this step.
    Thanks and Regards,
    Naveen.

  • Transport control program tp ended with error code 0212 | URGENT

    Hi All,
             We are trying to import requests in our PRD system. As soon as we select the request and try to import it , we get the error "Transport control program tp ended with error code 0212".
    This is tp version 305.12.42 (release 46D) for ANY database            
    /usr/sap/trans/cofiles/K915883.<SID> for transport: <SID>K915883: Permissio
    HALT 20070222114323                                                    
    ERROR: /usr/sap/trans/cofiles/K915883.<SID> : cant open                  
    : Permission denied                                                    
    ERROR: EXIT(16) -> process ID is: 6878                                 
    tp returncode summary:                                                 
    TOOLS: Highest return code of single steps was: 16                     
    ERRORS: Highest tp internal error was: 0212                            
    Output from tools called by tp:                                        
    This is R3trans version 6.05 (release 46D - 18.10.01 - 11:30:00).      
    R3trans finished (0000).                                                                               
    When i checked the transport tool and rfc destinations, everything was successful.
    When i tried to do tp connect -
    23> tp connect <SID> pf=/usr/sap/tran/bin/TP_DOMAIN_<SID>.PFL
    This is tp version 305.12.42 (release 46D) for ANY database
    E-/usr/sap/tran/bin/TP_DOMAIN_<SID>.PFL could not be opened.
    EXIT
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 0
    ERRORS: Highest tp internal error was: 0212
    tp finished with return code: 212
    meaning:
      could not access file as supposed (see SLOG for more details)
    We are having SAP 4.6C with DB -Oracle and OS HP-UX.
    Please let me know whow to rectifiy the issue. The situation here is getting worse.
    Regards,
    NK

    Hi Ruchit, Sorry for the delay. Here is the file you wanted -
    steic25q:root>ls
    DOMAIN.CFG          TPPARAM.bak         TP_DOMAIN_ID1.PFL   TP_DOMAIN_IQ1.PFL
    TMS_TEST.IS1        TPPRAMA0918         TP_DOMAIN_ID1.orig  nik.dev_evt
    TPPARAM             TP_DOMAIN_ID1.BAK   TP_DOMAIN_IP1.BAK
    steic25q:root>more TP_DOMAIN_ID1.PFL
    #TMS:0078:DOMAIN_ID1
    Caution !
    This file was generated by the Transport Management System.
    Do not change this file using a text editor.
    For more information, refer to the online documentation of the
    Transaction STMS.
    If this file was destroyed, it can be regenerated in the TMS.
    To do this, log on to the domain controller (system ID1) and call
    transaction STMS. In the System Overview, you can distribute the TMS
    configuration. This regenerates the file.
    STMS -> Overview -> Systems -> Extras -> Distribute TMS configugration
    TRANSDIR            = /usr/sap/trans
    DU1/CTC             = 1
    DU1/DUMMY           = 1
    DU1/NBUFFORM        = 1
    DU1/TP_VERSION      = 266
    DU2/CTC             = 1
    DU2/DUMMY           = 1
    DU2/NBUFFORM        = 1
    DU2/TP_VERSION      = 266
    ID1/CTC             = 0
    ID1/DBHOST          = steic24q
    ID1/DBLIBPATH       = /usr/sap/ID1/SYS/exe/run
    ID1/DBNAME          = ID1
    ID1/DBSWPATH        = /oracle/ID1/817_64
    ID1/DBTYPE          = ora
    ID1/NBUFFORM        = 1
    ID1/TP_VERSION      = 266
    IP1/CTC             = 0
    IP1/DBHOST          = steic25q
    IP1/DBLIBPATH       = /usr/sap/IP1/SYS/exe/run
    IP1/DBNAME          = IP1
    IP1/DBSWPATH        = /oracle/IP1/817_64
    IP1/DBTYPE          = ora
    IP1/NBUFFORM        = 1
    IP1/TP_VERSION      = 266
    IQ1/CTC             = 1
    IQ1/DBHOST          = cbnysap2
    IQ1/DBLIBPATH       = /usr/sap/IQ1/SYS/exe/run
    IQ1/DBNAME          = IQ1
    IQ1/DBSWPATH        = /oracle/IP1/817_64
    IQ1/DBTYPE          = ora
    IQ1/NBUFFORM        = 1
    IQ1/TP_VERSION      = 266
    TRN/CTC             = 1
    TRN/DUMMY           = 1
    TRN/NBUFFORM        = 1
    TRN/TP_VERSION      = 266
    steic25q:root>

  • Re: Transport control program tp ended with error code 0212

    Hi ,
              When transport request is added to import queue, getting following error :
    "Transport control program tp ended with error code 0212 "
    Please find the slog file description as follows:
       HALT 20110530001050
    ERROR: /usr/sap/trans/cofiles/K904416.<SID>: cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 2273
    HALT 20110530004629
    ERROR: /usr/sap/trans/cofiles/K904416.<SID> : cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 14341
    HALT 20110530004703
    ERROR: /usr/sap/trans/cofiles/K904416.<SID> : cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 14514
    How to correct this ?
    Thanks
    Srikanth

    Hi,
    It may happen happen due to permission issue when you are having SAN and sharing common trans directory now to check the permission of the file you have to login at os level and check the permission of the TR.
    cd /usr/sap/trans/cofiles/
    ls -l K904416<SID> - now here it will show the permission of the file please paste the output
    Thanks,
    Saleem

  • Help with Transport control program tp ended with error code 0203

    when i import queue and transport queue from dev to prd ,error show:
    Transport control program tp ended with error code 0203
    Message no. XT200
    Diagnosis
    An error occurred when executing a tp command.
    Command: IMPORT DEVK900298 P01 clientP01 U0 pf=/usr/sap/tra
    Return code: 0203
    Error text: wrong syntax in tp call
    Request: DEVK900298
    System Response
    The function terminates.
    Procedure
    Correct the error and execute the command again if necessary.

    Thank you !
    My DEV system  TP profile parameters is :
    TRANSDIR            = /usr/sap/trans
    DEV/CTC             = 0
    DEV/DBHOST          = P550A
    DEV/DBLIBPATH       = /usr/sap/DEV/DVEBMGS01/exe
    DEV/DBNAME          = DEV
    DEV/DBTYPE          = ora
    DEV/NBUFFORM        = 1
    DEV/TP_VERSION      = 266
    #System from Transport Domain DOMAIN_P01
    #TMS:0002:DOMAIN_P01
    P01/DUMMY           = 1
    P01/NBUFFORM        = 1
    P01/TP_VERSION      = 266
    P01/CTC             = 1
    My PRD system  TP profile parameters is :
    P01/CTC             = 0
    P01/DBHOST          = XCPRD01
    P01/DBLIBPATH       = /usr/sap/P01/DVEBMGS01/exe
    P01/DBNAME          = P01
    P01/DBTYPE          = ora
    P01/NBUFFORM        = 1
    P01/TP_VERSION      = 266
    #System from Transport Domain DOMAIN_DEV
    #TMS:0009:DOMAIN_DEV
    DEV/DUMMY           = 1
    DEV/NBUFFORM        = 1
    DEV/TP_VERSION      = 266
    DEV/CTC             = 1

  • Transport control program tp ended with error code 0232

    Dear all
    I've change password for user SAPSR3 by mistake
    the result from brtools is "password changed successfully in table OPS$CAPADM.SAPUSER for user SAPSR3"
    after that i can not transport to my production client
    with error : TP_REPORTED_ERROR
    Transport control program tp ended with error code 0232
    Can anybody help me please
    thanks & rgds,
    Della

    I've changed my SAPSR3 password to sap but still error
    this is the error log from Check Transport Tool
    DB Connect            Link to database failed
    This is tp version 372.04.70 (release 700, unicode enabled)
    Warning: Parameter DBLIBPATH is no longer used.
    ERROR: Connect to CAP failed (20091217174435, probably wrong environmen
    TRACE-INFO: 1:  [dev trc     ,00000]  Thu Dec 17 17:44:35 2009
    0.007435
    TRACE-INFO: 2:  [dev trc     ,00000]  DlLoadLib() success: dlopen("/usr
    0.007448
    TRACE-INFO: 3:  [dev trc     ,00000]  Got
    LIBPATH=/usr/sap/CAP/DVEBMGS32/exe:/usr/sap/CAP/DVEBMGS32/exe:/usr/lib
    lient from environment
    TRACE-INFO: 4:
    0.008053
    TRACE-INFO: 5:  [dev trc     ,00000]  Oracle Client Version: '10.2.0.2.
    0.008140
    TRACE-INFO: 6:  [dev trc     ,00000]    >oci_initialize(con_hdl=0, char
    0.008158
    TRACE-INFO: 7:  [dev trc     ,00000]  application info callback registe
    0.008173
    TRACE-INFO: 8:  [dev trc     ,00000]  OCIEnvCreate(mode=16384=OCI_UTF16
    0.010330
    TRACE-INFO: 9:  [dev trc     ,00000]  Client character set UTF16 -> UTF
    0.010421
    TRACE-INFO: 10:  [dev trc     ,00000]  Client NLS setting (OCINlsGetInf

Maybe you are looking for

  • AP Trial Balance

    I'm not sure if this is the best place to ask this question, but here goes... I'm trying to re-create the AP Trial Balance in Discoverer so I can add additional info for the Accountants allowing them to analyze the data better. I found XLA_TRIAL_BALA

  • How do you add a watermark to a protected file?

    How do you add a watermark to a protected file?

  • "Fire-vault protected home folder did not open and needs to be repaired."

    I recently updated my macbook to leopard and after my laptop downloaded system updates, it had to restart but when I came to the login section and tried to login, I get this message: "Fire-vault protected home folder did not open and needs to be repa

  • Cannot update customer name in R12.0.6

    We are experiencing one issue where we cannot update the customer name in the customer form in AR. When we try to update a customer name we get an error message. "Error Page You have encountered an unexpected error. Please contact the System Administ

  • Place of Singleton class in OO Design

    Hi Can any body make me clear on, why we make use of Singleton Class and how it is related to Object Oriented world. Thanks, Prasanth