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

Similar Messages

  • 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'

  • Oracle 9.2.0.7 vs Oracle 10.2.3 with COMPATIBLE parameter set to 9.2.0.7

    Hi,
    First off, I am NOT an oracle DBA (or even a DBA!), so please excuse my ignorance or errors contained within this post.
    My client is currently planning to upgrade their 9.2.0.7 database server to 10.2.3. Reading through the oracle upgrade documentation, I came accross the compatible parameter, and further more you can set it to 9.2.0.7. I realise that by setting this, many new features introduced in Oracle 10g will not be available - however getting of the unsupported 9.2.0.7 platform is priority.
    Can someone please advise what are the differences between a real 9.2.0.7 database server versus a 10.2.3 (with 9.2.0.7 compatible) server. By setting this will it guarantee sql scripts and external applications continue to work after the upgrade? I.e the list of compatibility issues detailed in the oracle database upgrade guide, will these issues be made irrelevant by this setting?
    Your expert knowledge is appreciated.
    Regards,
    Shan

    When upgrading from 9i to 10g the compatible parameter should be set to 9.2.0. All of the new feature will only be available when the parameter is set to 10.0.0 or higher and the instance restarted.
    Once an instance has been restarted with a compaticble value of 10.0.0 it can never be set back to 9.x.
    Why do you think the upgrade is required if you still want to use the features of 9.2.0.7?

  • COMPATIBLE parameter

    I want to know the impact of COMPATIBLE parameter on the database.
    I have 2 database of versions on different machines.
    COMPATIBLE parameter = 9.2.0.1 in one database and COMPATIBLE=10.2..0.3.0 in another.
    Are both database enviornments different?
    How are they dependant on COMAPTIBLE parameter?
    Yachendra

    COMPATIBLE parameter allow you to use some new features of the version, you should have a look into the corresponding docs.
    Take care, if you are allowed to set the parameter to a higher value, you cannot modify the value to a lower value.
    Nicolas.

  • 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.

  • 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.

  • INIT.ora-COMPATIBLE parameter

    Hi,
    My oracle version is 11.2.0.2 but in INIT.ora the parameter COMPATIBLE is set to 10.1.0.2.0.How does it impact DB?Does it mean that optimizer will use 10.1.0.2 features? Does it affect the performance of DB/queries in any manner?How will it impact if i change the vaue of this parameter t0 11.2.0.2 in INIT.ORA?Please throw some light on it
    SQL*Plus: Release 11.2.0.2.0 Production on Mon Sep 26 12:59:29 2011
    Copyright (c) 1982, 2010, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> show parameter compat
    NAME                                 TYPE        VALUE
    compatible                           string      10.1.0.2.0Thanks.

    Thanks Hemant again.
    Pasted from the link.
    <How the COMPATIBLE Initialization Parameter Operates
    The COMPATIBLE initialization parameter operates in the following way:
    It controls the behavior of your database. For example, if you run an Oracle Database 11g Release 2 (11.2) database with the COMPATIBLE initialization parameter set to 10.1.0, then it generates database structures on disk that are compatible with Oracle Database 10g Release 1 (10.1). >
    So eventhough the oracle version is 11.2.0.2.0 it works more or less like 10.1.0.2.Is my understanding correct?If so,then there is no point in upgrading oracle to 11.2 if this parameter has a lower value.Pls correct me.
    Thanks.

  • 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.

  • How to use lexical parameter in report

    i want to use lexical parameter in report and pass parameter from form how it is possible in detail
    A.R

    Hi,
    typically you fill your lexical paramter in the after-paramform-trigger out of the values of your bind-parameters (giving end users directly control over lexical parameters might not be a good idea). Inside PL/SQL a lexical parameter is referenced like bind parameters with ":". In the query it's referenced via "&" and represents a part of the query.
    A simple example.
    - p_deptno as bind parameter
    - p_where as lexical paramter
    - end user choose value for p_deptno (10,20,... or nothing)
    - Trigger: if :p_deptno is not null then
    :p_where := 'WHERE deptno = :p_deptno'
    else
    :p_where := null;
    end if;
    - Query select ... from emp &p_where
    Regards
    Rainer

  • How to use import parameter to be instead of SQL where sub-sentence ?

    I wrote a RFC to read data from SAP table. To fetch data flexibility, I want to use import parameter xx instead of where sub-sentence in SQL sentence.
       For example, "SELECT * FROM T WHERE XXX",  and "XXX" is a importing parameter.
       How can I use it.
       Thanks a lot.
       Frank.

    FUNCTION ZRFC_04.
    *"*"Local Interface:
    *"  IMPORTING
    *"     VALUE(TARGETTABLE) LIKE  MAKT-MAKTX
    *"     VALUE(TWHERE) LIKE  MAKT-MAKTX
    *"  EXPORTING
    *"     VALUE(ZRETURN) LIKE  MAKT-MAKTX
    *"  TABLES
    *"      TMP_TEST1 STRUCTURE  ZTEST1
      DATA:
      TRANSACTION_ID LIKE ARFCTID,
      V_VAILD(1) TYPE C,
      scond(80) TYPE c.
      V_VAILD = 'X'.
    GET PARAMETER twhere fields scond.
    The error " 'LATE FIELDS' expected, not 'TWHERE FIELDS' " generated.

  • Want to use one parameter of first command into second parameter.

    Hi, Experts,
    Please help me out I am stuck in a crystal report. Actually i have written two commands in crystal report.
    first one is as follows:-
    Select * from oinv T0 inner join inv1 T1 on T0.DocEntry = T1.DocEntry Where T0.DocNum = {?Invoice No}
    Second One is as follows:-
    Select * from ibt1_Link Where BaseNum = {?Invoice No}
    What i want is I am passing Parameter in both Command Which took Invoice no as an input, So i don't want to input ttwo parameter both for invoice no. can i use first parameter in my second command or not. If Yes then please tell me.How can i do the same.
    Regards
    Hanes

    Have you tried joining your commands on the basenum = docnum fields? That should filter the second command?

  • How to use a parameter field value as a substring in a "like" statement?

    Hi all,
    I'm trying to use a parameter field in a Record selection formula where the parameter field value would be a substring of the data stored in the field.
    My parameter field (SlctResearcher) is constructed as follows:
    Type: string
    List of Values: static
    Value Field: (Reports) RptAuthors
    (in Value Options) Allow custom values?: True
    {Reports.PubDate} in DateTime (2009, 04, 01, 00, 00, 00) to DateTime (2010, 03, 31, 23, 59, 59) and
    {Reports.RptAuthors} like "*{?SlctResearcher}*"
    When I hit F5 to generate the data, I get no results (and the parameter prompt field does not even come up...)
    If I modify the formula to put a hard-coded string, like
    "*Jones*"
    after the 'like', I get results (all the reports where "Jones" is a substring in the RptAuthors string.) If I modify the formula to just use the parameter field without the quotes/stars like:
    {Reports.PubDate} in DateTime (2009, 04, 01, 00, 00, 00) to DateTime (2010, 03, 31, 23, 59, 59) and
    {Reports.RptAuthors} like {?SlctResearcher}
    I do get the parameter prompt field, but still no results even if I put in a valid substring value (since it is not searching for a substring anymore...)
    How can I do this?
    Thanks,
    Will

    1st thing... Make a copy of your report before doing anything!!!
    To use a SQL Command, you'll want to open the Database Expert and look at the Current Connections. Expand the data source and the 1st option you see is the Add Command option.
    To find the SQL That CR is currently using, choose Database from the menu bar and select Show SQL Query...
    You can copy this and paste it directly into the command window. (If you you can write your own SQL you don't need copy CR's, it's just an option.)
    You'll also want to take not of any parameters that you have, you'll need to add them the the Parameter List of the command as well... be sure to spell them EXACTLY as they are in the design pane.
    Anyway, once the SQL statement is in the Command window you'll be able to alter the WHERE clause to use the wild cards.
    For future reference... What type of database are you reporting against???
    Jason

  • HR ABAP: Issue with using 'nocommit' parameter on FM HR_INFOTYPE_OPERATION

    Issue with using nocommit parameter on FM HR_INFOTYPE_OPERATION:
    My client has a requirement to create the following 4 infotypes in sequence in a LUW, i.e either all are created or none is created.
    9045   (custom infotype)
    0045
    0078
    0015
    I tried to use the nocommit parameter on FM HR_INFOTYPE_OPERATION to insert the 4 infotypes
    in a nocoomit mode and then at the end I have issued
    'Commit Work', but to my surprise only I/T 0015 is created in the database and the first three (9045, 0045 and 0078) did not make it to database.
    I searched many threads on SDN but could not find a solution.
    Please let me know if there could be any solution to implement the LUW.
    YOur inputs will be appreciated.

    Hi ,
    i think u can also try with this FM HR_MAINTAIN_MASTERDATA , see its documentations.
    no commit works like a simulation mode , what u can do is  ,
    call FM for all Infotypes and collect all error msgs if any , then finally call FM for all infotypes again without passing nocommit work ( i.e space).
    regards
    prabhu

  • Use of parameter sets with prepared INSERTS via Oracle's ODBC driver 8.1.6.4

    Oracles ODBC driver, version 8.1.6.4, allows for driver configuration of three different batch auto commit modes. If I select COMMIT ALL SUCCESSFUL STATEMENTS and cause my app to execute a prepared and parameterized INSERT statement that makes use of parameter value sets, all records up to the first record that causes an error are committed. What is happening? The driver returns only one diagnostic record, with SQLGetDiagField returning the index of the bad record through the [SQL_DIAG_ROW_COUNT] field. Regardless of whether SQLExecute executed successfully or not, the [SQL_ATTR_PARAM_OPERATION_PTR]/ [SQL_ATTR_PARAM_STATUS_PTR] buffers are not initialized by the driver. Even more so, the drive returns SQL_PARC_NO_BATCH for SQLGetInfo when [SQL_PARAM_ARRAY_ROW_COUNTS] is passed. Does anyone know if the driver fully or partially or does not support use of parameter value sets. If it is only partial implementation, ignoring the parameter operation and status buffers, in my opinion, greatly diminishes any real use of parameter value sets. Does anyone known if the above problems disappear with use of Oracles ODBC driver, version 8.1.7.3.0?
    All help is greatly appreciated,
    Chris Simms
    null

    <BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Justin Cave ([email protected]):
    What version of the database do you have on the back end?
    Justin<HR></BLOCKQUOTE>
    Oracle8i version 8.1.6. Looking at the specs that come with the ODBC driver upgrades, version 8.1.7.3.0 [which requires Oracle*i version 8.1.7] and 8.1.6.4, it seems that similar enhancements/fixes were made to both. I honestly do not know if what I am attempting is possible with either of the ODBC drivers. I really would prefer not to have to drop down to programming using OCI.
    Chris
    null

  • Getting error when using the "/parameter" switch in command line run

    Has anyone experienced this problem before?
    My report queries over 100,000 records from a view. When the report is run from the command line every thing works fine.
    But when I add a condition using a "parameter", although the report still runs fine from the destop, when launched from the command line it errs.
    "Oracle Discoverer Desktop has encountered a problem and needs to close. ..."
    "The instruction at "0x0044397c" referenced memory at "0x0000004e". The memory cound not be "read"...."
    I'm guessing its a memory issue with my PC. I've tested using a parameter with other reports using fewer records and it doesn't err from the command line.
    I can work around the issue by not using a parameter but then I have 20 versions of the same report each with a different condition.
    Any suggestions would be appreciated.
    Lise McGillis

    Hi Michael,
    I'm using an DELL Intel Pentium 4 CPU 3.00 GHz with 1 GB of RAM. We use Microsoft Windows XP Prof version 2002.
    As for Discoverer we are using 10G, Desktop Client 10.1.2.48.18 - 1047500 KB available memory , 2099744 KB Free disk space.
    I'm not sure I have acess to a computer with more RAM but I'm looking into it.
    What I'm frustrated by is the fact that the parameter works fine when run directly from the desktop but when passed from the command line it bombs... but only when dealing with mega records.
    Lise.

Maybe you are looking for