Value: 11.2.0 (<> 10.2.0) # Database compatibility mode

[Former Member]

Dear SAP friends,

We have upgraded oracle 10.2.0.4 to 11.2.0.2 in our development system.

It was completed succesfully.

but if i checked in DB16 ,i am getting the following message.

Value: 11.2.0 (<> 10.2.0) # Database compatibility mode

Corrective Action Change the Oracle parameter

I have checked one parameter in initSID.ORA file regarding compatible.

*.compatible='11.2.0'

I suppose the value of this is correct according database version.

Please guide me.

Thanks & Regards

Kumar.

[Former Member · Accepted solution]

Hello,

What is the sap kernel release and patch level, and what is BR*Tools version at the moment ?

What is the output of following query-

sql> show parameter compatible

Once verify from standard oracle parameters11g SAP Note whether the value should be 11.2.0 or 11.2.0.2. I think it should be 11.2.0 but still once verify it.

Thanks

[Former Member · Accepted solution]

Hi ,

SAP kernel release is 701 patch level 111,

Brtools vesrion 7.00(50)

I am not getting any value after execution of sql> show parameter compatible,

and in my initSID.ora file the parameter compatible was already set as 11.2.0

Thank you

[former_member188883 · Accepted solution]

Hi,

Please update brtools 7.20 in your system. This should help.

Regards,

Deepak Kori

[Former Member · Accepted solution]

Hi,

After Oracle upgrade you need to follow below few post upgrade steps.

1) Updating the BR tools latest version

2) Checking the upgraded database.

3) Check the database compatible by executing below commands.

SQL>show parameter compatible.

4) Change DB compatible by executing the below command.

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

5) Update the optimizer statistics and db statistics.

Please refer sap standard document.

I hope it will help you.

Regards,

Kiran .V

[Former Member]

Kiran Kumar answer helped me as well in resolving an upgrade issue with the below step.

SQL>show parameter compatible

4) Change DB compatible by executing the below command.

SQL>ALTER SYSTEM SET COMPATIBLE = '11.2.0' SCOPE = SPFILE;

I was getting " ORA-43851: LOB feature unsupported below compatible 11.0.0 " error in EX000000.DPR file while doing a upgrade ECC5 to ERP6.0 Ehp6 on windows 2008 / Oracle 11.2 environment

Thanks

[former_member664968]

Hi,

i am also facing the same error in DBcheck as stated above.i.e.Value: 11.2.0 (<> 10.2.0) # Database compatibility mode,change the oracle parameter,but if i check the parameter value at DBlevel its showing as 11.2.0.how to proceed to fix this issue.

i already did all the steps mentioned above also.

Regards,

Satheesh Kumar N

[Reagan]

Hello

Did you configure the condition COMPATIBLE in Tx DB17 ?

If not you may do it.

Regards

RB

[former_member664968]

Hi RB,

can you please share me the procedure how to maintain the same.

Regards,

Satheesh

[Reagan]

All you need to do is connect to the SAP system and call Tx DB17 and modify the condition  COMPATIBLE to 11.2.0

Regards

RB

[former_member664968]

Hi RB,

currently i am having the entry in DB17 as below

please advice me what to change in all the fields.

regards,

Satheesh N

[Reagan]

There is an edit button at the top.

You may use it and change it to 11.2.0

Regards

RB

[former_member664968]

Hi RB,

what should be the condition level and check condition values.

Regards,

Satheesh

[Reagan]

I already told you what you need to do. It looks like you don't read replies.

Here it is once again.

All you need to do is connect to the SAP system and call Tx DB17 and modify the condition  COMPATIBLE to 11.2.0

Good Luck

RB

[former_member664968]

Hi RB,

Thanks for all your support.

Regards,

Satheesh

[Former Member]

DB16 is still using the old checks from 10g times.

You have to adjust the checks.

Either do it manually in transaction DB17.

Or use the script attached to SAP Note 403704 - BRCONNECT - Enhanced functions for Oracle DBA.

regards

[former_member188883]

Hi,

As per SAP recommendation for Oracle 11g compatible parameter should have value

*.compatible='11.2.0'

Regards,

Deepak Kori