Action
Specify the meridian indicator in the correct format, A.M./AM or P.M./PM.
ORA–01856
BC/B.C. or AD/A.D. required
Cause
A date specification contained a BC/AD format code but a valid BC/AD
indicator was not specified. If one of the BC/AD format codes, BC/AD or B.C./A.D., is specified in a date format, the date must include BC/B.C.
or AD/A.D.
Action
Specify the BC/AD indicator in the date using the correct format.
ORA–01857
not a valid time zone
Cause
An incorrect time zone code was specified for the NEW_TIME function.
Action
Correct the invalid time zone code, then retry the operation.
ORA–01858
a non–numeric character found where a digit was expected
Cause
The input data to be converted using a date format model was incorrect. The format model expected a number but found a non–numeric character.
Action
Check the input data and the date format model to make sure the elements match in number and type, then retry the operation.
2 – 180
Oracle7 Server Messages
01800–01899: The Date Function
ORA–01859
a non–alphabetic character was found where a letter was expected Cause
The input data to be converted using a date format model was incorrect. The format model expected a letter but found a non–alphabetic character.
Action
Check the input data and the date format model to make sure the elements match in number and type, then retry the operation.
ORA–01860
week of year must be between 1 and 53
Cause
A week number outside the range 1 to 53 was specified.
Action
Use only a value within the valid range for the week number.
ORA–01861
literal does not match format string
Cause
Literals in the input string must be the same length as the literals in the format string, except for the leading white space characters. If the “FX” modifier is specified, the literal must match exactly, including the leading white space.
Action
Correct the format string to match the string literal.
ORA–01862
wrong number of digits for this format item
Cause
The number of digits in this format item is not equal to the number required for the format. This error usually occurs when the “FX” modifier (format exact) has been specified.
Action
Resubmit the command using the required amount of numbers for the
format mask.
ORA–01898
too many precision specifiers
Cause
While trying to truncate or round dates, extra data was found in the date format picture.
Action
Check the syntax of the date format picture and retry.
ORA–01899
bad precision specifier
Cause
An invalid precision code was specified in a date.
Action
Enter a valid precision code in the date format. Valid precision types are: century, year, month, day, Julian date, hours, minutes, and seconds.
Oracle7 Server Messages
2 – 181
01900–02039: SQL Parsing
01900–02039: SQL Parsing
This section lists some of the messages generated when SQL statements are parsed by the Oracle Server.
ORA–01900
LOGFILE keyword expected
Cause
The keyword LOGFILE is required in this context.
Action
Check the syntax, insert the keyword LOGFILE where required, then
re–execute the statement.
ORA–01901
ROLLBACK keyword expected
Cause
The keyword ROLLBACK is required in this context.
Action
Check the syntax, insert the keyword ROLLBACK where required, and
re–execute the statement.
ORA–01902
SEGMENT keyword expected
Cause
The keyword SEGMENT is required in this context.
Action
Check the syntax, insert the keyword SEGMENT where required, and
re–execute the statement.
ORA–01903
EVENTS keyword expected
Cause
The keyword EVENTS is required in this context.
Action
Check the syntax, insert the keyword EVENTS where required, and re–execute the statement.
ORA–01904
DATAFILE keyword expected
Cause
The keyword DATAFILE is required in this context.
Action
Check the syntax, insert the keyword DATAFILE where required, and
re–execute the statement.
ORA–01905
STORAGE keyword expected
Cause
The keyword STORAGE is required in this context.
Action
Check the syntax, insert the keyword STORAGE where required, and
re–execute the statement.
2 – 182
Oracle7 Server Messages
01900–02039: SQL Parsing