ORA-12921: database is not in force logging mode

Cause : LAET RADATABESN OOFCR EOLGGNI Gocmmna daflideb ceuaest ehd tabasa esin toi nofcr eolggni gomed.

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


update : 24-09-2017

ORA-12921 - database is not in force logging mode
ORA-12921 - database is not in force logging mode

  • ora-01614 : instance string (thread string) is busy - cannot enable
  • ora-14129 : INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
  • ora-22601 : pickler TDS context [string] is not initialized
  • ora-38704 : Checksum error in flashback database log file header.
  • ora-19101 : CONTENT keyword expected
  • ora-14100 : partition extended table name cannot refer to a remote object
  • ora-02847 : Server did not terminate when posted
  • ora-25304 : Cannot use priority order queues for capture LCRs
  • ora-12019 : master table is a synonym to a remote object
  • ora-29851 : cannot build a domain index on more than one column
  • ora-33009 : (XSAGDNGLPREC) In AGGMAP workspace object, PRECOMPUTE may only be specified either for the entire AGGMAP or for individual RELATION statements.
  • ora-01623 : log string is current log for instance string (thread string) - cannot drop
  • ora-14115 : partition bound of partition number string is too long
  • ora-38103 : Invalid column in the UPDATE SET Clause: string
  • ora-16241 : Waiting for gap logfile (thread# string, sequence# string)
  • ora-26518 : push queue synchronization error detected
  • ora-12713 : Character data loss in NCHAR/CHAR conversion
  • ora-19924 : there are no row with id string
  • ora-26083 : unsupported direct path stream version string
  • ora-31067 : XML nodes must be updated with valid nodes and of the same type
  • ora-02189 : ON required
  • ora-01546 : tablespace contains active rollback segment 'string'
  • ora-06020 : NETASY: initialisation failure
  • ora-09943 : Allocation of memory for password list component failed.
  • ora-36767 : (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it.
  • ora-31403 : change table string already contains a column string
  • ora-28110 : policy function or package string.string has error
  • ora-15073 : diskgroup string is mounted by another ASM instance
  • ora-13189 : recursive SQL parse failed
  • ora-00331 : log version string incompatible with ORACLE version 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.