Re: ORA-1575 error

In article <876v6g$jqp$1_at_nnrp1.deja.com>,   joe_celko_at_my-deja.com wrote:
> We are getting ORA-1575 errors ("Oracle has timed out waiting to
> acquire the Space Transaction enqueue lock") in Oracle 8 on a Sun.
This
> is happening with simple loads, Navigator and IQ for ad hoc queries
>
> I will post the details of the system configuration shortly, but it is
> a good sized Sun with a Raid 5 disk array -- space should not be a
> problem. Are other people are getting the same error? Does somceone
> have a solution?
>
> --CELKO--
>

We have had ST lock errors. They are mostly associated with Oracle Parallel server environments, but if you are not OPS then take a look at your temporary, sort, tablespace parameters and your init.ora parameters for sort as this is the other main cause.

There is a white paper available on this topic from support. I cut the following out of one of two tar reports we entered with Oracle on this back in version 7 days. >> Oracle support e-mailed Note: 33567.1 which provide init.ora events that may be used to help if the problem is caused by coalesing temp segments. Note makes reference to OLS 9869022.61 for situations where other Oracle process's cause problem.

Excessive fragmentation accompanied by heavy allocation and deallocation of extents can lead to the problem also as the ST lock is involved in acess to the base tables fet$ and uet$ which hold all extent information.

Our first set of problems with ST locks was traced to excessive fragmentation. Later we had problems running OPS when both systems attempted to coalesce the same tablespace at the same time. There are events to set coalescing off for an instance to handle this problem.

Your best bet is to look at your sort activity. --
Mark D. Powell -- The only advice that counts is the advice that  you follow so follow your own advice --

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Tue Feb 01 2000 - 14:46:39 CST