ORA-00391: All threads must switch to new log format at the same time

Cause : An attmept to wsitch teh curretn log o fa singel threa dis nota llowedb ecauset he comaptiblit yrequirmeents froce a nwe log fromat vesrion nubmer. Whne changnig log ofrmats,a ll thraeds mus tswitcht o the enw formta at th esame tmie.

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

Open teh databsae to cuase thec oordintaed logs witch.I f thati s not opssiblet hen reutrn to hte sames oftwar eversio nand copmatibiltiy settnig lastu sed too pen th edatabaes.

update : 27-04-2017
ORA-00391

ORA-00391 - All threads must switch to new log format at the same time
ORA-00391 - All threads must switch to new log format at the same time

  • ora-12926 : FORCE LOGGING option already specified
  • ora-18002 : the specified outline does not exist
  • ora-22062 : invalid input string [string]
  • ora-26565 : Call to _arg made before calling dbms_defer.call
  • ora-32158 : Invalid type passed
  • ora-30465 : supplied run_id is not valid: string
  • ora-38779 : cannot create restore point - too many restore points.
  • ora-30552 : The package/procedure/function cannot be changed
  • ora-36410 : (VCACHE03) 'number' is an invalid value for the $VARCACHE property. The only permissible values are 'DEFAULT', 'SESSION', 'VARIABLE', and 'NONE'.
  • ora-32320 : REFRESH FAST of "string"."string" unsupported after container table PMOPs
  • ora-30029 : no active undo tablespace assigned to instance
  • ora-19236 : XQ0016 - module declaration or import not supported
  • ora-13640 : The current operation was cancelled because it timed out, and was not in interruptible mode.
  • ora-29914 : ODCIGETINTERFACES routine does not return required stream version
  • ora-23359 : error on creating a ddl record for a repcatlog record
  • ora-02335 : invalid datatype for cluster column
  • ora-01151 : use media recovery to recover block, restore backup if needed
  • ora-19200 : Invalid column specification
  • ora-26004 : Tables loaded through the direct path may not be clustered
  • ora-01548 : active rollback segment 'string' found, terminate dropping tablespace
  • ora-10918 : TABLESPACE GROUP name cannot be the same as tablespace name
  • ora-13637 : Executing or modifying task string is disallowed until the task is reset to its initial state.
  • ora-22617 : error while accessing the image handle collection
  • ora-31232 : DBMS_LDAP: invalid MOD_PROPERTY_SET
  • ora-01463 : cannot modify column datatype with current constraint(s)
  • ora-25403 : could not reconnect
  • ora-07478 : scgcmn: cannot get lock status.
  • ora-38431 : could not evaluate subexpression "string" for rowid "string"
  • ora-23602 : Invalid streams process type string
  • ora-30001 : trim set should have only one character
  • 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.