Table of Contents

Search

  1. Preface
  2. Introduction
  3. Servers
  4. Console Client
  5. Search Clients
  6. Table Loader
  7. Update Synchronizer
  8. Globalization
  9. Siebel Connector
  10. Web Services
  11. ASM Workbench
  12. System Backup and Restore
  13. Batch Utilities

Error Logs

Error Logs

IIR error logs may be output by various utilities and/or returned in response to an
ids_error_get
API call.
This is a sample Error Log created by the Table Loader:
ErrorLog: [ 1.773 2] loadit > It is now 20020612123407 ErrorLog: [ 1.773 2] exit code -252010410 ErrorLog: [ 1.543 2] loadit.c 3013 rc 10 32520104*100 ErrorLog: [ 1.493 2] thread_init failed ErrorLog: [ 1.442 2] loadit.c 2494 rc 4 325201*100 ErrorLog: [ 1.392 2] match_rb_open returned -325201 ErrorLog: [ 1.342 2] utils.c 1342 rc 1 3252*100 ErrorLog: [ 1.292 2] connect to rb server failed -3252 ErrorLog: [ 1.242 2] sockapi.c 394 rc 2 23*10 ErrorLog: [ 1.192 2] socket.c 1765 rc 3 2*10 ErrorLog: [ 1.142 2] socket.c 581 rc 2 ErrorLog: [ 1.092 2] send(568) failed -1: winsock error 0 ErrorLog: [ 1.022 2] sockapi.c 627 rc 2 325*10 ErrorLog: [ 0.972 2] sockapi.c 595 rc 5 32*10 ErrorLog: [ 0.922 2] socket.c 1860 rc 2 3*10 ErrorLog: [ 0.872 2] socket.c 1833 rc 3 ErrorLog: [ 0.822 2] ssasocket_recv_n: received zero bytes ErrorLog: [ 0.581 2] loadit.c 2848 rc 3 3691524*100 ErrorLog: [ 0.531 2] process_input: thread_init failed for thread #1 ErrorLog: [ 0.481 2] loadit.c 2729 rc 24 36915*100 ErrorLog: [ 0.431 2] loadit.c 1448 rc 15 369*100 ErrorLog: [ 0.361 2] ssaxld_init failed -369: ErrorLog: [ 0.311 2] dbops.c 4815 rc 9 36*10 ErrorLog: [ 0.201 2] ssaodbc.c 15352 rc 36 ErrorLog: [ 0.151 2] ssadb6_ssaxld_init failed: SSAST Could not get memory ErrorLog: [ 0.101 2] sort.c 1775 rc 13 ErrorLog: [ 0.050 2] sort.c 1305 rc 6

Interpreting an Error Log

Find the oldest message. It indicates the first error that occurred. It is identified by the smallest relative timestamp. For example, the last line from the log above is:
ErrorLog: [ 0.050 2] sort.c 1305 rc 6
This line of data has the following format:
  • Timestamp - message relative (0.050)
  • Thread number (2)
  • Module name (sort.c)
  • Line number (1305)
  • Response code (6)
We can infer that an error occurred in a sort routine. Continue up the stack in order of increasing timestamp looking for a text message. The messages containing module names and line numbers can be ignored. They simply give context information (a stack trace) of who called the function that reported the error.
The first text message is as follows:
ErrorLog:[0.151 2] ssadb6_ssaxld_init failed: SSAST Could not get memory
This message indicates that the sort routine failed when attempting to allocate some memory. In response to this you could add some RAM and/or increase the available swap space, or decrease the amount of memory required by the Table Loader by adjusting its parameters.
You could continue up the stack looking for more information. However, the first message is the important one. The other messages may report consequential errors, and are of less interest.
Some Error Logs will contain two error stacks. This typically occurs when two communicating processes fail. For example, when a search client (say relate) calls the Search Server which subsequently reports an error, both processes will report their Error Logs.

0 COMMENTS

We’d like to hear from you!