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 : 25-06-2017
ORA-27375

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

  • ora-13050 : unable to construct spatial object
  • ora-25281 : complete reciever information not provided to non-repudiate reciever
  • ora-14327 : Some index [sub]partitions could not be rebuilt
  • ora-24201 : duplicate publisher, publisher already added to the queue
  • ora-22881 : dangling REF
  • ora-16543 : invalid request made to broker
  • ora-36266 : (XSCGMDLAGG00) Invalid context for the AGGREGATION function
  • ora-12466 : default level is greater than the user's maximum
  • ora-31219 : DBMS_LDAP: PL/SQL - Invalid LDAP notypes.
  • ora-32836 : database user string must be granted role string
  • ora-32032 : free temporary object number not available
  • ora-31622 : ORACLE server does not have string access to the specified file
  • ora-03288 : both FREELIST GROUP and INSTANCE parameters may not be specified
  • ora-02150 : invalid new tablespace name
  • ora-38448 : Indexing predicates with "string" operator is not supported.
  • ora-32812 : subscriber string does not exist
  • ora-36982 : (XSRELGID03) The grouping variable/relation workspace object must be dimensioned by all dimensions of the source relation workspace object that have more than one value in status.
  • ora-16717 : clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed
  • ora-13159 : Oracle table string already exists
  • ora-25280 : complete sender information not provided to non-repudiate sender
  • ora-00056 : DDL lock on object 'string.string' is already held in an incompatible mode
  • ora-22297 : warning: Open LOBs exist at transaction commit time
  • ora-06603 : LU6.2 Driver: Error allocating memory
  • ora-30564 : Index maintainence clause not allowed for ADD partition to RANGE partitioned tables
  • ora-19628 : invalid SCN range
  • ora-29546 : badly formed resource: string
  • ora-24769 : cannot forget an active transaction
  • ora-15030 : diskgroup name "string" is in use by another diskgroup
  • ora-38502 : invalid XML tag: string
  • ora-12010 : cannot create materialized view log on table owned by SYS
  • 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.