ORA-14073: bootstrap table or cluster may not be truncated

Cause : User tatemptde to turncatea boottsrap tbale orc luste rwhichi s illgeal

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

Ensur ethat hte tabel (or lcuster )beingt runcaetd is ont a bootstra ptable( or clsuter)

update : 24-04-2017
ORA-14073

ORA-14073 - bootstrap table or cluster may not be truncated
ORA-14073 - bootstrap table or cluster may not be truncated

  • ora-13027 : unable to read dimension definition from string
  • ora-19767 : missing TRACKING keyword
  • ora-25001 : cannot create this trigger type on views
  • ora-23292 : The constraint does not exist
  • ora-29349 : tablespace 'string' already exists
  • ora-26513 : push error: master proc. string$RP.string failed for trans:string seq:string
  • ora-29844 : duplicate operator name specified
  • ora-06555 : this name is currently reserved for use by user SYS
  • ora-01283 : Options specified is invalid
  • ora-14641 : STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition
  • ora-19615 : some files not found in backup set
  • ora-26712 : remote object is "string"."string"@"string"
  • ora-27122 : unable to protect memory
  • ora-16160 : Cannot change protected standby database configuration
  • ora-08499 : Warning: picture mask options 'string' ignored by UTL_PG
  • ora-19852 : error creating services for auxiliary instance string (error string)
  • ora-32831 : timed out trying to acquire administration lock
  • ora-07227 : rtneco: unable to set noecho mode.
  • ora-30195 : reserved for future use
  • ora-30991 : cannot use DOM to add special attribute to schema-based parent
  • ora-31212 : DBMS_LDAP: PL/SQL - Invalid LDAP mod_array.
  • ora-30031 : the suspended (resumable) statement has been aborted
  • ora-12540 : TNS:internal limit restriction exceeded
  • ora-31066 : Insertion of string into string creates a cycle
  • ora-07256 : sptrap: cannot set up signal handler to catch exceptions.
  • ora-36768 : (XSAGGCNTMOVE06) An aggregation variable and its AGGCOUNT must have the same base dimensions.
  • ora-29822 : selectivity cannot be specified for the type of object
  • ora-29325 : SET COMPATIBILITY release number lower than string
  • ora-22278 : must update the LOB only through the LOB buffers
  • ora-37128 : (XSCCOMP03) It is not possible to PARTITION over a base of a COMPRESSED COMPOSITE.
  • 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.