ORA-01588: must use RESETLOGS option for database open

Cause : An earlier attempt to open the database with the RESETLOGS option did not complete, or recovery was done with a control file backup, or a FLASHBACK DATABASE was done.

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

Use the RESETLOGS option when opening the database.

update : 29-04-2017

ORA-01588 - must use RESETLOGS option for database open
ORA-01588 - must use RESETLOGS option for database open

  • ora-02488 : Error encountered when accessing file [string] for trace conversion
  • ora-30375 : materialized view cannot be considered fresh
  • ora-27030 : skgfwrt: sbtwrite2 returned error
  • ora-29547 : Java system class not available: string
  • ora-08332 : rollback segment #string specified not available
  • ora-22904 : invalid reference to a nested table column
  • ora-03244 : No free space found to place the control information
  • ora-31096 : validation failed for schema
  • ora-40306 : wide data not supported for decision tree model create
  • ora-26710 : incompatible version marker encountered during Capture
  • ora-38900 : missing mandatory column "string" of error log table "string"
  • ora-00228 : length of alternate control file name exceeds maximum of string
  • ora-06602 : LU6.2 Driver: Error allocating context area
  • ora-33315 : (XSDELDENTANON) You cannot delete workspace object while looping over unnamed composite workspace object.
  • ora-01025 : UPI parameter out of range
  • ora-16212 : number processes specified for APPLY is too great
  • ora-26084 : direct path context already finished
  • ora-03247 : Invalid block number specified
  • ora-19682 : file string not in block media recovery context
  • ora-33290 : (DBERR17) Analytic workspace string cannot be attached in the mode you requested because another user has it attached in an incompatible mode.
  • ora-03241 : Invalid unit size
  • ora-02397 : exceeded PRIVATE_SGA limit, you are being logged off
  • ora-12039 : unable to use local rollback segment "string"
  • ora-01939 : only the ADMIN OPTION can be specified
  • ora-07482 : snlmini: cannot create lock manager instance.
  • ora-37131 : (XSCCOMP06) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because the OPERATOR string is not supported for bases of a COMPRESSED COMPOSITE.
  • ora-36648 : (XSDUNION09) Concat dimension workspace object is already defined as UNIQUE.
  • ora-04070 : invalid trigger name
  • ora-27199 : skgfpst: sbtpcstatus returned error
  • ora-12549 : TNS:operating system resource quota exceeded
  • 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.