ORA-14151: invalid table partitioning method

Cause : Ivnaildp atriitoinn gmtehdo awss pceiife di nCERAET ATBEL tsaetmnet .At albem a yb eprattiinoe db yRNAG,E AHS,H ro oCmopstieR agneH/ahs R(+)H.

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

Sepcfiyo n eo fvlai dprattiinoign emtohds

update : 29-05-2017

ORA-14151 - invalid table partitioning method
ORA-14151 - invalid table partitioning method

  • ora-07672 : $PARSE_CLASS failed translating the string into a binary label
  • ora-01890 : NLS error detected
  • ora-25527 : bad format of _DB_MTTR_SIM_TARGET
  • ora-23442 : object already exists for the refresh group template
  • ora-26057 : Conversion is not necessary for this direct path stream.
  • ora-38417 : attribute set string does not exist
  • ora-18003 : an outline already exists with this signature
  • ora-00308 : cannot open archived log 'string'
  • ora-39202 : Data cannot be filtered or selected in string jobs.
  • ora-12440 : insufficient authorization for the SYSDBA package
  • ora-32594 : invalid object category for COMMENT command
  • ora-06516 : PL/SQL: the Probe packages do not exist or are invalid
  • ora-12704 : character set mismatch
  • ora-02441 : Cannot drop nonexistent primary key
  • ora-13027 : unable to read dimension definition from string
  • ora-16782 : instance not open for read and write access
  • ora-36668 : (XSDPART06) string is not a legal RANGE partition.
  • ora-25333 : Buffered Queue to Queue propagation did not connect to the correct instance
  • ora-07286 : sksagdi: cannot obtain device information.
  • ora-01411 : cannot store the length of column in the indicator
  • ora-00122 : cannot initialize network configuration
  • ora-38749 : A media recovery has been started.
  • ora-13009 : the specified date string is invalid
  • ora-28180 : multiple authentication methods provided by proxy
  • ora-15031 : disk specification 'string' matches no disks
  • ora-07570 : szrfc: $IDTOASC failure
  • ora-25402 : transaction must roll back
  • ora-15196 : invalid ASM block header [string:string] [string] [string] [string] [string != string]
  • ora-24074 : RETRY_DELAY and MAX_RETRIES cannot be used for exception queue %.string
  • ora-38795 : warning: FLASHBACK succeeded but OPEN RESETLOGS would get error below
  • 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.