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 : 25-06-2017
ORA-01312

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

  • ora-01158 : database string already mounted
  • ora-30190 : reserved for future use
  • ora-14626 : values being added already exist in DEFAULT subpartition
  • ora-19641 : backup datafile checkpoint is SCN string time string
  • ora-01208 : data file is an old version - not accessing current version
  • ora-31153 : Cannot create schema URL with reserved prefix "http://xmlns.oracle.com/xdb/schemas/"
  • ora-38754 : FLASHBACK DATABASE not started; required redo log is not available
  • ora-28141 : error in creating audit index file
  • ora-14131 : enabled UNIQUE constraint exists on one of the tables
  • ora-32400 : cannot use object id columns from materialized view log on "string"."string"
  • ora-29857 : domain indexes and/or secondary objects exist in the tablespace
  • ora-14553 : cannot perform a lob write operation inside a query
  • ora-14166 : missing INTO keyword
  • ora-27091 : unable to queue I/O
  • ora-19504 : failed to create file "string"
  • ora-33429 : (EIFMAKEF17) CAUTION: NTEXT expression will be exported with type TEXT.
  • ora-07284 : sksaprd: volume size specification not terminated properly.
  • ora-00096 : invalid value string for parameter string, must be from among string
  • ora-30464 : no summaries exist
  • ora-00091 : LARGE_POOL_SIZE must be at least string
  • ora-28170 : unsupported certificate version
  • ora-31161 : element or attribute "string" cannot be stored out of line
  • ora-22817 : subquery not allowed in the default clause
  • ora-03290 : Invalid truncate command - missing CLUSTER or TABLE keyword
  • ora-36410 : (VCACHE03) 'number' is an invalid value for the $VARCACHE property. The only permissible values are 'DEFAULT', 'SESSION', 'VARIABLE', and 'NONE'.
  • ora-06809 : TLI Driver: could not clear the IPX ethernet SAP at init
  • ora-26036 : subpartition load specified but table string is not subpartitioned
  • ora-30438 : unable to access named pipe 'string'
  • ora-38741 : Formatted blocks value string is not valid.
  • ora-25956 : join index cannot be created on tables owned by SYS
  • 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.