Cause: ddcstrc was not able to write the trace information to the filename that it has been instructed to write to.
Action: Ensure that the filename specified is valid for your file system. If a filename is not specified, ensure that you have the necessary permission to write to the default file ddcstrc.tmp.
Cause: Because of an error condition ddcstrc has not been turned off. This was done to ensure that the trace information will not be lost before being safely placed in a file.
Action: Correct the ddcstrc error condition reported prior to this error and attempt to turn off the trace again.
Cause: The user specified an invalid buffersize for the ddcstrc command.
Action: Ensure that the buffersize used is numeric and greater than or equal to 65536 (64K). Note that the memory to be used will be a multiple of 64K. ddcstrc rounds down the buffersize specified to the nearest multiple of 64K.
Cause: An unexpected error occurred when starting the DB2 security daemon.
Action: Check the db2diag.log file for further information, and then retry the DB2START command.
Cause: DB2VIA support was not started successfully at db2start time. The reason code indicates the error:
Action:
Cause: Either the DEGREE bind option was specified with a value greater than 1 or the SET CURRENT DEGREE statement was executed with a value greater than 1, but the database manager was not enabled for intra-partition parallelism.
The database manager must be started with the intra_parallel configuration parameter set to ON in order for the instance to be enabled for intra-partition parallelism.
The statement or command completed successfully, but the degree specification was ignored.
Action: If you want to use intra-partition parallelism restart the database manager with the intra_parallel configuration parameter set to ON.
Otherwise use a value of 1 or ANY for the degree specification.
sqlcode: +1530
sqlstate: 01623
Cause: During the execution of the SQL statement, a code page conversion operation has resulted in a string that is longer than the maximum size of the target object. Processing continued because only blank characters were truncated.
Action: Ensure that the output is as expected and that the truncation has not caused any unexpected consequences.
sqlcode: 1580
sqlstate: 01004
Cause: There are two situations where this error is issued.
Action: If a clustering index is necessary then alter the table to set append mode off. If append mode is desired, drop the existing clustering index on the table.
sqlcode: -1581
sqlstate: 428CA
Cause: The PAGESIZE value specified in the CREATE TABLESPACE statement does not match the page size of the bufferpool specified for use with the table space. These values must match.
The statement cannot be processed.
Action: Change the value specified for PAGESIZE to match the page size of the bufferpool or change the bufferpool to one that has a page size that matches.
sqlcode: -1582
sqlstate: 428CB
Cause: The PAGESIZE that is specified in the CREATE BUFFERPOOL or CREATE TABLESPACE statement is not a supported page size. The supported page sizes for Version 5 are 4K, 8K, 16K, and 32K.
The statement cannot be processed.
Action: Specify one of the supported page sizes.
sqlcode: -1583
sqlstate: 428DE
Cause: A temporary table space was required to process the statement. There was no temporary table space available that had a page size of "<pagesize>" or larger.
The statement cannot be processed.
Action: Create a temporary table space with a page size of at least "<pagesize>".
sqlcode: -1584
sqlstate: 57055
Cause: Devices (raw i/o) on HP require i/o to be aligned on 1024 byte boundaries. LONG VARCHAR and LONG VARGRAPHIC fields are handled in 512 byte pieces, and thus can only be used in SYSTEM MANAGED TABLESPACEs or in DATABASE MANAGED TABLESPACEs with only FILE containers.
Action: Alternatives:
sqlcode: 1590
sqlstate: 56097