Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-00723: Initialization parameter COMPATIBLE must be
explicitly set
- 1 Answers
- 4861 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: Oracle detected that the initialization parameter
COMPATIBLE was not explicitly specified, and the
compatibility of the database is lower than the default
value of the COMPATIBLE parameter. In order to use the new
compatible setting, the intialization parameter must be
explicitly set by the user.
Action: Explicitly set the value of COMPATIBLE parameter
either in PFILE or SPFILE, whichever is used.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-23393: the user is already the propagator
QSM-02032: no joins are present in the WHERE clause
ORA-16003: standby database is restricted to read-only access
ORA-09850: soacon: Archmon unable to lock named pipe.
ORA-36614: (XSLMS02) string attempted to retrieve a nonexistent user message. (Message number number)
ORA-09950: Unable to get server operating system privileges
ORA-19642: incremental-start SCN is string
TNS-12516: TNS:listener could not find available handler with matching protocol stack
ORA-00309: log belongs to wrong database
SQL-02102: Inconsistent cursor cache. No global cursor entry.
ORA-10657: Lob column to be shrunk does not exist
TNS-00028: INTCTL: Could not resolve Connection Manager's name/address
Oracle Errors 
