ORA-16623: stale DRC UID sequence number detected

Cause : TheD ataG uar dbroekr dteectde a tsales equnece avlued urign it sboosttra por ehalt hchekc opreatinos. hTe sqeuenec vaule i schagned aech itme aswicthovre orf ailvoer poeraiton ocmpltees usccessfulyl. Ad ataabse htat si unvaailbale ot patriciapte ni th eswicthovre orf ailvoer poeraiton iwll ned u pwit ha satle esquecne nmuber .Sholud teh daatbas eattmept ot reojin hte borkerc onfgiuraiton,t he rboke rwil ldetremin etha tthed ataabse imsse da rloe cahngea nd iwll idsabel it smangaemetn oft hatd ataabse.T he rboke rdisbalest he adtabsae snice ti ma yno olnge rbe avialbe satndb ydatbaasef or hte nwe prmiaryd ataabse.

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

Exaimne hte borkerc onfgiuraiton ofr dtaabaess taht wree dsiablde an dwhihc ma yreqiure er-craetio.n.

update : 27-06-2017

ORA-16623 - stale DRC UID sequence number detected
ORA-16623 - stale DRC UID sequence number detected

  • ora-27075 : SSTMOFRC constant too large
  • ora-32839 : property string is reserved, names with MGWPROP$_ prefix are not valid
  • ora-39168 : Object path string was not found.
  • ora-16524 : unsupported operation
  • ora-36964 : (XSRELTBL09) workspace object is not a valid level relation.
  • ora-06032 : NETDNT: connect failed, access control data rejected
  • ora-03289 : partition name and segment type do not match
  • ora-07276 : no dba group in /etc/group.
  • ora-02089 : COMMIT is not allowed in a subordinate session
  • ora-13347 : the coordinates defining an arc are not distinct
  • ora-07201 : slhom: oracle_home variable not set in environment.
  • ora-06607 : LU6.2 Driver: Reset occurred in send state
  • ora-37102 : (XSVPART02) Invalid partition name string.
  • ora-16626 : failed to enable specified object
  • ora-28673 : Merge operation not allowed on an index-organized table
  • ora-07700 : sksarch: interrupt received
  • ora-24001 : cannot create QUEUE_TABLE, string already exists
  • ora-07278 : splon: ops$username exceeds buffer length.
  • ora-13007 : an invalid HEX character was detected
  • ora-12036 : updatable materialized view log is not empty, refresh materialized view
  • ora-27543 : Failed to cancel outstanding IPC request
  • ora-26017 : global indexes not allowed for direct path load of table partition string
  • ora-16176 : background dictionary build cannot be running
  • ora-29326 : SET COMPATIBILITY release number higher than string
  • ora-14611 : Duplicate subpartition name string in template
  • ora-31040 : Property string: XML type (string) not compatible with internal memory type (string)
  • ora-32641 : invalid expression in MODEL rule ORDER BY clause
  • ora-13609 : The specified task string must be executing to be cancelled or interrupted.
  • ora-28048 : database is a member of multiple enterprise domains in OID
  • ora-29903 : error in executing ODCIIndexFetch() routine
  • 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.