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 : 24-07-2017

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

  • ora-23315 : repcatlog version or request string is not supported by version string
  • ora-22907 : invalid CAST to a type that is not a nested table or VARRAY
  • ora-13417 : null or invalid layerNumber parameter
  • ora-25140 : %s space policy cannot be specified for the string extent management
  • ora-00276 : CHANGE keyword specified but no change number given
  • ora-02278 : duplicate or conflicting MAXVALUE/NOMAXVALUE specifications
  • ora-08443 : syntax error in BLANK WHEN ZERO clause in mask options
  • ora-16625 : cannot reach the database
  • ora-16202 : Skip procedure requested to replace statement
  • ora-23399 : generation of replication support for "string"."string" is not complete
  • ora-24087 : Invalid database user string
  • ora-14186 : number of sub-partitions of LOCAL index must equal that of the underlying table
  • ora-08183 : Flashback cannot be enabled in the middle of a transaction
  • ora-01228 : SET DATABASE option required to install seed database
  • ora-07646 : sszfck: $CREATE failure
  • ora-02446 : CREATE TABLE ... AS SELECT failed - check constraint violated
  • ora-28602 : statement not permitted on tables containing bitmap indexes
  • ora-25254 : time-out in LISTEN while waiting for a message
  • ora-26035 : Error attempting to encrypt or decrypt column
  • ora-06306 : IPA: Message write length error
  • ora-22613 : buflen does not match the size of the scalar
  • ora-09352 : Windows 32-bit Two-Task driver unable to spawn new ORACLE task
  • ora-10261 : Limit the size of the PGA heap
  • ora-16764 : redo transport service to a standby database is offline
  • ora-04009 : MAXVALUE cannot be made to be less than the current value
  • ora-09316 : szrpc: unable to verify password for role
  • ora-34719 : (NLSCHARSET03) Character data loss in NTEXT/TEXT conversion
  • ora-02172 : The PUBLIC keyword is not appropriate for a disable thread
  • ora-16587 : ambiguous object specified to Data Guard broker
  • ora-02196 : PERMANENT/TEMPORARY option already specified
  • 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.