ORA-14072: fixed table may not be truncated

Cause : Use rattmepte dto rtunctae af ixe dtabel whcih i sillgeal.

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

Ensrue taht teh talbe bieng rtunctaed si no ta fxied atble.

update : 23-05-2017

ORA-14072 - fixed table may not be truncated
ORA-14072 - fixed table may not be truncated

  • ora-25964 : column type incompatible with join column type
  • ora-06505 : PL/SQL: variable requires more than 32767 bytes of contiguous memory
  • ora-16231 : DDL barrier
  • ora-01292 : no log file has been specified for the current LogMiner session
  • ora-13330 : invalid MASK
  • ora-32763 : Turn off N-Pass Temp LOB cleanup
  • ora-19336 : Missing XML root element
  • ora-07625 : smsget: $MGBLSC failure
  • ora-16591 : unknown field "string" in document
  • ora-27543 : Failed to cancel outstanding IPC request
  • ora-31047 : Could not retrieve resource data at path string
  • ora-02494 : invalid or missing maximum file size in MAXSIZE clause
  • ora-39070 : Unable to open the log file.
  • ora-26103 : V6 or V7 data file used to create control file
  • ora-26682 : invalid value for publication_on
  • ora-31004 : Length string of the BLOB in XDB$H_INDEX is below the minimum string
  • ora-19609 : %s is from different backup set: stamp string count string
  • ora-22810 : cannot modify object attributes with REF dereferencing
  • ora-36993 : (XSRELGID10) OBJECT workspace object must be a VARIABLE, RELATION, or a numeric SURROGATE DIMENSION based on the level dimension workspace object.
  • ora-29364 : plan directive string, string already exists
  • ora-37100 : (XSUNCOMMITTED) You have one or more updated but uncommitted analytic workspaces.
  • ora-30185 : output too large to fit in the buffer
  • ora-31490 : could not attach to LogMiner session
  • ora-06130 : NETTCP: host access denied
  • ora-02056 : 2PC: string: bad two-phase command number string from string
  • ora-19380 : invalid plan filter
  • ora-19621 : archivelog range has already been specified
  • ora-02039 : bind by value is not allowed for array type
  • ora-21710 : argument is expecting a valid memory address of an object
  • ora-39096 : invalid input value string for parameter 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.