Shared Memory Areas not accessible in background processing

Question

Hi there
We're using Shared Memory Areas to share data between an on-line transaction and a background program. The on-line transaction collects the data, creates the Shared Memory Area and submits a background job to process it. So, after the detach_commit, it performs submit program via job_name xxxx number nnnn.
It works OK in our dev and quality systems, but does not work in our production system. The memory area is created OK, but the job cannot access it. In the background program, we get the message:
"The read lock on the instance 'ZNNNNNNN' in the client '100' of the shared objects memory area 'ZCL_XXX' cannot be set, since there is no active version of this area instance. However, the area constructor for the automatic construction of the area instance was started."
On the SMA side, we've tried seemingly every combination, even "propagate_instance".
The job seems to be running on the same application server as the SMA.
Any ideas about what we're doing wrong, anyone?
Thanks
Ged

Answer 1

Hello Ged,
Please remember that SHM is accessible across one App Server(AS) only.
If your SAP landscape has multiple AS's then it might pose a problem. When you're scheduling the background job, i guess that the Bgd work process is started in a different AS(load balancing ) and hence SHM is no accessible.
If this is the case, then you've no other option but to store the data persistently in DB clusters viz., INDX-type tables (EXPORT TO/IMPORT FROM DATABASE).
BR,
Suhas
Message was edited by: Suhas Saha