cancel
Showing results for 
Search instead for 
Did you mean: 

long2lob conversion of table SOFFCONT1 ends with ora-03113: end-of-file on communication channel

jonasmeyer1
Explorer
0 Kudos

We have to do long2lob conversion before online reorganization of the table (~55GB) will be possible, because field CLUSTD is LONG RAW.

Name                  Null?    Type

--------------------- -------- ----------------------------

MANDT                NOT NULL VARCHAR2(3)

RELID                NOT NULL VARCHAR2(2)

PHIO_ID              NOT NULL VARCHAR2(32)

SRTF2                NOT NULL NUMBER(10)

PH_CLASS              NOT NULL VARCHAR2(10)

CLUSTR                NOT NULL NUMBER(5)

CLUSTD                LONG RAW

Analysis of table was done before reorg:
analyze table sapmib.soffcont1 validate structure online;

Table analyzed.

The actual command used by brspace was:

brspace -p initP57.sap -s 20 -l E -u / -f tbreorg -a long2lob -t SOFFCONT1


But in the end I always get this error:

BR0301E SQL error -3113 at location tab_onl_reorg-63, SQL statement:

'BEGIN DBMS_REDEFINITION.FINISH_REDEF_TABLE (UNAME => '"SAPMIB"', ORIG_TABLE => '"SOFFCONT1"', INT_TABLE => '"SOFFCONT1#

$"'); END;'

ORA-03113: end-of-file on communication channel


System Details:

DB: Oracle 11.2.0.2.0

SAP: ERP 6.0, NW 7.4, EHP 7 SP4

Kernel: HP-UX ia64, 741_REL, Patch 216

BR*Tools: 740, Patch 13


At the moment, I don't know what to do about this, are there any ideas?

Find attached the alert log from that day plus the ddl-statement and brspace log.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

For ORA-03113 there may be a lot of possible reasons.

There are also a lot of SAP notes; I suppose you already went through 335199 and others?

The most serious problem I can see in your alert.log is this line:

ORA-00600: internal error code, arguments: [kghfrempty:ds], [0x9FFFFFFFFD3E0010], [], [], [], [], [], [], [], [], [], []

Let me suggest you open a support call, concerning this ORA-00600 message.

jonasmeyer1
Explorer
0 Kudos

Thank you for your reply. Yes, we went through the related notes, including the 335199.
I opened a support message, let's see what we get!