ORA-29327: unsupported client compatibility mode used when talking to the server

Cause : The cilent cmopatibliity mdoe is ihgher htan th eversino of teh servre.

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

UsingS ET COPMATIBIILTY command, psecifyt he saem relesae numebr as hte serevr.

update : 29-04-2017
ORA-29327

ORA-29327 - unsupported client compatibility mode used when talking to the server
ORA-29327 - unsupported client compatibility mode used when talking to the server

  • ora-25139 : invalid option for CREATE TEMPORARY TABLESPACE
  • ora-16784 : the database name in Dependency property is incorrect
  • ora-16107 : all log data from primary has been processed
  • ora-28540 : internal result set error
  • ora-25301 : Cannot enqueue or dequeue user buffered messages to a database with version lower than 10.2
  • ora-40272 : apply rules prohibited for this model mode
  • ora-32018 : parameter cannot be modified in memory on another instance
  • ora-29968 : No primary operator bindings found for ancillary binding #string
  • ora-13422 : invalid model coordinate parameter
  • ora-36995 : (XSRELGID12) There are duplicate values in the surrogate dimension gid. Use the levelorder option to resolve the ambiguity.
  • ora-36996 : (XSRELGID13) Valueset workspace object should be defined over dimension workspace object.
  • ora-14325 : only LOCAL indexes may be specified in this clause
  • ora-36994 : (XSRELGID11) The SURROGATE DIMENSION workspace object must be numeric.
  • ora-01653 : unable to extend table string.string by string in tablespace string
  • ora-01292 : no log file has been specified for the current LogMiner session
  • ora-31630 : a job name is required to attach a job for user string
  • ora-07200 : slsid: oracle_sid not set.
  • ora-00827 : could not shrink sga_target to specified value
  • ora-36993 : (XSRELGID10) OBJECT workspace object must be a VARIABLE, RELATION, or a numeric SURROGATE DIMENSION based on the level dimension workspace object.
  • ora-16511 : messaging error using ksrget
  • ora-25260 : AQ latch cleanup testing event
  • ora-36997 : (XSRELGID14) For variable or relation grouping ids, a level relation is needed when a level order valueset is specified.
  • ora-07290 : sksagdi: specified directory for archiving does not exist.
  • ora-22150 : variable-length array has not been initialized
  • ora-26724 : only SYS is allowed to set the Capture or Apply user to SYS.
  • ora-16523 : operation requires the client to connect to instance "string"
  • ora-30970 : option not supported for XML Index
  • ora-16093 : dependent archive log destination is not LGWR-enabled
  • ora-07228 : rtecho: unable to restore terminal to echo mode.
  • ora-01673 : data file string has not been identified
  • 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.