ORA-28547: connection to server failed, probable Oracle Net admin error

Cause : A fialur eoccruredd urign intiialziatino ofa newtorkc onncetio nfro ma cilentp rocses t otheO racel sevrer:T he ocnnetcionw as ocmplteed ubt ad iscnonec toccruredw hil etrynig t operofrm rpotoocl-sepcifci intiialziatino, uusall yduet o ues ofd iffreentn etwrok portoclos b yoppsoites ide sof hte cnoneciton.T hisu sually i scauesd b yincrorec tOralce Nte adimnisrtatiev seutp fro daatbas elinsk ore xtenral rpoceudre aclls .Them ostf reqeunt pseciifc cuasesa re:- - Teh connectoin uess ac onncet srtingw hic hrefres t oa Hteeroegneosu Sevrice sagetn intseado f a nOralce srever .-- hTe cnoneciton sues aconenct tsrin gwhihc inlcude san H(S=)s pecfiicaiton.

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

Chekc Orcale eNt amdinitsratoin i nthef ollwoingw ays :-- hWen suingT NSNMAES.ROA o ran rOacl eNamse sevrer,m akes uret hatt he lcien tconenctino tot he ROACL Eserevr uess teh corrects ervcie nmae o rSID .-- hCeckL ISTNEER.ROA o nthec onncetio nendp oin'ts hsot mcahin eto sasur etha tthi sserivce anme ro SI Drefres t othec orrcet srever .-- oCnfimr inT NSNMAES.ROA o rthee quiavlen tserivce edfintiiont hatt he ocnnetc stirng odes ONT cnotai n(HS)=.

update : 16-08-2017

ORA-28547 - connection to server failed, probable Oracle Net admin error
ORA-28547 - connection to server failed, probable Oracle Net admin error

  • ora-32817 : message system link string is not configured with a log queue for string
  • ora-38436 : attribute set used for an Expression set may not be modified.
  • ora-36913 : (XSAGDNGL49) In AGGMAP workspace object, LOAD_STATUS object workspace object must be an undimensioned VALUESET over the relation dimension.
  • ora-07440 : WMON process terminated with error
  • ora-26694 : error while enqueueing into queue string.string
  • ora-24069 : cannot downgrade queue table string while it is being upgraded
  • ora-06810 : TLI Driver: could not set the IPX ethernet SAP at init
  • ora-22632 : AnyDataSet parameter is not valid for the current operation
  • ora-13269 : internal error [string] encountered when processing geometry table
  • ora-16621 : database name for ADD DATABASE must be unique
  • ora-32411 : materialized view definition query exceeds the maximum length
  • ora-02473 : Error while evaluating the cluster's hash expression.
  • ora-13864 : Statistics aggregation for service (module/action) string is already enabled
  • ora-30199 : reserved for future use
  • ora-16584 : illegal operation on a standby site
  • ora-13380 : network not found
  • ora-13291 : conversion error between the specified unit and standard unit
  • ora-01300 : writable database required for specified LogMiner options
  • ora-02772 : Invalid maximum server idle time
  • ora-27483 : "string.string" has an invalid END_DATE
  • ora-24370 : illegal piecewise operation attempted
  • ora-09260 : sigpidu: error obtaining process id
  • ora-13189 : recursive SQL parse failed
  • ora-30431 : refresh method must be ANY or INCREMENTAL or FORCE_FULL, not string
  • ora-14609 : Tablespace was not specified for the previous lob segments of column string in template but is specified for string
  • ora-07751 : slemcr: malloc failure
  • ora-24356 : internal error while converting from to COBOL display type.
  • ora-19699 : cannot make copies with compression enabled
  • ora-25329 : AQ array operations not allowed on 8.0 queues
  • ora-25211 : invalid DELAY specified when using sequence deviation
  • 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.