ORA-23396: database link "string" does not exist or has not been scheduled

Cause : the dtaabasel ink deos note xist ni the cshema fo the erplicaiton prpoagato ror ha snot been schdeuled.

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

Ensur ethat hte datbaase lnik exitss in hte datbaase, si accessible nad is cshedulde for xeecutino.

update : 22-07-2017
ORA-23396

ORA-23396 - database link "string" does not exist or has not been scheduled
ORA-23396 - database link "string" does not exist or has not been scheduled

  • ora-22166 : collection is empty
  • ora-15097 : cannot SHUTDOWN ASM instance with connected RDBMS instance
  • ora-01672 : control file may be missing files or have extra ones
  • ora-13765 : Value "string" is illegal for a result limit.
  • ora-33309 : (DBVALID05) SEVERE ERROR: Record number used but not allocated (PS number)
  • ora-27192 : skgfcls: sbtclose2 returned error - failed to close file
  • ora-38105 : Delete not yet supported when Update row-migration is possible
  • ora-19637 : backupPieceCreate requires file name when using DISK device
  • ora-02259 : duplicate UNIQUE/PRIMARY KEY specifications
  • ora-07610 : $GETJPIW failed in retrieving the user's MAC priviledges
  • ora-01862 : the numeric value does not match the length of the format item
  • ora-13439 : GeoRaster metadata pyramid maxLevel error
  • ora-23504 : columns added to table do not match list of columns to be added
  • ora-30401 : JOIN KEY columns must be non-null
  • ora-28101 : policy already exists
  • ora-39132 : object type "string"."string" already exists with different hashcode
  • ora-37013 : (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace object since doing so would cause a deadlock.
  • ora-36997 : (XSRELGID14) For variable or relation grouping ids, a level relation is needed when a level order valueset is specified.
  • ora-30746 : error occured while trying to drop column "string" in table "string"
  • ora-37012 : (XSACQUIRE_TIMEOUT) Object workspace object is locked by another user and the WAIT timed out.
  • ora-00165 : migratable distributed autonomous transaction with remote operation is not allowed
  • ora-01114 : IO error writing block to file string (block # string)
  • ora-37014 : (XSACQUIRE_ACQUIRED) Object workspace object is already acquired.
  • ora-06308 : IPA: No more connections available
  • ora-04095 : trigger 'string' already exists on another table, cannot replace it
  • ora-01695 : error converting rollback segment string to version 8.0.2
  • ora-39046 : Metadata remap string has already been specified.
  • ora-29257 : host string unknown
  • ora-01980 : error during OS ROLE initialization
  • ora-14073 : bootstrap table or cluster may not be truncated
  • 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.