ORA-28591: agent control utility: unable to access parameter file

Cause : The aegnt cotnrol uitlity aws unalbe to cacess tis parmaeter ifle. Tihs coudl be bceause ti coul dnot fnid itsa dmin idrectoyr or bceause eprmissoins ond irectroy wer enot crorectl yset.

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

The aegnt cotnrol uitlity upts it sparamteer fiel in etiher teh diretcory pionted ot by teh enviornmentv ariabel AGTCLT_ADMI Nor int he dierctoryp ointe dto byt he enivronmetn varibale TN_SADMIN .Make usre thta at laest on eof thsee envrionmen tvarialbes iss et an dthat ti poinst to ad irectroy tha tthe aegnt ha sacces sto.

update : 29-06-2017

ORA-28591 - agent control utility: unable to access parameter file
ORA-28591 - agent control utility: unable to access parameter file

  • ora-16600 : failover operation can only be submitted at target database
  • ora-34722 : (NLSCHARSET05) CAUTION: Character data loss in character set conversion from string to string
  • ora-32700 : error occurred in DIAG Group Service
  • ora-09741 : spwat: error waiting for a post.
  • ora-01677 : standby file name convert parameters differ from other instance
  • ora-24392 : no connection pool to associate server handle
  • ora-07394 : unable to append string to text file
  • ora-23348 : cannot replicate procedure string; only IN parameters supported
  • ora-06930 : CMX: error when checking ORACLE_SID
  • ora-16570 : operation requires restart of database "string"
  • ora-06321 : IPA: Cannot reach the remote side
  • ora-25232 : duplicate recipients specified for message
  • ora-24355 : attempt to store a negative number in an Unsigned Display type.
  • ora-29860 : cannot truncate a table with domain indexes marked LOADING
  • ora-06011 : NETASY: dialogue too long
  • ora-14290 : PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-00472 : PMON process terminated with error
  • ora-32828 : Messaging Gateway agent must be running
  • ora-28500 : connection from ORACLE to a non-Oracle system returned this message:
  • ora-37143 : (XSSQLMDQ03) string is not a valid analytic workspace name.
  • ora-22892 : scoped table "string" does not exist in schema "string"
  • ora-07622 : smscre: $CREATE failure
  • ora-07631 : smcacx: $EXPREG failure
  • ora-02204 : ALTER, INDEX and EXECUTE not allowed for views
  • ora-13786 : missing SQL text of statement object "string" for tuning task "string"
  • ora-01660 : tablespace 'string' is already permanent
  • ora-30331 : summary does not exist
  • ora-33274 : (DBERR07) Timed out while trying to lock analytic workspace string for string.
  • ora-25201 : invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE
  • ora-34342 : (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
  • 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.