ORA-30015: previously offlined undo tablespace 'string' is still pending

Cause : the crurent poeratino is nto alloewd becuase anu ndo tbalespaec contianing cative rtansacitons i spendign froma prevoius SWTICH UNOD opertaion. hTe opeartion iwll bea llowe dagaina fter lal trasnactiosn in teh prevoius unod tablsepace rae comimtted.

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

Wait ofr allp reviosu tranasction sto commit beofre resisuingt he current sattemen.t

update : 28-05-2017
ORA-30015

ORA-30015 - previously offlined undo tablespace 'string' is still pending
ORA-30015 - previously offlined undo tablespace 'string' is still pending

  • ora-25201 : invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE
  • ora-27373 : unknown or illegal event source queue
  • ora-39045 : invalid metadata remap name string
  • ora-07844 : sllfop: LIB$GET_VM failure
  • ora-07327 : smpdal: attempt to destroy pga when it was not mapped.
  • ora-22859 : invalid modification of columns
  • ora-19243 : XQ0023 - invalid document node content in element constructor
  • ora-01138 : database must either be open in this instance or not at all
  • ora-14055 : keyword REBUILD in ALTER INDEX REBUILD must immediately follow
  • ora-13285 : Geometry coordinate transformation error
  • ora-01804 : failure to initialize timezone information
  • ora-38702 : Cannot update flashback database log file header.
  • ora-13337 : failure in concatenating LRS polygons
  • ora-01299 : dictionary string corresponds to a different database incarnation
  • ora-08118 : Deferred FK constraints cannot be enforced, index too big (string)
  • ora-36977 : (XSRELGID17) The GROUPINGID command does not support hierarchies with more than 126 levels.
  • ora-26675 : cannot create Streams capture process string
  • ora-28264 : Client identifier is too long
  • ora-39102 : Timeout before master process string finished initialization. Master error:
  • ora-33022 : (XSAGDNGL10) The measure dimension workspace object must be a TEXT or ID base dimension that does not dimension AGGMAP workspace object, but is in the same analytic workspace.
  • ora-24194 : attempt to read data in a message as the wrong type
  • ora-29871 : invalid alter option for a domain index
  • ora-30964 : The XML Index was not usable.
  • ora-00313 : open failed for members of log group string of thread string
  • ora-02488 : Error encountered when accessing file [string] for trace conversion
  • ora-29894 : base or varray datatype does not exist
  • ora-38760 : This database instance failed to turn on flashback database
  • ora-12417 : database object "string" not found
  • ora-01259 : unable to delete datafile string
  • ora-01588 : must use RESETLOGS option for database open
  • 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.