Skip to end of metadata
Go to start of metadata


The purpose of this wiki is to provide information on how to check if note 1020260 has been applied.


 This wiki will provide details on how to verify if Oracle stats on the following RFC tables are up to date: ARFCRSTATE, ARFCSDATA, ARFCSSTATE, TRFCQDATA, TRFCQIN,

Performance problems

If you experience performance problems when processing tRFC or qRFC calls, the issue may be occurring because it take a long time to read the RFC tables. If this is the case, you would see long sequential read times in transaction SM50 or in transaction SM66.  See the following example, showing a sequential read issue reading table TRFCQOUT:


 In this case it would be advised to check if the statistics are up to date.  As per note 1020260. 

 How to check?

Call transaction  DB20 and enter table TRFCQOUT (or ARFCSSTATE or TRFCQIN or any tqRFC table) and click on the Refresh button.

Make sure the statistics are set to Inactive (Active Flag = ‘I’ “DBSTATC settings” section at the end of the screen). See example below:


And just above it, check the 2 numbers listed (Under Number of Table Rows section) - "Old Number" and "New Number".

The "Old number" should correspond to the number delivered in the note 1020260. The new number should be as close to old number as possible.


The script in 1020260 sets the old number for TRFCQOUT to 331796 (if you look for statement EXECUTE DBMS_STATS.SET_TABLE_STATS(:OWNER, '"TRFCQOUT"' in the script). From the script:


So, the "Old number" should correspond to the number delivered in the note 1020260 which is 331796. In the example below this is the case indicating that the note has been applied:



The Old Number for the other tables is as follows:

Table TRFCQOUT  the Old Number is 331796

Table  TRFCQSTATE the Old Number is  29575

Table TRFCQDATA the Old NUmber is 71165 

Table  TRFCQIN the Old Number is 20994

Table ARFCRSTATE the Old Number is 3390

 Table ARFCSDATA the Old Number is 419227

Table ARFCSSTATE the Old Number is 331849


Just above the Old Number in the Last Refresh section, the  Date and Time should be closer to the current date. If it is very far (more than half an year), then the script from Note 1020260  should be run again. As per note 1020260:

"It is usually sufficient to execute the script once. However, to allow for continuous adjustments to the script, you can import the latest version in regular intervals (for example, once per quarter). It may also be useful to execute the script again after SAP upgrades.


Related Content

Related Documents

Related Notes

742950     Performance affected on Oracle DB with Supplement 11
932975     Oracle statistics for RFC tables
1485789    QRFC: Long running processes in SM50
1484197    ARFCSDATA for one LUW was read by 100 DIA processes                             
1528988    Queue scheduler uses a wrong index to access
1623430    Outbound queue (qout) scheduler does not process a
1573359    tRFC Idoc delay processing in BW

1493644    Long running process reading TRFCQIN blocking execution      
1497510    Experiencing deadlocks, lock & waits in inbound processing   
1500048    SMQ2 inbound Queue remains in READY state