KFAA50019-E

An error has occurred while accessing a message log file.

aa....aa: Cause of the error

• FAILED TO GET THE PATH NAME OF THE MESSAGE LOG FILE

  An attempt to get the name of a server message log file failed.

• FAILED TO GET THE PATH NAME OF THE CLIENT MESSAGE LOG FILE

  An attempt to get the name of a client message log file failed.

• System call error, system call = "bb....bb", errno = cc....cc

  A system call error has occurred.

  bb....bb: Name of system call in which the error occurred

  cc....cc: Error number

S:

Terminates processing.

Action:

Eliminate the error based on the cause of the error aa....aa that is output in the message.

• If aa....aa is FAILED TO GET THE PATH NAME OF THE MESSAGE LOG FILE

  Carefully review both the server message log file's storage directory ($ADBDIR/spool/) and the value specified in environment variable ADBDIR.

• If aa....aa is FAILED TO GET THE PATH NAME OF THE CLIENT MESSAGE LOG FILE

  Carefully review both the client message log file's storage directory^# and the value specified in environment variable ADBCLTDIR.

  #

  • HADB client for Windows: %ADBCLTDIR%\spool

  • HADB client for Linux: $ADBCLTDIR/spool

• If aa....aa is System call error, system call = "bb....bb", errno = cc....cc

  Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

After taking corrective action, execute the adbstart command to restart the HADB server.