Re: Errors in Trace and Alert Files Concerning Disappearing Processes

I don't know about windows, but on unix and VMS those kind of things usually mean dead computer, one way or another. I'm not too familiar with how windows does things without doing research, but just as a user it seems to be a bit aggressive about putting things out to disk that haven't been used, whenever I sqlplus XE it takes forever to wake up.

Excessive paging by itself can look like hanging. That's why you see advice laying about that says things like don't make your SGA so large that swapping starts. But you might not see it too often, since it is often a gross configuration mistake to get there. It could also come from memory leaks and configuring too close to the edge of swapping. So how big is your SGA and are you swapping?

In your case, you need to pursue the 7445 to its root cause. Like Charles did in the querying V$ACCESS thread. There are views specific to shared server you might be checking, in case that last alert log message is related. Maybe the real problem is dying shared servers not releasing memory or something. You don't want to use shared servers with long running processes, they block shorter running processes. It's been a while since I've looked, but I'm pretty sure that's explained in the docs.

jg

--
@home.com is bogus.
Commuting by Amtrak now.  Hour late after getting soaked in the rain
Wednesday night walking from the parking lot, two hours late this
morning because the engine blew an oil line next to the nuke plant,
had to wait for next train to give it a push.

Out of a total server memory of 16GB, 12 GB is allocated to Oracle.  There 
is also 250MB in the PGA.  I don't have direct access to the server so I can 
only use what information I can get off of the Enterprise Manager (or 
alert/trace files I get sent to me).  Charles Hooper did mention to me that 
Enterprise Manager could give false information about page swapping but, 
that being said, it constantly shows at 100% for Virtual Memory Page 
Swapping.

You mentioned memory leaks.  I recall seeing something in a number of the 
trace files I was sent about SGA memory leaks.  I'll have to pursue that 
also.

My manager has requested our off-site DBA to put in a SR with Oracle over 
the 7445 error.

Unfortunately we are a datawarehouse which has been configured completely as 
a shared server.  We have a lot of long-running processes.