nVision Performance Tuning

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)

As many PeopleSoft developers and managers I have suffered through my share of nVision Tuning efforts and until very recent we could not get our reports to run under 4 hours, until the recent change…
In any case here are a few points from my experience:
We experienced an almost almost 5 fold increase in performance when we did a PS_LEDGER reorg with PSCLEDGER index option as follows:

db2 "reorg table PSFSSYS.PS_LEDGER index PSFSSYS.PSCLEDGER allow read access indexscan" 
db2 "RUNSTATS ON TABLE PSFSSYS.PS_LEDGER FOR INDEX PSFSSYS.PSCLEDGER" 
db2 "reorgchk current statistics on table PSFSSYS.PS_LEDGER"

Also it is great to cleanup treeselectors, to make sure that static selectors did not get out of sync with trees, this can be done on a regular basis, see a sample script below. Please note that the number in the end of the treeselector name xx – corresponds to the chartfield length:

-- Delete TreeSelectors
Delete from PSFSSYS.PSTREESELECT05;
Delete from PSFSSYS.PSTREESELECT06;
Delete from PSFSSYS.PSTREESELECT10;

-- Delete Tree Control table for the respective selectors above
delete from PSFSSYS.pstreeselctl
where length in (5,6,10);

For details about PeopleSoft nVision architecture and structure please make sure to read the Red Paper by clicking below

PeopleSoft nVision Red Paper

Tags:

I really want to know what you think