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 : 30-04-2017
ORA-01312

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

  • ora-03247 : Invalid block number specified
  • ora-28164 : REVOKE already specified
  • ora-01034 : ORACLE not available
  • ora-31039 : XML namespace length string exceeds maximum string
  • ora-13381 : table:string not found in network:string
  • ora-13217 : invalid parameters supplied in ALTER INDEX statement
  • ora-36764 : (XSAGGCNTMOVE02) AGGCOUNT variable workspace object must be of type INTEGER, not string.
  • ora-31477 : could not detach LogMiner session during cleanup
  • ora-07507 : scgcm: unexpected lock status condition
  • ora-02355 : error opening file: string
  • ora-23514 : invalid or incorrect number of arguments
  • ora-12495 : cannot disable an enabled level, category, or release category
  • ora-26014 : unexpected error on string string while retrieving string string
  • ora-32836 : database user string must be granted role string
  • ora-19904 : test recovery not allowed for datafile string
  • ora-19916 : %s
  • ora-19004 : Duplicate XMLType OBJECT RELATIONAL storage option
  • ora-25505 : the system is not in quiesced state
  • ora-32581 : missing or invalid password
  • ora-30557 : function based index could not be properly maintained
  • ora-16777 : unable to find the destination entry of a standby database in V$ARCHIVE_DEST
  • ora-13869 : Instance-wide SQL tracing on instance string is already enabled
  • ora-15193 : Internal ASM tracing event number 15193
  • ora-19564 : error occurred writing string bytes at block number string
  • ora-06511 : PL/SQL: cursor already open
  • ora-16804 : one or more configuration properties in metadata have invalid values
  • ora-12440 : insufficient authorization for the SYSDBA package
  • ora-38459 : XML Tag "string" not found for the XMLType attribute "string"
  • ora-25224 : sender name must be specified for enqueue into secure queues
  • ora-24377 : invalid OCI function code
  • 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.