ORA-13124: unable to determine column id for column string

Cause : This is an internal error.

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

Contact Oracle Support Services.

update : 24-07-2017

ORA-13124 - unable to determine column id for column string
ORA-13124 - unable to determine column id for column string

  • ora-29844 : duplicate operator name specified
  • ora-23405 : refresh group number string does not exist
  • ora-28515 : cannot get external object definitions from string
  • ora-06765 : TLI Driver: error awaiting orderly release
  • ora-23363 : mismatch of mview base table "string" at master and mview site
  • ora-27029 : skgfrtrv: sbtrestore returned error
  • ora-29974 : Internal event for PL/SQL debugging
  • ora-19770 : invalid change tracking file name
  • ora-15127 : ASM file name 'string' cannot use templates
  • ora-36686 : (XSDPART24) Value number is not in partition number.
  • ora-25408 : can not safely replay call
  • ora-09820 : Conversion of class string to numeric representation failed.
  • ora-01901 : ROLLBACK keyword expected
  • ora-02299 : cannot validate (string.string) - duplicate keys found
  • ora-38404 : schema extension not allowed for the attribute set name
  • ora-29356 : These parameters can be specified only for directives that refer to consumer groups
  • ora-06578 : output parameter cannot be a duplicate bind
  • ora-10617 : Cannot create rollback segment in dictionary managed tablespace
  • ora-04930 : open sequence number failed or initial state is valid
  • ora-29887 : cannot support row movement if domain index defined on table
  • ora-22276 : invalid locator for LOB buffering
  • ora-29287 : invalid maximum line size
  • ora-30458 : 'string.string' cannot be refreshed because the refresh mask is string
  • ora-19773 : must specify change tracking file name
  • ora-31508 : invalid parameter value for synchronous change set
  • ora-13044 : the specified tile size is smaller than the tolerance
  • ora-33274 : (DBERR07) Timed out while trying to lock analytic workspace string for string.
  • ora-01938 : IDENTIFIED BY must be specified for CREATE USER
  • ora-07624 : smsdes: $DGBLSC failure
  • ora-32060 : channel failure
  • 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.