Cause: The user does not have the necessary authority at the DB2 Administration Server to perform the attempted action.
Action: Attach to the DB2 Administration Server using a user ID with the necessary Authority. Most tasks performed at the DB2 Administration Server require SYSADM authority.
Cause: An error was encountered during startup of the DB2 Administration Server.
Action: Refer to the DB2 Administration Server's First Failure Data Capture Log for additional information. Take the appropriate action as necessary and attempt to restart the DB2 Administration Server.
If the problem persists contact your technical service representative.
Cause: All processing completed normally.
Action: No further action is required.
Cause: The command was entered using invalid arguments or an invalid number of parameters.
Action: Re-submit the command with valid argument(s).
Cause: The DB2 Administration Server was not found on the machine.
Action: Create the DB2 Administration Server on the machine by entering DB2ADMIN command as follow:
DB2ADMIN CREATE
Cause: The DB2 Administration Server already exists on the machine
Action: No further action is required.
Cause: All processing completed normally.
Action: No further action is required.
Cause: All processing completed normally.
Action: No further action is required.
Cause: The DB2 Administration Server must be stopped before it can be dropped.
Action: To stop the DB2 Administration Server, enter the following command:
DB2ADMIN STOP
Cause: The DB2ADMIN START command can not be processed because the DB2 Administration Server is already active.
Action: No further action is required.
Cause: The DB2ADMIN STOP command can not be processed because the DB2 Administration Server is not active.
Action: No further action is required.
Cause: The requested operation is only valid when issued against the DB2 Administration Server.
Action: The DB2 Administration Server should be set up using the DB2ADMIN command. Refer to the Quick Beginnings for further information about the DB2ADMIN command.
Cause: To perform the requested task, the DB2 Administration Server must be running under a valid logon user account. This error is either caused by the account not being setup, or the logon user account does not contain a valid DB2 user ID.
Action: If a logon user account has been set up, then ensure that the account uses a valid DB2 user ID.
You can set up the logon user account for the DB2 Administration Server by using the following command:
DB2ADMIN SETID <userid> <password>
Cause: The DB2ADMIN command syntax is:
DB2ADMIN CREATE [/USER:<username> /PASSWORD:<password>]
DROP
START
STOP
SETID <username> <password>
/h
The command options are:
Action: Issue the DB2ADMIN command with one of the valid command options.
Cause: The request cannot be processed unless the DB2 Administration Server is active.
Action: Start the DB2 Administration Server by issuing the command DB2ADMIN START, and reissue the request.