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 : 28-04-2017

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

  • ora-12479 : file label string must equal DBHIGH string
  • ora-07617 : $FORMAT_CLASS failed translating the binary label to a string
  • ora-00325 : archived log for thread string, wrong thread # string in header
  • ora-23374 : object group "string"."string" already exists
  • ora-02733 : osnsnf: database string too long
  • ora-25448 : rule string.string has errors
  • ora-12852 : PARALLEL_MIN_SERVERS must be less than PROCESSES, string
  • ora-28261 : CURRENT_USER can not be used in PLSQL Definer's Right procedure.
  • ora-19263 : XQ0043 - duplicate namespace prefix string
  • ora-25445 : invalid column number: string for table alias: string
  • ora-00238 : operation would reuse a filename that is part of the database
  • ora-32140 : cannot peform this operation on stream
  • ora-09805 : conversion of category number to string failed.
  • ora-12616 : TNS:no event signals
  • ora-36404 : (XSSPROP04) Property string cannot be applied to an undimensioned (scalar) TEMPORARY variable.
  • ora-07614 : $CHANGE_CLASS failed in retrieving the user's process label
  • ora-22813 : operand value exceeds system limits
  • ora-24750 : incorrect size of attribute
  • ora-34900 : (PPWKDAYS00) At least 7 day names must be given. Only number were provided.
  • ora-30373 : object data types are not supported in this context
  • ora-22328 : object "string"."string" has errors. string
  • ora-25269 : cant specify sognature with get signature option
  • ora-19694 : some changed blocks were not found in the change tracking file
  • ora-19768 : USING clause only valid with ENABLE CHANGE TRACKING
  • ora-07345 : The datafile name must not contain the string '..'.
  • ora-32321 : REFRESH FAST of "string"."string" unsupported after detail table TRUNCATE
  • ora-01551 : extended rollback segment, pinned blocks released
  • ora-04088 : error during execution of trigger 'string.string'
  • ora-02331 : cannot create constraint on column of datatype string
  • ora-24032 : object string exists, index could not be created for queue table string
  • 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.