cancel
Showing results for 
Search instead for 
Did you mean: 

ORA-43851 during a HetSysCopy to oracle 11.2.0.2

Former Member
0 Kudos

Hi,

Please can anybody help me out on the issue below ?

During a System Copy with SAPINST to oracle 11.2.0.2 in the ABAP IMPORT phase I got an ORA-43851 error :

DbSl Trace: ORA-43851 occurred when executing SQL stmt (parse error offset=451)

(DB) ERROR: DDL statement failed

I can see it is related to a LOB feature as below:

ORA-43851:

LOB feature unsupported below compatible 11.0.0

Cause:

An 11g LOB feature was specified when the RDBMS is operating at a compatible setting lower than "11.0.0".

Action:

Upgrade the RDBMS compatible setting to "11.0.0" or higher to enable the desired new features.

Please how can I fix it to allow SAPINST to finish successfully ?

Thanks very for much for some help.

Best regards,

Mauricio

Accepted Solutions (0)

Answers (1)

Answers (1)

markus_doehr2
Active Contributor
0 Kudos

> Please how can I fix it to allow SAPINST to finish successfully ?

Did you INSTALL 11g from the SAP DVDs?

Markus

Former Member
0 Kudos

Hi Markus,

That's correct: DVD 51041033 - I am installing a new ECC6 EHP5 as HetSysCopy.

ORACLE 11.2.0.2 64-BIT

RDBMS

Windows Server on x64 64bit

Number 51041033

Thanks and regards,

Mauricio

Former Member
0 Kudos

Folks,

I started the instance in nomount state and found out the following:

SQL> show parameter compatible

NAME TYPE VALUE

-


-


-


compatible string 10.2.0

But how can I change it ?

I mean, there is no init.ora/spfile at this point.

when I tried ALTER SYSTEM SET COMPATIBLE = ''11.2.0' I got:

SQL> alter system set compatible = '11.2.0' scope=spfile;

alter system set compatible = '11.2.0' scope=spfile

*

ERROR at line 1:

ORA-32001: write to SPFILE requested but no SPFILE is in use

SQL> alter system set compatible = '11.2.0';

alter system set compatible = '11.2.0'

*

ERROR at line 1:

ORA-02095: specified initialization parameter cannot be modified

SQL>

I think when I installed oracle 11.2.0 it came with this setting.

Anh idea ?

Thanks in advance,

Mauricio

Former Member
0 Kudos

Hi All,

This issue is fixed. I set the compatible parameter to 11.2.0 and updated the kernel level.

ABAP IMPORT phase is running now.

Thanks

Former Member
0 Kudos

Hi, facing the same error can you be more specific "set the compatible parameter to 11.2.0" SAP note or detailes?

Former Member
0 Kudos

Hi,

I had the the same problem and was able to to overcome that error by updating the parameter

compatible = 10.2.0 to 11.2.0 at init<SID).ora file

Regards

Uday

 

Former Member
0 Kudos

Hey,

Thanks for solution,it worked for me...

I was getting error in system import's R3load jobs.

I changed parameter, created spfile from pfile and retried phase.......

Regards,

Ishan