IBM PureData System for Analyticscollects all key database logs in the directory /nz/kit/logs. All logfiles are in plain text and are rotated on a regular basis. If there is a need to retain logfiles for more than 28 days, you must archive them. The logfiles are all owned by the 'nz' user.
Thisis one of the most useful when reviewing activity. This contains pg.log files which contain all details of database activity including background activity. Entries in the pg.log file can be tracked using the process id which can be obtained from the output of nzsession or dbos logfiles.
This directory can give additional detail on sessions. It contains the dbos.log files. While the pg.log (under /nz/kit/log/postgres) files tell you what has been submitted, the dbos.log file will tell you when it completes. It can also hold some useful error data.
This subdirectory holds logs for all events that may be used to generate alerts. When an event takes place, it is logged here regardless of whether a rule is created to take action or not.
backupsvr / restoresvr subdirectories
Every time an nzbackup operation is carried out, a logfile is produced in the backupsvr subdirectory. It contains details of all objects backed up and timings. This has the same output that would go to stdout if an nzbackup - v was run. Every time an nzrestore operation is carried out, a logfile is produced in the restoresvr subdirectory. It contains details of all objects restored and timings. This has the same output that would go to stdout if a nzrestore -v is run.
This contains the sysmgr process logs.The sysmgr process monitors the overall system state. Notable events being recorded here can include (but is not restricted to):
- Blade state changes
- Disk errors
- Disk or blade reallocation (for example, during failover).
Any support diagnosis is very likely to require the sysmgr.log file.
When queries complete execution, if it had a plan file, it isarchived to this directory. NPS only hold a finite number of plan files (configurable at startup - 2000 for 6.0 and earlier, 10,000 for 7.0 and later). It may be desirable to consider archiving these for a period of time for analysis in case of issues.
Core files produced by processes on the blades that are results of user written functions or exceptions in the core PureData processes are logged here. You can contact IBM support if these core files need to be analyzed.
Other Useful Subdirectories
Many other processes have subdirectories here but are of more limited use - if these need to be reviewed, then support will direct on which ones to provide.
Some of the more useful include:
alcapp / alcloader- related to query history load processes and can give details if you have errors loading this data.
startupsvr- records the process that starts the other database services.
sendMail- documents the successes or errors when trying to email from the system.
Likes before 03/04/2016 - 1
Views before 03/04/2016 - 426