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-05-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-37026 : (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.
  • ora-29315 : tablespace 'string' has been recreated
  • ora-38731 : Expected version string does not match string in log header.
  • ora-32589 : unable to drop minimal supplemental logging
  • ora-30457 : 'string.string' cannot be refreshed because of unmnanaged NOT NULL columns in container
  • ora-39040 : Schema expression "string" must identify exactly one schema.
  • ora-33082 : (XSAGDNGL41) In AGGMAP workspace object, the non-dimensioned valueset workspace object must have a parent QDR in its VALUESET statement over the VALUESET's base dimension.
  • ora-29975 : Cannot register a query in the middle of an active transaction
  • ora-30376 : prevent sharing of a parsed query of an explain rewrite session
  • ora-06261 : NETNTT: nrange() failed
  • ora-29951 : warning in the execution of ODCIINDEXSPLITPARTITION routine
  • ora-38746 : error occurred while restoring data block (file# string, block# string)
  • ora-19588 : %s recid string stamp string is no longer valid
  • ora-00163 : internal database name length string is greater than maximum (string)
  • ora-28554 : pass-through SQL: out of cursors
  • ora-30558 : internal error [string] in function based index
  • ora-12333 : database (link name string) is not mounted
  • ora-15107 : missing or invalid ASM disk name
  • ora-13337 : failure in concatenating LRS polygons
  • ora-07303 : ksmcsg: illegal database buffer size.
  • ora-14041 : partition bound may not be specified for resulting partitions
  • ora-36161 : (XSAGGRRUVCV) Aggregation variable workspace object cannot have itself as a COUNTVAR.
  • ora-34177 : (MXCHGDCL19) number cannot be deleted because one or more partitioned variables instantiate it.
  • ora-16166 : LGWR network server failed to send remote message
  • ora-16083 : LogMiner session has not been created
  • ora-16401 : archivelog rejected by RFS
  • ora-13030 : Invalid dimension for the SDO_GEOMETRY object
  • ora-27371 : jobs of type EXECUTABLE are not supported on this platform
  • ora-21605 : property [string] is not a property of value instances
  • ora-01412 : zero length not allowed for this datatype
  • 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.