DMB0001E | The DB2 Extenders server was not connected. Reason: "<code>". |
Cause: The attempted operation attempted requires the DB2 extenders services to be running.
Action: On the server, run the DMBSTART command on the command line for the operating system.
DMB0003W | The DB2 extenders trace facility is running for this session. |
Cause: The trace facility uses up system resources.
Action: If the performance of your system is affected, you might want to turn off tracing.
DMB0004I | This program can be run only by the instance owner: "<name>". |
Cause: The DB2 extender servers must be started from the user ID under which the instance was created.
Action: Run the DMBSTART command from the user ID under which the instance was created.
DMB0005E | The current database is not enabled for the "<extender-name>" extender. |
Cause: An operation was attempted that requires the database to be enabled for a specific DB2 extender. For example, if you want to enable a table for DB2IMAGE data, you must first enable the database in which the table is stored for DB2IMAGE data.
Action: Enable the database for the extender data type you want and try again.
DMB0006E | User "<name>" is not authorized to call this API. |
Cause: The call to an application programming interface was attempted from a user ID that does not have the level of authority required for that API.
Action: Either run the application from another user ID, or get the database administrator to change the level of authority for the initial user ID.
DMB0007E | User table "<table-name>" is not enabled for extender "<extender-name>". |
Cause: The table on which the operation was attempted is not enabled for that DB2 extender. For example, a table must be enabled to hold audio data before a column in the table can be enabled for audio.
Action: Make sure that the table is enabled for the extender first. Then enable the column.
DMB0008E | An error occurred while running the stored procedure "<name>". |
Cause: Either there is an error in the stored procedure that is identified in the message, or there is a problem with the environment.
Action: Verify your application and try again.
DMB0009E | Memory allocation error. |
Cause: The system was unable to allocate memory that is required to support the attempted operation.
Action: Verify that your system has enough memory to complete the operation.
DMB0010E | The "<extender-name>" extender has been previously defined for the UDT "<name>". |
Cause: The name of the user-defined type (UDT) has already been used for a UDT that was defined for another DB2 extender.
Action: Choose another name for your UDT.
DMB0011E | User column "<column-name>" cannot be enabled for the "<extender-name>" extender. The definition of the user column is not compatible with the distinct type "MMDBSYS.<name>" associated with the extender. |
Cause: The indicated column is not defined for the data type that is shown in the message, so it cannot be enabled for that extender.
Action: Make sure that the column you want to enable has been defined using the data type that corresponds to the extender.
DMB0012E | The specified user table "<table-name>" does not exist. |
Cause: No table exists with the specified name.
Action: Check the name of the table and whether the table exists.
DMB0013E | Column "<column-name>" is not defined for table "<table-name>". |
Cause: The attempted operation referred to a column name that does not exist in the identified table.
Action: Check the names of the table and the column.
DMB0014W | Column "<column-name>" in user table "<table-name>" is already enabled for the "<extender-name>" extender. |
Cause: An attempt was made to enable the column for an extender for which the column is already enabled.
Action: No action is required.
DMB0015W | The database is already enabled for extender "<extender-name>". |
Cause: An attempt was made to enable the database for an extender for which the database is already enabled.
Action: No action is required.
DMB0016W | User table "<table-name>" is already enabled for the "<extender-name>" extender. |
Cause: An attempt was made to enable a table for an extender for which the table is already enabled.
Action: No action is required.
DMB0017E | User table "<table-name>" is already enabled for the "<extender-name>" extender. But at least one of the associated metadata tables "<table-name>" or "<table-name>" doesn't exist. |
Cause: One or more of the administrative support (metadata) tables that are associated with the table has been damaged or destroyed. Without these metadata tables, the user table cannot be used for data of that extender's type.
Action: Disable the user table and re-enable it for the extender.
DMB0018E | The system cannot create a unique trigger name for column "<column-name>" in table "<table-name>". |
Cause: When the system tried to enable the column in the user table, an error occurred during the creation of triggers that are used by the DB2 extenders.
Action: Repeat the operation. If the error occurs again, contact your database administrator, then contact IBM service.
DMB0019I | "<Count>" files are referered to in table "<table-name>" for extender "<extender-name>". |
Cause: The message displays the number of external media files that are referred to by a user table for a specific extender.
Action: No action is required.
DMB0020I | "<Count>" files are referenced in tables with table schema "<name>" for the "<extender-name>" extender. |
Cause: The message displays the number of external media files that are referred to by user tables with a specific schema name.
Action: No action is required.
DMB0021I | There are "<count>" inaccessible files refererenced in table "<table-name>" for the "<extender-name>" extender. |
Cause: The message displays the number of external media files that are referred to by a user table for a specific extender, but are inaccessible. The files might have been erased.
Action: No action is required.
DMB0022I | There are "<count>" inaccessible files referenced by the "<extender-name>" extender. |
Cause: The message displays the number of external media files that are:
Action: No action is required.
DMB0023I | There are "<count>" inaccessible files referenced in tables with table schema "<name>" for extender "<extender-name>". |
Cause: The message displays the number of external media files that are referred to by user tables with a specific schema name, but are inaccessible. The files might have been erased. The messages also indicates the number of extenders the tables are enabled for.
Action: No action is required.
DMB0024I | The current database is enabled for "<count>" extenders. |
Cause: The message lists the number of DB2 extenders the current database is enabled for.
Action: No action is required.
DMB0025I | Table "<table-name>" is enabled for "<count>" extenders. |
Cause: The message lists the number of DB2 extenders the indicated table is enabled for.
Action: No action is required.
DMB0026I | Column "<column-name>" in table "<table-name>" is enabled for "<count>" extenders. |
Cause: The message lists the number of DB2 extenders the indicated column is enabled for.
Action: No action is required.
DMB0027I | The current database is enabled for extender "<extender-name>". |
Cause: The message indicates the DB2 extender for which the current database is enabled.
Action: No action is required.
DMB0028I | Table "<table-name>" is enabled for extender "<extender-name>". |
Cause: The message indicates the media data type the user table is enabled to hold.
Action: No action is required.
DMB0029I | Column "<column-name>" in table "<table-name>" is enabled for extender "<extender-name>". |
Cause: The message indicates the media data type the user column is enabled to hold.
Action: No action is required.
DMB0030E | The current database cannot be enabled for the "<extender-name>" extender. RC = "<code>." |
Cause: Either the database does not exist, or you are not authorized to enable the database.
Action: Make sure the database exists and that you are authorized to enable the database.
DMB0031E | The table cannot be enabled for the "<extender-name>" extender. RC = "<code>." |
Cause: The database does not exist, or the table is not enabled, or you are not authorized to enable the table.
Action: Make sure the database exists and that both the database and table are enabled for the extender. Make sure that you are authorized to enable the table.
DMB0032E | The column cannot be enabled for the "<extender-name>" extender. RC = "<code>." |
Cause: The column is was not defined using the data type for this extender, or the column does not exist, or the table is not enabled, or you are not authorized to enable the column.
Action: Make sure the column was defined using the right data type. Make sure that the table is enabled and you are authorized to enable the column.
DMB0033E | You are not authorized to run this command. |
Cause: Your user ID does not have the level of authority required to run the command.
Action: Either run the command from another user ID, or get the database administrator to change the level of authority for your current user ID.
DMB0034I | The DB2 Extenders Server for database "<database-name>" was started successfully. |
Cause: The server started successfully for the current database.
Action: No action is required.
DMB0035I | The DB2 Extenders Server for database "<database-name>" was stopped. |
Cause: The server stopped successfully for the current database.
Action: No action is required.
DMB0036E | The DB2 Extenders server cannot be started or stopped. The DB2 Extenders server daemon is probably not running. Contact your database administrator. |
Cause: An error occurred while starting or stopping the DB2 extenders server. The DB2 extenders server daemon is probably not running.
Action: Please contact your database administrator.
DMB0037E | The USE session handle is not valid. |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0038E | The USE statement handle is not valid. |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0039E | USE error: "<error>." |
Cause: An internal error has occurred.
Action: Follow the instructions that are contained in the associated error message and repeat the operation. If the error occurs again, contact IBM service.
DMB0040E | SQL error: "<error>" |
Cause: An internal error has occurred.
Action: Follow the instructions that are contained in the associated error message and repeat the operation. If the error occurs again, contact IBM service.
DMB0041W | The current database is re-enabled for the "<extender-name>" extender using the newly specified table space. |
Cause: When the current database was previously enabled, it used a different table space. The database is now enabled with a new table space for the administrative support tables.
Action: No action is required.
DMB0042E | Column "<column-name>" in table "<table-name>" is not enabled for the "<extender-name>" extender. |
Cause: The indicated column is not enabled for the extender for which the operation was attempted. For example, you might have tried to disable a column that was not currently enabled for the indicated extender.
Action: Make sure that the column is enabled for the extender that is indicated in the message.
DMB0043I | The current database is disabled for the "<extender-name>" extender. |
Cause: The disable operation was successful.
Action: No action is required.
DMB0044I | Table "<table-name>" is disabled for the "<extender-name>" extender. |
Cause: The disable operation was successful.
Action: No action is required.
DMB0045I | Column "<column-name>" in table "<table-name>" is disabled for the "<extender-name>" extender. |
Cause: The disable operation was successful.
Action: No action is required.
DMB0046E | The current database cannot be disabled for the "<extender-name>" extender. RC = "<code>." |
Cause: The database does not exist or is not enabled for the extender, or you are not authorized to disable the database.
Action: Make sure that the database exists and is enabled for the extender. Make sure that you are authorized to disable the database.
DMB0047E | The table cannot be disabled for the "<extender-name>" extender. RC = "<code>." |
Cause: The table does not exist or is not enabled for the extender, or you are not authorized to disable the table.
Action: Make sure that the table exists and is enabled for the extender. Make sure that you are authorized to disable the table.
DMB0048E | The column cannot be disabled for the "<extender-name>" extender. RC = "<code>" |
Cause: The column is not enabled for the extender that is indicated in the message, so it cannot be disabled for that extender.
Action: Verify the name of the extender and whether the user column is the one you want to disable.
DMB0049E | You are not authorized to run this command. |
Cause: Your user ID does not have the level of authority required to run the command.
Action: Either run the application from another user ID, or get the database administrator to change the level of authority for your current user ID.
DMB0050E | You do not have "<authority-level>" authority on table "<table-name>". |
Cause: The operation requires a level of authority higher than the one of the user ID that made the attempt.
Action: Either perform the operation from the user ID with the right authorization, or get the database administrator to change the level of authority for your current user ID.
DMB0051E | Bad media file header. |
Cause: The system cannot read or open the header of the media file. Either the file is damaged, or it is not a media file.
Action: Verify that the file is a media file and is not damaged.
DMB0052I | The DB2 Extenders server for database "<database-name>" was started successfully. |
Cause: The server started successfully.
Action: No action is required.
DMB0053I | The DB2 Extenders server for database "<database-name>" was stopped successfully. |
Cause: The server stopped successfully.
Action: No action is required.
DMB0054E | The DB2 Extender server cannot connect to the database or allocate a DB2 statement handle. The DB2 Extender server for database "<database-name>" is probably not running. |
Cause: The DB2 extenders server cannot connect to the database or allocate a DB2 statement handle. The DB2 extenders server for the database is probably not running.
Action: Make sure that the DB2 extender server for the database is running. If it is not, either start the specific extender server for the database, or ask your system administrator to restart the extender services.
DMB0055I | The "command-name" command completed successfully. |
Cause: The command completed successfully.
Action: No action is required.
DMB0056E | An unexpected token "<token>" was found following "<keyword>". Expected tokens can include: <extendername>. |
Cause: The command expected the name of a DB2 extender instead of the token that is indicated in the message.
Action: Follow the syntax of the command and try again.
DMB0057E | The table space "<table-space-name>" is not valid. |
Cause: The table space in the message does not exist.
Action: Verify the name of the table space and whether it exists.
DMB0058I | "<Count>" files are referenced by the "<extender-name>" extender. |
Cause: The message displays the number of external media files that are referred to by a specific extender.
Action: No action is required.
DMB0059E | "<Name>" is not a valid name for an DB2 extender. Valid extender names include "<extender-name,>" DB2VIDEO, DB2AUDIO, and DB2IMAGE. |
Cause: The extender name is misspelled.
Action: Verify the extender name.
DMB0060E | The correct syntax for "<function>" is: "<syntax>." |
Cause: The syntax of the command you entered is wrong.
Action: Follow the syntax as described in the message.
DMB0061E | The table name "<name>" that follows "<keyword>" is not valid. |
Cause: The command expected the name of a table.
Action: Follow the syntax of the command and try again.
DMB0062E | The column name "<name>" that follows "<keyword>" is not valid. |
Cause: The command expected the name of a column.
Action: Follow the syntax of the command and try again.
DMB0064E | The system does not recognize the token "<token>" that follows "<keyword>". |
Cause: The command expected something other than the token that is indicated in the message.
Action: Follow the syntax of the command and try again.
DMB0065E | The user ID "<identifier>" that follows "<keyword>" is not valid. |
Cause: The command expected a valid user ID.
Action: Verify the user ID you want and try again.
DMB0066E | The password "<password>" that follows "<keyword>" is not valid. |
Cause: The command expected a valid user ID instead of the token that is indicated in the message.
Action: Verify the password and try again.
DMB0067E | The command you entered is not valid. |
Cause: The name of the command was misspelled, or the syntax was wrong.
Action: Follow the syntax of the command and try again.
DMB0068E | Metadata table does not exist. |
Cause: The function tried to use an administrative support (metadata) table that should exist for the data object. The metadata table might have been damaged or erased.
Action: Check the name and verify the existence of the metadata table. If the metadata tables were accidentally erased or damaged, disable and then reenable the data object.
DMB0069E | DBname "<name>" invalid. |
Cause: A database with that name does not exist.
Action: Check the name and verify the existence of the database.
DMB0070E | Handle not valid. |
Cause: The handle value you passed in your application might be damaged.
Action: Verify your application to make sure that the extender handle values are not changed.
DMB0071E | Can't connect to "<database-name>". |
Cause: The DB2 extender server for the database might not be started.
Action: Check the status of the server. If the server is not running, restart it using the START SERVER command on the DMB command line.
DMB0072E | UDF SQL server can't disconnect from DB. |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0073E | USE session handle not valid. |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0074E | USE statement handle not valid. |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0075E | Specify a file name. |
Cause: The operation requires a media file name.
Action: Enter the name of a media file.
DMB0076E | Can't open import file. |
Cause: The import file is either missing or damaged.
Action: Verify the name and existence of the import file.
DMB0077E | Can't open/read content file. |
Cause: The extender handle points to a file that does not exist or is corrupted. The file has become inaccessible to the extender.
Action: Use the FILENAME UDF to find the name of the file, or verify the existence of the content file.
DMB0078E | Can't create export file. |
Cause: The export file is either missing or corrupted.
Action: Verify the name and existence of the export file.
DMB0079E | Can't copy BLOB to file. |
Cause: The file cannot accept the BLOB. There might not be enough storage space to accommodate the BLOB.
Action: Compare the size of the BLOB to the available storage, and increase storage if necessary.
DMB0080E | Can't write to file. |
Cause: The file is damaged or does not exist, or the name is misspelled.
Action: Verify the name and existence of the file.
DMB0081E | Offset or size invalid. |
Cause: The operation did not find the expected data in the data structure. Either the size of the field or the offset is incorrect.
Action: Verify the offset and the size of the field.
DMB0082E | Can't build handle. |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0083E | "<extender-name>" and "<extender-name>" incompatible. |
Cause: The two extenders specified in the message are not compatible in this usage. The insert operation, by either full or subselect, is not valid.
Action: Make sure that your target object is enabled for the same extender for which the source object is enabled.
DMB0084E | Import request invalid: filename, content, storage type. |
Cause: The import operation failed. Either the file name, the content, or the storage type was not valid.
Action: Check the data and try again.
DMB0085E | The update request is not valid: filename, content, storage type. |
Cause: The update operation failed. Either the file name, the content, or the storage type was not valid.
Action: Check the data and try again.
DMB0086E | Requested size too large. |
Cause: The size you requested is larger than the maximum blob size for the UDF.
Action: Request a smaller size.
DMB0087E | File name invalid. |
Cause: There is no file with that name.
Action: Verify the name and existence of the file.
DMB0088E | Handle value is NULL. |
Cause: The UDF was expecting a non-null handle.
Action: Make sure that the application gets a valid handle and passes it to the UDF.
DMB0089E | Handle value doesn't exist. |
Cause: The handle passed to the UDF is not valid.
Action: Make sure the application passes a valid handle.
DMB0090E | Data truncated. |
Cause: The file or buffer was too small to accept the data.
Action: Increase the size of the file or buffer.
DMB0091W | Content already in file. |
Cause: The file already has content. The content will be overwritten.
Action: No action is required.
DMB0092E | The insert operation attempted for column "<column-name>" is not valid. The column is enabled for the "<extender-name>" extender. |
Cause: The data type of the data that is being inserted is different from the extender for which the column is enabled.
Action: Make sure your target object is enabled for the same extender for which the source object is enabled.
DMB0093E | The update operation attempted for column "<column-name>" is not valid. The column is enabled for the "<extender-name>" extender. |
Cause: The data type of the data that is being updated is different from the extender for which the column is enabled.
Action: Make sure that your target object is enabled for the same extender for which the source object is enabled.
DMB0094I | Table "<table-name>" does not exist. |
Cause: The system cannot find a table with that name. It might exist in another database.
Action: No action is required.
DMB0095W | The table "<table-name>" is not enabled for the "<extender-name>" extender. |
Cause: The table is not enabled for the extender.
Action: No action is required.
DMB0096W | Column "<column-name>" in table "<table-name>" was not enabled for the "<extender-name>" extender. |
Cause: The system expected the column to be enabled.
Action: No action is required.
DMB0097W | The current database is not enabled for the "<extender-name>" extender. |
Cause: The system expected the database to be enabled.
Action: Enable the database for the extender that is indicated in the message.
DMB0098E | The user does not have "<authority-level>" authority on table "<table-name>". |
Cause: The operation requires a level of authority higher than the one of the user ID that made the attempt.
Action: Either perform the operation from the user ID that owns the table, or ask the database administrator to change the level of authority for your current user ID.
DMB0099E | Can't commit transaction. |
Cause: The extender server for the current database might be stopped.
Action: Check the status of the server. If the server is not running, restart it using the START SERVER command on the db2ext command line.
DMB0100E | "<name>" is not a valid table name. |
Cause: No table with that name exists.
Action: Verify the name and existence of the table and try again.
DMB0101E | Invalid NULL parameter. |
Cause: The command was expecting a non-null parameter.
Action: Check the syntax and try again.
DMB0102E | Invalid storage type. |
Cause: For the DB2 extenders, the storage type indicates where the media data is stored.
Action: Specify 0 to indicate external (in a file) and 1 to indicate external (in the database).
DMB0103E | Unsupported format. |
Cause: DB2 extenders do not support the format of this object.
Action: Convert the object to a supported format.
DMB0104E | Video content buffer too small. |
Cause: The video clip is too big for the buffer that is allocated for it.
Action: Allocate a bigger buffer.
DMB0105E | MPEG1 header invalid. |
Cause: The header of the MPEG1 file is missing or corrupt.
Action: Verify that the file is a MPEG1 file.
DMB0106E | AVI header invalid. |
Cause: The header of the AVI file is missing or corrupt.
Action: Verify that the file is an AVI file.
DMB0107E | Export environment not set up. |
Cause: In the DB2 extenders, the environment variables for the export environment are not set properly.
Action: Make sure that the environment variables are set properly, as described in Appendix A, Setting environment variables for DB2 extenders.
DMB0108E | Import environment not set up. |
Cause: In the DB2 extenders, the environment variables for the import environment are not set properly.
Action: Make sure that the environment variables are set properly, as described in Appendix A, Setting environment variables for DB2 extenders.
DMB0109E | Can't resolve import file. |
Cause: There is no import file with that name.
Action: Verify the name and existence of the file and make sure that the environment variables are set properly, as described in Appendix A, Setting environment variables for DB2 extenders.
DMB0110E | Can't resolve export file. |
Cause: There is no export file with that name.
Action: Verify the name and existence of the file and make sure that the environment variables are set properly, as described in Appendix A, Setting environment variables for DB2 extenders.
DMB0111E | Store environment not set up. |
Cause: The environment variables for the store environment are not set properly,
Action: Make sure the environment variables are set properly, as described in Appendix A, Setting environment variables for DB2 extenders.
DMB0112E | Can't resolve store file. |
Cause: There is no store file with that name.
Action: Verify the name and existence of the file and make sure that the environment variables are set properly, as described in Appendix A, Setting environment variables for DB2 extenders.
DMB0113E | Can't open import file. |
Cause: The file might be locked by someone else, or the file is missing or corrupt.
Action: Verify the name, existence, and status of the file, and your authorization level.
DMB0114E | Can't open export file. |
Cause: The file might be locked by someone else, or the file is missing or corrupt.
Action: Verify the name, existence, and status of the file, and your authorization level.
DMB0115E | Can't open store file. |
Cause: The system is trying to write a file, but the file already exists. The server does not have the authority to overwrite the file.
Action: Verify the name, existence, and status of the file, and your authorization level.
DMB0116E | Can't create temporary file. |
Cause: There might not be enough storage space to create the temporary file.
Action: Make sure that the temporary environment variables for the extender are set properly. Increase the storage if necessary.
DMB0117E | Temporary environment not set up. |
Cause: The environment variables for the temporary environment are not set properly,
Action: Make sure that the environment variables are set properly, as described in Appendix A, Setting environment variables for DB2 extenders.
DMB0118E | Can't open temporary file. |
Cause: The temporary file might have been overwritten or damaged.
Action: Make sure that the environment variables are set properly, as described in Appendix A, Setting environment variables for DB2 extenders.
DMB0119I | The dmbsrv server is starting for "<name>" with "<count>" connections. |
Cause: The message indicates how many connections are made when the server starts.
Action: No action is required.
DMB0120E | The dmbsrv server failed to start for "<name>" with "<count>" connections. |
Cause: DB2 might not be started yet, or the database might not exist, or your system might have run out of licensed connections.
Action: Make sure that DB2 is started and the database exists. If the problem persists, contact IBM to get more licences.
DMB0121I | The dmbsrv server is started for "<name>" with "<count>" connections. |
Cause: The message indicates how many connections are made when the server starts.
Action: No action is required.
DMB0122I | The dmbssd server is ready. |
Cause: The server is ready to run your application.
Action: No action is required.
DMB0129E | Invalid operation: "<operation-name>". |
Cause: No command or API exists with that name.
Action: Verify the command or API and try again.
DMB0130E | Column "<column-name>" failed to be bound to the SQL statement. |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0131E | SQL prepare statement failed. |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0132E | SQL set parameter failed. |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0133E | SQL execute statement failed. |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0134E | File format conversion failed. |
Cause: The format of the stored multimedia data is not support for format conversion.
Action: You cannot convert the format of this file.
DMB0135E | Can't open/read thumbnail. |
Cause: The thumbnail file might be missing or damaged.
Action: Verify the name, existence, and integrity of the thumbnail file.
DMB0136E | Can't find bind file. |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0137E | Can't connect to DB "<database-name>" |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0138E | Can't free an SQL statement. |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0139E | The feature name "<name>" that follows "<keyword>" is not valid. |
Cause: The Image Extender expected a valid feature name in this command.
Action: Try the command again with a valid feature name. Valid feature names include:
DMB0141E | The qualifier "<identifier>" that follows "<keyword>" is not valid. |
Cause: The system cannot identify the qualifier in the command.
Action: Check the qualifier and try again.
DMB0142E | No catalog was opened. |
Cause: In the DB2 extenders, the current command needs a QBIC catalog to be opened.
Action: Open the QBIC catalog with the OPEN QBIC CATALOG command.
DMB0143I | In the QBIC catalog for column "<column-name>" in table "<table-name>", auto-cataloging has been set to "<status>". There are "<count>" features: |
Cause: The message indicates the number of features defined in the QBIC catalog for a specific image column, and whether auto-cataloging is turned on.
Action: No action is required.
DMB0145E | The query handle is not valid. |
Cause: The query handle you used in the API call is not valid.
Action: Check your application to see if you are obtaining the correct query handle.
DMB0146E | The feature class name "<feature-class>" is not valid. |
Cause: There is no feature class with that name. Valid feature names include:
Action: Correct the name of the feature and try again.
DMB0147E | The feature class name "<feature-class>" is either missing or not valid. |
Cause: Valid feature names include:
Action: Correct the name of the feature and try again.
DMB0148E | Feature "<feature-name>" is already a member of the query. |
Cause: The query already supports the feature indicated in the message.
Action: No action is required.
DMB0149E | Feature "<feature-name>" is not a member of the query. |
Cause: The query does not include the specified feature name.
Action: To add the feature to the query before calling other APIs that access the feature, use the QbQueryAddFeature API.
DMB0150E | The system cannot allocate memory. |
Cause: The system was unable to allocate memory required to support the attempted operation.
Action: Verify that your system has enough memory to complete the operation.
DMB0151E | The pointer to the return value is NULL. |
Cause: The API call did not complete successfully because the pointer to a return value must not be NULL.
Action: Make sure that valid parameters are supplied to the API call and the syntax is followed correctly.
DMB0152E | The pointer to the list return value is NULL. |
Cause: The API call did not complete successfully because the pointer to a return value must not be NULL.
Action: Make sure that valid parameters are supplied to the API call and the syntax is followed correctly.
DMB0153E | The scope parameter is reserved and must be 0. |
Cause: The parameter is reserved for future use.
Action: Set the scope to 0.
DMB0154E | The pointer to the feature class name is not valid. |
Cause: The API call expected a valid pointer to the input feature class name.
Action: Make sure that valid parameters are supplied to the API call and the syntax is followed correctly.
DMB0155I | A buffer size of zero was passed to the "<function-name>" function. |
Cause: The API call needs the buffer to return information.
Action: No action is required.
DMB0156E | The QbImageSource pointer is NULL. |
Cause: A NULL value indicates that the structure should not be changed.
Action: No action is required.
DMB0157E | The QbImageSource type "<type>" is not valid. |
Cause: The data structure referred to by this DB2 extender API is of the wrong data type.
Action: The data type of the structure should be QbImageSource.
DMB0159E | The pointer to the QbImageSource image buffer is NULL. |
Cause: The API call expected a pointer to be returned.
Action: Check your application to see if the API call and the buffer is specified correctly.
DMB0160I | The length of the image buffer or file is zero. |
Cause: The length is zero.
Action: No action is required.
DMB0161E | The pointer to the table and/or column name is NULL. |
Cause: The API call expected a pointer to be supplied.
Action: Check your application to see if the input to the API call is specified correctly.
DMB0162I | You set requestedHits to zero. |
Cause: With requestedHits set to zero, you get nothing back.
Action: No action is required.
DMB0163I | That function is not yet supported. |
Cause: That function is not yet supported.
Action: No action is required.
DMB0164E | The system cannot process the query (<query-name>). |
Cause: An error occurred when the query was created.
Action: Check the input to the command or API and try again.
DMB0165E | The system cannot run the query (<query-name>). |
Cause: An error occurred when the query was created.
Action: Check the input to the command or API and try again.
DMB0166E | A statement error was found in "<name>" while executing "<name>": "<error>" |
Cause: An internal IBM error occurred.
Action: Please contact your database administrator.
DMB0167E | An error occurred while reading QbGenericImageDataClass (<error>). |
Cause: An internal IBM error occurred.
Action: Please contact your database administrator.
DMB0168E | A query's feature "<feature-name>" was not set prior to search. |
Cause: The query did not run because it had no feature assigned to it.
Action: Add a feature to the query using either the QbAddFeature API or the ADD QBIC FEATURE command.
DMB0169E | The following error occurred in the Call-Level Interface: "<error>". |
Cause: CLI error.
Action: Follow the directions in the message text.
DMB0170E | Query name "<query-name>" is already in use. |
Cause: Another query exists with that name.
Action: Select another name.
DMB0171E | Query name "<query-name>" has not been stored. |
Cause: After creating the query, the system could not store it.
Action: Make sure that you have write authority and enough storage to store the query.
DMB0172E | SQL Error: "<error>". |
Cause: An internal error has occurred.
Action: Follow the instructions that are contained in the associated error message and repeat the operation. If the error occurs again, contact IBM service.
DMB0173E | The catalog is open, but for read-only: "<catalog-name>". |
Cause: You cannot update the catalog because someone else already opened the catalog in write mode, or you do not have write authority for it.
Action: Wait until the other user is finished, run the application from another user ID, or get the database administrator to change the level of authority for your current user ID.
DMB0174E | A system error occurred: "<error>". |
Cause: An internal IBM error occurred.
Action: Follow the instructions that are contained in the associated error message and repeat the operation. If the error occurs again, contact IBM service.
DMB0175I | Images were not found: "<information>". |
Cause: No images were found that matched the query. The database might be empty.
Action: No action is required.
DMB0176I | The column already has a QBIC catalog: "<table-name column-name>". |
Cause: Another catalog exists with that name.
Action: No action is required.
DMB0177E | The system cannot open the catalog; the error message is: "<error>". |
Cause: The catalog was damaged.
Action: Follow the instructions in the message text.
DMB0178E | The system cannot delete the catalog; the error message is: "<error>". |
Cause: Either the catalog does not exist, or it was damaged.
Action: Verify the name and existence of the catalog and try again.
DMB0179E | The catalog handle is not valid: "<error>". |
Cause: The catalog handle you used in the API call is not valid.
Action: Check your application to see if you are obtaining the correct catalog handle.
DMB0180I | Access to catalog is denied: "<error>". |
Cause: Access is denied.
Action: No action is required.
DMB0181I | Catalog is in use "<error>". |
Cause: Another operation is using this catalog.
Action: No action is required.
DMB0184I | Tracing has already been started: |
Cause: Tracing has already been started.
Action: No action is required.
DMB0185I | Tracing has not been started yet. |
Cause: Tracing has not been started yet.
Action: No action is required.
DMB0186I | Tracing was turned on at "<time>" from directory "<directory-name>". The trace file is "<file-name>". "<Count> bytes of trace data have been written. |
Cause: Tracing is on.
Action: No action is required.
DMB0187E | Communication cannot be established because the system cannot open file "<file-name>" for writing. |
Cause: Either you are not the owner of the current instance that is described by environment variable DB2INSTANCE, or the environment variables such as DB2MMTOP are not set correctly.
Action: Log with the user ID that owns the instance. Verify that the environment variables are set correctly.
DMB0188I | An error occurred when creating the trace daemon: "<error>" |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0189I | Tracing has already been successfully started: |
Cause: Tracing has already been started.
Action: No action is required.
DMB0190E | Tracing cannot be started. |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0191E | Environment variable "<name>" needs to be set. |
Cause: The system configuration is not correct.
Action: Set the variable and try again.
DMB0192I | Tracing has been successfully turned off. |
Cause: Tracing is off.
Action: No action is required.
DMB0193E | The system cannot write to file "<file-name>". |
Cause: You do you have write authority for the directory of the specified file.
Action: Please contact your database administrator to get authority.
DMB0194E | The system cannot read from file "<file-name>". |
Cause: Either the file does not exist or you do not have read authority for the file.
Action: Make sure the file exists and that you have read authority for the file.
DMB0198E | The trace code "<code>" in the input file is unknown. The input file might be damaged. |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0199E | You do not have "<authority-level>" authority for any of the referenced tables. |
Cause: Your user ID does not have the level of authority required for the operation.
Action: Either perform the operation from another user ID, or get the database administrator to change the level of authority for your current user ID.
DMB0200W | You do not have "<authority-level>" authority for at least one of the referenced tables. |
Cause: Your user ID does not have the level of authority required for some tables.
If you are listing referrred to files, the files that are listed are referred to by tables for which you have Select authority. If there are tables on your system for which you do not have Select authority, the files referred to by them are not listed.
If you are reorganizing metadata, the system only reorganized metadata for tables for which you have Control authority.
Action: To get all the files, either perform the operation from another user ID, or get the database administrator to change the level of authority for your current user ID.
DMB0201I | A feature with that name already exists: "<feature-name>". |
Cause: A feature with that name is already included in the QBIC catalog.
Action: No action is required.
DMB0202E | The feature name is not valid: "<feature-name>". |
Cause: There is no feature class with that name. Valid feature names include:
Action: Correct the name of the feature and try again.
DMB0203E | The feature was not found: "<feature-name>". |
Cause: There is no feature class with that name, or the feature class is not included in the QBIC catalog. Valid feature names include:
Action: Correct the name of the feature and try again.
DMB0204E | The column is not enabled for DB2IMAGE: "<column-name>". |
Cause: The column is not enabled for the Image Extender.
Action: Make sure that the column is enabled for the DB2 Image Extender.
DMB0205E | No catalog found for "<table-name column-name>". |
Cause: There is no QBIC catalog associated with the specified column.
Action: Create a QBIC catalog for the column before performing any other QBIC operations.
DMB0206W | The specified column is not enabled for any extender. |
Cause: The column might not exist or its data type might not be compatible with the extenders.
Action: Verify that the column has been defined using the correct data type.
DMB0207E | Can not overwrite the file. |
Cause: The file already exists, but the EXPORT UDF cannot overwrite it.
Action: Export the file to a different file name or allow the EXPORT UDF to overwrite the file.
DMB0208E | sqlcode=<code> clistate=<code>. |
Cause: An internal error has occurred.
Action: Repeat the operation. If the error occurs again, contact IBM service.
DMB0209E | Invalid audio header. |
Cause: The header of the audio file is missing or corrupt.
Action: Verify that the format of the audio file is supported by DB2 extenders.
DMB0211W | File exists w/o overwrite. |
Cause: The specified target file already exists and is not overwritten.
Action: No action is required.
DMB0212E | The resultType parameter is reserved and must be 0. |
Cause: The parameter is reserved for future use.
Action: Set the resultType to 0.
DMB0214E | The pointer to the query name is not valid. |
Cause: The API call expected a valid pointer to the input query name.
Action: Make sure that valid parameters are supplied to the API call and the syntax is followed correctly.
DMB0352E | Command line environment not initialized. |
Cause: The command line environment is not initialized to run the db2ext command-line processor. (This message applies only to Windows NT and Windows 95 environments.)
Action: Issue the db2cmd command to open a DB2CLP window, then issue the db2ext command to run the db2 command-line processor in that window.
DMB0353E | Cannot communicate with db2ext command-line processor's background process. |
Cause: The background process for the db2ext command-line processor is running, but the db2ext command-line processor cannot communicate with it.
Action: Try issuing the db2ext command in a different window.
DMB0354E | Cannot start db2ext command-line processor's background process. |
Cause: The background process for the db2ext command-line processor is running, but the db2ext command-line processor cannot communicate with it.
Action: Check that the executable module for the background process (db2extb or db2extb.exe) exists, and its directory is in the PATH environment variable.
DMB0355E | db2ext command-line processor's background process timed out. |
Cause: The background process for the db2ext command-line processor started successfully, but the db2ext command-line processor cannot communicate with it within the allowed time limit.
Action: Try issuing the db2ext command in a different window.
DMB0356E | Cannot communicate with the db2ext command-line processor's background process. |
Cause: The db2ext command-line processor sent a request to its background process, but the request was not received.
Action: Make sure that the background process for the db2ext command-line processor is still running.
DMB0357E | db2ext command-line processor's background process is not responding. |
Cause: The db2ext command-line processor sent a request to its background process, but the background process did not respond within the allowed time limit.
Action: Make sure that the background process for the db2ext command-line processor is still running.
DMB0359E | The db2ext command-line-processor background process request queue or input queue was not created within the timeout period. |
Cause: The background process for the db2ext command-line processor did not create message queues within the allowed time limit. (This message applies only to UNIX environments.)
Action: Make sure that the disk on which the DB2 instance home directory resides is not full (the background process needs this home directory to create a file for message queues). If the disk is not full, check whether you have started too many db2extb processes. This is possible if you are running the db2ext command-line processor in many windows. A background process is started in a window the first time you issue a db2ext command-line processor request in command mode. Make sure that you issue the command db2ext terminate to end the db2ext command-line processor when you no longer need it. Message queues for the backend process are deleted only if you issue the terminate command.
DMB0361E | Column or table not enabled. |
Cause: An import UDF was specified, but the specified table column is not enabled for the extender.
Action: Enable the table column and retry.
DMB0363E | Missing table and column name. |
Cause: An update UDF was invoked, but a table was not specified.
Action: Specify a table and retry.
DMB0364E | Extender "<extender-name>" has been previously defined for the table space "<tablespace-name>". |
Cause: The specified database, table, or column has already been enabled for the extender using a different tablespace than the one specified.
Action: Check that the table space specification is correct.
DMB0365E | You don't have CONTROL privilege on "<metadata-table-name>" and "<metadata-table-name >" which are the metadata tables for "<schema-name>"."<table-name>". |
Cause: Your request was denied because you do not have the required CONTROL privilege on the metadata tables for the specified user table.
Action: Have your database administrator grant you CONTROL privilege on the metadata tables.
DMB0366E | Expected feature name. |
Cause: A feature name is expected in the query string.
Action: Correct the query string and try again.
DMB0367E | Expected color|color histogram|file. |
Cause: Either "color", "histogram", or "file" is expected in the query string.
Action: Correct the query string and try again.
DMB0368E | Expected ','. |
Cause: A ',' is expected in the query string.
Action: Correct the query string and try again.
DMB0369E | File is not valid. |
Cause: The file specified in the query string is not valid.
Action: Correct the query string and try again.
DMB0370E | Expected filename. |
Cause: A filename is expected in the query string.
Action: Correct the query string and try again.
DMB0371E | Expected server|client. |
Cause: Either "server" or "client" is expected in the query string.
Action: Correct the query string and try again.
DMB0372E | Expected '('. |
Cause: A '(' is expected in the query string.
Action: Correct the query string and try again.
DMB0373E | Expected ')'. |
Cause: A ')' is expected in the query string.
Action: Correct the query string and try again.
DMB0374E | Expected percentage. |
Cause: The percent value is expected in the query string.
Action: Correct the query string and try again.
DMB0375E | Expected color. |
Cause: The red, green, and blue values are expected in the query string.
Action: Correct the query string and try again.
DMB0376E | Expected '='. |
Cause: An '=' is expected in the query string.
Action: Correct the query string and try again.
DMB0377E | Expected '<'. |
Cause: An '<' is expected in the query string.
Action: Correct the query string and try again.
DMB0378E | Expected '>'. |
Cause: An '>' is expected in the query string.
Action: Correct the query string and try again.
DMB0379E | Expected 'and'. |
Cause: An 'and' is expected in the query string.
Action: Correct the query string and try again.
DMB0380E | Expected weight. |
Cause: A weight is expected in the query string.
Action: Correct the query string and try again.
DMB0381E | Feature not set. |
Cause: The feature has not been added to the QBIC catalog.
Action: Add the feature to the QBIC catalog, and recatalog the images.
DMB0382E | Could not build query. |
Cause: The extender server for the current database might be stopped.
Action: Check the status of the server. If the server is not running, restart it using the START SERVER command on the db2ext command line.
DMB0383E | Could not execute query. |
Cause: The extender server for the current database might be stopped.
Action: Check the status of the server. If the server is not running, restart it using the START SERVER command on the db2ext command line.
DMB0384E | Could not get next item. |
Cause: End of the list has been reached.
Action: Make sure that your application is not attempting to retrieve an item beyond the end of the list.
DMB0386E | Can't collocate with user data |
Cause: The SQL API sqluihsh() has returned a non-zero return code.
Action: Retry. If the problem persists, call IBM support.
DMB0387E | The nodegroup for the specified tablespaces is different from the nodegroup of the user table. |
Cause: One or more of the tablespaces (that is, for the metadata table, index, or BLOB) passed as input for enabling a table is defined on a nodegroup that is different from the one the user table is defined on.
Action: Use tablespaces that are defined on the same nodegroup as the user table to be enabled.
DMB0388E | The regular, long or index tablespaces are not defined on the same nodegroup. |
Cause: One or more of the tablespaces (that is, for the metadata table, index, or BLOB) passed as input for enabling a database is not defined on the same nodegroup as the other tablespaces.
Action: Use tablespaces that are defined on the same nodegroup.
DMB0389W | The nodegroup for the specified tablespaces does not include all of the partition servers. |
Cause: The tablespaces passed as input are defined on a nodegroup that does not include all partition servers.
Action: No action is required. However, the import and update UDFs will perform more efficiently if the tablespaces are defined on a nodegroup that covers all the partition servers. This is especially true if the extender applications store media content in BLOB format.
DMB0391I | This command can be run only when a DB2 UDB client is accessing a DB2 UDB server. |
Cause: Either the db2ext command-line processor is not connected to a DB2 UDB server, or the db2ext command-line processor has not been started by a DB2 UDB client. For example, the command START SERVER is valid only if the db2ext command-line processor is connected to a DB2 non-Extended Enterprise Edition server.
Action: Do not issue this command in the current client/server configuration.
DMB0392I | The command can be run only when a DB2 UDB client is accessing a DB2 UDB Extended Enterprise Edition server. For example, the command DISCONNECT SERVER is valid only if the db2ext command-line processor is connected to a DB2 Extended Enterprise Edition server. |
Cause: Either the db2ext command-line processor is not connected to a DB2 UDB Extended Enterprise Edition server, or the db2ext command-line processor has not been started from a DB2 UDB client.
Action: Do not issue this command in the current client/server configuration.
DMB0402E | Option "<option-name>" for command "<command-name>" is valid only if the application is connected to a DB2 "<server-type>" server. |
Cause: The specified parameter is not valid because the db2ext command-line processor is not connected to the type of server that supports that option. For example, the command GET SERVER STATUS can be specified with the parameter NODENUM <nodenum> only if the db2ext command-line processor is connected to a DB2 Extended Enterprise Edition server.
Action: Do not issue this command-parameter combination in the current client/server configuration.
DMB0411E | Invalid base port |
Cause: An invalid TCP/IP port number was entered as the base port during instance creation.
Action: The correct syntax is dmbicrt -r:base_port,end_port -t:base_port,end_port. Correct the parameter and retry the command.
DMB0412E | Invalid end port |
Cause: An incorrect TCP/IP port number was entered as the end port during instance creation.
Action: The correct syntax is dmbicrt -r:base_port,end_port -t:base_port,end_port. Correct the parameter and retry the command.
DMB0413E | Unable to resolve the DB2 Extenders installation path. |
Cause: The instance creation program could not find a value for the environment variable "DMBPATH."
Action: Set the variable "DMBPATH" and retry the application.
DMB0414E | Unable to resolve the computer hostname. |
Cause: An internal error was encountered while trying to resolve the computer's name.
Action: Contact IBM support.
DMB0415E | Unable to resolve the node number for this machine. |
Cause: The machine on which the instance creation is being run is not listed in the file "db2nodes.cfg."
Action: Add the machine to the "db2nodes.cfg" and retry the application.
DMB0416E | This program must be started by the root. Unable to continue. |
Cause: The user ID under which the program is being run does not have root authority.
Action: Logon as the root and retry the application.
DMB0417E | This program must be executed by a user with administrator authority. Unable to continue. |
Cause: The user ID under which the program is being run does not have administrator authority.
Action: Logon with a user ID that has administration authority, and retry the application.
DMB0418E | Unable to get information about user: "<userid>". |
Cause: An internal error occured when trying to get user information that is associated with the instance being created.
Action: Ensure that there is a valid user ID with the same name as the instance being created, and retry the application.
DMB0419E | Unable to create AIV Extenders directory "<directory_name>. Return Code = <code> |
Cause: An error occured while trying to create the specified directory. The return code represents the error returned from the operating system.
Action: Ensure that the file system/drive specified in the directory name exists and that permissions allow a directory to be created.
DMB0420E | Unable to create link for AIV Extenders directory "<directory_name>". Return Code = <code> |
Cause: An error occured while trying to create the specified symbolic link. The return code represents the error that is returned from the operating system.
Action: Ensure that the file system/drive specified in the directory name exists and that permissions allow a link to be created.
DMB0421E | Unable to open file: "<file_name>". Return Code = <code> |
Cause: An error occured while trying to open the specified file. The return code represents the error that is returned from the operating system.
Action: Ensure that the file exists and that permissions allow the file to be opened.
DMB0422E | Unable to write to file: "<file_name>". Return Code = <code> |
Cause: An error occurred while trying to write to the specified file. The return code represents the error that is returned from the operating system.
Action: Ensure that the file exists and that permissions allow the file to be written to.
DMB0424E | Unable to find "db2nodes.cfg" file. |
Cause: The DB2 file "db2nodes.cfg" could not be located.
Action: Ensure that the correct version of DB2 UDB Extended Enterprise Edition has been installed and retry the application.
DMB0426E | Error: "<error_code>" opening key "<registry_key>". |
Cause: An error occurred while trying to open the specified registry key.
Action: Record the return code and contact IBM support.
DMB0427E | The variable "<variable>" was not set in the profile registry. |
Cause: The specified value was not found in the Windows NT registry.
Action: Ensure that the name of a valid DB2 Extender variable was specified.
DMB0430E | Unable to find DB2 registry values |
Cause: The registry values used by DB2 could not be found.
Action: Ensure that the correct version of DB2 UDB Extended Enterprise Edition is installed and retry the application.
DMB0431E | Unable to create Extender Registry Key: "<registry_key>". |
Cause: An internal error occured while trying to create an extender registry key.
Action: Contact IBM support.
DMB0432E | Unable to set value for extender registry key: "<registry_key>". |
Cause: An internal error occurred while trying to set an extender registry key value.
Action: Contact IBM support.
DMB0435E | Unable to access control file "<control_file>". |
Cause: The specified control file could not be found.
Action: Contact IBM support.
DMB0443E | Unable to open directory "<directory_name>". Return = <code> |
Cause: An error occurred while trying to open the specified directory. The return code represents the error that is returned from the operating system.
Action: Ensure that the file system/drive specified in the directory name exists and that permissions allow a directory to be opened.
DMB0449W | -q:datapath is required for DB2 extender instance creation. |
Cause: The -q parameter was not specified when trying to create an DB2 extender instance.
Action: Specify the parameter and retry the application.
DMB0450W | One or more of the specified "<port>" ports are already in use. |
Cause: A port was specified for use by DB2 Extenders that is already listed in the services file as being in use.
Action: Specify a port or ports that are not in use and retry the application.
DMB0452E | Node number "<node_num>" was not found in the "db2nodes.cfg" file. |
Cause: The node number of this machine was not found in the db2nodes.cfg file.
Action: Add the node number to the db2nodes.cfg file and retry the application.
DMB0460W | Unable to determine if TCP/IP ports are available. |
Cause: An error occurred while trying to verify if the specified TCP/IP ports are already in use.
Action: Ensure that the ports specified are not listed in the services file as being in use by another application.
DMB0462E | Unable to initialize this node. Return code = <code> |
Cause: Extender startup encountered an error while trying to initialize the current node.
Action: Contact IBM support.
DMB0495E | This version of AIV Extenders doesn't support long names. |
Cause: You have specified a long identifier when calling an extenders administration API or when issuing a db2ext command-line command. The maximum length of identifiers supported in this version of the AIV Extenders is:
Check the API call or the command to be sure to use short identifiers.
DMB0496E | Invalid table name or column name is specified. |
Cause: You have specified an invalid identifier when calling an extenders administration API or when issuing a db2ext command-line command. The likely cause is that the identifier name was too long. Check the Quick Beginnings book for information on the lenght of names in UDB Db2.
Check the API call or the command to be sure to use short identifiers.
DMB497E | Access denied on DB2MMDATAPATH. |
Cause: (EEE only) You have specified a directory or shared name that is not accessible on all nodes. The directory or shared name specified when creating an instance of DB2 extenders must exist and be accessible on all nodes. Check that the directory or shared name you specified when you created the instance exists on all nodes and is accessible.
DMB498E | At lease one part of DB2MMDATAPATH path is not a directory. |
Cause: (EEE only) You have specified a directory or shared name that is not a directory on a node. The directory or shared name specified when creating an instance of DB2 extenders must exist and be accessible on all nodes. Check that the directory or shared name you specified when you created the instance exists on all nodes and is accessible.
DMB499E | The DB2MMDATAPATH string is too long. |
Cause: (EEE only) You have specified a directory or shared name that has caused the variable DB2MMDATAPATH to be too long. The directory or shared name specified when creating an instance of DB2 extenders must exist and be accessible on all nodes. Check that the directory or shared name you specified when you created the instance is correct and that it exists and is accessible on all nodes.
DMB500E | The DB2MMDATAPATH directory does not exist. |
Cause: (EEE only) You have specified a directory or shared name that does not exist on a node. The directory or shared name specified when creating an instance of DB2 extenders must exist and be accessible on all nodes. Check that the directory or shared name you specified when you created the instance exists on all nodes and is accessible.
DMB501E | Unknown stat( ) error on DB2MMDATAPATH. |
Cause: (EEE only) A problem was encountered when trying to access a directory or shared name that in this environment variable. The directory or shared name specified when creating an instance of DB2 extenders must exist and be accessible on all nodes. Check that the directory or shared name you specified when you created the instance exists on all nodes and is accessible.
DMB502E | DB2MMDATAPATH exists but is not a directory. |
Cause: (EEE only) You have specified the name for a directory or shared name but the name is not that of a directory or shared name on all nodes. The directory or shared name specified when creating an instance of DB2 extenders must exist and be accessible on all nodes. Check that the directory or shared name you specified when you created the instance exists on all nodes and is accessible.
DMB503E | DB2MMDATAPATH exists but is not readable. |
Cause: (EEE only) You have specified a directory or shared name that can not be read from on all nodes. The directory or shared name specified when creating an instance of DB2 extenders must exist and be accessible on all nodes. Check that the directory or shared name you specified when you created the instance exists on all nodes and is accessible.
DMB504E | DB2MMDATAPATH exists but is not writable. |
Cause: (EEE only) You have specified a directory or shared name that can not be written to on all nodes. The directory or shared name specified when creating an instance of DB2 extenders must exist and be accessible and read/write on all nodes. Check that the directory or shared name you specified when you created the instance exists on all nodes and is accessible.
DMB504E | DB2MMDATAPATH is not set. |
Cause: (EEE only) The environment variable DB2MMDATAPATH was not set when you created a DB2 extenders instance. If this is a new DB2 extenders instance, drop the instance using DMBIDROP; then recreate it specifying the -q option correctly.
If this is not a new DB2 extender instance, then:
DMB506E | Instance name is not set. |
Cause: The DB2INSTANCE environment variable was not set when you ran DMBSTART. Make sure that DB2START works properly before starting DB2 extenders services with DMBSTART.
DMB507E | dmbssd name node arguments |
Cause: Internal error. Contact your IBM representative.
DMB508E | Node number must be greater than or equal to 0. |
Cause: Internal error. Contact your IBM representative.
DMB509E | This program should not be started manually. |
Cause: Internal error. Contact your IBM representative.
DMB512E | Usage: arguments dmbInstName. |
Cause: Internal error. Contact your IBM representative.
DMB513E | Name is not a valid instance name. |
Cause: The name you specified when trying to drop a DB2 extender instance was not recognized as the name of an instance. Check that you specified the a correct instance name and that the directory $INSTHOME/dmb with that name exists
DMB514I | Neither server nor client has been installed on this instance. |
Cause: You have tried to drop a DB2 extenders instance, but the extenders haven't been installed. Check to make sure your installation is correct and that the installation directories have not been renamed.
DMB515I | The DB2 instance was NOT dropped. The DB2 instance can be dropped by invoking DB2IDROP. |
Cause: When you drop a DB2 extenders instance, the associated instance of DB2 is not dropped. Use DB2IDROP to drop the DB2 instance.
DMB518E | Unexpected error. Function = function name, Return Code = return_code. |
Cause: An unexpected error was encountered when you tried to create or drop a DB2 extenders instance. Check that your installation and set up are correct.
DMB520E | You cannot execute this program as root. |
Cause: Check that you have the correct authority to perform this action.
DMB521E | An attempt to change permissions for name failed. |
Cause: Make sure you have the correct authority to change permissions.
DMB522E | An attempt to change ownership for name failed. |
Cause: Make sure you have the correct authority to change ownership.
DMB523E | An attempt to change group ownership for name failed. |
Cause: Make sure you have the correct authority to change group ownership.
DMB524E | The file or directory name already exists. |
Cause: A file or a directory with the name you specified already exists. Choose a different name and rerun the command.
DMB525E | An attempt to create name failed. |
Cause: Check that you have the correct authority to preform this action.
DMB526E | The file or directory name is missing. |
Cause: The file or the directory indicated could not be found. Check that you specified a valid file or directory name.
DMB527E | An attempt to copy the file or directory name to name failed. |
Cause: Check that you have the correct authority to copy the file or directory; check that there is enough space for the copy.
DMB528E | The user ID user_ID is invalid. |
Cause: You specified an invalid user ID. Check the user ID, and rerun the command.
DMB529E | The primary group group of the user ID user_ID is invalid. |
Cause: You specified an invalid primary group for the user ID. Check for the correct primary group, and rerun the command.
DMB530E | The instance name name is invalid. |
Cause: You specified an invalid name when trying to create or work with an instance. Check for a valid instance name, and rerun the command.
DMB531E | Unsupported Operating System name, version version_number. |
Cause: You have tried to run this command on an unsupported version of the operating system. Check the requirements for performing this operation.
DMB535E | The specified file cannot be accessed. |
Cause: Check that you have access to the file before running this command.
DMB0533E | The API <API name> is not supported for a partitioned database server environment. |
Cause: You cannot use the API specified in a partitioned database environment.
Action: Refer to the section on the API specified for information on how to handle this function in your application.
DMB0534E | UDF not supported. |
Cause: You cannot use the user-defined function in a partitioned database environment.
Action: Check the message SQL0443N to determine which UDF encountered a problem. Refer to the section on that UDF for information on how to handle this function in your application.