Utility messages (20000 through 23030)
SQL 20000
20000 File system error error number occurred during file open.
Cause
SQL was not able to open the requested file and received error error number.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20001
20001 File system error error number occurred during file read.
Cause
SQL was not able to open the requested file and received error error number.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20002
20002 File system error error number occurred during file write.
Cause
SQL was not able to write to the requested file and received error error number.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20003
20003 File system error error number occurred during file close.
Cause
SQL was not able to close the requested file and received error error number.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20004
20004 File system error error number occurred while trying to set EOF to zero for file.
Cause
SQL was not able to set EOF to zero for the requested file and received error error number.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20005
20005 File system error error number occurred while retrieving file info.
Cause
SQL was not able to retrieve information for the requested file and received error error number.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20006
20006 File system error error number occurred while enabling large transfers for file.
Cause
SQL could not enable a large transfer to the requested file and received error number.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20007
20007 Transaction Management subsystem could not commit the current transaction.
Cause
The utility subsystem that performs transaction management operations failed while trying to commit the current transaction.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20008
20008 An internal error occurred - buffer size is not a multiple of the block size for file.
Cause
The utility subsystem that performs fast data transfer was sent an invalid buffer size.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20009
20009 An internal error occurred - buffer size is larger than maximum transfer size for file.
Cause
The utility subsystem responsible for performing fast data transfer was sent an invalid buffer size.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20010
20010 Previous read in file failed.
Cause
The utilities subsystem that performs fast data transfer received an error when attempting to read data from the file. This error possibly results from retrying a previously failed read operation.
Effect
The operation fails.
Recovery
Use the errors that accompany this one to diagnose and correct the problem with the previous file read.
SQL 20011
20011 An internal error occurred while performing a command on file file. Statement is out of sequence.
-
FILE OPEN
-
FILE READ
-
FILE WRITE
-
FILE CLOSE
-
SET LARGE TRANSFER
-
FILE ALLOCATE/DEALLOCATE
-
FILE SET EOF TO 0
Cause
The utility subsystem that performs a file request received a request out of sequence.
Effect
The operation fails.
Recovery
Do not attempt recovery. Contact your service provider.
SQL 20012
20012 Previous write in file failed.
Cause
The utility subsystem that performs fast data transfer could not successfully write data into the file. This error possibly results from a previous failed write to the same partition.
Effect
SQL is unable to complete the command.
Recovery
Determine what caused the previous command to fail and correct the problem.
SQL 20013
20013 An internal error occurred - did not enable large transfer for file.
Cause
The utility subsystem that performs fast data transfer performed steps out of sequence.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20014
20014 File system error error number occurred while getting allocated extents for file.
Cause
SQL was not able to obtain the number of allocated extents for the requested file and received error error number.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20015
20015 An internal error occurred - no write access for file.
Cause
The utility subsystem that performs fast data transfer performed operations out of sequence.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20016
20016 File system error error number occurred while getting block size for file.
Cause
SQL was not able to obtain the blocksize for the requested file and received error error number.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20017
20017 File system error error number occurred while getting partition length for file.
Cause
SQL was not able to obtain the partition length (EOF) for the requested file and received error error number.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20018
20018 An internal error occurred. There is an inconsistency between the data type (type) and default state (default) for column (name).
-
Where,
-
type is the SQL_DATA_TYPE specified in the COLS metadata table;
-
default is the DEFAULT_CLASS specified in the COLS metadata table;
-
name is the COLUMN_NAME specified in the COLS metadata table.
Cause
NonStop SQL/MX found a discrepancy while reading metadata information. The information returned is inconsistent. This is an internal error.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20019
20019 An internal error occurred. An invalid default state (state) exists in the COLS metadata table for column (name).
-
Where,
-
state is the DEFAULT_CLASS specified in the COLS metadata table;
-
name is the COLUMN_NAME specified in the COLS metadata table.
Cause
NonStop SQL/MX found a discrepancy while reading metadata information. The information returned is inconsistent. This is an internal error.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20020
20020 An internal error occurred. The number of columns (num1) defined for the referenced table table1 does not match the number of columns (num2) defined on the referencing table table2 for constraint const.
-
Where,
-
num1 is the number of columns associated with the referenced table constraint;
-
table1 is the name of the referenced table;
-
num2 is the number of columns associated with the referencing table constraint;
-
table2 is the name of the referencing table;
-
const is the name of the constraint for the referencing table.
Cause
NonStop SQL/MX found a discrepancy while reading metadata information. The information returned is inconsistent.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20021
20021 An internal error occurred - invalid column data type.
Cause
The utility subsystem that reads and maintains metadata encountered an unexpected data type for a column.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20022
20022 The field length (lengthvalue) for column columnname does not match the required length (requiredlength).
-
Where,
-
lengthvalue is the value of the field length specified in the format file;
-
columnname is the corresponding column name;
-
requiredlength is the required value for the field length.
Cause
The field length provided in the format file (for binary import) and the field length required by the column are not the same.
Effect
The operation fails.
Recovery
Correct the field length in the format file and resubmit.
SQL 20023
20023 Object does not exist.
Cause
The utility subsystem that reads and maintains metadata could not find the requested SQL/MX object. A possible cause is that the catalog, schema, or object name is misspelled in the request. SQL/MX objects can be catalogs, schemas, tables, trigger temporary tables, stored procedures, indexes, or MP aliases.
Effect
The operation fails.
Recovery
Check for misspellings and resubmit.
SQL 20024
20024 Object already exists.
Cause
You tried to create a table that exists.
Effect
The operation fails.
Recovery
Change the name of the table and resubmit.
SQL 20025
20025 An internal error occurred while trying to access metadata for object object-name. Expecting cache state (state1) but cache state is (state2).
-
[not] opened,
-
[not] closed,
-
[not] modified,
-
[not] created.
Cause
Illegal sequence of operations performed by a utility.
Effect
The operation fails.
Recovery
Do not attempt recovery. Contact your service provider.
SQL 20026
20026 An internal error occurred - invalid privilege type.
Cause
The utility subsystem that reads and maintains metadata encountered an unexpected privilege type.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20027
20027 The specified begin key is greater than the end key for an ADD, MOVE, or DROP data request.
Cause
You attempted to add, move, or drop data, but the beginning key range you specified is greater than the ending key range, which is not supported.
Effect
The operation fails.
Recovery
Specify a beginning key range that is less than the ending key range.
SQL 20028
20028 Specified an invalid partition physical size, should be BYTES, MBYTES, KBYTES, or GBYTES.
Cause
You specified an invalid partition physical size, which must be expressed in bytes, megabytes, kilobytes, or gigabytes.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 20029
20029 Key range was specified incorrectly, most likely because either the begin key was specified as non-inclusive (>) or end key specified as inclusive (=).
Cause
You specified an invalid key range, possibly because you specified the begin key as noninclusive (>) or specified the end key as inclusive (=).
Effect
The operation fails.
Recovery
Correct the first key value and resubmit.
SQL 20030
20030 The specified start key cannot be HIGH_VALUES.
Cause
You specified a start key as HIGH_VALUES, which is not supported.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20031
20031 The specified end key cannot be LOW_VALUES.
Cause
You specified an end key as LOW_VALUES, which is not supported.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20032
20032 An internal problem was detected.
Cause
SQL detected an internal error.
Effect
SQL is unable to process the statement.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20033
20033 The partition must be empty before you drop it.
Cause
You attempted to drop a nonemtpy range partition.
Effect
The operation fails.
Recovery
Make sure that the range partition is empty before dropping it.
SQL 20034
20034 Catalog does not exist or has not been registered on the local node.
Cause
The catalog is not visible on the local node, either because it does not exist or because it exists elsewhere in the network and has not been registered on the local node. This utility message corresponds to message 1002.
Effect
The operation fails.
Recovery
Verify the location of the catalog and resubmit.
SQL 20035
20035 Schema does not exist.
Cause
You specified a modify request without a valid schema name.
Effect
The operation fails.
Recovery
Verify the location of the schema and resubmit.
SQL 20036
20036 Table table-name does not exist.
Cause
The MODIFY utility could not find the specified table.
Effect
The operation fails.
Recovery
Check the spelling of the specified table name and resubmit.
SQL 20037
20037 An invalid operation was specified - only ADD, DROP, and MOVE are supported.
Cause
You specified a request that was not ADD, DROP, MOVE, or REUSE.
Effect
The operation fails.
Recovery
Check the spelling in the request and resubmit.
SQL 20038
20038 The specified key value uses incorrect syntax.
Cause
You specified a key value with incorrect syntax.
Effect
The operation fails.
Recovery
Check the syntax of the specified partitioning key value and resubmit.
SQL 20039
20039 For the MOVE, DROP, and REUSE requests, the key range must specify an exact partition range.
Cause
You used the add-move-boundary-range syntax instead of partition-identification to identify a partition to be moved, dropped, or reused, but you did not specify the exact partition range.
Effect
The operation fails.
Recovery
Reissue the request with the correct partition range. Consider using the partition-identification syntax instead.
SQL 20040
20040 An internal error occurred - file name not specified while getting file label information.
Cause
The utility subsystem that retrieves data from the file system failed because no file name was specified to the subsystem.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20041
20041 File system error error number was encountered.
Cause
The utility subsystem that retrieves data from the file system failed with an unexpected error.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20042
20042 Importing binary data to UCS2 character column columnname is not allowed.
Cause
You attempted to import UCS2 character data in binary mode.
Effect
The operation fails.
Recovery
Prepare the UCS2 data in a UCS2 data file and import it in delimited mode.
SQL 20043
20043 The specified attribute cannot be modified for the existing object.
Cause
You attempted to modify a nonmodifiable attribute of a table.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20044
20044 An internal error occurred - invalid file attribute.
Cause
The utility subsystem that reads and maintains metadata encountered an unexpected value for a file attribute.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20045
20045 An internal error occurred - invalid sort order.
Cause
The utility subsystem that reads and maintains metadata encountered an unexpected value for the sort order (ASC, DESC) on the primary key.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20046
20046 An internal error occurred - invalid size unit.
Cause
The utility encountered an unexpected value for a size unit designation.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20047
20047 An internal error occurred - invalid store option.
Cause
The utility subsystem that reads and maintains metadata encountered an unexpected value for the STORE BY option for the table.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20048
20048 Range requested for the operation does not specify a subset of a single partition.
Cause
You attempted to add a partition or move a boundary of an existing partition with an invalid key range. The key range specified must be a subset of an existing partition, either the prefix or the suffix.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 20049
20049 File system error error occurred while retrieving the name of the local system.
Cause
An unexpected error occurred while decomposing a Guardian file name or template.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20050
20050 The modify request failed. See subsequent errors for more details.
Cause
You attempted to perform a modify request, which failed.
Effect
The operation fails.
Recovery
Use the messages that accompany this one to diagnose and correct the problem.
SQL 20051
20051 Transaction Management subsystem could not rollback the current transaction.
Cause
The utility subsystem that performs transaction management operations failed while trying to roll back the current transaction.
Effect
The operation fails.
Recovery
Use the messages that accompany this one to diagnose and correct the problem.
SQL 20052
20052 Transaction Management subsystem could not set the AutoCommit.
Cause
The utility subsystem that performs transaction management operations failed while trying to set the auto commit attribute.
Effect
The operation fails.
Recovery
Use the messages that accompany this one to diagnose and correct the problem.
SQL 20053
20053 Transaction Management subsystem could not begin a new transaction.
Cause
The utility subsystem that performs transaction management operations failed while trying to begin a new transaction.
Effect
The operation fails.
Recovery
Use the messages that accompany this one to diagnose and correct the problem.
SQL 20054
20054 An internal error occurred - Transaction Management subsystem could not do Close()on a transaction.
Cause
The utility subsystem that performs CLI requests to SQL failed trying to clean up memory upon completion of a request.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20055
20055 An internal error occurred - Transaction Management subsystem could not prepare a dynamic SQL statement.
Cause
The utility subsystem that performs CLI requests to SQL failed trying to prepare a dynamic SQL statement as part of the current request.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20056
20056 An internal error occurred - Transaction Management subsystem could not close a statement.
Cause
The utility subsystem that performs CLI requests to SQL failed trying to close a previously executed SQL statement.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20057
20057 An internal error occurred - Transaction Management subsystem could not do GetRowsAffected on a statement.
Cause
The utility subsystem that performs CLI requests to SQL failed trying to extract the number of rows affected from the previously executed request.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20058
20058 The specified data file does not exist or cannot be opened for READ access.
Cause
The input file specified as the command-line option for IMPORT does not exist or could not be opened.
Effect
The operation fails.
Recovery
Verify that the input data file exists and is in a valid state.
SQL 20059
20059 The specified format file does not exist or cannot be opened for READ access.
Cause
The format file specified as the command-line option for IMPORT does not exist or could not be opened.
Effect
The operation fails.
Recovery
Verify that the format file exists and is in a valid state.
SQL 20060
20060 The -F command-line option cannot have a negative value.
Cause
You specified the first row (or record) to be imported as a negative value. The first row of the input file is designated as the number 0 (zero).
Effect
The operation fails.
Recovery
Specify a first-row value of either 0 (zero) or a positive value.
SQL 20061
20061 The -C command line option must have a value greater than zero.
Cause
You specified the number of rows (or records) to be imported as a negative value.
Effect
The operation fails.
Recovery
Specify a positive num-rows value.
SQL 20062
20062 The -T command-line option must have a value greater than zero.
Cause
The transaction-size value that you specified is either negative or zero.
Effect
The operation fails.
Recovery
Specify a positive transaction-size value.
SQL 20064
20064 The file type specified in the command line is not valid. Only DELIM or FIXED (case insensitive) can be specified.
Cause
You specified an invalid file type for the -W attribute.
Effect
The operation fails.
Recovery
Specify a valid file type attribute: DELIM or FIXED.
SQL 20065
20065 The target table name is not specified.
Cause
You did not specify a table name as a parameter to the IMPORT command.
Effect
The operation fails.
Recovery
Specify a valid table name in the ANSI name format.
SQL 20066
20066 The specified error file does not exist or cannot be opened for write access.
Cause
The error file that you specified cannot be opened because it was not created, or it has been corrupted.
Effect
The operation fails.
Recovery
Verify that the error file has been created. If it exists, check to see if the file is corrupted.
SQL 20067
20067 A syntax error occurred at or before: string0.
Cause
You specified the wrong syntax.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 20068
20068 An internal error or exception occurred.
Cause
SQL detected an internal error.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20069
20069 The field delimiter should not contain a qualifier character.
Cause
The field delimiter string that you specified, either at the command line or in the DELIMITED FORMAT section of the format file, contains a field qualifier character.
Effect
The operation fails.
Recovery
Specify a field delimiter string that does not contain a field qualifier character and resubmit.
SQL 20070
20070 Columns in the datafile are not correct. Columns found so far: columnnumber
Cause
The specific field in the current row in the input file could not be processed.
Effect
The operation fails.
Recovery
Check the specified column in the current row for valid data.
SQL 20071
20071 The row delimiter should not contain a qualifier character.
Cause
The row delimiter string that you specified, either at the command line or in the DELIMITED FORMAT section of the format file, contains a field qualifier character.
Effect
The operation fails.
Recovery
Specify a row delimiter string that does not contain a field qualifier character and resubmit.
SQL 20072
20072 First character of the field delimiter must be different than the first character of the row delimiter.
Cause
The field delimiter and row delimiter strings that you specified, either at the command line or in the DELIMITED FORMAT section of the format file, start with the same character. When only one of them is specified at the command line, the value for the other delimiter is either the default value, as specified in the IMPORT topic of the SQL/MX Reference Manual, or the value specified in the DELIMITED FORMAT section of the format file.
Effect
The operation fails.
Recovery
Specify a row delimiter and field delimiter that start with a different character and resubmit. If you specify only one at the command line, it should not start with the same character as the other delimiter.
SQL 20073
20073 Object objname does not exist.
Cause
The object name that you specified was invalid or does not exist.
Effect
The operation fails.
Recovery
Specify a valid object name. Verify that the catalog name, schema name, and table name sections of the ANSI name are specified.
SQL 20074
20074 IMPORT cannot open datafile - file name.
Cause
SQL was unable to open the data file that you specified either because it was missing or because of some other file system problem. The input file might be corrupt or, if it resides on a remote system, the remote system password is not set.
Effect
The operation fails.
Recovery
Check the validity of the input file. If the input file is a valid remote file, verify that the remote password for the system is set.
SQL 20079
20079 User does not have INSERT privilege to perform import operation for object object-name.
Cause
You do not have the minimum required privileges to perform the IMPORT operation.
Effect
The operation fails.
Recovery
Obtain the required INSERT privileges and resubmit.
SQL 20080
20080 Last row processed was rownum.
Cause
An error occurred while processing the input data file, and import terminated after processing the row number specified.
Effect
The import was partially completed.
Recovery
Use the message that is shown before this one to diagnose and correct the problem.
SQL 20081
20081 Row number rownum and column number columnnum could not be processed. Column Data: text.
Cause
An internal error occurred in a stored procedure.
Effect
The import was partially completed. It terminated while processing the row specified.
Recovery
None. Contact your service provider.
SQL 20082
20082 The fixed-width data file does not contain enough data to be imported into the current row at column columnnum.
Cause
The fixed-width data file is incomplete and does not provide enough data at the end of the file for importing.
Effect
The last transaction of the import is aborted, and all rows in that transaction are not imported.
Recovery
Append more data to the end of the data file.
SQL 20083
20083 The column name in the FIXED WIDTH FORMAT part of the format file is not valid.
Cause
The column name that you specified in the FIXED WIDTH FORMAT part of the format file was invalid.
Effect
The operation fails.
Recovery
Correct the column name in the FIXED WIDTH FORMAT part of the format file and resubmit.
SQL 20084
20084 The start position in the FIXED WIDTH FORMAT part of the format file is not valid.
Cause
The start position for one of the columns that you specified in the FIXED WIDTH FORMAT part of the format file was invalid.
Effect
The operation fails.
Recovery
Verify and correct the column start position in the FIXED WIDTH FORMAT part of the format file and resubmit.
SQL 20085
20085 The column size in FIXED WIDTH FORMAT part of the format file is not valid.
Cause
The column size that you specified for one of the columns in the FIXED WIDTH FORMAT part of the format file was invalid.
Effect
The operation fails.
Recovery
Correct the column size specified for one of the columns in the FIXED WIDTH FORMAT part of the format file and resubmit.
SQL 20086
20086 Column columname in the FIXED WIDTH FORMAT part of the format file is not found in the target table. Key = keyval
-
Where,
-
columnname is the column name specified in the FIXED WIDTH FORMAT part of the format file.
-
keyval is the column key value specified in the FIXED WIDTH FORMAT part of the format file.
Cause
You specified an invalid column name for one of the columns in the FIXED WIDTH FORMAT part of the format file.
Effect
The operation fails.
Recovery
Verify and correct the column name in the FIXED WIDTH FORMAT part of the format file and resubmit.
SQL 20087
20087 One or more of the specified command-line arguments are not valid. Syntax: import catalog.schema.table -I input-file [-C number-of-rows] [-E error-file] [-F rows-to-skip] [-L max-errors] [-R multiple of trans-size] [-S] [-T trans-size] [-U format-file] [-W file-type] [-FD field-delimiter] [-QL field-qualifier] [-RD row-delimiter] [-Z character-set]
Cause
One or more of the command line arguments that you specified were invalid.
Effect
The operation fails.
Recovery
See the SQL/MX Reference Manual for the correct parameters for the IMPORT command.
SQL 20088
20088 The format file name is not present in compile time arguments. Key=keyval.
Cause
The format file name was missing from an internal message.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20089
20089 The column name is not found in compile time arguments. Key = columnname
Cause
The column name that you specified was missing from an internal message.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20090
20090 The column type is not present in compile time arguments. Key=columntype
Cause
The column name that you specified was missing from an internal message.
Effect
The operation fails.
Recovery
None. Contact your service provider
SQL 20091
20091 The column size is not specified in compile time arguments. Key= columnsize
Cause
The column size that you specified was missing from an internal message.
Effect
The import operation fails.
Recovery
None. Contact your service provider.
SQL 20092
20092 The column precision is not present in compile time arguments. Key = precision
-
Where,
-
precision is the column precision specified in the FIXED WIDTH FORMAT part of the format file.
Cause
The precision value that you specified was missing from an internal message.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20093
20093 The column scale is not present in compile time arguments. Key = scale
Cause
The scale value that you specified was missing from an internal message.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20094
20094 Column first precision not present in compile time arguments. Key = precision.
Cause
The specified attribute value is missing from an internal message.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20095
20095 The column last precision is not present in compile time arguments. Key=lastprecision
Cause
The scale value that you specified was missing from an internal message.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20096
20096 The column IsSkipped is not present in compile time arguments. Key=value.
Cause
The attribute value that you specified was missing from an internal message.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20097
20097 Date order dateorder is not valid.
Cause
The date order that you specified was invalid.
Effect
The operation fails.
Recovery
Valid date order values are MDY, MYD, DMY, DYM, YMD, and YDM. Correct the date order in the DATE FORMAT section of the format file.
SQL 20098
20098 The column name is not specified in the COLUMN FORMAT section of the format file.
Cause
The column name was missing from the COLUMN FORMAT section of the format file.
Effect
The operation fails.
Recovery
Verify that the column names specified in the COLUMN FORMAT section of the format file are correct and add names that are missing.
SQL 20099
20099 Column columnname defined as NOT NULL NO DEFAULT cannot be skipped.
Cause
The skip flag for this column in the COLUMN FORMAT section of the format file was set to Y, but the column was defined as NOT NULL NO DEFAULT and, therefore, cannot be skipped.
Effect
The operation fails.
Recovery
Set the skip flag to Y or N in the COLUMN FORMAT section of the format file.
SQL 20100
20100 No value is specified for ‘skip' in the COLUMN FORMAT of the format file. Column name=columnname.
Cause
The skip flag was missing for this column from the COLUMN FORMAT section of the format file.
Effect
The operation fails.
Recovery
Set the skip flag to Y or N in the COLUMN FORMAT section of the format file.
SQL 20101
20101 detail text.
Cause
SQL has received an error as shown in the detail text.
Effect
The operation fails.
Recovery
Use the detail text to diagnose and correct the problem.
SQL 20102
20102 The object name should not have a trailing blank.
Cause
The utility subsystem that reads and maintains metadata discovered an unexpected blank in an object name.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20103
20103 The object name contains an invalid character: position in string pos, length of string len, value found char.
Cause
You specified an object name that contains an illegal character.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 20104
20104 The object name is over the maximum length.
Cause
You specified an object name that exceeds the maximum length.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 20105
20105 An internal error occurred - invalid object type.
Cause
SQL detected an internal error while performing a utility operation.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20106
20106 An internal error occurred - invalid lock mode.
Cause
SQL detected an internal error while performing a utility operation.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20107
20107 An internal error occurred - invalid access option.
Cause
SQL detected an internal error while performing a utility operation.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20108
20108 A qualifier is missing in the data file. Column Number=columnnumber.
Cause
There is a missing or mismatched field qualifier for the column in the data file.
Effect
The operation fails.
Recovery
Verify the data and add the missing qualifier.
SQL 20109
20109 details.
Cause
An unexpected error was returned from the CLI while accessing file system information.
Effect
The operation fails.
Recovery
Use the accompanying error messages to diagnose and correct the problem.
SQL 20110
20110 IMPORT cannot insert data into a populated table that is not audited. Delete the data or have an administrator make the table audited.
Cause
You tried to import into a destination file that was populated with data and was not audited, which is invalid.
Effect
The operation fails.
Recovery
Either delete the data or make the table audited.
SQL 20111
20111 Source catalog catalog-name does not exist or cannot be accessed.
Cause
You specified a source catalog name that does not exist or could not be accessed.
Effect
The operation fails.
Recovery
Correct the catalog name and resubmit.
SQL 20112
20112 Source schema schema name does not exist or cannot be accessed.
Cause
You specified a source schema name that does not exist or could not be accessed.
Effect
The operation fails.
Recovery
Correct the schema name and resubmit.
SQL 20113
20113 Source table table name does not exist or cannot be accessed.
Cause
You specified a source table name that does not exist or could not be accessed.
Recovery
The operation fails.
Effect
Correct the table name and resubmit.
SQL 20114
20114 Target catalog catalog name does not exist or cannot be accessed.
Cause
You specified a target catalog name that does not exist or could not be accessed.
Effect
The operation fails.
Recovery
Correct the catalog name and resubmit.
SQL 20115
20115 Target schema schema name does not exist or cannot be accessed.
Cause
You specified a target schema name that does not exist or could not be accessed.
Effect
The operation fails.
Recovery
Correct the schema name and resubmit.
SQL 20116
20116 Target table is the same as source. Operation failed.
Cause
The target table name you specified was the same as the source table name.
Effect
The operation fails.
Recovery
Correct the target table name and resubmit.
SQL 20117
20117 Catalog catalog name does not exist or cannot be accessed.
Cause
You specified a catalog name that does not exist or could not be accessed.
Effect
The operation fails.
Recovery
Verify the catalog name and resubmit.
SQL 20118
20118 Schema schema name does not exist or cannot be accessed.
Cause
You specified a schema name that does not exist or could not be accessed.
Effect
The operation fails.
Recovery
Verify the schema name and resubmit.
SQL 20119
20119 Table table name does not exist or cannot be accessed.
Cause
You specified a table name that does not exist or could not be accessed.
Effect
The operation fails.
Recovery
Verify the table name and resubmit.
SQL 20120
20120 Partition does not exist or cannot be accessed.
Cause
You specified a partition that does not exist or could not be accessed.
Effect
The operation fails.
Recovery
Verify the partition name and resubmit.
SQL 20121
20121 Partition is not the last in a table that is not key-sequenced. PURGEDATA cannot be performed.
Cause
The table being purged has multiple partitions and is not key-sequenced. This type of table is not supported.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20122
20122 Table has indexes. Cannot purge data from partition.
Cause
You attempted to perform a partial PURGEDATA operation, which is supported only on tables that do not have dependent indexes. The table you requested has dependent indexes.
Effect
The operation fails.
Recovery
Remove any associated indexes and resubmit. If this is not possible, perform a DELETE request in the range of the specified partition.
SQL 20123
20123 A user-defined transaction has been started. Utility-operation cannot be performed.
Cause
You attempted to perform a utility operation after a user-defined transaction was started.
Effect
The operation fails.
Recovery
Commit or roll back the transaction and resubmit.
SQL 20125
20125 table name is a metadata table. PURGEDATA cannot be performed on metadata tables.
Cause
The table name that you specified was a metadata table. You cannot perform the PURGEDATA operation on metadata tables.
Effect
The operation fails.
Recovery
Specify a different table and resubmit.
SQL 20127
20127 Target option was specified as NEW but object-type exists. DUP operation failed.
Cause
The target name you specified was not valid.
Effect
The operation fails.
Recovery
Specify TARGET PURGE for an existing target object and resubmit.
SQL 20128
20128 table name is a metadata table. DUP cannot be performed on metadata tables.
Cause
The table name that you specified was a metadata table. You cannot perform the DUP operation on metadata tables.
Effect
The operation fails.
Recovery
Specify a different table and resubmit.
SQL 20129
20129 Internal error occurred while performing DUP.
Cause
An internal error occurred while performing the DUP operation.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20130
20130 The Column IsNullable not present in compile time arguments. Key=keyval.
Cause
The specified attribute was missing from an internal message.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20131
20131 The row delimiter is missing from the data file.
Cause
The row delimiter was missing from the delimited input data file.
Effect
The operation fails.
Recovery
Add a row delimiter and run the import again.
SQL 20132
20132 A NULL value cannot be assigned to a NOT NULL NO DEFAULT field. Column number=column number
Cause
You attempted to import data that would assign a NULL to a NOT NULL field.
Effect
The IMPORT operation fails.
Recovery
Either change the data or change the field to accept NULL.
SQL 20133
20133 A user defined transaction has been started. DUP cannot be performed.
Cause
You cannot perform the DUP operation under a user-defined transaction.
Effect
The DUP operation fails.
Recovery
Commit or roll back the user-defined transaction and resubmit.
SQL 20134
20134 IMPORT can not open errorfile - file name.
Cause
SQL was unable to open the file name that you specified with the -E command-line option.
Effect
The IMPORT operation fails.
Recovery
Specify a valid error file name and resubmit.
SQL 20136
20136 The qualifier must be a single character.
Cause
The field qualifier that you specified, either at the command line or in the DELIMITED FORMAT section of the format file, is more than one character long.
Effect
The operation fails.
Recovery
Specify a single character qualifier at the command line or in the DELIMITED FORMAT section of the format file and resubmit.
SQL 20137
20137 table has features that require schema version version1 or higher. The version of schema is version2. Cannot perform DUP.
-
Where,
-
table is the source table for the DUP operation;
-
version1 is the object feature version (OFV) of table. This is the lowest schema version that can store the features of the source table;
-
schema is the target schema for the DUP operation;
-
version2 is the version of schema.
Cause
The DUP operation attempts to dup the source table into a target schema of a lower version, which cannot store the features of the source table.
Effect
The DUP operation fails.
Recovery
None. Contact your service provider.
SQL 20138
20138 The dummy column in the format file must be skipped.
Cause
You specified an invalid column name in the COLUMN FORMAT section of the format file.
Effect
The operation fails.
Recovery
Specify a valid column name.
SQL 20139
20139 ABORTTRANSACTION failed with TMF error error number.
Cause
The utility subsystem that performs CLI operations failed while trying to perform an ABORTTRANSACTION.
Effect
The operation fails.
Recovery
Use the messages that accompany this one to diagnose and correct the problem.
SQL 20140
20140 Wrong parameter name passed.
Cause
The utility subsystem responsible for performing CLI operations failed while trying to get information from the returned statement. This is an internal error.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20141
20141 Wrong parameter index passed.
Cause
The utility subsystem that performs CLI operations failed while trying to get information from the returned statement.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20142
20142 An internal error occurred - invalid datatype
invalid-datatype. Allowed datatypes are '' and ''.
charvarchar
Cause
The utility subsystem that performs CLI operations failed while trying to get information from the returned statement.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20143
20143 Equal sign is missing.
Cause
An equal sign is missing from an equation.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 20145
20145 Key range specified for a table that is not a key-sequenced table. PURGEDATA cannot be performed.
Cause
You attempted to perform a PURGEDATA operation on a table by specifying a key range. The table is not a key-sequenced table and therefore there are no key ranges to specify.
Effect
The operation fails.
Recovery
Perform the PURGEDATA request without specifying key ranges.
SQL 20146
20146 Key does not exist. Cannot perform PURGEDATA.
Cause
The key value you specified in the partition map clause does not specify a valid partition.
Effect
The operation fails.
Recovery
Specify a valid partition map and resubmit.
SQL 20147
20147 User specified an empty range. Cannot perform PURGEDATA.
Cause
The range that you specified is empty.
Effect
The operation fails.
Recovery
Verify the key range and resubmit.
SQL 20148
20148 Begin key same as end key. PURGEDATA cannot be performed.
Cause
The list of partitions specified in the key range has the same begin and end key. There are no partitions to purge.
Effect
The operation fails.
Recovery
Specify a valid key range and resubmit.
SQL 20149
20149 External indexes exist for this object-type. Since the source and target have the same catalog and schema, index-map must be specified. DUP cannot be performed.
Cause
You failed to define all the indexes of the index-map.
Effect
The operation fails.
Recovery
Specify the target indexes through the index-map clause and resubmit.
SQL 20150
20150 Since the source and target have the same catalog and schema, the source and the target names in index map and constraint map must be unique. DUP cannot be performed.
Cause
The source and target names in the index-map or the constraint-map are the same.
Effect
The operation fails.
Recovery
Fix the index-map or constraint-map clause and resubmit.
SQL 20151
20151 IMPORT does not currently support binary data files.
Cause
The format file has a line that specifies
FileIsBinary=Y.This option is not supported in the current release of NonStop SQL/MX.
Effect
The operation fails.
Recovery
Change the format file to specify
FileIsBinary=N and resubmit.
SQL 20152
20152 The VARCHAR varying-length can support non-binary FIXED-WIDTH format file only.
Cause
You specified VARCHAR for a format file that is binary FIXED-WIDTH.
Effect
SQL is not able to perform the IMPORT operation.
Recovery
Verify your format file and resubmit.
SQL 20153
20153 The VARCHAR varying-length can support VARCHAR data type only.
Cause
You specified VARCHAR for a column that is not a VARCHAR data type.
Effect
The operation fails.
Recovery
Verify your data file and resubmit.
SQL 20154
20154 Column Null or Default flag is not present in COMPILE TIME ARGS. Key=key value
Cause
SQL encountered an internal error in the stored procedure interface.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20155
20155 Column default value is not present in COMPILE TIME ARGS. Key=key value
Cause
SQL encountered an internal error in the stored procedure interface.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20157
20157 Assigning a DEFAULT value to the NO DEFAULT field. Column number=column number
Cause
You attempted to assign a default value to a field, in column number, with NO DEFAULT.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 20160
20160 Error occurred while encoding key value key value for catalog.schema.table.
Cause
You specified an invalid key value for the first key of a partition.
Effect
The operation fails.
Recovery
Correct input data and resubmit.
SQL 20161
20161 Resume option of RECOVER command for DUP is possible only if DUP finished the data transfer between the source and target objects. RECOVER cannot be performed.
Cause
You cannot specify the RESUME option before bulk I/O has finished.
Effect
The operation fails.
Recovery
Use the CANCEL option to cancel the request. Start a new DUP request after RECOVER is done.
SQL 20162
20162 catalog.schema.table. Object is not valid.
Cause
The utility subsystem that reads and maintains metadata could not successfully read information for catalog.schema.table.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20163
CREATE TABLE LIKE20163 An internal error occurred - invalid include option of .
Cause
SQL was unable to perform the requested operation.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20164
20164 The search condition for the specified check constraint has a syntax error.
Cause
You attempted to create a check constraint, but a syntax error was found in the search condition.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 20165
20165 The number of key columns ( value1) defined on the table or index is less than the number of key columns (value2) defined in the request.
Cause
The number of columns defined in the partitioning key for the table or index is less than the number of columns defined in the VALUE clause.
Effect
The operation fails.
Recovery
Verify the number of key columns in the table and resubmit.
SQL 20166
20166 Reserved words cannot be used for an object name.
Cause
You used an SQL reserved word as an object name.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 20167
20167 The object name must contain at least one character.
Cause
The object name that you specified is not valid. It must contain at least one character.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 20168
20168 The partition key value cannot be specified when adding a partition to a hash-partitioned table or index.
Cause
You specified partitioning key values in an "Add a new hash partition" request. You can specify the partitioning key values only when adding a new range partition.
Effect
The operation fails.
Recovery
Remove the WHERE clause and resubmit.
SQL 20169
20169 Only the last partition of a hash-partitioned table or index can be dropped.
Cause
The partition you specified in the DROP request is not the last partition.
Effect
The operation fails.
Recovery
Use the LAST PARTITION syntax and resubmit.
SQL 20170
20170 The specified location does not exist.
Cause
The partition that you specified in the LOCATION clause does not exist.
Effect
The MODIFY utility did not process the request.
Recovery
Check the location of the partition and resubmit.
SQL 20171
20171 section name section is missing in the format file.
Cause
The section name is missing from the format file.
Effect
The operation fails.
Recovery
Correct the format file and resubmit.
SQL 20172
20172 RecordLength is missing in the FIXED WIDTH FORMAT section of the format file.
Cause
The record length value is missing in the FIXED WIDTH FORMAT section of the format file.
Effect
The operation fails.
Recovery
Correct the format file and resubmit.
SQL 20173
20173 A transaction must be started before executing this request.
Cause
SQL detected an internal error.
Effect
SQL is unable to process the statement.
Recovery
None This is an internal error. Contact your service provider.
SQL 20174
20174 An internal error occurred - A valid SQLNode is expected.
Cause
SQL detected an internal error.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20175
20175 An internal error occurred - trying to commit or rollback a transaction that does not exist.
Cause
SQL detected an internal error.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20176
20176 A concurrent utility or DDL operation (operation) is being performed on object object-name. It must complete before the requested utility operation can run.
-
Where,
-
operation is type of operation that is currently holding the DDL lock. Operation is one of the following: BACKUP, DUP, IMPORT, MODIFY TABLE, POPULATE INDEX, RECOVER, RESTORE, UPDATE STATISTICS, REFRESH, UPGRADE, DOWNGRADE, GIVE SCHEMA, FASTCOPY, and PURGEDATA;
-
object-name is the name of the SQL object. For example, table, view, synonym, trigger, and so on;
-
utility is name of utility that is running, for example – PURGEDATA.
Cause
You attempted to execute a utility or alter the DDL of an object while a concurrent utility or DDL operation was being performed on the object, its parent, or its dependent.
Effect
The operation fails.
Recovery
Retry the utility operation once the previous utility operation has completed.
SQL 20177
20177 Resume option of RECOVER command for Import is possible only if Import finished inserting the data in the target table. RECOVER cannot be performed.
Cause
The resume option is not allowed for the failed IMPORT operation because the data insertion part was not finished.
Effect
The operation fails.
Recovery
Retry the operation using the CANCEL option of the RECOVER utility.
SQL 20178
20178 Internal error occurred while performing Import.
Cause
An unspecified internal error occurred during the IMPORT utility operation.
Effect
The operation fails.
Recovery
None. Use the RECOVER utility to retrieve the table in a usable format.
SQL 20179
20179 An unexpected error condition was encountered.
Cause
The MODIFY utility encountered an unexpected error condition.
Effect
Depending on the severity of the problem, the MODIFY utility might not process the request, or it might partially process the request.
Recovery
Execute the RECOVER command to undo the changes made by the aborted request. If the recovery does not complete successfully, contact your service provider.
SQL 20180
20180 section name section of the format file is not valid.
Cause
The specified section name in the format file was invalid.
Effect
The operation fails.
Recovery
Correct the format file and resubmit.
SQL 20181
20181 Begin key is greater than end key. PURGEDATA cannot be performed.
Cause
The list of partitions specified in the key range specified an invalid range. There are no partitions to purge.
Effect
The operation fails.
Recovery
Specify a valid key range and resubmit.
SQL 20182
20182 An internal error was encountered: OPEN of Import Stored Procedure failed.
Cause
SQL encountered an internal error in the stored procedure interface.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20183
20183 The key value definition contains an invalid character string (value column-value).
-
Where,
-
column-value is the partitioning key value whose data type is incompatible with the character data type of the corresponding partitioning key column.
Cause
The data type of the specified partitioning key value column-value was incompatible with the character type of the corresponding partitioning key column.
Effect
The operation fails.
Recovery
Correct the partitioning key value and resubmit.
SQL 20184
20184 The syntax of the format file file name is not valid.
Cause
The format file name that you specified was not a valid format file.
Effect
The operation fails.
Recovery
Correct the format file and resubmit.
SQL 20185
20185 More than one partition resides on volume volume name. The MODIFY utility does not know which partition to move or drop.
Cause
You specified only the volume name in the LOCATION clause, but the object has more than one partition in the specified volume.
Effect
The operation fails.
Recovery
Correct the sections in the format file and resubmit.
SQL 20186
20186 A syntax error was found near ‘char' at line number line number.
-
Where,
-
char is the data that the IMPORT command cannot process;
-
line number is the line number where the problem occurred.
Cause
SQL detected a syntax error near char at line number.
Effect
The operation fails.
Recovery
Correct the data in the input file and resubmit.
SQL 20188
20188 Command line options -L and -XL must specify a value greater than or equal to zero and less than or equal to 2147483646.
Cause
The command line options -L and -XL must specify a value greater than or equal to zero and less than or equal to 2147483646.
Effect
The operation fails.
Recovery
Specify a value greater than or equal to zero and resubmit.
SQL 20189
20189 Data in the primary partition (or subset) cannot be moved to the previous partition because no previous partition exists.
Cause
You tried to move data in the first partition to a nonexisting previous partition.
Effect
The operation fails.
Recovery
Remove the TO PREVIOUS PARTITION phrase and resubmit.
SQL 20190
20190 Data in the last partition (or subset) cannot be moved to the next partition because no next partition exists.
Cause
You tried to move data in the last partition to a nonexisting next partition.
Effect
The operation fails.
Recovery
Remove the TO NEXT PARTITION phrase and resubmit.
SQL 20191
20191 This operation is not supported on nonaudited tables.
Cause
You issued a MODIFY request on a nonaudited table, which is not supported.
Effect
SQL is unable to prepare the statement.
Recovery
If the MODIFY operation is required, alter the table to audited, perform the MODIFY, and then alter the table back to nonaudited.
SQL 20192
20192 Operation is not allowed because table table name is a metadata table.
Cause
You tried to perform a modify request on a metadata table, which is not supported.
Effect
The operation fails.
Recovery
None.
SQL 20193
20193 This operation cannot be performed under a user-defined transaction.
Cause
You cannot perform a POPULATE INDEX operation under a user-defined transaction.
Effect
The operation fails.
Recovery
Commit or roll back the user-defined transaction and resubmit.
SQL 20194
20194 Loading of index index-name failed.
Cause
The index load failed because of some problem.
Effect
The operation fails.
Recovery
If the problem was caused by a uniqueness violation, remove duplicate rows, and resubmit. If the problem occurred for some other reason, use the messages that accompany this one to diagnose and fix the problem.
SQL 20195
20195 The specified index (index-name) does not belong to table (table-name).
-
Where,
-
index-name is the index to be populated as specified by the POPULATE INDEX command;
-
table-name is the table or view being populated.
Cause
The index name specified by the caller does not belong to the table or view being populated.
Effect
The operation fails.
Recovery
Specify a valid name and resubmit.
SQL 20196
20196 The specified index index-name contains user data.
Cause
The index name specified by the caller should not contain data. Data was found to exist, most likely because a previous POPULATE INDEX command failed.
Effect
The operation fails.
Recovery
Execute the RECOVER command to clean up the previously failed command and resubmit.
SQL 20197
20197 The specified index index-name is not available.
Cause
The index name specified by the caller is not valid. The caller qualifying the index name with a catalog or schema is the probable cause. Catalog and schema names are not supported.
Effect
The operation fails.
Recovery
Specify a valid name, and resubmit.
SQL 20198
20198 A syntax error was found near ‘string', near character position int.
-
Where,
-
string is the value where the syntax error was detected;
-
int is the byte location in the string where the error occurred.
This message is obsolete for users who have applied T1058G10ABO or a superseding SPR.
Cause
You specified the wrong syntax.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 20199
20199 An internal error or exception occurred.
Cause
An unknown error occurred while populating an index.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20200
20200 Catalog does not exist.
Cause
You specified a catalog name that is not defined or not visible on the system.
Effect
The operation fails.
Recovery
Specify a valid catalog name and resubmit.
SQL 20201
20201 Schema does not exist.
Cause
The schema name specified by the caller is not valid.
Effect
The operation fails.
Recovery
Specify a valid schema name and resubmit.
SQL 20202
20202 Table does not exist.
Cause
The specified table does not exist.
Effect
The operation fails.
Recovery
Specify the correct object name and resubmit.
SQL 20203
20203 Index index-name does not exist.
Cause
The MODIFY utility could not find the specified index.
Effect
The operation fails.
Recovery
Check the spelling of the specified index name and resubmit.
SQL 20204
20204 The specified recover option is not allowed on (object-name).
Cause
The index name could not be recovered with the given RECOVER command.
Effect
The operation fails.
Recovery
Use the correct RECOVER option and resubmit.
SQL 20205
20205 Index index-name is online. Cannot perform POPULATE INDEX.
Cause
An attempt to populate the index that is already populated.
Effect
None.
Recovery
None.
SQL 20206
20206 Data type conversion failed while converting key value (column-value[, column-value]...)to data type(s) ( data-type[,date-type]...) for object-name.
-
Where,
-
column-value is a column value in the specified partitioning key value;
-
data-type is the data type of a column in the partitioning key column list;
-
object-name is the name of the specified table or index, in ANSI SQL name format.
Cause
You specified a key column value whose data type was incompatible with the data type of the corresponding partition key column.
Effect
The operation fails.
Recovery
None.
SQL 20208
20208 A user transaction is running.
Cause
You cannot perform a RECOVER operation under a user-defined transaction.
Effect
The operation fails.
Recovery
Commit or roll back the user-defined transaction, and resubmit.
SQL 20209
20209 Nothing remains to be recovered on object-name.
Cause
Recovery is not needed for object-name.
Effect
The operation fails.
Recovery
If object-name was not incorrectly added, no recovery is required.
SQL 20210
20210 A DDL_LOCKS name must be specified for object-name.
Cause
RECOVER found multiple entries for the current table or index that needs to be recovered and cannot determine which operation to recover.
Effect
The operation fails.
Recovery
Select the lock name from the DDL_LOCKS metadata table to determine which operation to recover and resubmit.
SQL 20211
20211 Specified DDL_LOCKS name lock-name is not found.
Cause
A DDL_LOCKS lock name was specified but not found, possibly because the wrong name was specified.
Effect
The operation fails.
Recovery
Specify the correct name and resubmit.
SQL 20212
20212 Utility process is still running for DDL_LOCKS name lock-name.
Cause
You attempted to recover an operation that is still running.
Effect
The operation fails.
Recovery
Determine the operation that is currently running, wait until it completes, and then resubmit.
SQL 20213
20213 An internal error occurred during RECOVER.
Cause
An unknown error occurred while recovering a utility operation.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20214
20214 No recover is defined for DDL_LOCKS name lock-name.
Cause
A request was made to recover an operation which is not specified correctly in the metadata.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20215
20215 Recovery failed for DDL_LOCKS name lock-name.
Cause
The RECOVER operation could not be performed onlock lock-name.
Effect
The operation fails.
Recovery
Check for other messages to determine the cause of failure, and resubmit.
SQL 20216
20216 No recover is available for object object-name.
Cause
A request was made to recover an operation which is not specified correctly in the metadata.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20217
20217 Catalog does not exist.
Cause
The catalog name specified by the caller is not defined or not visible on the current system.
Effect
The operation fails.
Recovery
Specify a valid catalog name and resubmit.
SQL 20218
20218 Schema does not exist.
Cause
The schema name specified by the caller is not defined or not visible on the current system.
Effect
The operation fails.
Recovery
Specify a valid schema name and resubmit.
SQL 20219
20219 Table table-name does not exist.
Cause
The table name specified by the caller is not defined or not visible on the current system.
Effect
The operation fails.
Recovery
Specify a valid table name and resubmit.
SQL 20220
20220 Index (index-name) does not exist.
Cause
The index name specified by the caller is not defined or not visible on the current system.
Effect
The operation fails.
Recovery
Specify a valid name and resubmit.
SQL 20221
20221 A syntax error was found near ‘string', near character position int.
-
Where,
-
string is the value where the syntax error was detected;
-
int is the byte location in the string where the error occurred.
As of this ABU SPR, this message is no longer generated.
Cause
You specified the wrong syntax.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 20222
20222 Error occurred for partition file file name when attempting to set the number of index levels.
Cause
An unexpected error occurred while completing a data movement operation for the request.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20223
20223 Internal error on unsupported character set conversion.
Cause
An invalid character set designation was encountered.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20224
20224 This table cannot be purged because at least one of the referencing tables is not empty.
Cause
You attempted to purge data from a table that is being referenced by at least one non-empty table through referential integrity constraint.
Effect
The operation fails.
Recovery
Remove the referential integrity constraint and resubmit.
SQL 20225
20225 Table table-name is a hash-partitioned object. PURGEDATA does not allow individual or sets of partitions to be purged, only the entire table can be purged.
Cause
You attempted to purge individual partitions of a hash-partitioned table, which is not supported.
Effect
The operation fails.
Recovery
Either purge the entire file or use a DELETE statement (DML statement) to remove the required rows.
SQL 20226
20226 An internal error occurred - trigger parameter is not set.
Cause
The utility subsystem that reads and maintains the metadata could not find all the information for a trigger.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20227
20227 The specified syntax is not supported for a hash-partitioned table or index.
Cause
You issued a REUSE request for a hash-partitioned table, or you moved the hash partition to an existing partition location.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20228
20228 An internal error occurred - DDL Lock does not exist for the source table. Cannot perform RECOVER.
Cause
The DDL_LOCK specified was not defined in metadata.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20229
20229 A request to update the index status for index index-name failed. DUP could not be performed.
Cause
An unexpected error is returned during the final phase of duplicating indexes to the target table.
Effect
The operation fails.
Recovery
Use the messages that accompany this one to diagnose and correct the problem.
SQL 20230
20230 You cannot drop all partitions of the table or index. At least one partition must remain.
Cause
You tried to drop the only remaining partition of a table or index.
Effect
The operation fails.
Recovery
If you want to drop the last remaining partition, use the DROP TABLE or INDEX statement.
SQL 20231
20231 The specified syntax is valid only with a hash-partitioned table or index.
Cause
You issued a request containing syntax that is valid only with a hash-partition table or index.
Effect
The operation fails.
Recovery
Check the syntax and resubmit.
SQL 20232
20232 This operation cannot be done on a nonaudited table that contains data.
Cause
You tried to perform a MODIFY utility on a nonaudited table containing data.
Effect
The operation fails.
Recovery
None.
SQL 20233
20233 No partition could be found in volume volume name for the specified object.
Cause
The MODIFY utility could not find, in volume volume-name, partitions that belong to the specified object.
Effect
The operation fails.
Recovery
None.
SQL 20234
20234 Partition partition could not be found.
Cause
The MODIFY utility could not locate the specified partition.
Effect
The operation fails.
Recovery
None.
SQL 20235
20235 Error returned from USER_GETINFO_ while converting userid to user name, status: status, userid: userid.
Cause
An unexpected error was returned while converting the current user ID to user name.
Effect
The operation fails.
Recovery
Diagnose the returned status described in the Guardian Procedure Errors and Messages Manual to determine the problem and resubmit.
SQL 20236
20236 Error returned from USER_GETINFO_ while converting username to userid, status: status, username: username.
Cause
An unexpected error was returned while converting the current user name to user ID.
Effect
The operation fails.
Recovery
Diagnose the returned status described in the Guardian Procedure Errors and Messages Manual to determine the problem and resubmit.
SQL 20237
20237 An internal error occurred: invalid username specified, username: username.
Cause
The user name is not valid.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20238
20238 A user-defined transaction has been started. The MODIFY utility cannot perform the partition management operation.
Cause
You started a user-defined transaction (using the BEGIN WORK command) before starting the MODIFY command. The MODIFY utility manages its own transactions.
Effect
The operation fails.
Recovery
You can commit or roll back the transaction (using the COMMIT WORK or ROLLBACK WORK command) and then resubmit.
SQL 20239
20239 default-attribute is not a valid default attribute.
Cause
You specified an invalid attribute value for attribute PM_ONLINE_TRANSACTION_GRANULARITY for online operation and attribute PM_OFFLINE_TRANSACTION_GRANULARITY for offline operation.
Effect
The operation fails.
Recovery
Commit or roll back the transaction (using the COMMIT WORK or ROLLBACK WORK command) and resubmit.
SQL 20240
20240 Table table-name has materialized views. The utility-name utility cannot be performed.
-
Where,
-
table-name is the name of the table on which the utility operation is attempted.
-
utility-name is the name of the utility operation attempted.
Cause
A utility operation was attempted on the table that has a dependent materialized view.
Effect
The operation fails.
Recovery
Drop the materialized view and rerun the operation.
SQL 20241
20241 The MODIFY utility cannot perform a DROP HASH operation on the object object-name because the target partition partition-name does not have enough space for the redistribution of data.
Cause
The MODIFY DROP HASH operation failed because the remaining partitions do not have enough space for the redistribution of the dropped partition data.
Effect
The operation fails.
Recovery
Increase the maxextents of the object so that the target partitions can handle the increase in the space.
SQL 20242
20242 The table has DELETE triggers enabled on it. Please disable them and try again.
Cause
The specified table has DELETE triggers enabled on it, so you cannot purge data from it.
Effect
The operation fails.
Recovery
Disable the DELETE trigger and retry the PURGEDATA request.
SQL 20243
20243 Unicode data file file has no byte order mark at the beginning.
Cause
Two byte order mark bytes cannot be found at the beginning of the Unicode data file.
Effect
The Unicode data import fails.
Recovery
Re-create the Unicode data file and add the two byte order marks.
SQL 20244
20244 The byte order mark in Unicode data file file is not valid.
Cause
The byte order mark bytes specified are invalid.
Effect
The Unicode data import fails.
Recovery
Re-create the Unicode data file. Specify the standard byte order mark sequence: 0xFF 0xFE, for the little- endian byte order, and 0xFE 0xFF, for the begin-endian byte order.
SQL 20245
20245 An invalid character set was specified. Column column-name is part of the partitioning key and must be defined with the character set ISO88591.
Cause
You specified a literal, with a character set other than ISO8859, for column column-name, which is part of the partition key.
Effect
The operation fails.
Recovery
Partition key columns must be defined with character set ISO88591.
SQL 20246
20246 The utility-name utility operation is not supported on object-name.
-
Where,
-
utility-name is the name of the utility operation attempted.
-
object-name is the name of the object on which the utility operation is attempted.
Cause
A utility operation was attempted on an object for whose type the operation is not yet supported.
Effect
The operation fails.
Recovery
None.
SQL 20250
20250 The first partition cannot be reused because the specified new key range overlaps the existing key range of the first partition.
Cause
You tried to reuse the first partition, but the new key range that you specified (in the WITH clause) overlaps the existing key range of the first partition.
Effect
The operation fails.
Recovery
None.
SQL 20251
20251 Request operation uses the same partition location as another request in the command.
Cause
This is an internal error.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20252
20252 Only a single ADD, MOVE, DROP, or REUSE request is allowed.
Cause
You included more than one request to the MODIFY command. The REUSE request works only with range-partitioned tables.
Effect
The operation fails.
Recovery
None.
SQL 20253
20253 The new key range must be empty before you can reuse a partition.
Cause
The table already has data in the key range specified in the WITH clause of the REUSE request.
Effect
The operation fails.
Recovery
None.
SQL 20254
20254 Partition could not be reused because the partition's key range contains data and the PURGEDATA option was not specified.
Cause
The specified partition contains data, but you did not specify the PURGEDATA option in the REUSE request.
Effect
The operation fails.
Recovery
None.
SQL 20255
20255 An invalid partition management operation was specified for an index. Only ADD, DROP, and MOVE requests are supported.
Cause
You attempted a partition management request other than ADD, DROP, or MOVE on an index. The REUSE request works only with range-partitioned requests.
Effect
The operation fails.
Recovery
None.
SQL 20257
20257 This partition management operation is not supported for system-clustered base table table-name.
Cause
You attempted a partition management operation other than moving an entire partition to a new location.
Effect
The operation fails.
Recovery
None.
SQL 20258
20258 The WHERE clause cannot be used with table-name because it is a system-clustered base table.
Cause
You specified the WHERE clause in the request to move the partition of a system-clustered base table to a new location.
Effect
The operation fails.
Recovery
None.
SQL 20259
20259 An internal PURGEDATA error occurred.
Cause
An unexpected error was detected.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20261
20261 The WHERE clause must be used with object-name because it has more than one partition.
Cause
In the WHERE clause, you did not specify the partition in the request to move the partition to a new location. When the object has more than one partition, you must specify the partition.
Effect
The operation fails.
Recovery
None.
SQL 20262
20262 Online operation is not supported on unpopulated indexes.
Cause
You attempted a MODIFY operation WITH SHARED ACCESS on an unpopulated index.
Effect
The MODIFY operation fails.
Recovery
Populate the index using the POPULATE INDEX command and then retry the operation.
SQL 20263
20263 An invalid DUP operation was specified; The INDEX ON option is required for duplicating unique and/or nonclustering primary key constraints.
Cause
The INDEX ON option is required for duplicating a source table with unique or nonclustering primary key constraints.
Effect
The operation fails.
Recovery
Specify the INDEX ON option and resubmit.
SQL 20264
20264 Invalid index names were specified in index-map. Cannot perform DUP.
Cause
One or more of the source index names specified in the index-map clause is not part of the source table.
Effect
The operation fails.
Recovery
Enter the correct source index name and resubmit.
SQL 20265
20265 Error error number returned during a call to SPI command command.
-
Where,
-
error number is the error returned from the SPI interface;
-
command is the SPI command being processed.
Cause
An unexpected error was returned from SPI when MODIFY attempted to start an ORSERV process to perform a FUP RELOAD operation.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20266
20266 Invalid message code code1 returned from SPI request, expecting code2.
Cause
An unexpected error was returned from SPI when MODIFY attempted to start an ORSERV process to perform a FUP RELOAD operation.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20267
20267 Returned buffer from SPI request has a length of len1, expected a value less than or equal to len2.
Cause
An unexpected error was returned from SPI when MODIFY attempted to start an ORSERV process to perform a FUP RELOAD operation.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20268
20268 The audit attribute of table table name which was turned off during import operation could not be turned on.
Cause
The audit attribute of the table is turned off during the IMPORT operation if the table is empty and contains no indexes. This enables IMPORT to use Side Tree inserts for better performance. The audit attribute could not be turned back on after the IMPORT operation was complete because of an internal failure.
Effect
The IMPORT operation is complete. The table might remain in an unaudited state.
Recovery
See the Guardian Procedure Errors and Messages Manual file system errors for possible recovery action and resubmit.
SQL 20269
20269 The audit attribute of table table-name could not be turned off during import operation.
Cause
The audit attribute of the table could not be turned off during the IMPORT operation due to an internal failure. The attribute is turned off when the table is empty and contains no indexes. This enables IMPORT to use Side Tree inserts for better performance. The attribute is turned back on after the IMPORT operation is complete.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual file system errors for possible recovery action and resubmit.
SQL 20270
20270 Redefinition timestamp has been reset for only local partitions of name object. Please execute the command on the remote nodes to update respective remote partitions.
Cause
This warning message indicates that not all partitions associated with the specified object have had their redefinition timestamps updated.
Effect
The operation completes with warnings.
Recovery
After completing this request, the same request must be issued on all systems that contain a partition of the object.
SQL 20271
20271 SPI Error error returned from subsystem while performing an online reload operation.
Cause
An unexpected error was returned while attempting to perform a SPI operation.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20272
20272 Non-audited tables are not supported. Cannot perform DUP.
Cause
The DUP operation does not support nonaudited tables.
Effect
The operation fails.
Recovery
Change the table to be audited using the FIXUP command, and resubmit.
SQL 20273
20273 An internal error occurred.
Cause
An unexpected error was returned while attempting to perform a SPI operation.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20274
20274 Decoding the signature for a ROUTINE object failed.
Cause
An unexpected error occurred while decoding the signature for a ROUTINE object.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20275
20275 Reload operation failed, file system error error returned from ORSERV for file file.
Cause
An unexpected error occurred while performing a FUP RELOAD.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose the error and then resubmit.
SQL 20276
20276 Reload operation failed, already in progress.
Cause
SQL attempted to start a FUP RELOAD operation but an operation was already in progress.
Effect
The operation fails.
Recovery
Wait until the current RELOAD operation completes, and resubmit.
SQL 20283
20283 Row number inconsistency between table tabname and index indname: The table has tabrow rows, the index has indrow rows.
-
Where,
-
tabname is the table name.
-
indname is the index name.
-
tabrow is the number of rows in the table.
-
indrow is the number of rows in the index.
Cause
The number of rows in the table and the index does not match.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20290
20290 The current operation on partition partition for the object object failed because a utility operation on the same partition is already in progress or has failed.
Cause
The specified partition partition is already involved in another utility operation, or a previous utility operation on the specified partition failed.
Effect
The MODIFY utility did not process the request.
Recovery
Wait until the other utility operation completes and retry the MODIFY request. If another utility operation is not running, perform a RECOVER operation on the table or index that owns the partition to clean up the failed operation. Then resubmit.
SQL 20292
20292 The MODIFY utility does not support online partition management on an object that has a decoupled partitioning key.
Cause
You specified the WITH SHARED ACCESS clause in the partition management request of an object that has a decoupled partitioning key. Only offline partition management operations are allowed on such an object.
Effect
The MODIFY utility did not process the request.
Recovery
Retry the operation without the WITH SHARED ACCESS clause.
SQL 20293
20293 The partition cannot be reused because the partition contains data and the specified table is referenced by another table.
Cause
The partition that you specified in the partition management request contains data, and the specified base table is referenced by another base table through a referential integrity constraint. The REUSE operation is not allowed on such a partition.
Effect
The operation fails.
Recovery
None.
SQL 20294
20294 The partition cannot be reused because the partition contains data and the table has an enabled DELETE trigger.
Cause
The partition that you specified in the partition management request contains data, and the specified base table has an enabled DELETE trigger. The REUSE operation is not allowed on such a partition.
Effect
The MODIFY utility operation fails.
Recovery
Disable all triggers on the table and retry the REUSE operation.
SQL 20295
20295 The MODIFY request has completed successfully, but ORSERV failed. Please run FUP RELOAD to reclaim free space.
Cause
The MODIFY utility has completed, but it failed to start ORSERV (the FUP RELOAD operation) successfully. The failures are reported in separate error messages. If the failures were caused by the MODIFY process being killed inadvertently, the warning message is issued by the RECOVER utility during the recovery.
Effect
The MODIFY utility completed the request, but the specified partitions might not have been reloaded. Therefore, their D flag (INCOMPLETE SQLDDL OPERATION), F flag (UNRECLAIMED FREE SPACE), or both flags might still be set, and no subsequent DDL commands or utilities can operate on the partitions.
Recovery
Run FUP RELOAD manually to reclaim free space on the specified partitions if the D or F flag is present for the partitions. Use the FUP INFO or SHOWLABEL utility to see if the D or F flag is set.
SQL 20296
20296 The MODIFY request has completed successfully, but ORSERV might not have completed successfully. Please run FUP RELOAD to reclaim free space.
Cause
The MODIFY utility encountered failures after it started all ORSERVs (the FUP RELOAD operation) successfully. The failures are reported in separate error messages. If the failures were caused by the MODIFY process being killed inadvertently, the warning message is issued by the RECOVER utility during the recovery.
Effect
The MODIFY utility completed the request, but the FUP RELOAD operation might not have finished successfully.
Recovery
Run FUP RELOAD manually to reclaim any free space on the specified partitions if the D flag (INCOMPLETE SQLDDL OPERATION), or F flag (UNRECLAIMED FREE SPACE) is present for the partitions. Use the FUP INFO or SHOWLABEL utility to see if the D or F flag is set.
SQL 20297
20297 The MODIFY request has completed successfully, but was directed not to start ORSERV. Please run FUP RELOAD to reclaim free space.
Cause
The MODIFY utility was directed not to start ORSERV because the NO RECLAIM option was specified, but partitions involved in the operation require reloading.
Effect
The MODIFY utility completed the request successfully but left unreclaimed free space in one or more partitions of the object.
Recovery
Run FUP RELOAD manually to reclaim any free space on any partitions of the object if the D (INCOMPLETE SQLDDL OPERATION) or F (UNRECLAIMED FREE SPACE) flag is present for the partition. Use the FUP INFO or SHOWLABEL utility to see if the D or F flag is set.
SQL 20298
20298 The program file progname is not licensed.
Cause
You specified a program file that is not licensed.
Effect
The operation fails.
Recovery
License the specified program and resubmit.
SQL 20300
20300 The object type object is not currently supported.
Cause
You attempted to perform a backup or a restore on object type, which is not supported.
Effect
The operation fails.
Recovery
None.
SQL 20302
20302 The IO buffer is not large enough to hold the object's metadata.
Cause
This is an internal error.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20303
20303 CANCEL cannot be used as an option for this RECOVER operation.
Cause
You attempted to recover a failed PURGEDATA request by specifying CANCEL. However, PURGEDATA has progressed too far, and only RESUME can be specified.
Effect
SQL is unable to recover the PURGEDATA command.
Recovery
Use RESUME to recover the operation.
SQL 20304
20304 RESUME cannot be used as an option for this RECOVER operation. NO actual PURGEDATA work has been done. Retry your operation with CANCEL.
Cause
You attempted to recover a failed PURGEDATA request by specifying RESUME. However, PURGEDATA has progressed too far, and only CANCEL can be specified.
Effect
SQL is unable to recover the PURGEDATA command.
Recovery
Use CANCEL to retry the operation.
SQL 20306
20306 There is no data associated with the object name object.
Cause
Internal error.
Effect
The backup or restore could not be performed.
Recovery
None. Contact your service provider.
SQL 20307
20307 The catalog object already exists.
Cause
You are trying to restore a catalog object that already exists.
Effect
The operation fails.
Recovery
Check the location of the catalog.
SQL 20308
20308 The schema object already exists.
Cause
You are trying to restore a schema object that already exists.
Effect
The backup or restore operation fails.
Recovery
Check the location of the schema.
SQL 20309
20309 An internal error occurred - invalid count, unable to obtain the size of the metadata.
Cause
This is an internal error.
Effect
The backup or restore operation fails.
Recovery
None. Contact your service provider.
SQL 20310
20310 The size of the metadata is not valid.
Cause
This is an internal error.
Effect
The backup or restore operation fails.
Recovery
None. Contact your service provider.
SQL 20311
20311 The column data type is not supported.
Cause
You are trying to create a column of a data type that is not supported.
Effect
The backup or restore operation fails.
Recovery
None.
SQL 20312
20312 The index object already exists.
Cause
You are trying to restore an index object that already exists.
Effect
The operation fails.
Recovery
Check the location of the index.
SQL 20318
20318 The partition object was not found.
Cause
This is an internal error.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20319
20319 The table object already exists.
Cause
You are trying to restore a table object that already exists.
Effect
The operation fails.
Recovery
Check the location of the table and resubmit.
SQL 20320
20320 The view object already exists.
Cause
You are trying to restore a view object that already exists.
Effect
The operation fails.
Recovery
Check the location of the view.
SQL 20321
20321 An internal error was encountered: invalid catalog or schema object.
Cause
SQL could not find the catalog or schema referenced by a view.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20324
20324 The table object does not exist.
Cause
You attempted to perform a PARTONLY restore to a table that does not exist.
Effect
The operation fails.
Recovery
Check the location of the table.
SQL 20325
20325 The job failed due to an internal error.
Cause
This is an internal error.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20330
20330 The specified parameter is not valid.
Cause
An internal function has specified the wrong parameters.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20331
20331 The specified parent object is not valid.
Cause
You tried to perform an online restore, but the audit object has an invalid SQL node object.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20332
20332 The audit metadata is not valid.
Cause
You tried to perform an online restore, but the audit trail data (the metadata of the audit object) on the tape is invalid.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20333
20333 The audit file name is not valid.
Cause
The DP2 file name of an audit object, passed by the transaction management process (TMP), is invalid.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20334
20334 The restore options do not match the backup options.
Cause
The restore options you specified do not match the backup options.
Effect
The operation fails.
Recovery
Correct the restore options and resubmit.
SQL 20335
20335 Selected run time option is not valid.
Cause
The restore session mode is unknown.
Effect
The backup or restore could not be performed.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20336
20336 TMF function call failed, error code = error number.
Cause
Internal error during online backup or restore.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20337
20337 Feature not supported by the online option.
Cause
The online backup or restore feature is not supported for the specified object.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20338
20338 Master audit trail does not exist.
Cause
In a snapshot restore, the master audit trail data was missing.
Effect
The operation fails.
Recovery
None. This an internal error. Contact your service provider.
SQL 20339
20339 Indexes index-list on table table did not populate successfully.
Cause
One of more indexes did not populate correctly, probably because of uniqueness violations when loading unique indexes.
Effect
The operation fails.
Recovery
For unique indexes, remove conflicting records from the base table and retry the populate operation. For non-unique indexes, do not attempt recovery.
SQL 20340
20340 Indexes index-list on table table were successfully populated.
Cause
One or more indexes successfully populated.
Effect
The operation partially succeeded.
Recovery
This is an informational message that indicates indexes that were successfully populated. This message appears with error 20339, which lists the indexes that failed to populate. If all the indexes are populated successfully, this error does not appear. The situations that require correction action are reported by error 20339.
SQL 20350
20350 A syntax error was found near "string", near character position int.
-
Where,
-
string is the value where the syntax error was detected;
-
int is the byte location in the string where the error occurred.
Cause
You specified the wrong syntax.
Effect
The operation fails.
Recovery
Enter MXTOOL HELP to get correct syntax and resubmit.
SQL 20351
20351 An internal error occurred.
Cause
An unexpected error occurred while performing an MXTOOL operation.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20352
20352 Syntax error. No arguments were provided. Try ‘mxtool help'.
Cause
You specified MXTOOL without any arguments.
Effect
The operation fails.
Recovery
Enter MXTOOL HELP to get correct syntax, and resubmit.
SQL 20353
20353 Syntax error. An invalid operation operation was requested. Try ‘mxtool help'.
Cause
You specified MXTOOL but did not specify FIXUP, VERIFY, GOAWAY, or INFO as a valid operation.
Effect
The operation fails.
Recovery
Enter MXTOOL HELP to get correct syntax, and resubmit.
SQL 20354
20354 Only super ID and the schema owner can use the MXTOOL operation operation.
Cause
The GOAWAY or FIXUP operation failed because you do not have super ID or schema owner privilege.
Effect
The operation fails.
Recovery
Log on as the super ID and resubmit.
SQL 20355
20355 File name was not found.
Cause
The Guardian file that you specified does not exist, possibly because of a spelling error.
Effect
The operation fails.
Recovery
Specify the Guardian file correctly and resubmit.
SQL 20356
20356 File name could not be accessed. Error error was returned.
-
Where,
-
name is the name of the Guardian file requested to be removed;
-
error is the error returned by the file system.
Cause
GOAWAY could not drop the specified Guardian file.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20357
20357 File name is not an SQL/MX object.
Cause
GOAWAY could not drop the specified Guardian file.
Effect
The operation fails.
Recovery
None. You can use GOAWAY only with SQL/MX objects.
SQL 20358
20358 Catalog catalog does not exist.
Cause
You specified a catalog name that is not defined or is not visible on the system.
Effect
The operation fails.
Recovery
Enter the correct catalog name and resubmit.
SQL 20359
20359 Schema schema does not exist.
Cause
You specified an invalid schema name.
Effect
The operation fails.
Recovery
Enter the correct schema name and resubmit.
SQL 20360
20360 Object object does not exist or the Object is not valid for the current operation.
Cause
You specified an incorrect table, index, or view name.
Effect
The operation fails.
Recovery
Enter the correct object name and resubmit.
SQL 20361
20361 FixRcb failed for object object-name.
Cause
The mxtool fixrcb command tried to fix the RCB of the object whose partition is on a remote node running an incompatible version of SQL/MX.
Effect
The operation fails.
Recovery
Upgrade the remote node to a compatible SQL/MX version and retry the mxtool fixrcb command.
SQL 20362
20362 Error error was returned while validating the file set list specified by "Guardian file".
-
Where,
-
error is the error returned by the Guardian file system while searching for files
-
Guardian file is the template of Guardian files requested to be removed.
Cause
MXTOOL generates a list of files to check as specified by a Guardian file template. An error was returned during this generation process.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20363
20363 Warning - file system error error returned at the end of search.
Cause
MXTOOL generates a list of files to check as specified by a Guardian file template. An error was returned during the processing of this list.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20364
20364 An internal error occurred while getting the Guardian file name.
Cause
An unexpected error was returned while reading the file label for a Guardian file.
Effect
The operation fails.
Recovery
None. This is an internal error. Contact your service provider.
SQL 20370
20370 Invalid flag provided for the operation. Try ‘mxtool help' for the operation.
Cause
The syntax you specified was invalid.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 20371
20371 The specified object object-name is not an SQL/MX object.
Cause
The object specified by the caller is not an SQL/MX object.
Effect
The operation fails.
Recovery
Specify the correct object name and resubmit.
SQL 20372
20372 The resource fork is not accessible.
Cause
The resource fork is either broken or does not exist.
Effect
None.
Recovery
None. This is an informational message.
SQL 20373
20373 The specified system does not exist in the network.
Cause
The system name specified in the file template for Guardian files does not exist in the current network, possibly because of a misspelling.
Effect
The operation fails.
Recovery
Correct the spelling and resubmit.
SQL 20374
20374 Option -s cannot be used in combination with any filtering option.
Cause
A syntax error occurred while processing the GOAWAY operation. An invalid list of options was specified.
Effect
The operation fails.
Recovery
Run "mytool help goaway" to get the list of correct options and retry request.
SQL 20376
20376 The environment variable SQLMX_TERMINAL_CHARSET = charsetname is not supported.
Cause
You specified a non-ISO88591 character set name.
Effect
The operation fails.
Recovery
Specify an ISO88591 character set name.
SQL 20377
20377 An error occurred while doing a conversion between TERMINAL_CHARSET & ISO_MAPPING CQD.
Cause
You specified an invalid character set.
Effect
The operation fails.
Recovery
Specify an ISO88591 character set.
SQL 20381
20381 Wrong target format specification number for fixmxcsmd
Cause
You have entered an invalid target format specification.
Effect
The mxtool fixmxcsmd operation fails.
Recovery
Execute the command with a valid target format specification. For SQL/MX Release 3.2, the valid numbers are 2 and 3.
SQL 20382
20382 Not a valid CPU list specification: text
Cause
The CPU list has an invalid format in metadata. The target format already exists in the MXCS metadata.
Effect
This is a warning condition where the
mxtool fixmxcsmd skips the invalid CPU list and processes remaining valid CPU list specifications.
Recovery
If MXCS metadata already has the target format, no action is required. Otherwise, contact your service provider.
SQL 20383
20383 Ambiguous CPU list specification: text
Cause
The CPU list found in the MXCS metadata has a format that can be either source version or the target version. The target format might already exist in the MXCS metadata.
Effect
This is a warning condition where the
mxtool fixmxcsmdprocesses the ambiguous CPU list and the remaining valid cpu list specifications.
Recovery
If the resulting CPU list is not correct, use mxci to alter the CPU list to a desired value.
SQL 20400
20400 The option option may not be specified more than once.
Cause
You specified option more than once.
Effect
The operation fails, the target table or index is not modified.
Recovery
Specify the option only once.
SQL 20401
20401 The value for the option option must be a number between low and high.
- option
-
is an actual option, one of: RATE, PRIORITY, SLACK, DSLACK, ISLACK, or CONCURRENCY.
-
low and high are the boundaries for the range of valid values for option.
Cause
You specified an invalid option value.
Effect
The operation fails, the target table or index is not modified.
Recovery
For the RATE option: Specify a percentage between 1 and 100.For the SLACK, DSLACK, or ISLACK options: Specify a percentage between 1 and 99.For the PRIORITY option: Specify an NSK priority between 1 and 199.For the CONCURRENCY option: Specify a number between 1 and the actual number of partitions for the affected table or index.
SQL 20402
20402 No REORG operation exists on object-type object-name.
- object-type
-
is the type of the affected SQL/MX table or index.
- object-name
-
is the ansi-name of the affected SQL/MX table or index.
Cause
You MODIFY REORG with the STATUS, SUSPEND, ACTIVATE, or CANCEL action on an object when a REORG on the specified object is not in progress.
Effect
The operation fails.
Recovery
Specify a correct TABLE or INDEX name on which a REORG command is issued but it has not completed yet.
SQL 20403
20403 The REORG operation on object-type object-name is already running.
- object-type
-
is the type of the affected SQL/MX table or index.
- object-name
-
is the ansi-name of the affected SQL/MX table or index.
Cause
You issued MODIFY REORG on an object on which a REORG command is already running.
Effect
The operation fails.
Recovery
Wait until the already started REORG command completes.
SQL 20404
20404 The REORG operation on object-type object-name has already been suspended.
- object-type
-
is the type of the affected SQL/MX table or index.
- object-name
-
is the ansi-name of the affected SQL/MX table or index.
Cause
You issued MODIFY REORG with the SUSPEND action on an already suspended REORG operation.
Effect
The operation fails.
Recovery
As operation is already suspended, no recovery is required.
SQL 20405
20405 No suspended REORG operation exists for object-type object-name.
- object-type
-
is the type of the affected SQL/MX table or index.
- object-name
-
is the ansi-name of the affected SQL/MX table or index.
Cause
You issued MODIFY REORG with the ACTIVATE action on an object on which no suspended REORG operation exists.
Effect
The operation fails.
Recovery
As operation is already active, no recovery is required.
SQL 20406
20406 RELOAD of the partition partition-location failed with error zerror. RELOAD for the partition is skipped.
- partition-location
-
is the physical location of the partition.
- zerror
-
is the file-system error number returned by ORSERV when RELOAD of the partition was initiated.
Cause
RELOAD could not be initiated on the partition, zerror indicates the reason.
Effect
RELOAD of that partition fails, other partitions are reloaded.
Recovery
Address the reported error then use RECOVER with the RESUME option to complete the REORG.
SQL 20407
20407 The original MODIFY REORG command is not active. For SUSPEND and CANCEL commands, the original MODIFY REORG command must be active.
Cause
You issued either SUSPEND or CANCEL command when the original REORG is no longer active.
Effect
The operation fails.
Recovery
Issue SUSPEND or CANCEL command only when the original REORG command is still active.
SQL 20408
20408 The value of option CONCURRENCY cannot be less than 1.
Cause
You specified the value of option CONCURRENCY less than 1.
Effect
The operation fails.
Recovery
Specify a positive number for option CONCURRENCY.
SQL 20410
20410 object-type model-object-name cannot be used to REPARTITION target-object-name.
- object-type
-
is the type of the affected SQL/MX table or index.
- model-object-name
-
is the fully qualified ANSI name of the model object.
- target-object-name
-
is the fully qualified ANSI name of the target object.
Cause
The model object is not compatible with the target object. An accompanying repartitioning error message will state the reason.
Effect
The target table or index is not modified.
Recovery
Specify a model object that is compatible with the target object, then retry the MODIFY REPARTITION command.
SQL 20411
20411 Table table-name is not empty.
Cause
The model table for MODIFY TABLE ... REPARTITION is not empty.
Effect
The target table or index is not modified.
Recovery
Specify an empty model table in the MODIFY TABLE ... REPARTITION command text.
SQL 20412
20412 The LIKE clause must specify object-type in the same catalog and schema as target-object-name.
- object-type
-
is the type of the affected SQL/MX table or index.
- target-object-name
-
is the fully qualified ANSI name of the target object.
Cause
The model object for MODIFY REPARTITION is in a different schema than the target object.
Effect
The target table or index is not modified.
Recovery
Specify a model object in the same catalog and schema as the target object.
SQL 20413
20413 The attribute for object-type model-object-name must be the same as the attribute for target-object-name.
- attribute
-
is one of:
-
PARTITION BY columns
-
BLOCKSIZE
-
PRIMARY KEY (not relevant for an index)
-
STORE BY key (not relevant for an index)
-
number of columns
-
AUDITCOMPRESS
-
- object-type
-
is the type of the affected SQL/MX table or index.
- model-object-name
-
is the fully qualified ANSI name of the model object.
- target-object-name
-
is the fully qualified ANSI name of the target object.
Cause
The model object for MODIFY REPARTITION differs from the target object on the specified attribute.
Effect
The target table or index is not modified.
Recovery
Specify a model object with attribute identical to that of the target object.
SQL 20414
20414 object-type model-object-name must be partitioning-scheme partitioned.
- object-type
-
is the type of the affected SQL/MX table or index.
- model-object-name
-
is the fully qualified ANSI name of the model object.
- partitioning-scheme
-
is the partitioning scheme of the target object: HASH or RANGE.
Cause
The model object for MODIFY REPARTITION has a different partitioning scheme than the target object.
Effect
The target table or index is not modified.
Recovery
Specify a model object with the same partitioning scheme as the target object.
SQL 20415
20415 Table model-table-name cannot have a constraint-type constraint.
- model-table-name
-
is the fully qualified ANSI name of the model table.
- constraint-type
-
is the type of an incompatible constraint: UNIQUE or FOREIGN KEY.
Cause
The model table for MODIFY REPARTITION has a UNIQUE or FOREIGN KEY constraint.
Effect
The target table or index is not modified.
Recovery
Specify a model table without UNIQUE and FOREIGN KEY constraints.
SQL 20416
20416 Table model-table-name is referenced by ref-obj-type ref-obj-name.
-
Where,
-
model-table-name is the fully qualified ANSI name of the model table.
-
ref-obj-type is the object type: view, trigger, or constraint, of an object that references the model table.
-
ref-obj-name is the fully qualified ANSI name of a view, trigger, or constraint that references the model table.
Cause
The model table for MODIFY REPARTITION is referenced by a view, a trigger, or a foreign key constraint. This includes the case where the model table is the subject table of a trigger.
Effect
The target table or index is not modified.
Recovery
Specify a model object with no offending referencing object.
SQL 20417
20417 Column name1 in model-table-name is incompatible with column name2 in target-table-name: reason is different.
-
Where,
-
name 1 is the name of a column in the model table.
-
name 2 is the name of the corresponding column, by column number, in the target table.
-
model-table-name is the fully qualified ANSI name of the model table.
-
target-table-name is the fully qualified ANSI name of the target table.
-
reason is a specification why the columns are incompatible. One of:
-
column names
-
data types
-
default values/headings
-
identity column specifications
-
column class attributes (system-defined/user-defined/user-defined added)
-
Cause
The model table for MODIFY REPARTITION has a column that differs from the corresponding column in the target table.
Effect
The target table or index is not modified.
Recovery
Specify a model table where each column matches its counterpart in the target table on all important aspects.
SQL 20418
20418 Index index-name must be offline.
Cause
The model index for a MODIFY INDEX ... REPARTITION is not offline.
Effect
The target table or index is not modified.
Recovery
Specify a model index that was created using the NO POPULATE clause.
SQL 20419
20419 Index index-name must be an index on table-name.
-
Where,
-
index-name is the fully qualified ANSI name of the model index.
-
table-name is the fully qualified ANSI name of the target index base table.
Cause
The model index for a MODIFY INDEX ... REPARTITION is on a different table than the target index.
Effect
The target table or index is not modified.
Recovery
Specify a model index that is on the same table as the target index.
SQL 20420
20420 Index index-name reason be UNIQUE.
-
Where,
-
index-name is the fully qualified ANSI name of the model index.
-
reason is one of “cannot” or “must”.
Cause
The model index for a MODIFY INDEX ... REPARTITION is unique and the target index is non-unique or conversely.
Effect
The target table or index is not modified.
Recovery
Specify a model index with the same uniqueness as the target index.
SQL 20421
20421 Index index-name1 must be on the same columns as index-name2, in the same sequence, and with the same ascending/descending specification.
-
Where,
-
index-name1 is the fully qualified ANSI name of the model index.
-
index-name2 is the fully qualified ANSI name of the target index.
Cause
The model index for a MODIFY INDEX ... REPARTITION has a different index column specification than the target index.
Effect
The target table or index is not modified.
Recovery
Specify a model index that is on the same set of columns as the target index, in the same sequence, and with the same ascending/descending specification.
SQL 20422
20422 Table table-name must be owned by user-name.
-
Where,
-
table-name is the fully qualified ANSI name of the model table.
-
user-name is the Guardian user name of the owner of the target table.
Cause
The model table is not owned by the same user as the target table.
Effect
The target table or index is not modified.
Recovery
Specify a model table that is owned by the same user as the target table.
SQL 20423
20423 The model object and the target object cannot be the same.
Cause
The model object is the same as the target object.
Effect
The target table or index is not modified.
Recovery
Specify a model object that is not the target object.
SQL 20450
20450 You asked to drop only the data fork data fork name but a resource fork exists (resource fork name).
-
Where,
-
data fork name is the Guardian file of the data fork;
-
resource fork name is the Guardian file of the resource fork.
Cause
You specified invalid options for the GOAWAY command.
Effect
The operation fails.
Recovery
Do not use the DATA/RESOURCE FORK option, and resubmit.
SQL 20451
20451 You asked to drop only the resource fork resource fork name but a data fork exists (data fork name).
-
Where,
-
resource fork name is the Guardian file of the resource fork;
-
data fork name is the Guardian file of the data fork.
Cause
You specified invalid options for the GOAWAY command.
Effect
The operation fails.
Recovery
Do not use the DATA/RESOURCE FORK option, and resubmit.
SQL 20452
20452 GOAWAY cannot be used to remove a Guardian file on a remote system (system).
Cause
You tried to remove a Guardian object on a remote system.
Effect
The operation fails.
Recovery
Run the GOAWAY operation on a local machine.
SQL 20453
20453 Operation failed on name due to timeout.
Cause
The GOAWAY operation failed because the label has a lock on it, and the operation timed out after 90 seconds.
Effect
The operation fails.
Recovery
Remove the lock on the label and retry the operation.
SQL 20454
20454 Only Super.Super user can perform the GOAWAY operation.
Cause
User error. Only the SUPER ID user can run the GOAWAY utility.
Effect
The operation fails.
Recovery
Have the SUPER ID user run the GOAWAY utility.
SQL 20456
20456 The following file will be removed name. Are you sure? (Enter YES or NO):
-
Where name is a comma-separated list of Guardian objects to remove. It contains the resource fork name, the data fork name, or both.
Cause
GOAWAY is ready to remove the requested files.
Effect
GOAWAY is waiting for a response before continuing.
Recovery
None.
SQL 20457
20457 GOAWAY aborted at the request of the user.
Cause
The GOAWAY operation was terminated.
Effect
None.
Recovery
None. This is an informational message.
SQL 20458
20458 GOAWAY of file: file failed due to file system error error.
-
Where,
-
file is the name of the Guardian file;
-
error is the file system error returned while trying to remove a Guardian file.
Cause
The GOAWAY operation failed because of an unexpected error.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 20459
20459 You specified -both for the GOAWAY request. However, only file exists. You must use -df or -rf option to GOAWAY the label.
Cause
The GOAWAY operation failed because only the data fork or resource fork exists, and the -both option was specified.
Effect
The operation fails.
Recovery
If file ends in 00, rerun the request with the -df option. If file ends in 01, rerun the request with the -rf option.
SQL 20460
20460 You specified -both for GOAWAY request of resource fork name You must specify data fork name to GOAWAY the label.
-
Where,
-
resource fork name is the name of the resource fork;
-
data fork name is the name of the data fork.
Cause
The GOAWAY operation failed because you specified
resource fork name with the
-both option
Effect
The operation fails.
Recovery
Retry with data fork name label name.
SQL 20461
20461 Option -df does not match label resource fork name. Use -rf to GOAWAY the label.
Cause
The GOAWAY operation failed because you specified
resource fork name with the
-df option.
Effect
The operation fails.
Recovery
Retry with the
-rf option.
SQL 20462
20462 Option -rf does not match label data fork name. Use -df to GOAWAY the label.
Cause
The GOAWAY operation failed because you specified
data fork name with the
-rf option.
Effect
The operation fails.
Recovery
Retry with the
-df option.
SQL 20520
20520 Object object cannot participate in refresh; a utility operation associated with a DDL lock on it is currently running.
Cause
Object object has a DDL lock on it.
Effect
The refresh operation fails.
Recovery
After the concurrent operation that holds the DDL lock finishes, rerun refresh again. If no concurrent operations are running, the DDL lock must be removed. Contact your service provider to remove the lock.
SQL 20521
20521 Object object cannot participate in refresh; a process associated with a DDL lock on it is currently running.
Cause
Object object has a DDL lock on it by another concurrent refresh utility execution.
Effect
This refresh operation fails.
Recovery
After the concurrent operation that holds the DDL lock finishes, run refresh again. If no concurrent operations are running, the DDL lock must be removed. Contact your service provider to remove the lock.
SQL 20525
20525 Task task-name cannot be executed remotely.
Cause
The refresh operation cannot be executed remotely because the buffer is full.
Effect
The operation fails.
Recovery
Do not attempt recovery. Contact your service provider.
SQL 20531
20531 An internal error occurred while extracting data type information from an internal data buffer.
Cause
An internal error occurred.
Effect
The operation fails.
Recovery
Do not attempt recovery. Contact your service provider.
SQL 20532
20532 An internal error occurred while comparing data from internal data buffers.
Cause
The refresh operation cannot complete because a failure occurred on a required internal task, which is a comparison of values attempted for SQL item data types that are not identical.
Effect
The operation fails.
Recovery
Do not attempt recovery. Contact your service provider.
SQL 20562
20562 An internal error occurred on an attempt to begin a new transaction. There are too many outstanding transactions.
Cause
Refresh reached a transaction management facility (TMF) limit on the number of transactions that the facility can start.
Effect
The refresh operation fails.
Recovery
Do not attempt recovery. Contact your service provider.
SQL 20588
20588 Invalid Character error converting string from character set charset1 to character set charset2.
Cause
You specified an invalid character set.
Effect
The operation fails.
Recovery
Specify an ISO88591 character set.
SQL 20589
20589 Buffer Overrun error converting string from character set charset1 to character set charset2.
Cause
You specified an invalid character set.
Effect
The operation fails.
Recovery
Specify an ISO88591 character set.
SQL 20680
20680 Object has no matching locations.
Cause
Specified Guardian File Name pattern or set of patterns does not match any of the table or index partitions.
Effect
Rename operation fails and partitions are not renamed.
Recovery
Specify the Guardian File Name pattern that matches at least one of the table or index partitions and retry rename operation using MODIFY command.
SQL 20681
20681 Target location location already exists.
Cause
An existing target location is specified.
Effect
Rename operation fails and partitions are not renamed.
Recovery
Specify a non-existing target location, and retry rename operation using MODIFY command.
SQL 20682
20682 Duplicate target location location was specified.
Cause
Duplicate target locations are specified.
Effect
Rename operation fails and partitions are not renamed.
Recovery
Specify unique set of target locations, and retry rename operation using MODIFY command.
SQL 20683
20683 The target map target-map has mapped source location source-location to target-location which already exists.
-
Where,
-
target-map is the specified target map;
-
source-location is an existing location that matches a file name pattern;
-
target-location is the generated location for the specified source-location.
Cause
Specified target map generates an existing target location.
Effect
Rename operation fails and partitions are not renamed.
Recovery
Modify target map to generate non-existing target locations, and retry rename operation using MODIFY command.
SQL 20684
20684 Duplicate target location target-location was generated by map from source-location.
-
Where,
-
target-location is the generated location for the specified source-location;
-
map is the specified target map;
-
source-location is an existing location that matches a file name pattern.
Cause
The specified target map generates a target location for more than one existing location.
Effect
Rename operation fails and partitions are not renamed.
Recovery
Modify the target map to produce a unique set of target locations, and retry rename operation using MODIFY command.
SQL 20685
20685 Existing location location matches multiple patterns.
Cause
Multiple Guardian File Name patterns are specified and an existing location matches more than one of these patterns.
Effect
Rename operation fails and partitions are not renamed.
Recovery
Modify the patterns and ensure that each pattern matches a unique set of source locations, and retry rename operation using MODIFY command.
SQL 20686
20686 Duplicate source location location was specified.
Cause
Duplicate source location is specified.
Effect
Rename operation fails and partitions are not renamed.
Recovery
Specify unique source location, and retry rename operation using MODIFY command.
SQL 20687
20687 Sequence generator seq-name does not exist.
Cause
Where The utility operation cannot find the specified sequence generator.
Effect
The statement fails.
Recovery
Check the name of the specified sequence generator and resubmit.
SQL 20688
20688 This partition management operation is not supported for sequence generator seq-name.
Cause
You attempted a partition management operation other than moving an entire partition to a new location.
Effect
The statement fails.
Recovery
None.
SQL 20689
20689 The WHERE clause cannot be used with seq-name because it is a sequence generator.
Cause
You specified the WHERE clause in the request to move the partition of a sequence generator to a new location.
Effect
The statement fails.
Recovery
None.
SQL 20701
20701 Audit fix process process name was not able to allocate an extended memory segment. SEGMENT_ALLOCATE_ returned error error number.
Cause
During an online partition management operation, memory allocation errors prevented the MXAUDSRV process from initializing. The error number given is the return code MXAUDSRV received from a SEGMENT_ALLOCATE_ request.
Effect
The MODIFY operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual topic SEGMENT_ALLOCATE_ for possible recovery actions for error number.
SQL 20702
20702 A file system error occurred during the audit fixup phase of the operation, on file Guardian file name.
Cause
During the online partition management operation, the MXAUDSRV process encountered a file system error on the partition named by Guardian file name during redo processing.
Effect
The MODIFY operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual for possible recovery action.
SQL 20703
20703 A heap allocation error occurred in process process name during the audit fixup phase of the operation.
Cause
During an online partition management operation, the MXAUDSRV process encountered a heap allocation error.
Effect
The MODIFY operation fails.
Recovery
None. Contact your service provider.
SQL 20704
20704 A hardware trap occurred in audit fixup process process name.
Cause
During an online partition management operation, the MXAUDSRV process encountered a hardware trap. Such traps might be caused by programming errors in the MXAUDSRV process itself.
Effect
The MODIFY operation fails.
Recovery
None. Contact your service provider.
SQL 20705
20705 An audit fixup request was made out of sequence.
Cause
During an online partition management operation, the MXAUDSRV process received an unexpected request from the MODIFY code.
Effect
The MODIFY operation fails.
Recovery
None. Contact your service provider.
SQL 20706
20706 An audit fixup process received a request with an invalid type for an audit fixup operation.
Cause
During an online partition management operation, the MXAUDSRV process received an invalid request from the MODIFY code. The probable cause was incorrect versions of MXCMP or MXAUDSRV software.
Effect
The MODIFY utility did not process the request.
Recovery
None. Contact your service provider.
SQL 20707
20707 A parameter was missing or not valid in an audit fixup request (process process name).
Cause
During an online partition management operation, the MXAUDSRV process received an invalid request from the MODIFY code. Such an error might be caused by the use of incorrect versions of MXCMP or MXAUDSRV software.
Effect
The MODIFY operation fails.
Recovery
None. Contact your service provider.
SQL 20708
20708 An error occurred in audit fixup process process name while processing a TMF audit record during the audit fixup phase of the operation.
Cause
During an online partition management operation, the MXAUDSRV process encountered an error while processing an HPE NonStop Transaction Management Facility (TMF) audit record.
Effect
The MODIFY operation fails.
Recovery
None. Contact your service provider.
SQL 20709
20709 A TMF audit read error occurred during the audit fixup phase of the operation, in audit fixup process process name.
Cause
During an online partition management operation, the MXAUDSRV process encountered an error while reading a TMF audit record.
Effect
The MODIFY operation fails.
Recovery
Verify that TMF is up and running normally. If not, correct this problem and resubmit. Otherwise, contact your service provider.
SQL 20710
20710 An error occurred while attempting to perform a REDO of a TMF audit record during the audit fixup phase of the operation, in audit fixup process process name.
Cause
During an online partition management operation, the MXAUDSRV process encountered an error while applying TMF audit.
Effect
The MODIFY operation fails.
Recovery
Verify that TMF is up and running normally. If not, correct this problem and resubmit. Otherwise, contact your service provider.
SQL 20711
20711 An error occurred while reporting an event to the EMS collector during the audit fixup phase of the operation, in process process name.
Cause
During an online partition management operation, the MXAUDSRV process encountered an error while attempting to report an EMS event to $0.
Effect
The MODIFY operation fails.
Recovery
Verify that EMS is up and running normally. If not, correct this problem and retry the operation. Otherwise, contact your service provider.
SQL 20712
20712 An internal error occurred during the audit fixup phase of the operation. The maximum size for a request message to the audit fixup server was exceeded.
Cause
During an online partition management operation, the MXAUDSRV process received a request of an invalid size from the MODIFY code.
Effect
The MODIFY operation fails.
Recovery
None. Contact your service provider.
SQL 20716
20716 The audit fixup phase of the operation was unable to retrieve information from the TMF subsystem.
Cause
During an online partition management operation, the MXAUDSRV process was not able to retrieve information from TMF.
Effect
The MODIFY operation fails.
Recovery
Verify that TMF is up and running normally. If not, correct this problem and retry the operation. Otherwise, contact your service provider.
SQL 20717
20717 Audit fixup process ( process name) could not begin or commit a TMF transaction.
Cause
During an online partition management operation, the MXAUDSRV process encountered an error when attempting to begin or commit a TMF transaction. The probable cause is that the TMF subsystem is down or has transactions disabled.
Effect
The MODIFY utility did not process the request.
Recovery
Correct the TMF problem and resubmit.
SQL 20718
20718 An audit trail version incompatibility on audit volume volume name was encountered in audit fixup process process name.
-
Where,
-
volume name is the volume where the audit trails resides;
-
process name is the name of the MXAUDSRV process.
Cause
During an online partition management operation, the MXAUDSRV process encountered an audit trail versioning error while processing audit records.
Effect
The MODIFY operation fails.
Recovery
Correct the TMF problem and resubmit.
SQL 20719
20719 A request with an incompatible version was made to audit fixup process process name.
Cause
During an online partition management operation, the MXAUDSRV process received a request from the MODIFY code with an incompatible version field. The probable cause is the use of incorrect product versions of MXCMP and MXAUDSRV.
Effect
The MODIFY operation fails.
Recovery
Verify that correct versions of MXCMP and MXAUDSRV are installed. If so, contact your service provider.
SQL 20720
20720 The audit fixup process process name could not run on system system name due to a software version incompatibility.
-
Where,
-
process name is the MXAUDSRV process name;
-
system name is the name of the system where the version incompatibility occurs.
Cause
The wrong product version of MXAUDSRV is installed on the named system.
Effect
The MODIFY operation fails.
Recovery
Install the current product version of MXAUDSRV.
SQL 20721
20721 An internal error (unknown exception class) occurred in audit fixup process process name.
Cause
During an online partition management operation, the MXAUDSRV process encountered an internal error.
Effect
The MODIFY operation fails.
Recovery
None. Contact your service provider.
SQL 20723
20723 An audit fixup process found a label change audit record during fixup work. These audit records are most likely caused by another process performing a concurrent DDL operation, which is not allowed.
Cause
During an online partition management operation, the MXAUDSRV process encountered a file label change audit record.
Effect
The MODIFY operation fails.
Recovery
Resubmit the request.
SQL 20724
20724 Audit fixup process process name found a violation of the uniqueness constraint while populating a unique index.
Cause
A record with a duplicate key from the audit trail was found while populating the index.
Effect
Populate is not done.
Recovery
Recover the index file, remove conflicting records from base table and retry.
SQL 20725
20725 Audit fixup process process name detected an internal error.
Cause
During an online partition management operation, the MXAUDSRV process encountered an internal error.
Effect
The MODIFY operation fails.
Recovery
None. Contact your service provider.
SQL 20726
20726 An audit fixup process's program file process name is not licensed.
Cause
The MXAUDSRV program file is not licensed.
Effect
The MODIFY operation fails.
Recovery
License the MXAUDSRV program file and retry the operation.
SQL 20727
20727 An unexpected error code error code was returned by the audit fixup process process name.
Cause
During an online partition management operation, the MXAUDSRV process. reported an unknown error code.
Effect
The MODIFY operation fails.
Recovery
None. Contact your service provider.
SQL 20728
20728 An SQL/MX error error code occurred in audit fixup process process name.
Cause
During an online partition management operation, the MXAUDSRV process encountered an error when attempting an SQL/MX statement.
Effect
The MODIFY utility did not process the request.
Recovery
Contact your service provider.
SQL 20729
20729 File system error error code was returned from an MXARLIB call in audit fixup process process name.
Cause
During an online partition management operation, the MXAUDSRV process encountered an error when attempting to extract data fields from a TMF audit record.
Effect
The MODIFY operation fails.
Recovery
None. Contact your service provider.
SQL 20730
20730 An unexpected key transform error error code occurred in audit fixup process process name.
Cause
During an online partition management operation, the MXAUDSRV process encountered an error when attempting to examine data fields extracted from a TMF audit record.
Effect
The MODIFY operation fails.
Recovery
None. Contact your service provider.
SQL 20731
20731 The time given in the BEFORE clause has already passed.
Cause
The MODIFY command includes a COMMIT BEFORE timestamp clause, and the MODIFY processing did not reach commit phase before the specified timestamp. The timestamp is checked at two points during processing: at the time the MODIFY command is first parsed and again when MODIFY is ready to begin commit phase.
Effect
The MODIFY operation fails.
Recovery
If the timestamp check failed at the beginning of the commit phase, perform a RECOVER command to undo partial processing. Then, retry the MODIFY operation with a timestamp sufficiently in the future.
SQL 20732
20732 The time given in the AFTER clause is more than 30 days in the future.
Cause
The MODIFY command includes a COMMIT AFTER timestamp clause, and the timestamp specifies a time that is more than 30 days in the future.
Effect
The MODIFY operation fails.
Recovery
Correct the COMMIT AFTER clause to use a time within 30 days of the present, and resubmit.
SQL 20733
20733 The times given in ONCOMMITERROR clauses are not in ascending order.
Cause
The MODIFY command includes multiple COMMIT BEFORE and/or COMMIT AFTER clauses, and a time given in one such clause is earlier than one given in some preceding clause.
Effect
The MODIFY utility did not process the request.
Recovery
Correct the COMMIT clauses so that they are in ascending order in time, and retry the operation.
SQL 20734
20734 Error error number was returned by CONVERTTIMESTAMP while trying to obtain local civil time.
Cause
When processing COMMIT BEFORE or COMMIT AFTER clauses, the MODIFY command encountered an error number from the CONVERTTIMESTAMP Guardian procedure when converting the current time to local civil time.
Effect
The MODIFY operation fails.
Recovery
See the Guardian Procedure Calls Reference Manual topic CONVERTTIMESTAMP Procedure for the meaning of error number and possible recovery actions.
SQL 20735
20735 An unexpected index transform error error number occurred in audit fixup process process name.
Cause
An unexpected error occurred when trying to find audit records to apply to index.
Effect
Populate is not done.
Recovery
Recover the index file, check environment, and retry.
SQL 20751
20751 A user-defined transaction has been started. VERIFY cannot be performed.
Cause
A TMF transaction is currently active. The VERIFY process does not allow active transactions.
Effect
The operation fails.
Recovery
Commit or terminate the current transaction and resubmit.
SQL 20752
20752 The cmdname command cannot work on object object-name that has an object type of type. cmdname supports only objects that have an object type of BT.
-
Where,
-
cmdname is the name of the utility;
-
object-name is the name of the specified object;
-
type is the object's type as found in the metadata—base table (BT).
Cause
You possibly specified a utility operation on a view, stored procedure, or an alias for an SQL/MP object. The utility operation on these objects is not allowed.
Effect
The operation fails.
Recovery
Specify the name of a table and resubmit.
SQL 20753
20753 An internal error was encountered by the VERIFY operation.
Cause
An unexpected error caused VERIFY to terminate.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20754
20754 File system error (error) was returned while retrieving the object from the resource fork.
-
Where,
-
error is the error returned by the file system;
-
object is the information being retrieved, such as the ANSI name.
Cause
An unexpected error occurred while you were retrieving ANSI name information.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual topic File- System Errors for possible recovery action and resubmit.
SQL 20755
20755 VERIFY cannot work on object (object-name) either because the object is not a table, view, stored procedure, or because the specified table, view, stored procedure does not exist.
Cause
VERIFY failed because the specified object is not a table, view, or stored procedure. Possibly, the name is misspelled, or the object does not exist.
Effect
The operation fails.
Recovery
Retry the command by specifying a valid object name.
SQL 20756
20756 VERIFY cannot work on Guardian file (file) because it belongs to the space name space. VERIFY supports only objects in the namespace name space.
Cause
You specified a Guardian file that was not a base table.
Effect
The operation fails.
Recovery
None. VERIFY supports only Guardian files that belong to the SQL/MX table name space.
SQL 20757
20757 The file specified (filename) is a resource fork. Verify does not support operations on resource forks.
Cause
VERIFY failed because the name of the file is a resource fork.
Effect
The operation fails.
Recovery
None. VERIFY does not allow resource fork names to be specified.
SQL 20758
20758 Partition name is offline.
Cause
VERIFY discovered that the table being verified has a partition that is offline. This is a partition that is currently part of an active MODIFY request or a failed MODIFY request.
Effect
None. This is an informational message.
Recovery
If a MODIFY operation is currently in progress, this error can be ignored. If a MODIFY operation is not in progress, the offline partition needs to be recovered. Determine which MODIFY operation did not complete, and perform a RECOVER operation, and then resubmit.
SQL 20759
20759 Index name is offline.
Cause
The POPULATE INDEX command has not been run.
Effect
None. This is an informational message.
Recovery
At some point, the POPULATE INDEX command should be performed to make the index available for queries.
SQL 20760
20760 The redefinition timestamp (time1) defined on the label does not match the time (time2) defined in the metadata for Guardian file (file).
-
Where,
-
time1 is the Julian timestamp found on the label.
-
time2 is the Julian timestamp found in the metadata.
-
file is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Use FIXUP to change the redefinition timestamp to correct the inconsistency.
SQL 20761
20761 The corrupt flag (flag1) defined on the label does not match the corrupt flag (flag2) defined in the metadata for Guardian file (fname).
-
Where,
-
flag1 is the value of the corrupt flag on the label.
-
flag2 is the value of the corrupt flag found in the metadata.
-
fname is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Use FIXUP to change the corrupt bit to correct the inconsistency.
SQL 20762
20762 The primary extent size (size1) defined on the label does not match the value (size2) defined in the metadata for Guardian file (file).
-
Where,
-
size1 is the primary extent size defined on the label;
-
size2is the primary extent size defined in the metadata;
-
file is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20763
20763 The secondary extent size (size1) defined on the label does not match the value (size2) defined in the metadata for Guardian file (file).
-
Where,
-
size1 is the secondary extent size defined on the label;
-
size2 is the secondary extent size defined in the metadata;
-
file is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20764
20764 The max extent size (size1) defined on the label does not match the value (size2) defined in the metadata for Guardian file (file).
-
Where,
-
size1 is the maxextent size defined on the label;
-
size2 is the maxextent size defined in the metadata;
-
file is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20765
20765 The audit flag (flag1) defined on the label does not match the audit flag (flag2) defined in the metadata for Guardian file (file).
-
Where,
-
flag1 is the value of the flag stored in the label;
-
flag2 is the value of the flag stored in the metadata;
-
file is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Use VERIFY to change the audit attribute to correct the inconsistency.
SQL 20766
20766 The record size (size1) defined on the label does not match the record size (size2) defined in the metadata for Guardian file (file).
-
Where,
-
size1 is the record size stored in the file label;
-
size2 is the record size found in the metadata;
-
file is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20767
20767 The key size (size1) defined on the label does not match the key size (size2) defined in the metadata for Guardian file (file).
-
Where,
-
size1 is the key size stored in the file label;
-
size2 is the key size found in the metadata;
-
file is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20768
20768 The file (file) requested belongs to an object (object) with name space (space) which is not found in the metadata.
-
Where,
-
file is the Guardian file name of the partition being verified;
-
object is the ANSI name of the object the Guardian file belongs to;
-
space is the ANSI name space.
Cause
VERIFY was unable to find metadata associated with the Guardian file, possibly because the Guardian file is orphaned or the metadata is wrong.
Effect
The operation fails.
Recovery
If the Guardian file is no longer needed, use GOAWAY to remove it. If the Guardian file should be part of an ANSI name, the metadata tables might need to be recovered. Contact your service provider about metadata recovery.
SQL 20769
20769 The ANSI name (name1) in resource fork does not match the ANSI name (name2) defined in the metadata for Guardian file (file).
-
Where,
-
name1 is the ANSI name found in the resource fork;
-
name2is the ANSI name found in the metadata;
-
file is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20770
20770 The ANSI name namespace (space1) in resource fork does not match the ANSI namespace (space2) defined in the metadata for Guardian file (file).
-
Where,
-
space1 is the ANSI namespace found in the resource fork;
-
space2 is the ANSI namespace found in the metadata;
-
file is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20773
20773 The partition count in resource fork (num1) does not match the partition count (num2) in the metadata for Guardian file (file).
-
Where,
-
num1 is the number of partitions described in the resource fork;
-
num2 is the number of partitions described in the metadata;
-
file is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20774
20774 The constraint text in the resource fork does not match the constraint text in the metadata for constraint (name) while processing the Guardian file (file).
-
Where,
-
name is the constraint name described in the metadata;
-
file is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20775
20775 The number of droppable check constraints in resource fork (num1) does not match the number of droppable check constraints (num2) in the metadata for Guardian file (file).
-
Where,
-
num1 is the number of constraints described in the constraint map in the resource fork;
-
num2 is the number of constraints described in the metadata;
-
file is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20776
20776 Check constraint (constraint) is defined in the metadata but missing from the resource fork for object (object-name).
-
Where,
-
constraint is the name of the constraint that should exist in the constraint map in the resource fork;
-
object-name is the name of the object.
Cause
An inconsistency was found during the VERIFY operation.
Effect
This is an informational message. VERIFY found a problem that needs attention.
Recovery
Contact your service provider.
SQL 20777
20777 The constraint map is missing from the resource fork for Guardian file (file).
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20778
20778 The constraint information is missing from the metadata for object (name).
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20779
20779 The number of indexes (num1) in the index map array on the resource fork does not match the number of indexes (num2) in the metadata for Guardian file (file).
-
Where,
-
num1 is the number of indexes in the index map in the resource fork;
-
num2 is the number of populated indexes found in the metadata;
-
file is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20780
20780 Index (name) is defined in the metadata but missing from the resource fork for Guardian file (file).
-
Where,
-
name is the name of the index that should exist in the index map in the resource fork;
-
file is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20781
20781 The index map array is missing from the resource fork for Guardian file (file).
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20782
20782 The index information is missing from the metadata for index (name).
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20783
20783 The location (string1) defined in the partition map for Guardian file (file) does not match the location (string2) defined in metadata.
-
Where,
-
string1 is the Guardian name of the partition that is defined in the partition map on the resource fork that does not exist in the metadata;
-
file is the name of the Guardian file;
-
string2 is the Guardian name of the partition as it is defined in the metadata (PARTITIONS or REPLICAS tables).
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20784
20784 Partition map entry (file1) is defined in the metadata but is missing from the resource fork for Guardian file (file2).
-
Where,
-
file1 is the Guardian name of the partition;
-
file2 is the Guardian file where there was no partition map. The metadata indicates that there should be a partition map.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20785
20785 The partition information for Guardian file (file) is missing from the metadata for object (name).
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20786
20786 The partition map is missing from the resource fork for Guardian file (file).
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20787
20787 The partition (name1) defined in the metadata for index (index) does not match the partition (name2) defined in the resource fork for Guardian file (file).
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20788
20788 User does not have authority to perform operation for object object.
Cause
The requestor does not have the privileges to perform the VERIFY operation.
Effect
The operation fails.
Recovery
Fix the problem and resubmit.
SQL 20789
20789 The object schema version in resource fork (rversion) does not match version (mversion) in the metadata for Guardian file (file).
-
Where,
-
rversion is the object schema version stored in the resource fork;
-
mversion is the object schema version stored in the Guardian file;
-
file is the Guardian file where an inconsistency is detected.
Cause
An inconsistency was found between the object schema version stored in the resource fork and object schema version found in the metadata.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20790
20790 The partition name (rname) defined in the resource fork does not match the partition name (mname) defined in the metadata for Guardian file (file).
-
Where,
-
rname is the partition name defined in the resource fork;
-
mname is the partition name defined in the metadata;
-
file is the file being verified.
Cause
An inconsistency was found between the partition name stored in the resource fork and the partition name found in the metadata.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20791
20791 An internal error occurred - the partition list is missing from the metadata for object (name).
Cause
VERIFY is comparing the partition map defined in the resource fork with the information stored in the metadata. It discovered that the metadata does not contain any partition information. Metadata should show at least one entry for the object.
Effect
VERIFY has detected a problem and reported an inconsistency.
Recovery
Contact your service provider.
SQL 20792
20792 VERIFY is not able to read file label information for Guardian file file name.
Cause
An unexpected error was returned while extracting parts of the ANSI name from the resource fork.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual topic File- System Errors for possible recovery action and resubmit.
SQL 20794
20794 Error (number) was returned when trying to extract the catalog, schema, or table from the ANSI name defined in the resource fork for Guardian file (file).
Cause
An unexpected error returned on an attempt to extract the catalog name, schema, or table from the resource fork.
Effect
The operation fails.
Recovery
Correct the problem and resubmit. If the problem persists, contact your service provider about this condition.
SQL 20795
20795 VERIFY cannot work on Guardian file (file) that has an object type of (type1). VERIFY supports only objects that have an object type of type2.
-
Where,
-
file is the Guardian file being verified;
-
type1 is the object type found in the label information;
-
type2 is the supported object type.
Cause
You attempted to verify a Guardian file with an unsupported object type.
Effect
The operation fails.
Recovery
None.
SQL 20797
20797 The partition list for index (name) found in the index map array for object (table) does not match the partition information stored in the metadata.
-
Where,
-
name is the name of the index in the index map array being verified;
-
table is the name of the table being verified.
Cause
VERIFY compared the list of indexes defined in the index map of the specified table with the list of indexes defined in the metadata and discovered that the information does not match.
Effect
VERIFY has detected a problem and reported an inconsistency.
Recovery
Contact your service provider.
SQL 20798
20798 There is currently an active/inactive DDL lock for object (object name).
-
Where,
-
active/inactive specifies whether the lock is active or inactive;
-
object specifies whether the object is a table or view;
-
object name is the ANSI fully qualified name of the table or view.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
For an inactive DDL lock, contact your service provider. For an active DDL lock, wait for the operation holding the lock to complete.
SQL 20799
20799 The object-type UID in the resource fork (ruid) does not match the UID (muid) in the metadata for Guardian file (file-name).
-
Where,
-
object-type is the type of object, which can be CATALOG, SCHEMA, TABLE, or INDEX;
-
ruid is the UID value of the object stored in the resource fork;
-
muid is the UID value of the object stored in the metadata;
-
file-name is the name of the Guardian file.
Cause
An inconsistency was found. The UID value in the metadata tables does not match the UID value in the resource fork.
Effect
This mismatch causes operations that depend on these values to be the same to fail.
Recovery
Run the
-ru option of
MXTOOL FIXUP to make the UID value in the resource fork match the UID value in the metadata.
SQL 20800
20800 The partitioning scheme in resource fork rscheme does not match the partitioning scheme mscheme defined in the metadata for Guardian file (file-name).
-
Where,
-
rscheme is the partitioning scheme of the object stored in the resource fork;
-
mscheme is the partitioning scheme of the object stored in the metadata;
-
file-name is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20801
20801 There is currently an activity row hiding predicate for file-name.
-
Where,
-
activity indicates an active row hiding a predicate;
-
file-name is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation. Another utility operation on the same partition is already in progress or has failed.
Effect
None. This is an informational message.
Recovery
Check if another utility operation is using the same partition and is in progress. If it is not, contact your service provider.
SQL 20802
20802 The IncompletePartBoundChg flag is turned on for object (object-name), file (file-name).
Cause
An inconsistency was found during the VERIFY operation. Another utility operation on the same partition is already in progress or has failed.
Effect
None. This is an informational message.
Recovery
Check if another utility operation is using the same partition and is in progress. If it is not, contact your service provider.
SQL 20803
20803 The UnreclaimedSpace flag is turned on for object (object-name), file (file-name).
Cause
An inconsistency was found during the VERIFY operation. Another utility operation on the same partition is already in progress or has failed.
Effect
None. This is an informational message.
Recovery
Check if another utility operation is using the same partition and is in progress. If it is not, contact your service provider.
SQL 20804
20804 The object type in resource fork (robject-type) does not match the object type (mobject-type) defined in the metadata for Guardian file (file-name).
-
Where,
-
robject-type is the object type in the resource fork;
-
mobject-type is the object type in the metadata;
-
file-name is the name of the Guardian file.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider C.
SQL 20805
20805 The auditcompress flag (flag value) defined on the label does not match the auditcompress flag (flag value) defined in the metadata for Guardian file (file-name).
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20806
20806 The (flag value) flag is set for Guardian file (file-name).
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20807
20807 File code (code value) is incorrect for Guardian file ( file-name).
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20816
20816 The current_epoch defined on the label does not match the current_epoch defined in the metadata for Guardian file (file).
Cause
An inconsistency was found during the VERIFY operation.
Effect
This is an informational message. VERIFY found a problem that needs attention.
Recovery
Contact your service provider.
SQL 20820
20820 The RCB (Record Control Block) version defined on the label does not match the RCB version defined in the metadata for Guardian file file-name of object object-name.
-
Where,
-
file-name is the name of the Guardian file.
-
object-name is the name of the object being verified.
Cause
An inconsistency was found during the VERIFY operation. The object has not been updated since the system upgrade.
Effect
None. This is an informational message.
Recovery
Perform a SELECT COUNT (*) on the object being verified to perform a lazy update to fix the RCB version. If the problem persists after the SELECT operation, contact your service provider.
mxtool fixup fixes the RCB version inconsistency when used with the "-rt" option for SQL/MX objects
.
SQL 20821
20821 Constraint constraint is disabled.
Cause
MXTOOL VERIFY found a constraint that is disabled.
Effect
This is an informational message.
Recovery
Contact your service provider to enable the constraint.
SQL 20822
20822 The DML privileges in the file label do not match the privileges defined in the metadata.
Cause
An inconsistency was found during the VERIFY operation.
Effect
None. This is an informational message.
Recovery
Contact your service provider.
SQL 20850
20850 Audit bit was not changed for file file-name. Already set to the correct value of value.
-
Where,
-
file-name is the Guardian file name of the SQL/MX object;
-
value is either a 0 or 1. A 0 indicates that the file is not currently audited, and a 1 indicates that the file is currently audited.
Cause
The "-a" option was used with the FIXUP utility to change the audit bit on an SQL/MX file to the currently set value.
Effect
None. This is a warning.
Recovery
No recovery is necessary.
SQL 20851
20851 The resource fork for file filename contains inconsistent information.
Cause
The resource fork for the specified file contains inconsistent information.
Effect
The operation fails.
Recovery
Recover the resource fork using the TMF online DUMP, if available.
SQL 20852
20852 Broken bit was not changed for file file-name. Already set to the correct value of value.
-
Where,
-
file-name is the Guardian file name of the SQL/MX object;
-
value is always 0 to indicate the broken bit is already cleared.
Cause
The ‘-rb" option was used with the FIXUP utility to reset the broken bit on a file where the broken bit is not currently set.
Effect
None. This is a warning.
Recovery
No recovery is necessary.
SQL 20853
20853 name is not an SQL/MX object that is supported by FIXUP. Only TABLES and INDEXES are supported.
Cause
You attempted to run the FIXUP utility on an SQL/MX object that was not a table or index.
Effect
The operation fails.
Recovery
Do not attempt to run the FIXUP utility on objects other than tables and indexes. Enter a valid name and resubmit.
SQL 20854
20854 Table table references an MP object. Please fix up MP objects through SQL/MP.
Cause
You attempted to use the FIXUP utility on an SQL/MP object.
Effect
The operation fails.
Recovery
See the SQL/MP documentation for instructions on fixing SQL/MP objects.
SQL 20856
20856 FIXUP did not reset the corrupt bit for file-name. It is already set to the correct value of value.
-
Where,
-
file-name is the Guardian file-name of the SQL/MX object;
-
value is always 0 to indicate the corrupt bit is cleared.
Cause
The "-rc" option was used with the FIXUP utility to reset the corrupt bit on a file where the corrupt bit is not currently set.
Effect
None. This is a warning.
Recovery
No recovery is necessary.
SQL 20857
20857 FIXUP did not change the redefinition timestamp for file file-name. It is already set to the correct value of time.
-
Where,
-
file-name is the Guardian file-name of the SQL/MX object;
-
time is the current redefinition timestamp associated with the SQL/MX object.
Cause
The "-rt" option was used with the FIXUP utility to set the correct redefinition timestamp for an SQL/MX object, but the time was already the same time recorded in the file label for the object.
Effect
None. This is a warning.
Recovery
No recovery is necessary.
SQL 20858
20858 File file-name is located on a remote node. The current FIXUP operation cannot be performed remotely.
Cause
You attempted to specify the FIXUP utility on a file that exists on a remote node.
Effect
The operation fails.
Recovery
Run the FIXUP utility on the remote node.
SQL 20859
20859 An internal FIXUP error occurred.
Cause
An internal error occurred.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 20860
20860 file-name is not a datafork/label. Only changes to datafork/label are supported.
Cause
You specified a file other than an SQL/MX data fork.
Effect
The operation fails.
Recovery
Enter the correct SQL/MX file-name and resubmit.
SQL 20861
20861 The corrupt bit has been reset for only local partitions of file-name. Please execute the command on the remote nodes to update respective remote partitions.
Cause
This message is displayed whenever FIXUP is used with the "-rc" option on a table or index with partitions on a remote node.
Effect
The corrupt bit is reset only on the local node.
Recovery
Clear the corrupt bit on each remote node by issuing the FIXUP command with the ‘-rc" option.
SQL 20877
20877 The input file name contains invalid header information.
Cause
The header information of the input file did not match the header format.
Effect
The operation fails.
Recovery
Fix the header information and retry the request.
SQL 20991
20991 Materialized View materialized-view-name has refresh type not supported by PURGEDATA. PURGEDATA cannot be performed.
-
Where,
-
materialized-view-name is the name of the object on which the command was attempted.
Cause
The PURGEDATA command was run on a materialized view object.
Effect
The operation fails.
Recovery
None.
SQL 21051
21051 FASTCOPY is not possible because tables source-table and target-table are not equivalent.
-
Where,
-
source-table is the three-part ANSI name of the source table of a FASTCOPY command;
-
target-table is the three-part ANSI name of the target table of a FASTCOPY command.
Cause
The FASTCOPY TABLE or FASTCOPY INDEX command is executed with incompatible source and target objects. The accompanying error messages are displayed with detailed incompatibility information.
Effect
The fastcopy operation fails. The source and target tables are available to other operations.
Recovery
None.
SQL 21052
21052 Tables source-table and target-table have incompatible clustering key specifications.
-
Where,
-
source-table is the three-part ANSI name of the source table of a FASTCOPY command;
-
target-table is the three-part ANSI name of the target table of a FASTCOPY command.
Cause
The FASTCOPY TABLE or FASTCOPY INDEX command is executed. The clustering keys for the source and target tables do not satisfy all the following conditions:
-
either both tables have a SYSKEY column or both tables must not have a SYSKEY column
-
SYSKEY column, if any, have the same column number in the tables
-
clustering keys have the same number of columns
-
each source-target pair of clustering key columns, in key sequence order, have the same column number in the tables
Effect
The fastcopy operation fails. The source and target tables are available to other operations.
Recovery
None.
SQL 21053
21053 Indexes source-index and target-index have incompatible index specifications.
-
Where,
-
source-index is the three-part ANSI name of the source index of a FASTCOPY command;
-
target-index is the three-part ANSI name of the target index of a FASTCOPY command.
Cause
The FASTCOPY INDEX command is executed. The index specifications for the source and target tables do not satisfy all the following conditions:
-
indexes have the same number of index columns
-
each source-target pair of index columns, in key sequence order, have the same column number in the tables
Effect
The fastcopy operation fails. The availability of source and target indexes and their tables is not affected.
Recovery
None.
SQL 21054
21054 Index target-index has no matching index from table source-table.
-
Where,
-
source-table is the three-part ANSI name of the source table of a FASTCOPY command;
-
target-index is the three-part ANSI name of an index on the target table of a FASTCOPY command.
Cause
An initial FASTCOPY command is executed and no index on the source table matches the target-index . Two indexes match when all the following conditions are satisfied:
-
indexes have the same number of index columns
-
each source-target pair of index columns, in key sequence order, have the same column number in the tables
Effect
The fastcopy operation fails. The source and target tables are available to other operations.
Recovery
None.
SQL 21055
21055 object-type target-object has been processed by another FASTCOPY command.
-
Where,
-
object-type is a table or index you specified in the command syntax;
-
target-object is the three-part ANSI name of the target object for a FASTCOPY command.
Cause
A FASTCOPY command is executed and all the rows from the source objects are already copied to the specified target object or they are being copied by previous FASTCOPY command.
Effect
None. This is an informational command.
Recovery
None.
SQL 21056
21056 Index index is offline.
-
Where index is the three-part ANSI name of the source or target index of the FASTCOPY INDEX command.
Cause
The FASTCOPY INDEX command is executed and the source or target index is offline.
Effect
The fastcopy operation fails. The availability of source and target indexes and their tables is not affected.
Recovery
Make the above indicated index, index, online using the appropriate utility command, before retrying the fastcopy operation.
SQL 21057
21057 Cannot FASTCOPY to table target-table because it is being referenced by another table.
Cause
A FASTCOPY command is executed for a non-empty target table or target index and the REFERENTIAL INTEGRITY (RI) constraint on another table references the target table.
Effect
The fastcopy operation fails. The target table and its indexes are available to other operations.
Recovery
Remove the RI constraint and retry, if required.
SQL 21058
21058 Data copy failed for the FASTCOPY of source-object into target-object.
-
Where,
-
source-object is the three-part ANSI name of a source table or index for a FASTCOPY command;
-
target-object is the three-part ANSI name of a target table or index for a FASTCOPY command.
Cause
An error occurred during the data copy part of the fastcopy operation. The accompanying error messages provide the details.
Effect
The FASTCOPY operation fails; target objects are left in an incomplete state.
Recovery
Use the RECOVER operation to either CANCEL or RESUME the fastcopy operation depending on the actual error.
SQL 21059
21059 object-name cannot participate in a FASTCOPY command.
Cause
The FASTCOPY operation is attempted on an unsupported object for the operation.
Effect
The operation fails.
Recovery
None.
SQL 21060
21060 A user-defined transaction has been started. FASTCOPY cannot be performed.
Cause
A user-defined transaction is active when a FASTCOPY command is executed.
Effect
The fastcopy operation fails; involved objects are left unchanged.
Recovery
Commit the user-defined transaction and retry the FASTCOPY command.
SQL 21061
21061 Catalog catalog does not exist or cannot be accessed.
Cause
A FASTCOPY command referenced an object from catalog. However, the catalog does not exist or is not registered on the system where the command is executed.
Effect
The fastcopy operation fails; involved objects are left unchanged.
Recovery
None.
SQL 21062
21062 Schema schema does not exist or cannot be accessed.
Cause
A FASTCOPY command referenced an object from schema. However, the schema does not exist.
Effect
The fastcopy operation fails; involved objects are left unchanged.
Recovery
None.
SQL 21063
21063 Object object does not exist or cannot be accessed.
Cause
A FASTCOPY command referenced an object. However, the object does not exist.
Effect
The fastcopy operation fails; involved objects are left unchanged.
Recovery
None.
SQL 21064
21064 object-1 already participates in a fastcopy operation whereas object-2 does not.
-
Where,
-
object-1 is the three-part ANSI name of one of the two objects for a FASTCOPY command;
-
object-2 is the three-part ANSI name of the other object for a FASTCOPY command.
Cause
One of the objects for continuation FASTCOPY command does not participate in any fastcopy operation, whereas the other object participates in a fastcopy operation.
Effect
The operation fails; involved objects are left unchanged.
Recovery
None.
SQL 21065
21065 source and target already participate in different fastcopy operations.
-
Where,
-
source-object is the three-part ANSI name of a source table or index for a FASTCOPY command;
-
target-object is the three-part ANSI name of a target table or index for a FASTCOPY command.
Cause
The source and target objects for continuation FASTCOPY command are either part of different fastcopy operations or their roles are reversed compared to the corresponding original FASTCOPY command.
Effect
The operation fails; involved objects are left unchanged.
Recovery
None.
SQL 21066
21066 Target object-type is the same as source.
Cause
For a FASTCOPY command, source and target specify the same object.
Effect
The operation fails; involved objects are left unchanged.
Recovery
None.
SQL 21067
21067 Source and target index belong to the same base table.
Cause
For the FASTCOPY INDEX command, source and target specify indexes from the same base table.
Effect
The operation fails; involved objects are left unchanged.
Recovery
None.
SQL 21068
21068 The FASTCOPY of target-object has been canceled.
-
Where target-object is the three-part ANSI name of a target table or index for a FASTCOPY or RECOVER...RESUME command.
Cause
The RECOVER...CANCEL operation is in progress for the target object.
Effect
The operation fails; involved objects are left unchanged.
Recovery
None.
SQL 21069
21069 FASTCOPY already is in progress for target-table.
Cause
A FASTCOPY command uses INDEXES IMPLICIT. However, a fastcopy operation is already initiated for the target table or one of its indexes.
Effect
The operation fails; involved objects are left unchanged.
Recovery
None.
SQL 21070
21070 source-object has been modified since the initial FASTCOPY was started.
Cause
The FASTCOPY is a continuation of a previous command and the source object is modified because the previous command was issued.
Effect
The entire fastcopy operation is canceled. Involved target objects are left empty and available.
Recovery
Initiate a new fastcopy operation.
SQL 21071
21071 target-table has DELETE triggers enabled.
Cause
The target table for an initial FASTCOPY command is non-empty; is the subject table for a DELETE trigger that is enabled.
Effect
The operation fails; involved objects are left unchanged.
Recovery
Disable DELETE triggers on the target table, retry the FASTCOPY command, and then enable the triggers again.
SQL 21072
21072 target-table has a SYSKEY column and is the subject table for a trigger.
Cause
The target table for an initial FASTCOPY command has a system defined SYSKEY column, and is the subject table for one or more triggers. A FASTCOPY command cannot operate on such a table.
Effect
The operation fails; involved objects are left unchanged.
Recovery
Drop all triggers that have the target table as subject table, retry the FASTCOPY command, and then recreate the triggers. If necessary, execute queries that will perform the trigger actions.
SQL 21073
21073 FASTCOPY does not support target tables with names longer than 122 characters.
Cause
The target table for a FASTCOPY command has an ANSI name part that is longer than 122 characters. This is not supported by FASTCOPY.
Effect
The operation fails; involved objects are left unchanged.
Recovery
None.
SQL 21074
21074 IDENTITY column on target table has IDENTITY specifications that are incompatible with corresponding IDENTITY column on source table.
Cause
The sequence generator specifications of source and target tables do not match.
Effect
The FASTCOPY operation fails to execute.
Recovery
This error is returned when the following conditions are not met. Ensure that these conditions are met, and retry FASTCOPY operation.
-
If the IDENTITY column of target table is defined as GENERATED ALWAYS, the source table IDENTITY column must be defined as GENERATED ALWAYS.
-
If the IDENTITY columns of source and target tables are defined as GENERATED ALWAYS, their sequence generator attributes must be identical.
-
If the IDENTITY columns of source and target tables are defined as GENERATED ALWAYS, their IDENTITY column positions must match.
SQL 23001
23001 servername: An error occurred while instantiating class-name.
-
Where,
-
servername is the name of the server program that issued the error;
-
class-name is the name of the class that could not be instantiated.
Cause
An error occurred while instantiating the class-name.
Effect
The operation fails.
Recovery
Do not attempt recovery. Contact your service provider.
SQL 23002
23002 servername: An error occurred while allocating heap.
Cause
An error occurred when allocating an object on the heap.
Effect
A resource cannot be allocated and the program fails.
Recovery
Resubmit on another processor.
SQL 23003
23003 servername: File error encountered: description.
-
Where,
-
description is the name of the server program that issued the error;
-
servername provides more detail about the file error.
Cause
See details in description.
Effect
The operation fails.
Recovery
Correct the run-time argument and resubmit.
SQL 23004
23004 Specified argument is not valid: argument_1 argument_2.
-
Where,
-
argument_1 is the parameters provided to a utility operation or command.
-
argument_2 is the parameters provided to a utility operation or command.
Cause
The unsupported parameters were specified in a utility operation or command.
Effect
The operation fails.
Recovery
None.
SQL 23005
23005 Required argument is missing — argument_type.
Cause
A run-time argument is missing.
Effect
The operation fails.
Recovery
Correct the run-time argument and resubmit.
SQL 23007
23007 servername: An SQL Error occurred: description.
-
Where,
-
servername is the name of the server program that issued the error;
-
description provides details about the file error.
Cause
The DML Layer reported an SQL error. See description for the reason.
Effect
The operation fails.
Recovery
Do not attempt recovery. Contact your service provider.
SQL 23008
23008 Assertion failed.
Cause
Internal program ASSERT failed, indicating an invalid program state.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 23009
In the context of SqlMxHealthCheck, this error will be issued if mutually exclusive arguments are specified.
23009 Too many arguments were provided: details.
Cause
The run-time arguments specified are mutually exclusive, both the arguments cannot be specified together.
Effect
The operation fails.
Recovery
Correct the run-time arguments and resubmit.
SQL 23011
23011 servername: An unexpected XML tag found: xml_tag.
-
Where,
-
servername is the name of the server program that issued the error;
-
xml_tag is the XML tag that could not be identified.
Cause
servername discovered an XML tag that is not supported or is invalid. This error could indicate a problem with the
mxexportddl XML file generation. It could also indicate a version problem of a downrev
mximportddl running on input from an uprev
mxexportddl.
Effect
The operation fails.
Recovery
Correct the input XML file and resubmit.
SQL 23012
23012 servername: File system error error_number from procedure: proc_call.
-
Where,
-
servername is the name of the server program that issued the error;
-
error_number is the file-system error number returned;
-
proc_call is the name of the procedure call returning the error.
Cause
The file system procedure proc_call returned an error error_number.
Effect
The operation fails.
Recovery
Correct the problem and resubmit.
SQL 23013
23013 servername: Error code: nnn. No error text available for this code.
-
Where,
-
servername is the name of the server program that issued the error;
-
nnn is the unknown error code.
Cause
An exception occurred for an unexpected error.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 23014
23014 servername: An internal error occurred - unhandled exception; cannot proceed.
Cause
An unexpected exception occurred.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 23015
23015 servername: DDL command could not be found in buffer: description.
-
Where,
-
servername is the name of the server program that issued the error;
-
description contains details about the missing information in the DDL buffer.
Cause
Expected DDL command not found in the XML input file. This might indicate a problem with
mxexportddl XML file generation.
Effect
The operation fails.
Recovery
Determine the problem with the input file and resubmit.
SQL 23016
23016 servername: Formatted file error was encountered: description.
-
Where,
-
servername is the name of the server program that issued the error;
-
description contains detailed information about the formatted file in error.
Cause
The formatted XML file is invalid.
description indicates the nature of the problem. If the file is damaged or not a valid format, it might indicate a problem with the
mxexportddl program.
Effect
The operation fails.
Recovery
Determine the problem with the formatted file and resubmit. If the problem persists, contact your service provider.
SQL 23017
23017 servername: Expected XML tag is missing: description.
-
Where,
-
servername is the name of the server program that issued the error;
-
description contains detailed information about the missing XML tag.
Cause
When processing an XML input file, an expected tag or tag attribute was not found. This might indicate a problem with the
mxexportddl generated output XML file.
Effect
The operation fails.
Recovery
Determine the problem with the input file and resubmit.
SQL 23018
23018 servername: Expected map entry is missing: description.
-
Where,
-
servername is the name of the server program that issued the error;
-
description contains detailed information about the missing mapping file section name.
Cause
When processing a mapping file, an expected section or attribute was not found.
Effect
The operation fails.
Recovery
Correct the mapping file and resubmit.
SQL 23019
23019 An invalid combination of options was provided description.
Cause
An invalid set of run-time arguments are provided.
Effect
The operation fails.
Recovery
Specify a valid set of run-time arguments and resubmit.
SQL 23020
23020 servername: SQL/MX object was not found: object-name.
-
Where,
-
servername is the name of the server program that issued the error;
-
object-name is the name of the missing SQL/MX object.
Cause
An expected SQL/MX object is not on the target system.
Effect
The operation fails.
Recovery
Correct the target system and resubmit.
SQL 23021
23021 An argument requires a corresponding value description.
Cause
You did not specify a needed value for a specific run-time argument.
Effect
The operation fails.
Recovery
Specify a valid argument value and resubmit.
SQL 23022
23022 Error occurred for partition file name when attempting to set the statistics metadata.
Cause
The program was unable to update the partition metadata.
Effect
The operation fails.
Recovery
None. Contact your service provider
SQL 23023
23023 SQL/MP tables and aliases are not supported.
Cause
None.
Effect
SQL/MP tables and aliases will not be exported or imported.
Recovery
None.
SQL 23024
23024 object-type object-name already exists.
Cause
The target SQL/MX object already exists.
Effect
None.
Recovery
None.
SQL 23025
23025 object-type object-name is skipped.
Cause
An unexpected error has occurred.
Effect
The reported SQL/MX object is skipped.
Recovery
None. Contact your service provider.
SQL 23026
23026 object-type object-name is dropped and recreated.
Cause
The target SQL/MX object already exists and
KEEPDDL option is set to OFF.
Effect
The target SQL/MX object will be dropped and recreated.
Recovery
None. Contact your service provider.
SQL 23027
23027 Statistics of the table table-name already exists.
Cause
The target table already contains statistics.
Effect
None.
Recovery
None.
SQL 23028
23028 Statistics of the table table-name is cleared.
Cause
The target table already contains statistics and
KEEPSTATS option is set to OFF.
Effect
The target table's statistics will be cleared.
Recovery
To avoid statistics from being cleared, set
KEEPSTATS option to ON.
SQL 23029
23029 option-name argument is provided and so SQL/MX objects are not imported.
Cause
None.
Effect
SQL/MX objects will not be imported.
Recovery
None.
SQL 23030
23030 Only schema owner or super.super can perform the operation.
Cause
The
mxexportddl or
mximportddl operation is started by non-schema owner or non super ID user.
Effect
The operation fails.
Recovery
None.