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 : 18-08-2017
ORA-16623

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

  • ora-31671 : Worker process string had an unhandled exception.
  • ora-01908 : EXISTS keyword expected
  • ora-14619 : resulting List subpartition(s) must contain at least 1 value
  • ora-00131 : network protocol does not support registration 'string'
  • ora-07290 : sksagdi: specified directory for archiving does not exist.
  • ora-13413 : null or invalid resampling parameter
  • ora-30359 : Query rewrite is not supported on SYS materialized views
  • ora-01097 : cannot shutdown while in a transaction - commit or rollback first
  • ora-08238 : smsfre: cannot detach from SGA
  • ora-02149 : Specified partition does not exist
  • ora-29811 : missing STATISTICS keyword
  • ora-10947 : trace name context forever
  • ora-33274 : (DBERR07) Timed out while trying to lock analytic workspace string for string.
  • ora-02762 : file number to be cancelled is greater than the maximum.
  • ora-24098 : invalid value string for string
  • ora-31112 : fail to string for string port using xdb configuration
  • ora-21301 : not initialized in object mode
  • ora-39105 : Master process string failed during startup. Master error:
  • ora-07672 : $PARSE_CLASS failed translating the string into a binary label
  • ora-07665 : ssrexhd: recursive exception encountered string string string string string string
  • ora-01485 : compile bind length different from execute bind length
  • ora-25469 : data not specified for alias: string column name: string
  • ora-28674 : cannot reference transient index-organized table
  • ora-19724 : snapshot too old: snapshot time is before file string plug-in time
  • ora-01105 : mount is incompatible with mounts by other instances
  • ora-35280 : (SNSYN165) The format of the AGGREGATE command is: AGGREGATE varname1 [varname2 varname3 ...] USING aggmap-name [COUNTVAR intvar-name1 [intvar-name2 intvar-name3 ...]] [FUNCDATA] [THREADS #]
  • ora-00335 : online log string: No log with this number, log does not exist
  • ora-12828 : Can't start parallel transaction at a remote site
  • ora-37155 : OLAP API bootstrap error: (case string)
  • ora-16737 : the redo transport service for standby database "string" has an error
  • 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.