P
Paul Koufalis
Guest
Are you seeing gajillions of short connect/disconnect in the logs or relatively few, long running connections? Has this crept up slowly over weeks and months or all-of-a-sudden? Are the _proapsv processes consuming a lot of CPU? Or disk I/O? Or both? Excessive CPU use could point to rapid reader issues. Check the disk I/O usage of the temp file system. Use -t -T to show linked temp files. Which ones are big if any? Heavy temp-table use in a slow temp FS could slow down the _proapsv's. One thing that I have seen is Apsv agents doing OS-COMMAND SILENT and that something getting jammed up. Keep an eye on the _proapsv processes and their children. You can also install ProTop Free and drill down to the Apsv user to see what they are doing in the DB, providing your table/index range size startup parameters are set correctly. Mind you, I don't remember if _UserTableStat and _UserIndexStat were available in 10.2A05. Finally, please contact me offline at pk@wss.com regarding something I don't want to discuss here.
Continue reading...
Continue reading...