XPRA_EXECUTION error while PI upgrade

Question

Hi
I ran into an issue upgrading the R3 plug-in from PI from 2002_1_470 to
2004_1_470 in SAINT. The update terminated during phase XPRA_EXECUTION with dump READ_REPORT_LINE_TOO_LONG. We are on 4.7 with HPUX and Oracle. Could'nt find much help in Notes or online. Any help will be appreciated.
The log file in SAINT shows this error
"Program terminated (job: RDDEXECL, no.: 07431301)
   See job log
Execution of programs after import (XPRA)
End date and time : 20071204074418
Ended with return code:  ===> 12 <==="
The trace file is as shown below.
Mon Dec 3 17:33:15 2007
ABAP/4 Program SAPMV80H .
Source MV80HF0A Line 751.
Error Code READ_REPORT_LINE_TOO_LONG.
Module $Id: //bas/640_REL/src/krn/runt/abdbif4.c#3 $ SAP.
Function readreport Line 982.
RABAX: level LEV_RX_STDERR completed.
RABAX: level LEV_RX_RFC_ERROR entered.
RABAX: level LEV_RX_RFC_ERROR completed.
RABAX: level LEV_RX_RFC_CLOSE entered.
RABAX: level LEV_RX_RFC_CLOSE completed.
RABAX: level LEV_RX_IMC_ERROR entered.
RABAX: level LEV_RX_IMC_ERROR completed.
RABAX: level LEV_RX_DATASET_CLOSE entered.
RABAX: level LEV_RX_DATASET_CLOSE completed.
RABAX: level LEV_RX_RESET_SHMLOCKS entered.
RABAX: level LEV_RX_RESET_SHMLOCKS completed.
RABAX: level LEV_RX_ERROR_SAVE entered.
RABAX: level LEV_RX_ERROR_SAVE completed.
RABAX: level LEV_RX_ERROR_TPDA entered.
RABAX: level LEV_RX_ERROR_TPDA completed.
RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
RABAX: level LEV_RX_END entered.
RABAX: level LEV_RX_END completed.
RABAX: end no http/smtp
RABAX: end RX_BTCHLOG|RX_VBLOG
The ABAP source code lines are longer than the width of the internal
table..
***LOG R68=> ThIRollBack, roll back () [thxxhead.c 12372]
ThWpRestart: restart wp (pid=706) automatically
WARNING ==> PfFileIndUpd: new starttime < starttime
Disconnecting from ALL connections:
Thanks
Vic

Answer 1

Hi Vic,
I was trying to draw your attention to the cause of the error. To me I think you may have missed some Basis support pack.
I suggest you raise an OSS message if you are unable to reset the SPAM/SAINT Queue.
Regards,
Siddhesh