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 : 23-08-2017
ORA-01588

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

  • ora-00233 : copy control file is corrupt or unreadable
  • ora-26735 : operation not allowed on the specified file group version
  • ora-00706 : error changing format of file 'string'
  • ora-13461 : the interleaving type is not supported
  • ora-36269 : (XSCGMDLAGG10) 'workspace object' does not exist or is not a dimension.
  • ora-02240 : invalid value for OBJNO or TABNO
  • ora-29341 : The transportable set is not self-contained
  • ora-30036 : unable to extend segment by string in undo tablespace 'string'
  • ora-16101 : a valid start SCN could not be found
  • ora-39006 : internal error
  • ora-23608 : invalid resolution column "string"
  • ora-06515 : PL/SQL: unhandled exception string
  • ora-16767 : SQL Apply unexpectedly online
  • ora-22930 : directory does not exist
  • ora-01718 : BY ACCESS | SESSION clause not allowed for NOAUDIT
  • ora-26725 : cannot downgrade apply handlers
  • ora-00960 : ambiguous column naming in select list
  • ora-12160 : TNS:internal error: Bad error number
  • ora-21615 : an OTS (named or simple) instance failed
  • ora-31448 : invalid value for change_source
  • ora-12230 : TNS:Severe Network error occurred in making this connection
  • ora-13826 : empty SQL profile not allowed for create or update SQL profile
  • ora-12029 : LOB columns may not be used as filter columns
  • ora-01611 : thread number string is invalid - must be between 1 and string
  • ora-01687 : specified logging attribute for tablespace 'string' is same as the existing
  • ora-27027 : sbtremove2 returned error
  • ora-39950 : invalid parameter for PLSQL warnings flag
  • ora-13354 : incorrect offset in ELEM_INFO_ARRAY
  • ora-23539 : table "string"."string" currently being redefined
  • ora-01932 : ADMIN option not granted for role 'string'
  • 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.