SAP Note 18319 - Difficulties with the batch input log file

Symptom:

Difficulties occur when accessing the batch input log file.
Up to now we are aware of the following:

1. The reorganization program RSBDCREO or the reorg job SAP_REORG_BATCHINPUT continues running and eventually hangs. Therefore, the work process must be cancelled manually.

2. The reorganization program RSBDCREO or the reorg job SAP_REORG_BATCHINPUT terminates with the ABAP short dump. In the short text you can find:
ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
The internal table BDCLDA could not be extended.

3. The work process which processes a batch input session terminates with a core dump. The C stack from the core refers to a routine BtcClFindPart() or BtcClCrPart(). For example:
BtcClFindPart()
BtcClCrPart()
bil_open()
dybisbdc()
ab_jcaly()
ab_extri()
ab_xevent()

4. Report RSBDCLOG reads the batch input logs.
The work process hangs, and after a while the PAGING is filled up.
Error message or RABAX 'NO MORE PAGING'.
ABAP/4 runtime error TSV_TNEW_PG_CREATE_FAILED
Paging file overflow
Runtime error TSV_TNEW_PG_CREATE_FAILED
rdisp/PG_MAXFS

5. When processing a session or during a reorganization (see above) several processes are hanging. In the process overview (SM50), semaphore 22 is entered as waiting reason.

6. In the system log display, a log of a totally different folder is displayed.

7. The system log (SM21) contains messages such as:
Error processing job log files
> Log file btccllog0592
> Function BtcClFindPart btccllog0592
Job log file ID not found
Failed to open log partition
> Funktion BtcClWrEntry btccllog1574
> Transaction No: 0 Block No: 0
> Error creating batch input log
or
Error editing job log file
> Log file btccllog1703
> Function BtcClRmPart btccllog1703
Log partition does not exist

Cause and prerequisites

The log file is corrupt (end identifier is missing).

Solution

The log file or files are in the directory /usr/sap//SYS/global and have the name BI
for example: System K11 Server hs1033 Instance 00
File: /usr/sap/K11/SYS/global/BIhs103300
A reorganization file is created for reorganization.
Up to Release 2.2C it has the name /usr/sap/K11/SYS/global/BDCREORG.
As of Release 3.0D it has the name //BI
Example: /usr/sap/K11/D00/data/BIhs103300


Solution:

• Find the corrupt log file (possibly RSBDCLOG and execute in debugging BREAK-POINT in FORM routine LOG_DIR, field LOGNAME).

• Remove the corrupt log file (remove or rename on operating system level. The renamed file must not start with BI).

• Find the reorganization file in the DATA directory ().

• Copy the reorganization file under the old log name to precisely the same position.

• If you cannot find a reorganization file, delete the corrupt log file nevertheless since otherwise no batch input will run any longer.
  
  

Caution:
Up to Release 3.0C!!!:
The reorganization of the logs must always run separately. No batch input may be processed in parallel. Take this into account.

All valid releases:
An overflow of the file system is the most frequent cause for a corrupt log file. In particular for large or a great number of batch input sessions, provide sufficient disk space in the global directory.

Additional key words

btccllog