I'm working on a project that has now run across this error in two different processes. We have
done as the Oracle books suggest and bumped up the parameters in the init.ora, but still get it ...
we just delay the frequency.
This message seems to occur after a large number of committed transactions. Shouldn't the shared
memory be deallocated and reclaimed by Oracle? The transactions are each independent connections
scattered throughout the day ... the latest cases occurs after approximately 170,000 transactions.
Is there some sort of magical, "this is for OLTP" switch somewhere?
Thanks in advance for your assistance.
Bill Roney
Received on Mon Oct 14 1996 - 00:00:00 CEST
