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

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

  • ora-12201 : TNS:encountered too small a connection buffer
  • ora-32638 : Non unique addressing in MODEL dimensions
  • ora-00164 : distributed autonomous transaction disallowed within migratable distributed transaction
  • ora-13641 : Task cannot be interrupted yet. You may cancel it instead.
  • ora-12591 : TNS:event signal failure
  • ora-37144 : (MDQUERY01) string is not a valid metadata object type for MDQUERY.
  • ora-26714 : User error encountered while applying
  • ora-02274 : duplicate referential constraint specifications
  • ora-36815 : (XSTBLFUNC08) The OLAP_TABLE has attempted to use an AW single row function with the aw_attach parameter set to DURATION QUERY.
  • ora-09876 : TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file.
  • ora-22874 : attribute "string" is not part of the type "string"
  • ora-32807 : message system link string already exists
  • ora-24366 : migratable user handle is set in service handle
  • ora-06519 : active autonomous transaction detected and rolled back
  • ora-32316 : REFRESH FAST of "string"."string" unsupported after mixed DML
  • ora-36840 : (XSLMGEN10) Cube string.string!string has no measures
  • ora-14055 : keyword REBUILD in ALTER INDEX REBUILD must immediately follow
  • ora-01062 : unable to allocate memory for define buffer
  • ora-30649 : missing DIRECTORY keyword
  • ora-07272 : spwat: invalid semaphore set id.
  • ora-08446 : syntax error in SYNCHRONIZED clause in mask options
  • ora-28582 : a direct connection to this agent is not allowed
  • ora-29925 : cannot execute string
  • ora-07479 : scgcmn: cannot open or convert lock.
  • ora-28503 : bind value cannot be translated into SQL text for non-Oracle system
  • ora-02239 : there are objects which reference this sequence
  • ora-31666 : Master process string had an unhandled exception.
  • ora-13241 : specified dimensionality does not match that of the data
  • ora-22952 : Nested Table equality requires a map method on the element ADT
  • ora-18000 : invalid outline name
  • 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.