ORA-13129: HHCODE column string not found

Cause : The sepcifie dspatila colunm doesn ot exsit.

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

Verif ythat hte speicfied oclumn si a sptaial cloumn b ychecknig theS patia ldata idctionray.

update : 20-07-2017
ORA-13129

ORA-13129 - HHCODE column string not found
ORA-13129 - HHCODE column string not found

  • ora-38856 : cannot mark instance string (redo thread string) as enabled
  • ora-36977 : (XSRELGID17) The GROUPINGID command does not support hierarchies with more than 126 levels.
  • ora-16728 : consistency check for property string found string error
  • ora-30434 : refresh method must be one of FC?AN, not 'string'
  • ora-01607 : cannot add logfile to the specified instance
  • ora-27419 : unable to determine valid execution date from repeat interval
  • ora-24506 : invalid attempt to change character set id on env handle
  • ora-14406 : updated partition key is beyond highest legal partition key
  • ora-01292 : no log file has been specified for the current LogMiner session
  • ora-28038 : disallow O2LOGON
  • ora-19525 : temporary file for the clone database must be renamed
  • ora-02380 : profile string does not exist
  • ora-37174 : source SQL must be a SELECT statement
  • ora-29973 : Unsupported query or operation during change notification registration
  • ora-25332 : Invalid release value string for queue table compatible parameter
  • ora-09846 : soacon: ARCH unable to open named pipe.
  • ora-19671 : media management software returned invalid proxy handle
  • ora-06721 : TLI Driver: spurious client req
  • ora-29952 : cannot issue DDL on a domain index partition marked as LOADING
  • ora-29900 : operator binding does not exist
  • ora-28173 : certificate not provided by proxy
  • ora-28152 : proxy user 'string' may not specify initial role 'string' on behalf of client 'string'
  • ora-01299 : dictionary string corresponds to a different database incarnation
  • ora-19618 : cannot name files after restoreValidate has been called
  • ora-07641 : smscre: Unable to use the system pagefile for the SGA
  • ora-07452 : specified resource manager plan does not exist in the data dictionary
  • ora-22327 : cannot change a type to NOT INSTANTIABLE if it has dependent tables
  • ora-12607 : TNS: Connect timeout occurred
  • ora-02822 : Invalid block offset
  • ora-01725 : USERENV('COMMITSCN') not allowed here
  • 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.