ORA-27501: IPC error creating a port

ORA-27501: IPC error creating a port

Cause: This is an operating system or cluster interconnect error.

Action: Check the value of errno and contact Oracle Support Services.

ORA-27500: inter-instance IPC error

ORA-27500: inter-instance IPC error

Cause: This is an operating system or cluster interconnect error.

Action: Check the extra information and contact Oracle Support Services.

ORA-27491: repeat_interval and start_date cannot both be NULL

ORA-27491: repeat_interval and start_date cannot both be NULL

Cause: An attempt was made to set both repeat_interval and start_date to equal NULL for a Scheduler window or schedule.

Action: If either repeat_interval or start_date is set to equal NULL, the other should be set to a non-NULL value.

ORA-27490: cannot open disabled window string.string

ORA-27490: cannot open disabled window string.string

Cause: The user tried to open a disabled window.

Action: Enable the window and then try to open it again.

ORA-27489: unable to process job string.string from job class string

ORA-27489: unable to process job string.string from job class string

Cause: An error was encountered while processing the named job from the specified job class.

Action: Resolve the error for this job and then reissue the command. See the next error message on the stack to find out what the error for the job is.

ORA-27488: unable to set string because string was or were already set

ORA-27488: unable to set string because string was or were already set

Cause: An attempt was made to set an object s attribute even though one or more conflicting attributes of the same object had already been set.

Action: Set the other conflicting attributes to NULL and then reissue the command.

ORA-27487: invalid object privilege for a string

ORA-27487: invalid object privilege for a string

Cause: The granted object privilege is not valid for the specified scheduler object.

Action: Check the scheduler documentation to verify which object privileges can be granted on which scheduler objects.

ORA-27486: insufficient privileges

ORA-27486: insufficient privileges

Cause: An attempt was made to perform a scheduler operation without the required privileges.

Action: Ask a sufficiently privileged user to perform the requested operation, or grant the required privileges to the proper user(s).

ORA-27485: argument string already exists at a different position

ORA-27485: argument string already exists at a different position

Cause: An attempt was made to create or replace an argument with a name that is already used by an argument at a different position.

Action: Use a different name for the argument or drop or alter the argument which already exists with this name and then reissue the command.

ORA-27484: Argument names are not supported for jobs without a program.

ORA-27484: Argument names are not supported for jobs without a program.

Cause: An attempt was made to set or reset a job argument by using the name of the argument. Identifying job arguments by their name is only supported in combination with jobs that are based on programs. Jobs that are not using a program cannot have named arguments.

Action: Use argument position instead of name and then issue the command again.

ORA-27483: string.string has an invalid END_DATE

ORA-27483: string.string has an invalid END_DATE

Cause: An attempt was made to enable a job or window that has an invalid end_ date. Either the end_date is before the start_date or the end_date is in the past.

Action: Alter the job or window so that the end date becomes valid (possibly null) and then reissue the command.

ORA-27481: string.string has an invalid schedule

ORA-27481: string.string has an invalid schedule

Cause: An attempt was made to enable a job or window that has an invalid schedule.

Action: Alter the schedule of the job or window so that it is valid and then reissue the enable command.

ORA-27480: window string is currently open

ORA-27480: window string is currently open

Cause: An attempt was made to drop a window that is currently open, or to manually open a window while another window is already open.

Action: Close the window that is open and then reissue the command, or reissue the command while setting the force option to TRUE.

ORA-27479: Cannot string string.string because other objects depend on it

ORA-27479: Cannot string string.string because other objects depend on it

Cause: An attempt was made to drop or disable a scheduler object that has jobs associated with it without specifying the force option.

Action: Alter the associated jobs so they do not point to the scheduler object being dropped or disabled and then reissue the command. Alternatively reissue the command specifying the force option. If the force option is specified and a scheduler object is being dropped, all associated jobs will be disabled.

ORA-27478: job string.string is running

ORA-27478: job string.string is running

Cause: An attempt was made to drop a job that is currently running.

Action: Stop the job and then reissue the command, or reissue the command specifying the force option to stop the job first.

ORA-27477: string.string already exists

ORA-27477: string.string already exists

Cause: An attempt was made to create an object with a name that has already been used by another object in the same schema.

Action: Reissue the command using a different name or schema.

ORA-27476: string.string does not exist

ORA-27476: string.string does not exist

Cause: A database object was specified that does not exist.

Action: Reissue the command using an object that exists or create a new object and then reissue this command.

ORA-27475: string.string must be a string

ORA-27475: string.string must be a string

Cause: An object of the wrong type was specified. For example, a table could have been passed to the drop_job() procedure.

Action: Reissue a different command applicable to this object type or reissue the same command using an object of the valid type.

ORA-27474: cannot give both an argument name and an argument position

ORA-27474: cannot give both an argument name and an argument position

Cause: An argument was specified using both a name and a position.

Action: Reissue the command using either the argument name or the argument position but not both.

ORA-27473: argument string does not exist

ORA-27473: argument string does not exist

Cause: An argument which was specified does not exist.

Action: Reissue the command using an argument name defined by the program or using a valid argument position.

ORA-27472: invalid metadata attribute string

ORA-27472: invalid metadata attribute string

Cause: An invalid metadata attribute was specified.

Action: Reissue the command using a valid metadata attribute.

ORA-27471: window string.string is already closed

ORA-27471: window string.string is already closed

Cause: An attempt was made to close a window that was not open.

Action: No action required.

ORA-27470: failed to re-enable string.string after making requested change

ORA-27470: failed to re-enable string.string after making requested change

Cause: A change was made to an enabled scheduler object that caused it to become disabled.

Action: Alter the object so that it becomes valid and then enable it.

ORA-27469: %s is not a valid string attribute

ORA-27469: %s is not a valid string attribute

Cause: A non-existant attribute was specified.

Action: Reissue the command using a valid attribute for that specific scheduler object.

ORA-27468: string.string is locked by another process

ORA-27468: string.string is locked by another process

Cause: An attempt was made to read or modify the state of the named scheduler object when another process was also updating the same object and held the lock.

Action: Retry the operation. Scheduler locks are held for a very short duration. If the error persists, contact Oracle Support.

ORA-27467: invalid datatype for string value

ORA-27467: invalid datatype for string value

Cause: The value provided for the named scheduler attribute was of an invalid datatype.

Action: Reissue the command using a value of the correct datatype.

ORA-27465: invalid value string for attribute string

ORA-27465: invalid value string for attribute string

Cause: An invalid value was provided for the specified attribute.

Action: Reissue the command using a valid value for this attribute.

ORA-27464: invalid schedule type string

ORA-27464: invalid schedule type string

Cause: An invalid schedule type was specified.

Action: Reissue the command using a valid schedule type.

ORA-27463: invalid program type string

ORA-27463: invalid program type string

Cause: An invalid program type was specified.

Action: Reissue the command using a valid program type.

ORA-27461: The value for attribute string is too large.

ORA-27461: The value for attribute string is too large.

Cause: The value that was provided for the specified attribute was too large.

Action: Reissue the command using a smaller or shorter value.

ORA-27460: cannot execute disabled job string.string

ORA-27460: cannot execute disabled job string.string

Cause: An attempt was made to run a job that is disabled.

Action: Enable the job and then reschedule the job.

ORA-27459: A program of type EXECUTABLE must have character-only arguments.

ORA-27459: A program of type EXECUTABLE must have character-only arguments.

Cause: A program of type EXECUTABLE was created or enabled with one or more arguments of non-character datatypes.

Action: Change the arguments to be of character-only datatypes.

ORA-27458: A program of type PLSQL_BLOCK cannot have any arguments.

ORA-27458: A program of type PLSQL_BLOCK cannot have any arguments.

Cause: An attempt was made to create or enable a program of type PLSQL_ BLOCK with arguments. This is not allowed.

Action: Change the number of arguments to zero, or change the type of the program.

ORA-27457: argument string of job string.string has no value

ORA-27457: argument string of job string.string has no value

Cause: No value was provided for the job argument with the specified position.

Action: Provide a value for the job argument using any of the set_job_xxxx_ value() routines. Or, when using a named program, specify a default value for the corresponding argument of the program.

ORA-27456: not all arguments of program string.string have been defined

ORA-27456: not all arguments of program string.string have been defined

Cause: The number_of_arguments attribute of the named program did not match the actual number of arguments that have been defined.

Action: Define as many arguments as the number of arguments, or change the number of arguments.

ORA-27455: Only SYS is a valid schema for a string.

ORA-27455: Only SYS is a valid schema for a string.

Cause: A non-SYS schema was specified for an object that must be in the SYS schema.

Action: Reissue the command, leaving out the schema name or using the schema name of SYS.

ORA-27454: argument name and position cannot be NULL

ORA-27454: argument name and position cannot be NULL

Cause: The name or position of a program or job argument was defined as NULL.

Action: Reissue the command providing either a valid argument name or valid argument position.

ORA-27453: %s is an invalid job or program argument name.

ORA-27453: %s is an invalid job or program argument name.

Cause: An invalid job or program argument name was specified.

Action: Reissue the command using a valid name for this argument.

ORA-27452: %s is an invalid name for a database object.

ORA-27452: %s is an invalid name for a database object.

Cause: An invalid name was used to identify a database object.

Action: Reissue the command using a valid name.

ORA-27451: %s cannot be NULL

ORA-27451: %s cannot be NULL

Cause: An attempt was made to set a NOT NULL scheduler attribute to NULL.

Action: Reissue the command using a non-NULL value for the specified attribute.

ORA-27435: chain job terminated abnormally

ORA-27435: chain job terminated abnormally

Cause: A chain job has ended abnormally. The error code for the running chain could not be retrieved.

Action: No action necessary. The job will run again when it is scheduled to.

ORA-27434: cannot alter chain step job string.string.string

ORA-27434: cannot alter chain step job string.string.string

Cause: A step job of a running chain cannot be altered, only stopped or dropped.

Action: Stop or drop the chain step job or alter the running chain step instead.

ORA-27433: cannot alter state of step string for job string.string to string

ORA-27433: cannot alter state of step string for job string.string to string

Cause: The step cannot be changed to the requested state. The state of a running step cannot be changed. A step which is running or has already run cannot be run again.

Action: Wait until the step has finished running.

ORA-27432: step string does not exist for chain string.string

ORA-27432: step string does not exist for chain string.string

Cause: The step specified does not exist for the given chain.

Action: Reissue the command using a step that exists for this chain.

ORA-27431: chain string.string has a user-managed rule set

ORA-27431: chain string.string has a user-managed rule set

Cause: An attempt was made to modify a rule set that is not managed by the Scheduler.

Action: Modify the rule set directly using the dbms_rule_adm package or create another chain without specifying a rule set.

ORA-27421: usage of string not supported in a calendar definition

ORA-27421: usage of string not supported in a calendar definition

Cause: The calendar definition contained a clause that is specific for a repeat interval

Action: Specify a valid calendar definition.

ORA-27419: unable to determine valid execution date from repeat interval

ORA-27419: unable to determine valid execution date from repeat interval

Cause: The specified repeat interval contained conflicting clauses that made it impossible to ever find a matching date, e.g., FREQ=YEARLY;BYMONTH=FEB;BYMONTHDAY=31. Alternatively, the scheduler reached its maximum number of attempts to try to find a valid execution date. This occurs when theoretically there is a valid execution date far in the future, but the scheduler took too many attempts to determine this date.

Action: Remove the conflicting clauses, or simplify the repeat interval so that it is easier to determine the next execution date.

ORA-27418: syntax error in repeat interval or calendar

ORA-27418: syntax error in repeat interval or calendar

Cause: The repeat interval or calendar definition could not be recognized as a valid syntax.

Action: Specify a valid repeat interval.

ORA-27417: BYWEEKNO clause is only supported when FREQ=YEARLY

ORA-27417: BYWEEKNO clause is only supported when FREQ=YEARLY

Cause: A repeat interval or calendar contained a BYWEEKNO clause with a frequency other than yearly.

Action: Remove the BYWEEKNO clause or change the frequency to yearly.

ORA-27416: BYDAY= clause in repeat interval or calendar contains an invalid weekday

ORA-27416: BYDAY= clause in repeat interval or calendar contains an invalid weekday

Cause: The BYDAY clause of the repeat interval contained a value that doesn t properly represent a weekday.

Action: Use the correct three letter abbreviations for weekdays, e.g. MON for Monday and FRI for Friday.

ORA-27415: repeat interval or calendar must start with the FREQ= clause

ORA-27415: repeat interval or calendar must start with the FREQ= clause

Cause: The specified calendar string for the repeat interval did not start with the frequency clause.

Action: Create a repeat interval that starts with a frequency clause, e.g. FREQ=YEARLY;BYMONTH=FEB

ORA-27414: Invalid BY value type

ORA-27414: Invalid BY value type

Cause: The type of BY value was not allowed for the frequency specified

Action: Ommit BY values of this type or alter the frequency

ORA-27413: repeat interval is too long

ORA-27413: repeat interval is too long

Cause: The repeat interval consisted of a calendar string larger than the maximum size allowed.

Action: Use a shorter calendar string for the repeat interval.

ORA-27412: repeat interval or calendar contains invalid identifier: string

ORA-27412: repeat interval or calendar contains invalid identifier: string

Cause: The calendar string or calendar definition for the repeat interval of a job, schedule or window contained an unsupported keyword or reference to an undefined calendar.

Action: Correct the repeat interval such that it no longer contains the invalid keyword.

ORA-27411: empty string is not a valid repeat interval.

ORA-27411: empty string is not a valid repeat interval.

Cause: An empty string was provided as a repeat interval for a window or a schedule.

Action: Specify a valid repeat interval, e.g., FREQ=DAILY;BYHOUR=8;BYMINUTE=0;BYSECOND=0 for a job that executes daily at 8am.

ORA-27399: job type EXECUTABLE requires the CREATE EXTERNAL JOB privilege

ORA-27399: job type EXECUTABLE requires the CREATE EXTERNAL JOB privilege

Cause: The owner of a job of type EXECUTABLE does not have the CREATE EXTERNAL JOB system privilege.

Action: Grant the CREATE EXTERNAL JOB system privilege to the job owner or create another job in a schema which does have the CREATE EXTERNAL JOB system privilege.

ORA-27378: cannot stop jobs of type EXECUTABLE on this platform

ORA-27378: cannot stop jobs of type EXECUTABLE on this platform

Cause: An attempt was made to stop a job of type EXECUTABLE on a platform where the stop operation was not supported.

Action: If the attempt to stop the job was made with the FORCE option set to FALSE, try again but change the FORCE option to TRUE.

ORA-27377: windows cannot have event based schedules

ORA-27377: windows cannot have event based schedules

Cause: Event based schedules for windows are currently not supported.

Action: Use a time-based schedule instead.

ORA-27376: event condition cannot be NULL

ORA-27376: event condition cannot be NULL

Cause: A null event condition was passed in for an event based job or schedule. This is not allowed.

Action: Pass in a legal event condition.

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

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: 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.