Hi Holger,
Your understanding is correct on rdisp/bufreftime and 'Last modified' . On the F1 help on buffer state for 'Pending' I can only find the OSS which is also not clear. But I tried to read a table in "Pending" for a about 6 -7 times in SE16 . After a while ( say 10 mins ) I ran ST02 again and the table status changed to valid . So the documentation is correct that buffer will be loaded after certain read access but its still not confirmed as to how many read access would reload the buffer in "pending" state and after how much time.
That is it on this topic.
Cheers
Hi Holger,
I am not sure about this as documenattion on pending status in OSS 3501 says -
Pending: All generic areas of the table contained in the
buffer are invalid, but a certain number of read
accesses can be reloaded into the buffer. ( This is kind of not clear )
On the time rdisp/bufreftime is only applicable when you have multiple application server . It is the time interval at which the various application servers read DDLOG and reload only those tables which have been marked as updated in DDLOG.
Check this - http://help.sap.com/saphelp_47x200/helpdata/en/c4/3a6dd5505211d189550000e829fbbd/frameset.htm.
You can use report RSDBBUFF to see the above parameter of your application server.
So "Pending" is the state of an individual table.
rdisp/bufreftime is the time interval at which buffers ( written in DDLOG since last synchronization )in an application serever is refreshed. Tables which are in pending and not changed since last synchronization will still be in pending .
In ST02 -. Detailed Analysis -> Generic key -> Buffered Objects , I can find some of tables on my system as pending . I ran Se16 ( read access on this table with SQL + Buffer trace on ). In trace display I find that it is always bypassing the buffer ( yellow line ) even after a number of repetitions of SE16 . This table was last modified in 1997 . So seems pending will only change when we modify the table with insert/ updat/delete .
Cheers
Add comment