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 : 25-09-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-27124 : unable to detach from shared memory segment
  • ora-16246 : User initiated abort apply successfully completed
  • ora-36640 : (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype.
  • ora-06811 : TLI Driver: could not set the IPX network number at init
  • ora-37001 : You have one or more attached but unupdated analytic workspaces.
  • ora-23389 : obsolete procedure; drop objects and recreate using new master
  • ora-00212 : block size string below minimum required size of string bytes
  • ora-24508 : Buffer is not aligned correctly.
  • ora-07284 : sksaprd: volume size specification not terminated properly.
  • ora-30477 : The input select_clause is incorrectly specified
  • ora-28010 : cannot expire external or global accounts
  • ora-32578 : password for SYS already specified
  • ora-37129 : (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. All static MODEL statements must precede all RELATION statements over the bases of the COMPRESSED COMPOSITE.
  • ora-14048 : a partition maintenance operation may not be combined with other operations
  • ora-30016 : undo tablespace 'string' is already in use by this instance
  • ora-00608 : testing error [string] [string] [string] [string] [string]
  • ora-37144 : (MDQUERY01) string is not a valid metadata object type for MDQUERY.
  • ora-07622 : smscre: $CREATE failure
  • ora-07491 : scgrcl: cannot cancel lock request.
  • ora-30047 : Internal event for kti tracing
  • ora-22303 : type "string"."string" not found
  • ora-01466 : unable to read data - table definition has changed
  • ora-00448 : normal completion of background process
  • ora-32775 : cannot change size attributes of read only tablespace string
  • ora-30347 : a table name is required to qualify the column specification
  • ora-02202 : no more tables permitted in this cluster
  • ora-15076 : Emulating I/O errors on the OSM disk
  • ora-30505 : system triggers should not reference a column in a WHEN clause
  • ora-02476 : can not create index due to parallel direct load on table
  • ora-19105 : invalid XQueryX: expected text node - got string
  • 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.