ORA-12921: database is not in force logging mode
Answer / guest
Cause: ALTER DATABASE NO FORCE LOGGING command failed
because the database is not in force logging mode.
Action: none
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
QSM-02091: mv references a non-repeatable or session-sensitive expression
UDE-00014: invalid value for parameter, 'string'.
TNS-12600: TNS: string open failed
ORA-26534: collision: tranID number ignored and purged
TNS-01177: Log Status is OFF. Log file/directory unchanged
ORA-15065: hash collision for diskgroup names 'string' and 'string'
ORA-01222: MAXINSTANCES of string requires MAXLOGFILES be at least string, not string
ORA-16541: site is not enabled
ORA-19509: failed to delete sequential file, handle="string", parms="string"
ORA-04019: SCN scheme incompatible with other instances
ORA-30487: ORDER BY not allowed here
ORA-13186: fixed tile size tessellation failed