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.
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
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