Message Reference
ADM message updates
7
7
7ADM12504E
7The description for message ADM12504E incorrectly implies that the instance
7name on the primary database should match the instance name on the standby
7database.
7
7- ADM12504E
7- Unable to establish HADR primary-standby connection because the DB2 instance
7names do not match. Correct the HADR_REMOTE_INST configuration parameter.
7
7
7It is not a HADR requirement for the instance name on the primary to match
7the instance name on the standby.
CLP message updates
7
7
7DB21015E
7The Command Line Processor backend process request queue or input queue
7was not created within the timeout period.
7
7- Explanation
7- Either the values for the DB2BQTRY and DB2BQTIME environment variables
7need to be increased or the command line processor back-end program "db2bp"
7cannot be started. The "db2bp" program must reside in the correct database
7manager install path and users must have execute permission on the file.
7
7
On Linux and UNIX platforms, ensure that the file system has enough file blocks
7and inodes.
7
7- User Response
7- Correct the error and resubmit the command.
7
7
5
5
5DBI message updates
5
5DBI1060E
5Invalid package name <"pkg-name">
5
5
5- Explanation:
5- An incorrect name has been entered. The package either does not exist
5or the name has been entered incorrectly.
5
5- User Response:
5- Check to see if the name of the given package exists on the distribution
5media. If so, examine the name to see if it has been misspelled. All package
5names should be in lowercase.
5
5
SQL message additions and updates
7
7
7SQL0121N
7The target name "<name>" is specified more than once for assignment
7in the same SQL statement.
7
7- Explanation
7- The same target name "<name>" is specified more than once as an
7 OUT or INOUT argument of a CALL statement, or in the list of columns of an
7 INSERT statement, the left hand side of assignments in the SET clause of an UPDATE statement, or the left hand side of the assignment
7statement. The target name identifies a column, SQL parameter, SQL variable,
7or new transition variable.
7
Note that this error may occur when updating
7or inserting into a view where more than one column of the view is based
7on the same column of a base table.
7The statement cannot be processed.
7
7- User Response
7- Correct the syntax of the statement so each name is specified only once.
7
7
sqlcode : -121
7
7
7
7
7SQL0270N
7Function not supported (Reason code = "<reason-code>")
7
7
7- Explanation
7- 74 Updating a status field in the recovery history file by timestamp
7is not allowed.
7
7- User Response
7- 74 Update the status field in the recovery history file by EID only.
7
7
7
7
7- Explanation
7- 75 Automatic statistics collection is not supported on a multiple
7database partition system, on a system where SMP is enabled, or on a federated
7system.
7
7- User Response
7- 75 Disable automatic statistics collection for this database by setting
7the database configuration parameters AUTO_STATS_PROF and AUTO_PROF_UPD to
7OFF.
7
Or change the system to one that is on a single database partition,
7where SMP is not enabled, and that is not federated.
7
7
7
7
7SQL0494W
7The number of result sets is greater than the number of locators.
7
7
7- Explanation
7- The number of result set locators specified on the ASSOCIATE LOCATORS
7statement is less than the number of result sets returned by the stored procedure.
7The first "n" result set locator values are returned, where "n" is the number
7of result set locator variables specified on the SQL statement.
7
The SQL
7statement is successful.
7
7- User Response
7- Increase the number of result set locator variables specified on the
7SQL statement.
7
7
7sqlcode : +494
7sqlstate : 01614
7
7
7SQL1227N
7
7- Explanation
7-
7
7- Reason code 4
7- Buffer size entries of PAGE_FETCH_PAIRS must be ascending in value.
7Also, for 32-bit instances, any buffer size value in a PAGE_FETCH_PAIRS entry
7cannot be greater than the number of pages in the table or 524287, whichever
7is lower. For 64-bit instances, any buffer size value in a PAGE_FETCH_PAIRS
7entry cannot be greater than the number of pages in the table or 2147483674.
7
7
7
7
8
8
8SQL1271W
8SQL1271W Database "<name>" is recovered but one or more table
8spaces are offline on node(s) "<node-list>".
8
8
8- Explanation
8- This message can occur after crash recovery, database level roll-forward
8recovery, or table space level roll-forward recovery. For database level roll-forward
8recovery, the database is available for use if the STOP option was specified.
8 One or more table spaces on the specified nodes are not available. This situation
8could occur under any of the following situations:
8
8- One or more table spaces receive I/O errors during recovery.
8- One or more table spaces may require storage definition following recovery.
8- One or more table spaces are unusable and must be dropped.
8- One or more table spaces have been taken offline.
8- Additional table spaces are restored while a table space level roll-forward
8recovery is already in progress.
8- The database is rolled forward past a previous point-in-time table space
8roll-forward recovery, causing all table spaces involved to be placed in restore-pending
8state.
The table spaces that are offline can be identified on the specified
8node or nodes by the LIST TABLESPACES command or the db2dart utility. The administration notification log will provide more
8information on specific table spaces.
8If ",..." is displayed at
8the end of the node list, see the administration notification log for the
8complete list of nodes.
8
8Note:
8If you are using a partitioned database
8server, the node number or numbers indicate which node or nodes the error
8occurred on. Otherwise, the node number is not pertinent and should be ignored.
8
8- User Response
8- Repair or restore the table spaces if necessary and run roll-forward
8recovery. If the same error occurs, try running table space level roll-forward
8recovery offline.
8
8
7
7
7SQL1768N
7Unable to start HADR. Reason code = "<reason-code>"
7
7
7- Explanation:
7- 9 The database is configured to use raw logs.
7
7- User Response:
7- 9 Reconfigure the database to use only file system storage for the
7log files, instead of using raw i/o (direct disk access) devices. Refer to
7the discussion of the logpath and newlogpath database configuration parameters in Administration Guide: Performance.
7
7
7
7
7SQL1790W
7A default table space could not be found with a page size of at least
7"<page size>".
7
7
7- Explanation
7- The procedure NNSTAT was not able to create the SYSPROC.FED_STATS table
7to keep a history of the statement that was run. The table space with sufficient
7page size (at least "<pagesize>") could not be found.
7
7- User Response
7- Ensure that a table space with a page size of at least "<pagesize>"
7exists.
7
7
7sqlcode: +1790
7sqlstate: 01670
7
7
7SQL1791N
7The specified server definition, schema, or nickname object-name does not
7exist.
7
7
7- Explanation
7- The procedure NNSTAT accepts a server definition, schema, and nickname
7as input and one or more of these objects, including object-name, could not
7be found.
7
7- User Response
7- Specify an existing server definition, schema, or nickname and resubmit
7the statement.
7
7
7sqlcode: -1791
7sqlstate: 42704
7
7
7SQL2316W
7The Runstats command string for the statistics profile has exceeded the
7maximum size. The Runstats command string will be truncated to the maximum
7size and stored in the catalog table SYSIBM.SYSTABLE.
7
7
7- Explanation
7- The maximum size of the STATISTICS_PROFILE column is 32768 bytes. If
7the size of the Runstats command string for the statistics profile is greater
7than this amount, the Runstats command string is truncated to the maximum
7size.
7
The utility continues processing.
7
7- User Response
7- Refer to the STATISTICS_PROFILE column in the catalog table SYSIBM.SYSTABLES
7to review the statistics profile. If the existing statistics profile is not
7desired, reissue the RUNSTATS utility and specify the UPDATE PROFILE or the
7UPDATE PROFILE ONLY option to modify the profile. Refer to the RUNSTATS utility
7documentation for information about the utility options.
7
7
7
7
7SQL3705N
7The buffer size parameter specified is not valid. The buffer size must
7be specified as 0 or be between 8 and 250000 inclusive. For multiple buffers,
7the total buffer size must not exceed 250000.
8
8
8SQL5099N
8There is a new reason code for SQL5099N:
817 - Cannot disable log archiving when database is in roll forward pending
8state.
7
7
7SQL20290N
7The SQL statement references routine "<routine-name>" (specific name
7"<specific-name>") which cannot be run on partition "<partition-number>".
7
7
7- Explanation
7- The routine "<routine-name>" (specific name "<specific-name>")
7was called with an invalid partition number "<partition-number>".
7
7- User Response
7- Specify -1 for the partition number parameter to run the routine on
7the current partition.
7
7
7sqlcode: -20290
7sqlstate: 560CA
7
7
7SQL22025N
7An invalid input argument was specified for the reorgchk stored procedure.
7
7
7- Explanation
7- Only 'T' and 'S' are supported for the first argument of the stored
7procedure. If 'T' is specified as the first argument, the second argument
7to the stored procedure must be a fully qualified table name as <schema.table-name>.
7
7- User Response
7- Resubmit with valid input arguments.
7
7
7
7
7SQL27994W
7The length of a special register default column is smaller than the target
7column length. Load may truncate the values corresponding to this column
7(<column-num>).
7
7
7- Explanation
7- The clause SESSION_USER, CURRENT_USER, SYSTEM_USER, or CURRENT_SCHEMA
7has been specified for column "<column-num>", but this column was either
7defined with a length that is less than 128 bytes (SESSION_USER only) or
7the column-value inserted into this column may exceed the target length after
7code page conversion. Load may truncate the column-value.
7
7- User Response
7- If your system standards would not allow a user ID (SESSION_USER) to
7exceed the length of the column, then this warning may be ignored. To prevent
7this warning from occurring, the length of the column must be at least 128
7bytes. If code page conversion resulted in the growth of this register default
7column, increase the length of the column to accommodate the growth.
7
7
[ Top of Page |Previous Page | Next Page | Contents ]