You may want to look up the init.ora parameter temp_table_locks. A couple
of years ago when our site was having ST lock related problems and after
talking to Oracle support we had to bump this number up. Increasing the
size of temporary segments and setting the initial and next extent equal
with pctincrease set to zero is a good idea. You can query v$sysstat to
check to see if you need more enqueue resources. If you change
enqueue_resources you may need to adjust dm_locks parameter also.
BADRI <Badri_at_cris.com> wrote in article
<6gtqg1$kvv_at_examiner.concentric.net>...
> Hi:
>
> How many locks of type ST (space management) can exist in
> the database? Does this lock type serialize transactions under high load?
> This is a followup to the ORA 1575 (timeout occurred waiting for
> space management resource). It seems like it is waiting for a lock
> of type ST that is held in exclusive mode by other xns at that time.
>
> I was wondering if increasing enqueue resources would help
> among other steps such as making pctincrease 0 on temp tablespaces,
> making initial extent in temp tablespaces larger and making
sort_area_size
> larger.
>
> is there any documentation on how many locks of a given type
> can exist?
>
> thanks a lot,
>
> -Badri
>
Received on Wed Apr 15 1998 - 10:39:21 CDT
