Hi Guys,
I am sure someone might face this error in the future, i have a work around from SAP. I hope this can be useful for others who may face similar issue in the future.
Diagnoses:
- 1AETR012XProgram canceled (job "RDDEXECL", number "19543500")
- Job RDDEXECL is cancelled with the log showing runtime error DBSQL_SQL_ERROR
- The trace file shows that WP has reached abap/heaplimit = 40000000 bytes after which the Oracle 600 occurred.
- Oracle 600 occurred with the following argument
ORA-00600: internal error code, arguments: [kdlxdup:kdlwReadCallback_pga], [294] , [0], [], [].
Some thing to notice here is the code kdlxdup and 294.
5. And SM21 shows the following.
SM21
Database error 600 with FET access to table SCPRSREVERTD
FET - Reading one or several records of a database cursor
Solution:
SAP says the following
The issue seems to be related to bug 17533661 currently being worked on by Oracle Development.
Unfortunately there is not yet any fix available for this.
SAP gives the below work around.
They asked me to use the "old" LOBs (BasicFiles) for the table SCPRSREVERTD
instead of the "new" SecureFile LOBs.
instead of the "new" SecureFile LOBs.
They asked me to use the brspace tool for the reorganisation as described in the SAP note:
1431296 - LOB conversion and table compression with BRSPACE 7.20
Chapter 1.2: Syntax of the options for LOB conversion"
1431296 - LOB conversion and table compression with BRSPACE 7.20
Chapter 1.2: Syntax of the options for LOB conversion"
With Note 1
Note 1: There is, however, a hidden option "-COL" (create old LOBs) that prevents this.
If this is set on the command line, the system converts the LONG fields into the old LOBs (BasicFiles).
In the "lob2lob" action, you can use this option to force the system to convert the new LOBs into old LOBs
If this is set on the command line, the system converts the LONG fields into the old LOBs (BasicFiles).
In the "lob2lob" action, you can use this option to force the system to convert the new LOBs into old LOBs
So I reorganized the table with the action lob2lob with the -COL option and continued the upgrade, then issue got resolved. While SAP is working on providing a fix for this
Regards,
Sebastian