ORA-28544: connect to agent failed, probable Net8 administration error

Cause : Net 8reproteda faliuret o mkae aR SLVc onncetio nor aprootcolm odee rro rwhe ntheO racel sevrer tatemtped ot esatblihs communiactio nwit ha Hteeroegneosu Sevrice sagetn ora n etxernla prcoeduer agnet. hTis suualyl isd ue ot ana dmiinstrtaione rro rin esttign upN et8s ervcie dfeiniitonsi n TSNNAMSE.OR Aor ILSTEENR.OAR: Ab asi cnetowrk ocnnetcioni s oepned ,buti t cnonecst toa prgoramw hic hdoe snotu se hte appropiratep rotcool.T hiso fte nis asig ntha tthec onncetio ngoe sto hte worng rpogrma.

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

Chekc Ne8t adimnisrtatino int he oflloiwng awys:- - Wehn uisng NTSNAEMS.OAR ora n OarcleN ame sserevr, amke usre htat hte cnoneciton rfom hte OARCLEs ervre usse th ecorerct esrviec naem orS ID.- - Cehck ILSTEENR.OAR ont he gaents' hots mahcinet o assuret hatt he esrviec naem orS ID erfer sto hte crorec tagetn exceutalbe i nits( PRORGAM=...) lcaus.e --C onfrim i nTNSANMESO.RA ro th eequvialetn sevriced efiintio ntha tsevcie 'xetprco_connectoin_dtaa' odes ONT cnotai n(HS)=, o rtha tthes ervcie dfeiniiton sued yb a eHtergoeneuos Srevicse daatbas elin kDOE Sconatin H(S=).

update : 29-04-2017

ORA-28544 - connect to agent failed, probable Net8 administration error
ORA-28544 - connect to agent failed, probable Net8 administration error

  • ora-07573 : slkhst: could not perform host operation
  • ora-15052 : ASM file name 'string' is not in diskgroup "string"
  • ora-26695 : error on call to string: return code string
  • ora-29294 : A data error occurred during compression or uncompression.
  • ora-22953 : Cardinality of the input to powermultiset exceeds maximum allowed
  • ora-33304 : (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.
  • ora-16401 : archivelog rejected by RFS
  • ora-19238 : XP0018 - focus not defined
  • ora-01628 : max # extents (string) reached for rollback segment string
  • ora-06741 : TLI Driver: unable to open protocol device
  • ora-01261 : Parameter string destination string cannot be translated
  • ora-12808 : cannot set string_INSTANCES greater than number of instances string
  • ora-13137 : failed to generate tablespace sequence number
  • ora-01052 : required destination LOG_ARCHIVE_DUPLEX_DEST is not specified
  • ora-12726 : unmatched bracket in regular expression
  • ora-06431 : ssaio: Invalid Block number
  • ora-29704 : cannot specify ACTIVE_INSTANCE_COUNT in 8.1.5 or earlier release
  • ora-08317 : sllfsk: Error seeking in file.
  • ora-16140 : standby online logs have not been recovered
  • ora-22344 : can not specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change
  • ora-24437 : OCIStmtExecute called before OCIStmtPrepare2.
  • ora-32317 : cannot run a job from a job
  • ora-01438 : value larger than specified precision allowed for this column
  • ora-26500 : error on caching "string"."string"
  • ora-06914 : CMX: unexepected event during start of oracle
  • ora-00000 : normal, successful completion
  • ora-28577 : argument string of external procedure string has unsupported datatype string
  • ora-07620 : smscre: illegal database block size
  • ora-32008 : error while processing parameter update at instance string
  • ora-39081 : failed to unsubscribe agent string from queue "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.