194 Delivering Continuity and Extreme Capacity with the IBM DB2 pureScale Feature
6. Connect to the SAMPLE database again, and run the command to get the log
path information. The path is set to the shared db2log file system
(Example 3-57).
Example 3-57 Retrieve the log file path information
db2sdin1@node101:~> db2 connect to SAMPLE
Database Connection Information
Database server = DB2/LINUXX8664 10.1.0
SQL authorization ID = DB2SDIN1
Local database alias = SAMPLE
db2sdin1@node101:~> db2 get db cfg | grep 'Path to log files'
Path to log files = /db2fs/db2log/NODE0000/LOGSTREAM0000/
3.5.5 Processor binding
When a cluster caching facility and a DB2 member coexist on a single host, the
CF processes can be assigned to some processor cores to
improve performance.
To assign CF processor cores, complete the following steps:
1. Log in as an instance user, for example, db2sdin1.
2. As shown in Example 3-58, run db2stop to stop the database manager.
Example 3-58 Stop the DB2 manager
db2sdin1@node101:~> db2stop
03/13/2012 15:35:49 0 0 SQL1064N DB2STOP processing was
successful.
03/13/2012 15:35:55 1 0 SQL1064N DB2STOP processing was
successful.
SQL1064N DB2STOP processing was successful.
3. Determine the primary CF ID in your cluster by running db2instance -list
(Example 3-59, “Output of the db2instance -list command” on page 194). It is
usually 128.
Example 3-59 Output of the db2instance -list command
db2sdin1@node101:~> db2instance -list
ID TYPE STATEHOME_HOSTCURRENT_HOSTALERTPARTITION_NUMBERLOGICAL_PORT
NETNAME
Attention: Complete this task from one host in the DB2 pureScale cluster.

Get Delivering Continuity and Extreme Capacity with the IBM DB2 pureScale Feature now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.