ORA 43851 during System Copy with SAPINST

[Former Member]

Hi,

Please can anybody help me out on the issue below ?

During a System Copy with SAPINST on 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 veru for much for some help.

Best regards,

Mauricio

[Former Member · Accepted solution]

How about setting compatible = 11.2.0?

Cheers Michael

[Former Member · Accepted solution]

Michael,

The point is: the instance is not started yet at this ABAP IMPORT phase. I don't see any init.ora and/or spfile configured.

It seems sapinst set it on some phase but I didn't find it yet if this is correc because I am not sure.

Thanks

Mauricio

[Former Member · Accepted solution]

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]

Try this:

sqlplus

/as sysdba

show parameter spfile

If you do NOT see anything in the VALUE for the parameter spfile, then the SPFILE was NOT created and you are using the PFILE. The pfile (and spfile) are located in $ORACLE_HOME/dbs directory. You have 2 options:

1) Create an spfile

sqlplus "/as sysdba"

create spfile from pfile;

shutdown immediate

startup

Then run your alter system command for the compatible

shutdown immediate

startup

That should ensure that the parameter is loaded on the restart of the DB.

2) cd $ORACLE_HOME/dbs

edit the init<SID..ora

Change the compatible parameter in the init<SID>.ora

sqlplus "/as sysdba"

shutdown immediate

startup

Now the parameter should be enabled.

Then enable the SPFILE as shown aboe in #1.

Good Luck,

Mike Kennedy

[Former Member]

This could be cause be a wrong version of the installation dvd's. sapinst will create the initial parameter file, no matter if it is a spfile or old school init.ora. And it looks like in your case it created a 10g version, instead of a 11g one.

You should double check your installation media.

Cheers Michael

PS: and the instance will certainly be started during the import but sapinst probably stopped it when the error happened...

[Former Member]

Guys,

The parameter is changed now to 11.2.0:

SQL> show parameter compatible

NAME TYPE VALUE

-

---

-

---

-

---

compatible string 11.2.0

SQL>

But still having the same error:

DbSl Trace: Error 43851 in exec_immediate() from oci_execute_stmt(), orpc=0

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

(DB) ERROR: DDL statement failed

(CREATE TABLE "ECSCR_TSVAR" ( "NAME" VARCHAR2(90) DEFAULT ' ' NOT NULL , "VERSION" VARCHAR2(24) DEFAULT '00000000' NOT NULL , "ABLNR" VARCHAR2(90) DEFAULT ' ' NOT NULL , "COMMID" VARCHAR2(24) DEFAULT ' ' NOT NULL , "SUBID" VARCHAR2(24) DEFAULT ' ' NOT NULL , "CALLNO" VARCHAR2(30) DEFAULT '0000000000' NOT NULL , "VARNO" VARCHAR2(30) DEFAULT '0000000000' NOT NULL , "VALUE" CLOB ) TABLESPACE PSAPSR3 LOB ("VALUE") store as securefile (enable storage in row cache ) STORAGE (INITIAL 137743 NEXT 0000000160K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )

DbSlExecute: rc = 99

(SQL error 43851)

error message returned by DbSl:

ORA-43851: LOB feature unsupported below compatible 11.0.0

(DB) INFO: disconnected from DB

Thanks in advance for any new idea.

Best regards,

Mauricio

[Former Member]

What is the output from :

sqlplus "/as sysdba"

col comp_name format a40

select comp_name, version, status from dba_registry;

Mike Kennedy

[Former Member]

Mike,

Here you go:

SQL> col comp_name format a40

SQL> select comp_name, version, status from dba_registry;

COMP_NAME VERSION

-

---

-

---

STATUS

-

---

Oracle Database Catalog Views 11.2.0.2.0

VALID

Oracle Database Packages and Types 11.2.0.2.0

VALID

Thanks a lot,

Mauricio

[Former Member]

Ok. Let's try:

sqlplus "/as sysdba"

col name format a20

col value format a20

select name, value, isdefault, ISMODIFIED, ISADJUSTED from v$parameter where name = 'compatible';

I tried this in my system as a test and it created fine:

CREATE TABLE "MAURICIO"

( "NAME" VARCHAR2(90) DEFAULT ' ' NOT NULL , "VERSION" VARCHAR2(24) DEFAULT '00000000' NOT NULL , "ABLNR" VARCHAR2(90) DEFAULT ' ' NOT NULL ,

"COMMID" VARCHAR2(24) DEFAULT ' ' NOT NULL , "SUBID" VARCHAR2(24) DEFAULT ' ' NOT NULL , "CALLNO" VARCHAR2(30) DEFAULT '0000000000' NOT NULL ,

"VARNO" VARCHAR2(30) DEFAULT '0000000000' NOT NULL , "VALUE" CLOB )

TABLESPACE PSAPSR3

LOB ("VALUE") store as securefile (enable storage in row cache )

STORAGE (INITIAL 137743 NEXT 0000000160K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 );

drop table "MAURICIO";

[Former Member]

Hi Mike,

I was travelling back home yesterday. so I was not able to try this yet.

I did it here and it worked as well. Please see below.

E:\usr\sap\DEC\SYS\exe\uc\NTAMD64>sqlplus /nolog

SQL*Plus: Release 10.2.0.4.0 - Production on Sat Jul 23 05:40:02 2011

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

SQL> connect / as sysdba

Connected.

SQL> col name format a20

SQL> col value format a20

SQL> select name, value, isdefault, ISMODIFIED, ISADJUSTED from v$parameter wher

e name = 'compatible';

NAME VALUE ISDEFAULT ISMODIFIED ISADJ

-

---

-

---

-

---

-

---

-

---

compatible 11.2.0 FALSE FALSE FALSE

SQL> CREATE TABLE "MAURICIO"

2 ( "NAME" VARCHAR2(90) DEFAULT ' ' NOT NULL , "VERSION" VARCHAR2(24) DEFAULT

'00000000' NOT NULL , "ABLNR" VARCHAR2

3 (90) DEFAULT ' ' NOT NULL ,

4 "COMMID" VARCHAR2(24) DEFAULT ' ' NOT NULL , "SUBID" VARCHAR2(24) DEFAULT '

' NOT NULL , "CALLNO" VARCHAR2(30)

5 DEFAULT '0000000000' NOT NULL ,

6 "VARNO" VARCHAR2(30) DEFAULT '0000000000' NOT NULL , "VALUE" CLOB )

7 TABLESPACE PSAPSR3

8 LOB ("VALUE") store as securefile (enable storage in row cache )

9 STORAGE (INITIAL 137743 NEXT 0000000160K MINEXTENTS 0000000001 MAXEXTENTS 2

147483645 PCTINCREASE 0 );

Table created.

SQL> drop table "MAURICIO";

Table dropped.

SQL>

I updated R3load with the last version but still the import fails with the same error ora-43851.

Is there anything else we can try ?

Thanks for all your help on this issue.

Mauricio

[Former Member]

Mike,

I went ahead and updated the entire kernel and the ABAP IMPORT phase is running fine.

Thanks very, very, very much for all help I got from all of you, scpecially Mike.

Best regards,

Mauricio

[former_member683001]

Hello

I have exactly the same problem.

What did you mean by "I updated the entire kernel " ?

Thanks

pascal

[Former Member]

hi experts

i completed sap installation with abap. i trying login through GUI in client 001 i given user sap* password 06071992 and pass.

i also try 800 client and ddic user with 19920706. but its not working. its shows name or password is incorrect. kindly help to solve this issue.