Oracle 8.1.7 system copy 6.20

Hello
I have a DEV machine installed 6.40, i deleted database files oracle 8.1.7 sap crm 3.0, then o copied from PRD the files again.
and the sid changes... how can i change it ?
Now i want to make a system copy. How can I do ?
I created manually the control.sql, where i Copy this file?
I have to use 6.20/6.40 master intalation? but there is not comming crm 3.0, just 4.0...for system copy...which one i should use?
any1 can tell me step by step, or using r3load, or something without using any instalation dvd ?
what i have to do for make it run again.
thanks
regards.
Pheno
SAP Jr.Adminsitrator

thanks,
i need to ask some questions:
1- In system copy make differente if its CRM 3.0 or 4.0 or NW2004s or something?
like in master dvd 6.40 i dont find anything related of CRM3.0, just CRM 4.0.
2- what about database password? how can I reset it?
3- this documents its in Unix, the parameter are same for windows?
thank you very much for your help
Regards

Similar Messages

MOS-01012 during Oracle Pre-Load phase system copy

Hello,
The problem is in phase 'Oracle Pre-Load Actions', we have error:
MOS-01012 PROBLEM: '/sapmnt/Q02/exe/saplicense -R3Setup Q02 "OMLRUURS" TRACE=2' returned with '254' which is not a defined as a success code.
Homogenous system copy, AIX, ORA 9.2.0.8
I've checked a few things:
- when I manually execute this command I have:
Fri Jan 28 17:04:02 2011
MtxInit: 0 0 0
- R3trans -d is ok (rc 0000)
- Q02 database is up
- oracle listener is up
- saplicense -show
LICENSE system: Q02 hardware key: N1153195602 expiration_date: 99991231
 installation no: 0110004123 key: xxxxx
 userlimit: 0 productid: R3_ORA
 system-nr: 000000000310644498
license useable ***
- saplicense -get (returns N1153195602)
- saplicense.log contain:
Fri Jan 28 17:04:02 2011
MtxInit: 0 0 0
I'm stuck, no more idea...
Best regards,
MIchal
dev_slic contains:
SlicIGetDate: <20110129>
SlicPwForR3Setup: calc password out of <Q0220110129FJAWFNLTL>
SlicIGetDate: <20110129>
SlicSapInstall: sysname: >Q02< connect: >1< rollback: >1<
SlicIDbLock: first call to SlicIDbLock: initialize Mutex
db_con_init called
create_con (con_name=R/3)
Loading DB library '/sapmnt/Q02/exe/dboraslib.o' ...
load shared library (/sapmnt/Q02/exe/dboraslib.o), hdl 0
Library '/sapmnt/Q02/exe/dboraslib.o' loaded
function DbSlExpFuns loaded from library /sapmnt/Q02/exe/dboraslib.o
Version of '/sapmnt/Q02/exe/dboraslib.o' is "640.00", patchlevel (0.220)
function dsql_db_init loaded from library /sapmnt/Q02/exe/dboraslib.o
function dbdd_exp_funs loaded from library /sapmnt/Q02/exe/dboraslib.o
New connection 0 created
0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
db_con_connect (con_name=R/3)
find_con_by_name found the following connection for reuse:
0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
Got ORACLE_HOME=/oracle/Q02/920_64 from environment
-->oci_initialize (con_hdl=0)
got NLS_LANG='AMERICAN_AMERICA.UTF8' from environment
ERROR => OCI-call 'OCIEnvCreate(mode=16384)' failed: rc = -1 [dboci.c 2287]
 set_ocica() -> OCI or SQL return code -1
ERROR => OCI-call 'OCIErrorGet' failed: rc = -2 [dboci.c 2081]
-->oci_initialize (con_hdl=0)
got NLS_LANG='AMERICAN_AMERICA.UTF8' from environment
Client NLS settings:
Logon as OPS$-user to get SAPQ02's password
Connecting as /@Q02 on connection 0 (nls_hdl 0) ... (dbsl 640 070308)
Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
0 0 (nil) (nil) (nil)
Allocating service context handle for con_hdl=0
ERROR => OCI-call 'OCIHandleAlloc' failed: rc = -2 [dboci.c 2830]
ERROR => CONNECT failed with sql error '-2' [dbsloci.c 11395]
 set_ocica() -> OCI or SQL return code -2
ERROR => OCI-call 'OCIErrorGet' failed: rc = -2 [dboci.c 2081]
Try to connect with default password
Connecting as SAPQ02/<pwd>@Q02 on connection 0 (nls_hdl 0) ... (dbsl 640 070308)
Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
0 0 (nil) (nil) (nil)
Allocating service context handle for con_hdl=0
ERROR => OCI-call 'OCIHandleAlloc' failed: rc = -2 [dboci.c 2830]
ERROR => CONNECT failed with sql error '-2' [dbsloci.c 11395]
 set_ocica() -> OCI or SQL return code -2
ERROR => OCI-call 'OCIErrorGet' failed: rc = -2 [dboci.c 2081]
Edited by: Michal Sarna on Jan 29, 2011 4:37 PM

> Got ORACLE_HOME=/oracle/Q02/920_64 from environment
> -->oci_initialize (con_hdl=0)
> got NLS_LANG='AMERICAN_AMERICA.UTF8' from environment
> *** ERROR => OCI-call 'OCIEnvCreate(mode=16384)' failed: rc = -1 [dboci.c 2287]
> set_ocica() -> OCI or SQL return code -1
> *** ERROR => OCI-call 'OCIErrorGet' failed: rc = -2 [dboci.c 2081]
> -->oci_initialize (con_hdl=0)
Did you install the Oracle 9.2.0.8 client? Or did you link the binaries from the ORACLE_HOME? Or are you using the Oracle client from the installation DVD?
Markus

System copy for ECC 6.0 system no j2ee process under MMC

Dear support,
This has been observed in many of our clients system which are on ECC 6.0 abap+java system, that after we perform system copy from one system to another
whether it is Oracle platform or mssql server platform ( system copy for oracle using controlfile script ) ( system copy for mssql with restoring .BAK file from source )
systems are running fine but j2ee process table showing no processes like
SDM, dispatcher , server0
even configtool and go.bat are unable to connect.
Is there any specific settings we do after system copy for java side
Please let me know at earliest, as it is most strange thing i have seen in almost all my system where system copy is performed.I have already raised a post against this error but at that time i was not aware of this system copy reason behind the same.
Best regards,
AjitR

Your main problem is not, that you don't see anything in MMC (the system can be added manually without much hazzle) - but is, that you database content of schema SAP<SID>DB does not match the data found on the filesystem.
If you copy the filesystem structure from production to test/qa, you need to make sure, the database and filesystem are in sync. You will have two problems if you "just copy them":
- They are out of sync because your production was going on running since you copied the backup files
- all configuration (all java property sheets) is/are set to point to the production system instead of the test/qa system
I doubt, that it will work if you copy it over. This also explains, why you can't even start configtool, because it points to the wrong system/schema. You MAY be able to fix all that manually, but you may encounter subsequent errors because not all configuration is documented, you would need to step into the whole j2ee tree and look at each and every propertysheet to find out, whether it's correct or not. Additionally, the database may have other information (see above) and all that may become overwritten during bootstrap.
So - the best way to get your system up and running quickly is to start sapinst on the source system, export your Java instance (not using ABAP but the Java dump) and re-importing that to your test/qa system.
Markus

Installation Master DVD Distributed Java System Copy menu missing

Hello Gurus
We want to perfom an Java system copy of our EP 6.0 using sapinst
The source OS is Solaris 8.0 with Oracle 10.2.0.2
The target OS is Solaris 10.0 with Oracle 10.2.0.2
Our architecture is Distributed , CI is running on a system and DB server on another system.
For this operation we use the master DVD 51033746_12 but we have an issue in exporting the DB as the
Option for exporting the DB on a Distributed system is not displayed on the sapinst Menu .
We followed the last guide taken from sap 'Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP Web Application Server Java 6.40 SR 1' and this option should be listed
Excerpt:
Choose the installation service SAP NetWeaver u201904 Support Release 1--> Java System --><DB> --> Distributed System --> Migration - Database Export.
Unfortunately the Distributed system is not displayed and though we are stuck at the export step .
I could not find any sapinst patches . Is it a known issue for Soalris system and is there a Workaround .
Thanks for your help
De Palma Lionel .

Hello
Thanks for your answer . Unfortunately this option is not available as we are using a NW04 SR1 system , not a nw'2004's one . With the latest master install (Installation_Master_6.20_6.40_05_08 51033746_5 )we have the choice of
System copy Source --> Java system --> oracle --> Migration Data export
--> HA Java system --> oracle --> Migration Data export
System copy Target --> Java system --> oracle --> Central system-> Migration Data export
Target --> Java system --> oracle --> Distributed system -> Migration Target Central instance / Db instance install
The Distributed system is available for Import option but no for the export one .
My questions are :
- Can we use a master nw2004's master DVD for system copy on a Nw'04s one ?
- As the central instance is hosted on different system than DB instance , should I use the HA option ?
Regards

System copy from SAP R/3 47x110 with Oracle 10.2 to Oracle 11.2

Hello,
I want to do a system copy from SAP R/3 4.7 Enterprise 47x110 with Oracle 10.2 to a new machine with same SAP version but with oracle 11.2. (After this I will upgrade to ERP 6.0)
I will do this with export/import but I don't find any documentation (manuals or notes).
I only find this:
Note 1499877 - Oracle 11.2 for R/3 Enterprise 4.7 Ext. Set 1.10
but this note is only for a new installation, I don't know if this work with system copy
Note 516246 - INST- System Copy for SAP Systems based on SAP Web AS 6.20
This don't have information about oracle 11.2
I read the manual "Homogeneous and Heterogeneous System Copy for SAP® Systems Based on SAP Web Application Server 6.20" but this also don't say nothing about oracle 11.2
Can you help me? Where can I find this documentation and what DVDs (master and kernel) should I use?
Best regards

Hi Juan,
Thanks for your answer.
That is my doubt, what installation master shoud I use for export oracle 10.2 and import in oracle 11.2?
Note "1499877 - Oracle 11.2 for R/3 Enterprise 4.7 Ext. Set 1.10" say that I can use installation master of R/3 4.7 Set 2 (47x200) to install a new system.
I found this media:
51033746_9 Installation Master 6.20/6.40 Linux on x86_64 64bit
and
51040087_7 NW 04 SR1 Inst. Mst. Linux x86_64 64bit f. Oracle 10.2/11.2
I think this is the note that I need:
Note 1478351 - Oracle 11g Support on UNIX: 6.40-Based SAP Systems

R/3 System Copy PRD -- QA Oracle 9

Hi all,
We need to perform a system copy of Production back to QA (4.7/6.40 kernel). My previous experience with a system copy was on a 4.6C system with Oracle 8 using R3COPY. I have just downloaded the latest system copy guide 'Homogeneous and Heterogeneous System Copy for SAP® Systems Based on SAP Web Application Server 6.20' and for Oracle it says that backup/restore method is not recommended or support and to use R3LOAD. We are not keen to use this method as it requires a longer Production downtime for us (more than twice what would be required for offline backup), also we would need the space available on the disk.
Has anyone still used the backup/restore method as described in the 4.6C system copy guide with Oracle 9? I don't see why this method is not supported since for us it would be much easier.
Thanks
- Natalie

Hello,
Perhaps this notes can be of help:
<a href="http://service.sap.com/sap/support/notes/427836">427836</a> OneDb system: Homogeneous system copy with DBR3CP.R3S ( bit old, perhaps not good for your system )
<a href="http://service.sap.com/sap/support/notes/713685">713685</a> Hom./Het.System Copy SAP Web AS 6.40
<a href="http://service.sap.com/sap/support/notes/857734">857734</a> System Copy of SAP Systems based on 6.20 and 6.40 / Oracle
On this notes you can find other interesting refering the same issue
Not much into system copies with the new tools, but I think it is possible to use backup/restore.
The only thing is that you will have a little "mess" -> the tablespace name will have the old "SID", same happens with the schema. Unless you have installed the system with this issue in mind and used a "neutral" schema, the note is ( I think )[url=http://service.sap.com/sap/support/notes/617444]617444[/url]

Problems with the Oracle Pre-Load actions in an homogeneous system copy

Hi,
I am trying to do a NW04 homogeneous system copy, and I am having troubles with the ABAP copy. (Oracle Pre-Load Actions step)
I am with the database specific procedure, so I am creating the new system until the sapinst asks me to bring an online-offline backup and the control file, then the sapinst tries to recover the database by himself, but he finds trouble:
Error: CJS-00084 SQL statement or script failed. DIAGNOSIS: Error message: ORA-01194: file 1 needs more recovery to be consistent Ora-01110: data file 1: 'oracle/XIE...'
If I try to do the recover manually I have to make the usual:
RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE;
CANCEL
ALTER DATABASE OPEN RESETLOGS;
If I follow the sapinst.log I find that the sapinst tries to recover the database but fails with the above message and:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
Yes, that's true, if I make it manually I have to open the database with the 'alter database open resetlogs';
the problem could be fixed modifying the run_control.sql statement that the SAPINST creates at the working directory, but no modification to that statement is possible because the SAPINST deletes and creates the statement IMMEDIATELY before executing it, so what can I do?
Many thanks
Mario

SOLVED
for your info, the run_control.sql is UNMODIFIABLE, but I could modify the CONTROL.SQL that he calls, so I recovered manually the Database, and the CONTROL.SQL was a simply CONNECT and then OPEN DATABASE, just like that, so I could continue with my installation, another point for us against the damned SAPINST !!!

System Copy Questions R/3 4.6c + Oracle + Solaris

dear gurus
goal system copy in R/3 4.6c + Oracle + Solaris
I am doing the db export using R3SETUP (quite slow, I have optimize it using split SRT files method)
I have questions here..
when I do export I download latest R3szchk, R3load, R3SETUP, R3check, R3LDCTL
I download from
Support Packages and Patches - Archive - Additional Components - SAP Kernel -SAP KERNEL 64-BIT - SAP KERNEL 4.6D 64-BIT
R3szchk, R3load, R3check, R3LDCTL using SAPEXEDB_2364-10001132.SAR (Kernel Part II for Stack Q1-2008)
R3SETUP using R3SETUP_29-10001132.CAR
source system : Oracle 8.1.7 - R/3 4.6C - Solaris 9
my question is
target system : Oracle 10.0.2 with patches - R/3 4.6C - Solaris 10
later on when i do import to target system, should I use the same kernel when I do the export, or should I use the one from
Support Packages and Patches -> Additional Components -> SAP Kernel -> SAP KERNEL 64-BIT -> SAP KERNEL 4.6D_EX2 64-BIT
another question
how to speed up the export ? i am stucked with bottle neck in IO, CPU usage is very low, please dont recommend me something related to hardware or disk architecture, if possible recommend me something related to Oracle parameter.
disk IO using IO stat showing 100% busy and service time 800-1500
thanks !

later on when i do import to target system, should I use the same kernel when I do the export, or should I use the one from
Support Packages and Patches -> Additional Components -> SAP Kernel -> SAP KERNEL 64-BIT -> SAP KERNEL 4.6D_EX2 64-BIT
Yes - use that one. It uses the Oracle instantclient instead of the old 9.2 client. Make sure you add "-loadprocedure fast" to the load options, this will enable the fastloader.
Make also sure you install all the patchsets and interim patches BEFORE you start the data load.
another question
how to speed up the export ? i am stucked with bottle neck in IO, CPU usage is very low, please dont recommend me something related to hardware or disk architecture, if possible recommend me something related to Oracle parameter.
if you disk I/O subsystem can´t deliver more than you are lost with Oracle parameters.
Markus

System copy Oracle 10.2 in MSCS

Hi,
we need to move (using system copy) for a old MSCS cluster to new HW MSCS cluster of our NW04s (Abap and Java) + Oracle 10.2.0.2 + Win03 X86.
I would like to use backup/restore method due a very large Oracle database.
OK, I've already move a stand alone system to a MSCS using backup/restore method... but now, into MSCS source system I can't select method of backup/restore export to generare SDM, ecc. jar file to complete system copy on target system.
Is it possible to use a Oracle backup/restore method to copy an existing MSCS to new MSCS ?
Regards.
Ganimede Dignan

Hi,
>there should be no functional difference in systemcopy in MSCS compared to standalone configuration.
>
>because SDM is installed on a local instance you should run the steps on this node where the SDM is >installed on.
I suppose that but during db export on source system we are not be able to flag "use database specifc tools"
http://img510.imageshack.us/img510/2825/12584947li9.gif
(this is a previus hom. system copy based on Oracle backup/restore... but not in MSCS)
We can't see this step and SAPinst jump directly to export path request.
Regards.
Ganimede Dignan.

Heterogeneous System Copy from MS SQL to Oracle 11g

Good day friends,
I am currently in the stage of running SAPINST to continue the System Copy to the Target (i.e. the export is complete).
This may seem like a rudimentary question, but I am trying to implement Oracle 11g as the new database (and the SAP version of ECC 5). Now when I execute the sapinst, I only get the option for the Client on 9.2 and the RDBMS on 10.2.0.4.
I would like to specify 10.2 for the Client and 11g for the RDBMS, but those options are not included in the SAPINST. What must I do to get these options in the SAPINST?
Any help would be welcome.
Thanks.

I have run a system export from MSSQL and Windows Server, and I wish to run the import to Red Hat 5.4 and Oracle 11g.
I have used the latest ECC 5 Installation Master disk, which still does not have the option to install Oracle 11g. In fact, it only has the option to install Oracle 10g with an Oracle Client version 9. Surely there must be a newer option with Oracle Client 10?
Here is the product code for the Inst Master I downloaded.
6.20/6.40 based products Installation Master (Edition May 2008) Number 51033746

System Copy/ Oracle Backup/Restore as part of migrating from 32 to 64-bit

Source system (I386): R3E47 Ext Set 2.00 SAP_BASIS 620 Kernel 640 Windows 2000, Oracle 10.2.0.4, non-unicode
Target system (x86-64/AMD64): R3E47 Ext Set 2.00 SAP_BASIS 620 Kernel 640 Windows 2000 Oracle 10.2.0.4, non-unicode
Am using method System Copy/ Oracle Backup/Restore to migrate from 32 to 64 bit (HOM System Copy).
Actions on source system:
a) Upgrade from 9.2.0.7 to Oracle 10.2.0.4
b) Used ora_br_copy.bat to generate CONTROL.SQL and init<sid>.ora
c) Switched logfiles
d) Performed offline backup
Actions on target system:
a) Installed Oracle 10.2.0.1 and patched it to 10.2.0.4
b) Used CD 51033746 "6.20/6.40 based products Installation Master (Edition May 2008)" to install the CI
c) Started installation of the DB instance selecting System Copy/ Oracle Backup/Restore (same <SID> for source and target systems)
Relevant input parameters used:
Database schema: SAPR3
Database character set: US7ASCII
d) When SAPINST stopped to allow for restoring of datafiles, logs and init<sid.ora>:
- copied datafiles and logs to the usual place
- copied CONTROL.SQL (edited to include utilrp.sql and utlrp.sql for the migration from 32 to 64) to the DB-instance intallation . directory.
- copied generated init<SID>.ora to the <ORACLE_HOME>\database
e) Resumed SAPINST.
David Byrne in a previous post suggested: "check your oracle alert file in case there are errors there you may need to update the word size for the 64bit install. Errors like this in the oracle alert file would suggest that.,
ORA-12012
ORA-06544: PL/SQL: internal error, arguments: [ORA-06544: PL/SQL: internal error, arguments: 56319], [, ], [, ], [, ], [
ORA-06553"
Well, I am getting ORA-06553: PLS-801: internal error [56319] but then my edited CONTROL.SQL (which is mainly a CREATE CONTROLFILE as it would be obtained with a ...BACKUP CONTROLFILE TO TRACE) includes at the end this:
shutdown immediate
startup upgrade
spool utlirp.log
@?/rdbms/admin/utlirp.sql
spool off
Shutdown immediate
Startup
Spool utlrp.log
@?/rdbms/admin/utlrp.sql
Spool off
exit
which is supposed to do just that... (I think)
Help, anyone?

> Trying to cheer me up, are you?
No
> It is NOT free that reorganization! Quite expensive, actually, paid for in time! But you're right... the database needed a reorg anyway :-\
True, not "free" - it takes time but the data will be nicely aligned then
> And why would I have to reconfigure all those 10.2 features? Everything's either in the database or init<sid>.ora, ain't it? And my database is a pretty 10.2.0.4 with all those nice features already activated...
No - not really auotmatically if you upgraded from 9.2 And "init<SID>.ora" is past, you nowadays use "spfile" If, of course, e. g. Automatic Undo was activated in 9.2 then it's there of course in 10.2 too.
> One sticky point... I haven't really read the r3load procedure yet and I will before I import, but... I would say I don't have to do anything about the 32->64 bit, right? I mean, it should behave properly while reloading on 64-bit...
The exported content is about 10 % of the size of the system, it's database and OS independent so yes, you can import it nicely on 32bit. Another tip: make sure you don't just use the default configurations for R3load, it will take a HUGE amount of time. Use the package splitter (builtin-in in sapinst) so you get a much higher parallelism when importing.
Markus

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

Homogeneous system copy for 4.7.x.1.1 windows/oracle 9.2.0.3.0

I plan Homogeneous system copy for 4.7.x.1.1 windows/oracle at a
customer
downloaded tools(do I have to put extracted files on the sorce machine
in kernel directory?):
MIGMON_2-20001410
MIGMON_2-20001410.SAR
MIGTIME_2-20001410
MIGTIME_2-20001410.SAR
ORABRCOPY_2-20001410
ORABRCOPY_2-20001410.SAR
SAPCAR_5-10002026
SAPCAR_5-10002026.EXE
SPLIT_2-20001410
SPLIT_2-20001410.SAR
I would have additional questions.
1. In note 516246(System copy for SAP Systems based on SAP Web AS 6.20)
it is mentioned to download the latest version of R3LDCTL and apply it
to the system. I have following questions:
under service.sap.com/patches
i found only
R3LDCTL
Support Package SAP KERNEL 4.5B 32-BIT Windows Server on IA32 32bit
ORACLE
Is this file ok?(I will perform a homogeneous system copy of an 4.7x1.1
system)
If the file is ok what is meant as apply?(put it in kernel directory?)
2. Very similar question applies to file R3szchk
under service.sap.com/patches I found only
R3szchk
Support Package SAP KERNEL 4.6C 32-BIT Windows Server on IA32 32bit
ORACLE
Is this file ok?(I will perform a homogeneous system copy of an 4.7x1.1
system)
3.In same note(516246) the SAPinst CD is mentioned. How could I get it?
4.On the Source system I have kernel 640. I guess I have to copy the
content of this directory to the target system also. But in which phase?

hi,
first my question GGG
-> by which means do you plan to copy? brbackup/brrestore? r3copy? r3load?
ad 1.
SAPNet -> Patches -> Add. Components -> SAP Kernel -> 32 BIT (uni oder non-uni depending on your environment) -> SAP Kernel 6.40 32-bit -> Windows Srv -> Oracle -> R3ldctl_6-20000185.SAR (13.07.2006) is the right file (your kernel is 6.40!!!)
ad 2.
SAPNet -> Patches -> Add. Components -> SAP Kernel -> 32 BIT (uni oder non-uni depending on your environment) -> SAP Kernel 6.40 32-bit -> Windows Srv -> Oracle -> R3szchk_12-20000185.SAR is the right file (your kernel is 6.40!!!)
ad 3.
SAPNet -> SWDC (= Downloads) -> Download -> Inst. and Upgrades -> Entry by applic. group -> SAP Applic. Components -> SAP R/3 Enterprise -> Ent. 47X110 -> Installation -> Windows Server -> Oracle -> CD SAP R3E 4.7x1.10 SR1 SAPINST ORACLE (CD N° 51019679)
ad 4.
not really....it depends on the strategy (see my question above)...you first install the database software (oracle), then the central instance using sapinst, afterwards you will install the database instance using sapinst as well; while installing the db instance you have to chose db copy (or homogeneous copy, system copy) as the "database installation method" if you choose to copy the database files or did a backup if you choose to use the export/import method (using standard r3load) you will use the SystemCopy method as well but you will point (later on) to the directory where you (source) db export lies.
brrestore or copy method:
=========================
sapinst will popup at the appropriate point that the db load has to be done and depending on your strategy you have either to restore or copy files...
by the way: did you already export/backup/copy your source system?
if any further questions arise feel free to post
GreetZ, AH

Homogeneous system copy from ORacle 10.2 to 11.2 ?

Hello,
We are moving our SAP infrastructure to a new datacenter.
We are currently running 15 SAP systems (ABAP and J2EE) on HP-UX 11.23, Oracle 10.2 and are planning to relocate our
SAP instances on HP-UX 11.31 ( Oracle 11.2 Ready) but we intend to stay on Oracle 10.2 and then in a few months upgrade to Oracle 11.2, to benefit from full SAP support.
We will be using the homogenous system copy technique.
Is it possible to perfrom an homogeneous system copy from Hp-UX 11.23 Oracle 10.2 to HP-UX 11.31 to Oracle 11.2 ?
I am quite certain that I have read a similar discussion on SDN, but I can't find it anymore.
Thank you very much.
Regards

Hi,
You can check compatibility via PAM section on SAP Market place.
however , it is allowed to migrate to below new combination considering your SAP platform as NW 7.0.
released Database Version :Operating System :Date :Status
ORACLE 11.2 64-BIT HP-UX 11.31/IA64 64BIT 30.03.2010 Released
ORACLE 11.2 64-BIT HP-UX 11.31/PA-RISC 12.07.2010 Released
Regards,
Edited by: Rupali B on Feb 20, 2012 6:06 PM

Homogeneous System Copy Oracle procedure in R/3 4.7

Hi all
I want to know that whether I can do a homogeneous system copy oracle procedure in below environment.
SAP R/3 4.7 SR1 with Oracle 9.2.0.5.5 database and on windows 2003 environment.
I have done homogeneous Oracle procedure before on ECC 5.0 with Oracle 9 on windows environment. so I am confident through Oracle procedure.
I have Homogeneous document for SAP Web Application Server
ABAP 6.40 SR1.
But I was not able to find the document for the above environment.
Reply ASAP as I have currently the above R/3 4.7 Environment where I have to do Homogeneous Copy.
Thanks to all.
Regards
Vinay Paul

Hello Vinay,
Yes you can use the DB specific procedure for the homogneous copy of this system.
Please remember that in this environment you should not restore the database until prompted to do so by sapinst.
Regards,
David

Oracle 8.1.7 system copy 6.20

Similar Messages

Maybe you are looking for