ORA-27375: valid agent name must be specified for secure queues

Cause : The queue specified for the event based job or schedule was a secure queue and either no agent name was specified or an invalid agent name was specified.

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

If no agent name was specified, retry the call with a valid agent name. If the agent name was valid, check if the agent is currently subscribed to the queue and, in the case of jobs, check is the agent has been authorized to act as the job owner.

update : 28-04-2017

ORA-27375 - valid agent name must be specified for secure queues
ORA-27375 - valid agent name must be specified for secure queues

  • ora-02094 : replication option not installed
  • ora-12804 : parallel query server appears to have died
  • ora-31211 : DBMS_LDAP: PL/SQL - Invalid LDAP entry dn.
  • ora-02196 : PERMANENT/TEMPORARY option already specified
  • ora-02344 : cannot revoke execute on a type with table dependents
  • ora-00285 : TIME not given as a string constant
  • ora-30467 : internal data for filter number string is inconsistent
  • ora-29800 : invalid name for operator
  • ora-26721 : enqueue of the LCR not allowed
  • ora-29520 : name string resolved to a class in schema string that could not be accessed
  • ora-02284 : duplicate INCREMENT BY specifications
  • ora-27193 : sbtinfo2 did not return volume label
  • ora-02786 : Size needed for shared region is greater than segment size
  • ora-39021 : Database compatibility version string is not supported.
  • ora-40291 : model cost not available
  • ora-38505 : invalid default value for the attribute
  • ora-30772 : opaque types do not have default constructors
  • ora-31191 : Resource string is already checked out
  • ora-16655 : specified target standby database invalid
  • ora-09939 : Restoration of signal handlers failed.
  • ora-23302 : application raised communication failure during deferred RPC
  • ora-01503 : CREATE CONTROLFILE failed
  • ora-16089 : archive log has already been registered
  • ora-29826 : keyword FOR is missing
  • ora-19035 : Invalid select item of the query in newContextFromHierarchy()
  • ora-24371 : data would not fit in current prefetch buffer
  • ora-15068 : maximum number of diskgroups string already mounted
  • ora-23537 : function or procedure string is not allowed to be invoked from this site.
  • ora-30493 : The percentile value should be a number between 0 and 1.
  • ora-28008 : invalid old password
  • 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.