Import package failed

hi
When compiled with java 1.5, I get the message package a.b.c does not exist.
Into what directory do you need to store a executalbe jar file in order to be able to import the package?

hi
When compiled with java 1.5, I get the message
package a.b.c does not exist.
Into what directory do you need to store a executalbe
jar file in order to be able to import the package?you have not yet successfully compile your project and you are already wanting to make an executable jar file? i say to compile it first, then proceed.
[com]
   |---[mysite]
              |----[app1]
              |          |---myclass1.java      // package com.mysite.app1
              |
              |----[app2]
                         |---myclass2.java      // pakage com.mysite.app2
after compile 9if the folder is not there, the compiler will create the folder structure for you.
[com]
   |---[mysite]
              |----[app1]
              |          |---myclass1.class      // package com.mysite.app1
              |
              |----[app2]
                         |---myclass2.class      // pakage com.mysite.app2as you can see..the packaging of the java class is very much similiar to the file system
for executable jar file
the manifest file should include
Main-Class: com.mysite.app1.MyClass1 // if myClass1 is the main class (notice the folder structure)

Similar Messages

  • Re-importing a package fails

    Hi,
    usually, you can always re-import a package into OWB (10gR2) and synchronize it with the database. But I have the phenomenon that some (not all) packages fail in this process; after pressing Finish the import wizard dies and does almost nothing. I tracked it down to the the DebugSQL.000.log file and found as last entry:
    select line, text from all_source@owb_1335 where owner = 'DWH_ADMIN' and name = 'UTIL' and type = 'PACKAGE' order by line
    With other packages which do the re-import perfectly the next line would be the analogous query to read the PACKAGE BODY. This would indicate an overflow issue, but the package isn't big at all and works well when imported into another module. I cannot find any trace log of this failure. And - strange enough - the failing process is still able to drop the temporary database link owb_nnnn.
    Some ideas
    regards
    Thomas

    Hi Borkur,
    Dropping and re-importing the package would work well (works for another module) but this is a package whose procedures and functions are heavily referenced in several mappings and process flows (supports the custom job management). So, I would be forced to re-synchronize them all which I want to avoid. The other way would be to modify the package manually (only the signature is needed not the code since I will not deploy it from OWB, in fact, I deployed it from Oracle Designer !!!). But OWB Paris doesn't allow this. Once imported, always imported. You can modify imported tables, procedures, functions but not packages. Or is there a way ???
    regards
    Thomas

  • NetWeaver install on Windows - Import Monitor failing to import packages

    Following are the errors in import_monitor.log during installation.  The errors are due to sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline.  7 out of 28 packages imported fine.  What is the fix?
    TRACE: 2009-11-24 12:07:32 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER' import package is started.
    TRACE: 2009-11-24 12:07:32 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPUSER' import package into database:
    C:\usr\sap\DE2\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -nolog -c 50000
    TRACE: 2009-11-24 12:07:32 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is started.
    TRACE: 2009-11-24 12:07:32 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAP0000' import package into database:
    C:\usr\sap\DE2\SYS\exe\uc\NTI386\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -nolog -c 50000
    ERROR: 2009-11-24 12:07:33 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER' import package is interrupted with R3load error.
    Process 'C:\usr\sap\DE2\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -nolog -c 50000' exited with return code 2.
    For mode details see 'SAPUSER.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
    ERROR: 2009-11-24 12:07:33 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is interrupted with R3load error.
    Process 'C:\usr\sap\DE2\SYS\exe\uc\NTI386\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -nolog -c 50000' exited with return code 2.
    For mode details see 'SAP0000.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
    WARNING: 2009-11-24 12:08:02
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2009-11-24 12:08:02
    20 error(s) during processing of packages.
    INFO: 2009-11-24 12:08:02
    Import Monitor is stopped.
    Jay
    Part of details of sapuser.log.
    C:\usr\sap\DE2\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP
    C:\usr\sap\DE2\SYS\exe\uc\NTI386\R3load.exe: version R7.01/V1.4 [UNICODE]
    Compiled Feb  3 2009 23:16:17
    C:\usr\sap\DE2\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -nolog -c 50000
    DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:[5] database not running))
    (DB) ERROR: db_connect rc = 256
    DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:[5] database not running))
    (DB) ERROR: DbSlErrorMsg rc = 99
    C:\usr\sap\DE2\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    C:\usr\sap\DE2\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20091124120733
    Jay
    Edited by: jay sethi on Nov 24, 2009 6:58 PM

    What is the content of 'SAPUSER.log'?

  • PI 711 Installation: Loading of 'SAPNTAB' import package: error but no log

    Hello,
    I'm perfromong an installation of a SAP PI 7.11 ystem on windoows Server 2003 and Oracle 10.2 .
    I've perfromed the installation of the DEV system without particular issue.
    But now when tryning to install the QAS system , I can't finish the installation : Im' stuck in the import ABAP step ...
    It is impossible to import the 'SAPNTAB' package. I couln't find the reason.
    I've tried updating the R3load binary, rebooting the server, restarting the instalaltion from scratch but it didn't help.
    Here I provide you the logs, maybe you can help me
    SAPNTAB.log
    E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110223195542
    E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/711_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
    E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: version R7.11/V1.4 [UNICODE]
    Compiled Dec 14 2010 22:52:23
    E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -stop_on_error -loadprocedure fast
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (DB) INFO: SVERS deleted/truncated #20110223195543
    sapinst_dev.log
    Syslib info about system call. OS message 109 (The pipe has been ended.
    ) after execution of system call 'ReadFile' with parameter ((read end of child process output pipe)), line (403) in file (synxcpipe.cpp).
    WARNING    2011-02-23 19:56:12.607
               CJSlibModule::writeWarning_impl()
    Execution of the command ""C:\Program Files\sapinst_instdir\NW71\INSTALL\SYSTEM\ORA\STD\AS\sapjvm\sapjvm_5\bin\java.exe" -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
    java version "1.5.0_14"
    Java(TM) 2 Runtime Environment, Standard Edition (build 5.1.024)
    SAP Java 64-Bit Server VM (build 5.1.024, Sep  4 2008 23:21:58 - 51_REL - optU - windows amd64 - bas2:106386 (mixed mode))
    Import Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29.
    Loading of 'SAPNTAB' import package: ERROR
    Import Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29.
    TRACE      2011-02-23 19:56:12.607
    Function setMessageIdOfExceptionMessage: nw.programError
    ERROR      2011-02-23 19:56:12.607
               CJSlibModule::writeError_impl()
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    import_monitor.log
    TRACE: 2011-02-23 19:55:42 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\NW71\INSTALL\SYSTEM\ORA\STD\AS\DDLORA.TPL' template file is started.
    INFO: 2011-02-23 19:55:42 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\NW71\INSTALL\SYSTEM\ORA\STD\AS\DDLORA.TPL' template file is successfully completed.
    Primary key creation: after load.
    Index creation: after load.
    INFO: 2011-02-23 19:55:42
    Data codepage 1100 is determined using TOC file 'E:\SAPCD\51036706\DATA_UNITS\EXP1\DATA\REPOSRC.TOC' for package 'REPOSRC'.
    INFO: 2011-02-23 19:55:42
    Version table 'SVERS' is found in STR file 'E:\SAPCD\51036706\DATA_UNITS\EXP3\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
    INFO: 2011-02-23 19:55:42
    Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\SAPCD\51036706\DATA_UNITS\EXP3\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
    TRACE: 2011-02-23 19:55:42 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPNTAB' import package is started.
    TRACE: 2011-02-23 19:55:42 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPNTAB' import package into database:
    E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -stop_on_error -loadprocedure fast
    ERROR: 2011-02-23 19:55:45 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPNTAB' import package is interrupted with R3load error.
    Process 'E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -stop_on_error -loadprocedure fast' exited with return code -1,073,741,819.
    For mode details see 'SAPNTAB.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
    WARNING: 2011-02-23 19:56:12
    Cannot continue import because not all import packages with data conversion tables are loaded successfully.
    WARNING: 2011-02-23 19:56:12
    1 error(s) during processing of packages.
    INFO: 2011-02-23 19:56:12
    Import Monitor is stopped.
    Edited by: Raoul Shiro on Feb 23, 2011 8:11 PM
    Edited by: Raoul Shiro on Feb 23, 2011 8:12 PM

    Hello,
    Thank you for your answer.
    I already opened a sap cutomer call, they answered that it it not a database issue,
    I restarted the installationfriom scracth , but i still got the same error :
    Here is the full content of the file SAPNTAB.log
    E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110225170643
    E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/711_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
    E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: version R7.11/V1.4 [UNICODE]
    Compiled Dec 22 2008 00:13:12
    E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe -ctf I E:\SAPCD\51036706\DATA_UNITS\EXP3\DATA\SAPNTAB.STR C:\Program Files\sapinst_instdir\NW71\INSTALL\SYSTEM\ORA\STD\AS\DDLORA.TPL SAPNTAB.TSK ORA -l SAPNTAB.log
    E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: job completed
    E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20110225170643
    E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110225170643
    E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/711_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
    E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe: version R7.11/V1.4 [UNICODE]
    Compiled Dec 22 2008 00:13:12
    E:\usr\sap\PIQ\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -stop_on_error -loadprocedure fast
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (DB) INFO: SVERS created #20110225170643
    Regards.
    Raoul

  • Loading of 'SEOCOMPODF' import package is interrupted with R3load error.

    Dear SAP Colleagues,
    Please advice with the following, we try to install SAP ERP  6.0 support release 3 on windows 2008 server with oracle database 10g 10.2.0.4.0,
    The error is occurred in Import ABAP phase as follow,
    ERROR 2010-10-14 12:10:00.729
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    Hint : I already applied this scenario of installation in two other server with same hardware and sap software and itu2019s already up and running,
    From my side I applied the following but nothing is changed, 
    u2022     Applied sap Note 709389
    u2022     Replaced the sap source more times,
    u2022     Maintained the paging file,
    u2022     Restart the sap server
    u2022     Restart the installation from scratch
    Also I can see that the oracle service and listener is started automatically
    I checked the log files mentioned above as follow,
    Contents in log file u201Cimport_monitor.javau201D
    java version "1.4.2_17"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)
    Java HotSpot(TM) Client VM (build 1.4.2_17-b06, mixed mode)
    Import Monitor jobs: running 1, waiting 4, completed 23, failed 0, total 28.
    Import Monitor jobs: running 2, waiting 3, completed 23, failed 0, total 28.
    Import Monitor jobs: running 3, waiting 2, completed 23, failed 0, total 28.
    Loading of 'SEOCOMPODF' import package: ERROR
    Loading of 'DD03L' import package: ERROR
    Import Monitor jobs: running 0, waiting 2, completed 23, failed 3, total 28.
    Loading of 'FUPARAREF' import package: ERROR
    Import Monitor jobs: running 0, waiting 2, completed 23, failed 3, total 28.
    Import Monitor jobs: running 0, waiting 2, completed 23, failed 3, total 28.
    Import Monitor jobs: running 1, waiting 1, completed 23, failed 3, total 28.
    Loading of 'TODIR' import package: ERROR
    Import Monitor jobs: running 0, waiting 1, completed 23, failed 4, total 28.
    Contents in log file u201Cimport_monitoru201D
    ERROR: 2010-10-14 12:09:04 com.sap.inst.migmon.LoadTask run
    Loading of 'SEOCOMPODF' import package is interrupted with R3load error.
    Process 'D:\usr\sap\ECP\SYS\exe\uc\NTAMD64\R3load.exe -i SEOCOMPODF.cmd -dbcodepage 4103 -l SEOCOMPODF.log -stop_on_error' exited with return code 2.
    For mode details see 'SEOCOMPODF.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
    ERROR: 2010-10-14 12:09:04 com.sap.inst.migmon.LoadTask run
    Loading of 'DD03L' import package is interrupted with R3load error.
    Process 'D:\usr\sap\ECP\SYS\exe\uc\NTAMD64\R3load.exe -i DD03L.cmd -dbcodepage 4103 -l DD03L.log -stop_on_error' exited with return code 2.
    For mode details see 'DD03L.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
    ERROR: 2010-10-14 12:09:04 com.sap.inst.migmon.LoadTask run
    Loading of 'FUPARAREF' import package is interrupted with R3load error.
    Process 'D:\usr\sap\ECP\SYS\exe\uc\NTAMD64\R3load.exe -i FUPARAREF.cmd -dbcodepage 4103 -l FUPARAREF.log -stop_on_error' exited with return code 2.
    For mode details see 'FUPARAREF.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
    TRACE: 2010-10-14 12:09:30 com.sap.inst.migmon.LoadTask run
    Loading of 'TODIR' import package is started.
    TRACE: 2010-10-14 12:09:30 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'TODIR' import package into database:
    D:\usr\sap\ECP\SYS\exe\uc\NTAMD64\R3load.exe -i TODIR.cmd -dbcodepage 4103 -l TODIR.log -stop_on_error
    ERROR: 2010-10-14 12:09:30 com.sap.inst.migmon.LoadTask run
    Loading of 'TODIR' import package is interrupted with R3load error.
    Process 'D:\usr\sap\ECP\SYS\exe\uc\NTAMD64\R3load.exe -i TODIR.cmd -dbcodepage 4103 -l TODIR.log -stop_on_error' exited with return code 2.
    For mode details see 'TODIR.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
    WARNING: 2010-10-14 12:10:00
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2010-10-14 12:10:00
    4 error(s) during processing of packages.
    INFO: 2010-10-14 12:10:00
    Import Monitor is stopped.
    Regards,
    Ahmed Saber

    Hi Gagan Deep Kaushal,
    The todir.log file it was so big so I backup it run the installation again to regenerate the log file, please find below the log file you requested,
    D:\usr\sap\ECP\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20101014135456
    D:\usr\sap\ECP\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
    D:\usr\sap\ECP\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Jan 24 2008 01:41:44
    D:\usr\sap\ECP\SYS\exe\uc\NTAMD64\R3load.exe -i TODIR.cmd -dbcodepage 4103 -l TODIR.log -stop_on_error
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: db_connect rc = 256
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: DbSlErrorMsg rc = 99
    D:\usr\sap\ECP\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
    D:\usr\sap\ECP\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20101014135457
    Regards,
    Ahmed Saber

  • SAPAPPL0,SAPSSEXC,SAPAPPL2 import package is interrupted with R3load

    Hi SAP Experts,
    I am installing ECC 6.0 SR1 EHP4 with DB29.1 on AIX6.1 but durning Import ABAP , I am getting error
    SAPAPPL2' import package is interrupted with R3load error.
    SAPAPPL0' import package is interrupted with R3load error.
    SAPSSEXC' import package is interrupted with R3load error.
    I am attaching all the logs import_monitor,import_monitor.java, SAPAPPL2,SAPAPPL0,SAPSSEXC
    Kindly help me to come out from this error.
    Import_monitor----
    TRACE: 2010-08-19 22:16:46 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL0' import package into database:
    /usr/sap/LD1/SYS/exe/run/R3load -i SAPAPPL0.cmd -dbcodepage 4102 -l SAPAPPL0.log -stop_on_error -loadprocedure fast LOAD
    ERROR: 2010-08-19 22:16:47 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2' import package is interrupted with R3load error.
    Process '/usr/sap/LD1/SYS/exe/run/R3load -i SAPAPPL2.cmd -dbcodepage 4102 -l SAPAPPL2.log -stop_on_error -loadprocedure fast LOAD' exited with return code 2.
    For mode details see 'SAPAPPL2.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
    ERROR: 2010-08-19 22:16:47 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is interrupted with R3load error.
    Process '/usr/sap/LD1/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4102 -l SAPSSEXC.log -stop_on_error -loadprocedure fast LOAD' exited with return code 2.
    For mode details see 'SAPSSEXC.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
    ERROR: 2010-08-19 22:18:00 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is interrupted with R3load error.
    Process '/usr/sap/LD1/SYS/exe/run/R3load -i SAPAPPL0.cmd -dbcodepage 4102 -l SAPAPPL0.log -stop_on_error -loadprocedure fast LOAD' exited with return code 2.
    For mode details see 'SAPAPPL0.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
    WARNING: 2010-08-19 22:18:14
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2010-08-19 22:18:14
    3 error(s) during processing of packages.
    INFO: 2010-08-19 22:18:14
    Import Monitor is stopped.
    SAPAPPL2
    /usr/sap/LD1/SYS/exe/run/R3load: START OF LOG: 20100819221646
    /usr/sap/LD1/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP
    /usr/sap/LD1/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
    Compiled Feb 24 2009 21:54:08
    /usr/sap/LD1/SYS/exe/run/R3load -i SAPAPPL2.cmd -dbcodepage 4102 -l SAPAPPL2.log -stop_on_error -loadprocedure fast LOAD
    (DB) INFO: connected to DB
    (TSK) ERROR: file /tmp/sapinst_instdir/ERPEhP4/AS-ABAP/DB6/CENTRAL/SAPAPPL2.TSK.bck already seems to exist
                 a previous run may not have been finished cleanly
                 file /tmp/sapinst_instdir/ERPEhP4/AS-ABAP/DB6/CENTRAL/SAPAPPL2.TSK possibly corrupted
    /usr/sap/LD1/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/LD1/SYS/exe/run/R3load: END OF LOG: 20100819221647
    SAPAPPL0
    /usr/sap/LD1/SYS/exe/run/R3load: START OF LOG: 20100819221646
    /usr/sap/LD1/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP
    /usr/sap/LD1/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
    Compiled Feb 24 2009 21:54:08
    /usr/sap/LD1/SYS/exe/run/R3load -i SAPAPPL0.cmd -dbcodepage 4102 -l SAPAPPL0.log -stop_on_error -loadprocedure fast LOAD
    (DB) INFO: connected to DB
    (DB) INFO: /1CN/CPTSAP00005 dropped #20100819221758
    (DB) INFO: /1CN/CPTSAP00005 created #20100819221759
    (DB) INFO: /1CN/CPTSAP00005~0 created #20100819221759
    (DB) INFO: /1CN/CPTSAP00005SC created #20100819221759
    (IMP) INFO: import of /1CN/CPTSAP00005 completed (0 rows) #20100819221759
    (DB) ERROR: DDL statement failed
    ( CREATE TABLE "/1CN/CPTSAP00006" ( "CLIENT" SAPDB6FIXCHAR(3) DEFAULT '000' NOT NULL , "VARNUMH" CHAR(16) FOR BIT DATA NOT NULL , "PRT_PARTNER" CHAR(16) FOR BIT DATA NOT NULL , "KSCHL" SAPDB6CHAR(4) DEFAULT ' ' NOT NULL , "OBJECT_ID" CHAR(16) FOR BIT DATA , "TIMESTAMP_TO" SAPDB6CHAR(14) DEFAULT ' ' NOT NULL , "RELEASE_STATUS" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "TIMESTAMP_FROM" SAPDB6CHAR(14) DEFAULT ' ' NOT NULL , "KSCHL_SUPP" SAPDB6CHAR(4) DEFAULT ' ' NOT NULL , "COND_GROUP_ID" CHAR(16) FOR BIT DATA , "MAINT_STATUS" SAPDB6CHAR(2) DEFAULT ' ' NOT NULL , "CREATED_BY" SAPDB6CHAR(12) DEFAULT ' ' NOT NULL , "CREATED_ON" SAPDB6CHAR(8) DEFAULT '00000000' NOT NULL , "KOPOS" SAPDB6FIXCHAR(3) DEFAULT '000' NOT NULL , "SUPP_EXIST" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "SCALE_DIM" SAPDB6FIXCHAR(2) DEFAULT '00' NOT NULL , "KBETR" DECIMAL(15,2) DEFAULT 0 NOT NULL , "KPEIN" DECIMAL(5,0) DEFAULT 0 NOT NULL , "KMEIN" SAPDB6CHAR(3) DEFAULT ' ' NOT NULL , "KONWA" SAPDB6CHAR(5) DEFAULT ' ' NOT NULL , "KRECH" SAPDB6CHAR(3) DEFAULT ' ' NOT NULL  ) IN LD1#STABD INDEX IN LD1#STABI LONG IN LD1#STABD )
    dsql_exec_immediate returned DS_DBOBJECTEXISTS
    (DB) INFO: disconnected from DB
    /usr/sap/LD1/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/LD1/SYS/exe/run/R3load: END OF LOG: 20100819221800
    SAPSSEXC
    /usr/sap/LD1/SYS/exe/run/R3load: START OF LOG: 20100819221646
    /usr/sap/LD1/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP
    /usr/sap/LD1/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
    Compiled Feb 24 2009 21:54:08
    /usr/sap/LD1/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4102 -l SAPSSEXC.log -stop_on_error -loadprocedure fast LOAD
    (DB) INFO: connected to DB
    (DB) INFO: BRATEXT dropped #20100819221647
    (DB) INFO: BRATEXT created #20100819221647
    (DB) INFO: BRATEXT~0 created #20100819221647
    (IMP) INFO: import of BRATEXT completed (0 rows) #20100819221647
    (DB) ERROR: DDL statement failed
    ( CREATE TABLE "D010INC" ( "MASTER" SAPDB6CHAR(40) DEFAULT ' ' NOT NULL , "INCLUDE" SAPDB6CHAR(40) DEFAULT ' ' NOT NULL  ) IN LD1#ES701D INDEX IN LD1#ES701I LONG IN LD1#ES701D )
    dsql_exec_immediate returned DS_DBOBJECTEXISTS
    (DB) INFO: disconnected from DB
    /usr/sap/LD1/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/LD1/SYS/exe/run/R3load: END OF LOG: 20100819221647
    IMPORT_MONITOR.JAVA
    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 AIX ppc64-64 j9ap64142ifx-20100615 (JIT enabled)
    J9VM - 20100610_59470_BHdSMr
    JIT  - 20090210_1447ifx2_r8
    GC   - 200902_24)
    Import Monitor jobs: running 1, waiting 3, completed 24, failed 0, total 28.
    Import Monitor jobs: running 2, waiting 2, completed 24, failed 0, total 28.
    Import Monitor jobs: running 3, waiting 1, completed 24, failed 0, total 28.
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.
    Loading of 'SAPSSEXC' import package: ERROR
    Import Monitor jobs: running 1, waiting 1, completed 24, failed 2, total 28.
    Loading of 'SAPAPPL0' import package: ERROR
    Import Monitor jobs: running 0, waiting 1, completed 24, failed 3, total 28.
    PLEASE HELP ANYONE TO RESOLVE THIS ERROR

    SAPINST.LOG
    INFO 2021-03-23 14:09:35
    Copied file 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/inifile.14.xml'.
    INFO 2021-03-23 14:09:36
    Copied file 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/inifile.15.xml'.
    INFO 2021-03-23 14:09:40
    Execute step
    Component  W2K_ServicePack_Check|ind|ind|ind|ind
    Preprocess  of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
    INFO 2021-03-23 14:10:04
    Copied file 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/keydb.8.xml'.
    INFO 2021-03-23 14:10:04
    Execute step runMigrationMonitor of component |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.
    WARNING 2021-03-23 14:10:11
    Error 5 (Access is denied.) in execution of a 'RegOpenKeyEx' function, line (645), with parameter (S-1-5-21-1712382466-689420201-920741312-1010).
    WARNING 2021-03-23 14:10:11
    Error 5 (Access is denied.) in execution of a 'RegOpenKeyEx' function, line (645), with parameter (ProtectedRoots).
    INFO 2021-03-23 14:10:11
    Switched to user: rasadm.
    INFO 2021-03-23 14:10:11
    Creating file C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\import_monitor.java.log.
    INFO 2021-03-23 14:10:11
    Switched to user: rasadm.
    INFO 2021-03-23 14:10:11
    Working directory changed to C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS.
    INFO 2021-03-23 14:10:11
    Output of C:\j2sdk1.4.2_13\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_1\EXP1;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_2\EXP2;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_3\EXP3;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_4\EXP4;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_5\EXP5;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP6;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP7;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP8;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP9;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP10;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP11" -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe H:\usr\sap\RAS\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst is written to the logfile import_monitor.java.log.
    WARNING 2021-03-23 14:10:43
    Execution of the command "C:\j2sdk1.4.2_13\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_1\EXP1;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_2\EXP2;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_3\EXP3;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_4\EXP4;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_5\EXP5;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP6;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP7;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP8;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP9;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP10;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP11" -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe H:\usr\sap\RAS\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_13"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
    Java HotSpot(TM) Client VM (build 1.4.2_13-b06, mixed mode)
    Import Monitor jobs: running 1, waiting 3, completed 15, failed 0, total 19.
    Import Monitor jobs: running 2, waiting 2, completed 15, failed 0, total 19.
    Import Monitor jobs: running 3, waiting 1, completed 15, failed 0, total 19.
    Loading of 'SAPAPPL0' import package: ERROR
    Loading of 'SAPSSEXC' import package: ERROR
    Import Monitor jobs: running 1, waiting 1, completed 15, failed 2, total 19.
    Import Monitor jobs: running 1, waiting 1, completed 15, failed 2, total 19.
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 0, waiting 1, completed 15, failed 3, total 19.
    ERROR 2021-03-23 14:10:43
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    ERROR 2021-03-23 14:10:43
    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 .
    INFO 2021-03-23 14:10:45
    An error occured and the user decided to retry the current step: "|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".
    INFO 2021-03-23 14:10:46
    Switched to user: rasadm.
    INFO 2021-03-23 14:10:46
    Creating file C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\import_monitor.java.log.
    INFO 2021-03-23 14:10:46
    Switched to user: rasadm.
    INFO 2021-03-23 14:10:46
    Working directory changed to C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS.
    INFO 2021-03-23 14:10:46
    Output of C:\j2sdk1.4.2_13\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_1\EXP1;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_2\EXP2;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_3\EXP3;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_4\EXP4;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_5\EXP5;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP6;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP7;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP8;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP9;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP10;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP11" -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe H:\usr\sap\RAS\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst is written to the logfile import_monitor.java.log.
    WARNING 2021-03-23 14:11:16
    Execution of the command "C:\j2sdk1.4.2_13\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_1\EXP1;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_2\EXP2;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_3\EXP3;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_4\EXP4;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_5\EXP5;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP6;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP7;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP8;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP9;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP10;D:\SAP IDES 60\SAP_ERP60_IDES_Export\51032413_6\EXP11" -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe H:\usr\sap\RAS\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_13"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
    Java HotSpot(TM) Client VM (build 1.4.2_13-b06, mixed mode)
    Import Monitor jobs: running 1, waiting 3, completed 15, failed 0, total 19.
    Import Monitor jobs: running 2, waiting 2, completed 15, failed 0, total 19.
    Import Monitor jobs: running 3, waiting 1, completed 15, failed 0, total 19.
    Loading of 'SAPAPPL0' import package: ERROR
    Import Monitor jobs: running 2, waiting 1, completed 15, failed 1, total 19.
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 1, waiting 1, completed 15, failed 2, total 19.
    Loading of 'SAPSSEXC' import package: ERROR
    Import Monitor jobs: running 0, waiting 1, completed 15, failed 3, total 19.
    ERROR 2021-03-23 14:11:16
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    ERROR 2021-03-23 14:11:16
    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 .

  • Import package error in SAP BPC 4.1

    Hi,
    Can anyone please assist.
    I tried running the import package several times on bpc ver 4.1 without aby success. I even tripple checked Users and Security and it validated successfully but the package still crashes in the middle of processing.
    The error message read:
    [Package Result = Error]
    Package:                    Import
    Appset:                       CQS
    Application:                 FIXEDCOST
    Request Time:             2009-06-23 13:44:42
    Start   Time:                2009-06-23 13:44:42
    End     Time:               2009-06-23 13:48:51
    Total   Time:                00:04:09
    TOTAL STEPS  3
    1. Assign initial parameters:        completed  in 0 sec.
    2. Convert data:                     completed  in 7 sec.
    3. Load and process:                 Failed  in 241 sec.
    [Selection]
    FILE= DATAMANAGER\DATAFILES\CQSSA\2009\Fixed Costs Testnew.txt
    TRANSFORMATION= DATAMANAGER\TRANSFORMATIONFILES\CQSSA\FC_Trans_ZA_ACT.xls
    CLEARDATA= Yes
    RUNLOGIC= No
    [Member Selection]
    CATEGORY: ACTUAL
    ENTITY: SQSSA
    TIME: 2009.MAY
    [The list of conversion file in each transformation file]
    Transformation file: DATAMANAGER\TRANSFORMATIONFILES\CQSSA\FC_Trans_ZA_ACT.xls
         - Conversion file : ConversionFiles\CQSSA\FC_CONV_ZA.XLS!FCOSTACCOUNT
         - Conversion file : ConversionFiles\CQSSA\FC_CONV_ZA.XLS!FCOSTCENTRE
         - Conversion file : ConversionFiles\CQSSA\FC_CONV_ZA.XLS!MARKETS
    [Messages]
    FIXEDCOST
    Failed
    Submit Count  : 15278 (Record count in source file  : 20056)
    Accept Count : 0
    Reject Count : 15278
    You do not have WRITE authority.::ACTUAL
    Where can I enable WRITE authority?

    Hi Vishal Mahawadhi,
    Thank you for replying. I've tried all your suggestions before I even logged the query. I even went to analysis manager, gave access to the application and processed the cube but still that didn't help.
    But I noticed that I only have read access when I look at the settings on the roles in analysis manager. The problem is that I can't change the settings to read/write. Version 4.1 is a mess.

  • Re-importing packages during installation

    Hello all,
    Was doing an installation.When it started, got the following errors:
    Import Monitor jobs: running 1, waiting 110, completed 1, failed 0, total 112.
    Import Monitor jobs: running 2, waiting 109, completed 1, failed 0, total 112.
    Import Monitor jobs: running 3, waiting 108, completed 1, failed 0, total 112.
    Loading of 'DOKCLU' import package: ERROR
    Import Monitor jobs: running 1, waiting 108, completed 1, failed 2, total 112.
    Loading of 'PCL4' import package: ERROR
    Import Monitor jobs: running 1, waiting 108, completed 1, failed 2, total 112.
    Loading of 'REPOSRC' import package: ERROR
    Import Monitor jobs: running 0, waiting 108, completed 1, failed 3, total 112.
    This seems to have failed on the first 3 packages: DOKCLU, PCL4 and REPOSRC. These were the first 3 packages that were to be imported. After that, all was fine. As of now, the last line in the import_monitor.java.log file is:
    Loading of 'SAPDFACT' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 108, failed 3, total 112.
    So, 108 have been completed with no issue.
    Only the first 3 failed.
    How can one re-import these packages again.
    TIA

    Hello again,
    When looking at the TSK files, it seems to specify that the files associated with several packages loaded OK.
    15 Jul  1 10:01 REPOSRC.TSK
    38 Jul  1 10:34 PCL2.TSK
    28 Jul  1 10:43 DOKCLU.TSK
    Example, for PCL2.TSK, got the following:
    T PCL2 C ok
    D PCL2 I ok
    P PCL2~0 C ok
    For DOKCLU.TSK, got the following:
    T DOKCLU C ok
    D DOKCLU I ok
    and for REPOSRC.TSK, got the following:
    T REPOSRC C ok
    saw the following *.bck files
    DDLORA.TPL.bck     
    DOKCLU.TSK.bck 
    REPOSRC.TSK.bck
    DDLORA_LRG.TPL.bck 
    PCL4.TSK.bck
    Edited by: Casey Harris on Jul 2, 2009 9:54 AM

  • Import job failes with ORA-01403: no data found ORA-06512: at "SYSMAN.MGMT

    Hello everyone,
    I need a help on importing data from a schema in server 1 to the same schema in server 2 via network link. I receive following error when I try to submit a job on Enterprise Manager:
    Import Submit Failed
    ORA-01403: no data found ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 5806 ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 7812 ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 8608 ORA-01403: no data found ORA-06512: at "SYSMAN.MGMT_JOBS", line 273 ORA-06512: at "SYSMAN.MGMT_JOBS", line 86 ORA-06512: at line 1
    Sql of the job:
    declare
    h1 NUMBER;
    begin
    h1 := dbms_datapump.open (operation => 'IMPORT', job_mode => 'FULL', remote_link => 'B_PROD_LINK', job_name => 'BIMPORTFRMPRDTORPT4', version => 'COMPATIBLE');
    dbms_datapump.set_parallel(handle => h1, degree => 1);
    dbms_datapump.add_file(handle => h1, filename => 'IMPORT.LOG', directory => 'DATA_PUMP_DIR', filetype => 3);
    dbms_datapump.set_parameter(handle => h1, name => 'KEEP_MASTER', value => 0);
    dbms_datapump.set_parameter(handle => h1, name => 'INCLUDE_METADATA', value => 1);
    dbms_datapump.set_parameter(handle => h1, name => 'ESTIMATE', value => 'BLOCKS');
    dbms_datapump.set_parameter(handle => h1, name => 'REUSE_DATAFILES', value => 0);
    dbms_datapump.set_parameter(handle => h1, name => 'TABLE_EXISTS_ACTION', value => 'TRUNCATE');
    dbms_datapump.set_parameter(handle => h1, name => 'SKIP_UNUSABLE_INDEXES', value => 0);
    dbms_datapump.start_job(handle => h1, skip_current => 0, abort_step => 0);
    dbms_datapump.detach(handle => h1);
    end;
    It says network link is active when I test the network link to make sure its connectivity. I create the network link as a system account. I'm trying to do an import from an Oracle database 10.2.0.2 to 11.2.0.1. My 10g database is on ms windows 2003x64 while my 11g database is on OEL 5.4x64.
    What should I do for now?
    Thank you.
    Edited by: user12144220 on Nov 4, 2012 5:02 AM

    It will be wise to run the Oracle supply streams health check script to check your existing streams environment.
    From the result, you can also open a tar with Oracle to see if they can help you with the setup.
    In addition to the ORA-01403 error, you can also run some of the Oracle Streams packages (Managing Apply Errors) to see the full detail of what is missing that caused the Ora-01403 error.
    I will also try to implement a smoke test using the simple heartbeat table suggested by Oracle Streams, if that is working, then you can begin your full scale setup in your environment knowing that the base Streams Structure is setup correctly.
    HTH

  • Loading of 'SAPSSEXC' import package: ERROR

    Hi All
    I am installing Solution Manager 7.0
    but it prompt error when import ABAP ......
    Loading of 'SAPSSEXC' import package: ERROR
    Edited by: Kevin Wong on Jun 19, 2009 9:53 AM

    Log of 'SAPSSEXC'
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20090618160337
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Jan 24 2008 01:41:39
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe -ctf I F:\software\sap\51033518_2\EXP4\DATA\SAPSLEXC.STR C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL SAPSLEXC.TSK ORA -l SAPSLEXC.log
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: job completed
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090618160337
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20090618160337
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Jan 24 2008 01:41:39
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: db_connect rc = 256
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: DbSlErrorMsg rc = 99
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090618160338
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20090619095804
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Jan 24 2008 01:41:39
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: db_connect rc = 256
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: DbSlErrorMsg rc = 99
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090619095805
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20090619153522
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Jan 24 2008 01:41:39
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    (DB) ERROR: db_connect rc = 256
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    (DB) ERROR: DbSlErrorMsg rc = 99
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    F:\usr\sap\PAS\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090619153527
    Edited by: Kevin Wong on Jun 19, 2009 9:54 AM

  • Argument Order Reversed Importing Package into OWB

    I'm having a problem importing Packages into OWB. It recognizes the Functions contained in the Package, however the order of the arguments for each Function are reversed after I complete the import into OWB. This causes execution of the mapping to fail... Additionally, after importing into OWB, OWB doesn't seem to recognize any optional parameters or default values in the signature of the Function. I must be doing something wrong... Can anyone help...
    Thanks
    Alan

    Hi
    Standard approach to be followed for any object modification
    1. If you have created your package from OWB and deployed it into your DB, always do it that way i.e. Design center -->DB . Do not make any modifications on DB level and import in back to your Design center. OWB manages Ids for all objects on the repository and this will confuse it. That is why you see two versions of the same package . Any modifications should be done on Design center level and then do a replace on the package from control center
    2. If an object (package or procedure) is created on DB directly and is imported into design center, follow the same norm everytime you make any changes to that object. The status of that object will appear as "New" or "Not deployed" on control center but that is fine because OWB has no ID on its repository to maintain this information.
    3. If you need to rename any object already deployed from OWB, always drop it first, then rename it and then deploy it. That way OWB will maintain the name and ID on its end and not get confused.
    4. For your case, you can drop the older version of the package from OWB, delete the one imported from Database into OWB, make the changes on OWB level (adding parameter etc) and then redeploy the same package as replace from control center.
    Hope these tips help
    birdy

  • The package failed to load due to error 0xC0011008

    I am trying to run a SSIS Package from SQL Server BI Studio. I receive the error "The package failed to load due to error 0xC0011008".  SQL Server 2008 R2 installed (32bit Win 7), along with Integration Services.  The Package connects
    to a SQL Server DB.
    Here is the full error taken from consol in BI Studio:
    SSIS package "CreateDynSSIS_DB_RunDynSSiSDB.dtsx" starting.
    Error: 0x1 at ST_Gen_Pkg_Src_SqlServ: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.SqlServer.Dts.Runtime.DtsRuntimeException: The package failed to load due to error 0xC0011008
    "Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored.". This occurs when CPackage::LoadFromXML fails.
     ---> System.Runtime.InteropServices.COMException (0xC0011008): The package failed to load due to error 0xC0011008 "Error loading from XML. No further detailed error information can be specified for this problem because no Events object was
    passed where detailed error information can be stored.". This occurs when CPackage::LoadFromXML fails.
       at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.LoadPackage(String FileName, Boolean loadNeutral, IDTSEvents100 pEvents)
       at Microsoft.SqlServer.Dts.Runtime.Application.LoadPackage(String fileName, IDTSEvents events, Boolean loadNeutral)
       --- End of inner exception stack trace ---
       at ST_0f39f89613ca43e9a6660953aa72fa2c.csproj.ScriptMain.Main()
       --- End of inner exception stack trace ---
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig,       MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
       at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args, CultureInfo culture)
       at Microsoft.SqlServer.Dts.Tasks.ScriptTask.VSTATaskScriptingEngine.ExecuteScript()
    Task failed: ST_Gen_Pkg_Src_SqlServ
    Warning: 0x80019002 at CreateDynSSIS_DB_RunDynSSiSDB: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED.  The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the
    number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
    SSIS package "CreateDynSSIS_DB_RunDynSSiSDB.dtsx" finished: Failure.
    The error is thrown at this line:
    DynamicPackage = app.LoadPackage(DynamicPackagePath, null);
    Any help would be great! I've done a bit of Googling on the topic already.. and nothing has worked so far.

    Hi,
    Reason for the error: Old
    version of the DTEXEC is picked up by SQL Server instead of the new one. 
    Refer this link for more info
    THE PACKAGE FAILED TO LOAD DUE TO ERROR 0XC0011008
    Hope this info Helps

  • Error while running import package

    Hi,
    Transformation file was validated successfully. But after running import package i am having following error on MS-BPC-7.0.
    Invalid character in the given encoding. Line 1, position 1.
    When i try validate and process trans file i am having the following error message. But same data file and same trans file was working till couple of days ago. After that whatever changes i have made to file, i did revert them to have it working like beofre.
    Warning: Some records were rejected.
    Rejected records reference either calculated members or invalid members.
    Actually rejected record is only, one, but even other data was not loaded.
    Thanks in advance for sharing your ideas or similar experiences.
    Thanks,
    KK

    Hi,
    There is definitely some problem with one of the records there. Do you have header? What is the delimiter? Do you have the same delimiter in the transformation file? You need to take a look at all the possibilities.
    Hope this helps.

  • SSIS Package Fails when Scheduled as a SQL Server Agent Job

    I have an SSIS package that runs without any problems when executed through BIDS.
    However, when I schedule the SSIS as an Agent job, it fails completely or part way through. When it partially runs, the part that it is failing on is a Script Task that moves the source data file to an archive folder (on the same server).
    I have tried using my domain account as the owner of the job, then the job fails straight off and I get an error:
    Unable to determine if the owner (Domain\MyID) of job JobName has server access (reason: Could not obtain information about Windows NT group/user 'Domain\MyID'
    If I change the owner to the 'sa' account , then the job partially runs, but then fails because 'sa' is a SQL account and does not have access to the filesystem.
    I have managed to get it to work by using the SQL2008_Local account and granting modify permissions to the affected folders.
    My question is - what is the advised way of doing this?
    Thanks
    Gary

    Hi Garyv.King,
    When you see a SSIS package fails running in a SQL Agent job, you need to first consider the following conditions:
    1. The user account that is used to run the package under SQL Server Agent differs from the original package author.
    2. The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
    For more detailed information about the issue, please following this KB article:
    An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step
    http://support.microsoft.com/kb/918760 
    You can check SQL Server Agent’s activity logs, Windows Event logs and SSIS logs to get more clues. Also the tool Process Monitor is helpful to track the cause of registry or file access related issues.
    The following 4 issues are common encountered in the SSIS forum.
    1. The package's Protection Level is set to EncryptSensitiveWithUserKey but your SQL Server Agent service account is different from the SSIS package creator.
    2. Data source connection issue.
    3. File or registry access permission issue.
    4. No 64-bit driver issue.
    For more information about it, please see:
    How do I troubleshoot SSIS packages failed execution in a SQL Agent job:
    http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/e13c137c-1535-4475-8c2f-c7e6e7d125fc 
    Thanks,
    Eileen

  • SSIS package fails because of excel connection manager when deploying package from development to production

    Hello,
    When I move the package from development to production package fails due to excel connection manager.
    Error message---
    Message
    Executed as user: Answers\Administrator. ...lt: 0x80040154  Description: "Class not registered".  End Error  Error: 2014-06-27 05:10:26.50     Code: 0xC0202009     Source: CPRO_Prod_to_XLS_Worksheet_Basic_EX
    Connection manager "Excel Connection Manager"     Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040154.  An OLE DB record is available.  Source: "Microsoft OLE
    DB Service Components"  Hresult: 0x80040154  Description: "Class not registered".  End Error  Error: 2014-06-27 05:10:26.50     Code: 0xC0202009     Source: CPRO_Prod_to_XLS_Worksheet_Basic_EX
    Connection manager "Excel Connection Manager"     Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040154.  An OLE DB record is available.  Source: "Microsoft OLE
    DB Service Components"  Hresult: 0x80040154  Description: "Class not registered".  End Error  Error: 2014-06-27 05:10:26.50     Code: 0xC0202009     Source...  The package execution
    fa...  The step failed.
    Any help would be appreciated.

    Hi Vinay,
    As Visakh mentioned, the issue usually occurs because the package runs in 64-bit runtime, however, the Excel driver is 32-bit. According to your another thread, it seems that you use SSIS 2005, right? In SSIS 2005, there is no “use 32 bit runtime” option
    for the package executions of a SSIS package job step. In this condition, you have two choices:
    Install the 64-bit Microsoft ACE OLE DB 12.0 Provider on the production server. Here is the download link (AccessDatabaseEngine_x64.exe):
    http://www.microsoft.com/en-in/download/details.aspx?id=13255 
    Create a CmdExec type job step instead of SSIS Package job step, so that we can call 32-bit DTExec.exe to execute the package within command line. For more information, please see:
    http://support.microsoft.com/kb/934653/en-us 
    Regards,
    Mike Yin
    TechNet Community Support

Maybe you are looking for