System copy tool

Hi friends,
I want to know from where i can download system copy tool for BW 3.5 640_REL HPUX 640 itinuim.
Please help and let us know.
thanks.

Hi:
Pls chk this document , might be useful
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
Check following OSS notes.
Note 543715 - Projects for BW Migrations and System Copies
Note 886102 - System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
Note 325525 - Copying and renaming systems in a BW environment
Note 184754 - Procedure after BW database copy
BW system Copy :
System Copy BW
Re: bw system copy
BDLS :
Re: After R/3 Refresh
BDLS on BW Q/A
Regards
CSM Reddy
*pls assign points if links are useful**

Similar Messages

Java System Copy tool

Hi,
We have an ECC6 on NW 7 landscape and require a tool to copy system data across 2 SAP systems. I have come across this Java System Copy Tool. I have downloaded the packages:-
Time analyzer
Package Splitter
Migration monitor
OraBRcopy
read the various documents that came with it and i just wanted to know that does this need to be run with SAPinst or can these need to be run individually? seems a bit confusing as there is no a straight forward document to read. I have read the Oracle Parameters that need to be set so that is one thing to discuss with my team.
We have a very big database and i wanted to ask if someone out there has used this that how long did it take migrating your database and under what conditions i.e. was database shutdown, done when system least used, etc?
It seems that Migration Monitor does the job of exporting and importing the packages but i am not sure how Package splitter or time analyzer fits into this?
OraBRcopy is the same as using R3COPY so that is no problem for me but just these inidividual tools i need help understanding.
Your help would be very much appreciated.
Thanks
Mani

> We use the database copy procedure and apply redo logs after to a level the apps poeple want it, but recovery takes a long time and it requires lengthy file checks as some are missing so we were investigating alternative methods available one of which was this SAP tool.
You never do full backups?
> My understanding of what you are saying and please correct me if i am wrong.. is that sapinst can copy either java content (assume you mean the java database schema??) or ABAP schema or both. export the java contents and continue using the normal database copy/redo logs method?
Yes. You would
- take a backup of the source database
- execute "sapinst", select system copy and select, that you're doing a "backup/restore" procedure
- sapinst will put all the Java parts together and create a dump of it
- you start sapinst on the target system, select system copy and that you're doing a "backup/restore" procedure
- sapinst will install SCS/CI and stop then asking you to recover the database
- sapinst will continue and setup the Java part
What you encounter is one of the major drawbacks when using DualStack instances. I would, if it's possible, separate the two instances so you can copy them independently of each other.
Markus

System copy tools for SAP Basis 46C.

Hi All,
I need to do system copy for SAP Basis 46c. I have a query regarding the tools used for system copy. It is written in the SAP Documents and we need to use the latest version of the system copy tools (i.e. R3load,R3check,R3ldctl,,R3szchk,R3trans).
I need to do the Heterogeneouse system copy
Source :- Oracle 9.2.0.8 , AIX 5.3
Target :- Oralce 9.2.0.8 (Or 10.2.0.4 if possible) , Sun Solaris
So my question is
1) Am i suppose to use only the tools (i.e. R3load,R3check,R3ldctl,,R3szchk,R3trans) which are compatible to relase 4.6C (Kernel 46D_EXT, latest path level is 2541) or
2) Can i download and use the Latest version of system copy tools (i.e. Withe release 7.00 for R3load,R3check,R3ldctl,,R3szchk,R3trans) to do the herogeneous system copy of SAP Basis 4.6C ??
Please reply.
Thanks

> Yes we are aware about the certified consultant. But before going for such a big project we wanted to find out the possibilities how we can minimise system downtime and optimize the process therefore wanted to have some information earlier.
Exactly that is the use of that consultant Those are experienced people who have done lots of migrations in the past, they know the possibilities of the tools and versions.
> So now i am very sure that we can use 10.2 while installation of new target system while doing heterogenouse system copy from oracle 9.2.
Correct.
> 1) Migration Monitor (source :-System copy & Migration optimization.pdf)
> The Migration Monitor is downward-compatible. As new features and bug fixes are only implemented in the latest version, SAP urgently recommends that you always use the latest version available.
You can use it of course but support of it is not "built in" - there's no clicker to check as is in newer versions of sapinst. You will need to modify the R3S file at the "correct place" to make use of it.
> 2) Distribution Monitor (Source :- Distribution Monitor (version 1.9.1) Usersu2019 Guide)
> Restrictions:-The following restrictions apply to the current implementation:The DM does not support system copies of releases lower than SAP_BASIS 6.20
So you can't use that option.
> 3) PACKAGE SPLITTING (source :-System copy & Migration optimization.pdf)
> The package splitting option is available and integrated into the system copy tools R3SETUP and SAPinst since SAP R/3 4.0B SR1.
The "old version" is a perl script, you'll need to make sure you have perl installed.
>
> 4) TABLE SPLITTING (source :-System copy & Migration optimization.pdf)
> AVAILABILITY:
> Table splitting can be used for ABAP systems with SAP kernel 6.40 or above
So that is also not usable.
> 6) R3LOAD OPTIONS - (source :-System copy & Migration optimization.pdf)
> R3load option '-fast' (<= 4.6D) or '-loadprocedure fast': These options are available
> u2022 from SAP kernel release 6.40 for - DB2/UDB - MSSQL - Oracle (see SAP Note 1045847 - Oracle Direct Path Load Support in R3load)
So it's also not built in for Kernel 46D_EX2.
> Request your final comments on the above points and Need to know whether parallel import and export can be done for 4.6C (46D_EXT Kernel) release using migration monitor. Please reply.
As I said before and as is written in the documentation, it can be used but not "by default", you'll make sure you stop at the right place with your migration to configure it manually (or the consultant will do).
Markus

PI 7.1 system copy (abap+java)

Hello,
We need homogenous copy of PI 7.1 system to an existing system (newly installed PI 7.1). I would like to use database specific option (oracle).I was studying SAP guide for System copy of PI 7.1 and there are slight diff comparing to NW 7.0 double stacks.
Comparing to NW 7.0 double stacks I can't see here step for exporting central instance where application specific filesystem and SDM filesystem was archived (I know SDM is not present in 7.1 anymore). In addition I can see in guide for 7.1 new option for database refresh. However this section also does not describes any needs for taking special care of java filesystem content.Does it mean that I do not need to take special care for java filesytem content anymore on 7.1?
I am bit wondering if it is sufficient for 7.1 just to refresh DB (with restore method for oracle for example) and then perform just adaptation of java IDs in profiles as described in section for database refresh of system copy guide PI 7.1? Will be this way system consistent (consistent abap part and consistent java part)? On NW 7.0 after restore of DB only, java part would be not consistent, is this new in 7.1?
Thanks for your feedback in advance

Hello -
Since you need the complete ABAP and JAVA databases, you will want to use the system copy tool on the installation CD. If you are using a Micrsoft SQL system, you will be able to save yourself some steps. Here is what we did for our MSSQL refresh:
Use sapinst to do a file system export on the source system.
Take back up of source system and use sapinst to restore it to target system.
Process
1. Detach the database files from the source system database or create a backup and copy the files
to the target system.
2. Attach the database files or restore the backup of the source database on the target database server.
3. Run SAPinst to install the target system by choosing the following on the Welcome screen:
<Your SAP system> Software Life-Cycle Options System Copy Target System <system variant>
<technical stack> .
Let me know if you have more questions or if you need more information. I can try and answer a few if you are trying to use ORACLE and UNIX / LINUX. Thanks! - Will S.

Homogeneous System Copy on Windows/Oracle.

Hi!
I have to start a project on Homogeneous System Copy on Windows/Oracle.
I have gone through the System Copy documents by SAP and also verious SAP note (spl. 659509 ). But still I am not really clear about the whole process.
As per my understanding, as follows :
1. Export the Database from Source Host. But HOW? Wheather I have to use any System Tool from SAP ? 
Copy that to Target Host.
2. Install the CI in Target Host. As I am working on SAP 4.7 1.10 (SR1) with Kernel 6.20 (NU).
3. At the time of installation of DI in Target Host give the path of Exoprt fileset.
My question :
1. Wheather my plan is right or needs change?
2. What type of copy it will be :
a) Homogeneous System Copy using Online / Offline Database Backup.
b) Homogeneous System Copy using R3LOAD Procedure.
c) Homogeneous System Copy using R3COPY Procedure.
3. Do I really need to download/order any system copy tool from SAP?
My Source :
SAP 4.7 on Windows 2000 with Oracle 8.1.7 with noarchivelog mode.
Terget :
SAP 4.7 on Windows 2003 with Oracle9.2.0.8
All Kernel : 620 (NU)
Looking for an urgent solution.
With Kind Regards,
Pratip Bhattacharyya

Hi! Umesh,
I have found 2 errore .
1) ORA-01652: unable to extend temp segment by 2560 in tablespace PSAPTEMP
2) DbSl Trace: ORA-1403 when accessing table SAPUSER
Two things I want to mention here.
1. I donot know the passwd of datadase users of Source . I have used different passwd for Target DB userd.
2. Used defferent SAP SID. Source : ID4 and Target : IDN
Is that cause any harm?
Here is the detail logs of those two files.
SAPSSEXC.log
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: START OF LOG: 20061222010532
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: version R6.20/V1.2
D:\usr\sap\IDN\SYS\exe\run/R3load.exe -ctf I G:\Export/DATA/SAPSSEXC.STR C:\SAPinst ORACLE SAPINST_di/DDLORA.TPL C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.TSK ORA -l C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.log
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: job completed
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: END OF LOG: 20061222010532
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: START OF LOG: 20061222010539
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: version R6.20/V1.2
D:\usr\sap\IDN\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.cmd -l C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.log -stop_on_error
DbSl Trace: Got ORACLE_HOME=D:\oracle\idn\928 from environment
DbSl Trace: Client NLS settings: AMERICAN_AMERICA.WE8DEC
DbSl Trace: Logon as OPS$-user to get SAPIDN's password
DbSl Trace: Connecting as /@IDN on connection 0 ...
DbSl Trace: Attaching to DB Server IDN (con_hdl=0,svchp=0146C57C,svrhp=0146E82C)
DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
DbSl Trace: Now I'm connected to ORACLE
DbSl Trace: ORA-1403 when accessing table SAPUSER
DbSl Trace: Disconnecting from connection 0 ...
DbSl Trace: Closing user session (con_hdl=0,svchp=0146C57C,usrhp=01477414)
DbSl Trace: Now I'm disconnected from ORACLE
DbSl Trace: Try to connect with default password
DbSl Trace: Connecting as SAPIDN/<pwd>@IDN on connection 0 ...
DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
DbSl Trace: Now I'm connected to ORACLE
DbSl Trace: Database NLS settings: AMERICAN_AMERICA.WE8DEC
DbSl Trace: Database instance idn is running on DLWSDV10 with ORACLE version 9.2.0.8.0 since 20061222
Fri Dec 22 01:05:39 2006
***LOG BZA=> table SVERS does not exist on database [dblink#1 @ 1292] [dblink 1292 ]
(DB) INFO: connected to DB
(GSI) INFO: dbname = "IDN20061222121231 "
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname = "DLWSDV10 "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "DLWSDV10"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "8x Intel 801586 (Mod 4 Step 9)"
(DB) INFO: BCACT created
(IMP) INFO: import of BCACT completed (0 rows)
(DB) INFO: BCACT~0 created
(DB) INFO: BCCOM created
(IMP) INFO: import of BCCOM completed (0 rows)
(DB) INFO: BCCOM~0 created
(DB) INFO: BCEXC created
(IMP) INFO: import of BCEXC completed (0 rows)
(DB) INFO: BCEXC~0 created
(DB) INFO: BCRES created
(IMP) INFO: import of BCRES completed (0 rows)
(DB) INFO: BCRES~0 created
(DB) INFO: BCSPO created
(IMP) INFO: import of BCSPO completed (0 rows)
(DB) INFO: BCSPO~0 created
(DB) INFO: BCTOU created
(IMP) INFO: import of BCTOU completed (0 rows)
(DB) INFO: BCTOU~0 created
(DB) INFO: BRATEXT created
(IMP) INFO: import of BRATEXT completed (914265 rows)
(DB) INFO: BRATEXT~0 created
(DB) INFO: BTCSED created
(IMP) INFO: import of BTCSED completed (623 rows)
(DB) INFO: BTCSED~0 created
(DB) INFO: CD0T000 created
(IMP) INFO: import of CD0T000 completed (0 rows)
(DB) INFO: CD0T000~0 created
(DB) INFO: CD0T120TAB created
(IMP) INFO: import of CD0T120TAB completed (0 rows)
(DB) INFO: CD0T120TAB~0 created
(DB) INFO: CD0T130TAB created
(IMP) INFO: import of CD0T130TAB completed (0 rows)
(DB) INFO: CD0T130TAB~0 created
(DB) INFO: CD0T140TAB created
(IMP) INFO: import of CD0T140TAB completed (0 rows)
(DB) INFO: CD0T140TAB~0 created
(DB) INFO: CD0T500TAB created
(IMP) INFO: import of CD0T500TAB completed (0 rows)
(DB) INFO: CD0T500TAB~0 created
(DB) INFO: CD2APP0 created
(IMP) INFO: import of CD2APP0 completed (0 rows)
(DB) INFO: CD2APP0~0 created
(DB) INFO: CD2HV1PTAB created
(IMP) INFO: import of CD2HV1PTAB completed (0 rows)
(DB) INFO: CD2HV1PTAB~0 created
(DB) INFO: CD2HV2FTAB created
(IMP) INFO: import of CD2HV2FTAB completed (0 rows)
(DB) INFO: CD2HV2FTAB~0 created
(DB) INFO: CNTLWARN created
(IMP) INFO: import of CNTLWARN completed (0 rows)
(DB) INFO: CNTLWARN~0 created
(DB) INFO: D010INC created
(IMP) INFO: import of D010INC completed (3599971 rows)
(DB) INFO: D010INC~0 created
(DB) INFO: D010INC~1 created
(DB) INFO: D010TAB created
(IMP) INFO: import of D010TAB completed (11017270 rows)
DbSl Trace: ORA-1652 occured when executing SQL statement (parse error offset = 35)
DbSl Trace: sc_p=013ED590,no=20,idc_p=00000000,con=0,act=0,slen=187,smax=256,#vars=0,stmt=01E1A0C8,table=
DbSl Trace: CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPIDN620 STORAGE (\
DbSl Trace: INITIAL 0 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) ;
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPIDN620 STORAGE (INITIAL 0 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 1652)
error message returned by DbSl:
ORA-01652: unable to extend temp segment by 2560 in tablespace PSAPTEMP
DbSl Trace: Disconnecting from connection 0 ...
DbSl Trace: Closing user session (con_hdl=0,svchp=0146C57C,usrhp=01477414)
DbSl Trace: Detaching from DB Server (con_hdl=0,svchp=0146C57C,srvhp=0146E82C)
DbSl Trace: Now I'm disconnected from ORACLE
(DB) INFO: disconnected from DB
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: job finished with 1 error(s)
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: END OF LOG: 20061222011210
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: START OF LOG: 20061222023556
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: version R6.20/V1.2
D:\usr\sap\IDN\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.cmd -l C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.log -stop_on_error
DbSl Trace: Got ORACLE_HOME=D:\oracle\idn\928 from environment
DbSl Trace: Client NLS settings: AMERICAN_AMERICA.WE8DEC
DbSl Trace: Logon as OPS$-user to get SAPIDN's password
DbSl Trace: Connecting as /@IDN on connection 0 ...
DbSl Trace: Attaching to DB Server IDN (con_hdl=0,svchp=0146C57C,svrhp=0146E82C)
DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
DbSl Trace: Now I'm connected to ORACLE
DbSl Trace: ORA-1403 when accessing table SAPUSER
DbSl Trace: Disconnecting from connection 0 ...
DbSl Trace: Closing user session (con_hdl=0,svchp=0146C57C,usrhp=01477414)
DbSl Trace: Now I'm disconnected from ORACLE
DbSl Trace: Try to connect with default password
DbSl Trace: Connecting as SAPIDN/<pwd>@IDN on connection 0 ...
DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
DbSl Trace: Now I'm connected to ORACLE
DbSl Trace: Database NLS settings: AMERICAN_AMERICA.WE8DEC
DbSl Trace: Database instance idn is running on DLWSDV10 with ORACLE version 9.2.0.8.0 since 20061222
(DB) INFO: connected to DB
(GSI) INFO: dbname = "IDN20061222121231 "
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname = "DLWSDV10 "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "DLWSDV10"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "8x Intel 801586 (Mod 4 Step 9)"
(DB) ERROR: DDL statement failed
(DROP INDEX "D010TAB~0")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: ORA-1652 occured when executing SQL statement (parse error offset = 35)
DbSl Trace: sc_p=013ECFEC,no=1,idc_p=00000000,con=0,act=0,slen=187,smax=256,#vars=0,stmt=01E06DA8,table=
DbSl Trace: CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPIDN620 STORAGE (\
DbSl Trace: INITIAL 0 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) ;
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPIDN620 STORAGE (INITIAL 0 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 1652)
error message returned by DbSl:
ORA-01652: unable to extend temp segment by 2560 in tablespace PSAPTEMP
DbSl Trace: Disconnecting from connection 0 ...
DbSl Trace: Closing user session (con_hdl=0,svchp=0146C57C,usrhp=01477414)
DbSl Trace: Detaching from DB Server (con_hdl=0,svchp=0146C57C,srvhp=0146E82C)
DbSl Trace: Now I'm disconnected from ORACLE
(DB) INFO: disconnected from DB
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: job finished with 1 error(s)
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: END OF LOG: 20061222023612
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: START OF LOG: 20061222031914
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: version R6.20/V1.2
D:\usr\sap\IDN\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.cmd -l C:\SAPinst ORACLE SAPINST_di/SAPSSEXC.log -stop_on_error
DbSl Trace: Got ORACLE_HOME=D:\oracle\idn\928 from environment
DbSl Trace: Client NLS settings: AMERICAN_AMERICA.WE8DEC
DbSl Trace: Logon as OPS$-user to get SAPIDN's password
DbSl Trace: Connecting as /@IDN on connection 0 ...
DbSl Trace: Attaching to DB Server IDN (con_hdl=0,svchp=0146C57C,svrhp=0146E82C)
DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
DbSl Trace: Now I'm connected to ORACLE
DbSl Trace: ORA-1403 when accessing table SAPUSER
DbSl Trace: Disconnecting from connection 0 ...
DbSl Trace: Closing user session (con_hdl=0,svchp=0146C57C,usrhp=01477414)
DbSl Trace: Now I'm disconnected from ORACLE
DbSl Trace: Try to connect with default password
DbSl Trace: Connecting as SAPIDN/<pwd>@IDN on connection 0 ...
DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
DbSl Trace: Now I'm connected to ORACLE
DbSl Trace: Database NLS settings: AMERICAN_AMERICA.WE8DEC
DbSl Trace: Database instance idn is running on DLWSDV10 with ORACLE version 9.2.0.8.0 since 20061222
(DB) INFO: connected to DB
(GSI) INFO: dbname = "IDN20061222121231 "
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname = "DLWSDV10 "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "DLWSDV10"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "8x Intel 801586 (Mod 4 Step 9)"
(DB) ERROR: DDL statement failed
(DROP INDEX "D010TAB~0")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: ORA-1652 occured when executing SQL statement (parse error offset = 35)
DbSl Trace: sc_p=013ECFEC,no=1,idc_p=00000000,con=0,act=0,slen=187,smax=256,#vars=0,stmt=01E06DA8,table=
DbSl Trace: CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPIDN620 STORAGE (\
DbSl Trace: INITIAL 0 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) ;
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "D010TAB~0" ON "D010TAB" ( "MASTER", "TABNAME" ) TABLESPACE PSAPIDN620 STORAGE (INITIAL 0 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 1652)
error message returned by DbSl:
ORA-01652: unable to extend temp segment by 2560 in tablespace PSAPTEMP
DbSl Trace: Disconnecting from connection 0 ...
DbSl Trace: Closing user session (con_hdl=0,svchp=0146C57C,usrhp=01477414)
DbSl Trace: Detaching from DB Server (con_hdl=0,svchp=0146C57C,srvhp=0146E82C)
DbSl Trace: Now I'm disconnected from ORACLE
(DB) INFO: disconnected from DB
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: job finished with 1 error(s)
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: END OF LOG: 20061222031938
SAPAPPL0.log
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: START OF LOG: 20061222010528
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: version R6.20/V1.2
D:\usr\sap\IDN\SYS\exe\run/R3load.exe -ctf I G:\Export/DATA/SAPAPPL0.STR C:\SAPinst ORACLE SAPINST_di/DDLORA.TPL C:\SAPinst ORACLE SAPINST_di/SAPAPPL0.TSK ORA -l C:\SAPinst ORACLE SAPINST_di/SAPAPPL0.log
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: job completed
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: END OF LOG: 20061222010530
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: START OF LOG: 20061222010539
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
D:\usr\sap\IDN\SYS\exe\run/R3load.exe: version R6.20/V1.2
D:\usr\sap\IDN\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\SAPinst ORACLE SAPINST_di/SAPAPPL0.cmd -l C:\SAPinst ORACLE SAPINST_di/SAPAPPL0.log -stop_on_error
DbSl Trace: Got ORACLE_HOME=D:\oracle\idn\928 from environment
DbSl Trace: Client NLS settings: AMERICAN_AMERICA.WE8DEC
DbSl Trace: Logon as OPS$-user to get SAPIDN's password
DbSl Trace: Connecting as /@IDN on connection 0 ...
DbSl Trace: Attaching to DB Server IDN (con_hdl=0,svchp=0146C57C,svrhp=0146E82C)
DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
DbSl Trace: Now I'm connected to ORACLE
DbSl Trace: ORA-1403 when accessing table SAPUSER
DbSl Trace: Disconnecting from connection 0 ...
DbSl Trace: Closing user session (con_hdl=0,svchp=0146C57C,usrhp=01477414)
DbSl Trace: Now I'm disconnected from ORACLE
DbSl Trace: Try to connect with default password
DbSl Trace: Connecting as SAPIDN/<pwd>@IDN on connection 0 ...
DbSl Trace: Starting user session (con_hdl=0,svchp=0146C57C,srvhp=0146E82C,usrhp=01477414)
DbSl Trace: Now I'm connected to ORACLE
DbSl Trace: Database NLS settings: AMERICAN_AMERICA.WE8DEC
DbSl Trace: Database instance idn is running on DLWSDV10 with ORACLE version 9.2.0.8.0 since 20061222
Fri Dec 22 01:05:39 2006
***LOG BZA=> table SVERS does not exist on database [dblink#1 @ 1292] [dblink 1292 ]
(DB) INFO: connected to DB
(GSI) INFO: dbname = "IDN20061222121231 "
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname = "DLWSDV10 "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "DLWSDV10"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "8x Intel 801586 (Mod 4 Step 9)"
(DB) INFO: /1SAP1/FC_TFG200 created
(IMP) INFO: import of /1SAP1/FC_TFG200 completed (3 rows)
(DB) INFO: /1SAP1/FC_TFG200~0 created
(DB) INFO: /1SAP1/FC_TFG201 created
(IMP) INFO: import of /1SAP1/FC_TFG201 completed (2 rows)
(DB) INFO: /1SAP1/FC_TFG201~0 created
(DB) INFO: /1SAP1/FC_TFG300 created
(IMP) INFO: import of /1SAP1/FC_TFG300 completed (3 rows)
(DB) INFO: /1SAP1/FC_TFG300~0 created
(DB) INFO: /1SAP1/FC_TFG301 created
(IMP) INFO: import of /1SAP1/FC_TFG301 completed (4 rows)
(DB) INFO: /1SAP1/FC_TFG301~0 created
(DB) INFO: /SAPDMC/LSCDOCU created
(IMP) INFO: import of /SAPDMC/LSCDOCU completed (25 rows)
(DB) INFO: /SAPDMC/LSCDOCU~0 created
(DB) INFO: /SAPDMC/LSCDOCUT created
(IMP) INFO: import of /SAPDMC/LSCDOCUT completed (200 rows)
(DB) INFO: /SAPDMC/LSCDOCUT~0 created
(DB) INFO: /SAPDMC/LSCRULE created
(IMP) INFO: import of /SAPDMC/LSCRULE completed (15 rows)
(DB) INFO: /SAPDMC/LSCRULE~0 created
(DB) INFO: /SAPDMC/LSCRULET created
(IMP) INFO: import of /SAPDMC/LSCRULET completed (119 rows)
(DB) INFO: /SAPDMC/LSCRULET~0 created
(DB) INFO: /SAPDMC/LSCSTEPS created
(IMP) INFO: import of /SAPDMC/LSCSTEPS completed (62 rows)
(DB) INFO: /SAPDMC/LSCSTEPS~0 created
(DB) INFO: /SAPDMC/LSCSTEPT created
(IMP) INFO: import of /SAPDMC/LSCSTEPT completed (495 rows)
(DB) INFO: /SAPDMC/LSCSTEPT~0 created
(DB) INFO: /SAPDMC/LSCVERSN created
(IMP) INFO: import of /SAPDMC/LSCVERSN completed (19 rows)
(DB) INFO: /SAPDMC/LSCVERSN~0 created
(DB) INFO: /SAPDMC/LSGBDCA created
(IMP) INFO: import of /SAPDMC/LSGBDCA completed (74 rows)
(DB) INFO: /SAPDMC/LSGBDCA~0 created
(DB) INFO: /SAPDMC/LSGBDCS created
(IMP) INFO: import of /SAPDMC/LSGBDCS completed (74 rows)
(DB) INFO: /SAPDMC/LSGBDCS~0 created
(DB) INFO: /SAPDMC/LSGBDCT created
(IMP) INFO: import of /SAPDMC/LSGBDCT completed (74 rows)
(DB) INFO: /SAPDMC/LSGBDCT~0 created
(DB) INFO: /SAPDMC/LSGCUST created
(IMP) INFO: import of /SAPDMC/LSGCUST completed (0 rows)
(DB) INFO: /SAPDMC/LSGCUST~0 created
(DB) INFO: /SAPDMC/LSGSUB created
(IMP) INFO: import of /SAPDMC/LSGSUB completed (166 rows)
(DB) INFO: /SAPDMC/LSGSUB~0 created
(DB) INFO: /SAPDMC/LSGUSDFI created
(IMP) INFO: import of /SAPDMC/LSGUSDFI completed (16 rows)
(DB) INFO: /SAPDMC/LSGUSDFI~0 created
(DB) INFO: /SAPDMC/LSMCUST created
(IMP) INFO: import of /SAPDMC/LSMCUST completed (0 rows)
(DB) INFO: /SAPDMC/LSMCUST~0 created
(DB) INFO: /SAPDMC/LSOALG created
(IMP) INFO: import of /SAPDMC/LSOALG completed (1250 rows)
(DB) INFO: /SAPDMC/LSOALG~0 created
(DB) INFO: /SAPDMC/LSOATT created
(IMP) INFO: import of /SAPDMC/LSOATT completed (269 rows)
(DB) INFO: /SAPDMC/LSOATT~0 created
(DB) INFO: /SAPDMC/LSOLOG created
(IMP) INFO: import of /SAPDMC/LSOLOG completed (461 rows)
(DB) INFO: /SAPDMC/LSOLOG~0 created
(DB) INFO: /SAPDMC/LSOPAR created
(IMP) INFO: import of /SAPDMC/LSOPAR completed (1421 rows)
(DB) INFO: /SAPDMC/LSOPAR~0 created
(DB) INFO: /SAPDMC/LSOREC created
(IMP) INFO: import of /SAPDMC/LSOREC completed (56 rows)
(DB) INFO: /SAPDMC/LSOREC~0 created
(DB) INFO: /SAPDMC/LSOTXT created
(IMP) INFO: import of /SAPDMC/LSOTXT completed (455 rows)
(DB) INFO: /SAPDMC/LSOTXT~0 created
(DB) INFO: /SAPDMC/LSRATT created
(IMP) INFO: import of /SAPDMC/LSRATT completed (304 rows)
(DB) INFO: /SAPDMC/LSRATT~0 created
(DB) INFO: /SAPDMC/LSRTXT created
(IMP) INFO: import of /SAPDMC/LSRTXT completed (308 rows)
(DB) INFO: /SAPDMC/LSRTXT~0 created
(DB) INFO: /SAPDMC/LSUCUST created
(IMP) INFO: import of /SAPDMC/LSUCUST completed (22 rows)
(DB) INFO: /SAPDMC/LSUCUST~0 created
(DB) INFO: /SAPDMC/LSUMENU created
(IMP) INFO: import of /SAPDMC/LSUMENU completed (0 rows)
(DB) INFO: /SAPDMC/LSUMENU~0 created
(DB) INFO: /SAPDMC/LSUPROF created
(IMP) INFO: import of /SAPDMC/LSUPROF completed (19 rows)
(DB) INFO: /SAPDMC/LSUPROF~0 created
(DB) INFO: /SAPNEA/MR3_SODT created
(IMP) INFO: import of /SAPNEA/MR3_SODT completed (0 rows)
(DB) INFO: /SAPNEA/MR3_SODT~0 created
(DB) INFO: /SAPSLL/ECPPA created
(IMP) INFO: import of /SAPSLL/ECPPA completed (0 rows)
(DB) INFO: /SAPSLL/ECPPA~0 created
(DB) INFO: /SAPSMOSS/STAT created
(IMP) INFO: import of /SAPSMOSS/STAT completed (9 rows)
(DB) INFO: /SAPSMOSS/STAT~0 created
(DB) INFO: /SAPSMOSS/STATT created
(IMP) INFO: import of /SAPSMOSS/STATT completed (171 rows)
(DB) INFO: /SAPSMOSS/STATT~0 created
(DB) INFO: /SAPSMOSS/TURL created
(IMP) INFO: import of /SAPSMOSS/TURL completed (4 rows)
(DB) INFO: /SAPSMOSS/TURL~0 created
(DB) INFO: /SAPTRX/APARPRF created
(IMP) INFO: import of /SAPTRX/APARPRF completed (0 rows)
(DB) INFO: /SAPTRX/APARPRF~0 created
(DB) INFO: /SAPTRX/APARPRFT created
(IMP) INFO: import of /SAPTRX/APARPRFT completed (0 rows)
(DB) INFO: /SAPTRX/APARPRFT~0 created
(DB) INFO: /SAPTRX/ASFCTEV created
(IMP) INFO: import of /SAPTRX/ASFCTEV completed (40 rows)
(DB) INFO: /SAPTRX/ASFCTEV~0 created
(DB) INFO: /SAPTRX/ASFCTEVT created
(IMP) INFO: import of /SAPTRX/ASFCTEVT completed (88 rows)
(DB) INFO: /SAPTRX/ASFCTEVT~0 created
(DB) INFO: /SAPTRX/ASFCTPAR created
(IMP) INFO: import of /SAPTRX/ASFCTPAR completed (305 rows)
(DB) INFO: /SAPTRX/ASFCTPAR~0 created
(DB) INFO: /SAPTRX/ASFCTPAT created
(IMP) INFO: import of /SAPTRX/ASFCTPAT completed (671 rows)
(DB) INFO: /SAPTRX/ASFCTPAT~0 created
(DB) INFO: /SAPTRX/ASPARDC created
(IMP) INFO: import of /SAPTRX/ASPARDC completed (0 rows)
(DB) INFO: /SAPTRX/ASPARDC~0 created
(DB) INFO: /SAPTRX/ASPARDCT created
(IMP) INFO: import of /SAPTRX/ASPARDCT completed (0 rows)
(DB) INFO: /SAPTRX/ASPARDCT~0 created
(DB) INFO: /SAPTRX/SCSOMAP created
(IMP) INFO: import of /SAPTRX/SCSOMAP completed (0 rows)
(DB) INFO: /SAPTRX/SCSOMAP~0 created
(DB) INFO: /SAPTRX/SOLUTN created
(IMP) INFO: import of /SAPTRX/SOLUTN completed (0 rows)
(DB) INFO: /SAPTRX/SOLUTN~0 created
(DB) INFO: /SAPTRX/SOLUTNT created
(IMP) INFO: import of /SAPTRX/SOLUTNT completed (0 rows)
(DB) INFO: /SAPTRX/SOLUTNT~0 created
(DB) INFO: /SDF/STGLTRAN created
(IMP) INFO: import of /SDF/STGLTRAN completed (0 rows)
(DB) INFO: /SDF/STGLTRAN~0 created
(DB) INFO: /SOMO/INPUTTAB created
(IMP) INFO: import of /SOMO/INPUTTAB completed (12 rows)
(DB) INFO: /SOMO/INPUTTAB~0 created
(DB) INFO: A000 created
(IMP) INFO: import of A000 completed (0 rows)
(DB) INFO: A000~0 created
(DB) INFO: A002 created
(IMP) INFO: import of A002 completed (68 rows)
(DB) INFO: A002~0 created
(DB) INFO: A008 created
(IMP) INFO: import of A008 completed (0 rows)
(DB) INFO: A008~0 created
(DB) INFO: A011 created
(IMP) INFO: import of A011 completed (28 rows)
(DB) INFO: A011~0 created
(DB) INFO: A013 created
(IMP) INFO: import of A013 completed (68 rows)
(DB) INFO: A013~0 created
(DB) INFO: A014 created
(IMP) INFO: import of A014 completed (62 rows)
(DB) INFO: A014~0 created
(DB) INFO: A020 created
(IMP) INFO: import of A020 completed (2 rows)
(DB) INFO: A020~0 created
(DB) INFO: A027 created
(IMP) INFO: import of A027 completed (16 rows)
(DB) INFO: A027~0 created
(DB) INFO: A029 created
(IMP) INFO: import of A029 completed (0 rows)
(DB) INFO: A029~0 created
(DB) INFO: A031 created
(IMP) INFO: import of A031 completed (0 rows)
(DB) INFO: A031~0 created
(DB) INFO: A033 created
(IMP) INFO: import of A033 completed (8 rows)
(DB) INFO: A033~0 created
(DB) INFO: A034 created
(IMP) INFO: import of A034 completed (0 rows)
(DB) INFO: A034~0 created
(DB) INFO: A035 created
(IMP) INFO: import of A035 completed (56 rows)
(DB) INFO: A035~0 created
(DB) INFO: A036 created
(IMP) INFO: import of A036 completed (56 rows)
(DB) INFO: A036~0 created
(DB) INFO: A037 created
(IMP) INFO: import of A037 completed (56 rows)
(DB) INFO: A037~0 created
(DB) INFO: A038 created
(IMP) INFO: import of A038 completed (56 rows)
(DB) INFO: A038~0 created
(DB) INFO: A039 created
(IMP) INFO: import of A039 completed (56 rows)
(DB) INFO: A039~0 created
(DB) INFO: A040 created
(IMP) INFO: import of A040 completed (454 rows)
(DB) INFO: A040~0 created
(DB) INFO: A041 created
(IMP) INFO: import of A041 completed (0 rows)
(DB) INFO: A041~0 created
(DB) INFO: A042 created
(IMP) INFO: import of A042 completed (0 rows)
(DB) INFO: A042~0 created
(DB) INFO: A043 created
(IMP) INFO: import of A043 completed (0 rows)
(DB) INFO: A043~0 created
(DB) INFO: A048 created
(IMP) INFO: import of A048 completed (0 rows)
(DB) INFO: A048~0 created
(DB) INFO: A050 created
(IMP) INFO: import of A050 completed (2 rows)
(DB) INFO: A050~0 created
(DB) INFO: A057 created
(IMP) INFO: import of A057 completed (1364 rows)
(DB) INFO: A057~0 created
(DB) INFO: A066 created
(IMP) INFO: import of A066 completed (4 rows)
(DB) INFO: A066~0 created
(DB) INFO: A067 created
(IMP) INFO: import of A067 completed (1 rows)
(DB) INFO: A067~0 created
(DB) INFO: A068 created
(IMP) INFO: import of A068 completed (0 rows)
(DB) INFO: A068~0 created
(DB) INFO: A069 created
(IMP) INFO: import of A069 completed (0 rows)
(DB) INFO: A069~0 created
(DB) INFO: A070 created
(IMP) INFO: import of A070 completed (0 rows)
(DB) INFO: A070~0 created
(DB) INFO: A071 created
(IMP) INFO: import of A071 completed (70 rows)
(DB) INFO: A071~0 created
(DB) INFO: A072 created
(IMP) INFO: import of A072 completed (0 rows)
(DB) INFO: A072~0 created
(DB) INFO: A073 created
(IMP) INFO: import of A073 completed (159 rows)
(DB) INFO: A073~0 created
(DB) INFO: A074 created
(IMP) INFO: import of A074 completed (0 rows)
(DB) INFO: A074~0 created
(DB) INFO: A075 created
(IMP) INFO: import of A075 completed (0 rows)
(DB) INFO: A075~0 created
(DB) INFO: A076 created
(IMP) INFO: import of A076 completed (0 rows)
(DB) INFO: A076~0 created
(DB) INFO: A077 created
(IMP) INFO: import of A077 completed (0 rows)
(DB) INFO: A077~0 created
(DB) INFO: A078 created
(IMP) INFO: import of A078 completed (10 rows)
(DB) INFO: A078~0 created
(DB) INFO: A079 created
(IMP) INFO: import of A079 completed (84 rows)
(DB) INFO: A079~0 created
(DB) INFO: A080 created
(IMP) INFO: import of A080 completed (0 rows)
(DB) INFO: A080~0 created
(DB) INFO: A081 created
(IMP) INFO: import of A081 completed (1128 rows)
(DB) INFO: A081~0 created
(DB) INFO: A082 created
(IMP) INFO: import of A082 completed (0 rows)
(DB) INFO: A082~0 created
(DB) INFO: A083 created
(IMP) INFO: import of A083 completed (0 rows)
(DB) INFO: A083~0 created
(DB) INFO: A084 created
(IMP) INFO: import of A084 completed (0 rows)
(DB) INFO: A084~0 created
(DB) INFO: A085 created
(IMP) INFO: import of A085 completed (0 rows)
(DB) INFO: A085~0 created
(DB) INFO: A086 created
(IMP) INFO: import of A086 completed (0 rows)
(DB) INFO: A086~0 created
(DB) INFO: A087 created
(IMP) INFO: import of A087 completed (10 rows)
(DB) INFO: A087~0 created
(DB) INFO: A088 created
(IMP) INFO: import of A088 completed (0 rows)
(DB) INFO: A088~0 created
(DB) INFO: A089 created
(IMP) INFO: import of A089 completed (0 rows)
(DB) INFO: A089~0 created
(DB) INFO: A090 created
(IMP) INFO: import of A090 completed (42 rows)
(DB) INFO: A090~0 created
(DB) INFO: A091 created
(IMP) INFO: import of A091 completed (0 rows)
(DB) INFO: A091~0 created
(DB) INFO: A092 created
(IMP) INFO: import of A092 completed (0 rows)
(DB) INFO: A092~0 created
(DB) INFO: A093 created
(IMP) INFO: import of A093 completed (0 rows)
(DB) INFO: A093~0 created
(DB) INFO: A094 created
(IMP) INFO: import of A094 completed (0 rows)
(DB) INFO: A094~0 created
(DB) INFO: A095 created
(IMP) INFO: import of A095 completed (0 rows)
(DB) INFO: A095~0 created
(DB) INFO: A096 created
(IMP) INFO: import of A096 completed (41 rows)
(DB) INFO: A096~0 created
(DB) INFO: A097 created
(IMP) INFO: import of A097 completed (56 rows)
(DB) INFO: A097~0 created
(DB) INFO: A098 created
(IMP) INFO: import of A098 completed (2 rows)
(DB) INFO: A098~0 created
(DB) INFO: A099 created
(IMP) INFO: import of A099 completed (2 rows)
(DB) INFO: A099~0 created
(DB) INFO: A100 created
(IMP) INFO: import of A100 completed (0 rows)
(DB) INFO: A100~0 created
(DB) INFO: A101 created
(IMP) INFO: import of A101 completed (0 rows)
(DB) INFO: A101~0 created
(DB) INFO: A102 created
(IMP) INFO: import of A102 completed (0 rows)
(DB) INFO: A102~0 created
(DB) INFO: A103 created
(IMP) INFO: import of A103 completed (0 rows)
(DB) INFO: A103~0 created
(DB) INFO: A104 created
(IMP) INFO: import of A104 completed (150 rows)
(DB) INFO: A104~0 created
(DB) INFO: A105 created
(IMP) INFO: import of A105 completed (192 rows)
(DB) INFO: A105~0 created
(DB) INFO: A106 created
(IMP) INFO: import of A106 completed (0 rows)
(DB) INFO: A106~0 created
(DB) INFO: A107 created
(IMP) INFO: import of A107 completed (0 rows)
(DB) INFO: A107~0 created
(DB) INFO: A108 created
(IMP) INFO: import of A108 completed (0 rows)
(DB) INFO: A108~0 created
(DB) INFO: A109 created
(IMP) INFO: import of A109 completed (0 rows)
(DB) INFO: A109~0 created
(DB) INFO: A110 created
(IMP) INFO: import of A110 completed (0 rows)
(DB) INFO: A110~0 created
(DB) INFO: A112 created
(IMP) INFO: import of A112 completed (15 rows)
(DB) INFO: A112~0 created
(DB) INFO: A113 created
(IMP) INFO: import of A113 completed (0 rows)
(DB) INFO: A113~0 created
(DB) INFO: A114 created
(IMP) INFO: import of A114 completed (0 rows)
(DB) INFO: A114~0 created
(DB) INFO: A115 created
(IMP) INFO: import of A115 completed (0 rows)
(DB) INFO: A115~0 created
(DB) INFO: A116 created
(IMP) INFO: import of A116 completed (0 rows)
(DB) INFO: A116~0 created
(DB) INFO: A117 created
(IMP) INFO: import of A117 completed (0 rows)
(DB) INFO: A117~0 created
(DB) INFO: A118 created
(IMP) INFO: import of A118 completed (12 rows)
(DB) INFO: A118~0 created
(DB) INFO: A119 created
(IMP) INFO: import of A119 completed (0 rows)
(DB) INFO: A119~0 created
(DB) INFO: A120 created
(IMP) INFO: import of A120 completed (0 rows)
(DB) INFO: A120~0 created
(DB) INFO: A121 created
(IMP) INFO: import of A121 completed (0 rows)
(DB) INFO: A121~0 created
(DB) INFO: A122 created
(IMP) INFO: import of A122 completed (0 rows)
(DB) INFO: A122~0 created
(DB) INFO: A123 created
(IMP) INFO: import of A123 completed (0 rows)
(DB) INFO: A123~0 created
(DB) INFO: A124 created
(IMP) INFO: import of A124 completed (0 rows)
(DB) INFO: A124~0 created
(DB) INFO: A125 created
(IMP) INFO: import of A125 completed (73 rows)
(DB) INFO: A125~0 created
(DB) INFO: A126 created
(IMP) INFO: import of A126 completed (0 rows)
(DB) INFO: A126~0 created
(DB) INFO: A127 created
(IMP) INFO: import of A127 completed (0 rows)
(DB) INFO: A127~0 created
(DB) INFO: A128 created
(IMP) INFO: import of A128 completed (0 rows)
(DB) INFO: A128~0 created
(DB) INFO: A129 created
(IMP) INFO: import of A129 completed (0 rows)
(DB) INFO: A129~0 created
(DB) INFO: A130 created
(IMP) INFO: import of A130 completed (0 rows)
(DB) INFO: A130~0 created
(DB) INFO: A131 created
(IMP) INFO: import of A131 completed (0 rows)
(DB) INFO: A131~0 created
(DB) INFO: A132 created
(IMP) INFO: import of A132 completed (0 rows)
(DB) INFO: A132~0 created
(DB) INFO: A133 created
(IMP) INFO: import of A133 completed (0 rows)
(DB) INFO: A133~0 created
(DB) INFO: A134 created
(IMP) INFO: import of A134 completed (0 rows)
(DB) INFO: A134~0 created
(DB) INFO: A135 created
(IMP) INFO: import of A135 completed (0 rows)
(DB) INFO: A135~0 created
(DB) INFO: A136 created
(IMP) INFO: import of A136 completed (8 rows)
(DB) INFO: A136~0 created
(DB) INFO: A137 created
(IMP) INFO: import of A137 completed (0 rows)
(DB) INFO: A137~0 created
(DB) INFO: A138 created
(IMP) INFO: import of A138 completed (0 rows)
(DB) INFO: A138~0 created
(DB) INFO: A139 created
(IMP) INFO: import of A139 completed (0 rows)
(DB) INFO: A139~0 created
(DB) INFO: A140 created
(IMP) INFO: import of A140 completed (2 rows)
(DB) INFO: A140~0 created
(DB) INFO: A141 created
(IMP) INFO: import of A141 completed (0 rows)
(DB) INFO: A141~0 created
(DB) INFO: A142 created
(IMP) INFO: import of A142 completed (0 rows)
(DB) INFO: A142~0 created
(DB) INFO: A143 created
(IMP) INFO: import of A143 completed (0 rows)
(DB) INFO: A143~0 created
(DB) INFO: A144 created
(IMP) INFO: import of A144 completed (0 rows)
(DB) INFO: A144~0 created
(DB) INFO: A145 created
(IMP) INFO: import of A145 completed (0 rows)
(DB) INFO: A145~0 created
(DB) INFO: A146 created
(IMP) INFO: import of A146 completed (0 rows)
(DB) INFO: A146~0 created
(DB) INFO: A147 created
(IMP) INFO: import of A147 completed (0 rows)
(DB) INFO: A147~0 created
(DB) INFO: A148 created
(IMP) INFO: import of A148 completed (0 rows)
(DB) INFO: A148~0 created
(DB) INFO: A149 created
(IMP) INFO: import of A149 completed (0 rows)
(DB) INFO: A149~0 created
(DB) INFO: A152 created
(IMP) INFO: import of A152 completed (0 rows)
(DB) INFO: A152~0 created
(DB) INFO: A153 created
(IMP) INFO: import of A153 completed (0 rows)
(DB) INFO: A153~0 created
(DB) INFO: A154 created
(IMP) INFO: import of A154 completed (0 rows)
(DB) INFO: A154~0 created
(DB) INFO: A155 created
(IMP) INFO: import of A155 completed (0 rows)
(DB) INFO: A155~0 created
(DB) INFO: A156 created
(IMP) INFO: import of A156 completed (0 rows)
(DB) INFO: A156~0 created
(DB) INFO: A160 created
(IMP) INFO: import of A160 completed (7 rows)
(DB) INFO: A160~0 created
(DB) INFO: A161 created
(IMP) INFO: import of A161 completed (0 rows)
(DB) INFO: A161~0 created
(DB) INFO: A162 created
(IMP) INFO: import of A162 completed (0 rows)
(DB) INFO: A162~0 created
(DB) INFO: A173 created
(IMP) INFO: import of A173 completed (0 rows)
(DB) INFO: A173~0 created
(DB) INFO: A174 created
(IMP) INFO: import of A174 completed (0 rows)
(DB) INFO: A174~0 created
(DB) INFO: A175 created
(IMP) INFO: import of A175 completed (0 rows)
(DB) INFO: A175~0 created
(DB) INFO: A176 created
(IMP) INFO: import of A176 completed (0 rows)
(DB) INFO: A176~0 created
(DB) INFO: A177 created
(IMP) INFO: import of A177 completed (0 rows)
(DB) INFO: A177~0 created
(DB) INFO: A178 created
(IMP) INFO: import of A178 completed (0 rows)
(DB) INFO: A178~0 created
(DB) INFO: A179 created
(IMP) INFO: import of A179 completed (0 rows)
(DB) INFO: A179~0 created
(DB) INFO: A180 created
(IMP) INFO: import of A180 completed (0 rows)
(DB) INFO: A180~0 created
(DB) INFO: A185 created
(IMP) INFO: import of A185 completed (0 rows)
(DB) INFO: A185~0 created
(DB) INFO: A190 created
(IMP) INFO: import of A190 completed (0 rows)
(DB) INFO: A190~0 created
(DB) INFO: A191 created
(IMP) INFO: import of A191 completed (0 rows)
(DB) INFO: A191~0 created
(DB) INFO: A192 created
(IMP) INFO: import of A192 completed (0 rows)
(DB) INFO: A192~0 created
(DB) INFO: A193 created
(IMP) INFO: import of A193 completed (0 rows)
(DB) INFO: A193~0 created
(DB) INFO: A194 created
(IMP) INFO: import of A194 completed (0 rows)
(DB) INFO: A194~0 created
(DB) INFO: A195 created
(IMP) INFO: import of A195 completed (13 rows)
(DB) INFO: A195~0 created
(DB) INFO: A196 created
(IMP) INFO: import of A196 completed (0 rows)
(DB) INFO: A196~0 created
(DB) INFO: A197 created
(IMP) INFO: import of A197 completed (5 rows)
(DB) INFO: A197~0 created
(DB) INFO: A198 created
(IMP) INFO: import of A198 completed (0 rows)
(DB) INFO: A198~0 created
(DB) INFO: A215 created
(IMP) INFO: import of A215 completed (0 rows)
(DB) INFO: A215~0 created
(DB) INFO: A291 created
(IMP) INFO: import of A291 completed (0 rows)
(DB) INFO: A291~0 created
(DB) INFO: A292 created
(IMP) INFO: import of A292 completed (0 rows)
(DB) INFO: A292~0 created
(DB) INFO: A293 created
(IMP) INFO: import of A293 completed (0 rows)
(DB) INFO: A293~0 created
(DB) INFO: A300 created
(IMP) INFO: import of A300 completed (0 rows)
(DB) INFO: A300~0 created
(DB) INFO: A301 created
(IMP) INFO: import of A301 completed (0 rows)
(DB) INFO: A301~0 created
(DB) INFO: A304 created
(IMP) INFO: import of A304 completed (3414 rows)
(DB) INFO: A304~0 created
(DB) INFO: A305 created
(IMP) INFO: import of A305 completed (54 rows)
(DB) INFO: A305~0 created
(DB) INFO: A306 created
(IMP) INFO: import of A306 completed (0 rows)
(DB) INFO: A306~0 created
(DB) INFO: A307 created
(IMP) INFO: import of A307 completed (0 rows)
(DB) INFO: A307~0 created
(DB) INFO: A310 created
(IMP) INFO: import of A310 completed (0 rows)
(DB) INFO: A310~0 created
(DB) INFO: A311 created
(IMP) INFO: import of A311 completed (0 rows)
(DB) INFO: A311~0 created
(DB) INFO: A312 created
(IMP) INFO: import of A312 completed (0 rows)
(DB) INFO: A312~0 created
(DB) INFO: A315 created
(IMP) INFO: import of A315 completed (0 rows)
(DB) INFO: A315~0 created
(DB) INFO: A316 created
(IMP) INFO: import of A316 completed (0 rows)
(DB) INFO: A316~0 created
(DB) INFO: A317 created
(IMP) INFO: import of A317 completed (0 rows)
(DB) INFO: A317~0 created
(DB) INFO: A320 created
(IMP) INFO: import of A320 completed (0 rows)
(DB) INFO: A320~0 created
(DB) INFO: A321 created
(IMP) INFO: import of A321 completed (0 rows)
(DB) INFO: A321~0 created
(DB) INFO: A325 created
(IMP) INFO: import of A325 completed (0 rows)
(DB) INFO: A325~0 created
(DB) INFO: A326 created
(IMP) INFO: import of A326 completed (0 rows)
(DB) INFO: A326~0 created
(DB) INFO: A330 created
(IMP) INFO: import of A330 completed (0 rows)
(DB) INFO: A330~0 created
(DB) INFO: A331 created
(IMP) INFO: import of A331 completed (0 rows)
(DB) INFO: A331~0 created
(DB) INFO: A335 created
(IMP) INFO: import of A335 completed (0 rows)
(DB) INFO: A335~0 created
(DB) INFO: A336 created
(IMP) INFO: import of A336 completed (0 rows)
(DB) INFO: A336~0 created
(DB) INFO: A340 created
(IMP) INFO: import of A340 completed (0 rows)
(DB) INFO: A340~0 created
(DB) INFO: A341 created
(IMP) INFO: import of A341 completed (0 rows)
(DB) INFO: A341~0 created
(DB) INFO: A342 created
(IMP) INFO: import of A342 completed (0 rows)
(DB) INFO: A342~0 created
(DB) INFO: A343 created
(IMP) INFO: import of A343 completed (0 rows)
(DB) INFO: A343~0 created
(DB) INFO: A344 created
(IMP) INFO: import of A344 completed (0 rows)
(DB) INFO: A344~0 created
(DB) INFO: A345 created
(IMP) INFO: import of A345 completed (0 rows)
(DB) INFO: A345~0 created
(DB) INFO: A346 created
(IMP) INFO: import of A346 completed (0 rows)
(DB) INFO: A346~0 created
(DB) INFO: A347 created
(IMP) INFO: import of A347 completed (0 rows)
(DB) INFO: A347~0 created
(DB) INFO: A348 created
(IMP) INFO: import of A348 completed (0 rows)
(DB) INFO: A348~0 created
(DB) INFO: A349 created
(IMP) INFO: import of A349 completed (0 rows)
(DB) INFO: A349~0 created
(DB) INFO: A350 created
(IMP) INFO: import of A350 completed (0 rows)
(DB) INFO: A350~0 created
(DB) INFO: A352 created
(IMP) INFO: import of A352 completed (0 rows)
(DB) INFO: A352~0 created
(DB) INFO: A353 created
(IMP) INFO: import of A353 completed (0 rows)
(DB) INFO: A353~0 created
(DB) INFO: A354 created
(IMP) INFO: import of A354 completed (0 rows)
(DB) INFO: A354~0 created
(DB) INFO: A355 created
(IMP) INFO: import of A355 completed (0 rows)
(DB) INFO: A355~0 created
(DB) INFO: A356 created
(IMP) INFO: import of A356 completed (0 rows)
(DB) INFO: A356~0 created
(DB) INFO: A357 created
(IMP) INFO: import of A357 completed (0 rows)
(DB) INFO: A357~0 created
(DB) INFO: A358 created
(IMP) INFO: import of A358 completed (0 rows)
(DB) INFO: A358~0 created
(DB) INFO: A359 created
(IMP) INFO: import of A359 completed (0 rows)
(DB) INFO: A359~0 created
(DB) INFO: A362 created
(IMP) INFO: import of A362 completed (0 rows)
(DB) INFO: A362~0 created
(DB) INFO: A363 created
(IMP) INFO: import of A363 completed (0 rows)
(DB) INFO: A363~0 created
(DB) INFO: A364 created
(IMP) INFO: import of A364 completed (0 rows)
(DB) INFO: A364~0 created
(DB) INFO: A365 created
(IMP) INFO: import of A365 completed (0 rows)
(DB) INFO: A365~0 created
(DB) INFO: A366 created
(IMP) INFO: import of A366 completed (0 rows)
(DB) INFO: A366~0 created
(DB) INFO: A367 created
(IMP) INFO: import of A367 completed (0 rows)
(DB) INFO: A367~0 created
(DB) INFO: A368 created
(IMP) INFO: import of A368 completed (0 rows)
(DB) INFO: A368~0 created
(DB) INFO: A369 created
(IMP) INFO: import of A369 completed (0 rows)
(DB) INFO: A369~0 created
(DB) INFO: A371 created
(IMP) INFO: import of A371 completed (0 rows)
(DB) INFO: A371~0 created
(DB) INFO: A372 created
(IMP) INFO: import of A372 completed (0 rows)
(DB) INFO: A372~0 created
(DB) INFO: A373 created
(IMP) INFO: import of A373 completed (0 rows)
(DB) INFO: A373~0 created
(DB) INFO: A374 created
(IMP) INFO: import of A374 completed (0 rows)
(DB) INFO: A374~0 created
(DB) INFO: A375 created
(IMP) INFO: import of A375 completed (0 rows)
(DB) INFO: A375~0 created
(DB) INFO: A376 created
(IMP) INFO: import of A376 completed (0 rows)
(DB) INFO: A376~0 created
(DB) INFO: A382 created
(IMP) INFO: import of A382 completed (0 rows)
(DB) INFO: A382~0 created
(DB) INFO: A390 created
(IMP) INFO: import of A390 completed (4 rows)
(DB) INFO: A390~0 created
(DB) INFO: A392 created
(IMP) INFO: import of A392 completed (0 rows)
(DB) INFO: A392~0 created
(DB) INFO: A393 created
(IMP) INFO: import of A393 completed (0 rows)
(DB) INFO: A393~0 created
(DB) INFO: A394 created
(IMP) INFO: import of A394 completed (0 rows)
(DB) INFO: A394~0 created
(DB) INFO: A395 created
(IMP) INFO: import of A395 completed (5 rows)
(DB) INFO: A395~0 created
(DB) INFO: A396 created
(IMP) INFO: import of A396 completed (0 rows)
(DB) INFO: A396~0 created
(DB) INFO: A397 created
(IMP) INFO: import of A397 completed (0 rows)
(DB) INFO: A397~0 created
(DB) INFO: A399 created
(IMP) INFO: import of A399 completed (0 rows)
(DB) INFO: A399~0 created
(DB) INFO: A441 created
(IMP) INFO: import of A441 completed (0 rows)
(DB) INFO: A441~0 created
(DB) INFO: A502 created
(IMP) INFO: import of A502 completed (58 rows)
(DB) INFO: A502~0 created
(DB) INFO: A503 created
(IMP) INFO: import of A503 completed (7 rows)
(DB) INFO: A503~0 created
(DB) INFO: A504 created
(IMP) INFO: import of A504 completed (4 rows)
(DB) INFO: A504~0 created
(DB) INFO: A506 created
(IMP) INFO: import of A506 completed (10 rows)
(DB) INFO: A506~0 created
(DB) INFO: A507 created
(IMP) INFO: import of A507 completed (0 rows)
(DB) INFO: A507~0 created
(DB) INFO: A510 created
(IMP) INFO: import of A510 completed (0 rows)
(DB) INFO: A510~0 created
(DB) INFO: A511 created
(IMP) INFO: import of A511 completed (0 rows)
(DB) INFO: A511~0 created
(DB) INFO: A518 created
(IMP) INFO: import of A518 completed (0 rows)
(DB) INFO: A518~0 created
(DB) INFO: A599 created
(IMP) INFO: import of A599 completed (0 rows)
(DB) INFO: A599~0 created
(DB) INFO: A601 created
(IMP) INFO: import of A601 completed (3 rows)
(DB) INFO: A601~0 created
(DB) INFO: A755 created
(IMP) INFO: import of A755 completed (0 rows)
(DB) INFO: A755~0 created
(DB) INFO: A800 created
(IMP) INFO: import of A800 completed (1 rows)
(DB) INFO: A800~0 created
(DB) INFO: A801 created
(IMP) INFO: import of A801 completed (0 rows)
(DB) INFO: A801~0 created
(DB) INFO: A805 created
(IMP) INFO: import of A805 completed (0 rows)
(DB) INFO: A805~0 created
(DB) INFO: A810 created
(IMP) INFO: import of A810 completed (0 rows)
(DB) INFO: A810~0 created
(DB) INFO: A815 created
(IMP) INFO: import of A815 completed (0 rows)
(DB) INFO: A815~0 created
(DB) INFO: A816 created
(IMP) INFO: import of A816 completed (1 rows)
(DB) INFO: A816~0 created
(DB) INFO: A817 created
(IMP) INFO: import of A817 completed (0 rows)
(DB) INFO: A817~0 created
(DB) INFO: A818 created
(IMP) INFO: import of A818 completed (6 rows)
(DB) INFO: A818~0 created
(DB) INFO: A819 created
(IMP) INFO: import of A819 completed (0 rows)
(DB) INFO: A819~0 created
(DB) INFO: A900 created
(IMP) INFO: import of A900 completed (250 rows)
(DB) INFO: A900~0 created
(DB) INFO: A902 created
(IMP) INFO: import of A902 completed (0 rows)
(DB) INFO: A902~0 created
(DB) INFO: A903 created
(IMP) INFO: import of A903 completed (11 rows)
(DB) INFO: A903~0 created
(DB) INFO: A933 created
(IMP) INFO: import of A933 completed (0 rows)
(DB) INFO: A933~0 created
(DB) INFO: A940 created
(IMP) INFO: import of A940 completed (0 rows)
(DB) INFO: A940~0 created
(DB) INFO: A941 created
(IMP) INFO: import of A941 completed (0 rows)
(DB) INFO: A941~0 created
(DB) INFO: A942 created
(IMP) INFO: import of A942 completed (0 rows)
(DB) INFO: A942~0 created
(DB) INFO: A972 created
(IMP) INFO: import of A972 completed (0 rows)
(DB) INFO: A972~0 created
(DB) INFO: A973 created
(IMP) INFO: import of A973 completed (0 rows)
(DB) INFO: A973~0 created
(DB) INFO: A974 created
(IMP) INFO: import of A974 completed (0 rows)
(DB) INFO: A974~0 created
(DB) INFO: A976 created
(IMP) INFO: import of A976 completed (0 rows)
(DB) INFO: A976~0 created
(DB) INFO: A977 created
(IMP) INFO: import of A977 completed (0 rows)
(DB) INFO: A977~0 created
(DB) INFO: A994 created
(IMP) INFO: import of A994 completed (0 rows)
(DB) INFO: A994~0 created
(DB) INFO: A997 created
(IMP) INFO: import of A997 completed (0 rows)
(DB) INFO: A997~0 created
(DB) INFO: A998 created
(IMP) INFO: import of A998 completed (1 rows)
(DB) INFO: A998~0 created
(DB) INFO: A999 created
(IMP) INFO: import of A999 completed (0 rows)
(DB) INFO: A999~0 created
(DB) INFO: AAA_KEYS created
(IMP) INFO: import of AAA_KEYS completed (0 rows)
(DB) INFO: AAA_KEYS~0 created
(DB) INFO: AAA_ROLES created
(IMP) INFO: import of AAA_ROLES completed (0 rows)
(DB) INFO: AAA_ROLES~0 created
(DB) INFO: AAA_ROLES2 created
(IMP) INFO: import of AAA_ROLES2 completed (0 rows)
(DB) INFO: AAA_ROLES2~0 created
(DB) INFO: AAA_USERS created
(IMP) INFO: import of AAA_USERS completed (0 rows)
(DB) INFO: AAA_USERS~0 created
(DB) INFO: AAA_VALUES created
(IMP) INFO: import of AAA_VALUES completed (0 rows)
(DB) INFO: AAA_VALUES~0 created
(DB) INFO: AAB_ID_ACT created
(IMP) INFO: import of AAB_ID_ACT completed (0 rows)
(DB) INFO: AAB_ID_ACT~0 created
(DB) INFO: AAB_VAR_ID created
(IMP) INFO: import of AAB_VAR_ID completed (6 rows)
(DB) INFO: AAB_VAR_ID~0 created
(DB) INFO: AAB_VAR_ID~ID1 created
(DB) INFO: AAB_VAR_PROP created
(IMP) INFO: import of AAB_VAR_PROP completed (9 rows)
(DB) INFO: AAB_VAR_PROP~0 created
(DB) INFO: AAB_VAR_PROPT created
(IMP) INFO: import of AAB_VAR_PROPT completed (18 rows)
(DB) INFO: AAB_VAR_PROPT~0 created
(DB) INFO: AAF_ROLES created
(IMP) INFO: import of AAF_ROLES completed (0 rows)
(DB) INFO: AAF_ROLES~0 created
(DB) INFO: AAT_ROLES created
(IMP) INFO: import of AAT_ROLES completed (0 rows)
(DB) INFO: AAT_ROLES~0 created
(DB) INFO: AAT_USERS created
(IMP) INFO: import of AAT_USERS completed (0 rows)
(DB) INFO: AAT_USERS~0 created
(DB) INFO: AAT_VALUES created
(IMP) INFO: import of AAT_VALUES completed (0 rows)
(DB) INFO: AAT_VALUES~0 created
(DB) INFO: AAUSVAR created
(IMP) INFO: import of AAUSVAR completed (0 rows)
(DB) INFO: AAUSVAR~0 created
(DB) INFO: ABAPHTML created
(IMP) INFO: import of ABAPHTML completed (859 rows)
(DB) INFO: ABAPHTML~0 created
(DB) INFO: ABAPTREE created
(IMP) INFO: import of ABAPTREE completed (487 rows)
(DB) INFO: ABAPTREE~0 created
(DB) INFO: ABAPTREET created
(IMP) INFO: import of ABAPTREET completed (7814 rows)
(DB) INFO: ABAPTREET~0 created
(DB) INFO: ABDOCMODE created
(IMP) INFO: import of ABDOCMODE completed (78 rows)
(DB) INFO: ABDOCMODE~0 created
(DB) INFO: ACAC_OBJECTS created
(IMP) INFO: import of ACAC_OBJECTS completed (0 rows)
(DB) INFO: ACAC_OBJECTS~0 created
(DB) INFO: ACAC_OBJECTS~1 created
(DB) INFO: ACCRBD created
(IMP) INFO: import of ACCRBD completed (0 rows)
(DB) INFO: ACCRBD~0 created
(DB) INFO: ACCRBD~1 created
(DB) INFO: ACCRFI created
(IMP) INFO: import of ACCRFI completed (0 rows)
(DB) INFO: ACCRFI~0 created
(DB) INFO: ACEDSASSGMT created
(IMP) INFO: import of ACEDSASSGMT completed (0 rows)
(DB) INFO: ACEDSASSGMT~0 created
(DB) INFO: ACEDSOH created
(IMP) INFO: import of ACEDSOH completed (0 rows)
(DB) INFO: ACEDSOH~0 created
(DB) INFO: ACEDSOI created
(IMP) INFO: import of ACEDSOI completed (0 rows)
(DB) INFO: ACEDSOI~0 created
(DB) INFO: ACEDSOP created
(IMP) INFO: import of ACEDSOP completed (0 rows)
(DB) INFO: ACEDSOP~0 created
(DB) INFO: ACEOBJ created
(IMP) INFO: import of ACEOBJ completed (0 rows)
(DB) INFO: ACEOBJ~0 created
(DB) INFO: ACEOBJ~001 created
(DB) INFO: ACE_SOP_DESTINTN created
(IMP) INFO: import of ACE_SOP_DESTINTN completed (0 rows)
(DB) INFO: ACE_SOP_DESTINTN~0 created
(DB) INFO: ACE_SOP_FFVERSNS created
(IMP) INFO: import of ACE_SOP_FFVERSNS completed (1 rows)
(DB) INFO: ACE_SOP_FFVERSNS~0 created
(DB) INFO: ACE_SOP_FFVRSTXT created
(IMP) INFO: import of ACE_SOP_FFVRSTXT completed (18 rows)
(DB) INFO: ACE_SOP_FFVRSTXT~0 created
(DB) INFO: ACE_SOP_INVERSNS created
(IMP) INFO: import of ACE_SOP_INVERSNS completed (0 rows)
(DB) INFO: ACE_SOP_INVERSNS~0 created
(DB) INFO: ACE_SOP_INVRSTXT created
(IMP) INFO: import of ACE_SOP_INVRSTXT completed (0 rows)
(DB) INFO: ACE_SOP_INVRSTXT~0 created
(DB) INFO: ACE_SOP_REFKEY created
(IMP) INFO: import of ACE_SOP_REFKEY completed (0

Java system copy with EP6.0 SP9 ora/unix to mss/win

Hi,
any document how to do java system copy ep6.0 SP (oracle/unix) to mss/window.
Thanks for your help.
Thanks & regards
pushpa

A system copy tool is not yet available. There is some work going on about this and may appear later.
What you can do is backing up and do it that way. See the "Technical Operatrions Manual"
Regards,
Benny

Hom System Copy- Error running J2ee migration tool kit

Good Day Guys,
Im performing homogenous system copy.I have encountered below error:
INFO 2008-10-20 13:05:33
Output of C:\j2sdk1.4.2_18-x64\bin\java.exe -classpath D:/usr/sap/LE1/SYS/global/sltools/sharedlib/launcher .jar;. com.sap.engine.offline.OfflineToolStart com.sap.sdt.jmt.migrationtool.MigrationToolImport D:/usr/sap/LE1/SYS/global/sltools/jmt;D:/usr/sap/LE1 /SYS/global/sltools/sharedlib import.switch resume downtime mti.properties is written to the logfile C:/Program Files/sapinst_instdir/ERP/LM/COPY/MSS/SYSTEM/CENTRA L/AS/runJmt.log.
WARNING 2008-10-20 13:05:34
Execution of the command "C:\j2sdk1.4.2_18-x64\bin\java.exe -classpath D:/usr/sap/LE1/SYS/global/sltools/sharedlib/launcher .jar;. com.sap.engine.offline.OfflineToolStart com.sap.sdt.jmt.migrationtool.MigrationToolImport D:/usr/sap/LE1/SYS/global/sltools/jmt;D:/usr/sap/LE1 /SYS/global/sltools/sharedlib import.switch resume downtime mti.properties" finished with return code 27. Output:
ERROR 2008-10-20 13:05:34
CJS-20068 Error when running the J2EE Migration Toolkit. SOLUTION: See output of logfile C:\Program Files/sapinst_instdir/ERP/LM/COPY/MSS/SYSTEM/CENTRA L/AS//runJmt.log: ''.
ERROR 2008-10-20 13:05:34
CJS-20068 Error when running the J2EE Migration Toolkit. SOLUTION: See output of logfile C:\Program Files/sapinst_instdir/ERP/LM/COPY/MSS/SYSTEM/CENTRA L/AS//runJmt.log: ''.
ERROR 2008-10-20 13:05:34
FCO-00011 The step RunMigrationController with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_One host_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind |ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|in d| ind|ind|ind|4|0|NW_RUN_MIGRATION_CONTROLLER|ind|ind |ind|ind|2|0|RunMigrationController was executed with status ERROR .
INFO 2008-10-20 13:06:29
An error occured and the user decide to stop.\n Current step "|NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_On ehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|in d|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|i nd|ind|ind|ind|4|0|NW_RUN_MIGRATION_CONTROLLER|ind |ind|ind|ind|2|0|RunMigrationController".
I have checked the runjmt.log its empty.
I did find a note 966752.but couldnt solve the problem.Another thing do we need to have same version of j2sdk,mine are different on source(ia64) and target(x64).
Please advice.
BasisNerd

CAn you precise also what Migration tool are you using?
Migration from 5.1 to SAP BPC 7.0 NW?
In that case when you are speaking about the installation about what part are you speaking?
I think actually you are speaking about the migration tool from 4.2 to 7.0 Microsoft version .
In that case you can install the mIgration tool just with SAP BPC sys admin users and you have to input the password for that user. Sys admin user for BPC is usually the user used for installation of SAP BPC server.
Any way I suggest to follow the Migration tool training document and there you will find all the information necessary.
Regards
Sorin Radulescu

ABAP+JAVA system copy using 3rd party export/import tools

Hi all,
I am trying to do a homogenous system copy. I am following the syscopy guide for SAP NW 7.0 SR3 ABAP+JAVA systems
We are running AIX 5.L and Oracle.
My question is this. We are using an IBM XiV system for our disk storage, and we are able to restore from "snaps" which is their version of images. Does anyone know if it is possible to restore or "import" the data in a system copy using an outside tool like this? If so, do you have any information on how to?
I know it is possible to restore the database from an offline backup using BRTools rather than r3load and jload, and I just wanted to see if I can restore from a snap as it would save a lot of time in the procedure.
Any help or ideas would be much appreciated.
Thanks!

>My question is this. We are using an IBM XiV system for our disk storage, and we are able to restore from "snaps" which is their version of images. Does anyone know if it is possible to restore or "import" the data in a system copy using an outside tool like this? If so, do you have any information on how to?
That approach is not supported.
The reason is: combined instances write the instance name and hostname in various places, on the filesystem in .properties files, in the JDBC configuration, depending on the java applications you run on top in various other places. What you're trying to do is effectively "renaming" an instance.
Technically it's possible to do it and to get it run, yes, but the supported way is running sapinst and choose ABAP + Java system copy. This will prevent you from lots of (not really documented) manual work after the copy.
Markus

Homgeneous System Copy with Java and DB2 with database tools.

Hello,
we have an single java stack (netweaver 2004s) and tried a system copy with database tools.
Source System: DP2, dp2adm, db2dp2, sapdp2db
Target System: SP2, sp2adm, db2sp2, ???
We followed the documentation "System copy for SAP systems based on sap netweaver 2004s SR1 JAVA. We exported the SDM on the source system made a redirected restore with db tools and tried to install a new target system.
During the import in the target system using sapinst we get in the
phase run java migration tool kit the following error message.
Caused by:
com.sap.engine.frame.core.configuration.ConfigurationException: Error
while connecting to DB.
at
com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.(ConfigurationManagerBootstrapImpl.java:49)
... 14 more
Caused by: com.ibm.db2.jcc.a.SqlException: Connection authorization
failure occurred. Reason: userid revoked.
What I didn't understand is, that in the documenation it is mentioned, that you have to use the same java database connect user. But during the installation of the target system (SP2) I cannot change the java database connect user to sapdp2db. I'm only allow to enter sapsp2db. That might then cause the connection problem.
Regards
Alexander Türk
I

Hi Alexander
yes , give it a try , but see note
970518 Hom./Het.System Copy SAP NetWeaver 2004s SR2
and all other related notes , if it matches your environment .
Best regards
dirk

Basis work for SAP system copy using DB2 cloning tool

My company is using the DB2 cloning tool, formerly from MainStar. Our DBAs have used this tool to create a clone of a technical sandbox (ST1) to another DB2 instance (SZ1).
I am reading through the System Copy for SAP Systems Based on SAP NetWeaver 2004s SR2 ABAP+Java guide and trying to follow the steps.
As information, our application servers are currently running on zLinux and I am trying to do a system copy of an HA ABAP+Java SID.
Since we have used the cloning tool, which I would equate to a homogeneous system copy using database specific tools, the guide looks like it says I can skip the Export Preparation and Table Splitting Preparation steps. The only other step for the source system is the Database and Central Instance Export.
When I execute this step, it creates a dump of the database. This seems useless as we already have a cloned copy of the database.
Does anyone have the list of Basis tasks for a system copy when the DB2 cloning tool is used?
Brian

Nevermind. If someone sets:
rdisp/j2ee_start = 0
in an ABAP+Java system, sapinst behaves strangely during the system export and does not give the option to only dump the filesystem. Bug?
Brian

Db2 homogenous system copy using DB specific tools.

Hi,
I'm currently doing a homogenous system copy using db specific tools option (DB2). I did an offline backup of the source system using db2 backup database command, then ran SAPinst (NW70SR2) on the source system to go through the export phase, no problem. On the destination system, I ran SAPinst (NW70SR3) to do the import phase and reached a point where SAPinst asked me to restore the database using db2 tools. I running command:
RESTORE DATABASE <SID> FROM "E:\backup_folder" TAKEN AT 20090617164332 TO "Q:" INTO <SID> NEWLOGPATH "F:\" WITH 2 BUFFERS BUFFER 1024 PARALLELISM 1 WITHOUT PROMPTING;
After running this command I get SQL0902C A system error (reason code = "") occurred. Subsequent
SQL statements cannot be processed.
sqlcode: -902
sqlstate: 58005
Some background information: I'm running this procedure to do a migrate the database from a 32 bit to 64 bit.
Am I doing something wrong? Do I need to run any other commands or prep on the detination system before running the restore command?

One other thing you might have wanted to check was the physical memory on the target machine. Does the target have the same amount of memory as the source? If it is much smaller, sometimes there can be issues with starting up the database on the smaller machine. There is an instance level registry setting you can use to reduce the amount of bufferpool memory the database wants to use.
Another issue I have seen is that you may want to restore a 32-bit backup to a 32-bit instance. You can then upgrade then instance and database to 64-bit.
EDIT: Sorry, I didn't realize this thread was 2 months old.
Edited by: Derek Barrett on Aug 18, 2009 4:39 AM

Homogeneous system copy using database specific tools

My enviroment is ECC6/Oracle 10.2.0.2/Solaris 10
I'm attempting my first system copy (central instance ABAP) using database specific tools from my PRD to my QAS system
in the source system I ran sapinst and proceed as follows
Execution of Service SAP ERP 6.0 SR3 > Software Life-cycle options > system copy > oracle > source system export >
central system > based on AS ABAP ? Database Instance Export
The export creates two folders and an file ie ABAP, JAVA & LABELIDX.
The folder ABAP is empty while JAVA has three files.see details below. I have a feeling something is not right ?
Kindly advice before I proceed with database offline backup and importation in the target system
*/oracle/INSTDIR/MIGRATION-CD/SYSCOPY*
*root@PRD#*
*root@PRD#*
*root@PRD#ls -l*
*total 6*
*drwxrwxr-x   2 root     sapinst      512 Jul 12 13:19 ABAP*
*drwxrwxr-x   2 root     sapinst      512 Jul 12 13:19 JAVA*
*-rw-rw-r--   1 root     sapinst       10 Jul 12 13:19 LABELIDX.ASC*
*root@PRD#*
*root@PRD#cd ABAP*
*root@PRD#ls -l*
*total 0*
*root@PRD#*
*root@PRD#cd ../JAVA*
*root@PRD#pwd*
*/oracle/INSTDIR/MIGRATION-CD/SYSCOPY/JAVA*
*root@PRD#ls -l*
*total 6*
*-rw-rw-r--   1 root     sapinst       19 Jul 12 13:19 LABEL.ASC*
-rw-r-----   1 root     sapinst       14 Jul 12 13:19 LABELIDX.ASC
-rw-r-----   1 root     sapinst      168 Jul 12 13:19 SOURCE.PROPERTIES
root@PRD#
root@PRD#
According to the system copy documents I've gone through I expect to see the following
in the export directory
=> structure with label files and source system information
=> database structure files (*.STR) for ABAP database objects
=> database statistics
=> Size calculation for the target database (*.EXT, DBSIZE.XML)
=> Archiving of the SDM
=> Archiving of application specific file system content
I get a dialog box message that the export has completed successfullu but only two phases were done ie
=> NW_export
=> Prepare To export Java

Thanks Mark
I'll proceed with the import & inform you about the outcome
My QAS system is the transport domain controller i.e. it hosts the transport directory /usr/sap/trans
What happens to pending transports after system copy ? Is there a way I can retain them or do I have to advice my users to complete pending requests so that I can import all of them before proceeding .
what happens to the CUA configurations in my 3 tier system landscape after I overwrite QAS ? I will make a note of all the RFC's & thier configuration details just incase I need to recreate them
Regards

PI 7.11 sp6 system copy causes target sys to register with source

Experts,
We have a PI 7.1 (EHP1, sp6) PI system based on AIX 6.1 OS and Oracle 11g.
I recently did the standard PI system copy from a prod source (PIP) to a training target (PIT).
I used the most recenty PI system copy guide that is specific for PI 7.1 EHP1
I did not run into any major problems doing the steps of the itself.
I did the usual "post" steps, documented in the guide that really are done on any NW system.
Then I got into the specific "PI" post steps and that's where I now have a problem.
I could not run the "wizard for post copy" since I'm on 7.11sp6. Yes, I know they "downported" it but I don't have those latest LMtools type packages. Anyway, I'm OK with that.
I followed all the steps, fixing my RFCs, JCos, Destinations, cleaning up SLD, SLDAPICUST, creating new business systems...etc.
My big problem is with the exchange profile. Yes, it's easy to change all the SIDs and hostnames using the search tool for all the parameters in the exchange profile, but the one I COULD NOT CHANGE was the "ABAP Connection". In there right after the copy was the hostname of the prod system, the client, and the user PILDUSER. I attempted to put the hostname of my target (PIT) system, but I would get the error:
RFC 399 unable to connect
I'm certain the user is NOT locked and the password is correct for PILDUSER.
Worse yet, If I left the hostname in there that was set to "prod", then when I changed all the other values in the "parameters" section of the XI profile, then it actually changed my PROD system!!
If I keep the ABAP connection to PIT, then the entire exchange profile disappears for PIT.
Also, now my PROD system shows the PIT system as a "non-central adapter engine".
Ughh! I'm totally stuck. I'm not sure what to do.
It's as if the PIT (PI training) system somehow is linked to PIP (PI prod). It's like PIT doesn't think he is his own box...
Any ideas? I'm resisting opening a message because this will be so hard to explain to sap support.
--NICK

Hi Nick,
We went thru the same issue. Fortunately, it was between Dev to sandbox. I stopped the dev system and changed the exchange profile parameters to sandbox hostname and brought the Dev up to fix the issue.
Prod showing as Non-Central Adapter engine :- Check your Business System in SLD and In CIM Instances in SLD, check your XI Integration server assigned to right Business System.
Note 764176 - Error in XI due to inconsistent SLD contents :- helped me come over PI post step issues.
Thanks,
Arjun

PI 7.11 sp6 system copy Exchange Profile error code: 399

Experts,
We have a PI 7.1 (EHP1, sp6) PI system based on AIX 6.1 OS and Oracle 11g.
I recently did the standard PI system copy from a prod source (PIP) to a training target (PIT).
I used the most recenty PI system copy guide that is specific for PI 7.1 EHP1
I did not run into any major problems doing the steps of the copy itself.
I did the usual "post" steps, documented in the guide that really are done on any NW system.
Then I got into the specific "PI" post steps and that's where I now have a problem.
I followed all the steps, fixing my RFCs, JCos, Destinations, cleaning up SLD, SLDAPICUST, creating new business systems...etc.
My big problem is with the exchange profile. Yes, it's easy to change all the SIDs and hostnames using the search tool for all the parameters in the exchange profile, but the one I COULD NOT CHANGE was the "ABAP Connection". In there right after the copy was the hostname of the prod system, the client, and the user PILDUSER. I attempted to put the hostname of my target (PIT) system, but I would get the error:
com.sap.rprof.dbprofiles.DBException: RFC call returned an error code: 399
I'm certain the user is NOT locked and the password is correct for PILDUSER. It'll give me a different error if I put the wrong password in, so I know it's hitting my system.
Worse yet, If I left the hostname in there that was set to "prod", then when I changed all the other values in the "parameters" section of the XI profile, then it actually changed my PROD system!!
If I keep the ABAP connection to PIT, then the entire exchange profile disappears for PIT.
I see these errors in the default trace and application log:
Caused by: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND:
No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",
Name="PIT.SystemHome.<traininghostname>"
Caused by: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND: No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="PIT.SystemHome.<traininghostname>"
at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120)
#2.#2011 11 03 13:49:47:008#0-500#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
#BC-XI-CON-AFW#com.sap.aii.af.lib#7E3832DEA80F002B00000000008700C6#4804850000001902##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#J2EE_GUEST#0##0AFD01D4064C11E1CB5E7E3832DEA80F#0afd01d4064c11e1cb5e7e3832dea80f#0afd01d4064c11e1cb5e7e3832dea80f#0#Application [24]#Plain##
SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
#2.#2011 11 03 14:51:18:096#0-500#Error#com.sap.esi.esp.service.server.ESPServiceInterfaceAbstract#
#BC-ESI-WS-JAV#tcesiespsrv#7E3832DEA80F001100000000009A004C#4804850000001385##com.sap.esi.esp.service.server.ESPServiceInterfaceAbstract####109F6812065511E1BF9C7E3832DEA80F#109f6812065511e1bf9c7e3832dea80f#109f6812065511e1bf9c7e3832dea80f#0#Service Runner [tcesiespsrv]#Plain##
+There is problem reading the hostname from the ClusterManager. This could lead to improper wsdl links.#
SLDCHECK shows this:
Function call returned exception code 3
Access to the XI Profile is currently disrupted.
I can't be the first person to run into this.
SO strange that I can actually plug in either my dev/QA or PROD hostname in the "ABAP connection" box and it WILL ACCEPT IT...but then, it registered my training system as a "non central adapter engine". I don't want that.
Any ideas?
Another issue is that the SLD PI information from the PIT system is missing the "Integration Directory". It has the other 5 entries...Adapter Engine, Domain, Integration Repository, Integration Server, RWB.
Thanks for reading this,
NICK

Here is the error I get when I try to change the "abap connection" to the correct hostname:
RFC call returned an error code: 399
Stack Trace class com.sap.rprof.dbprofiles.DBException: <pre>at com.sap.rprof.dbprofiles.DBProfiles.checkReturn(DBProfiles.java:184) at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:105) at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1378) at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:204) at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfile(RemoteProfile.java:154) at com.sap.rprof.dbprofiles.ExchangeProfile.getExchangeProfile(ExchangeProfile.java:46) at com.sap.rprof.remoteProfile.webui.ProfileWebTree.<init>(ProfileWebTree.java:24) at com.sap.rprof.remoteProfile.webui.Edit.getWebTree(Edit.java:322) at JEE_jsp_treeexprof_4804850_1319481176000_1319565151782._jspService(JEE_jsp_treeexprof_4804850_1319481176000_1319565151782.java:59) at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:436) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:493) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388) at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327) </pre>

New Development system copy from Production

Hi All,
Hope you can help me out here with some ideas.
We are currently planning to implement a new SAP BW Development system, and for this we would like to make it a 1:1 copy of our current production system. Meaning all from customizing, ABAP, workbench objects etc.
But what we do not want is all the transaction and master data in infoobject, cubes etc., we are only interested in the structure and objects. Therefore we can rule out "System copy".
My question is then, is there any other ways to do this when system copy is a no go? I know we can do client copy but then we will not get all the workbench / ABAP programs which we need.
Any ideas on how to do this?
Thx. in Advance

Hi Rasmus,
But what we do not want is all the transaction and master data in infoobject, cubes etc., we are only interested in the structure and objects. Therefore we can rule out "System copy".
Options 1: As BI objects are cross client , copying client will not solve your purpose 100%.
You can perform system copy and then clean up data in DEV
Option 2: You can create a new Development and then create TRs for required configuration objects and move to new development system.
Option 3: Use SLO tools to perform container copy without any data.
Hope this helps.
Regards,
Deepak Kori

System copy tool

Similar Messages

Maybe you are looking for