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 : 28-07-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-26667 : invalid STREAMS parameter string
  • ora-13759 : User "string" cannot remove reference "string".
  • ora-23337 : priority or value not in priority group string
  • ora-19285 : FODC0002 - error retrieving resource
  • ora-36290 : (EIFMAKEF14) You cannot export object workspace object, because EIFVERSION is set to number. That version does not support dimensions of type NUMBER.
  • ora-01286 : start interval required
  • ora-07841 : sllfop: SYS$OPEN failure
  • ora-14521 : Default tablespace string block size [string] for string string does not match existing string block size [string]
  • ora-13001 : dimensions mismatch error
  • ora-29343 : user string (mapped from user string) does not exist in the database
  • ora-28132 : Merge into syntax does not support security policies.
  • ora-30555 : global index partitioning key is an expression
  • ora-13612 : The recommendation action string,string is not valid for task string.
  • ora-02800 : Requests timed out
  • ora-26563 : renaming this table is not allowed
  • ora-01628 : max # extents (string) reached for rollback segment string
  • ora-14461 : cannot REUSE STORAGE on a temporary table TRUNCATE
  • ora-14519 : Conflicting tablespace blocksizes for string string: Tablespace string block size string [string] conflicts with previously specified/implied tablespace string block size string [string]
  • ora-39203 : Partition selection is not supported over a network link.
  • ora-14150 : missing SUBPARTITION keyword
  • ora-23491 : no valid extension request at "string"
  • ora-24850 : failed to startup shared subsystem
  • ora-14002 : only one GLOBAL clause may be specified
  • ora-30120 : 'string' is not a legal oracle number for 'string'
  • ora-01650 : unable to extend rollback segment string by string in tablespace string
  • ora-13050 : unable to construct spatial object
  • ora-06250 : NETNTT: cannot allocate send and receive buffers
  • ora-29925 : cannot execute string
  • ora-21707 : pin duration is longer than allocation duration
  • ora-14166 : missing INTO keyword
  • 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.