BFGDB0001 - BFGDB9999
- BFGDB0001E
- A message was rejected, but the database logger was unable to put it onto the reject queue. The transaction has been rolled back. The error reported by the MQ subsystem was: <insert_0>
- Severity
- 20 : Error
- Explanation
- A message was rejected, but the database logger was unable to put it onto the reject queue. The transaction has been rolled back so that the problem message is now on the input queue (which may be a managed subscription queue if the database logger is fed from a subscription).
- Response
- Examine your MQ configuration and the error message from the MQ subsystem to establish why the database logger cannot access the configured reject queue. In addition, inspection of the rejected message may reveal further problems.
- BFGDB0002E
- A message was rejected, but the database logger has already placed <insert_0> or more consecutive messages on the reject queue (<insert_1>). The database logger will rollback the transaction and retry at intervals until the message is accepted. The reason for the latest rejection was: <insert_2>
- Severity
- 20 : Error
- Explanation
- A large number of messages have been rejected without any being successfully processed. This suggests that the problem may not be with individual messages but with the general configuration instead. As in the case of other possible configuration errors, the database logger has entered an error state in which it will retry periodically until the error is resolved.
- Response
- Check the usr.WMQFTE_ReasonForRejection property of the messages on the reject queue to determine why they were rejected, and rectify the problem. The reason reported in this log entry relates to the last message rejected, in order to give an initial indication, but may not apply to all rejected messages. The database logger will restart normal processing when the message currently at the head of the input queue is successfully processed; if this message is in fact invalid you should either remove it manually or stop and restart the database logger.
- BFGDB0003E
- A problem occurred with the database. The database driver reported the following details: SQL State [<insert_0>], Error Code [<insert_1>], Message [<insert_2>]
- Severity
- 20 : Error
- Explanation
- The database logger was notified of a problem with the database that prevents message data being loaded. This may be due to an invalid message.
- Response
- Refer to your database's documentation to determine the correct response to the problem that was reported.
- BFGDB0004E
- An MQ problem occurred. The reported reason code was <insert_0> and the reported message text (if any) was: <insert_1>. You should examine the MQ error log (for example, /var/mqm/qmgrs/COORD_QM/errors/AMQERR01.LOG ) for further information about the problem.
- Severity
- 20 : Error
- Explanation
- The database logger encountered an MQ error.
- Response
- Refer to the MQ documentation to determine the cause of this error, and rectify it.
- BFGDB0005E
- A serious error has occurred, and the database logger will stop. Messages in progress will be rolled back to the queue manager. See the preceding log entry for details.
- Severity
- 20 : Error
- Explanation
- An error has occurred which means the database logger cannot continue to operate. Any messages not yet committed to the database will be rolled back to the queue manager.
- Response
- Examine the previous message in the log to determine the cause of the problem and the action to take. When the problem has been resolved, restart the database logger.
- BFGDB0006E
- The configuration file (<insert_0>) could not be read due to the following problem: <insert_1>
- Severity
- 20 : Error
- Explanation
- The database logger tried to read its configuration file, but was unable to do so due to an input/output problem.
- Response
- Examine the reported problem text to determine why the database logger could not read the file. Rectify the problem.
- BFGDB0007W
- A parser used by the database logger reported a problem. The type of exception was: <insert_0> and the detailed message was: <insert_1>
- Severity
- 10 : Warning
- Explanation
- A parsing subsystem, which the database logger uses to manipulate data, reported a serious problem and cannot continue to operate.
- Response
- Use the message reported by the parser to determine the cause of the problem and if possible rectify it, or contact the IBM support center for further assistance.
- BFGDB0008W
- The message is of an unexpected format which could not be identified.
- Severity
- 10 : Warning
- Explanation
- A message received by the database logger could not be understood. The message will be rejected to the configured reject queue.
- Response
- Examine the message to determine why it could not be understood. If the message is unrelated to WMQFTE you should examine your MQ configuration to determine why the message was delivered to the WMQFTE database logger.
- BFGDB0009W
- The message could not be decoded due to a parser problem. The type of exception was: <insert_0> and the detailed message was: <insert_1>
- Severity
- 10 : Warning
- Explanation
- A message received by the database logger could not be identified because a parser reported a problem when trying to decode it. The message will be rejected to the configured reject queue.
- Response
- Examine the message to determine why it could not be understood. If the message is unrelated to WMQFTE you should examine your MQ configuration to determine why the message was delivered to the WMQFTE database logger.
- BFGDB0010W
- A parsing library reported a problem while decoding data from the message. The reported problem was: <insert_0>
- Severity
- 10 : Warning
- Explanation
- The database logger uses parsing libraries to access the data in the messages it receives. The parsing library reported a problem. The message will be rejected to the configured reject queue.
- Response
- Examine the message and the reported problem to determine why the message could not be understood. If the message is unrelated to WMQFTE you should examine your MQ configuration to determine why the message was delivered to the WMQFTE database logger.
- BFGDB0011W
- The data value represented by "<insert_0>" could not be located in the message.
- Severity
- 10 : Warning
- Explanation
- An attribute which was expected to be in the message could not be found, and so the message cannot be correctly stored. The message will be rejected to the configured reject queue.
- Response
- Examine the rejected message to ensure it is a valid WMQFTE message. If you are upgrading your WMQFTE installation, ensure that you do so in the recommended order.
- BFGDB0012W
- The message refers to a schedule which does not exist in the database. The schedule is number <insert_0>, stored on agent <insert_1>.
- Severity
- 10 : Warning
- Explanation
- A message indicating a transfer start was received. The message included a scheduleLog element, indicating that the transfer was started by a schedule. However, there is no record in the database of this schedule having been set up, and so its details are unknown. Because these details are not available, the transfer start event cannot be properly recorded. For this reason, the message will be rejected to the configured reject queue.
- Response
- This message may result from ScheduleLog messages not reaching the database logger. Check your MQ configuration, especially the database logger's subscription, to ensure that all published ScheduleLog and TransferLog messages are received.
- BFGDB0013W
- A numeric message value could not be recognised as a valid number. The value that could not be converted was: <insert_0>
- Severity
- 10 : Warning
- Explanation
- A piece of data in the message, which was expected to be of numeric format, could not be recognised as a valid number. The message will be rejected to the configured reject queue.
- Response
- Examine the rejected message to ensure it is a valid WMQFTE message. If you are upgrading your WMQFTE installation, ensure that you do so in the recommended order.
- BFGDB0014E
- There is a problem with the following property or properties in the configuration file: <insert_0>.
- Severity
- 20 : Error
- Explanation
- One or more configuration properties were set to invalid values, or are mutually incompatible, or have other problems preventing the database logger using the configuration.
- Response
- Review the documentation on the configuration file properties to determine why it is invalid, and correct it.
- BFGDB0015I
- The MQ object <insert_0>, which is the source of messages for this database logger, is in use. The database logger will retry in ten seconds.
- Severity
- 0 : Information
- Explanation
- The subscription or queue which provides log messages to the database logger is in use and so the database logger cannot connect to it. If the database logger was previously connected within a short time, the object may still be marked as "in use" because of the previous connection. In this case the queue manager will automatically clear the "in use" marker after a short time, and the database logger will then be able to connect. The connection will be retried every ten seconds, so if this kind of stale marker is the problem it will be resolved without further intervention.
- Response
- If the database logger was recently restarted, and the connection succeeds after a small number of retries, no action is required. If the connection does not succeed, investigate whether there is another application (for example, another database logger) using the object named in the message.
- BFGDB0016E
- The database reported a problem related to the XA transaction standard. The reported problem was: <insert_0>
- Severity
- 20 : Error
- Explanation
- The database logger uses XA to coordinate transactions with the queue manager and the database. The database reported a problem in this area.
- Response
- Refer to the documentation for your database and for MQ.
- BFGDB0017W
- An IO problem prevented the database logger reading a message. The reported problem was: <insert_0>
- Severity
- 10 : Warning
- Explanation
- The database logger received an MQ message but was unable to read its contents. The message will be rejected to the configured reject queue.
- Response
- Examine the message on the reject queue to determine why it could not be read. If the message is unrelated to WMQFTE you should examine your MQ configuration to determine why the message was delivered to the WMQFTE database logger.
- BFGDB0018E
- An MQ problem occurred while the database logger was <insert_0>. The reported reason code was <insert_1> and the reported message text (if any) was: <insert_2> You should examine the MQ error log (for example, /var/mqm/qmgrs/COORD_QM/errors/AMQERR01.LOG ) for further information about the problem.
- Severity
- 20 : Error
- Explanation
- The database logger encountered an MQ error.
- Response
- Refer to the MQ documentation to determine the cause of this error, and rectify it.
- BFGDB0019W
- The update was processed by the database manager, but the database logger application deems it to have failed because <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The database software processed an SQL command and considered it to have executed successfully. However, the result of this processing was not acceptable to the application for the stated reason. The message will be rejected to the configured reject queue.
- Response
- Examine the rejected message to ensure it is a valid WMQFTE message. If you are upgrading your WMQFTE installation, ensure that you do so in the recommended order.
- BFGDB0020I
- The MQ object <insert_0>, which was previously in use, has now been successfully opened.
- Severity
- 0 : Information
- Explanation
- The subscription or queue which provides log messages to the database logger was in use and so the database logger could not connect to it. The database logger retried the connection, and has now succeeded.
- Response
- No action is required.
- BFGDB0021E
- During error handling, the database logger attempted to roll back the current transaction, but was unable to do so. The database logger will now end, causing the queue manager to roll back automatically. The cause of the failed roll back was: <insert_0>
- Severity
- 20 : Error
- Explanation
- While handling an error (which should be mentioned above this message) the database logger attempted to roll back the transaction to return one or more messages to the queue manager. However, the queue manager refused to allow the rollback to take place. The database logger will end which, on platforms other than z/OS, will cause the queue manager to attempt an automatic roll-back. On z/OS the transaction may need to be resolved manually.
- Response
- Review the MQ documentation to understand the reason for the failure to roll back, and the appropriate action to take in that case.
- BFGDB0022W
- The message refers to a transfer which does not exist in the database. The transfer ID is: <insert_0>
- Severity
- 10 : Warning
- Explanation
- A message indicating a transfer progress or completion was received. However, there is no record in the database of this transfer having been started, and so its details are unknown. Because these details are not available, the transfer event cannot be properly recorded. For this reason, the message will be rejected to the configured reject queue.
- Response
- This message may result from messages not reaching the database logger. Check your MQ configuration, especially the database logger's subscription, to ensure that all published Log messages are received. It may also be caused by a preceding transfer-start message having been rejected. Check whether any other messages on the reject queue relate to this transfer, and if so resolve the problem that caused them to be rejected.
- BFGDB0023I
- The database logger has completed startup activities and is now running.
- Severity
- 0 : Information
- Explanation
- This message is produced when the database logger has performed all its required one-time startup tasks and is about to retrieve and process its first message.
- Response
- No action is required.
- BFGDB0024E
- The database logger encountered an unexpected problem and will stop. The exception identifying the problem is: <insert_0>
- Severity
- 20 : Error
- Explanation
- An unexpected exception was encountered, which may represent a serious misconfiguration or a program error.
- Response
- Contact the IBM support center, supplying the exception details contained in the message and any trace and FFDC files generated.
- BFGDB0025E
- A problem occurred while locating the database logger''s configuration. The text of the problem is: <insert_0>
- Severity
- 20 : Error
- Explanation
- The database logger tried to locate its configuration file, but was unable to do so due to an input/output problem.
- Response
- Examine the reported problem text to determine why the database logger could not read the file. Rectify the problem.
- BFGDB0026W
- The MQ message-type was <insert_0> instead of MQMT_DATAGRAM.
- Severity
- 10 : Warning
- Explanation
- Normal MQ messages have their message-type field set to MQMT_DATAGRAM. This is the only kind of message that the database loader should receive. Non-datagram messages are rejected because in rare cases they could represent an attempt to breach security. This is because certain types of message (for example, report messages) are created with the authority of the queue manager rather than a user. \nHowever, in most cases, receiving incorrectly-typed messages will be due to an MQ configuration problem rather than a security breach.
- Response
- Examine your MQ configuration, to determine the origin of the message.
- BFGDB0027W
- A message was found on the command queue which was an FTE message but did not represent a command to the database logger.
- Severity
- 10 : Warning
- Explanation
- Only database logger commands conforming to the relevant schema should be on the database logger command queue. This message appeared to be an FTE log message of the kind usually found on the database logger's input queue or subscription. Non-command messages on the command queue are discarded, so you should avoid sending log messages here.
- Response
- Determine why a log message was found on the command queue, and, if relevant, prevent the problem from recurring.
- BFGDB0028W
- The database logger detected a problem related to a message on its command queue (<insert_0>). See the next log entry for more information. The message has been discarded.
- Severity
- 10 : Warning
- Explanation
- A problem was encountered related to an individual message on the database logger's command queue. Another log entry will be output containing more specific information about the problem.
- Response
- See the next entry in this log to determine the problem with the message.
- BFGDB0029E
- The database logger encountered a messaging problem while attempting to read its command queue (<insert_0>). See the next log entry for more information.
- Severity
- 20 : Error
- Explanation
- A problem was encountered related to the database logger's command queue. Another log entry will be output containing more specific information about the problem.
- Response
- See the next entry in this log to determine the problem with the messaging system.
- BFGDB0030I
- The database logger is shutting down.
- Severity
- 0 : Information
- Explanation
- The database logger received a command message to shut down, which it will now do. The command message has been logged in the database.
- Response
- If you initiated this shutdown, no action is required. If the shutdown is unexpected, examine the database to determine the origin of the command message.
- BFGDB0031E
- The DB2 driver file could not be loaded. Ensure that the wmqfte.database.driver property points to the db2jcc.jar file in your DB2 installation.
- Severity
- 20 : Error
- Explanation
- The database logger could not load a DB2 driver class. This class is normally provided in the file db2jcc.jar, as part of a DB2 installation. The precise location of this file may vary by platform and DB2 version; a typical location (for DB2 9.5 on AIX) is /opt/IBM/db2/V9.5/java/db2jcc.jar
- Response
- Ensure that the wmqfte.database.driver property points to the db2jcc.jar file in your DB2 installation.
- BFGDB0032E
- The database logger could not perform a database operation because it lacks the necessary permissions. The following message from the database should enable you to identify the user, operation, and table or other object concerned: <insert_0>
- Severity
- 20 : Error
- Explanation
- The database logger attempted an operation, such as an INSERT, on the database. The database refused to perform the operation because the user ID under which the database logger is operating has insufficient permissions to perform the operation. The original error message from the database is included to enable you to identify the specific permission that is missing.
- Response
- Ensure that the database logger is running as the proper user, and that permissions have been set correctly on the tables used by the database logger.
- BFGDB0033E
- A database object required by the database logger was not found. Ensure that the database logger is connected to the correct database and that the required tables have been created. The following message from the database should enable you to identify the table or other object concerned: <insert_0>
- Severity
- 20 : Error
- Explanation
- The database reported that an object referred to by the database logger did not exist. If this is the first time you have run the database logger, the most likely reason is that the provided SQL file has not been run against the database.
- Response
- If the SQL file from the FTE product directory has not yet been run, use your database's tools to import the table definitions it contains. Otherwise, examine the message from the database included in this error message to determine why the object cannot be found.
- BFGDB0034E
- A database column required by the database logger was not found. This indicates that the table structure in the database is not correct for this version of the database logger. The following message from the database should enable you to identify the column concerned: <insert_0>
- Severity
- 20 : Error
- Explanation
- The database reported that a column referred to by the database logger did not exist. If you have previously used an earlier version of this application, the most likely reason is that the versions of the table structure and the application do not match. Otherwise, the table structure may have been manually altered in a way incompatible with the database logger application.
- Response
- Compare the SQL file shipped or installed with your current version of the database logger against the database itself, and ensure that the table and column names match.
- BFGDB0035E
- A Java reflection problem occurred while accessing the database driver. Ensure that the file referred to by the wmqfte.database.driver property is a valid JDBC driver for a supported database. The reported problem was: <insert_0>
- Severity
- 20 : Error
- Explanation
- The Java classes provided as a JDBC driver could not be used, probably because they did not match the interface expected by the database logger. This could be due to incorrectly setting the wmqfte.database.driver property to point to a file that is not a valid JDBC driver for a supported database.
- Response
- Ensure that wmqfte.database.driver is set correctly and that you are using a supported database.
- BFGDB0036E
- Websphere MQ reported a serious problem when the database logger attempted to commit a transaction. To preserve data integrity, the database logger will stop.
- Severity
- 20 : Error
- Explanation
- A problem (which should be listed separately in this log) was reported during an MQ commit operation. Continuing to operate when transaction support is behaving abnormally risks corrupting data, and so the database logger will shut down.
- Response
- Examine the MQ problem report immediately before this entry, together with the MQ error logs. Resolve the problem and restart the database logger.
- BFGDB0037W
- The reason that this message was rejected is not known.
- Severity
- 10 : Warning
- Explanation
- The message has been backed out multiple times. This implies that it cannot be correctly handled, and so it has been placed on the reject queue. The database logger maintains a record of the messages it explicitly backs out so that the reason for rejecting them can be reported. However, when this message was being prepared for the reject queue, no such record was found. This could occur if multiple applications use the input queue simultaneously.
- Response
- Examine the rejected message itself to discover, if possible, why it was rejected. Ensure that no other application is causing messages to be backed-out to the database logger input queue (which may be a system-managed queue if the default subscription is used).
- BFGDB0038E
- A serious error has occurred. Messages in progress have been rolled back to the queue manager. The database logger will now refresh its internal state and rebuild its connections to MQ and the database before restarting processing. See the preceding log entry for details of the error.
- Severity
- 20 : Error
- Explanation
- An error has occurred which means the database logger cannot continue normally. The internal parts of the application will be restarted in order to continue processing with a fresh connection to MQ and the database.
- Response
- Examine the previous message in the log to determine the cause of the problem and the action to take.
- BFGDB0039E
- The DB2 driver could not load the native library it requires. Ensure that the wmqfte.database.native.library.path property points to the appropriate library directory (for example, /opt/IBM/db2/V9.5/lib64/ ) in your DB2 installation.
- Severity
- 20 : Error
- Explanation
- The database logger could not load a DB2 native (non-Java) library file.
- Response
- Ensure that the wmqfte.database.native.library.path property points to the appropriate library directory.
- BFGDB0040E
- The database named in the databaselogger.properties file could not be found. Ensure that you have created the database instance and that its name matches the name in the properties file. The message from the database driver is: <insert_0>
- Severity
- 20 : Error
- Explanation
- The value of the wmqfte.database.database.name property does not match a database accessible to the database logger.
- Response
- Ensure that the database named in the properties file exists.
- BFGDB0041E
- The Oracle driver file could not be loaded. Ensure that the wmqfte.database.driver property points to the ojdbc14.jar file in your Oracle installation.
- Severity
- 20 : Error
- Explanation
- The database logger could not load a Oracle driver class. This class is normally provided in the file ojdbc14.jar, as part of an Oracle installation.
- Response
- Ensure that the wmqfte.database.driver property points to the ojdbc14.jar file in your Oracle installation.
- BFGDB0042E
- The configured database platform is not supported on z/OS.
- Severity
- 20 : Error
- Explanation
- The database logger is running on z/OS and attempted to load the driver for a database whose use on that platform is not supported.
- Response
- Check the properties file to ensure that the correct database provider is configured.
- BFGDB0043W
- The message could not be stored in the database because to do so would violate a uniqueness constraint. A likely cause is that the message is a duplicate of one that has already been inserted. The error reported by the database is: <insert_0>
- Severity
- 10 : Warning
- Explanation
- The database reported an SQLSTATE of 23505, which means that a unique index or unique constraint was violated. An example of this would be an attempt to insert a transfer when a transfer with the same identifier (the hexadecimal ID reported by fteCreateTransfer) already exists in the database. The database error included in the message should enable you to determine which index or constraint was involved.
- Response
- Ensure that your handling of log messages does not result in the database logger processing the same messages twice (re-processing rejected messages is allowed). Also check that your database does not contain an additional constraint beyond those supplied with the product. If this error persists with messages that have not already been processed, contact the IBM support center for assistance.
- BFGDB0044I
- The database logger has successfully inserted one or more messages into the database.
- Severity
- 0 : Information
- Explanation
- This log entry is displayed when a transaction is successfully committed after one or more rollback-retry cycles. It implies that the problem which formerly existed has been resolved.
- Response
- No action is required.
- BFGDB0045E
- The database schema version does not match the database logger application version.
- Severity
- 20 : Error
- Explanation
- Each version of the database logger application requires certain tables and columns in the database, some of which might be specific to that version. If you upgrade the database logger software you must upgrade the database schema to match. This message indicates that a table or column required by this version of the database logger could not be found, and so it is likely that the necessary upgrade has not taken place. Note that only a subset of the database is checked, and so the absence of this message does not prove that every required table exists.
- Response
- Ensure that the database schema has been upgraded as stated in the migration instructions for this version. Check that the database logger is connected to the correct database instance.
- BFGDB0046E
- The database tables needed by the database logger were not found. Check that you have run the schema creation script against this database instance.
- Severity
- 20 : Error
- Explanation
- The database instance to which the database logger was connected did not contain the required tables.
- Response
- Ensure that the database schema has been created as stated in the installation instructions. Check that the database logger is connected to the correct database instance.
- BFGDB0047W
- The database logger could not create the pid file <insert_0>. The process ID of this database logger is <insert_1>. The following error was reported: <insert_2>
- Severity
- 10 : Warning
- Explanation
- When the database logger starts up, it creates a pid file in the same directory as its configuration file. This file contains the process ID of the database logger, so that the correct process can be located for management using operating system tools. On this occasion, the file could not be written. The database logger will continue without it.
- Response
- Use the reported error information to determine why the file could not be written, and then rectify the problem.
- BFGDB0048W
- The database logger found too many pid files (more than <insert_0>) which appear to be locked. The process ID of this database logger is <insert_1>.
- Severity
- 10 : Warning
- Explanation
- When the database logger starts up, it creates a "pid file" in the same directory as its configuration file. This file contains the process ID of the database logger, so that the correct process can be located for management using operating system tools. While a database logger process is running, it holds a lock on the file. If a subsequent process is started while the previous one is still running, it detects this lock and creates an additional pid file instead of using the existing one.
This message indicates that a large number of locked pid files were found when trying to create one for this process. Since it is unlikely that so many database logger processes are running concurrently on the same machine, it would appear that there is a problem with the locking mechanism. Instead of creating yet another pid file, the database logger will continue without creating one.
- Response
- Examine the coordination queue manager configuration directory to see whether there is a large number of databaselogger.pid files which are locked, and whether you have a large number of database logger processes running.
- BFGDB0049E
- The database logger failed to connect to the database due to an authorization error. The error reported by the database is: <insert_0>
- Severity
- 20 : Error
- Explanation
- When the database logger has attempted to connect to the database provided for its use an error has been returned indicating that the supplied database username and password are not authorized to carry out the required operations. The most likely cause for this failure is incorrect configuration so the database logger will be stopped to allow corrections to be made.
- Response
- Examine the database logger configuration file to see if the supplied database username and password are correct. If the database is running on the same machine as the database logger also ensure that the OS user account used to start the database logger has sufficient authorization with the database.
- BFGDB0050W
- The configuration property <insert_0> is deprecated and should no longer be used.
- Severity
- 10 : Warning
- Explanation
- The configuration property specified has been deprecated. To avoid incorrect configuration remove the property from your configuration or, if a new replacement property has been provided, change the property to the new value.
- Response
- Consult the product documentation to determine the correct course of action.
- BFGDB0051I
- The database logger is running as a <insert_0>-bit process.
- Severity
- 0 : Information
- Explanation
- This message describes the bit mode of the process running the database logger.
- Response
- No action is required.
- BFGDB0052E
- An SQL error occurred while the database logger was <insert_0>. The database driver reported the following details: SQL State [<insert_1>], Error Code [<insert_2>], Message [<insert_3>]
- Severity
- 20 : Error
- Explanation
- The database logger encountered an SQL error.
- Response
- Refer to your database's documentation to determine the correct response to the problem that was reported.
- BFGDB9997I
- <insert_0>
- Severity
- 0 : Information
- Explanation
- If this message does not give enough information, check the accompanying error messages for further information.
- Response
- For further information on resolving this error, see the problem determination information on the product Web site.
- BFGDB9998W
- <insert_0>
- Severity
- 10 : Warning
- Explanation
- If this message does not give enough information, check the accompanying error messages for further information.
- Response
- For further information on resolving this error, see the problem determination information on the product Web site.
- BFGDB9999E
- <insert_0>
- Severity
- 20 : Error
- Explanation
- If this message does not give enough information, check the accompanying error messages for further information.
- Response
- For further information on resolving this error, see the problem determination information on the product Web site.