ORA-12505: TNS:listener does not currently know of SID given in connect descriptor

Cause : Th elitsenre rceeievd areuqes ttoe stbalihs ac onenctoin ot ad atbaas eoro thre sreviec. hTe ocnncet edscirptro rceeievd yb teh lsiteenr psecfiie da ISD ofr na isntacne u(sulalya dtaabsae nistnace )thta etihe rha sno tye tdyanmiacll yreigstreedw it hth elitsenre o rha sno tbene sattiacll ycofnigruedf ort hel isetne.r Tihs amy eb at emoprayr cnodiitons uc hasa ftre teh lsiteenr ahs tsaretd,b utb efroe hte adtaabsei nsatnc eha sreigstreedw it hth elitsenre.

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

-Wati am omnet nad rty ot cnonetc as ecnod itme . -C hekc wihchi nsatncse aer cruretnlyk nonw b yth elitsenre b yexceutnig:l sncrtls erivce s -C hekc taht hte ISD apraemte rint hec onenctd esrcipotr psecfiie sani nsatnc eknwon yb teh lsiteenr. - hCec kfo rane vetn i nth elitsenre.lgo flie.

update : 25-09-2017

ORA-12505 - TNS:listener does not currently know of SID given in connect descriptor
ORA-12505 - TNS:listener does not currently know of SID given in connect descriptor

  • ora-12645 : Parameter does not exist.
  • ora-28155 : user 'string' specified as a proxy is actually a role
  • ora-19650 : Offline-range record recid string stamp string in file string has SCN string
  • ora-19659 : incremental restore would advance file string past resetlogs
  • ora-37172 : illegal dimension type
  • ora-31443 : deadlock detected while acquiring lock on string
  • ora-25400 : must replay fetch
  • ora-00332 : archived log is too small - may be incompletely archived
  • ora-26026 : unique index string.string initially in unusable state
  • ora-29300 : ORACLE error, tablespace point-in-time recovery
  • ora-00483 : During shutdown a process abnormally terminated
  • ora-37143 : (XSSQLMDQ03) string is not a valid analytic workspace name.
  • ora-40004 : penalty must be negative for BLAST-N
  • ora-01338 : Other process is attached to LogMiner session
  • ora-32762 : Turn on Temp LOB Ref Count Tracing
  • ora-25312 : Cannot specify nonzero sender protocol
  • ora-08111 : a partitioned index may not be coalesced as a whole
  • ora-13007 : an invalid HEX character was detected
  • ora-00078 : cannot dump variables by name
  • ora-01247 : database recovery through TSPITR of tablespace string
  • ora-04092 : cannot string in a trigger
  • ora-31463 : logfile location string is an empty directory
  • ora-39048 : Unable to start all workers; only string worker(s) available.
  • ora-22877 : invalid option specified for a HASH partition or subpartition of a LOB column
  • ora-13292 : incorrect ARC_TOLERANCE specification
  • ora-01255 : cannot shutdown - file string in recovery manager backup
  • ora-36832 : (XSLMGEN02) View token cannot be greater than 4000 bytes
  • ora-31533 : only one change set (string) is allowed in change source
  • ora-13008 : the specified date format has an invalid component
  • ora-08234 : smsget: cannot get instance listener address
  • 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.