IBM Books

Messages Reference


SQL1500 - SQL1599



SQL1512N ddcstrc could not write to the specified file.

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.



SQL1513W ddcstrc has not been turned off.

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.



SQL1520N Buffersize must be a numeric value greater than or equal to 65536.

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.



SQL1525N An error occurred when starting the DB2 security daemon.

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.



SQL1526N db2start failed because DB2VIA support was not started. Reason code "<reason code>".

Cause: DB2VIA support was not started successfully at db2start time. The reason code indicates the error:

  1. The VIPL library specified in DB2_VI_VIPL registry variable could not be loaded.

  2. The Device name specified in DB2_VI_DEVICE registry variable could not be opened.

  3. DB2 does not support the VIA implementation installed.

Action:

  1. Make sure the DB2 registry DB2_VI_VIPL is properly set and the name specified in DB2_VI_VIPL is in the %PATH% environment variable.

  2. Make sure the DB2 registry DB2_VI_DEVICE is properly set.

  3. DB2 only supports a VIA implementation that supports at least Reliable Delivery reliability level. It is also required that the VIA implementation complies with Intel Virtual Interface Architecture Implementation Guide and passes the conformance Suite. Make sure the VIA implementation you chose satisfies these requirements.


SQL1530W The specified degree of parallelism will be ignored because the system is not enabled for intra-partition parallelism.

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



SQL1580W Trailing blanks were truncated while performing conversion from codepage "<source>" to codepage "<target>". The maximum size of the target area was "<max-len>". The source string length was "<source-len>" and its hexadecimal representation was "<string>".

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



SQL1581N The table "<table-name>" cannot be in append mode and have a clustering index.

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



SQL1582N The PAGESIZE of the table space "<tbspace-name>" does not match the PAGESIZE of the bufferpool "<bufferpool-name>" associated with the table space.

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



SQL1583N PAGESIZE value "<pagesize>" is not supported.

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



SQL1584N Temporary tablespace with page size of at least "<pagesize>" could not be found.

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



SQL1590N LONG VARCHAR and LONG VARGRAPHIC fields are not permitted in TABLESPACEs which are built on DEVICEs.

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




[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]