I installed DB2yesterday.
The server started but then when I clicked on the control center view the following error was given...
SQL1032N No start database manager command was issued.
SQLSTATE=57019
Explanation:
The start database manager command has not been processed. It
must be processed before a stop database manager, any SQL
statement, or utility can be issued.
The command cannot be processed.
User Response:
Issue a start database manager command and resubmit the current
command.
If using multiple logical nodes, ensure the DB2NODE environment
variable is set correctly. The DB2NODE environment variable
indicates the node the application will attempt to connect to.
DB2NODE must be set to the node number of one of the nodes
defined on the same host as the application.
sqlcode : -1032
sqlstate : 57019
After clicking on the create database option the following error comes
Federated system users: this situation can also be detected by
the data source.
User Response:
Log on as a user with the correct authority and retry the failed
command or operation. Correct authorities may include SYSADM,
SYSCTRL, SYSMAINT, and DBADM. DBADM is granted on databases and
all other authorities are determined by membership in the groups
defined in the database manager configuration (eg. if
sysctrl_group in the database manager configuration file is
defined as 'beatles', then you must belong to the group 'beatles'
to have SYSCTRL authority). Refer to the Command Reference or
the SQL Reference for the listing of required authorities for the
attempted command or operation.
If you are using Kerberos authentication in a Windows
environment, ensure that you log on to the machine using a domain
account. Only domain users can use Kerberos authentication in a
Windows 2000 environment.
If you are using LDAP support, ensure that you or the DB2
Connect gateway has the authority to perform the CATALOG DATABASE,
NODE and DCS DATABASE commands. Invoke the command "UPDATE DBM
CFG USING CATALOG_NOAUTH YES" at the client or the gateway to
correct the problem.
Federated system users: if necessary isolate the problem to the
data source rejecting the request (see the problem determination
guide for procedures to follow to identify the failing data
source) and ensure that the authorization id specified has the
proper authority on that data source.
Contact the System Administrator for authority request
assistance. Do not attempt to execute the command without
appropriate authorization.