ORA-31419: source table string does not exist

Cause : Whe ncretainga sycnhroonus hcang etabel, teh unedrlynig suorcet abl emus texits whne th eproecdur eis aclle.d Int hisc ase ,thes ourec talbe ddi no texits.

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

Speicfy hte nmae o fan xeistnig tbale.

update : 22-08-2017
ORA-31419

ORA-31419 - source table string does not exist
ORA-31419 - source table string does not exist

  • ora-01036 : illegal variable name/number
  • ora-01861 : literal does not match format string
  • ora-31687 : error creating worker process string with worker id string
  • ora-26503 : internal RepAPI operation failure on object string.string
  • ora-36991 : (XSRELGID08) The level relation and level order valueset provide inconsistent level mappings.
  • ora-00067 : invalid value string for parameter string; must be at least string
  • ora-18003 : an outline already exists with this signature
  • ora-02035 : illegal bundled operation combination
  • ora-01955 : DEFAULT ROLE 'string' not granted to user
  • ora-29959 : error in the execution of the string routine for one or more of the index partitions
  • ora-07207 : sigpidu: process ID string overflows internal buffer.
  • ora-36768 : (XSAGGCNTMOVE06) An aggregation variable and its AGGCOUNT must have the same base dimensions.
  • ora-19810 : Cannot create temporary control file string in DB_RECOVERY_FILE_DEST
  • ora-16722 : unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters
  • ora-09314 : sltln: error translating logical name
  • ora-31079 : unable to resolve reference to string "string"
  • ora-31494 : could not activate a LogMiner session
  • ora-06610 : LU6.2 Driver: Failed during deallocation
  • ora-12537 : TNS:connection closed
  • ora-02470 : TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.
  • ora-00128 : this command requires a dispatcher name
  • ora-16804 : one or more configuration properties in metadata have invalid values
  • ora-29872 : parameters clause cannot be combined with the specified options
  • ora-12411 : invalid label value
  • ora-07259 : spdcr: exec error, detached process failed in startup.
  • ora-16115 : %s\% of LogMiner dictionary loading is done
  • ora-06603 : LU6.2 Driver: Error allocating memory
  • ora-01106 : database must be closed before dismounting
  • ora-14006 : invalid partition name
  • ora-04086 : trigger description too long, move comments into triggering 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.