Ansicht
Dokumentation

ora1747 in update process <br />Tip-No.: 2473 ( INFO2473 )

ora1747 in update process
Tip-No.: 2473 ( INFO2473 )

rdisp/max_wprun_time - Maximum work process run time   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

ora1747 in update process
Tip-No.: 2473

Symptom

An update order was terminated with ORACLE error number ORA-01747

Cause

An internal buffer of the data base interface is in an incorrect
state, and this sets up the SQL instructions incorrectly.

Solution

The buffer cannot be explicitly reset. As the buffer is process-
specific, you can "quasi reinitialize" by stopping and starting the
update process again.
The procedure for this is as follows:
1) Determine the process number ('PID') of the update process using
Transaction SM50. The update process has value 'VB' in column
'Type'.
2) Stop the update process by entering the command 'kill -2 xxxxx'
in a UNIX shell, whereby xxxxx is the PID you determined
previously. The update process is normally restarted by the
system automatically.
3) The system should now function correctly again. Lastly, you
should check whether the update program was active when you stopped
in. To do this, call up Transaction SM13, replace the user name with
an asterisk ('*'), and select all terminated update orders.
If the resulting list is not empty, when you should explicitly
update the corresponding update orders. You can do this in
Transaction SM13 via menu selection Administration -> Subsequent
update, -> V1 update, -> individual. You should not lose any data
you have already entered.

The problem should no longer occur from Release 1.1F.






BAL Application Log Documentation   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 1680 Date: 20240424 Time: 230934     sap01-206 ( 17 ms )