T
TheMadDBA
Guest
Like I said previously you are going to need to do something specific with code to get useful profiler results on an appserver pool OR you are going to need to set up an appserver with a min/max of 1 agent., otherwise all of the agents will try and write to the same output files. If you set up one agent then you can do the following... 1) Create a text file... profiler.cfg or whatever you want to call it and put these lines in the file... -OUTFILE /mydirectory/prof.out -DESCRIBE MyDescription 2) Add –profile /fullpathto/profiler.cfg to the pf file for the appserver 3) start the appserver 4) run the code 5) stop the appserver using asbman -stop 6) load the file into the profiler tool and look around Also a pretty good idea to download protop and see what is going on in the database. You will probably have to tweak the tablerangesize and indexrangesize parameters to make sure all of the tables and indexes are being tracked.
Continue reading...
Continue reading...