Release 8.1.5
A67785-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Error Messages Release 8.1.5 A67785-01 |
|
For more information about the Time Series option, refer to the Oracle8i Time Series User's Guide.
TS-00500 internal error
Cause: This is the generic internal error number for Time Series exceptions. This indicates that a process has encountered an exceptional condition.
Action: Contact Oracle Customer Support.
TS-00501 the input patterns are not of the same length
Cause: The input calendars have patterns of different lengths.
Action: Use calendars with patterns of the same length.
TS-00502 patanchor cannot be on the 29th or 30th day of the month
Cause: Time Series encountered a calendar having a pattern anchor on the 29th or 30th day of the month.
Action: Ensure that all calendar pattern anchors are not on the 29th or 30th day of the month.
TS-00503 patanchor can be null only for all-zero or all-one patterns
Cause: Pattern anchor was null, and pattern was not acceptable for a null patanchor. The anchor can be null only when using an all-zero or all-one pattern.
Action: Supply a pattern anchor date, or adjust the pattern.
TS-00504 illegal validflag parameter was passed to DisplayValCal/DisplayValTS
Cause: DisplayValCal or DisplayValTS was called with invalid parameters.
Action: Only call DisplayValCal and DisplayValTS with the output of ValidateCal or ValidateTS, respectively.
TS-00505 illegal outmessage parameter was passed to DisplayValCal/DisplayValTS
Cause: DisplayValCal or DisplayValTS was called with invalid parameters.
Action: Only call DisplayValCal and DisplayValTS with the output of ValidateCal or ValidateTS, respectively.
TS-00506 the calendar pattern is null
Cause: Time Series encountered a calendar having a null pattern.
Action: Ensure that all calendars have a non-null pattern.
TS-00507 the calendar has an imprecise mindate or maxdate
Cause: Time Series encountered a calendar having an imprecise MINDATE or MAXDATE.
Action: Ensure that all calendar MINDATEs and MAXDATEs are precise.
TS-00508 a NULL patanchor is illegal for calendars with frequencies - 5,7,10,16,18
Cause: Time Series encountered a calendar having a NULL pattern anchor date with one of the following frequencies:
Action: Ensure that all calendars with the frequency value in (5,10,16,18) have non-NULL pattern anchor dates.
TS-00509 the input calendars have unequal pattern bits greater than 1
Cause: Time Series encountered calendars having patterns with pattern bits greater than 1 and the corresponding pattern bits being unequal. For Union & Intersection operations, the two input calendars need to have matching pattern bits if the bits are greater than 1.
Action: Ensure that the two input Calendars passed in have patterns with matching pattern bits.
TS-00510 datetab has dates outside the bounds of the calendar
Cause: DeriveExceptions encountered dates outside of the input calendar's MINDATE/MAXDATE.
Action: Adjust MINDATE/MAXDATE or remove extraneous dates from the input DateTab.
TS-00511 calendar pattern bits array is either empty or null
Cause: Time Series encountered a calendar with an empty or null pattern bits array.
Action: Update the calendar to include a valid pattern.
TS-00512 invalid frequency value
Cause: Time Series encountered a calendar with an unsupported frequency.
Action: Restrict all calendars to frequencies: 1,2,3,4,5,6,7,8,10,16,18.
TS-00513 the input dates are in the wrong order
Cause: The date range provided was in reverse order.
Action: When specifying a date range, always list the earlier date first.
TS-00514 calendar pattern has an imprecise anchor date
Cause: Time Series encountered a calendar with an anchor having the wrong precision.
Action: Adjust the precision of the anchor to match the calendars frequency.
TS-00515 input date is beyond the calendar mindate/maxdate
Cause: Time Series encountered a date less than the MINDATE or greater than the MAXDATE.
Action: Ensure that all input dates are within the MINDATE-MAXDATE range of the calendar.
TS-00516 input date is greater than calendar maxdate
Cause: Time Series encountered a date greater than MAXDATE.
Action: Ensure that all input dates are within the MINDATE-MAXDATE range of the calendar.
TS-00517 unable to set precision of calendar pattern anchor
Cause: Time Series encountered a calendar with a pattern anchor whose precision cannot be set. Setting the precision of the anchor takes it beyond the allowed Oracle dates.
Action: Ensure that the calendar pattern anchor is at least frequency units from the minimum Oracle date (Julian 1). Pattern anchors have to lie within the following range: [Oracle MinDate + frequency, Oracle Maxdate].
TS-00519 the series attribute of the time series type is null
Cause: Time Series encountered a null series within a time series.
Action: Ensure that all time series have a non-null series component.
TS-00520 the input calendar is null
Cause: Time Series encountered a null calendar.
Action: Ensure that all calendars are non-null.
TS-00522 error scaling date to calendar
Cause: Input date cannot be scaled to given calendar.
Action: Ensure that the given calendar is valid and that the calendar's MINDATE and MAXDATE encompass all potential timestamp values.
TS-00523 the input date is null
Cause: Scaleup has encountered a null date. No scaling semantics are defined for a null date.
Action: Ensure that all input to Scaleup is non-null.
TS-00525 the input time series is null
Cause: Time Series encountered a null time series.
Action: Ensure that all time series are not atomically null.
TS-00526 the input time series has a null calendar
Cause: Time Series encountered a null calendar within a time series.
Action: Ensure that all time series include valid (non-null) calendars.
TS-00527 error scaling up to the target calendar frequency
Cause: Scaleup encountered a target calendar of finer frequency than that of the input time series' calendar.
Action: Scaleup requires a target calendar of equal or coarser frequency.
TS-00528 calendar has a null mindate or a null maxdate
Cause: Time Series encountered a calendar with a null MINDATE or MAXDATE.
Action: Ensure that all calendars have a valid MINDATE and MAXDATE.
TS-00529 calendar mindate is greater than its maxdate
Cause: Time Series encountered a calendar with MINDATE greater than MAXDATE.
Action: Ensure that all calendars have a valid MINDATE less than or equal to MAXDATE.
TS-00530 series indexes must be greater than 0
Cause: GetNthElement encountered an index less than 1.
Action: Use indexes greater than 0.
TS-00531 the input time series has a null calendar reference
Cause: Time Series encountered a time series with a null calendar reference.
Action: Ensure that all calendar references are valid.
TS-00532 unable to DEREF calendar referenced by time series
Cause: Time Series was unable to de-reference a calendar reference.
Action: Verify that the user executing the query has select privileges for the calendar table storing the object, and that the correct calendar has been referenced by the time series reference.
TS-00533 the time series has data beyond its calendar mindate/maxdate
Cause: Time Series encountered a time series with data beyond MINDATE/MAXDATE.
Action: Ensure that all time stamps in a time series are within the calendar's MINDATE/MAXDATE.
TS-00534 the number of rows requested must be a positive integer
Cause: The requested number of rows was less than 0.
Action: Use a positive number to specify the number of rows requested.
TS-00535 the time series ref has a null table_name parameter
Cause: Time Series encountered a time series reference having a null TABLE_NAME.
Action: Ensure that all time series references include a valid table name.
TS-00536 the time series ref has a null tstamp_colname parameter
Cause: Time Series encountered a time series reference having a null TSTAMP_COLNAME.
Action: Ensure that all time series references include a valid timestamp column name.
TS-00537 the time series ref has a null value_colname parameter
Cause: Time Series encountered a time series reference having a null VALUE_COLNAME.
Action: Ensure that all time series references include a valid value column name.
TS-00538 the time series ref has a null qualifier_colname parameter
Cause: Time Series encountered a time series reference having a null QUALIFIER_COLNAME.
Action: Ensure that all time series references include a valid qualifier column name.
TS-00539 the time series ref has a null qualifier_value parameter
Cause: Time Series encountered a time series reference having a null QUALIFIER_VALUE.
Action: Ensure that all time series references include a valid qualifier value.
TS-00540 the projected lead timestamp is beyond the calendar mindate/maxdate
Cause: The given parameters result in time stamps outside of MINDATE/MAXDATE.
Action: Adjust the lead timestamp or lead units to remain within calendar MINDATE/MAXDATE, or extend the MINDATE/MAXDATE.
TS-00541 the projected lag timestamp is beyond the calendar mindate/maxdate
Cause: The given parameters result in time stamps outside of MINDATE/MAXDATE.
Action: Adjust the lag timestamp or lag units to remain within calendar MINDATE/MAXDATE, or extend the MINDATE/MAXDATE.
TS-00542 the window size for mavg/msum must be >= 1
Cause: Window size parameter passed to moving average/sum was not greater than 0.
Action: Use a window size parameter greater than or equal to 1.
TS-00547 the input fill type is invalid
Cause: Fill has been called with a fill type less than 0 or greater than 2.
Action: Use a valid fill type: 0, 1, or 2.
TS-00548 the target timestamp for leading is invalid
Cause: The target timestamp input to the Lead function was invalid with respect to the input timeseries calendar.
Action: Ensure that the target timestamp input to the Lead function is a valid timestamp with respect to the input timeseries calendar.
TS-00551 error parsing the SQL statement with the time series ref
Cause: The SQL statement constructed from the time series reference was invalid.
Action: Verify the validity of the time series reference:
TS-00552 error executing the SQL statement with the time series ref
Cause: The SQL statement constructed from the time series reference was invalid.
Action: Verify the validity of the time series reference:
TS-00553 divide by zero error
Cause: An attempt was made to divide by zero with TSDivide.
Action: When dividing by a constant, ensure that the constant is non-zero.
TS-00554 the input calendar patterns are not equal
Cause: DeriveExceptions requires the reference time series' calendar to have the same pattern as the time series being processed.
Action: Ensure that DeriveExceptions is called only with time series having the same pattern.
TS-00555 the input calendar frequencies are not equal
Cause: DeriveExceptions requires the reference time series' calendar to have the same frequency as the time series being processed.
Action: Ensure that DeriveExceptions is called only with time series having the same frequency.
TS-00556 mindate of the ref calendar exceeds the mindate of the target calendar
Cause: DeriveExceptions encountered a reference time series' calendar having a MINDATE greater than that of the target time series' calendar.
Action: Ensure that DeriveExceptions is called only with appropriate time series.
TS-00557 maxdate of the target calendar exceeds the maxdate of the ref calendar
Cause: DeriveExceptions encountered a reference time series' calendar having a MAXDATE less than that of the target time series' calendar.
Action: Ensure that DeriveExceptions is called only with appropriate time series.
TS-00558 the target calendar should have empty on/off exception lists
Cause: DeriveExceptions encountered a target time series' calendar having non-empty exception lists.
Action: Ensure that DeriveExceptions is called only with target time series having empty exception lists.
TS-00559 the caltype field in the calendar has an illegal value
Cause: Time Series encountered a calendar with an invalid calendar type.
Action: Ensure that all calendars have valid calendar type value. Valid calendar types are: (Exception-driven calendars = 0).
TS-00560 the input data includes imprecise timestamps
Cause: DeriveExceptions function encountered an imprecise date in the timeseries (or datetab) input.
Action: Ensure that all the time stamps in the timeseries (datetab) are precise with respect to the target calendar before calling DeriveExceptions.
TS-00561 begin_create_ts_group has not been called
Cause: BEGIN_CREATE_TS_GROUP must be called before calling this procedure.
Action: Call BEGIN_CREATE_TS_GROUP before calling this function.
TS-00562 the column name is a duplicate
Cause: Two column names given for a time series were the same.
Action: Provide a unique column name for each time series column. Ensure that this column name does not conflict with any other column name including the explicit or default column name of the TSTAMP column or the column name of the GROUP_NAME column. Use GET_ATTRIBUTES to determine default values.
TS-00563 missing column attributes
Cause: A time series was defined without defining columns.
Action: Define at least one column for the time series using ADD_VARCHAR2, ADD_NUMBER, or ADD_INTEGER.
TS-00564 unknown storage model
Cause: The time series storage model specified does not correspond to a valid storage model.
Action: Ensure that the procedure is called with a valid storage model descriptor: 'OBJECT' or 'FLAT'.
TS-00565 wrong storage model
Cause: The time series procedure cannot be called for the storage model currently being defined.
Action: Ensure that the procedure called is appropriate for the time series being created.
TS-00566 unknown time series group
Cause: The time series definition specified is not known.
Action: Ensure that the call references a known time series definition.
TS-00567 unsupported datatype
Cause: The column datatype specified for a time series is not supported.
Action: Ensure that the column datatype for a time series is NUMBER, INTEGER, or VARCHAR2.
TS-00568 illegal call sequence
Cause: The function is not being called in the correct sequence.
Action: Ensure that the function is called in the correct sequence.
TS-00569 not all attributes dropped
Cause: Not all objects belonging to a time series group could be dropped. This was either because underlying objects no longer exist or because another timeseries definition references them.
Action: Get privileges to drop the object directly.
TS-00570 too many columns declared
Cause: Too many columns were declared for the time series. Please consult the documentation for a limit on the Maximum number of columns allowed.
Action: Declare another time series to accommodate the extra columns.
TS-00571 detail table must exist
Cause: ADD_EXISTING_COLUMN is illegal if the detail table does not exist.
Action: Call ADD_VARCHAR2_COLUMN or ADD_NUMBER_COLUMN procedure.
TS-00572 column not found
Cause: ADD_EXISTING_COLUMN was called for a column that does not exist in the detail table.
Action: Specify a NUMBER or VARCHAR2 column table in the existing detail table.
TS-00573 detail table must not exist
Cause: ADD_VARCHAR2_COLUMN, ADD_NUMBER_COLUMN is illegal if the detail table does not exist.
Action: Call ADD_COLUMN function when detail table exists.
TS-00574 log file is already open
Cause: OPEN_LOG was called when a log file is already open.
Action: Call CLOSE_LOG to close the current log file before calling OPEN_LOG.
TS-00575 parameters conflict with detail_table_exists
Cause: DETAIL_TABLE_ATTR, DETAIL_TABLE_PK, or TSNAME_LENGTH field was set to non-NULL values when DETAIL_TABLE_EXISTS was called with value of 1.
Action: When calling SET_FLAT_ATTRIBUTES with DETAIL_TABLE_EXISTS=1, DETAIL_TABLE_ATTR, DETAIL_TABLE_PK, and DETAIL_TSNAME_LENGTH parameters must be NULL.
TS-00576 parameters conflict with map_table_exists
Cause: MAP_TABLE_ATTR or MAP_TABLE_PK field was set to non-NULL values when MAP_TABLE_EXISTS was called with value of 1.
Action: When calling SET_FLAT_ATTRIBUTES with MAP_TABLE_EXISTS=1, MAP_TABLE_ATTR and MAP_TABLE_PK parameters must be NULL.
TS-00577 parameters conflict with cal_table_exists
Cause: CAL_TABLE_ATTR or CAL_TABLE_PK field was set to non-NULL values when CAL_TABLE_EXISTS was called with value of 1.
Action: When calling SET_FLAT_ATTRIBUTES with CAL_TABLE_EXISTS=1, CAL_TABLE_ATTR and CAL_TABLE_PK parameters must be NULL.
TS-00578 detail table not found
Cause: The detail table specified in SET_FLAT_ATTRIBUTES could not be found.
Action: Ensure that the detail table specified in SET_FLAT_ATTRIBUTES exists.
TS-00579 the tstamp field specified in SET_FLAT_ATTRIBUTES does not exist
Cause: The TSTAMP field is not found in the existing detail table.
Action: Ensure that the TSTAMP column name specified in SET_FLAT_ATTRIBUTES is in the detail table.
TS-00580 the tstamp field specified is not a DATE column
Cause: The call specified a TSTAMP field that is not a DATE datatype.
Action: Specify a TSTAMP column that is a DATE datatype.
TS-00581 the tsname field specified in SET_FLAT_ATTRIBUTES does not exist
Cause: The TSNAME field is not found in the existing detail table.
Action: Ensure that the TSNAME field column name specified in SET_FLAT_ATTRIBUTES is in the detail table.
TS-00582 the tsname field specified is not a VARCHAR2 column
Cause: The call specified a TSNAME field that is not a VARCHAR2 datatype.
Action: Specify a TSNAME column that is a VARCHAR2 datatype.
TS-00583 existing detail table missing primary key constraint
Cause: An attempt was made to build a time series on a detail table that is missing a required primary key constraint.
Action: Ensure that the detail table has a primary key constraint on the TSNAME and TSTAMP columns.
TS-00584 existing detail table missing index with tsname as first column
Cause: An attempt was made to build a time series on a detail table that does not specify the TSNAME field as the first column of a primary key index.
Action: Ensure that the detail table has a primary key constraint on the TSNAME and TSTAMP columns.
TS-00585 existing detail table missing index with tstamp as second column
Cause: An attempt was made to build a time series on a detail table that does not specify the TSTAMP field as the second column of a primary key index.
Action: Ensure that the detail table has a primary key constraint on the TSNAME and TSTAMP columns.
TS-00586 calendar table not found
Cause: The calendar table specified in SET_FLAT_ATTRIBUTES could not be found.
Action: Ensure that the calendar table specified in SET_FLAT_ATTRIBUTES exists.
TS-00587 calendar table not correct type
Cause: The calendar table specified in SET_FLAT_ATTRIBUTES was not an object table of type ORDSYS.ORDTCALENDAR.
Action: Ensure that the calendar table specified in SET_FLAT_ATTRIBUTES is an object table of type ORDSYS.ORDTCALENDAR.
TS-00588 calendar table missing primary key constraint
Cause: An attempt was made to build a time series on a calendar table that is missing a required primary key constraint.
Action: Ensure that the calendar table has a primary key constraint on the NAME field.
TS-00589 existing calendar table missing index with NAME as first column
Cause: An attempt was made to build a time series on a calendar table that does not specify the NAME field as the first column of a primary key index.
Action: Ensure that the calendar table has a primary key constraint on the NAME field.
TS-00590 map table not found
Cause: The map table specified in SET_FLAT_ATTRIBUTES could not be found.
Action: Ensure that the map table specified in SET_FLAT_ATTRIBUTES exists.
TS-00591 existing map table missing CALNAME field
Cause: The map table specified should have field called CALNAME of type VARCHAR2(256).
Action: Check to see that the existing map table specified is correct and has the required fields.
TS-00592 the CALNAME field in the existing map table is not a VARCHAR2 field
Cause: The existing map table specified should have a field call CALNAME of type VARCHAR2.
Action: Check to see that the existing map table specified is correct and has the required fields.
TS-00593 the CALNAME VARCHAR2 field is not of length 256
Cause: The existing map table specified should have a VARCHAR2 field called CALNAME of a length of 256.
Action: Check to see that the existing map table specified is correct and has the required fields.
TS-00594 the existing map table is missing the tsname column
Cause: The existing map table specified should have a field of the same name as the TSNAME column in the detail table.
Action: Check to see that the existing map table specified is correct and has the required fields.
TS-00595 the tsname field in the map table is not a VARCHAR2 column
Cause: The TSNAME field in the existing map table must be a VARCHAR2 field.
Action: Check to see that the existing map table specified is correct and has the required fields.
TS-00596 the length of the tsname field in the existing map table is incorrect
Cause: The length of the TSNAME field in the existing map table must be the same length as the TSNAME field in the detail table.
Action: Check to see that the existing map table specified is correct and has the required fields.
TS-00597 the map table is missing a primary key constraint
Cause: The map table specified must have a primary key constraint on the TSNAME field.
Action: Check to see that the existing map table specified is correct and has the required fields.
TS-00598 the map table is missing an index on the tsname field
Cause: An attempt was made to build a time series on a map table that does not specify the TSNAME field as the first column of a primary key index.
Action: Check to see that the existing map table specified is correct and has the required fields.
TS-00599 illegal input param values
Cause: The combination or the values of the input parameters are illegal.
Action: Check to see that the values and combination of input parameters to the call are correct.
TS-00600 update of tstamp value is illegal
Cause: An instead of trigger detected an attempt to update the TSTAMP field.
Action: Updates of TSTAMP fields in a time series are not permitted.
TS-00601 update of tsname value is illegal
Cause: An update trigger detected an attempt to update the TSNAME field.
Action: Updates of TSNAME fields in a time series are not permitted.
TS-00602 no calendar found
Cause: An insert or delete trigger failed to retrieve a calendar for a regular time series.
Action: Check to see that the time series being updated has a calendar associated with it.
TS-00603 tstamp date not valid
Cause: An insert was done using a timestamp date value that was not valid for the calendar.
Action: Check to see that the timestamp date is valid for the calendar of the time series.
TS-00604 time stamp must be next valid date before startdate
Cause: An attempt was made to insert a time stamp that was not the first legal date before the starting date.
Action: Check to see that the timestamp date is valid for the calendar of the time series.
TS-00605 time stamp must be next valid date after enddate
Cause: An attempt was made to insert a time stamp that was not the first legal date after the ending date.
Action: Check to see that the timestamp date is valid for the calendar of the time series.
TS-00606 cannot delete a legal date in the middle of a time series
Cause: An attempt was made to delete a timestamp in the middle of a time series.
Action: Delete time stamps from the ends of the time series.
TS-00607 time series group exists
Cause: The time series group specified already exists.
Action: Ensure that BEGIN_CREATE_TS_GROUP specifies a time series group that does not already exist.
TS-00608 no time series instance found
Cause: An insert or delete trigger failed to retrieve the time series instance.
Action: Check to see that the time series instance specified exists.
TS-00609 begin_create_ts_group already called
Cause: An attempt was made to call BEGIN_CREATE_TS_GROUP while currently defining a time series group.
Action: Call CANCEL_CREATE_TS_GROUP or complete a time series group definition that has been started.
TS-00610 nothing to cancel
Cause: Tried to call CANCEL_CREATE_TS_GROUP when no time series group definition has been started.
Action: Avoid making this call if a time series definition has not been started.
TS-00611 the frequency is not valid
Cause: The frequency passed into the function does not correspond to a valid calendar frequency value.
Action: Ensure that the call is passed a valid calendar frequency value.
TS-00612 the time series type specified is not supported
Cause: A wrong type was specified for the time series object table to be created.
Action: The only supported types for the time series object table are: ORDSYS.ORDTNUMSERIEA and ORDSYS.ORDTVARCHAR2SERIES.
TS-00613 time series object table not found
Cause: The time series object table specified in SET_OBJECT_ATTRIBUTES could not be found.
Action: Ensure that the time series object table specified in SET_OBJECT_ATTRIBUTES exists.
TS-00614 existing object table is of different type
Cause: The type of the (existing) object table does not match the type of the time series specified.
Action: Ensure that while trying to build a time series group on an existing object table, the type of the time series matches the type of the object table. Note that the only supported types for the time series are: ORDSYS.ORDTNUMSERIES and ORDSYS.ORDTVARCHAR2SERIES.
TS-00615 time series object table missing primary key constraint
Cause: Tried to build a time series on an object table that is missing a required primary key constraint.
Action: Ensure that the time series object table has a primary key constraint on the NAME field.
TS-00616 existing time series object table missing index on the NAME attribute
Cause: An attempt was made to build a time series on an object table that does not specify the name field as the first column of a primary key index.
Action: Ensure that the time series object table has a primary key constraint on the name field.
TS-00617 parameters conflict with object_table_exists
Cause: OBJECT_TABLE_ATTRIBUTES, STORAGE_TABLE_NAME, STORAGE_TABLE_ATTRIBUTES or OBJECT_TABLE_PK field was set to non-null value when SET_OBJECT_ATTRIBUTES was called with OBJECT_TABLE_EXISTS set to 1.
Action: Ensure that when SET_OBJECT_ATTRIBUTES is called with OBJECT_TABLE_EXISTS set to 1, OBJECT_TABLE_ATTRIBUTES, STORAGE_TABLE_NAME, STORAGE_TABLE_ATTRIBUTES and OBJECT_TABLE_PK are all set to NULL.
TS-00618 setprecision was called with unsuppored arguments
Cause: An attempt was made to call SetPrecision using a date and frequency as the arguments. This interface is no longer supported. SetPrecision now requires a calendar and a date as its arguments.
Action: Call SetPrecision with a calendar and a date, or change the database compatibility mode to 8.0.5. Note, changing the database compatibility mode will prevent new features from working.
TS-00619 OVERFLOW clause required in storage_table_attributes
Cause: OBJECT_TABLE_ATTRIBUTES was set using SET_OBJECT_ATTRIBUTES to a clause that did not include OVERFLOW. This is required when creating an object store of ORDTVARCHAR2SERIES.
Action: Ensure that when SET_OBJECT_ATTRIBUTES is called with OBJECT_TABLE_TYPE set to ORDTVARCHAR2SERIES that there is an OVERFLOW clause specified within the OBJECT_TABLE_ATTRIBUTES.
TS-00620 time series is invalid
Cause: A object view insert or update trigger failed because the new time series instance was not a valid time series.
Action: Check to see that the new time series being inserted or updated is a valid time series.
TS-00630 an irregular time series is not a valid input
Cause: DeriveExceptions function requires that the input time series be a regular time series (an irregular time series does not have an associated calendar and hence, is an illegal input to the DeriveExceptions function).
Action: Ensure that the time series input to the DeriveExceptions function is a regular time series.
TS-00631 lead and lag operations not supported for irregular timeseries
Cause: Lead and Lag operations require calendars to compute the time stamps of the resulting time series.
Action: Ensure that Lead and Lag are only used with timeseries that have calendars.
TS-00632 fill is not supported for irregular timeseries
Cause: Fill requires a calendar to compute the time stamps of the resulting time series.
Action: Ensure that Fill is only used with timeseries that have calendars.
TS-00633 table attribute value is too large
Cause: A table attribute value passed in was too large.
Action: Ensure that the table attribute VARCHAR2 value is less than 1023.
TS-00640 time series cannot be scaled to target calendar - frequencies incompatible
Cause: The frequencies of the time series and the calendar are not compatible.
Action: Ensure that the calendar associated with the scaled time series is compatible with the target calendar.
TS-00641 time series cannot be scaled to target calendar - calendar anchors incompatible
Cause: The calendar anchors associated with the time series and the calendar are not compatible.
Action: Ensure that the calendar associated with the scaled time series is compatible with the target calendar.
TS-00642 time scaling error: input interval straddles two or more output intervals
Cause: An interval of the source time series straddles two or more intervals of the target scaling calendar.
Action: Ensure that the time series to be scaled is compatible with the target calendar.
TS-00643 time scaling error: input interval maps to non-existing output interval
Cause: One or more cells of the input time series have no associated interval of the target calendar.
Action: Ensure that the time series to be scaled is compatible with the target calendar.
TS-00644 time scaling error: permitDropData parameter out of bounds
Cause: An invalid value of permitDropData was supplied as a parameter to Scaleup
Action: Ensure that the permitDropData parameter is either 0 or 1.
TS-00645 scaledownrepeat is not supported for irregular time series
Cause: A time series with a null calendar was passed to ScaleDownRepeat.
Action: Ensure that all time series used with ScaleDownRepeat have calendars.
TS-00646 scaledownsplit is not supported for irregular time series
Cause: A time series with a null calendar was passed to ScaleDownSplit.
Action: Ensure that all time series used with ScaleDownSplit have calendars.
TS-00647 invalid scaleup option
Cause: An unrecognized option has been used with a ScaleUp function.
Action: Consult the documentation for a list of valid options.
TS-00648 invalid combination of scaleup options
Cause: Multiple numeric options or a combination of numeric and named options has been used with ScaleUp
Action: Consult the documentation for a list of valid options, and ensure that named options are not used with a numeric option, and that no more than one numeric option is specified.
TS-00649 invalid scaleup option
Cause: An unrecognized numeric option has been used with a ScaleUp function. Valid numeric options include 0, 1, 10, and 11.
Action: Be sure to only use valid numeric options or consult the documentation for information about using named options.
TS-00650 duplicate scaleup option
Cause: A ScaleUp option has been specified twice, or two conflicting options have been specified.
Action: When using multiple named options be sure not to duplicate options and not to use conflicting options. Consult the documentation for a list of conflicting options.
