Database (`database name`) Test

The Database (database name) tests the DB2® manager status of the database name DB2 instance on the data server by running the db2status script.

Resources

The Database (database name) test uses the following resource:

The Application DB2 instance (on the data server)

Problem determination

If the Database (database name) test fails, do the following to find and resolve the access problem.

Procedure

Use the platform control tool to check the status of the components and to start and stop them as needed. Run the following command with the desired options. For component use dbsdb24app (in a standard environment) or dbsdb24appgrp (in a high availability environment) and specify your topology password for topology_password.
1. To check the status of the component run the following commands:
```
su - ibmadmin

IOCControl -a status -c component -p topology_password
```
2. To start the component run the following commands:
```
su - ibmadmin

IOCControl -a start -c component -p topology_password
```
3. To stop the component run the following commands:
```
su - ibmadmin

IOCControl -a stop -c component -p topology_password
```
If running in a standard environment, use the platform control tool to check the status of the components and to start and stop them as needed. Run the following command with the desired options. For component use db24app and specify your topology password for topology_password.
1. To check the status of the component run the following commands:
```
su - ibmadmin

IOCControl -a status -c component -p topology_password
```
2. To start the component run the following commands:
```
su - ibmadmin

IOCControl -a start -c component -p topology_password
```
3. To stop the component run the following commands:
```
su - ibmadmin

IOCControl -a stop -c component -p topology_password
```
If running in a high availability environment, use the platform control tool to check the status of the components and to start and stop them as needed. Run the following command with the desired options.
- To check the status of the primary server, specify 821 for action.
- To check the status of the standby server, specify 823 for action.
- To start the primary server, specify 141 for action.
- To start the standby server, specify 151 for action.
- To stop the primary server, specify 701 for action.
- To stop the standby server, specify 711 for action.
Specify your topology password for topology_password.
```
su - ibmadmin

IOCControl -a action -p topology_password
```
Check that there is network connectivity between the application server where the test was initiated and the data server where the database resides. This can be done by sending ping commands with both the short and fully-qualified host name of the data server from the application server. The results of the ping commands will show if the host name is being correctly resolved by the DNS or /etc/hosts file.
Review the log files for runtime exceptions.
1. On the application server review the following WebSphere® Portal logs:
  - /opt/IBM/WebSphere/wp_profile/logs/WebSphere_Portal/SystemOut.log
  - /opt/IBM/WebSphere/wp_profile/logs/WebSphere_Portal/SystemErr.log
  On the directory server, review the following Tivoli® Directory Server logs:
  - /datahome/dsrdbm01/idsslapd-dsrdbm01/logs/ibmslapd.log
  - /datahome/dsrdbm01/idsslapd-dsrdbm01/logs/db2cli.log
  - /datahome/dsrdbm01/idsslapd-dsrdbm01/logs/audit.log
Verify that the file system on the data server has not reached capacity. This can be determined by running the df -h command. The file system can be considered full even if it less than 100% used. For this reason if the df -h command returns that the file system is 90% or more full, you should consider that the file system has reached capacity.
Verify that the database manager used by the data server is started.
1. On the data server, run the following command from a command window as the Applications DB2 instance user (db2inst2).
```
db2 get snapshot for dbm | grep "Database manager status" 
```
  If the database manager is started for the database name instance, the following message is displayed: Database manager status = Active.
If the DB2 processes are not running, start them by running su - db2inst2 from the command window if running as the root user. Otherwise, run db2start to start the Database Manager.
Check the DB2 logs for errors related to the database instance used for this test. The logs are located on the data server in the /datahome/db2inst2/sqllib/db2dump directory. Check the db2diag.log in the /datahome/db2inst2/sqllib/db2dump directory for errors issued when starting the database used for this test.

What to do next