DB210000 - DB255499

DB2 Message ID Message Explanation User Response

DB210200I

 All applications must disconnect from the database before the changes become effective.

The ADD or DROP DATALINKS MANAGER command has been successfully processed. However, the change cannot be made effective until all applications have disconnected from the database. After the applications disconnect from the database, the first connection to the database will cause the changes to become effective.

Ensure that all applications disconnect from the database and issue a CONNECT statement.

DB210201I

 Reconcile utility should be run on database tables that contain links to files on the DB2 Data Links Manager. The DB2 Data Links Manager does not perform any unlink processing for these files.

The DROP DATALINKS MANAGER command has been successfully processed. Confirm that no database tables contained links to files on the DB2 Data Links Manager before dropping the DB2 Data Links Manager. If such links exist, they should be removed from the database tables by using the reconcile utility. Note that the files themselves will remain in linked state on the file system. For additional details, see the usage notes for the DROP DATALINKS MANAGER command in the Command Reference.

DB210202E

 Less than number MB of memory is dedicated to your server. No recommendation has been made. The current values match the suggested values.

Because the amount of memory dedicated to the server is so small, the Performance Configuration wizard cannot make a recommendation. Configuration parameters will not be changed.

If you can dedicate more memory to the server, re-run the command with a larger value specified for the option MEM_PERCENT.

DB210203I

 AUTOCONFIGURE completed successfully. Database manager or database configuration values may have been changed if you chose to apply changes. The instance must be restarted before any such applied changes come into effect. You may also want to rebind your packages after the new configuration parameters take effect so that the new values will be used.

The Configuration Advisor has generated its recommendations, and has updated the configuration parameters and buffer pool sizes as requested by the user.

The changes will not take effect until the instance is restarted on the server.

Packages were bound with the old configuration parameters. They need to be rebound, after the new parameters take effect, to exploit these new parameters.

When you are ready to use the new configuration parameters, stop the instance, and then restart the instance. Rebind your packages if necessary

DB210204E

 An error occurred when the Configuration Advisor tried to get system information from your server.

An unexpected error occurred. The Configuration Advisor cannot continue.

Contact your system administrator.

DB210205W

 The Configuration Advisor was unable to increase the sizes of the buffer pools due to other memory requirements determined from your responses. The buffer pool sizes are left unchanged. The use of the suggested set of configuration values may cause paging on the server.

This is a warning that there may not be enough memory dedicated to your server to run the workload that you specified.

Review your input for this command to check that the workload description is appropriate or add more memory to your server.

DB210206W

 The transactions rate you entered is more than ten times the average number of connected applications. If you are using a transaction manager, ignore this message. If not, consider changing the rate.

The Configuration Advisor verifies that the transactions rate is reasonable. The transaction rate may be too high if you are not using a transaction manager.

If you are using a transaction manager, ignore this message. Otherwise, use a lower number of transactions per minute, or increase the average number of connected applications.

DB210207E

 Unable to autoconfigure database-name. Creation of database database-name failed.

An unexpected error occurred. The Configuration Advisor cannot continue, and the database you were trying to create failed.

Try running CREATE DATABASE without the AUTOCONFIGURE option, and then running AUTOCONFIGURE in order to configure your database.

DB210208E

 Cannot autoconfigure databases in EEE system. Creation of database database-name failed.

The AUTOCONFIGURE option is not available for EEE. The database was not created.

Try running CREATE DATABASE without the AUTOCONFIGURE option, and then running AUTOCONFIGURE in order to configure your database.

DB210209I

 The database was created successfully. Please restart the instance so configuration changes take effect.

The Configuration Advisor has updated the database manager configuration parameters, database configuration parameters, and buffer pool sizes in the SYSBUFFERPOOLS catalog.

The changes will not take effect until the instance is stopped on the server.

Packages were bound with the old configuration parameters. They need to be rebound, after the new parameters take effect, to exploit these new parameters.

When you are ready to use the new configuration parameters, stop the instance, and then start the instance. Rebind your packages if necessary.

DB210210E

 The parameter for APPLY is not supported by the Configuration Advisor for this server release.

Only APPLY DB OR DBM or APPLY NONE are valid parameters for the Configuration Advisor for this server release.

Reissue the command using APPLY DB OR DBM or APPLY NONE.

DB210211W

 AUTOCONFIGURE completed successfully, but has only calculated recommendations for the current database partition. You may wish to run AUTOCONFIGURE on all database partitions or propagate these recommendations to all database partitions on your system.

The Configuration Advisor has generated its recommendations, and has updated the configuration parameters and buffer pool sizes as requested by the user for only the current database partition.

The changes will not take effect until the instance is restarted on the server, but should be propagated to other database partitions on this system by running AUTOCONFIGURE for each database partition, or through separate user action.

Packages were bound with the old configuration parameters. They need to be rebound, after the new parameters take effect, to exploit these new parameters.

When you are ready to use the new configuration parameters, stop the instance, and then start the instance. Rebind your packages if necessary.

DB210212W

 The recommendations made by the Configuration Advisor require a greater percentage of memory than that specified. No recommendation has been made. The current values match the suggested values.

There is not enough memory available to be allocated for the recommendations made by the Configuration Advisor.

Resubmit the command, specifying a greater percentage of memory.

DB210213W

 The recommended number of disks for the specified inputs exceeds the number available. No recommendation has been made. The current values match the suggested values.

There are not enough disks available for the recommendations made by the Performance Configuration Wizard.

Resubmit the command once there are more disks available.

DB210214W

 The recommended amount of memory for the specified inputs exceeds the amount available. No recommendation has been made. The current values match the suggested values.

There is not enough memory available to be allocated for the recommendations made by the Configuration Advisor.

Resubmit the command either with different input values or once a greater amount of memory is available.

DB210215W

 The Configuration Advisor was unable to assign a minimum amount of memory to the buffer pools due to other memory requirements determined from your responses.

The Configuration Advisor is unable to provide a set of recommendations based on the specified database requirement with the specified memory resource.

Increase the percentage of physical memory allocated, if more memory resource is available. Otherwise, increase the amount of physical memory on the server.

DB210220E

 The command number specified is not valid.

An invalid command number was specified for the EDIT or RUNCMD command. This command number does not exist in the current CLP interactive mode command history.

Run the HISTORY command to see a list of valid command numbers and resubmit the EDIT or RUNCMD command specifying a valid command number.

DB210221E

 The editor editor could not be launched.

An invalid editor was specified for the EDIT command. This editor either does not exist or it is not contained in the PATH.
The editor used in the EDIT command is decided in the following order:
  • by using the value of the EDITOR parameter in the EDIT command, if it was specified
  • by using the value of the DB2_CLP_EDITOR registry variable, if it was set
  • by using the value of the VISUAL environmental variable, if it was set
  • by using the value of the EDITOR environmental variable, if it was set.
Specify a valid editor contained in the PATH in the EDITOR parameter of the EDIT command or in the appropriate registry/environmental variable.

DB210222E

 The value specified for parameter is not in the valid range of number and number.

An invalid value was specified for parameter. This value does not lie within the valid range of number and number.

Refer to the appropriate documentation to find out the valid range for parameter and resubmit the command specifying a valid value.

DB210223E

 The command command can only be run in the CLP's interactive mode.

An attempt was made to run a DB2 command in either CLP's command or batch mode, but this command can only be run in CLP's interactive mode.

Reissue the same command within the CLP's interactive mode.

DB216001I

 The DECOMPOSE XML DOCUMENTS command successfully decomposed all documents. The number of documents requested was number-requested.

No errors were encountered during the execution of this command.

No user action is required.

DB216002W

 One or more documents could not be decomposed. The number of documents successfully decomposed was number-successful. The number of documents attempted was number-attempted.

Error conditions prevented one or more documents from being decomposed. For more details on the status of each document, refer to messages file specified by the MESSAGES parameter.

To decompose the XML documents that were not successfully decomposed:

  1. Review the error message information in the file specified by the MESSAGES parameter. If necessary, see the db2diag log file for more details about each error. The pertinent entries in the db2diag log file are identified by the document ID.
  2. Correct the errors described in the error messages file.
  3. Issue the DECOMPOSE XML DOCUMENTS command again, as follows:
    • If you specified a positive COMMITCOUNT value, reissue the command only for the documents that were not successfully decomposed.
    • If you specified a COMMITCOUNT value of 0, use one of the following options:
      • Perform a rollback, and then reissue the command for all the documents.
      • Commit the changes, and then reissue the command only for the documents that were not successfully decomposed.

DB216500W

 Unable to autoconfigure database_name. The database was created successfully, but it might not be optimally configured.

Although the database was created successfully, it might not be optimally configured, because an unexpected error occurred and the Configuration Advisor cannot continue.

Configure your database by running the AUTOCONFIGURE command.

DB216501W

 There is more than one database on your system, and if more than one database is active at the same time, database database_name might not be optimally configured.

There is more than one database on your system. The percentage of instance memory that is assigned to the database_name database is mem_percent_value, but if more than one database is active at the same time, the memory allotment might not be optimal.

Configure your databases by running the AUTOCONFIGURE command with the MEM_PERCENT input keyword.

DB216502E

 The statement was not processed because the extended index index-id of table table-id in tbspace-id is incompatible with the current level of the database manager.

The statement tried to update the extended index index-id when accessing the table table-id in tbspace-id, and the extended index is incompatible with the current level of the database manager. The statement cannot be processed.

Drop the extended index, create it again and retry the statement.

To determine the index name, use the following query:

SELECT IID, INDSCHEMA, INDNAME FROM SYSCAT.INDEXES AS I, SYSCAT.TABLES AS T WHERE IID = index-id AND TABLEID = table-id AND TBSPACEID = tbspace-id AND T.TBASCHEMA = I.TABSCHEMA AND T.TABNAME = I.TABNAME

DB250000I

 The command completed successfully.

The Command Line Processor Plus command completed successfully.

No action is required.

DB250001I

 CLPPlus has successfully read the configuration file named configuration-file-name.

When the DB2DSDRIVER_CFG_PATH environment variable is set, or when the path to the configuration file is found automatically by Command Line Processor Plus (CLPPlus), CLPPlus will read the configuration file during a connect attempt. This message is only displayed when verbose is set to on using the CLPPLUS command.

No user response is required.

DB250002E

 CLPPlus failed to read the configuration file named configuration-file-name in the directory named directory.

During a connect attempt, Command Line Processor Plus (CLPPlus) failed to read the configuration file specified by the DB2DSDRIVER_CFG_PATH environment variable.

Verify that the information in the configuration file is correct by performing the following steps:

  • Verify that the path to the configuation file matches what is specified by the DB2DSDRIVER_CFG_PATH environment variable.
  • Verify that the name of the configuation file matches what is specified by the DB2DSDRIVER_CFG_PATH environment variable.

DB250003E

 Could not find a DSN alias named dsn-alias-name in the configuration file named configuration-file-name. dsn-alias-name will be used as the database name in the subsequent interactive connect attempt.

When a DSN alias name specified during a connect attempt is not found in the configuration file read by CLPPlus, the DSN alias name is used as a database name in the subsequent interactive CLPPlus connect attempt. All other values for the connect must be specified by the user.

Continue with the interactive connect. You can also check the contents of the configuration file and use an existing DSN alias or create one for future use.

DB250004E

 The connection failed because an empty string was specified for the value for the database name.

Command Line Processor Plus (CLPPlus) requires you provide a valid database name when prompted. Entering an empty string for a database name is not allowed.

When prompted to retry the connection attempt, specify a valid database name.

DB250005E

 The command failed because the command is applicable only in a spawned console window.

A specific command, meant only for use in the spawned console window, was issued in the current console window.

Use only supported Command Line Processor Plus (CLPPlus) commands in the current console window.

DB250006E

 Command Line Processor Plus (CLPPlus) failed to start.

The default invocation of CLPPlus on Linux and Unix requires XServer running on your desktop.

Verify that the DISPLAY environment variable is set properly. Or, you can start a command line version of CLPPlus using the CLPPLUS command with the -nw option.

DB250007I

 CLPPlus canceled processing the current SQL statement due to a user initiated interrupt.

The current SQL statement being processed by CLPPlus has been canceled. A user interrupt initiated the cancel request.

If this was intentional then no response is required. If this was unintentional, reissue the canceled SQL statement.

DB250008E

 The CLPPlus command failed because the shell or environment variable with name variable-name could not be found.

A CLPPlus command can include embedded shell or environment variables. If the variable embedded in your CLPPlus command is not defined in the operating system the command fails.

You can:

  • Remove the reference to the variable and issue the command.
  • Define the variable and issue the command.

DB250009E

 The IMPORT CLPPlus command failed because the SKIPCOUNT value n is greater than the total number of rows in the import file.

The IMPORT CLPPlus command was run with the SKIPCOUNT option. The value specified for SKIPCOUNT exceeds the number of rows in the import file read. No rows were imported.

You can:

  • reset the SKIPCOUNT to a value less than the number of rows in the import file by using the SET CLPPlus command and retry IMPORT.
  • remove the SKIPCOUNT option and retry IMPORT.

DB250010E

 The explain facility failed due to an error on the database server.

When AUTOTRACE is set to ON in CLPPlus, and a select statement is run on an Informix database server, CLPPlus implicitly tries to set explain to on. SET EXPLAIN ON failed on the Informix database server and the statement failed.

Check with your Informix database administrator for the reason why SET EXPLAIN ON failed. Retry after resolving the error.

DB250011E

 Explain failed to generate data for the issued statement.

When AUTOTRACE is set to ON in CLPPlus, and an SQL statement is run on an Informix database server, the explain plan is only generated for SELECT statements. A statement other than a SELECT statement was issued.

Retry with valid SELECT statement.

DB250012E

 CLPPlus failed to process explain data.

When AUTOTRACE is set to ON in CLPPlus, and an SQL statement is run on an Informix database server, CLPPlus is unable to parse the explain plan data generated in XML format.

None

DB250013E

 A CLPPlus connection failed because security mechanism security-mechanism specified for DSN alias dsn-alias in the db2dsdriver.cfg file is not supported by CLPPlus.

The security mechanism specified for a DSN alias in the db2dsdriver.cfg file is not supported in CLPPlus. Any connection attempt using this DSN alias fails and is terminated.

You can:

  • specify a valid CLPPlus security mechanism in the db2dsdriver.cfg file for the applicable DSN alias and retry.
  • remove the security mechanism parameter for the applicable DSN Alias from the db2dsdriver.cfg file and retry.

DB250014I

 DSN alias dsn-alias is not found in the configuration file named config-file.

A DSN alias specified during a connect attempt is not found in the dsdriver configuration file read by CLPPlus. CLPPlus continues to search the LDAP Directory server configured by the user for that DSN alias.

None required. CLPPlus continues to search in the LDAP directory server for an entry named dsn-alias.

DB250015I

 CLPPlus successfully established a connection with LDAP directory server LDAP-server.

Connection information for an LDAP directory server was found in the dsdriver configuration file and a successful connection was established with that LDAP server during a CLPPlus connect attempt.

None

DB250016E

 DSN alias dsn_alias was not found in LDAP directory server LDAP-server. dsn_alias is used as the database name in the subsequent interactive CLPPlus connect attempt.

The DSN Alias name specified during a CLPPlus connect attempt is not found in LDAP directory server. The DSN alias name is treated as database name in the subsequent interactive connect attempt. All other required values for the connection must be specified interactively.

You can:

  • continue with the interactive connect attempt.
  • use an existing DSN alias name and retry the connect attempt.
  • create the DSN alias that was not found and retry the connect attempt.

DB250017E

 CLPPlus failed to establish a connection with the following LDAP directory server: LDAP-server. The following alias was used as the database name in an interactive connect attempt: dsn-alias.

CLPPlus failed to establish a connection with an LDAP directory server. The DSN Alias name used during the initial connect attempt will be treated as the database name in a subsequent interactive connect attempt. All other required values for the connection are specified interactively.

Respond to this message in one of the following ways:

  • Continue with interactive connect.
  • Verify and correct the LDAP directory server configuration in the db2dsdriver.cfg file, and retry the connection.
  • Check with the LDAP administration to ensure the LDAP directory server is running and retry the connection.

DB250018E

 A connection attempt during the CLPPlus environment start sequence failed. The CLPPlus environment failed to start.

During the CLPPlus environment start sequence, an option to connect to a database is available. If the database connection attempt fails, the CLPPlus start sequence stops and exits.

The reason for the database connection failure is captured by an accompanying JCC error.

Check the accompanying JCC error code and rerun the CLPPLUS command with valid database connection string parameters.

DB250019E

 The EDIT Command Line Processor Plus (CLPPlus) command failed. The editor specified with the define_editor command is not valid.

You can set an editor with the define_editor CLPPlus command. When you run the EDIT command, the editor specified with the define_editor command is started. This error is returned if the editor you specified with the define_editor command is not valid for your environment. The EDIT command failed.

Retry the EDIT command after you specify a valid editor for your environment with the define_editor command.

DB250020E

 The encoding property of the CLPPlus session was not changed because the specified encoding format value is not a valid encoding format. Specified encoding format: encoding-format.

You can use the SET ENCODING command to control how characters are converted in the CLPPlus console. Invalid encoding format was specified with the SET ENCODING command in the CLPPlus session.

Issue the SET ENCODING command again with a valid encoding format.

DB250021E

 Message text was not found for the following message: message-ID.

This message is returned when the CLPPlus utility is unable to retrieve text for an error message. The CLPPlus utility might be unable to retrieve message text for few, vary unusual reasons, such as if language-related components of the product were not installed, or have been moved.

Reinstall components of the product related to languages.

DB250022E

 A CALL statement with array parameters that was issued from the CLPPlus environment failed because the use of array parameter is not supported by the CLPPlus environment with the database server.

You can specify array parameters in a CALL statement only when you are connected to the DB2 for Linux, UNIX, and Windows server. This message is returned when a CALL statement with array parameters is issued from the CLPPlus environment to a database other than DB2 for Linux, UNIX and Windows.

Modify your application to avoid calling a routine with array parameters.

DB250100E

 The command text is not a valid CLPPlus command.

The text entered is not a valid Command Line Processor Plus (CLPPlus) command.

Specify a valid command. Refer to the documentation if required for a list of valid commands.

DB250101E

 The command syntax is invalid. An unexpected token token was found following text. Expected values include: token-list.

A syntax error in the command string was detected at the specified token following the text. The text field indicates the 20 characters of the input command string that preceded the token that is not valid.

As an aid, when possible, a partial list of valid tokens is provided in the token-list. This list assumes the statement is correct to that point. If the valid values would be unknown user inputs, token-list might be blank.

The command cannot be processed.

Refer to the documentation of the command to identify the valid command syntax.

Examine and correct the command in the area of the specified token. Issue the command again.

DB250102E

 The command syntax is invalid. The value of command parameter parameter-name of type type is invalid. Valid values include: token-list.

The command syntax is invalid. A command parameter parameter-name is of an invalid data type.

The command cannot be processed.

Examine and correct the parameter value the area of the specified token. Issue the command again.

DB250103E

 The command syntax is invalid. The value of command parameter parameter-name is out of range. The valid range is lower-bound to upper-bound, inclusive.

This message is returned when a value for a parameter is specified that is out of range for that parameter. The token parameter-name indicates the parameter for which an out of rage value was specified.

Issue the command again, specifying a value for the named parameter that is in the given range.

DB250104E

 The command is not supported for the database-server data server.

The command is not supported for specified data server. The command failed.

The command cannot be processed.

Refer to the documentation for the supported commands for the current data server.

DB250105W

 The CLPPlus command SET LOCALE failed because the locale locale is not valid or not supported in the CLPPlus environment.

The CLPPlus environment, by default, sets the locale with the value set in the operating system. You can also set or change the locale used by the CLPPlus environment with the SET LOCALE CLPPlus command.

The SET LOCALE command specified a locale that is not valid or not supported in the CLPPlus environment. The SET LOCALE command failed and the CLPPlus environment continues to use the last valid locale setting.

Specify a valid and supported locale and run the command again.

DB250200E

 The feature feature-name can not be enabled because the feature does not exist in the current installation.

The feature name feature-name is not valid. For valid feature names, search the documentation.

Specify a valid feature name, then try the request again.

DB250201E

 No database connection exists, but a database connection is required.

A database connection is required to issue the command. There is no database connection.

Establish a database connection using the clpplus command and try again.

DB250202E

 Connections to databases of type database-type are not supported by this feature.

The database type is not valid. For valid database types, refer to the documentation.

Specify the name of a database of a valid database type, then try the request again.

DB250203E

 Connection failed to be established.

An attempt to establish a database connection failed. No database connection exists.

Possible reasons include:

  • Invalid user-name
  • Invalid password
  • Invalid hostname
  • Invalid database name
  • Invalid port number

If explicitly connecting to a database, verify and correct the command syntax and try again. Otherwise try again and if the connection still cannot be established, contact your database administrator.

DB250204E

 An attempt to locate a file filename failed. The command cannot be processed.

A required file filename could not be located. Possible reasons include:

  • Invalid file name
  • Invalid file path
  • File not in the file path
  • Permissions on file or path do not allow reading of files
  • Verify that the file name is correct and that the file exists in the specified location.
  • Verify that the permissions on the file path and file allow read access of files.

DB250205E

 Attempt to read file file-name failed.

An attempt to read the file parameter file-name failed. Possible reasons include:

  • Invalid permissions on the file system.

The command cannot be processed.

If the file is a user-defined file, verify that the file permissions allow the file to be read.

DB250206E

 env-variable-name is not a defined environment variable.

The name env-variable-name is not a defined Command Line Processor Plus (CLPPlus) environment variable name or the variable is not set to a required value.

Verify and correct the command syntax, specify a valid environment variable name, and reissue the command or verify and set, if needed, the following CLPPlus environment variables set to required values:

On Windows operating systems:

   Variable:  CLPPLUS_HELP   Value: sqllib/bin/clpplus.bat

On UNIX operating systems:

   Variable:  CLPPLUS_HELP   Value: sqllib\bin\clpplus.sh

DB250207E

 Attempt to create file filename failed.

The required file filename could not be created. Possible reasons include:

  • File already exists
  • Invalid filename
  • Invalid file path
  • Invalid permissions on the file system
  • Insufficient memory in the file system

If the file is a user-defined file, verify and correct the filename or filepath, verify that the path is valid, verify that files can be written to the path, and that there is sufficient memory. If the file is a system-generated file, re-issue the command - if the command still fails, contact your database administrator.

DB250208E

 Invalid command sequence. A prerequisite command must be issued before this command. A possible prerequisite command is prereq-command.

For some CLPPlus commands, there is a prerequisite that one or more other CLPPlus commands be issued first. If the prerequisite commands are not issued, the current command cannot be issued.

The command has not been processed.

Issue the recommended prerequisite command, then reissue the current command. For more information about the command, see the CLPPlus documentation.

DB250209I

 A connection has been established. Database type: product-name. Database version: version. Host name: hostname. Port: port-number. Database name: database-name. User: auth-id.

A database connection has been established to a database of type: product-name of version: version. The host name of the database server is hostname. The port number is port-number. The name of the database is database-name. The authorization ID of the user is auth-id.

Database commands can now be issued for this database.

Queries and database operations can now be executed for this database.

Command Line Processor Plus (CLPPlus) commands that require a connection can be executed until the connection is closed or reset.

Proceed with using CLPPlus. Issue CLPPlus commands, database queries and operations.

DB250210I

 The connection to database database-name has been closed.

The connection to database database-name has been closed. No database communications can be made at this time.

To execute database operations or to issue commands that require a database connection, re-establish a database connection by issuing the CLPPLUS command.

DB250211E

 The database object named object-name was not found in the database.

You can list packages or tables that were created by the current user in the database by issuing the LIST PACKAGES command or the LIST TABLES command.

You can retrieve meta-data information about database objects such as tables, views, functions, and others by issuing the DESCRIBE command, and specifying the database object by name.

This message is returned when either the LIST command or DESCRIBE command is issued for a specified database object, and that object cannot be found in the database.

If this message was returned when the LIST command was issued, it is possible that the database object being searched for was created by a user other than the current user. By default, the LIST command lists only those database objects that were created by the current user.

Verify that the database object exists, and was created by the current user.

DB250212E

 The database object named object-name with type type was not found in the database.

You can retrieve meta-data information about database objects such as tables, views, functions, and others by issuing the DESCRIBE command, and specifying the database object by name.

This message is returned when the DESCRIBE command is issued for a specified database object, and that object cannot be found in the database.

Verify that the database object exists, and was created by the current user.

DB250300E

 An unexpected SQL error occurred while disconnecting from a database.

An SQL error occurred while committing data or closing a database connection for which no further information is available.

If required, re-establish a connection to the database before performing further database operations.

DB250301E

 An unexpected SQL error occurred while processing a Command Line Processor Plus command.

An unexpected SQL related error occurred on the data server which has interrupted the processing of the Command Line Processor Plus command. The command execution has not completed.

Reissue the command.

DB250302E

 An asynchronous notification notification-name received from the data server process with process ID (PID) process-id.

An asynchronous notification from the data server occurred with name notification-name and process ID process-id might require your immediate attention.

Using the process ID value, look up the process and related notification. Respond to any urgent requirements if required. Command Line Processor Plus is still active.

DB250303E

 The Command line processor plus line buffer size is less than the size of column column-name.

Column values cannot be displayed, because the Command line processor plus line buffer size is less than the size of column column-name. The column values would be truncated.

Specify a line buffer width that is greater than the column width and then issue the command or execute the SQL buffer again.

DB250400E

 The buffer line number is invalid. Valid values can be between min-value and max-value.

The command attempts to operate on a line in the buffer and the buffer line number provided is invalid. The line number could be wrong because there are no lines in the buffer or because the line number is out of range for the buffer. It is either less than ''min-value'' or greater than ''max-value''.

Re-submit the command with a valid line number.

DB250401E

 Spooling cannot be turned off because it is already off.

The SPOOLING OFF command has already been processed. The command cannot be processed.

Because the command is already processed, no further action is required.

DB250402E

 The command or statement terminator value is invalid.

The SQL terminator must be exactly one character long.

Set the terminator character to a single character value.

DB250403E

 The input string string specified in the CHANGE command was not found in the SQL buffer.

To successfully issue the CHANGE command the input string must be found in the SQL buffer and the input string string was not found.

Re-submit the command with valid argument(s).

DB250405E

 The DESCRIBE command does not support objects of type object-type. Valid types include token-list.

The DESCRIBE command can be used to access the definitions of a sub-set of database object types in a database. The object type object-type is not supported. Valid objects include those in token-list.

Refer to the DESCRIBE command documentation for a list of valid database object types. Specify the name of a supported database object and try again.

DB250406E

 The database object name of type object does not contain columns.

The issued command requires the specification of a database object that contains columns. Valid objects include:

  • tables
  • views
  • catalog tables
  • catalog views

The specified object did not contain any columns.

Specify the name of a database object that contains columns.

DB250407E

 The separator character character is invalid.

The character character specified as a separator character is invalid. Its use is not compatible with the use of the quotation mark character within the command syntax.

Do the following:

  1. Specify a different separator character or terminator character.
  2. Verify and correct the command syntax.
  3. Reissue the command.

DB250408E

 No user substitution variables are defined.

A user substitution variable was referenced, but no user substitution variables are defined.

The command cannot be processed.

Define a user substitution variable and try again.

DB250409E

 The command cannot be executed when the SQL buffer is empty.

The command cannot be issued when there is no data in the SQL buffer.

Add statements to the SQL buffer and re-submit the command.

DB250410I

 The Command Line Processor Plus is currently paused with the pause value set to pause-text.

The PAUSE command was previously issued with the pause text pause-text. To exit the paused state initiated by the PAUSE command, the enter key must be pressed.

Press enter to exit the paused state.

DB250411E

 The data type, type, of the column named column-name is not supported for this computation function.

The data type of the named column is not supported for the computation function specified in the COMPUTE command.

Valid numeric data type include the following:

  • SMALLINT
  • LONG
  • DOUBLE
  • FLOAT
  • DECIMAL
  • INTEGER

Specify a column of a valid data type as an argument to the function.

DB250412E

 No defined computations are available to be displayed.

No computations have been defined using the COMPUTE command.

If you want to calculate and display compute information, issue the COMPUTE command at least once and then issue the SHOW COMPUTE command.

DB250413E

 A compute with label label is already defined.

A compute with the name label is already defined for the column.

Define the computation using a different name or modify the computation so that it specifies a different column.

DB250414I

 There are no columns defined.

You can list the columns that have been defined by issuing the SHOW COLUMN command or by issuing the COLUMN command with no parameters.

This message is returned when the SHOW COLUMN command is issued, or when the COLUMN command is issued with no parameters, and there are no columns to display.

You do not need to respond to this message.

DB250415W

 No breakpoints were cleared, because there are no breakpoints defined for the specified column.

You can clear any breakpoints that have been defined for a column by issuing the CLEAR BREAK command, specifying the column name.

This message is returned when the CLEAR BREAK command has been issued for a specified column, and no breakpoints were defined for that column.

You do not need to respond to this message.

DB250416W

 There were no compute actions defined for the column named column-name to clear.

You can clear all the compute actions that have been defined for a given column by issuing the CLEAR COMPUTES command, specifying the column from which to clear the compute actions.

This message is returned when no compute actions have been defined for the specified column.

You do not need to respond to this message.

DB250417E

 The following function, specified in the COMPUTE command, is not a supported function for a compute action: function.

You can use the COMPUTE command to define a compute action to be performed for a given column when a breakpoint for that column is reached.

The syntax of the COMPUTE command is:

COMPUTE <function-1> LABEL <label-1> 
     OF <column-1>
        [{, <function-2> LABEL <label-2> 
            OF <column-2>} ...]
     ON <column-n>

where <function> can be one of:

[ SUM | MAX | MIN | AVG | COUNT | NUM ]

This message is returned when an invalid value for <function> is specified.

Issue the COMPUTE command again, specifying a valid function.

DB250418W

 The specified compute action was previously defined.

The COMPUTE command is used with the BREAK command. You can define a breakpoint for a specified column by issuing the BREAK command. You can use the COMPUTE command to define a compute action to apply to the specified column when a breakpoint for that column is reached during the execution of a SQL statement. A compute action is a function such as SUM, COUNT, or MAX that is applied to all elements of the column.

This message is returned when the COMPUTE command is issued to define a compute action for a column that is identical to a compute action that was previously defined for that column.

You do not need to respond to this message.

DB250419W

 The SQL buffer is empty.

As you issue CLPPlus commands, such as COMPUTE, and BREAK, the resulting objects and actions are stored in the SQL buffer.

Here is a list of just some of the actions that you can perform on a SQL buffer:

  • You can edit the contents of the SQL buffer by issuing the EDIT command.
  • You can append to the contents of the SQL buffer by issuing the APPEND command.
  • You can clear the contents of the SQL buffer by issuing the CLEAR command.

When a SQL statement is executed, the contents of that SQL buffer affect the exectution. For example, breakpoints and compute actions have been defined for a column, they will take effect when the SQL statement is run.

This message is returned when an attempt is made to act on the SQL buffer, but the SQL buffer is empty.

You do not need to respond to this message.

DB250420E

 Creation of a new bind variable failed because a bind variable already exists with the specified name.

You can create bind variables to contain values, and use those bind variables in SQL statements.

The scope of bind variables is the database session. After you connect to a database, you can create and use bind variables for the duration of that database session. When you disconnect from the database, those bind variables cease to exist.

You can create bind variables using the following syntax:

VARIABLE <bind-variable-name> <data-type>

This message is returned when an attempt is made to create a new bind variable, specifying the same name for that new variables as the name of a bind variable that already exists.

To create a new bind variable, issue the VARIABLE command again, specifying a name that is not the same as the name of any existing bind variable.

DB250421I

 There are no breakpoints defined.

You can list breakpoints that have been defined by issuing the BREAK command with no parameters.

This message is returned when the BREAK command is issued with no parameters, and there are no breakpoints to display.

You do not need to respond to this message.

DB250422W

 No columns were cleared, because there are no columns defined.

You can clear any columns that have been defined by issuing the CLEAR COLUMN command.

This message is returned when the CLEAR COLUMN command has been issued, and no columns were defined.

You do not need to respond to this message.

DB250500W

 An error occurred during the initialization of the CLPPlus terminal. However, processing can continue.

This message is returned when an internal error occurs while the CLPPlus terminal is being initialized. The initialization did not fail, and you can proceed with CLPPlus commands.

You do not have to respond to this message.

DB250501E

 Column with name column-name is not defined.

The column column-name specified is not defined.

Define the column and retry the command, or retry the command with a defined column.

DB250502E

 The name name is too long. The maximum length is maximum-length.

The length of the name specified is too long.

Retry the command with a name shorter than the maximum length specified.

DB250503E

 No format and display attributes found for column column-name.

The specified column does not have any format or display attributes set.

Using the COLUMN command, define any required format and display attributes for the column and retry the command.

DB250504E

 The ACCEPT command failed to accept the value for the substitution variable substitution-variable after three consecutive input value format errors.

The value of the substitution variable does not conform to the format specified in the ACCEPT command. Users are prompted to retry the command with a suitable substitution variable until three consecutive attempts have failed. The ACCEPT command has failed.

Ensure the substitution variable has a value that conforms to the format specified in the ACCEPT command and retry the ACCEPT command.

DB250505E

 Error fetching server output messages.

Server side procedures can have output messages. When you ask to print these messages on the client console, using the 'set serveroutput on' command, CLPPlus attempts to retrieve the server output messages from the server after the procedure has run.

An error has occurred when retrieving these server output messages.

Check the server-side db2diag.log for any associated errors.

DB250506E

 A column with alias name column-alias is already defined.

An alias name column-alias already exists for the column.

User reponse

Retry the command with a unique alias name.

DB250507I

 No errors found.

The Command Line Processor Plus command (CLPPlus) SHOW ERRORS returned successfully and found no errors.

No user response is required.

DB250508I

 No errors found for procedure-name.

The Command Line Processor Plus command (CLPPlus) SHOW ERROR returned no errors for the procedure procedure-name.

No user response is required.

DB250601E

 The SQL statement could not be executed because the following bind variable is used in the SQL statement, but does not exist: bind-variable-name.

You can create bind variables to contain values, and use those bind variables in SQL statements.

The scope of bind variables is the database session. After you connect to a database, you can create and use bind variables for the duration of that database session. When you disconnect from the database, those bind variables cease to exist.

You can create bind variables using the following syntax:

VARIABLE <bind-variable-name> <data-type>

You can use bind variables in SQL statements like this:

DELETE employee WHERE  empno = :id;

where ":id" is a bind variable.

This message is returned when an attempt is made to execute a SQL statement that contains a bind variable that has not been defined.

Respond to this message in one of the following ways:

  • Define the variable that was used in the SQL statement, and then attempt to execute the SQL statement again.
  • Attempt to execute the SQL statement again, specifying a bind variable that is defined.

DB255000I

 The RDF utilities were unable to sort the RDF triples.
  • You need to have access to the SORT command on Linux and UNIX operating systems.
  • You need to have the Cygwin program installed on the Windows operating system.

Ensure you have the proper permission or application installed for your operating system. Then attempt the operation again.

DB255001E

 The SPARQL query failed because an unexpected database error occurred while the query was being processed. Query: query-details. SQLCODE: sqlcode. SQLSTATE: sqlstate.

You can take advantage of the Resource Description Framework (RDF) by using RDF utility commands such as createRdfStore. You can query RDF data that is stored in databases using the SPARQL query language.

This message is returned when an attempt is made to query RDF data that is stored in a database, but an error was encountered while the query was being processed.

To assist with troubleshooting, the underlying database error code is included in the runtime token sqlcode. More diagnostic information can be found in the db2diag diagnostic log files. The runtime token sqlstate might sometimes be empty because not all SQL errors have an associated sqlstate.

Respond to this error by performing the following troubleshooting steps:

  1. Search in the db2diag log files for the sqlcode and sqlstate given in the runtime tokens sqlcode and sqlstate.
  2. Examine the underlying database error message.
  3. Take corrective actions to fix the error.
  4. Execute the SPARQL query again.

DB255002E

 Creation of an RDF store failed because an unexpected database error occurred while the underlying database objects were being created. SQLCODE: sqlcode. SQLSTATE: sqlstate.

You can take advantage of the Resource Description Framework (RDF) by using RDF utility commands such as createrdfstore. You can query RDF data that is stored in databases using the SPARQL query language.

This message is returned when an attempt is made to create a new RDF data store, but an error was encountered while the store was being created.

To assist with troubleshooting, the underlying database error code is included in the runtime token sqlcode. More diagnostic information can be found in the db2diag diagnostic log files. The runtime token sqlstate might sometimes be empty because not all SQL errors have an associated sqlstate.

Respond to this error by performing the following troubleshooting steps:

  1. Search in the db2diag log files for the sqlcode and sqlstate given in the runtime tokens sqlcode and sqlstate.
  2. Examine the underlying database error message.
  3. Take corrective actions to fix the error.
  4. Run the RDF command again to create the new RDF store.

DB255003E

 Dropping an RDF store failed because an unexpected database error occurred while the underlying database objects were being removed. SQLCODE: sqlcode. SQLSTATE: sqlstate.

You can take advantage of the Resource Description Framework (RDF) by using RDF utility commands such as createrdfstore. You can query RDF data that is stored in databases using the SPARQL query language.

This message is returned when an attempt is made to drop an existing RDF store from a database, but an error was encountered while the underlying tables and other database objects were being dropped and cleaned up.

To assist with troubleshooting, the underlying database error code is included in the runtime token sqlcode. More diagnostic information can be found in the db2diag diagnostic log files. The runtime token sqlstate might sometimes be empty because not all SQL errors have an associated sqlstate.

Respond to this error by performing the following troubleshooting steps:

  1. Search in the db2diag log files for the sqlcode and sqlstate given in the runtime tokens sqlcode and sqlstate.
  2. Examine the underlying database error message.
  3. Take corrective actions to fix the error.
  4. Call the droprdfstore command to drop the RDF store.

DB255004E

 Updating the statistics for an RDF store failed because an unexpected database error occurred during the operation. SQLCODE: sqlcode. SQLSTATE: sqlstate.

You can take advantage of the Resource Description Framework (RDF) by using RDF utility commands such as createrdfstore. You can query RDF data that is stored in databases using the SPARQL query language.

This message is returned when an attempt is made to update the statistics for an RDF store in a database, but an error was encountered while the statistics for the underlying database objects were being updated.

To assist with troubleshooting, the underlying database error code is included in the runtime token sqlcode. More diagnostic information can be found in the db2diag diagnostic log files. The runtime token sqlstate might sometimes be empty because not all SQL errors have an associated sqlstate.

Respond to this error by performing the following troubleshooting steps:

  1. Search in the db2diag log files for the sqlcode and sqlstate given in the runtime tokens sqlcode and sqlstate.
  2. Examine the underlying database error message.
  3. Take corrective actions to fix the error.
  4. Run the statistics updates RDF operation again.

DB255005E

 Reorganizing an RDF store failed because an unexpected database error occurred during the operation. SQLCODE: sqlcode. SQLSTATE: sqlstate. Reason code: reason-code.

You can take advantage of the Resource Description Framework (RDF) by using RDF utility commands such as createrdfstore. You can query RDF data that is stored in databases using the SPARQL query language.

To create tables optimized for an RDF store, you can reorganize the RDF store. Reorganizing an RDF store involves three steps, and this message can be returned when the reorganization operation fails in one of these three steps. The runtime token reason-code indicates which steps the reorganization operation failed:

1

Identifying whether the RDF store needs to be reorganized using the reorgcheckrdfstore command.

2

Creating tables and scripts to prepare to reorganize the RDF data using the reorgrdfstore command.

3

Transferring the RDF data into the new, optimized tables using the reorgcomplete command.

To assist with troubleshooting, the underlying database error code is included in the runtime token sqlcode. More diagnostic information can be found in the db2diag diagnostic log files. The runtime token sqlstate might sometimes be empty because not all SQL errors have an associated sqlstate.

Respond to this error by performing the following troubleshooting steps:

  1. Search in the db2diag log files for the sqlcode and sqlstate given in the runtime tokens sqlcode and sqlstate.
  2. Examine the underlying database error message.
  3. Take corrective actions to fix the error.
  4. Execute the reorganization operation again.

DB255006E

 Updating data in an RDF store failed because an unexpected database error occurred during the operation. SQLCODE: sqlcode. SQLSTATE: sqlstate.

You can take advantage of the Resource Description Framework (RDF) by using RDF utility commands such as createrdfstore. You can query RDF data that is stored in databases using the SPARQL query language.

This message is returned when an attempt is made to update data in an RDF store in a database, but an error was encountered while the operation was being processed.

To assist with troubleshooting, the underlying database error code is included in the runtime token sqlcode. More diagnostic information can be found in the db2diag diagnostic log files. The runtime token sqlstate might sometimes be empty because not all SQL errors have an associated sqlstate.

Respond to this error by performing the following troubleshooting steps:

  1. Search in the db2diag log files for the sqlcode and sqlstate given in the runtime tokens sqlcode and sqlstate.
  2. Examine the underlying database error message.
  3. Take corrective actions to fix the error.
  4. Execute the RDF command again.

DB255007E

 Creation of an RDF store failed because the current user id does not have the required authority or privileges to create objects in the specified schema. Schema name: schema-name. Reason code: reason-code.

The following privileges are required to create an RDF store:

  • CREATETAB permission to create tables in a schema.
  • CREATE_EXTERNAL_ROUTINE permission to create external functions.

The reason code indicates the type of object that was being created:

1

Table

2

External function

Assign the proper privilege to the user. Then issue the command again.

DB255008E

 Creation of an RDF store failed because the page size of the table spaces in the specified schema is too small.

An RDF store requires a table space with a page size of 32 KB to successfully create all the columns.

Create a table-space with 32 KB page size. Then use it to create the RDF store.

DB255009E

 Creation of an RDF store failed because an RDF store with the specified name already exists in the specified schema. Specified RDF store name: store-name. Schema name: schema-name.

There is a naming conflict for the RDF store you are attempting to create.

Use a different name to create the RDF store.

DB255010E

 The RDF operation failed because the current user id does not have SELECT privileges on a required RDF store table. RDF store name: store-name. Table name: table-name.

The necessary read permission for the RDF store metadata table is missing.

Ensure user has CONNECT and READ authority for the RDF store.

DB255011E

 Creation of an RDF store failed. The RDF utility was unable to create a required table for the new RDF store because a table with the same name already exists in the schema. Table name: table-name. Schema name: schema-name.

One or more tables failed to create successfully due to a naming conflict.
  1. Rename existing tables which are causing the conflict.
  2. Edit objectnames file and provide a different physical name for the tables which are causing the conflict.

DB255012E

 The RDF command failed because the specified RDF store does not exist in the specified schema. Specified RDF store name: store-name. Specified schema: schema-name.

The RDF store you are attempting to connect to does not exist.
  1. Check the name of the RDF store that you are connecting to and issue the command again.
  2. Create the RDF store and then connect to it.

DB255013E

 The droprdfstore command failed because the current user id does not have required authority or privileges to drop a table in the RDF store. Table name: table-name. Schema name: schema-name.

The user does not have the proper authority to drop the RDF store table.

Ensure the user has the DROP TABLE privilege for this database.

Then issue the command again.

DB255014E

 The RDF operation failed because the current user id does not have SELECT privileges on the data tables for the RDF store. RDF store name: store-name. Schema name: schema-name.

The user does not have the proper authority to read the data tables accessed using RDF commands or APIs.

Ensure the user has been granted READ permission for these tables.

Then issue the command or API again.

DB255015E

 The RDF command failed because a mandatory parameter was not specified. Parameter name: parameter-name. Command name: command-name.

This is a mandatory parameter for this command line tool.

Check your command to ensure it contains the mandatory parameter.

Then issue the command again.

DB255016E

 The RDF command failed because the specified RDF store name is too long. Specified RDF store name: store-name.

The maximum length of a store name is 128.

Ensure the store name is less than the maximum number of characters. Then issue your command again.

DB255017E

 Gathering statistics for an RDF store failed because the current user id does not have the required authority or privileges on a table in the RDF store. Table name: table-name. Schema name: schema-name.

The user does not have the proper authority to gather the latest statistics.
  • Ensure the user has READ privilege on all tables for this database.
  • Ensure the user has UPDATE privilege on all the statistics tables.

Then issue the command again.

DB255018E

 Creation of a new RDF graph failed because the specified graph name, "DEF", is invalid.

DEF is reserved for IBM use. It can not be used as the name of any user created graph.

Rename the graph. Avoid using DEF as the name.

DB255019E

 The RDF operation failed because the specified RDF quad contains a URI that is too long. Graph: graph. Subject: subject. Predicate: predicate. Object: object.

An URI in the quad has exceeded the maximum length of 2048 characters.

Examine the quad to reduce the length of the offending URI to less than 2048 characters.

DB255020E

 Parsing of a SPARQL query failed. Specified SPARQL query: query. Line number of the problem in the query: line-number. Column number of the problem in the query: column-number.

Check your SPARQL query at the location specified.

Rectify the error and issue the query again.

DB255021E

 The SPARQL feature feature-name is not supported.

IBM APIs do not support the feature.

Edit your query to refrain from using the unsupported feature.

DB255022E

 The RDF command failed because the following parameter is invalid: parameter-name.
  1. Parameters can not be abbreviated.
  2. Parameters can be issued in lower case only.
  1. Check the spelling of the parameter.
  2. Ensure the parameter is in lower case.

Issue the command again.

DB255023E

 The createrdfstoreandloader command failed because the RDF utility could not create the file specified with the -storeloadfile parameter or the utility could not create the file specified with the -storeschemafile parameter.

The user specified directory can not be created on the file system.

Ensure the directory structure already exists on the file system. Then Issue the command again.

DB255024E

 The RDF command failed because the current user id does not have INSERT and UPDATE privileges on the data tables for the RDF store. RDF store name: store-name. Schema name: schema-name.

The user does not have the proper authority to write to the data tables accessed using RDF commands or APIs.

Ensure the user has been granted WRITE permission for these tables.

Then issue the command or API again.

DB255025E

 The RDF command failed because the specified RDF store name does not satisfy DB2 database table naming conventions. Specified RDF store name: store-name.

The name must conform to naming conventions for table objects. Specifically, the name must not contain any space characters.

Ensure the store name does not contain any invalid characters. Then issue your command again.

DB255026E

 The RDF command failed because the specified schema name does not satisfy DB2 database schema naming conventions. Specified schema name: schema-name.

The schemaName does not follow the rules of DB2 schema names.

Ensure the schemaName rules are not being violated. Then issue your command again.

DB255027E

 The RDF operation failed because the specified RDF quad contains a literal string that is too long. Graph: graph. Subject: subject. Predicate: predicate. Object: object. Number of characters in the specified string literal: num-chars.

A literal in the quad has exceeded the maximum character length as configured for the store limit.
  • Examine the quad to reduce the length of the offending item to less than the configured length for the store.
  • Increase the configured length of literals for the store.

Then issue your query again.

DB255028E

 The SPARQL query was not processed because the query form does not match the method used to execute the query. Expected query form: query-form.

SPARQL supports four types of queries:

  • Describe
  • Ask
  • Select
  • Construct

The query type does not match the user operation. For example, execDescribe, execSelect, execConstruct, etc.

Ensure the query matches one of the supported query types.

DB255029E

 The RDF command failed because not all required table names were specified. RDF command name: command-name. Names of tables that were not specified: table-name-list.

If you choose to provide table names when issuing either the createrdfstore or createrdfstoreandloader commands, you need to specify names for all the tables.

Provide all the table names. Then issue your command again.

DB255030E

 An unexpected database error occurred during the operation. Operation name: operation-name. Query: query-details. SQLCODE: sqlcode. SQLSTATE: sqlstate.

You can take advantage of the Resource Description Framework (RDF) by using RDF utility commands such as createRdfStore. You can query RDF data that is stored in databases using the SPARQL query language.

This message is returned in two scenarios:

  • An RDF utility command encounter a database error while performing an RDF utility operation.
  • An attempt is made to query RDF data that is stored in a database, but an error was encountered while the query was being processed.

When this message is returned because a query fails, the details of the query will appear in the query-details runtime token. When this message is returned because an RDF utility command fails, the query-details runtime token will contain the following place holder: "*".

To assist with troubleshooting, the underlying database error code is included in the runtime token sqlcode. More diagnostic information can be found in the db2diag diagnostic log files. The runtime token sqlstate might sometimes be empty because not all SQL errors have an associated sqlstate.

Respond to this error by performing the following troubleshooting steps:

  1. Search in the db2diag log files for the sqlcode and sqlstate given in the runtime tokens sqlcode and sqlstate.
  2. Examine the underlying database error message.
  3. Take corrective actions to fix the error.
  4. Run the RDF operation again.

DB255031E

 The RDF operation failed because the RDF utilities could not find the Cygwin library.

The Cygwin application needs to be on the path if you are running your program on the Windows operating system.

Ensure the Cygwin application has been added to the path on Windows.

DB255032E

 The reorgswitchrdfstore command failed because reorganized tables for the RDF store are unavailable.

The reorgswitchrdfstore command transfers the RDF store to the new tables. No new reorganized tables are currently available for this store.

Issue the reorgrdfstore command first. After it completes successfully, then issue the reorgswitchrdfstore command.

DB255033E

 The following RDF command failed because the command is being issued remotely. Command name: command-name.

This command can only be run locally on the database server.

Command command-name has to be run locally on the database server.

DB255034I

 RDF data reorganization has completed.

Table data has been successfully reorganized into the new tables.

Begin using the reorganized tables by issuing the reorgswitchrdfstore command.

DB255035E

 Connecting to an RDF store failed because an unexpected database error occurred during the operation. SQLCODE: sqlcode. SQLSTATE: sqlstate.

You can take advantage of the Resource Description Framework (RDF) by using RDF utility commands such as createrdfstore. You can query RDF data that is stored in databases using the SPARQL query language.

This message is returned when an attempt is made to connect to an RDF store in a database, but an error was encountered while the connection was being processed.

To assist with troubleshooting, the underlying database error code is included in the runtime token sqlcode. More diagnostic information can be found in the db2diag diagnostic log files. The runtime token sqlstate might sometimes be empty because not all SQL errors have an associated sqlstate.

Respond to this error by performing the following troubleshooting steps:

  1. Search in the db2diag log files for the sqlcode and sqlstate given in the runtime tokens sqlcode and sqlstate.
  2. Examine the underlying database error message.
  3. Take corrective actions to fix the error.
  4. Execute the RDF operation again.

DB255036I

 The reorgrdfstore command completed successfully.

You can create tables with optimal number and length of columns for an RDF store using the reorgrdfstore command.

This message is returned when the command completes successfully.

To switch the RDF store to use the newly reorganized tables, use the reorgswitchrdfstore command.

DB255037I

 None of the RDF store tables need to be reorganized.

When significant amounts of data have been inserted into a RDF store, the number and length of columns for various tables in the store might no longer be optimal for your data. This might impact query and insert performance for the RDF store. You can determine whether any or all of the RDF store tables need to be reorganized using the reorgcheckrdfstore command.

This message is returned when the reorgcheckrdfstore utility determines that no RDF store tables need to be reorganized.

No user response is required.

DB255038E

 The reorgrdfstore command failed because an invalid value was specified for the -table parameter. Specified table name: specified-table-name.

You can create tables with optimal number and length of columns for an RDF store using the reorgrdfstore command.

You can specify which RDF store table needs to be reorganized using the -table parameter with the reorgrdfstore command. This message is returned when the value specified with the -table parameter is not a valid name of an RDF store table.

Call the reorgrdfstore command again, specifying a valid RDF store table name with the -table parameter.

DB255039E

 RDF store creation failed because the value of the database LOGFILSIZ parameter is not large enough.

The minimum required DB2 LOGFILSIZ parameter value is 20000 or more. If you get this error even with a value of 20000, you need to increase it further.
  1. Update the LOGFILSIZ database configuration parameter to a larger value.
  2. Issue the store creation command again.

DB255040E

 RDF store creation failed because the table space specified for a RDF Store table in the -objectnames parameter does not exist. Table space name: table-space-name.

The table space specified in the properties file of the -objectnames parameter does not exist.

Create the table space or check the spelling of the table space. Then issue the command again.

DB255041E

 The queryrdfstore command failed because reopt ONCE or ALWAYS option was specified but the corresponding REOPT package is not bound.
  • You need to bind the REOPT NULLIDR1 package if you are using the reopt ONCE option.
  • You need to bind the REOPT NULLIDRA package if you are using the reopt ALWAYS option.

For more information, see: http://www.ibm.com/developerworks/data/library/techarticle/dm-1011reopt/

Bind the respective NULLIDR1 or NULLIDRA packages. Then issue the queryrdfstore command again.

DB255042E

 The loadrdfstore command failed because the input load file is not specified as the last argument to the loadrdfstore command.

The loadrdfstore command requires an input load file. This load file is used to list the commands to load data into an RDF store.

Ensure the load file is specified. Then issue the loadrdfstore command again.

DB255043E

 The loadrdfstore command failed because the format of the input load file is not supported.

The loadrdfstore command requires an input load file in a supported file format.

The following load file formats are supported:

  • nquad
  • ntriple
  • rdfxml
  • trig
  • turtle
  • n3

Ensure the load file is formatted properly. Then issue the loadrdfstore command again.

DB255044E

 The queryrdfstore command failed because the SPARQL query is missing.

The queryrdfstore command accepts the SPARQL query as an input parameter in one of the following two ways:

  • as a file using the file parameter
  • as an inline string specified as the last argument to the queryrdfstore command

The command is missing the required query string.

Ensure that a SPARQL query is available to the queryrdfstore command as a parameter. Then issue the command again.

DB255048E

 Creation of an RDF store failed because the value of the LOGFILSIZ database configuration parameter is too small.

An RDF store in the database server is a set of user tables within a database schema that stores an RDF data set. You can create a default RDF store by calling the createrdfstore command.

One prerequisite for creating an RDF store is that the LOGFILSIZ database configuration parameter meet minimum size requirements.

Increase the LOGFILSIZ database configuration parameter to the minimum size required for creating an RDF store.

DB255049E

 Creation of an RDF store failed because the SYSTOOLS table space does not exist.

An RDF store in the database server is a set of user tables within a database schema that stores an RDF data set. You can create a default RDF store by calling the createrdfstore command.

One prerequisite for creating an RDF store is that the SYSTOOLSPACE table space be created. The SYSTOOLSPACE table space is a user data table space used by the DB2 administration tools and some SQL administrative routines for storing historical data and configuration information.

Manually create the SYSTOOLSPACE table space and then create the RDF store.