About this task
To perform the database setup for DB2® complete the following steps. If you are
using a Windows® operating
system, begin from step 2.
If you are using Linux® operating
system or AIX® operating systems,
begin from step 1:
Procedure
- To verify that DB2 and the instance are ready for remote connectivity
using TCP/IP complete the following steps:
- Run
db2 get database manager configuration
and
verify that the value of svcename is a valid
port. for example 50000
or a reference mapped to a valid port
for example,db2c_db2inst1.
- Ensure that the configured port is not used by other
processes in the system, or blocked by a firewall that sits between
the Application Server host and the DB2 server.
- Use the
db2stop
command
to stop the DB2 instance.
Set
DB2COMM to tcpip with the command
db2set DB2COMM=tcpip
Run db2start to
start the DB2 instance again.
The DB2 server is now
ready for accessing over the network.
- Create the database that IBM® BigFix® Remote Control will
use by running the following command as the instance owner:
Note: Not
necessary when the database is local.
db2 create db databasename using codeset UTF-8 territory requiredtrerritory
where databasename is
the name required for the database. This database name must be the
name that was referenced in any configuration settings. For example,
TRCDB.
requiredtrerritory is the required
territory. For example, GB for Great Britain.
- Verify the privileges that a specific user, for the database,
needs to have.
Do not use the db2inst1 user as the
user configured to access the IBM BigFix Remote Control database.
Create a new specific user for DB2 that
has the database owner privileges.
Results
With the blank database created and ready to use, the
next step is to set up the WebSphere® server,
see Setting up the application server. It is
possible to verify that the database is set up properly by using a DB2 client to connect to the database
from another host. For more details see the DB2 Infocenter.