RSS
热门关键字: oracle  mysql 密码  memcached  galaxy s2  debian 主机名  88888

Oracle 10g errors message troubleshooting 168 (ORA-27401 to

来 源:docfans.net 评论:0 时间:2010-12-03
ORA-27411: An 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-27412: repeat interval contains invalid keyword: string
Cause: The calendar string for the repeat interval of a job, schedule, or window contained an unsupported keyword.
Action: Correct the repeat interval such that it no longer contains the invalid keyword.
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-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-27415: repeat interval 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-27416: BYDAY= clause in repeat interval 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-27417: BYWEEKNO clause is only supported when FREQ=YEARLY
Cause: A repeat interval calendar string contained a BYWEEKNO clause with a frequency other than yearly.
Action: Remove the BYWEEKNO clause or change the frequency to yearly.
ORA-27418: syntax error in repeat interval
Cause: The repeat interval could not be recognized as a valid syntax.
Action: Specify a valid 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-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-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-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-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-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-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-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-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-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-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-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-27463: invalid program type string
Cause: An invalid program type was specified.
Action: Reissue the command using a valid program type.
ORA-27464: invalid schedule type string
Cause: An invalid schedule type was specified.
Action: Reissue the command using a valid schedule type.
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-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-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-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-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-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-27472: invalid metadata attribute string
Cause: An invalid metadata attribute was specified.
Action: Reissue the command using a valid metadata attribute.
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-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-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-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-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-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-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-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-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-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-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-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-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-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-27488: unable to set string because string was/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-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-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-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-27500: inter-instance IPC error
Cause: This is an operating system/cluster interconnect error.
Action: Check the extra information and contact Oracle Support Services.

    Tags:
    评论不能超过250字,请自觉遵守互联网相关政策法规。[Oracle 10g errors message troubleshooting 168 (ORA-27401 to]

    loading.. 评论加载中....
    赞助商
    相关文章