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 : 23-08-2017
ORA-12317

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

  • ora-15168 : rolling downgrade prevented by string
  • ora-31417 : column list contains control column string
  • ora-01610 : recovery using the BACKUP CONTROLFILE option must be done
  • ora-26055 : Invalid buffer specified for direct path unload
  • ora-07305 : ksmcsg: illegal database buffer size.
  • ora-01333 : failed to establish Logminer Dictionary
  • ora-13761 : invalid filter
  • ora-31686 : error creating worker processes
  • ora-13197 : element string.string.string is out of range
  • ora-14456 : cannot rebuild index on a temporary table
  • ora-40004 : penalty must be negative for BLAST-N
  • ora-07826 : sspscm: SYS$GETDVIW failure
  • ora-24390 : Unsupported scrollable cursor operation
  • ora-12508 : TNS:listener could not resolve the COMMAND given
  • ora-36679 : (XSDPART17) workspace object contains a leaf (workspace object) that is not part of the partition dimension workspace object.
  • ora-37060 : (XSMCSESS08) number is not a valid custom member in dimension workspace object.
  • ora-09916 : Required password was not specified.
  • ora-32700 : error occurred in DIAG Group Service
  • ora-29386 : plan or consumer group string is mandatory and cannot be deleted or modified
  • ora-29859 : error occurred in the execution of ODCIINDEXTRUNCATE routine
  • ora-31510 : name uses reserved prefix CDC$
  • ora-09809 : Unable to get user's group ID from connection
  • ora-27151 : buffer not large enough to hold process ID string
  • ora-16185 : REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG mutually exclusive
  • ora-16790 : the value of the configurable property is invalid
  • ora-19957 : database should have no datafiles in unknown state
  • ora-08111 : a partitioned index may not be coalesced as a whole
  • ora-04080 : trigger 'string' does not exist
  • ora-15121 : ASM file name 'string' contains an invalid diskgroup name
  • ora-02332 : cannot create index on attributes of this column
  • 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.