‎2012 Feb 29 9:51 PM
Hi All,
I am exporting data to memory using the below statement from Web Dynpro view.
CALL FUNCTION 'SYSTEM_UUID_C_CREATE'
IMPORTING
uuid = ev_cache_id_condcrett.
EXPORT tab = it_cond_cre
TO DATABASE zgpb_bckgrnd(ul)
FROM ls_zgpb_bckgrnd
CLIENT lv_clnt
ID ev_cache_id_condcrett.
After Exporting data to memory and Importing the data to a Program by using the below statement
Import from memory - Conditions
IMPORT tab = it_cond_cre
FROM DATABASE zgpb_bckgrnd(ul)
TO ls_zgpb_bckgrnd
CLIENT lv_clnt
ID p_cre_m.
FREE MEMORY ID p_cre_m.
Question 1 : I am uploading huge amount of data to memory by using different user ids .Is there any restriction of exporting data to memory.If please suggest solution to overcome the the problem.
Question 2: At the same time .I am getting the below Error and I could not able to login into SAP.
Rollin failed; Session Terminated and Rollout failed; Session Terminated.
Please suggest solution to overcome the above problem
Thanks and Regards,
Uma
‎2012 Feb 29 11:05 PM
You are not exporting / importing data to memory, but store it in cluster table zgpb_bckgrnd.
FREE MEMORY is unnecessary for this scenario.
I haven't heard about an explicit limit of how big a data cluster can be. Looks like you are hitting some barrier caused by the roll area that's defined in the system. You'll probably have to redesign the way you store your data.
‎2012 Feb 29 11:05 PM
You are not exporting / importing data to memory, but store it in cluster table zgpb_bckgrnd.
FREE MEMORY is unnecessary for this scenario.
I haven't heard about an explicit limit of how big a data cluster can be. Looks like you are hitting some barrier caused by the roll area that's defined in the system. You'll probably have to redesign the way you store your data.
‎2012 Feb 29 11:16 PM
HI Tamas,
Thanks for your solution.Could you please suggest solution for my second question. Is the cluster table effecting the roll in and roll out session failing.
FYI- After Importing I am running this data in aprogram in background mode which triggers workflow.
Thanks and Regards,
Uma
‎2012 Feb 29 11:38 PM
I don't think the cluster table would really be the problem, although I haven't experienced a similar situation yet.
I'd guess that too much data is being stored with one statement and that's the reason for the issue.
As I said, you may have to revisit your data storage design and see if you can store the data so that the cluster is not that large. Maybe use more than one cluster? Hard to say without knowing the application details.
Oh, and if you want to get rid of the stored cluster, use the DELETE FROM DATABASE command instead of FREE MEMORY.
Edited by: Tamas Hoznek on Feb 29, 2012 3:43 PM
‎2012 Mar 01 4:07 AM
‎2012 Mar 01 1:13 PM
Hi All,
Thanks for you help. Special thanks to Tamas.
The reason for getting roii in ,rollout session terimination is:
1.In SM 51 T code I have 3 servers and in Central Instance server all the work processes are full. At that time I am trying to login from SAP logon pad with Central Instance Server which is configured. So I am getting the roll in roll out error.
Thanks and Regards,
Uma