ORA-29323: ALTER DATABASE SET COMPATIBILITY command not supported by string

Cause : The ALTER DATABASE SET COMPATIBILITY command failed because one or more instances do not support dynamic compatible setting change.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

No action required.

update : 30-05-2017

ORA-29323 - ALTER DATABASE SET COMPATIBILITY command not supported by string
ORA-29323 - ALTER DATABASE SET COMPATIBILITY command not supported by string

  • ora-13226 : interface not supported without a spatial index
  • ora-26045 : REF column string expects string arguments; found string.
  • ora-13374 : SDO_MBR not supported for geodetic data
  • ora-07445 : exception encountered: core dump [string] [string] [string] [string] [string] [string]
  • ora-00476 : RECO process terminated with error
  • ora-07400 : slemtr: translated name for the message file is too long.
  • ora-29275 : partial multibyte character
  • ora-13288 : point coordinate transformation error
  • ora-12654 : Authentication conversion failed
  • ora-24755 : OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported
  • ora-30197 : reserved for future use
  • ora-13629 : The task or object string is being used by another operation.
  • ora-36816 : (XSTBLFUNC09) The workspace object dimension is of datatype string which does not support custom member upserts.
  • ora-17504 : ksfddel:Failed to delete file string
  • ora-09879 : sstascre/sstasat: shmat error, unable to attach tas read page
  • ora-09260 : sigpidu: error obtaining process id
  • ora-02430 : cannot enable constraint (string) - no such constraint
  • ora-09263 : spini: error initializing process
  • ora-22161 : type code [string] is not valid
  • ora-19708 : log destination exceeds maximum length of string characters
  • ora-00331 : log version string incompatible with ORACLE version string
  • ora-19684 : block media recovery failed because database is suspended
  • ora-16203 : Unable to interpret skip procedure return values
  • ora-33000 : (AGOPEN00) AGGMAP workspace object cannot be accessed because it was compiled by a more recent version of string.
  • ora-02403 : plan table does not have correct format
  • ora-24338 : statement handle not executed
  • ora-29904 : error in executing ODCIIndexClose() routine
  • ora-13068 : wrong table or column name in SDO_TOPO_GEOMETRY constructor
  • ora-09874 : TASDEF_READ: read error, unable to read tasdef@.dbf file.
  • ora-02266 : unique/primary keys in table referenced by enabled foreign keys
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.