Home » RDBMS Server » Enterprise Manager » ORA-00406: COMPATIBLE parameter
| ORA-00406: COMPATIBLE parameter [message #136151] |
Tue, 06 September 2005 07:06  |
ashishodia
Messages: 10
Registered: August 2005
Location: Mumbai
|
Junior Member |
 
|
|
Hi All,
I am facing problem when creating a table with list partition
ORA-00406: COMPATIBLE parameter needs to be 9.2.0.0.0 or greater
version of oracle whic i am using is greater then 9.2.0.0.0
SQL*Plus: Release 9.2.0.1.0 - Production on Tue Sep 6 16:53:15 2005
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
DDL command is
CREATE TABLE CS_CASE_INFO_PART
(
CS_CASE_INFO_ID NUMBER(10) NOT NULL,
FINANCIER_ID VARCHAR2(75 BYTE) NOT NULL,
APPL_ID VARCHAR2(75 BYTE) NOT NULL,
CUST_ID VARCHAR2(75 BYTE) NOT NULL,
PRODUCT_ID VARCHAR2(45 BYTE) NOT NULL,
CUST_NAME VARCHAR2(195 BYTE) NOT NULL,
DPD NUMBER(3) NOT NULL,
INSTALLMENT_DUE_DATE DATE,
NO_OF_INST_OVERDUE NUMBER(,
AMOUNT_OVERDUE NUMBER(16,2),
MIN_AMOUNT_DUE NUMBER(16,2),
NO_OF_INST_OUTSTANDING NUMBER(,
AMOUNT_OUTSTANDING NUMBER(16,2),
GRACE_DAYS NUMBER(3),
GRACE_AMOUNT NUMBER(16,2),
HHNO VARCHAR2(60 BYTE),
TOTAL_CHARGES_OVERDUE NUMBER(16,2),
PRINCIPLE_OVERDUE NUMBER(16,2),
PRINCIPLE_OUTSTANDING NUMBER(16,2),
INTEREST_OVERDUE NUMBER(16,2),
INTEREST_OUTSTANDING NUMBER(16,2),
COLLECTION_CYCLE NUMBER(2),
BUCKET NUMBER(3),
QUEUE VARCHAR2(24 BYTE),
ZONE VARCHAR2(24 BYTE)
AGENCY VARCHAR2(24 BYTE),
DISBURSAL_DATE DATE,
WLL_NO VARCHAR2(20 BYTE),
LAFNO VARCHAR2(20 BYTE),
DUPLICATE_BILL_REQUEST VARCHAR2(1 BYTE),
BUCKET0 NUMBER(16,2),
OTAF_DATE DATE,
PLAN VARCHAR2(100 BYTE),
LTD_PMNT NUMBER(16,2),
NO_BILLS_RAISED NUMBER(10),
AGENT_CODE VARCHAR2(24 BYTE)
)
TABLESPACE DATA
PARTITION BY LIST(ZONE)
(
PARTITION CIRCLE_CAP VALUES('CAP')NOLOGGING,
PARTITION CIRCLE_CBB VALUES('CBB')NOLOGGING,
PARTITION CIRCLE_CBB VALUES('CCC')NOLOGGING,
PARTITION CIRCLE_CBB VALUES('CDL')NOLOGGING,
PARTITION CIRCLE_CBB VALUES('CGJ')NOLOGGING,
PARTITION CIRCLE_CBB VALUES('CKL')NOLOGGING,
PARTITION CIRCLE_CBB VALUES('CKN')NOLOGGING,
PARTITION CIRCLE_CBB VALUES('CMH')NOLOGGING,
PARTITION CIRCLE_CBB VALUES('CMP')NOLOGGING,
PARTITION CIRCLE_CBB VALUES('CMU')NOLOGGING,
PARTITION CIRCLE_CBB VALUES('CPJ')NOLOGGING,
PARTITION CIRCLE_CBB VALUES('CRJ')NOLOGGING,
PARTITION CIRCLE_CBB VALUES('CTN')NOLOGGING,
PARTITION CIRCLE_CBB VALUES('CUP')NOLOGGING,
PARTITION CIRCLE_CBB VALUES('CWB')NOLOGGING,
PARTITION CIRCLE_NULL VALUES(NULL)NOLOGGING,
PARTITION CIRCLE_UNKNOWN VALUES(DEFAULT)NOLOGGING
);
Plz help m to remove this error .
Regards,
Amit Shishodia
|
|
|
|
| Re: ORA-00406: COMPATIBLE parameter [message #136154 is a reply to message #136151] |
Tue, 06 September 2005 07:25  |
tarundua
Messages: 1080
Registered: June 2005
Location: India
|
Senior Member |
|
|
what is the value of compatible in ur parameter file?
U can check with
| Quote: |
SQL> show parameter compatible
NAME TYPE VALUE
------------------------------------ ----------- ----------------------------
compatible string 9.2.0.0.0
|
if it is less than 9.2.0.0.0 then change it.
regards,
tarun
|
|
|
|
|
|
| Re: ORA-00406: COMPATIBLE parameter [message #136159 is a reply to message #136156] |
Tue, 06 September 2005 07:51 |
tarundua
Messages: 1080
Registered: June 2005
Location: India
|
Senior Member |
|
|
hi,
In ur pfile u wil find an entry for compatible parameter ,which will look like this ( its an excerpt from my pfile , ur pfile should contain value something like 9.0.2 or similar )--
| Quote: |
###########################################
# Miscellaneous
###########################################
compatible=9.2.0.0.0
|
now change the pfile parameter to 9.2.0.0.0 value and save it.
then, startup the database with this pfile ,
SQL> startup pfile=d:\oracle\ora92\....\pfile\init.ora
and then create spfile from this pfile,
SQL> create spfile from pfile;
check this out.
regards,
tarun
|
|
|
|
Goto Forum:
Current Time: Sat Jan 18 12:10:55 CST 2025
|
] 
Blog
Search
Help
Members
Register
Login
Home
