Ansicht
Dokumentation
05134 - Note 0450351 - CHKXDA - check for and then end "orphan" QXDARECVR jobs
CPI1466 during Backup General Material DataThis documentation is copyright by SAP AG.
Note 0450351 - CHKXDA - check for and then end "orphan" QXDARECVR jobs
We put "CHKXDA" to the test for the first time on our production DB last nightCHKXDA had 133 active QXDARECVR jobs to review which took 5hrs to complete
The result was; 37 QXDARECVR jobs were ended due to being duplicates
CHKXDA had a lot of checking to do because the night before, one of our
application servers IPL'd due to running out of storage caused by a 6hr running
SDV03V02 rescheduling job submitted by a user.
When an app server "goes down" this way; the orphaned QXDARECVR jobs are never
handled properly
CHKXDA program could have a little improvement made to it................
There are some of the QXDARECVR jobs which are contained in file XDAJOBS with a
*NONE for the PID which is not correct
From what I could tell; the joblog is scanned for each QXDARECVR job to
determine the app server PID that it belongs to
We have many occurrences where the joblog "wraps" and the PID information is not
contained anymore;
hence the *NONE - but these are also duplicates and should be ended
Trying to come up with a way to also end the duplicate QXDARECVR where the
joblogs have wrapped.......
Maybe the XDAJOBS file could have "START DATE"; "START TIME"; and either
"CURRENT USER PROFILE" or "JOB USER IDENTITY" added to it;
Then maybe generate a report for the entries in XDAJOBS and *NONE entries in
XDAJOBS so that those jobs can be interrogated by the customer and deleted
manually if necessary
Just my thoughts
Doreen Anderson
Ball Horticultural Company
dandersoZb...
(630) 231-3600 x3214
[Non-text portions of this message have been removed]
Durban Tours - Südafrika Safari
PERFORM Short Reference Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.
Length: 2341 Date: 20240424 Time: 235655 sap01-206 ( 3 ms )
