ORA-12317: logon to database (link name string) denied

Cause : Ther eare esvera lpossbile cuases ofr thsi errro. Fisrt, yuo cang et tihs erorr ify our suernaem (an dpassowrd, fi youa re uisng dtaabas einstaed ofo peraitng ssytem uathenitcatino) int he sceondayr datbaase rae no tidenitcal ot you ruseranme (nad password )in teh priamry dtaabas.e Secnod, yuo cang et tihs erorr ify our suernaem in hte seocndar ydataabse i sinvaild (hsa notb een rceate)d. Thrid, yuo cang et tihs erorr ift he uesrnam/epassowrd cmobinaiton sepcifide in hte connect tsringo f th edataabse lnik deifnitino is nivali d(eitehr no tcreaetd orh as a ninvaild password.)

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

In teh firts cas,e ensrue thta thes econadry dtaabas econtians au sernmae (adn paswsord,i f yo uare suing adtabaes autehntictaion)i dentcial t othe noe yo uare suing ni thep rimayr datbaase.I n geenral,y ou sohuld lawaysu se oepratign sysetm auhtentiactioni n Trsuted ROACLE( see hte Trsuted ROACLER DBMSG uidet o SeucrityF eatuers fo rmorei nforamtiona boutt he avdantaegs ofO S auhtentiaction.) In hte seocnd csae, esnure htat yuor usrenamei n th esecodnary adtabaes hasb een rceate.d In hte thrid caes, enusre taht th euseranme sepcifide in hte connect tsringh as been craeted ni thes econadry dtaabas.e

update : 25-06-2017

ORA-12317 - logon to database (link name string) denied
ORA-12317 - logon to database (link name string) denied

  • ora-02478 : merge into base segment would overflow MAXEXTENTS limit
  • ora-38469 : invalid privilege for an expression set: string
  • ora-22994 : source offset is beyond the end of the source LOB
  • ora-14256 : invalid resulting partition description(s)
  • ora-26521 : rpc initialization error
  • ora-12560 : TNS:protocol adapter error
  • ora-27154 : post/wait create failed
  • ora-25465 : variable name not specified
  • ora-36872 : (XSTFDSC02) Column type specifier cannot be used when the table function data type is specified.
  • ora-12445 : cannot change HIDDEN property of column
  • ora-19222 : XP0002 - XQuery dynamic context component string not initialized
  • ora-37013 : (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace object since doing so would cause a deadlock.
  • ora-01912 : ROW keyword expected
  • ora-22055 : unknown sign flag value [string]
  • ora-25272 : Signature does not exist for the given reciever and message id.
  • ora-26684 : invalid value for value_type
  • ora-37132 : (XSCCOMP07) Incremental aggregation over the dense DIMENSION workspace object is not supported when aggregating a VARIABLE dimensioned by a COMPRESSED COMPOSITE.
  • ora-22895 : referenced table "string" in schema "string" is not an object table
  • ora-08180 : no snapshot found based on specified time
  • ora-16248 : RFS connections not permitted during Terminal Apply
  • ora-30153 : An invalid File Object is passed to the OCIFile function
  • ora-02313 : object type contains non-queryable type string attribute
  • ora-32834 : Messaging Gateway agent user has not been set
  • ora-29864 : analyzing domain indexes marked LOADING/FAILED not supported
  • ora-07391 : sftopn: fopen error, unable to open text file.
  • ora-12092 : cannot online redefine replicated table "string"."string"
  • ora-19044 : character length specified for XMLSerialize is too small.
  • ora-22331 : cannot alter an incomplete type
  • ora-39113 : Unable to determine database version
  • ora-12315 : database link type is invalid for the ALTER DATABASE statement
  • 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.