DB2 Data Links Manager Quick Beginnings

Appendixes

Appendix A. DB2 Data Links Manager Errors and User Responses

This section describes the errors, messages, causes, and required actions to errors that you may encounter when using the Data Links File Manager on AIX or Windows NT.

On AIX, error messages are directed to the INSTHOME/sqllib/db2dump/db2diag.log file, where INSTHOME is the home directory of the instance owner. Error messages are also returned to the user who executed the dlfm command.

On Windows NT, error messages are directed to the x:\sqllib\instance\db2diag.log file, where x: is the directory where you installed DB2 Data Links Manager and instance is the name of the instance for which you want to change the diagnostic setting. Error messages are also returned to the user who executed the dlfm command.

DLFM001I:
Data Links File Manager started.

Cause:
The Data Links File Manager has started successfully.

Action:
None.

DLFM101E:
Error in the Data Links File Manager start-up. See the appropriate reason code.

Reason Code -1:
The Data Links File Manager is already running.

Cause:
Possible causes are:
  1. The Data Links File Manager is already running.
  2. The Data Links File Manager (or one of its agents) is still active, even after stopping the Data Links File Manager.

Action:
Perform the following steps:
  1. Log on to the system as the DB2 Data Links Manager Administrator.
  2. Enter the dlfm stop command to stop the Data Links File Manager.
  3. Enter the dlfm shutdown command to shutdown the Data Links server.
  4. Start the Data Links File Manager by entering the dlfm start command.

Reason Code -2:
Initialization of the Data Links File Manager log manager failed.

Cause:
There is a problem in initializing the Data Links File Manager log manager.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Report the problem to an IBM technical service representative.

Reason Code -3:
Data Links File Manager initialization failed.

Cause:
Possible causes are:
  1. An operating system call failed.
  2. There was an error in initializing global shared resources for the Data Links File Manager.
  3. There was an error in initializing a critical Data Links File Manager service.
  4. There was an error in initializing a communication service.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Contact the system administrator for further help.

DLFM201E:
Error in the Data Links File Manager registration service. See the appropriate reason code.

Reason Code -1:
There is an invalid database server registration entry.

Cause:
The database_name, instance_name, or node_name parameters in the registration entry are not valid.

Action:
The DB2 Data Links Manager Administrator should register the correct values for the database_name, instance_name, or node_name parameters.

For more information, see Listing or Adding Registered File Systems Under the Control of a Data Links Filesystem Filter on AIX.

Reason Code -2:
Error in database registration.

Cause:
There is an error with the Data Links File Manager log manager.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Report the problem to an IBM technical service representative.

Reason Code -3:
Invalid prefix entry.

Cause:
Possible causes are:
  1. A file system does not exist on the local system.
  2. On AIX, the file system is not mounted using the specified Data Links Filesystem Filter.
  3. On Windows NT, the share drive is not loaded using the specified Data Links Filesystem Filter.

Action:
The DB2 Data Links Manager Administrator should mount or load the file system using the Data Links Filesystem Filter as the specified file prefix.

Reason Code -4:
Error in prefix registration.

Cause:
There is an error with the Data Links File Manager log manager.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Report the problem to an IBM technical service representative.

For more information, see Listing or Adding Registered File Systems Under the Control of a Data Links Filesystem Filter on AIX.

DLFM301E:
Data Links File Manager agent closing connection with remote database.

Cause:
The Data Links File Manager log manager was interrupted while the Data Links File Manager was running.

Action:
Perform the following steps:
  1. Log on to the system as the DB2 Data Links Manager Administrator.
  2. Enter the dlfm shutdown command to shutdown the Data Links server.
  3. Start the Data Links File Manager by entering the dlfm start command.

DLFM401E:
Connection management service failed and therefore the database could not connect to the Data Links File Manager. See the appropriate action (Connect or Disconnect).

Connect

Cause:
The database failed to connect to the Data Links File Manager. The database is not registered with the Data Links File Manager, or there was an error accessing system shared resources, or an operating system error occurred.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. The DB2 Data Links Manager Administrator should register the database with the Data Links File Manager or report the problem to an IBM technical service representative.

Disconnect

Cause:
Possible causes are:
  1. There is an error with the Data Links File Manager log manager.
  2. There was an error encountered when accessing system shared resources or an operating system error occurred.
  3. The Data Links File Manager log file is corrupt.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Restart the Data Links File Manager (if needed).
  3. Report the problem to an IBM technical service representative.

DLFM501E:
Transaction management service failed. See the appropriate action (AbortTxn, BeginTxn, CommitTxn, PrepareTxn, QueryARTxn, or QueryPreparedTxn).

AbortTxn

Cause:
Possible causes are:
  1. There is an error with the Data Links File Manager log manager.
  2. There was an error encountered when accessing system shared resources or an operating system error occurred.
  3. The Data Links File Manager log file is corrupt.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Restart the Data Links File Manager (if needed).
  3. Report the problem to an IBM technical service representative.

BeginTxn

Cause:
Possible causes are:
  1. There is an error with the Data Links File Manager log manager.
  2. There was an error encountered when accessing system shared resources or an operating system error occurred.
  3. The Data Links File Manager log file is corrupt.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Restart the Data Links File Manager (if needed).
  3. Report the problem to an IBM technical service representative.

CommitTxn

Cause:
Possible causes are:
  1. There is an error with the Data Links File Manager log manager.
  2. There was an error encountered when accessing system shared resources or an operating system error occurred.
  3. The Data Links File Manager log file is corrupt.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Restart the Data Links File Manager (if needed).
  3. Report the problem to an IBM technical service representative.

PrepareTxn

Cause:
  1. There is an error with the Data Links File Manager log manager.
  2. There was an error encountered when accessing system shared resources or an operating system error occurred.
  3. The Data Links File Manager log file is corrupt.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Restart the Data Links File Manager (if needed).
  3. Report the problem to an IBM technical service representative.

QueryARTxn

Cause:
Possible causes are:
  1. There is an error with the Data Links File Manager log manager.
  2. There was an error encountered when accessing system shared resources or an operating system error occurred.
  3. The Data Links File Manager log file is corrupt.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Restart the Data Links File Manager (if needed).
  3. Report the problem to an IBM technical service representative.

QueryPreparedTxn

Cause:
Possible causes are:
  1. There is an error with the Data Links File Manager log manager.
  2. There was an error encountered when accessing system shared resources or an operating system error occurred.
  3. The Data Links File Manager log file is corrupt.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Restart the Data Links File Manager (if needed).
  3. Report the problem to an IBM technical service representative.

DLFM601E:
Group management service failed. See the appropriate action (DefineGroup, DeleteDatabase, DeleteGroup, and QueryGroups).

DefineGroup

Cause:
Possible causes are:
  1. There is an error with the Data Links File Manager log manager.
  2. There was an error encountered when accessing system shared resources or an operating system error occurred.
  3. The Data Links File Manager log file is corrupt.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Restart the Data Links File Manager (if needed).
  3. Report the problem to an IBM technical service representative.

DeleteDatabase

Cause:
Possible causes are:
  1. There is an error with the Data Links File Manager log manager.
  2. There was an error encountered when accessing system shared resources or an operating system error occurred.
  3. The Data Links File Manager log file is corrupt.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Restart the Data Links File Manager (if needed).
  3. Report the problem to an IBM technical service representative.

DeleteGroup

Cause:
Possible causes are:
  1. There is an error with the Data Links File Manager log manager.
  2. There was an error encountered when accessing system shared resources or an operating system error occurred.
  3. The Data Links File Manager log file is corrupt.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Restart the Data Links File Manager (if needed).
  3. Report the problem to an IBM technical service representative.

QueryGroups

Cause:
Possible causes are:
  1. There is an error with the Data Links File Manager log manager.
  2. There was an error encountered when accessing system shared resources or an operating system error occurred.
  3. The Data Links File Manager log file is corrupt.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Restart the Data Links File Manager (if needed).
  3. Report the problem to an IBM technical service representative.

DLFM701E:
Prefix management service failed. See the appropriate action (ResolvePrefixId or ResolvePrefixName).

ResolvePrefixId

Cause:
Possible causes are:
  1. There is an error with the Data Links File Manager log manager.
  2. There was an error encountered when accessing system shared resources or an operating system error occurred.
  3. The Data Links File Manager log file is corrupt.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Restart the Data Links File Manager (if needed).
  3. Report the problem to an IBM technical service representative.

ResolvePrefixName

Cause:
The prefix for the given file is not registered with the Data Links File Manager.

Action:
The DB2 Data Links Manager Administrator should register this file with the Data Links server.

DLFM801E:
File management service failed. See the appropriate action (LinkFiles, ReleaseDelete, ReleaseRestore, Takeover, or UnlinkFile).

LinkFiles

Cause:
Possible causes are:
  1. There is an error with the Data Links File Manager log manager.
  2. There was an error encountered when accessing system shared resources or an operating system error occurred.
  3. The Data Links File Manager log file is corrupt.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Restart the Data Links File Manager (if needed).
  3. Report the problem to an IBM technical service representative.

ReleaseDelete

Cause:
The Data Links File Manager is unable to delete the file in its current state. The file was deleted or modified while it was being managed by the Data Links File Manager.

Action:
Check the status of this file and delete it if necessary.

ReleaseRestore

Cause:
The Data Links File Manager is unable to restore the original owners and the permissions of this file. The file was deleted or modified while it was being managed by the Data Links File Manager.

Action:
Check the status of this file and delete it if necessary.

Takeover

Cause:
The Data Links File Manager is unable to initiate the management of a file. The file was deleted or modified while it was being managed by the Data Links File Manager.

Action:
Check the status of this file and delete it if necessary.

UnlinkFile

Cause:
Possible causes are:
  1. There is an error with the Data Links File Manager log manager.
  2. There was an error encountered when accessing system shared resources or an operating system error occurred.
  3. The Data Links File Manager log file is corrupt.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Restart the Data Links File Manager (if needed).
  3. Report the problem to an IBM technical service representative.

DLFM9001:
The Data Links File Manager server is stopped.

Cause:
The Data Links File Manager was stopped normally or abnormally.

Action:
None required.

DLFM901E:
One of the Data Links File Manager agents terminated abnormally.

Cause:
The Data Links File Manager was stopped normally or abnormally.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Log on to the system as the DB2 Data Links Manager Administrator.
  3. Enter the dlfm shutdown command to shutdown the Data Links server.
  4. Start the Data Links File Manager by entering the dlfm start command.

DLFM905E:
There was an abnormal shutdown of the Data Links File Manager.

Cause:
There was an abnormal shutdown of the Data Links File Manager due to a problem with global shared system resources.

Action:
Perform the following steps:
  1. See the error trace information in the db2diag.log.
  2. Log on to the system as the DB2 Data Links Manager Administrator.
  3. Enter the dlfm shutdown command to shutdown the Data Links server.
  4. Start the Data Links File Manager by entering the dlfm start command.

DLFM906E: Unable to take over file.
The Transaction Management service was unable to take over the file. The error message states The Data Links Manager will attempt the operation again.

Cause
Data Links Manager failed to takeover the file that was inserted into a DATALINK column. Before commit processing could complete, one of the following may have happened:
  • The filesystem containing the file went offline.
  • The file was deleted by the user.

DLFM907E: Unable to release file.
The Transaction Management service was unable to return the file to the filesystem. The error code was . The Data Links Manager will attempt the operation again.

Cause
Data Links Manager failed to release the file to the filesystem that was deleted from a DATALINK column. Before commit processing could complete, one of the following may have happened:
  • The filesystem containing the file went offline.
  • The file was deleted by an administrative user.

Action
No user action is required. Data Links Manager will try the operation again.

DLFM908E: Repeated failures in taking over file(s) or returning file(s) to filesystem.
The Transaction Management service was unable to take-over file(s) or release file(s)after repeated attempts. The Data Links Manager has been stopped. No further activity will be allowed.

Cause
Data Links Manager failed to take over or release file(s) to the filesystem that were inserted into, or deleted from, a DATALINK column. Before commit processing could complete, one of the following may have happened:
  • The filesystem containing the file went offline.
  • The file was deleted by an administrative user.

Action
Perform the following steps:
  1. Make sure the filesystem is available and check for the existence of the file.
  2. If the file was not deleted and is now available, then restart the Data Links Manager. This should release the file and the Data Links Manager should become usable.

If the file was deleted or if the problem persists, please report the problem to an IBM technical service representative.

[ Top of Page | Previous Page | Next Page ]