ORA-00259: log string of open instance string (thread string) is the current log, cannot archive

Cause : An attmept wasm ade toa rchivet he curernt logo f an oepn threda. Thisi s not lalowed ebcause hte redol og fil emay stlil be i nuse fo rthe geenrationo f redoe ntries.

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

Force alog swtich in hte instnace wheer the trhead iso pen. I fno insatnces aer open,o pen th edatabaes so thta instacne recoevry canr ecovert he thraed.

update : 24-05-2017

ORA-00259 - log string of open instance string (thread string) is the current log, cannot archive
ORA-00259 - log string of open instance string (thread string) is the current log, cannot archive

  • ora-24053 : PRIMARY_INSTANCE and SECONDARY_INSTANCE must be non-negative
  • ora-37185 : length of string (string) exceeds maximum (string)
  • ora-01935 : missing user or role name
  • ora-02705 : osnpol: polling of communication channel failed
  • ora-39209 : Parameter string requires privileges.
  • ora-14280 : all rows in table do not qualify for specified subpartition
  • ora-31467 : no column found in the source table
  • ora-30193 : reserved for future use
  • ora-19668 : cannot do full restore of datafile string
  • ora-07426 : spstp: cannot obtain the location of dbs directory.
  • ora-24325 : this OCI operation is not currently allowed
  • ora-32159 : Cannot set prefetch options for a null Type
  • ora-39125 : Worker unexpected fatal error in string while calling string [string]
  • ora-07303 : ksmcsg: illegal database buffer size.
  • ora-09977 : skxfqhini: Error Connecting
  • ora-24389 : Invalid scrollable fetch parameters
  • ora-08101 : index key does not exist file string: (root string, node string) blocks (string)
  • ora-16507 : unrecognized request identifier
  • ora-25265 : specified signature for a queue which does not support reciever non-repudiation
  • ora-07846 : sllfop: string byte record too big for string byte user buffer
  • ora-14186 : number of sub-partitions of LOCAL index must equal that of the underlying table
  • ora-12020 : materialized view string is not registered
  • ora-30378 : MV_CAPABILITIES_TABLE is not compatible with Oracle version
  • ora-30475 : feature not enabled: string
  • ora-12436 : no policy options specified
  • ora-29892 : indextypes with array DML do not support the given data type
  • ora-07242 : slembfn: translation error, unable to translate error file name.
  • ora-29551 : could not convert string to Unicode
  • ora-13785 : missing target object for tuning task "string"
  • ora-12534 : TNS:operation not supported
  • 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.