Hi,
We are in a similar environment but have not quite tested the same setup.
Can you run Costpoint 4.0 with Oracle 10.2.0.3 ? Does that behave the same way ?
I know Deltek does a terrible job in their SQL code, not using bind variables, missing indexes, you name it.
They keep telling us we have too mach data and they can't replicate our problems in their shop...
Oh well, I don't even want to go there....
We are currently on Costpoint 5.2 and have a test version in 6.1
But we are having both environments under Oracle 9.2.0.8, though.
I did not want to upgrade both environments at the same time and then trying to figure out if the change in Costpoint or Oracle is
causing problems.
I'm currently waiting on some memory to spike up our test environment so I can start a DB instance for Costpoint 6.1 testing with
the same parameters as our production DB under Costpoint 5.2.
I would run a client side trace under Costpoint 4.0 and check which tables are involved.
Then ensure that stats are computed and the same indexes exist for the Costpoint 6.1 environment.
Unfortunately, Deltek has no longer the client side tracing available for 6.1 (go figure !!).
But if it's a test DB, you could possible put the entire DB in trace mode and see where stuff is hanging.
I'm eager to get my Costpoint 6.1 in a valid testing state and probably will be kicking the same thing around pretty soon in Oracle
10.2.0.3 as well.
Chris.
-----Original Message-----
From: esd-dbas [mailto:oracledba-ezmlmshield-x77339987.[Email address protected]
Sent: Friday, April 04, 2008 5:08 AM
To: LazyDBA Discussion
Subject: Oracle 10g initialization parameters for Deltek Costpoint 6.1 PJPUPPSR process
We recently went from Costpoint 4.0 to Costpoint 6.1 - the underlying database went from 8.1.7 to 10.2.0.3
Running the PJPUPPSR takes significantly longer (PSR_FINAL_DATA insert) within the program. This used to take at the most 15
seconds to add a new record - now it takes up to 5 minutes to add only one.
Anyone else experience something similar - any insight into oracle initialization parameters that could affect this favorable or
disfavorably?
Hoping we're not the lone ranger - someone else has already dealt with this issue and knows the resolution.
Thanks!
---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
Oracle LazyDBA home page