ORA-00406: COMPATIBLE parameter needs to be 8.1.0.0.0 or greater

Hello there, I have an ERROR message while performing an Alter table instruction. Can anyone spot the flaw and propose possible solutions.
ALTER TABLE "ALMACEN2"."DINGRESOSALIDAALM"
DROP ("ITEMOTRABAJO", "IDORDENPRODUC", "IDEMPAQUE", "CANTEMPAQUE",
"TARA", "LIQUIDADO", "DEVUELTO", "ARANCEL", "DISTRIBUCION", "REVISADO",
"NUMPALETA", "DESPACHADO") CASCADE CONSTRAINTS;
S
Output:
ORA-00406: COMPATIBLE parameter needs to be 8.1.0.0.0 or greater
Thanks indeed

oerr ora 40600406, 00000, "COMPATIBLE parameter needs to be %s or greater"
// *Cause: The COMPATIBLE initialization parameter is not high
// enough to allow the operation. Allowing the command would make
// the database incompatible with the release specified by the
// current COMPATIBLE parameter.
// *Action: Shutdown and startup with a higher compatibility setting.

Similar Messages

ORA-00406: COMPATIBLE parameter.....

Hi,
I've 2 Oracle instance:
ORCL10 on Database 10.2.0.3 version
ORCL9 on Database 9.2.0.1 version
I run FGA for audit select on both instance
I run this script:
BEGIN
    DBMS_FGA.ADD_POLICY(
    OBJECT_SCHEMA => 'SCOTT',
    OBJECT_NAME   => 'HR',
    POLICY_NAME   => 'SELECT_HR',
    AUDIT_CONDITION => '',
    AUDIT_COLUMN => '',
    STATEMENT_TYPES => 'SELECT');
END;For ORCL10 FGA works correctly
For ORCL9 I get this error:
ERROR at line 2:
ORA-06550: line 2, column 5:
PLS-00306: wrong number or types of arguments in call to 'ADD_POLICY'
ORA-06550: line 2, column 5:
PL/SQL: Statement ignoredI changed parameter in:
BEGIN
    DBMS_FGA.ADD_POLICY(
    OBJECT_SCHEMA => 'SCOTT',
    OBJECT_NAME   => 'HR',
    POLICY_NAME   => 'SELECT_HR');
END;But I get this error:
ERROR at line 1:
ORA-00406: COMPATIBLE parameter needs to be 9.0.0.0.0 or greater
ora-06512: at "SYS:DBMS_FGA", line 92
ORA-06512: at line 2How can I use this FGA also for Oracle 9.2.0.1 version??
Thanks in advance!

Raf Royal wrote:
OK,
but what version I have to modify this parameter (9.2.0.0.0)??Start with the suggested one.
after that I modify COMPATIBLE parameter how can I fix this error?
BEGIN
DBMS_FGA.ADD_POLICY(
OBJECT_SCHEMA => 'SCOTT',
OBJECT_NAME   => 'HR',
POLICY_NAME   => 'SELECT_HR',
AUDIT_CONDITION => '',
AUDIT_COLUMN => '',
STATEMENT_TYPES => 'SELECT');
END;
ERROR at line 2:
ORA-06550: line 2, column 5:
PLS-00306: wrong number or types of arguments in call to 'ADD_POLICY'
ORA-06550: line 2, column 5:
PL/SQL: Statement ignored
You won't fix that error on your 9i database, you are specifying non-existing parameters, not valid, for 9i database.
Read the doc :
http://download.oracle.com/docs/cd/B10501_01/appdev.920/a96612/d_fga2.htm#1000757
Nicolas.

DBMS_AQADM error ora 00406

Hi,
Im running 9.2.0 on OS X and trying to set up a queue table. Any idea what I'm doing wrong?
9.2 docs say you can only use 8.0 or 8.1 as compatibility parameters. I've tried all options from
8.0-9.2 and tried deleting the compatible argument altogether. All attempts produce the same
result.
Thanks,
Jeff
SQL> begin
dbms_aqadm.create_queue_table(
queue_table => 'input_mqtab',
comment => 'inbound request queue table',
multiple_consumers => TRUE,
queue_payload_type => 'SYS.XMLType',
compatible => '8.1');
end;
ERROR at line 1:
ORA-00406: COMPATIBLE parameter needs to be 9.0.0.0.0 or greater
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 2197
ORA-06512: at "SYS.DBMS_AQADM", line 58
ORA-06512: at line 2

Depending on the Database type that you installed, you may need to modify your init.ora parameter file to include the updated Compatibility. Since I loaded a DW database, I added the:
COMPATIBILITY 9.0.2 to the end of the initdw.ora and then bounced the database.
The COMPATIBILITY is not a session or system modifyable parameter, so it needs to happen at startup.
-RM

Triggers - 00406 error (COMPATIBLE parameter)

I created a DDL - level trigger =
'create trigger prev_drop
before drop or truncate on kd.schema...'
which prevents anyone from droppping or truncating tables owned by the user 'kd'
with names starting from 'led'.
Upon compilation of the same i get the error
'ORA-00406 COMPATIBLE parameter needs to be string or greater'
Can anyone help me with this error.
null

Are you asking how to determine what parameters are in 10.2.0.3 that were not in 9.2.0.7?
I've not seen any documentation on this so my instinct would be a database link and then a variation on the following query:
set pagesize 35
set linesize 150
col NAME format a30
col VALUE format a20
col DESCRIPTION format a60
set pause on
set pause 'Hit enter to continue'
SELECT x.ksppinm NAME, y.ksppstvl VALUE, ksppdesc DESCRIPTION
FROM x$ksppi x, x$ksppcv y
WHERE x.inst_id = userenv('Instance')
AND y.inst_id = userenv('Instance')
AND x.indx = y.indx
AND SUBSTR(x.ksppinm,1,1) ^= '_'
ORDER BY 1;for undocumented parameters and just a straight MINUS set query from gv$parameter for those that are documented.

No Compatible parameter when creating 8i Repository

Hi, When I try to create the new repository (using RAU) I get an error, in ckrau61,script cktabs: "ORA-00406 Compatible parameter needs to be 8.1.0.0 or greater". It seems that I need a statement like: "Alter system set compatible='"8.1.0.0.0' scope=?????;"
What should the scope be and where does the statement go?
Thanks for your help. Martin

OK, I found it. It is a statement in the init***.ora files. There doesn't seem to be a scope clause. Why the instructions are not in the upgrade directions is anybody's guess.

11gRel2 DBCA - using compatible parameter 10.2.0.3.0 results in ORA-00201

Hi guys,
Following is the scenario:
1. Oracle DB Binaries: 11.2.0.2.2
2. Using dbca to create General Purpose Database and then modify initialization parameter "COMPATIBLE from 11.2.0.0.0 to 10.2.0.3.0" in the "All Initialization Parameters" window.
So, when I finally start installing database, I get following error during the install:
ORA-00201: control file version 11.2.0.0.0 incompatible with ORACLE version 10.2.0.3.0
ORA-00202: control file: '/u01/app/oracle/cfgtoollogs/dbca/infpp1/tempControl.clt'
IGNORE OR ABORT...
Now you might ask why i am doing this. Actually I want to install fresh 11grel2. database with lower compatible parameter. IMPORT DP custom schemas into this database making sure compatible is set to 10.2.0.3.0. Then run database with such settings for a week and finally change compatible parameter to 11.2.0.0.0
Any thoughts where i am going wrong? as the default template seems not accepting what i am interested to do.
regards,
Anjum

It is not clear why you need to have the compatible parameter set to 10.2.0.3 for the import - it will work perfectly fine with the default value (11.2.0.2) of the compatible parameter. As you have experienced, once you set this parameter, it cannot be changed to a lower value
http://docs.oracle.com/cd/E11882_01/server.112/e23633/intro.htm#CEGJDHGI
HTH
Srini

When to change COMPATIBLE parameter while upgrading to Oracle 11G

We are planning to upgrade from Oracle 10.2.0.4 on AIX to Oracle 11.2.0.2 soon.
While reading oracle upgrade documents and from oracle upgrade blog, it is mentioned that once we change compatible parameter,
we will not be able to catdwgrd.sql to downgrade.
However, if we don't change compatible parameter after an upgrade, all the testing efforts during upgrade process wont be complete
as we may need to do another round of testing after changing this value.
So what is the best time for changing this compatible parameter? 1 week or 2 weeks after upgrade?
We are considering catdwgrd.sql as our option to fallback if something goes wrong.
Thank You
Sarayu

Hi,
It's a difficult question. If your applications are validated with 11gR2, if your OS is certified to work with Oracle 11gR2, if you adjusted the requirements etc. it will work. Will it work 100% well ? Maybe not but downgrading is really an extreme solution. 11gR2 is a fully supported version and anyway you will obtain efficient support from Oracle if you encountered a bug etc.
If you have doubts change when you are sure every critical activity/charge you expect went well for example. We cannot know if it will be after 1 week or 2 weeks : it's up to you.
Be sure you check what Tom says about the COMPATIBLE parameter (it's interesting to know exactly what it covers, it does not cover the optimizer features etc.) : http://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:485421569569
Best regards
Phil

ORA-02069: global_names parameter must be set to TRUE for this operation

I have 10g database and a schema 'TMAPP'
And I have two table in TMAPP as
create table user_menu_privs
company_code           varchar2(5),
bu_code      varchar2(12),
user_group      varchar2(30),
user_group_type      varchar2(1),
menu_option_code number(5),
enabled varchar2(1),
query_only varchar2(1),
default_lang varchar2(3),
created_by      varchar2(10),
created_on      date,
updated_by      varchar2(10),
updated_on      date,
constraint pk_user_menu_privs primary key (company_code,bu_code,user_group,user_group_type,menu_option_code),
constraint fk_user_menu_privs foreign key (company_code,bu_code,user_group,user_group_type)
references user_group(company_code,bu_code,user_group,user_group_type)
create table user_dst
company_code           varchar2(5),
bu_code      varchar2(12),
userid varchar2(10),
user_group      varchar2(30) ,
user_group_type      varchar2(1) ,
font_size      number(2) ,
font_name      varchar2(100) ,
address_id number(10),
created_by      varchar2(10),
created_on      date,
updated_by      varchar2(10),
updated_on      date,
constraint pk_user_dst primary key (company_code,bu_code,userid,user_group,user_group_type),
constraint fk_user_dst foreign key (company_code,bu_code,user_group,user_group_type)
references user_group(company_code,bu_code,user_group,user_group_type)
I have another database 11g with a schema TMAPP.
Here I have created a database link 'to_dev' is connecting to the 10g db
using this I can connect and see the data from 10g TMAPP
I have created two views
create or replace view user_menu_privs as
select *
from user_menu_privs@to_dev
where user_group in
(select user_group from user_dst
where user_group_type='F');
create or replace view user_dst as
select * from user_dst@to_dev;
and I executed
delete from user_menu_privs
where menu_option_code=108;
I am getting the error
ORA-02069: global_names parameter must be set to TRUE for this operation
after that I set the global_names in 11g as TRUE
then I am getting another error as
ORA-02085: database link TO_DEV connects to DEV.REGRESS.RDBMS.DEV.US.ORACLE.COM -- that means link is not wokring
Please help
Dennis
Edited by: DJ on Mar 13, 2012 5:49 AM
Edited by: DJ on Mar 13, 2012 5:51 AM
Edited by: DJ on Mar 13, 2012 5:53 AM
Edited by: DJ on Mar 13, 2012 5:55 AM
Edited by: DJ on Mar 13, 2012 5:56 AM

OP wrote
>
But you said
create a database link in 11g database with 11g database global name and put 11g database global_name=true.
and put 10g database golba_name=false;
>
That isn't what I said at all. Reread my first reply. The first part is a copy of what you had stated.
>
ORA-02069: global_names parameter must be set to TRUE for this operation
after that I set the global_names in 11g as TRUE
>
And then I said
>
That is because when global_names is TRUE, the database link name MUST be same as the global db name of the database to which the link connects to.
You need to drop the database link and recreate it using the global name of the database it connects to.
'link name MUST be same as the global db name of the database to which the link connects to.' - I didn't say 11g.
And I didn't say 'put 11g database global_name=true' because you had already done that! 'after that I set the global_names in 11g as TRUE.
1. 11g - global_names MUST be TRUE
2. 11g - database link name MUST be the same as the global db name of the database to which the link connects to - 10g global db name
3. 10g - gloibal_names setting is irrelevant

Mismatch between COMPATIBLE Parameter and Oracle Version

Hi,
If the ORACLE version is say 11g but the compatible parameter in init.ora is say 9.2.0 or 8.1.7 what will be the effect on the database?
Will the database behave as like 11g or of the lower version?
If we alter the init.ora to the new version for compatible paremeter will it affect DB rebooting?
This is an interview question and i could not answer.
Please let me know the answers.

If the ORACLE version is say 11g but the compatible parameter in init.ora is say 9.2.0 or 8.1.7 what will be the effect on the database?
Will the database behave as like 11g or of the lower version?
If we alter the init.ora to the new version for compatible paremeter will it affect DB rebooting?
This is an interview question and i could not answer.Here, database created in 11gR2, if try to set lower compatibility it wont be allowed, Below is example.
Check this article of TKyte.
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:485421569569
Init.ora Parameter "COMPATIBLE" Reference Note [ID 30699.1]
SQL> show parameter compatible
NAME                                 TYPE        VALUE
compatible                           string      11.2.0.0.0
SQL> alter system set compatible='10.2.0' scope=spfile;
System altered.
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 778387456 bytes
Fixed Size                  1374808 bytes
Variable Size             276825512 bytes
Database Buffers          494927872 bytes
Redo Buffers                5259264 bytes
ORA-00201: control file version 11.2.0.0.0 incompatible with ORACLE version
10.2.0.0.0
ORA-00202: control file: 'C:\ORACLE\ORADATA\ORCL\CONTROL01.CTL'
SQL>SID3
     Newbie
Handle:      SID3
Status Level:      Newbie
Registered:      Sep 27, 2006
Total Posts:      493
Total Questions:      68 (56 unresolved)
Name      Amritansu Ray
Close the thread if answered, Keep the forum clean.
Edited by: CKPT on Feb 15, 2012 9:54 PM

COMPATIBLE parameter question

Our company makes an application which needs the COMPATIBLE parameter set to 10.2.0.1.0 . But our client says its db's COMPATIBLE parameter is set 10.2.0.3.0 . The only application that is going to run in this server will be our application. Do we have to ask the client to change the COMPATIBLE parameter to 10.2.0.1.0 or let it remain as 10.2.0.3.0?

On 10g the parameter COMPATIBLE cannot be downgraded, as once datafiles are open, they register this information on their headers.
In this particular case there is no conflict with the versions, as you are talking about the same functional version with different maintenances:
The first three digits refer to the major version and the functionality, meanwhile the last two digits refer to the DB and OS maintenance (bugs), but you are talking about the same version, 10.2.0.
~ Madrid

11gr2 database compatible parameter

I have a 11g r2 database and the compatible parameter was originally set to 11.2.0.0.0. I did an alter system set compatible='10.2.0.4' scope=spfiile;
Now when I try to start the database, it says control file version 11.2.0.0.0 incompatible with ORACLE version.
When I do a startup nomount and try to alter system set compatible='11.2.0.0.0' scope=spfile, I get ORA-32012: SPFILE format is inconsistent with value of COMPATIBLE parameter.
I also tried doing a create pfile from spfile and it gives me the same error. Is there anyway to fix this?
On another note, the reason why I tried this was because I tried installing Grid Control 10.2.0.3 using an existing database with this 11gr2 database. It doesn't let me proceed saying the database must be 10.2 or higher. It seems to not like my 11gr2 database version so that's why I tried changing the compatible parameter. Anyway to get around this?
Thanks for your help.

sb92075 wrote:
alter system set compatible='11.2.0.0.0' scope=spfile
I also tried doing a create pfile from spfile
As for shutdown abort and create the spfile, Why are you trying to CREATE SPFILE???????
it can't find the spfile in the dbs directory because I'm using ASM.Please make up your mind.
Either spfile exists or it does not.
Are you having a problem with the ASM instance or "normal" (OLTP?) instance?
Too bad CUT & PASTE are broken for you!Why the hostility? It was a typo. I was creating a pfile, not spfile.
Let me clarify. I am using ASM for this "normal" 11gr2 instance, so my spfile is located in a diskgroup called +DATA. When you shutdown the database and try to create a pfile from spfile, it looks for the spfile in the default directory under $ORACLE_HOME/dbs. So since I'm using ASM, my spfile is not located in this directory and oracle can't find the file.
Anyways, after some googling I answered my own question. I had to use create pfile from spfile='+DATA/emrep/spfileemrep.ora';
Thanks anyways...
But any direction on installing Grid Control using a 11gr2 existing database for the repository is appreciated.

Difference between compatible.rdbms in asm and compatible parameter in database

Hi Gurus,
Here i have small doubt. What is the difference between compatible.rdbms and compatible parameter in database.
We are having 2 node rac on solaris. When i checked at ASM instance level i found compatible.rdbms is set to 10.1.0.0.0 and compatible.asm is 11.2.0.0.0 and compatible parameter in database is set to 11.2.0.0.0.
Please guide me will it make any difference . Or do i need to change the compatible.rdbms to higher value.
Thanks & Regards,
Venkata Poorna Prasad.S

Hi,
I think you should check this
COMPATIBLE.RDBMS :Administering ASM Disk Groups
COMPATIBLE Oracle :Introduction to the Upgrade Process for Oracle Database
HTH

Compatible parameter set too specifically will it affect my database?

Hello,
I performed an upgrade from 9 to 10.2, when setting the compatible parameter I set that to 10.2.0.5 instead of 10.2.0.
I know that according to note 830576 and the guide, that parameter should be 10.2.0 but since I can't change it, I want to know if there would be any problems with the database or the SAP system
Thanks in advance

Hello Maria,
at first you should understand what happens when you set this parameter. Please check the official documentation for a detailed explanation: http://docs.oracle.com/cd/E11882_01/server.112/e25494/create005.htm#ADMIN11112
I want to know if there would be any problems with the database or the SAP system
Running your Oracle database with a 4 digit compatible parameter is not a "problem", but maybe you are not able to perform a rollback of the 10.2.0.5 patchset without a restore anymore. That's the reason why SAP (and other vendors) recommend to set only 2-3 digits of the oracle version.
Only Oracle knows, If the current patchset 10.2.0.5 (already) changed some stuff that is incompatible with an older 10g R2 patchset.
- A new feature stores any data on disk (including data dictionary changes) that cannot be processed with your previous release.
- An existing feature behaves differently in the new environment as compared to the old environment. This type of incompatibility is classified as a language incompatibility.
You can try to lower it and restart your DB - if your database is already incompatible you will get an ORA error.
Regards
Stefan

How to change COMPATIBLE parameter while creating the database using DBCA

I have installed 10.2.01.0 on centos 4.7
Now i want to create database with COMAPTIBLE parameter 9.2.0.1
I m trying to create database through DBCA, changed the initialization parameter COMAPTIBLE to 9.2.0.1.
But gives me error
ORA-19583: conversation termintated to error
ORA-19870: error reading backup peice /opt/oracle/assistants/dbca/templates/Seed_Database.dfb
ORA-00600: internal error code,arguments: [krbrckhr_compressed],[opt/oracle/assistants/dbca/templates/Seed_Database.dfb],[29],[30],[11420],[],[],[]
ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 5149
ORA-06512: at line 16
if i dont change the value of COMPATIBLE parameter then its running perfactly...
But i have to set compatible parameter as 9.2.0.1....
Can anybody tell me how to create database using 10g R2- 10.2.0.1.0 with compatible parameter 9.2.0.1

Thank you for your response.
I have tried that opting.
After creating the database with COMAPTIBLE parameter 10.2.0.1.0 changed that parameter in init.ora file to 9.2.0 and start the database.
But at that time getting
ORA-00201: contorl file version 10.2.01.0 incompatible with ORACLE version 9.2.0.0
ORA-00202: control file '/opt/oracle/oradata/ORCL/control01.ctl'

Error while exporting : ORA-24801: illegal parameter value in OCI lob funct

hello,
I am doing an export on a 10.2.0.4 , solaris machine.
The table i am doing an export has a blob & clob.
During the export I get the error :
EXP-00056: ORACLE error 24801 encountered
ORA-24801: illegal parameter value in OCI lob function
In metalink it was given : Check every parameter in the OCI Lob function call to make sure they
are correct. Offsets should be greater than or equal to one.
Where should I check for that OCI Lob function. Or is there any other alternative to do the export.
Thanks for any help.

I have increased the space on the mount I was doing the export and that solved the problem.
Thanks

ORA-00406: COMPATIBLE parameter needs to be 8.1.0.0.0 or greater

Similar Messages

Maybe you are looking for