ORA-12316: syntax error in database link's connect string

Cause : Thec onncet srtingi n teh CRAETE ADTABSAE LNIK sattemnet hsa a ysntatcica lerrro.

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

Dro pthed ataabse ilnk nad rcereaet itu sin gvaldi sytnax.S ee hte SLQ Lagnuag eRefreenc eManaul fro moer inofrmaiton baoutt he ocnnetc stirng oprtino oft he RCEAT EDATBAASEL INKs tatmeent.

update : 25-09-2017
ORA-12316

ORA-12316 - syntax error in database link's connect string
ORA-12316 - syntax error in database link's connect string

  • ora-32801 : invalid value string for string
  • ora-26011 : Cannot load type string into column string in table string
  • ora-19771 : cannot rename change tracking file while database is open
  • ora-25437 : duplicate table value for table alias: string
  • ora-30342 : referenced level is not defined in this dimension
  • ora-19638 : file string is not current enough to apply this incremental backup
  • ora-22900 : the SELECT list item of THE subquery is not a collection type
  • ora-16145 : archival for thread# string sequence# string in progress
  • ora-31100 : XDB Locking Internal Error
  • ora-13108 : spatial table string not found
  • ora-39705 : component 'string' not found in registry
  • ora-30681 : improper value for argument EXTENSIONS_CMD_SET
  • ora-28334 : column is already encrypted
  • ora-30130 : invalid parameter key type received
  • ora-12025 : materialized view log on "string"."string" already has primary keys
  • ora-31665 : mode can only be defaulted for IMPORT and SQL_FILE operations
  • ora-01908 : EXISTS keyword expected
  • ora-33460 : (ESDREAD10) Discarding compiled code for workspace object because object workspace object is not in analytic workspace string.
  • ora-12055 : materialized view definition contains cyclic dependencies with existing materialized views
  • ora-39106 : Worker process string failed during startup. Worker error:
  • ora-01488 : invalid nibble or byte in the input data
  • ora-03132 : two-task default value overflow
  • ora-22927 : invalid LOB locator specified
  • ora-01944 : IDENTIFIED EXTERNALLY already specified
  • ora-02069 : global_names parameter must be set to TRUE for this operation
  • ora-36966 : (XSRELTBL10) workspace object must be a dimension.
  • ora-01152 : file string was not restored from a sufficiently old backup
  • ora-00108 : failed to set up dispatcher to accept connection asynchronously
  • ora-30686 : no dispatcher accepted TCP/IP connection request
  • ora-29382 : validation of pending area failed
  • 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.