System Copy : Error during export

[Former Member]

Hi ,

Component :SAP ECC 5.0

Database :Oracle 10.2.0.2

We arer doing Homogenous SysteM Copy throught SAP standard procedure

While we export the data from Source system to the External Disk

We are encountering with the error show below

The retry failed

C:\usr\sap\TST\SYS\exe\run/R3load.exe: START OF LOG: 20090226155148

C:\usr\sap\TST\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#20 $ SAP

C:\usr\sap\TST\SYS\exe\run/R3load.exe: version R6.40/V1.4

Compiled Aug 16 2007 21:36:26

C:\usr\sap\TST\SYS\exe\run/R3load.exe -datacodepage 1100 -e C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\NUC\DBEXP/SAPAPPL1.cmd -l C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\NUC\DBEXP/SAPAPPL1.log -stop_on_error

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC

(GSI) INFO: dbname = "TST20080804080809 "

(GSI) INFO: vname = "ORACLE "

(GSI) INFO: hostname = "USLAFSV37 "

(GSI) INFO: sysname = "Windows NT"

(GSI) INFO: nodename = "USLAFSV37"

(GSI) INFO: release = "5.2"

(GSI) INFO: version = "3790 Service Pack 2"

(GSI) INFO: machine = "16x AMD64 Level 6 (Mod 15 Step 11)"

(GSI) INFO: instno = "0020137624"

DbSl Trace: Error 600 in stmt_fetch()

DbSl Trace: ORA-600 occurred when executing SQL statement (parse error offset=1121)

(EXP) ERROR: DbSlExeRead failed

rc = 99, table "S260BIW1"

(SQL error 600)

error message returned by DbSl:

ORA-00600: internal error code, arguments: [15201], [], [], [], [], [], [], []

(DB) INFO: disconnected from DB

C:\usr\sap\TST\SYS\exe\run/R3load.exe: job finished with 1 error(s)

C:\usr\sap\TST\SYS\exe\run/R3load.exe: END OF LOG: 20090226155152

Please help us in solving this issue

Regards

Haynes

[former_member204746 · Accepted solution]

DbSl Trace: ORA-600 occurred when executing SQL statement (parse error offset=1121)

check your alert_SID.ora file and provide lines in the area of that ORA-00600 error.

[Former Member]

Hi,

You can check your alert.log and background/user trace files for more details.

Hope this helps.

Manoj

[Former Member]

... which are precisely the traces I mentioned in my initial reply. One interesting bit of information there is the stack trace, in which you will find the names of the Oracle kernel routines (these usually start with a "k"). Especially for internal errors like ORA-00600, it is essential to have their names when searching for possible causes.

Rgds,

Mark

[former_member105207]

hi Haynes,

please refer the note

DbSl Trace: ORA-1403 when accessing table SAPUSER

400241 - Problems with ops$ or sapr3 connect to Oracle

regards,

chandru.

Edited by: Chandru on Feb 27, 2009 2:15 PM

[Former Member]

> please refer the note

>

>

DbSl Trace: ORA-1403 when accessing table SAPUSER

>

>

> 400241 - Problems with ops$ or sapr3 connect to Oracle

>

Nope -- at this point the ORA-1403 is perfectly normal (the SAPUSER table is empty, it only gets created later on towards the end of the system copy). Please ignore it, it has nothing to do with the ORA-00600 and will go away automatically.

[Former Member]

Hi,

ORA-00600 / 15201 is covered by Oracle Metalink article 138430.1. The artice explains possible causes but for a solution only refers to a list of patches. Did you install the patch set + minipatch for the Oracle release you are using? See note 871735 for the latest list of mandatory and recommended patches for your platform.

For further investigation - and also if you report the problem to SAP support - you must always add the Oracle trace file, which is created when the error occurs. This trace is located either in \oracle\<SID>\saptrace\usertrace (or \oracle\<SID>\saptrace\background if it was triggered from an Oracle system process).

Regards,

Mark