Error in export phase of a PI system copy

Hi,
In a PI (netweaver 04s) system copy, I was faced with an error message in log, where retry is not possible, as shown bellow:
Caught exception while getting information about SDAs and SCAs Throwable: com.sap.sdm.util.sduread.IllFormattedSduManifestException Throwable message: The information about the software component found in the manifest is either missing or incomplete!
Manifest attributes are missing or have badly formatted value:
the location defined in the component element does not fit to the location attribute
Does anybody know about this issue ?
Regards,
Roque.

Hi guys,
Thanks for you replies.
I am sorry about delay in my response.
As I could see my problem is exactly Sekhar pointed situation.
I am seeking wrong modules on sdm log in order to correct them and try this solution.
I will note here if I am succeeded.
Regards,
Roque.

Similar Messages

Error during export of ECC 6.0 system for unicode conversion

We have upgraded a 4.7 system to ECC 6.0 running on MSSQL 2000. We have the latest r3load, and are using the Netweaver 7.0 sapinst to perform the system copy (export) to convert to unicode. Our goal is an exported system which we can use on a clean install once we have de-installed SAP and SQL 2000 and installed MSSQL 2005.
When running the export, the r3szchk finishes and then the next phase runs. But it gets almost all errors (so we are stopping the export).
The export_monitor.log is shown below, and also an example of one of the table logs shown here as well. but its almost as if every table hits the same problem, BSIS, MSEG, EDIDS etc.....
If you look at the ACCTIT.log, it looks like the SQL/stored preocedure error is as follows, but not sure what this means:
check NameTab width SQL DbSlRead on DDNTT_CONV_UC failed for table T002 with rc 24
Export_Monitor.log
==============
NFO: 2008-08-25 17:30:11
Export Monitor is started.
CONFIG: 2008-08-25 17:30:11
Application options:
dataCodepage=4103
dbType=MSS
exportDirs=S:\ABAP
installDir=C:\Program Files\sapinst_instdir\NW04S\LM\COPY\MSS\EXP\CENTRAL\AS\EXP
jobNum=3
loadArgs=-stop_on_error
monitorTimeout=30
orderBy=
r3loadExe=D:\usr\sap\ED0\SYS\exe\run\R3load.exe
sapinst=
server=
trace=all
tskFiles=yes
CONFIG: 2008-08-25 17:30:11
List of packages with table structure: 'SAP0000'.
CONFIG: 2008-08-25 17:30:11
List of packages with views: 'SAPVIEW'.
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask run
Unloading of 'ACCTIT' export package is started.
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask run
Unloading of 'BSIS' export package is started.
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'ACCTIT' export package:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -ctf E S:\ABAP\DATA\ACCTIT.STR S:\ABAP\DB\DDLMSS.TPL ACCTIT.TSK MSS -l ACCTIT.log
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask run
Unloading of 'CMFP' export package is started.
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'BSIS' export package:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -ctf E S:\ABAP\DATA\BSIS.STR S:\ABAP\DB\DDLMSS.TPL BSIS.TSK MSS -l BSIS.log
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'CMFP' export package:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -ctf E S:\ABAP\DATA\CMFP.STR S:\ABAP\DB\DDLMSS.TPL CMFP.TSK MSS -l CMFP.log
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Unloading of 'ACCTIT' export package from database:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e ACCTIT.cmd -datacodepage 4103 -l ACCTIT.log -stop_on_error
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Unloading of 'CMFP' export package from database:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e CMFP.cmd -datacodepage 4103 -l CMFP.log -stop_on_error
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Unloading of 'BSIS' export package from database:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e BSIS.cmd -datacodepage 4103 -l BSIS.log -stop_on_error
ERROR: 2008-08-25 17:30:12 com.sap.inst.migmon.LoadTask run
Unloading of 'ACCTIT' export package is interrupted with R3load error.
Process 'D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e ACCTIT.cmd -datacodepage 4103 -l ACCTIT.log -stop_on_error' exited with return code 2.
For mode details see 'ACCTIT.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: 2008-08-25 17:30:12 com.sap.inst.migmon.LoadTask run
Unloading of 'CMFP' export package is interrupted with R3load error.
Process 'D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e CMFP.cmd -datacodepage 4103 -l CMFP.log -stop_on_error' exited with return code 2.
For mode details see 'CMFP.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: 2008-08-25 17:30:12 com.sap.inst.migmon.LoadTask run
Unloading of 'BSIS' export package is interrupted with R3load error.
Process 'D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e BSIS.cmd -datacodepage 4103 -l BSIS.log -stop_on_error' exited with return code 2.
For mode details see 'BSIS.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
etc.....
ACCTIT.log
=========
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: START OF LOG: 20080825191346
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#18 $ SAP
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: version R7.00/V1.4
Compiled Aug 18 2008 23:55:23
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -ctf E S:\ABAP\DATA\ACCTIT.STR S:\ABAP\DB\DDLMSS.TPL ACCTIT.TSK MSS -l ACCTIT.log
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: job completed
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: END OF LOG: 20080825191346
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: START OF LOG: 20080825191347
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#18 $ SAP
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: version R7.00/V1.4
Compiled Aug 18 2008 23:55:23
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e ACCTIT.cmd -datacodepage 4103 -l ACCTIT.log -stop_on_error
(DB) INFO: connected to DB
(EXP) WARN: check NameTab width SQL DbSlRead on DDNTT_CONV_UC failed for table T002 with rc 24.
(DB) ERROR: DbSlErrorMsg rc = 99
(EXP) WARN: check NameTab width SQL DbSlRead on DDNTT_CONV_UC failed for table CDPOS with rc 24.
(DB) ERROR: DbSlErrorMsg rc = 99
(EXP) WARN: check NameTab width SQL DbSlRead on DDNTT_CONV_UC failed for table TACOB with rc 24.
(DB) ERROR: DbSlErrorMsg rc = 99
(EXP) INFO: check NameTab widths: Ok.
(DB) INFO: Export without hintfile
(RSCP) INFO: UMGCOMCHAR read check, skip: no data found; probably old SPUMG.
(RSCP) INFO: environment variable "I18N_POOL_WIDTH" is not set. Checks are active.
(RSCP) WARN: UMGCONTAINER has 9 more problems.
(RSCP) WARN: UMGSETTINGS nametab creation: status not available, no table entry.
(RSCP) INFO: Global fallback code page = 0000
(RSCP) INFO: Common character set is 7-bit-ASCII
(RSCP) INFO: Collision resolution method is unexpected !
(RSCP) INFO: R3trans code pages = AskSPUMG
(RSCP) INFO: EXPORT TO ... code pages = AskSPUMG
(RSCP) INFO: Check for invalid language keys: active, by default
(RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 0
(RSCP) INFO: I18N_NAMETAB_ALT_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 0
(RSCP) INFO: I18N_NAMETAB_OLD_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 0
(GSI) INFO: dbname   = "ED0ecc6dev                                                                                "
(GSI) INFO: vname    = "MSSQL                           "
(GSI) INFO: hostname = "ECC6DEV                                                         "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "ECC6DEV"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 2"
(GSI) INFO: machine = "8x AMD64 Level 6 (Mod 23 Step 6)"
(BEK) ERROR: SAPSYSTEMNAME not in environment
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: END OF LOG: 20080825191348

> We will quickly implement the UC as a separate project, not put it off forever.
VERY good decision!
> But as we have single code page, no JAVA integration, no web integration (SOA) etc... the added complexity on our already short timeframe is more than we care to take on at this point.
Happy upgrading!
Our upgrade from 4.7 to ERP 6.0 was one of the smoothest I've made.
Markus

Error in Export of ABAP+JAVA Distributed system

Hi
I am exporting an ABAP(ECC 6.0)+JAVA Add-in system .
I have started the database instance export from the database instance host .
I am geting the following error :
An error occurred while processing service SAP ERP 6.0 Support Release 3 > Software Life-Cycle Options > System Copy > MS SQL Server > Source System Export > Distributed System > Based on AS ABAP and AS Java > Database Instance Export( Last error reported by the step :uncaught exception: nw.usageTypes.utlError: Execution of UTL tool 'D:\j2sdk1.4.2_13-x64\bin\java.exe -classpath D:\usr\sap\ERS\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
sdsapdbsbx1/sapmnt/ERS/SYS/global/security/lib/tools;D:/usr/sap/ERS/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;D:/usr/sap/ERS/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;D:/usr/sap/ERS/SYS/global/sltools/sharedlib/antlr.jar;D:/usr/sap/ERS/SYS/global/sltools/sharedlib/exception.jar;D:/usr/sap/ERS/SYS/global/sltools/sharedlib/jddi.jar;D:/usr/sap/ERS/SYS/global/sltools/sharedlib/logging.jar;D:/usr/sap/ERS/SYS/global/sltools/sharedlib/offlineconfiguration.jar;D:/usr/sap/ERS/SYS/global/sltools/sharedlib/opensqlsta.jar;D:/usr/sap/ERS/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/ERS/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;D:/usr/sap/ERS/SYS/global/sltools/sharedlib/SDMutil.jar;D:/usr/sap/ERS/SYS/global/sltools/sharedlib/SLUtil.jar;D:/usr/sap/ERS/SYS/exe/nuc/NTAMD64/mssjdbc/sqljdbc.jar -export -type=keydb "-expfile=C:/Program Files/sapinst_instdir/ERP/LM/COPY/MSS/EXP/DISTRIBUTED/AS/EXPDB/usages_data.xml" -log=UTL_load_usages.log -sid=ERS -dsn=jdbc/pool/ERS -ssprops=D:/usr/sap/ERS/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/ERS/SYS/global/security/data/SecStore.key' aborts with return code 1. Check 'UTL_load_usages.log' and 'C:/Program Files/sapinst_instdir/ERP/LM/COPY/MSS/EXP/DISTRIBUTED/AS/EXPDB/UTL.java.log' for more information. (in script unknown, line 0: ???)).
The file UTL.java.log is as follows:
java version "1.4.2_19-rev"
Java(TM) Platform, Standard Edition for Business (build 1.4.2_19-rev-b07)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_19-rev-b07, mixed mode)
java.lang.NoClassDefFoundError: com/sap/engine/offline/OfflineToolStart
Please help.
Regards
Ratnajit

Hi
with 1.4.2_18 and 1.4.2_19 we are currently having massive stack overflow check the below link for more clarifications
X64 java 1.4.2_18 for SAP
Regards
Uday

Error when exporting IDOC from one XI system to another

Hi all,
When I do an export for an IDOC from my one XI server to be able to import it into another I get the error below. The funny thing is that it works perfectly for my COND_A idoc but not at all for DEBMAS and MATMAS idoc.
Any ideas?
<b>Error during export. Internal error during pvc call: SAP DBTech JDBC: Result set is positioned after last row.</b>
Regards,
Liesel

Hey,
I guess you are using MAXDB,
please read note number 1055246
(Inconsistent XI content caused by bug in MAX DB)
Good luck!

Error at step Run ABAP Reports during system copy in HPUX

Hi experts,
During system copy from Prodcution to Development i am facing the following errror at step
Run ABAP Reports
INFO 2009-03-18 03:57:36
Information for application function INST_EXECUTE_REPORT copied to local Repository.
INFO 2009-03-18 03:57:36
Function module INST_EXECUTE_REPORT set successfully.
INFO 2009-03-18 03:57:36
Executing function call INST_EXECUTE_REPORT.
ERROR 2009-03-18 03:57:38
FRF-00025 Unable to call function. Error message: Exception condition "WRITE_FAILED" raised. .
INFO 2009-03-18 03:57:38
RFC connection closed.
ERROR 2009-03-18 03:57:38
MUT-03025 Caught ERfcExcept in Modulecall: Exception condition "WRITE_FAILED" raised..
ERROR 2009-03-18 03:57:38
FCO-00011 The step runRADDBDIF with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|runRADDBDIF was executed with status ERROR .
Please let me know the solution
Thanks & Regards,
Arun

This seems to be related with permission to write in /usr/sap/trans
Read,
Re: Run ABAP Reports error during ECC 6.0 installation on Win2003 with Oracle
Exception condition "WRITE_FAILED" raised during installation 4.0
and
Install error at Phase 33
Regards
Juan

Facing issue during the export of the oracle system_ system copy

Dear All,
    We are exporting the R3E 47 / oracle database 9.2.0.5.0. I am facing an error in the database export phase.
Dbsl Trace : Error 12535 in stmt_fetch()
Dbsl Trace: ORA-12535 occured when executing SQL statment ( parse error offset=373)
(EXP) ERROR: Dbsl ExeRead failed
    rc = 99, table "ZMT054_STOCKAGE"
   ( SQL error 12535)
error message retunred by Dbsl
ORA-12535:TNS:operation timed out
(DB) INFO : disconnected from DB
I have changed parameter CONNECT_TIMEOUT as per note 34479 to Value 0 restarted listener services and SAP as well. After restarting the export i am facing the same error.
Kindly suggest me pls
Regards
Raj

Hi Juan,
      Thanks for the info link. I have changed the paramater with higher value and skipped the table , then the export went fine.
Thanks again.
Raj

Error in import abap step while importing system copy.

Hi All,
My colleague had taken System copy of development server, few days back. it was completed successfully,
now we want to restore that system copy, as hardware failed. But when we start the import of system copy,
all ABAP jobs are failing in import abap step, Some DDL statement problem. can u pls help wht to do.
I found in some forums, SMIGR_create_DDL report need to be generated prior to taking system copy, but he
didnt taken tht.
OS: Windows 2003
DB: DB2
Pls find sapinst.log
INFO 2009-10-27 10:43:06.890
Output of C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING 2009-10-27 10:53:37.125
Execution of the command "C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -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) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)
Import Monitor jobs: running 1, waiting 63, completed 0, failed 0, total 64.
Import Monitor jobs: running 2, waiting 62, completed 0, failed 0, total 64.
Import Monitor jobs: running 3, waiting 61, completed 0, failed 0, total 64.
Loading of 'DOKCLU' import package: ERROR
Import Monitor jobs: running 2, waiting 61, completed 0, failed 1, total 64.
Loading of 'D010TAB' import package: ERROR
Import Monitor jobs: running 1, waiting 61, completed 0, failed 2, total 64.
Loading of 'REPOSRC' import package: ERROR
Import Monitor jobs: running 0, waiting 61, completed 0, failed 3, total 64.
Import Monitor jobs: running 1, waiting 60, completed 0, failed 3, total 64.
Import Monitor jobs: running 2, waiting 59, completed 0, failed 3, total 64.
Import Monitor jobs: running 3, waiting 58, completed 0, failed 3, total 64.
Loading of 'DYNPSOURCE' import package: ERROR
Import Monitor jobs: running 2, waiting 58, completed 0, failed 4, total 64.
Loading of 'SAPAPPL1_4' import package: ERROR
Import Monitor jobs: running 1, waiting 58, completed 0, failed 5, total 64.
Loading of 'SAPAPPL2_2' import package: ERROR
Import Monitor jobs: running 0, waiting 58, completed 0, failed 6, total 64.
Import Monitor jobs: running 1, waiting 57, completed 0, failed 6, total 64.
Import Monitor jobs: running 2, waiting 56, completed 0, failed 6, total 64.
Import Monitor jobs: running 3, waiting 55, completed 0, failed 6, total 64.
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 2, waiting 55, completed 0, failed 7, total 64.
Loading of 'SAPSSEXC_9' import package: ERROR
Import Monitor jobs: running 1, waiting 55, completed 0, failed 8, total 64.
Loading of 'SAPSSEXC_8' import package: ERROR
Import Monitor jobs: running 0, waiting 55, completed 0, failed 9, total 64.
Import Monitor jobs: running 1, waiting 54, completed 0, failed 9, total 64.
Import Monitor jobs: running 2, waiting 53, completed 0, failed 9, total 64.
Import Monitor jobs: running 3, waiting 52, completed 0, failed 9, total 64.
Loading of 'SAPAPPL2_6' import package: ERROR
Import Monitor jobs: running 2, waiting 52, completed 0, failed 10, total 64.
Loading of 'SAPAPPL1_3' import package: ERROR
Import Monitor jobs: running 1, waiting 52, completed 0, failed 11, total 64.
Loading of 'SAPAPPL2_5' import package: ERROR
Import Monitor jobs: running 0, waiting 52, completed 0, failed 12, total 64.
Import Monitor jobs: running 1, waiting 51, completed 0, failed 12, total 64.
Import Monitor jobs: running 2, waiting 50, completed 0, failed 12, total 64.
Import Monitor jobs: running 3, waiting 49, completed 0, failed 12, total 64.
Loading of 'D010INC' import package: ERROR
Import Monitor jobs: running 2, waiting 49, completed 0, failed 13, total 64.
Loading of 'SAPAPPL1_2' import package: ERROR
Import Monitor jobs: running 1, waiting 49, completed 0, failed 14, total 64.
Loading of 'SAPAPPL1_7' import package: ERROR
Import Monitor jobs: running 0, waiting 49, completed 0, failed 15, total 64.
Import Monitor jobs: running 1, waiting 48, completed 0, failed 15, total 64.
Import Monitor jobs: running 2, waiting 47, completed 0, failed 15, total 64.
Import Monitor jobs: running 3, waiting 46, completed 0, failed 15, total 64.
Loading of 'SAPSSEXC_2' import package: ERROR
Import Monitor jobs: running 2, waiting 46, completed 0, failed 16, total 64.
Loading of 'DYNPLOAD' import package: ERROR
Import Monitor jobs: running 1, waiting 46, completed 0, failed 17, total 64.
Loading of 'SAPSSEXC_5' import package: ERROR
Import Monitor jobs: running 0, waiting 46, completed 0, failed 18, total 64.
Import Monitor jobs: running 1, waiting 45, completed 0, failed 18, total 64.
Import Monitor jobs: running 2, waiting 44, completed 0, failed 18, total 64.
Import Monitor jobs: running 3, waiting 43, completed 0, failed 18, total 64.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 2, waiting 43, completed 0, failed 19, total 64.
Loading of 'SAPAPPL2_14' import package: ERROR
Import Monitor jobs: running 1, waiting 43, completed 0, failed 20, total 64.
Loading of 'SAPAPPL0_2' import package: ERROR
Import Monitor jobs: running 0, waiting 43, completed 0, failed 21, total 64.
Import Monitor jobs: running 1, waiting 42, completed 0, failed 21, total 64.
Import Monitor jobs: running 2, waiting 41, completed 0, failed 21, total 64.
Import Monitor jobs: running 3, waiting 40, completed 0, failed 21, total 64.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 2, waiting 40, completed 0, failed 22, total 64.
Loading of 'SAPSSEXC_4' import package: ERROR
Import Monitor jobs: running 1, waiting 40, completed 0, failed 23, total 64.
Loading of 'SAPAPPL2_10' import package: ERROR
Import Monitor jobs: running 0, waiting 40, completed 0, failed 24, total 64.
Import Monitor jobs: running 1, waiting 39, completed 0, failed 24, total 64.
Import Monitor jobs: running 2, waiting 38, completed 0, failed 24, total 64.
Import Monitor jobs: running 3, waiting 37, completed 0, failed 24, total 64.
Loading of 'SAPSSEXC_7' import package: ERROR
Import Monitor jobs: running 2, waiting 37, completed 0, failed 25, total 64.
Loading of 'SAPAPPL0_7' import package: ERROR
Import Monitor jobs: running 1, waiting 37, completed 0, failed 26, total 64.
Loading of 'SAPAPPL0_1' import package: ERROR
Import Monitor jobs: running 0, waiting 37, completed 0, failed 27, total 64.
Import Monitor jobs: running 1, waiting 36, completed 0, failed 27, total 64.
Import Monitor jobs: running 2, waiting 35, completed 0, failed 27, total 64.
Import Monitor jobs: running 3, waiting 34, completed 0, failed 27, total 64.
Loading of 'SAPAPPL2_7' import package: ERROR
Import Monitor jobs: running 2, waiting 34, completed 0, failed 28, total 64.
Loading of 'SAPAPPL2_4' import package: ERROR
Import Monitor jobs: running 1, waiting 34, completed 0, failed 29, total 64.
Loading of 'SAPAPPL1_6' import package: ERROR
Import Monitor jobs: running 0, waiting 34, completed 0, failed 30, total 64.
Import Monitor jobs: running 1, waiting 33, completed 0, failed 30, total 64.
Import Monitor jobs: running 2, waiting 32, completed 0, failed 30, total 64.
Import Monitor jobs: running 3, waiting 31, completed 0, failed 30, total 64.
Loading of 'SAPAPPL0_3' import package: ERROR
Import Monitor jobs: running 2, waiting 31, completed 0, failed 31, total 64.
Loading of 'SAPCLUST' import package: ERROR
Import Monitor jobs: running 1, waiting 31, completed 0, failed 32, total 64.
Loading of 'SAPAPPL0_8' import package: ERROR
Import Monitor jobs: running 0, waiting 31, completed 0, failed 33, total 64.
Import Monitor jobs: running 1, waiting 30, completed 0, failed 33, total 64.
Import Monitor jobs: running 2, waiting 29, completed 0, failed 33, total 64.
Import Monitor jobs: running 3, waiting 28, completed 0, failed 33, total 64.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 2, waiting 28, completed 0, failed 34, total 64.
Loading of 'ENHOBJCONTRACT' import package: ERROR
Import Monitor jobs: running 1, waiting 28, completed 0, failed 35, total 64.
Loading of 'SAPAPPL0_4' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 0, failed 36, total 64.
Import Monitor jobs: running 1, waiting 27, completed 0, failed 36, total 64.
Import Monitor jobs: running 2, waiting 26, completed 0, failed 36, total 64.
Import Monitor jobs: running 3, waiting 25, completed 0, failed 36, total 64.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 2, waiting 25, completed 0, failed 37, total 64.
Loading of 'SAPSSEXC_6' import package: ERROR
Import Monitor jobs: running 1, waiting 25, completed 0, failed 38, total 64.
Loading of 'SAPAPPL2_8' import package: ERROR
Import Monitor jobs: running 0, waiting 25, completed 0, failed 39, total 64.
Import Monitor jobs: running 1, waiting 24, completed 0, failed 39, total 64.
Import Monitor jobs: running 2, waiting 23, completed 0, failed 39, total 64.
Import Monitor jobs: running 3, waiting 22, completed 0, failed 39, total 64.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 0, failed 40, total 64.
Loading of 'SAPAPPL2_1' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 0, failed 41, total 64.
Loading of 'SAPAPPL1_5' import package: ERROR
Import Monitor jobs: running 0, waiting 22, completed 0, failed 42, total 64.
Import Monitor jobs: running 1, waiting 21, completed 0, failed 42, total 64.
Import Monitor jobs: running 2, waiting 20, completed 0, failed 42, total 64.
Import Monitor jobs: running 3, waiting 19, completed 0, failed 42, total 64.
Loading of 'REPOTEXT' import package: ERROR
Import Monitor jobs: running 2, waiting 19, completed 0, failed 43, total 64.
Loading of 'SAPAPPL0_5' import package: ERROR
Import Monitor jobs: running 1, waiting 19, completed 0, failed 44, total 64.
Loading of 'SAPAPPL2_9' import package: ERROR
Import Monitor jobs: running 0, waiting 19, completed 0, failed 45, total 64.
Import Monitor jobs: running 1, waiting 18, completed 0, failed 45, total 64.
Import Monitor jobs: running 2, waiting 17, completed 0, failed 45, total 64.
Import Monitor jobs: running 3, waiting 16, completed 0, failed 45, total 64.
Loading of 'SAPSSEXC_10' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 0, failed 46, total 64.
Loading of 'SAPAPPL2_3' import package: ERROR
Import Monitor jobs: running 1, waiting 16, completed 0, failed 47, total 64.
Loading of 'SAPAPPL0_6' import package: ERROR
Import Monitor jobs: running 0, waiting 16, completed 0, failed 48, total 64.
Import Monitor jobs: running 1, waiting 15, completed 0, failed 48, total 64.
Import Monitor jobs: running 2, waiting 14, completed 0, failed 48, total 64.
Import Monitor jobs: running 3, waiting 13, completed 0, failed 48, total 64.
Loading of 'SAPSLEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 13, completed 0, failed 49, total 64.
Loading of 'SAPAPPL0_9' import package: ERROR
Import Monitor jobs: running 1, waiting 13, completed 0, failed 50, total 64.
Loading of 'SAPAPPL2_11' import package: ERROR
Import Monitor jobs: running 0, waiting 13, completed 0, failed 51, total 64.
Import Monitor jobs: running 1, waiting 12, completed 0, failed 51, total 64.
Import Monitor jobs: running 2, waiting 11, completed 0, failed 51, total 64.
Import Monitor jobs: running 3, waiting 10, completed 0, failed 51, total 64.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 2, waiting 10, completed 0, failed 52, total 64.
Loading of 'SAPAPPL2_13' import package: ERROR
Import Monitor jobs: running 1, waiting 10, completed 0, failed 53, total 64.
Loading of 'SAPAPPL2_12' import package: ERROR
Import Monitor jobs: running 0, waiting 10, completed 0, failed 54, total 64.
Import Monitor jobs: running 1, waiting 9, completed 0, failed 54, total 64.
Import Monitor jobs: running 2, waiting 8, completed 0, failed 54, total 64.
Import Monitor jobs: running 3, waiting 7, completed 0, failed 54, total 64.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 2, waiting 7, completed 0, failed 55, total 64.
Loading of 'SAPSDOCU' import package: ERROR
Import Monitor jobs: running 1, waiting 7, completed 0, failed 56, total 64.
Loading of 'SAPAPPL1_1' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 0, failed 57, total 64.
Import Monitor jobs: running 1, waiting 6, completed 0, failed 57, total 64.
Import Monitor jobs: running 2, waiting 5, completed 0, failed 57, total 64.
Import Monitor jobs: running 3, waiting 4, completed 0, failed 57, total 64.
Loading of 'SAPDDIM' import package: ERROR
Import Monitor jobs: running 2, waiting 4, completed 0, failed 58, total 64.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 1, waiting 4, completed 0, failed 59, total 64.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 0, waiting 4, completed 0, failed 60, total 64.
Import Monitor jobs: running 1, waiting 3, completed 0, failed 60, total 64.
Import Monitor jobs: running 2, waiting 2, completed 0, failed 60, total 64.
Import Monitor jobs: running 3, waiting 1, completed 0, failed 60, total 64.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 0, failed 61, total 64.
Loading of 'SAPUSER1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 0, failed 62, total 64.
Loading of 'SAP0000' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 0, failed 63, total 64.
ERROR 2009-10-27 10:53:37.125
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2009-10-27 10:53:37.140
FCO-00011 The step runMigrationMonitor with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|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 ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
Thanks.

i checked the DOKCLU log, pls find the log below:
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20091027104307
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#20 $ SAP
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Aug 23 2009 23:42:38
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe -i DOKCLU.cmd -dbcodepage 4103 -k 1gage5M50Dp01eqte1]x3Qa5 -l DOKCLU.log -stop_on_error -loadprocedure fast LOAD
(DB) INFO: connected to DB
(GSI) INFO: dbname   = "ATD                                                                                "
(GSI) INFO: vname    = "DB6                             "
(GSI) INFO: hostname = "UNKNOWN                                                         "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "SERVER"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 23 Step 7)"
(DB) ERROR: DDL statement failed
( DROP TABLE "DOKCLU" )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
( CREATE TABLE "DOKCLU" ( "ID" SAPDB6CHAR(2) DEFAULT ' ' NOT NULL , "OBJECT" SAPDB6CHAR(60) DEFAULT ' ' NOT NULL , "LANGU" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "TYP" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "DOKVERSION" SAPDB6FIXCHAR(4) DEFAULT '0000' NOT NULL , "PAGENO" SMALLINT DEFAULT 0 NOT NULL , "TIMESTMP" SAPDB6CHAR(46) DEFAULT ' ' NOT NULL , "PAGELG" SMALLINT DEFAULT 0 NOT NULL , "VARDATA" VARCHAR(3800) FOR BIT DATA ) IN ATD#ES700D INDEX IN ATD#ES700I LONG IN ATD#ES700D )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(DB) INFO: disconnected from DB
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20091027104307
Thanks

Error while exporting the 3rd party technical system in SLD

Dear all,
    We're currently using PI 7.0. When trying to export the technical system in SLD, after the exporting, the IE jumps to the download page automatically, but there's a exclamation mark with no text info. I've tried to create a new 3rd-party technical system and try to export, the same thing happened.
    It happened in both our develop and our production PI system.
    Also I've found following error info in SLD server log:
Log Record Details
#33 04/19/2007 10:07:38.573 [SAPEngine_Application_Thread[impl:3]_33]
ERROR com.sap.sld.wd.technicalsystem.ExportView: null
Thrown:
java.lang.UnsupportedOperationException
at java.util.AbstractCollection.add(AbstractCollection.java:216)
at java.util.AbstractCollection.addAll(AbstractCollection.java:319)
at
com.sap.lcr.webui.admin.ImportExportControl.addAssociatorAndReferenceNames(ImportExportControl.java:1244)
at com.sap.sld.wd.technicalsystem.ExportView.getBCSystemExportList
(ExportView.java:285)
at com.sap.sld.wd.technicalsystem.ExportView.getExport
(ExportView.java:193)
at com.sap.sld.wd.technicalsystem.wdp.InternalExportView.getExport
(InternalExportView.java:137)
at
com.sap.sld.wd.technicalsystem.wdp.IPrivateExportView$IContextElement.wdGetObject(IPrivateExportView.java:208)
at com.sap.tc.webdynpro.progmodel.context.AttributePointer.getObject
(AttributePointer.java:158)
at com.sap.tc.webdynpro.clientserver.data.DataContainer.getAndFormat
(DataContainer.java:1092)
at com.sap.tc.webdynpro.clientserver.data.DataContainer.getAndFormat
(DataContainer.java:1064)
at
com.sap.tc.webdynpro.clientserver.uielib.standard.impl.FileDownload._getData(FileDownload.java:81)
at
com.sap.tc.webdynpro.clientserver.uielib.standard.uradapter.FileDownloadAdapter.getReference(FileDownloadAdapter.java:291)
at com.sap.tc.ur.renderer.ie6.LinkRenderer.render(LinkRenderer.java:53)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at
com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutCellFragment(GridLayoutRenderer.java:826)
at
com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutRowFragment(GridLayoutRenderer.java:424)
at
com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutFragment
(GridLayoutRenderer.java:336)
at com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.render
(GridLayoutRenderer.java:79)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at com.sap.tc.ur.renderer.ie6.GroupRenderer.renderGroupFragment
(GroupRenderer.java:1184)
at com.sap.tc.ur.renderer.ie6.GroupRenderer.render
(GroupRenderer.java:74)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at
com.sap.tc.ur.renderer.ie6.FlowLayoutRenderer.renderFlowLayoutItemFragment(FlowLayoutRenderer.java:254)
at
com.sap.tc.ur.renderer.ie6.FlowLayoutRenderer.renderFlowLayoutFragment
(FlowLayoutRenderer.java:210)
at com.sap.tc.ur.renderer.ie6.FlowLayoutRenderer.render
(FlowLayoutRenderer.java:49)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at
com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.renderScrollContainerFragment(ScrollContainerRenderer.java:619)
at com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.render
(ScrollContainerRenderer.java:74)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at
com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.renderViewContainerFragment(ViewContainerRenderer.java:134)
at com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.render
(ViewContainerRenderer.java:49)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at
com.sap.tc.ur.renderer.ie6.FlowLayoutRenderer.renderFlowLayoutItemFragment(FlowLayoutRenderer.java:254)
at
com.sap.tc.ur.renderer.ie6.FlowLayoutRenderer.renderFlowLayoutFragment
(FlowLayoutRenderer.java:210)
at com.sap.tc.ur.renderer.ie6.FlowLayoutRenderer.render
(FlowLayoutRenderer.java:49)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at
com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.renderScrollContainerFragment(ScrollContainerRenderer.java:619)
at com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.render
(ScrollContainerRenderer.java:74)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at
com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.renderViewContainerFragment(ViewContainerRenderer.java:134)
at com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.render
(ViewContainerRenderer.java:49)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at
com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.renderViewContainerFragment(ViewContainerRenderer.java:134)
at com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.render
(ViewContainerRenderer.java:49)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at
com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutCellFragment(GridLayoutRenderer.java:826)
at
com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutRowFragment(GridLayoutRenderer.java:424)
at
com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutFragment
(GridLayoutRenderer.java:336)
at com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.render
(GridLayoutRenderer.java:79)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at
com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.renderScrollContainerFragment(ScrollContainerRenderer.java:619)
at com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.render
(ScrollContainerRenderer.java:74)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.UiWindowRenderer.render(UiWindowRenderer.java:52)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at
com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendHtml
(HtmlClient.java:1039)
at
com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.fillDynamicTemplateContext(HtmlClient.java:455)
at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendResponse
(HtmlClient.java:1223)
at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendResponse
(HtmlClient.java:1179)
at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendResponse
(HtmlClient.java:299)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.finishTasks
(AbstractClient.java:173)
at
com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:753)
at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:705)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing
(ClientSession.java:261)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent
(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost
(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet
(HttpHandlerImpl.java:401)
at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet
(RequestAnalizer.java:387)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet
(RequestAnalizer.java:365)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle
(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle
(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request
(Processor.java:160)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run
(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run
(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute
(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run
(SingleThread.java:170)
Hope you can help us.
Thanks and B'Rgds,
YiNing

not sure if it has relevance, but the SLD level transports will do nothing but create a CIM file which should be downloaded to your deskktop.
1. Make sure that there are no Pop Up BLocker's acting on the XI server on your machine.
2. Make sure that you have the download authorizations on your machine.
Regards
Bhavesh

Getting error in Exporting the data from legacy system to Tables

Hi,
I am trying to export the data. But am getting the below error.
Unknown system exception - java.security.PrivilegedActionException: javax.security.auth.login.LoginException: java.net.ConnectException: t3://abc.com:7001: Bootstrap to abc.jdadelivers.com/0:0:0:0:0:0:0:1:7001 failed. It is likely that the remote side declared peer gone on this JVM.
No records are exported.
Include column headers: Yes
Format : Seperated (,) , enclosing character (")
{code}
I tried with with different user but getting the same error. Please have a look and let us know the route cause of the issue.
Many thanks in advance.
Vas.

Export ? What kind of export is this ? I see a weblogic port... Can you provide more information ?

Export for system copy fails - Error 9 (Bad file number)

Hello all,
I am attempting to perform the export phase for a hetergenous system copy on our BI system (BI 7.0 - NW2004s). This system runs on HP-UX 11.11 using Oracle 10.2.0.2 and will be migrated to Windows Server 2003 and MS SQL Server 2005, once the export is complete.
While running sapinst to export the data from the source system, there are several input dialog screens that are skipped, which means I am not able to enter all the paramters used for the export. After seeing this behavior from sapinst, I reviewed the sapinst.log and sapinst_dev.log files and find the warning/error "System call failed. Error 9 (Bad file number)". I have included a portion of these files below.
I have reviewed notes 546006 and 583861, but these seem to refer to an Oracle error ORA-27121, but I am not receiving any Oracle errors in sapinst.log or the Oracle alert log. I have looked for possible permission or ownership problems with any of the SAP or Oracle files, but have not found any that were incorrect. Also, these errors do not specify which file sapinst is having problems with, so I do not have a specific file or area to check.
If anyone has seen something similar to this and has any suggestions, I would greatly appreciate any help.
sapinst.log details:
INFO 2009-02-14 15:15:51.67
Execute step collect of component |NW_Export|ind|ind|ind|ind|0|0|NW_GetSidFromProfiles|ind|ind|ind|ind|1|0|NW_readProfileDir|ind|ind
|ind|ind|0|0
INFO 2009-02-14 15:15:52.737
Account bwpadm already exists.
WARNING 2009-02-14 15:15:52.747
System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
r.cpp).
INFO 2009-02-14 15:15:52.757
Account 0 already exists.
WARNING 2009-02-14 15:15:52.777
System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
r.cpp).
INFO 2009-02-14 15:15:52.777
Account 200 already exists.
WARNING 2009-02-14 15:15:52.827
System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
r.cpp).
INFO 2009-02-14 15:16:04.937
Creating file /tmp/sapinst_instdir/NW04S/LM/COPY/ORA/EXP/CENTRAL/AS/EXP/ypcat.log.
INFO 2009-02-14 15:16:05.007
Output of ypcat passwd.byname is written to the logfile ypcat.log.
sapinst_dev.log details:
TRACE      2009-02-14 15:15:52.737
2009-02-14 15:15:52.743 NW._getSAPMount() done: /sapmnt
INFO       2009-02-14 15:15:52.737 [syuxcaccmg.cpp:227]
           bool CSyAccountMgtImpl::isExisting(ISyAccountMgt::eAccountType accountType, iastring sName)
Account bwpadm already exists.
TRACE      2009-02-14 15:15:52.747 [syuxcuser.cpp:1943]
           CSyUserImpl_getOsInfos(ILogBook *m_logBook, iastring sName, iastring sID, tSyUserInfo& msUserinfo)
getspnam(bwpadm) returned NULL.
WARNING    2009-02-14 15:15:52.747 [syxxsyshlp.cpp:78]
           syslib::printOSError(const iastring &, int, DWORD, const iastring &, CMessage::eLogMessage)
System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
r.cpp).
Regards,
Rusty Robbins

Hello Peter,
Thanks for the reply. I did confirm the points you made, and have the details below.
1. check filesystem, if you have enough space, especially /tmp
All filesystems have available space, and /tmp has 310 MB available, before the start of sapinst.
2. check again alert log, trace log for Oracle,
I could not find any errors in the alert_SID.log or any unusual trace files.
3. How did you run sapinst? Are you using "root" account.
I am running sapinst as user root and I am following all the recomendations in the system copy guide (at least as far as I can tell. ;p )
We have four BI systems in this landscape, and the other three have migrated successfully. The procedure I am using, is the same as for the other 3 systems and uses the same SAP media directory that was used on the other systems.
One other item that may be part of my problem here, is that this system is the production system, and was originally installed as a high-availability system, using HP-UX Service Guard for clustering. Currently, this system does not have fail-over enabled, but of course the cluster is still intact. One required piece of the Service Guard enviornment is the use of a virtual hostname. This seems to resolve successfully by sapinst, as I see the correct (virtual) hostname referenced several times. While this is a clustered system (for fail-over purposes), the CI and DB are installed on the same host. So it is not a distributed system, and if failover had been initiated, it would fail both the CI and DB instance, which is the same and only SAP instance.
This did raise one question in my mind, however. I am attempting to extract this using the following menu path within sapinst.
SAP NetWeaver 7.0 Support Release 3 --> Software Life-Cycle Options --> System Copy --> Oracle --> Source System Export --> Central System --> Based on AS ABAP and AS Java
Since this does use Service Guard, but is not a distributed system, should I be using a different path in the sapinst tree, for the export? I have only performed a migration using the above path, so I am not familar with the detailf of the other types, such as High-Availabitly or Distributed-System.
Regards,
Rusty

Error while exporting objects

Hi friends,
I am getting the below error while exporting the objects from quality system(xi).
Error-->
"Workspace was not defined for software component version xxxx,1.0 of xx.com. Assign the software component version in the Landscape configurator of the change management service to a track."
Thanks,
Bharath.

https://forums.sdn.sap.com/click.jspa?searchID=16530537&messageID=4024393
Transport using CMS Export Error on Integration Repository
go thru these for it.

Error is system copy form 64 bit to 32bit

Dear All,
I am facing problem in system copy. we have the offlince backup of PRD(64 bit) and the test server is 32 bit.
1. oracle is up and when I try to start sap dispatched get stop in Trans log ORA-01017: invalid username/password; logon denied.
The sid is same as PRD .
2. when I am trying to run oradbusr.sql ORA-06553: PLS-801: internal error [56319]
Regards,
Kumar

Dear All,
We doing system copy and facing problem.
Connected.
ERROR: ORA-06553: PLS-801: internal error [56319]
There source system is 64bit and target system is on 32bit.
In Sap system copy there is upgrade your database from 32-bit to 64-bit but not form 64bit to 32bit.
Do I have to add the same in the control. sol file.
Changes to be made
1. If you want to upgrade your database from 32-bit to 64-bit, add the following lines at the bottom of
the CONTROL.SQL file:
shutdown immediate;
startup restrict
spool utlirp.log
@?/rdbms/admin/utlirp.sql
spool off
alter system disable restricted session;
Till no we have restore the database the oracle is up and running but when starting sap dispatches is getting stop.
It is possiable to do system copy form 64 bit to 32 bit . by any process like R3load.
So Please suggest is there any way .
Regards,
Kumar

Portal Error after system copy

We are getting below error after we performed a dual stack system copy. We are able to connect to VA, Configtool, SDM except portal. Any ideas?!
http://host:port
Application cannot be started.
Details: com.sap.engine.services.deploy.container.ExceptionInfo: Error in starting application [sap.com/com.sap.engine.docs.examples].
std_server0.out has erros like below:
com.sap.portal.prt.sapj2ee.error [SAPEngine_Application_Thread[impl:3]_33] Fatal:
com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_150] Fatal: Exception while starting: sap.com/com.sa
p.netweaver.bc.rf
com.sap.portal.prt.sapj2ee.error [SAPEngine_Application_Thread[impl:3]_7] Fatal:
com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_150] Fatal: Exception while starting: sap.com/com.sa
p.portal.pcm.admin.apiservice
dev_server0:
Wed Sep 17 21:52:37 2008
186.817: [GC 186.817: [ParNew: 119589K->32359K(130560K), 0.0669152 secs] 169148K->81918K(1005056K), 0.0670788 secs]
[Thr 223] Wed Sep 17 21:52:38 2008
[Thr 223] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]
Wed Sep 17 21:54:58 2008
327.480: [GC 327.481: [ParNew: 119399K->35834K(130560K), 0.0745068 secs] 168958K->85393K(1005056K), 0.0746528 secs]
Wed Sep 17 21:54:59 2008
328.550: [GC 328.551: [ParNew: 121894K->43519K(130560K), 0.0827871 secs] 171454K->93460K(1005056K), 0.0829520 secs]
Wed Sep 17 22:01:04 2008
693.368: [GC 693.368: [ParNew: 130559K->43520K(130560K), 0.1257561 secs] 180500K->103573K(1005056K), 0.1259380 secs]

Hello. Try to connect VA, after navigate --> Deploy --> Application , try to find applications
(for example sap.com/com.sap.netweaver.bc.rf or other, and try to start) if it not starts, check the errors directly here. Regards.

Odd System Copy

Hello Experts,
I am performing a homogeneous system copy on linux w/ MaxDB. The source system is really more like source systems. Using one database instance (XDB), I have an ERP 6.0 EHP4 system (XS1) and an EP instance (JS1). My first step was to export the database using the Database Manager; then I made the export available to the target system. The system copy for the abap application server went without a problem. Now I am having trouble with the J2EE system copy.
My assumption was that the single MaxDB export contained both the ABAP schema (SAPXS1) and the J2EE schema (SAPJS1DB). Also, I assumed since XS1 and JS1 are two separate instances sharing a single database instance, then I would also need to complete two system copies. Were any of those two assumptions false?
My hope was to skip the recovery w/ initialization step during the J2EE system copy since the DB containing the J2EE backup should already be loaded in the target database host. The error I'm encountering on the J2EE system copy is "You can not use existing instance while installing with backup/recovery method." Sadly, that error message is very straight forward and doesn't leave much hope to complete both system copies using this method.
A system copy for both ABAP and J2EE stacks ins't the correct path, is it?
Any help is appreciated.
Kind Regards,
Zach Shay

Markus,
Update #1:
It appears that sapinst will allow me to do a system copy of the J2EE stack via the first method.
Standard System Copy / Migration (load-based)
What is a bit queer on the whole situation is the wording that sapinst is presenting me. sapinst asks me for a "Migration Export." I supply the directory with the label, "JAVA." Then sapinst asks me if I would like to use the existing database or create a new one. It allows me to select use existing database (which is a step past what is allowed via Homogenous System Copy)! However, sapinst then asks me for another Migration Export.... Unfortunately this Migration Export has the label "SAP:MIGJDMP:701:::*", and is a label not present in any of my export directories (or subdirectories).
The labels I have from the ABAP and Java exports are:
SAP:JMIG:701:*:*:*
SAP:MIGSDM:701:MIGRATION:*:*
SAP:MIGAPPS:701:MIGRATION:*:*
SAP:MIG:*:EXPORT(1/:*:*
Is this MIGJDMP Migration Export related to a database export via R3Load or something similar? If so, how do I get this?
\[reading more documentation...\]
Thank you,
Zach

System Copy and Logical system name conversion

Hello All,
Can any one let me know some inputs over these few queries.
1. How much time would a 500+GB clients take for Export and reimport after the system copy.
2. What would be run time of the BDLSS report ( Converting the logical system names) for a typical 1500 GB QTY system
The requirement is my QTY has 3 clients, and i would like to refresh it with my PRD data. How do i safely perform thia activity with the least downtine possible and please note, the clients are around 500+ GB huge..
Thanks in advance for your inputs.
Rgds,
Sri

Hi Frank,
the parameters of my installation are as folows.
Appl Serv : OS - AIX (5.2 Version) and CPU's - 4 (Mem 20480) ::: DB serv : OS - AIX(5.2 Version) and CPU - 6 (Mem 22528)
The DB version is Oracle 9.2
We are on 4.7 enterprise version of SAP with SAPKA62055 patrch level.
br
Sri

Error in export phase of a PI system copy

Similar Messages

Maybe you are looking for