This command must be executed by the DB2 instance owner, in our case,
db2inst1. See Figure 91 for an example of the execution of this command on
our backend server, bdtest3.
[db2inst1@bdtest3 db2inst1]$ db2start
SQL1063N DB2START processing was successful.
Figure 91. Starting the DB2 instance
4.1.2.2 Stopping the DB2 instance
The DB2 instance is stopped with the command:
db2stop
This command must be executed by the DB2 instance owner, in our case,
db2inst1. See Figure 92 for an example of the execution of this command on
our backend server, bdtest3.
[db2inst1@bdtest3 db2inst1]$ db2stop
SQL1064N DB2STOP processing was successful.
Figure 92. Stopping the DB2 instance
In some cases, there may be active connections to a database in the DB2
instance. This DB2 database is considered to be active, and if the db2stop
command is issued, the DB2 database manager for the DB2 instance will
complain as shown in Figure 93.
[db2inst1@bdtest3 db2inst1]$ db2stop
SQL1025N The database manager was not stopped because databases are
still active
Figure 93. Stopping the DB2 instance when a database is still active
We can ensure what connections to the database exist and decide if we will
go ahead with halting the database instance. We use the
db2 list
applications
command. A sample output of this command is shown in Figure
94 on page 119.
118
Linux Web Hosting with WebSphere, DB2, and Domino




  

Home

About Services Network Support FAQ Order Contact
 

Linux Web Hosting

Our partners:Jsp Web Hosting Unlimited Web Hosting Cheapest Web Hosting  Java Web Hosting Web Templates Best Web Templates PHP Mysql Web Hosting Interland Web Hosting Cheap Web Hosting PHP Web Hosting Tomcat Web Hosting Quality Web Hosting Best Web Hosting  Mac Web Hosting 

Lunarwebhost.net  Business web hosting division of Vision Web Hosting Inc. All rights reserved