ORA-01613: instance string (thread string) only has string logs - at least 2 logs required to enable.

Cause : The thread cannot be enabled because it only has two online log files associated with it.

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

Add logs to the thread or pick another thread to enable

update : 23-07-2017

ORA-01613 - instance string (thread string) only has string logs - at least 2 logs required to enable.
ORA-01613 - instance string (thread string) only has string logs - at least 2 logs required to enable.

  • ora-27507 : IPC error disconnecting from a port
  • ora-06776 : TLI Driver: error sending parms
  • ora-02834 : Server unable to open file
  • ora-31644 : unable to position to block number string in dump file "string"
  • ora-16547 : cannot disable the primary database
  • ora-32016 : parameter "string" cannot be updated in SPFILE
  • ora-31019 : Recursive deletion snapshot too old for string/string
  • ora-19012 : Cannot convert XML fragment to the required datatype
  • ora-13126 : unable to determine class for spatial table string
  • ora-28237 : seed length too short
  • ora-28590 : agent control utility: illegal or badly formed command
  • ora-06420 : NETCMN: SID lookup failure
  • ora-13868 : Instance-wide SQL tracing on instance string is not enabled
  • ora-06811 : TLI Driver: could not set the IPX network number at init
  • ora-31072 : Too many child nodes in XMLType fragment for updateXML
  • ora-04017 : invalid value string (length = string) for parameter max_dump_file_size
  • ora-06706 : TLI Driver: service not found
  • ora-30556 : functional index is defined on the column to be modified
  • ora-38706 : Cannot turn on FLASHBACK DATABASE logging.
  • ora-02287 : sequence number not allowed here
  • ora-31673 : worker process interrupt for normal exit by master process
  • ora-24390 : Unsupported scrollable cursor operation
  • ora-16202 : Skip procedure requested to replace statement
  • ora-06030 : NETDNT: connect failed, unrecognized node name
  • ora-00036 : maximum number of recursive SQL levels (string) exceeded
  • ora-29821 : specified primary operator does not exist
  • ora-14700 : Object(s) owned by SYS cannot be locked by non-SYS user
  • ora-01987 : client os username is too long
  • ora-32154 : Anydata context not specified
  • ora-07222 : slspool: line printer spooler command exited with an error.
  • 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.