InfoScale™ 9.0 Storage and Availability Management for DB2 Databases - AIX, Linux
- Section I. Storage Foundation High Availability (SFHA) management solutions for DB2 databases
- Overview of Storage Foundation for Databases
- About Veritas File System
- Overview of Storage Foundation for Databases
- Section II. Deploying DB2 with InfoScale products
- Deployment options for DB2 in a Storage Foundation environment
- Deploying DB2 with Storage Foundation
- Deploying DB2 in an off-host configuration with Storage Foundation
- Deploying DB2 with High Availability
- Deployment options for DB2 in a Storage Foundation environment
- Section III. Configuring Storage Foundation for Database (SFDB) tools
- Configuring and managing the Storage Foundation for Databases repository database
- Configuring the Storage Foundation for Databases (SFDB) tools repository
- Configuring authentication for Storage Foundation for Databases (SFDB) tools
- Configuring and managing the Storage Foundation for Databases repository database
- Section IV. Improving DB2 database performance
- About database accelerators
- Improving database performance with Quick I/O
- About Quick I/O
- Improving DB2 database performance with Veritas Concurrent I/O
- Section V. Using point-in-time copies
- Understanding point-in-time copy methods
- Volume-level snapshots
- Storage Checkpoints
- Considerations for DB2 point-in-time copies
- Administering third-mirror break-off snapshots
- Administering Storage Checkpoints
- Database Storage Checkpoints for recovery
- Backing up and restoring with Netbackup in an SFHA environment
- Understanding point-in-time copy methods
- Section VI. Optimizing storage costs for DB2
- Section VII. Storage Foundation for Databases administrative reference
- Storage Foundation for Databases command reference
- Tuning for Storage Foundation for Databases
- Troubleshooting SFDB tools
SFDB logs
The SFDB commands generate logs that can be used to narrow down to the actual problem.
Log files are generated in the location
/var/vx/vxdba/logs
.There are two kind of logs:
User logs are generated in the <user> folder.
Logs from vxdbd and other root operations are generated in the logs folder.
The user log files have the naming convention: log_<service>_<app>_<service_id><app_id>.log.
A system.log is also present until vxsfadm can recognize the service and the application identifiers.
The vxdbd logs have the name vxsfaed.log.
A system.log also exists for all root operations performed.
The log files are archived after they reach a threshold of 1MB and are backed up as log_<service><application><application_identifier><service_identifier>.log.<randomnumber>
Every log file has a pointer to the previously archived log.
Log levels can be set using the environment variable SFAE_LOG_LEVEL.
The following additional environment variables can be set that override SFAE_LOG_LEVEL:
APP_LOG_LEVEL: Log application-specific operations.
SER_LOG_LEVEL: Log VxFS/VxVM stack specific operations.
REP_LOG_LEVEL: Log repository operations.
FSM_LOG_LEVEL: Log vxsfadm engine-specific operations.
The log levels can be set to the following levels:
FATAL: Logs only fatal messages.
ERROR: Logs errors and above messages.
WARN: Logs warning and above messages.
INFO: Logs info and above messages.
DEBUG: Logs debug and above messages.
The default log level is DEBUG.
The actual log messages appear in the following format:
yyyy/mm/dd hh:mm:ss: <loglevel> : <module> : <message>
For example: