June 7, 2011 at 2:23 am
Chandra
As I said in one of my last posts, I didn't have to use the traces suggested by Lutz because the development team fixed the problem by basically reverting to the old version of the code for that particular module. This picked up the performance and they reported this back to the software vendor. As a result I didn't have to get any deeper into this one.
Sorry I can't be of more help here.
thanks
Mark
June 7, 2011 at 3:40 am
Thanks for the info Mark, I will get in touch with the Siebel product team
June 7, 2011 at 4:59 am
If it's specifically Siebel I will ask the development team which area of the application code they changed. It might take a few days as some are off and some are on training but i'll post back here when I hear from them.
thanks
December 15, 2011 at 5:10 pm
Hi,
Same problem on same environment but diferent (Siebel 7 ==> 8 on Sql 2005==> 2008) cause for sure.
Not able to solve as easy as you did.
Are you use connection pooling?
Regards,
Bronco
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply