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 : 21-08-2017

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

  • ora-02724 : osnpbr: cannot send break message to orapop
  • ora-30488 : argument should be a function of expressions in PARTITION BY
  • ora-12853 : insufficient memory for PX buffers: current stringK, max needed stringK
  • ora-24184 : transformation string.string already exists
  • ora-14119 : specified partition bound is too long
  • ora-01502 : index 'string.string' or partition of such index is in unusable state
  • ora-31675 : worker process interrupt for unexpected death of master process
  • ora-12022 : materialized view log on "string"."string" already has rowid
  • ora-01554 : out of transaction slots in transaction tables
  • ora-30973 : invalid Path Table option for XML Index
  • ora-01484 : arrays can only be bound to PL/SQL statements
  • ora-12726 : unmatched bracket in regular expression
  • ora-15113 : alias name 'string' refers to a directory
  • ora-29906 : indextype string.string does not exist
  • ora-37182 : you may only specify one dimension to partition
  • ora-27087 : unable to get share lock - file not readable
  • ora-38756 : Flashback is already turned off for this tablespace.
  • ora-23491 : no valid extension request at "string"
  • ora-06518 : PL/SQL: Probe version string incompatible with version string
  • ora-30952 : illegal configuration of HTTP/HTTPS in xdbconfig.xml
  • ora-39207 : Value string is invalid for parameter string.
  • ora-27211 : Failed to load Media Management Library
  • ora-09214 : sfdone: I/O error detected
  • ora-07476 : slsget: cannot get mapped memory statistics.
  • ora-00288 : to continue recovery type ALTER DATABASE RECOVER CONTINUE
  • ora-01539 : tablespace 'string' is not online
  • ora-07261 : spdde: kill error, unable to send signal to process.
  • ora-19683 : real and backup blocksize of file string are unequal
  • ora-00912 : input parameter too long
  • ora-12482 : internal MLS error: string Error: 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.