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 : 24-04-2017

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

  • ora-33263 : Could not create analytic workspace string
  • ora-31080 : type not specified for attribute or element "string"
  • ora-08178 : illegal SERIALIZABLE clause specified for user INTERNAL
  • ora-02167 : LOGFILE clause specified more than once
  • ora-38455 : Expression Filter index should be created by the owner.
  • ora-30068 : Internal Event to turn on nested
  • ora-19776 : PROXY restore to ASM diskgroup "string" is not supported.
  • ora-30331 : summary does not exist
  • ora-06533 : Subscript beyond count
  • ora-19023 : The first argument to UPDATEXML operator has to be an XMLTYPE
  • ora-33030 : (XSAGDNGL14) In AGGMAP workspace object, you can have either a single independent PROTECT statement or PROTECT statements in your RELATION statements.
  • ora-06571 : Function string does not guarantee not to update database
  • ora-14602 : SUBPARTITION TEMPLATE is legal only for a composite partitioned table
  • ora-16073 : archiving must be enabled
  • ora-01025 : UPI parameter out of range
  • ora-28181 : proxy 'string' failed to enable one or more of the specified initial roles for client 'string'
  • ora-38440 : attribute set string does not exist
  • ora-19604 : conversation file naming phase is over
  • ora-24303 : call not supported in non-deferred linkage
  • ora-12996 : cannot drop system-generated virtual column
  • ora-06136 : NETTCP: error during connection handshake
  • ora-00261 : log string of thread string is being archived or modified
  • ora-40206 : invalid setting value for setting name string
  • ora-14025 : PARTITION may not be specified for a materialized view or a materialized view log
  • ora-00471 : DBWR process terminated with error
  • ora-24502 : codepoint length overflows
  • ora-31064 : Cannot instantiate abstract element or property [string]
  • ora-40226 : model upgrade/downgrade must be performed by SYS
  • ora-35578 : (SQLOUT11) SQL cursor 'number' cannot be used with CURRENT OF syntax
  • ora-28521 : no heterogeneous capability information available
  • 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.