ORA-28582: a direct connection to this agent is not allowed

Cause : A user or a tool tried to establish a direct connection to either an external procedure agent or a Heterogeneous Services agent, for example: "SVRMGR> CONNECT SCOTT/TIGER@NETWORK_ALIAS". This type of connection is not allowed.

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

When executing the CONNECT statement, make sure your database link or network alias is not pointing to a Heterogeneous Option agent or an external procedure agent.

update : 24-07-2017
ORA-28582

ORA-28582 - a direct connection to this agent is not allowed
ORA-28582 - a direct connection to this agent is not allowed

  • ora-30082 : datetime/interval column to be modified must be empty to decrease fractional second or leading field precision
  • ora-12048 : error encountered while refreshing materialized view "string"."string"
  • ora-29960 : line string, string
  • ora-16650 : command incompatible when Fast-Start Failover is enabled
  • ora-31205 : DBMS_LDAP: PL/SQL - Invalid LDAP Auth method.
  • ora-38714 : Instance recovery required.
  • ora-31016 : Attempted to delete entry without name
  • ora-26007 : invalid value for SETID or OID column
  • ora-39600 : Queue keys needs to be a suffix of cluster key.
  • ora-01246 : recovering files through TSPITR of tablespace string
  • ora-28575 : unable to open RPC connection to external procedure agent
  • ora-39313 : call to DBMS_SCHEMA_COPY.CLONE is not legal
  • ora-32588 : supplemental logging attribute string exists
  • ora-31223 : DBMS_LDAP: cannot open more than string LDAP server connections
  • ora-12899 : value too large for column string (actual: string, maximum: string)
  • ora-38464 : expression set is not empty.
  • ora-01273 : STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = string or higher
  • ora-19683 : real and backup blocksize of file string are unequal
  • ora-32114 : Cannot perform operation on a null LOB
  • ora-12914 : Cannot migrate tablespace to dictionary managed type
  • ora-36312 : (PHYS00) workspace object must be a dimension or dimensioned variable.
  • ora-29535 : source requires recompilation
  • ora-01938 : IDENTIFIED BY must be specified for CREATE USER
  • ora-07238 : slemcl: close error.
  • ora-37032 : (XSMLTMAINT03) You cannot MAINTAIN partition template workspace object in MULTI mode.
  • ora-23388 : replication parallel push watermark error
  • ora-33308 : (DBVALID04) SEVERE ERROR: Record number used but not allocated
  • ora-00253 : character limit string exceeded by archive destination string string
  • ora-19771 : cannot rename change tracking file while database is open
  • ora-01138 : database must either be open in this instance or not at all
  • 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.