22.12.10

SAP Note 15330 - System operation stops during word processing

Symptom:

Within word processing (up to now, always in connection with the processing of forms or when importing texts with report RSTXR3TR), SAP System operation stops when Table STXL is accessed.
This frequently occurs on SINIX computers, but has also happened on other hardware platforms. The session cannot be ended using normal means (SM04 -> Delete session), either.

System environment: SINIX version <=5.41,
Oracle version <=7.0.16.6.2
Windows NT (SAP Release 3.0)

Cause and prerequisites

The reason is unknown. All attempts to analyze the problem have failed. The error is caused by a bug in ORACLE communication.

Solution
If the session can no longer be ended, you can restart the work process with SM50/Click on WP/Menu: Process -> Cancel w/o core
Connect to the database with TWO-TASK set to avoid the problem. The problem has never appeared with this connection.
The problem has occurred only in connection with Table STXL.

The following procedure is valid only for UNIX Platforms. If the problem occurs on Windows NT, please see related Problem Notes 31559 and 31563.

To connect the R/3 Work processes to the database via Two Task, the startup script for the alias 'startsap' in the Home Directory of the User:
$HOME(adm)/startsap__
z.B. /usr/sap/DEC/home/startsap_da5201_00

( is the SAP System name, e.g., C11) must be chaned as follows: (lines 163-169):
#
# Start SAP-Instance
#
TWO_TASK="T::" <=========== Insert !!
export TWO_TASK <=========== Insert !!
if [ $TASK = "ALL" -o $TASK = "R3" ];then
if [ -f $EXEDIR/sapstart ];then
echo "\nStarting SAP R/3 Instance " tee -a $LOGFILE

Here stands for the computer name (e.g. hs0013) and for the database name (usually C11).

Additional key words

SAPACRIPT SE71 SAPLSTXD RSTXR3TR SCC1 CLIENTCOPY CLIENT-IMPORT

No comments:

Post a Comment