12.2.6 Troubleshooting related to the log monitoring program

In the SAP system, check the system log information or CCMS Alert Information output during the time period in which JP1 events were not issued successfully to identify all information that was not reported in the file monitoring product's log file traps. If any of the unreported information requires an action, take the appropriate action according to the output system log information or CCMS Alert Information.

Restart JP1/Base's log file traps.

Check and, if necessary, revise the size of the storage file.

Re-evaluate the size of system log information or CCMS Alert Information storage file (value of the SIZE label in the EXTRACTFILE section in the environment parameter file) based on size-extracted-and-output and valid-data-size displayed in the KAVF14280-W or KAVF14281-W message output to the Windows event log (in Windows) or syslog (in Linux) so that the file is larger than size-extracted-and-output and no more than the valid size of data that was written. The value of size-extracted-and-output minus valid-data-size is how much more space is needed.

Change the format of storage file from WRAP1 to WRAP2.

Before you change the storage file format, terminate any executing command or stop record collection, and then stop JP1/Base's log file traps. After that, manually delete the storage files, management files, and timestamp files.

In the SAP system, check the system log information output during and following the collection period in which this message was output to identify all information that was not reported in the file monitoring product's log file traps. If any of the unreported information requires an action, take the appropriate action according to the output system log information.

If the WRAP1-format file was being monitored by JP1/Base's log file traps, restart JP1/Base's log file traps.

Re-evaluate the size of system log information storage file (value of the SIZE label in the EXTRACTFILE section in the environment parameter file) based on size-extracted-and-output and valid-data-size displayed in the message so that the file is larger than size-extracted-and-output and no more than the valid size of data that was written. The value of size-extracted-and-output minus valid-data-size is how much more space is needed.

If you output storage files in the WRAP1 format, consider using the WRAP2 format that enables multiple files to be output.

In the SAP system, check the CCMS Alert Information output during and following the collection period in which this message was output to identify all information that was not reported in the file monitoring product's log file traps. If any of the unreported information requires an action, take the appropriate action according to the output CCMS Alert Information.

If the WRAP1-format file was being monitored by JP1/Base's log file traps, restart JP1/Base's log file traps.

Re-evaluate the size of CCMS Alert Information storage file (value of the SIZE label in the EXTRACTFILE section in the environment parameter file) based on size-extracted-and-output and valid-data-size displayed in the message so that the file is larger than size-extracted-and-output and no more than the valid size of data that was written. A value of size-extracted-and-output minus valid-data-size is how much more space is needed.

If you output storage files in the WRAP1 format, consider using the WRAP2 format that enables multiple files to be output.