Oracle Solaris: Formatting the database and log

Use the DSMSERV FORMAT utility to initialize a server instance. No other server activity is allowed while you initialize the database and recovery log.

After you set up server communications, you are ready to initialize the database. Ensure that you log in by using the instance user ID. Do not place the directories on file systems that might run out of space. If certain directories (for example, the archive log) become unavailable or full, the server stops.

For optimal performance and to facilitate I/O, specify at least two equally sized containers or Logical Unit Numbers (LUNs) for the database. In addition, each active log and archive log should have its own container or LUN.

Setting the exit list handler

Set the DB2NOEXITLIST registry variable to ON for each server instance. Log on to the system as the server instance owner and issue this command:

db2set -i server_instance_name DB2NOEXITLIST=ON

For example: Oracle Solaris operating systems

db2set -i tsminst1 DB2NOEXITLIST=ON

Initializing a server instance

Use the DSMSERV FORMAT utility to initialize a server instance. For example, if the server instance directory is /tsminst1, issue the following commands: Oracle Solaris operating systems

cd /tsminst1
dsmserv format dbdir=/tsmdb001 activelogsize=32768
activelogdirectory=/activelog archlogdirectory=/archlog 
archfailoverlogdirectory=/archfaillog mirrorlogdirectory=/mirrorlog

Tip: If you specify multiple directories, ensure that the underlying file systems are of equal size to ensure a consistent degree of parallelism for database operations. If one or more directories for the database are smaller than the others, they reduce the potential for optimized parallel prefetching and distribution of the database.

Tip: If DB2® does not start after you issue the DSMSERV FORMAT command, you might need to disable the file system mount option NOSETUID. If this option is set on the file system that contains the DB2 instance owner directory, or on any file system that contains the DB2 database, active logs, archive logs, failover logs, or mirrored logs, the option must be disabled to start the system.

After you disable the NOSETUID option, remount the file system and then start DB2 by issuing the following command:

db2start