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 .. 194 195 196 197 198 199 < 200 > 201 202 203 204 205 206 .. 218 >> Next


The first column is a sequential message number, reset to 1 at boot time.

The next column contains the timestamp of when the message is logged.

The timestamp is followed by 70-80 characters that contain encoded header information which is not usually very useful.

The actual message text appears at the end of the line.

Some messages are too long to fit onto one line, and are continued on following lines. You can tell which lines are continuations because they do not contain a header.

Displaying Log Files

You can use the errpt UNIX utility to display the /var/adm/streams/ and /var/adm/usererror/ logs. The errpt utility decodes the header information in each entry, and some kinds of encoded entries.

Viewing the Console Log

The AWS Consolidated Console Log brings together log messages from every node. To view the Consolidated Console Log on the AWS:

Step Action
1 Bring up the main AWS window.
2 From the Status menu, select Logs -> Console Logs. The Console Log window displays the UNIX console output.
3 To save the console output, choose Save Log from the File menu.
4 To exit the Console log window, choose Exit from the File menu.

Teradata RDBMS Database Administration

C - 5 Appendix C: Error Logs

Viewing Log Files

Viewing Node Logs

To view the log files for a particular node, perform the following steps in a UNIX shell on that node:

Step Action
1 To access a node log file, access a UNIX shell on the node and go to the directory: # cd /var/adm/streams
2 To see what files are there, enter: # ls -l
3 To examine a particular log file, for example, error.10-05, enter: # /usr/bin/errpt /var/adm/streams/error.10-05 > /var/adm/streams/error.10-05.errpt The command creates an a readable ASCII file named error.10-05.errpt.
4 To examine a particular log file that has information about disk arrays (for example, error.10-07), enter: /opt/adpxspt/errlog /var/adm/streams/error.10-07 > /var/adm/streams/error.10-07.errlog The command creates an a readable ASCII file named error.10-07.errlog. You may find the log files from the following directories useful for debugging: /var/adm/usererr /var/array/logs /var/adm/streams /etc/.osm and /etc/.osm.old /var/console/console.log

C - 6

Teradata RDBMS Database Administration C - 5 Appendix C: Error Logs

Viewing BYNET Activity

Viewing BYNET Activity

To verify if BYNET is running successfully on each node, enter the following command, using the appropriate month and day numbers:

# grep BMCA /var/adm/streams/error.mm-dd | tail

Messages similar to the following appear (where BLM means BYNET Link Manager):

oerror. 10-02:000041 21:24:11 00003d6c 11 15111 Ol 1 HIB10101 conf g. C1201518010 oerror.10-02:000042 21:24:11 00003d70 11 IS111011 IB10101confi g.C120151QO10 oerror.10-02:000050 21:24:22 000041 11 IS111011 IB10101confi g.C1201518010 ?3 nodes, bya0-0).

oerror.10-02:000051 21:24:22 000041aa 11 IS111011 IB10101confi g.C1201518010 ?3 nodes, bya0-1).

oerror.10-03:000033 14:00:47 005b7b17 11 IS1110 IB10101confi g.C1201518010 oerror.10-03:000034 14:00:47 005b7b6d 11 15111 Ol1 HIB10101confi g. C1201518010 oerror.10-03:000085 14:00:55 005b7e42 11ISIII0I1|4|B|0|0|config.C|20|5180|0 ?4 nodes, bya0-0).

oerror.10-03:000086 14:00:56 005b7e38 11 IS1110 |4|B|0|0|config.C|20|5180|0 successfully ?4 nodes, bya0-1).

... -32754 1 140003801Ibynet

1 ttBLM: BMCA 0 BVNET X starting network.

... -32754 1 140003801Ibynet

2ttBLM: BMCA 1 BVNET K starting network.

... -32754 1 140003801Ibynet

3ttBLM: BMCA 0 BVNET 0 started successfully

... -32754 1 140003801Ibynet

7ttBLM: BMCA 0 BVNET 0 restarting network.

... -32754 1 140003801Ibynet

8ttBLM: BMCA 1 BVNET 1 restarting network.

... -32754 1 140003801Ibynet

ttBLM: BMCA 0 BVNET 0 started successfully

... -32754 1 140003801Ibynet 10ttBLM: BMCA 1 BVNET 1 started

... -32754 1 140003801Ibynet 4ttBLM: BMCA 1 BVNET 1 started successfully

Note: BLM is an acronym for BYNET Link Manager. Examine the last few lines (BLM messages 9# and 10#) of the example. In this instance, BYNET 0 and BYNET 1 started successfully.

Teradata RDBMS Database Administration

C - 7 Appendix C: Error Logs

Viewing the SW_Event_Log

Viewing the SW_Event_Log

NCR recommends that you access the system view DBC.SW_Event_Log rather than the underlying table. You can view the contents of the log by submitting the query:

SELECT * FROM DBC.SW_EVENT_LOG ;

For SW_Event_Log column names and formats, see Teradata RDBMS Data Dictionary.

Note: The system views should already have been created in DBC during the Teradata RDBMS installation process. If you need to create them now, see "Database Initialization Program (DIP) Utility" in Teradata RDBMS Utilities.

C - 8

Teradata RDBMS Database Administration Appendix D:

Tools for Monitoring Performance

You can identify what session controls to impose and when to put them in place by monitoring performance on a regular basis. This chapter introduces:
Previous << 1 .. 194 195 196 197 198 199 < 200 > 201 202 203 204 205 206 .. 218 >> Next