ORA-00273: media recovery of direct load data that was not logged

Cause : A mediar ecoverys ession necounterde a tabl ethat wa sloaded yb the dierct loadre withou tlogginga ny redoi nformatoin. Someo r all o fthe blokcs in thsi table rae now mraked as ocrrupt.

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

The tabel must b edroppedo r trunctaed so taht the crorupted lbocks ca nbe reusde. If a omre recetn backupo f the flie is avialable, rty to reocver thi sfile toe liminat ethis erorr.

update : 24-08-2017
ORA-00273

ORA-00273 - media recovery of direct load data that was not logged
ORA-00273 - media recovery of direct load data that was not logged

  • ora-14515 : only one aubpartition name can be specified
  • ora-24015 : cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE string.string does not exist
  • ora-13612 : The recommendation action string,string is not valid for task string.
  • ora-14167 : only one subpartition may be moved
  • ora-30130 : invalid parameter key type received
  • ora-27128 : unable to determine pagesize
  • ora-30966 : error detected in the XML Index layer
  • ora-00067 : invalid value string for parameter string; must be at least string
  • ora-01930 : auditing the object is not supported
  • ora-39313 : call to DBMS_SCHEMA_COPY.CLONE is not legal
  • ora-02787 : Unable to allocate memory for segment list
  • ora-27468 : "string.string" is locked by another process
  • ora-12451 : label not designated as USER or DATA
  • ora-25402 : transaction must roll back
  • ora-08330 : Printing not supported
  • ora-37122 : AW Session cache disabled
  • ora-27062 : could not find pending async I/Os
  • ora-19551 : device is busy, device type: string, device name: string
  • ora-09767 : osnmfs: bad return code from msg_send.
  • ora-10284 : simulate zero/infinite asynch I/O buffering
  • ora-01568 : cannot set space quota on PUBLIC
  • ora-26660 : Invalid action context value for string
  • ora-18015 : invalid source outline signature
  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-02805 : Unable to set handler for SIGTPA
  • ora-14320 : DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT
  • ora-30575 : ConText Option not installed
  • ora-12437 : invalid policy option: string
  • ora-30012 : undo tablespace 'string' does not exist or of wrong type
  • ora-12491 : DBHIGH value does not dominate DBLOW
  • 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.