ORA-01312: Specified table/column does not exist

Cause : The table/column specified in the lcr_mine call does not exist at the the specified SCN. The table/column definition has to exist at the start SCN specified for lcr_mine to be able to identify the table/column correctly.

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

Create a LogMiner session at a start SCN at which the table definition is available.

update : 17-08-2017
ORA-01312

ORA-01312 - Specified table/column does not exist
ORA-01312 - Specified table/column does not exist

  • ora-01655 : unable to extend cluster string.string by string in tablespace string
  • ora-33072 : (XSAGDNGL35) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must be specified for every relation dimensioned by that hierarchy dimension.
  • ora-10370 : parallel query server kill event
  • ora-24411 : Session pool already exists.
  • ora-37108 : (XSVPART08) workspace object has an AGGCOUNT, but workspace object does not.
  • ora-31071 : Invalid database username or GUID string
  • ora-27075 : SSTMOFRC constant too large
  • ora-08100 : index is not valid - see trace file for diagnostics
  • ora-19712 : table name exceeds maximum length of string
  • ora-29510 : name, string.string, already used by an existing object
  • ora-31001 : Invalid resource handle or path name "string"
  • ora-19255 : XQ0035 - too many declarations of string in imported schemas
  • ora-39034 : Table string does not exist.
  • ora-31010 : XML element index string exceeds maximum insertion index string
  • ora-32695 : HTI: Not enough memory
  • ora-38490 : invalid name: quotes do not match
  • ora-32588 : supplemental logging attribute string exists
  • ora-30157 : An invalid argument was given to operating system call
  • ora-01093 : ALTER DATABASE CLOSE only permitted with no sessions connected
  • ora-25154 : column part of USING clause cannot have qualifier
  • ora-27150 : attempt to notify process of pending oradebug call failed
  • ora-06779 : TLI Driver: error reading ccode
  • ora-31225 : DBMS_LDAP: invalid BER_ELEMENT
  • ora-04011 : sequence string must range between string and string
  • ora-06260 : NETNTT: cannot write to remote process
  • ora-39099 : cannot create index for "string" on master table string
  • ora-07615 : $CHANGE_CLASS failed in retrieving the specified file label
  • ora-37003 : (AWLISTALL01) number readers
  • ora-22318 : input type is not an array type
  • ora-36671 : (XSDPART09) Leaves of workspace object have different datatypes. A partition dimension cannot have more than one datatype when RANGE partitioning is used.
  • 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.