Database Error Messages

Release
toggle
  • 23ai
Updated
Jun 24, 2024

ORA-27405

invalid schema or handler name for attribute "string"

Cause

A nonexistent or invalid schema name or scheduler job notification handler name was specified. This occurred when an attempt was made to set JOB_NOTIFICATION_HANDLER global attribute for the scheduler to a user-provided value and either of the following was true:

  • The JOB_NOTIFICATION_HANDLER_OWNERS system parameter was not configured to allow user-provided job notification handler.
  • The user schema was not allowed to own the job notification handler.
  • The current user executing either of the following API calls did not have EXECUTE privilege granted on the job notification handler procedure.
  • DBMS_SCHEDULER.set_scheduler_attribute to set the JOB_NOTIFICATION_HANDLER global attribute for the scheduler
  • DBMS_SCHEDULER.add_job_notification to add notifications for a scheduler job
  • The job notification handler procedure was created as an INVOKER rights PL/SQL procedure.
  • The job notification handler procedure was invalid.
  • The job notification handler procedure did not have the required number and type of input arguments.

Action

Specify a valid schema name or job notification handler for JOB_NOTIFICATION_HANDLER attribute. Depending on the error, either one of the following should be done:

  • If the JOB_NOTIFICATION_HANDLER_OWNERS system parameter is set to NULL (default value), then contact your database administrator to have it set it to an appropriate value (comma- separated list of database users) to allow user-provided job notification handler.
  • If the user schema is not allowed to own the job notification handler, then contact your database administrator to add the user as part of JOB_NOTIFICATION_HANDLER_OWNERS system parameter value. Only users specified as part of JOB_NOTIFICATION_HANDLER_OWNERS system parameter value are allowed to own job notification handler.
  • If you need EXECUTE privileges on the job notification handler procedure, then contact your database administrator.
  • If the job notification handler procedure is created as an INVOKER rights PL/SQL procedure, then create it as DEFINER rights PL/SQL procedure and retry operation setting JOB_NOTIFICATION_HANDLER global attribute. INVOKER rights PL/SQL procedures are not allowed as job notification handler procedure due to security reasons.
  • If the job notification handler procedure is in an INVALID state, then check DBA_ERRORS and DBA_OBJECTS view for more information.
  • Check the input and output arguments for the job notification handler procedure. It can only have one input argument of type IN with datatype CLOB and no arguments of type IN OUT or OUT are allowed.