Books
in black and white
Main menu
Share a book About us Home
Books
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics
Ads

Teradata RDBMS Database Administration - NCR

NCR Teradata RDBMS Database Administration - NCR , 2004. - 616 p.
Download (direct link): teradatadatabaseadmin2004.pdf
Previous << 1 .. 193 194 195 196 197 198 < 199 > 200 201 202 203 204 205 .. 218 >> Next


C - 2

Teradata RDBMS Database Administration Appendix C: Error Logs

Log File Summary

This directory/file name ... Contains . And lasts .
/ tpi-data/nodecheck.tpacycle_n (UNIX) ... \tdConfig\tpi-data\tpacycle_n (Windows 2000) where: n is the count extracted from the running PDE kernel memory entries generated by the Resource Check Tools nodecheck utility (if you ran the nodecheck command with the -L argument). If file number n already exists, the previous version is appended with .old to save up to one level of history logs. until you remove them with the syscheckrm command-line utility. If you enter the command syscheckrm without arguments, the utility prints the list of log files in all tpa nodes and removes any corresponding .old files.
/var/array/logs/* (LSI only) a file for each disk array that the node accesses. Each file includes all errors detected for that disk array. When an error exists in any file, that error is displayed once per hour to the console of that node until the error is removed from the file. To remove the error, enter: # /opt/adpxspt/clearlogs as long as you want. There is no built-in scheme for management of these files. You must manage them manually.
/var/adm/usererror/* log files with error information concerning: Saving Teradata crashdumps DMP errors csp errors Gateway errors These logs are similar to the /var/adm/ streams/ logs, except that they typically contain messages logged by user-level daemons. Most PDE andDBS errors go to the /var/adm/streams/ log, even those logged by user-level programs. no more than two weeks. A standard UNIX cron job runs every Sunday night just after midnight, which renames all error* files to oerror* and deletes the old set of oerror files. If you disable the cron job, files accumulate until they fill up /var. If storage is unlimited, the date-unique filenames make these files good for one year.
/sdd/logs/restart.log a copy of the xpt output from its shutdown and its startup. until the next shutdown. The system creates or empties this file during shutdown, then duplicates all output of xptinit in the file. The file is cumulative until the next system shutdown. At startup, the system empties shutdown information from this file and then writes startup information into this file.

C - 2 Teradata RDBMS Database Administration

Appendix C: Error Logs

Log File Summary

This directory/file name ... Contains . And lasts .
/tdsw/recon_out the output from the last reconcile performed on the system. You should view it only on the Package Distribution Node (PDN) or on the node where the reconcile occurred. until the next reconcile. This file is overwritten at the start of a new reconcile. You can view previous reconcile output in the /etc/.osm file.
/tdsw/logtms/tmslog /tdsw/logtms/tmsdlog log files exist for proc daemons. Server tmssrvr log files exist on all nodes. The daemon tmsd log file is only on the PDN. until the next reboot of a node. At a node reboot: a The system renames the current log files with a .old extension in this directory. b The system starts new log files start for tmsd and tmssrvr.

AWS Error Logs

These error logs are generated by the AWS administering an NCR MPP system.

This directory/file name . Contains . And lasts .
/var/adm/streams/* files for each day of the year, uniquely identified with a month and day. Each file includes all AWS system error information. no more than two weeks. A standard UNIX cron job runs every Sunday night just after midnight, which renames all error* files to oerror* and deletes the old set of oerror files. Note: If you disable the cron job, files accumulate until they fill up /var. If storage is unlimited, the date-unique filenames make these files good for one year.
/var/console/console.log a mirror of all information that goes to /dev/console/ of all nodes that are managed by this AWS. You can display this file via the AWS GUI interface using the Status->Event menu selections. until the /var/console/console.log file grows to 500K in size. Then the system moves the file contents to a uniquely stamped file in the /var/console/old_logs/ directory. The amount of information saved is depends on: The number of nodes managed by this AWS The frequency of information transfer to /dev/consoles of all the nodes The size of the /var file system on the AWS
CSF event list all of the errors, warnings, and state changes that occur on a 5100 machine. This list has its own GUI interface. indefinitely. Note: It is up to you to remove entries in the list.
DBC.software_event_ log the Teradata RDBMS view of software events. indefinitely. Note: It is up to you to remove entries.

C - 2

Teradata RDBMS Database Administration Appendix C: Error Logs

Viewing Log Files

Viewing Log Files

This section provides procedures for viewing the console log and node logs.

Log File Error Formats

Both the /var/adm/streams/ and /var/adm/usererror/ logs contain a standard header at the beginning of each line.
Previous << 1 .. 193 194 195 196 197 198 < 199 > 200 201 202 203 204 205 .. 218 >> Next