on 06-25-2011 12:40 AM
Planned GO-Live with SCM running on DB2 v9.7 AIX P-570....
We have been having issues with SCM implemenatation with DB2. We cannot run key business processes and are seeing bad performance. This is causing GO Live issue due to work stoppage and schedule delays.
In our Quality SCM system there seems to be performance issues reading tables such as /SAPAPO/CI /SAPAPO/OP and /SAPAPO/FU.
We are also getting DBIF_RSQL_SQL_ERROR+CX_SY_OPEN_SQL_DB dumps when running /SAPAPO/BOP
Our processing is really slow in SCM and there is limited or no I/O taking place with some of the sequential reads and direct reads equating to long run times!!
*Also please let us know if we can distribute queue execution load across multiple application servers to prevent one application server from getting over loaded....
Any light you can shed on this would be helpful -
Thanks
Fred
You can run BOP with Parallel processing (as specified in the BOP variant). Review runtime of BOP using transaction /SAPAPO/BOP_RUNTIME and review in what stage (Filter, Sort, etc) BOP is taking most of its time.
Another suggestion is that if you have multiple document types (Sales Orders and Stock Transport Orders), run BOP seperately (using filter variants) to narrow down the cause of the problem. I've noticed that Stock Transport Orders tend to create a lot more problems than sales orders.
Review OSS notes for the dump issue. BOP is very complex and SAP has literally hundreds of notes out there.
You can also setup parallel processing of CIF queues so that updates in ECC occur faster (ECC update has to complete before BOP can finish).
Rishi Menon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
13 | |
4 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.