ORA-01239: database must be in ARCHIVELOG mode to use external cache

Cause : An onlnie fileu ses ane xterna lcache,b ut thed atabas eis in ONARCHIVLEOG mod.e Sincea n extenral caceh may rqeuire mdeia recvoery thsi can nto be alolwed.

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

Changed atabas eto be ni ARCHIEVLOG moed or don ot usea n extenral caceh.

update : 22-09-2017

ORA-01239 - database must be in ARCHIVELOG mode to use external cache
ORA-01239 - database must be in ARCHIVELOG mode to use external cache

  • ora-36714 : (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.
  • ora-19635 : input and output filenames are identical: string
  • ora-10268 : Don't do forward coalesce when deleting extents
  • ora-36636 : (XSDUNION04) The unique concat dimension workspace object cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension.
  • ora-16545 : unable to get response
  • ora-30682 : improper value for argument OPTION_FLAGS
  • ora-19109 : RETURNING keyword expected
  • ora-27165 : tried to join thread that does not exist
  • ora-24029 : operation not allowed on a single-consumer queue
  • ora-14165 : MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations
  • ora-12166 : TNS:Client can not connect to HO agent.
  • ora-00953 : missing or invalid index name
  • ora-00569 : Failed to acquire global enqueue.
  • ora-36220 : (XSLPDSC01) All dimensions in LIST number are also in the IGNORE clause.
  • ora-24318 : call not allowed for scalar data types
  • ora-24027 : AQ HTTP propagation encountered error, status-code string, string
  • ora-12924 : tablespace string is already in force logging mode
  • ora-09273 : szrfc: error verifying role name
  • ora-21503 : program terminated by fatal error
  • ora-26099 : direct path context is already prepared
  • ora-03237 : Initial Extent of specified size cannot be allocated in tablespace (string)
  • ora-29544 : invalid type
  • ora-31215 : DBMS_LDAP: PL/SQL - Invalid LDAP mod value.
  • ora-23305 : internal deferred RPC error: string
  • ora-40215 : model string is incompatible with current operation
  • ora-39159 : cannot call this function from a non-Data Pump process
  • ora-06780 : TLI Driver: recv error code failed
  • ora-24031 : invalid value, string should be non-NULL
  • ora-27460 : cannot execute disabled job "string.string"
  • ora-12830 : Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE
  • 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.