Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Striping and CI Locks

Re: Striping and CI Locks

From: Christian Lang <clang_at_mediaprint.at>
Date: 5 Feb 2002 00:18:55 -0800
Message-ID: <6cf185c9.0202050018.3de5ed93@posting.google.com>


Hi,
I'm not using OPS. I think that the CI Locks are caused of DBWR. I'm using DB_WRITERS = 4, async_read/write is set to FALSE.

In Note 10417444.6 on Metalink I read that the value of DB_FILE_SIMULTANEOUS_WRITES should be correct if Stripesets are used. (4 times the max number of Disk in the biggest stripe).

will see wheter this solves my problem.

thank you very much for your suggestion. Chris
clang_at_mediaprint.at (Christian Lang) wrote in message news:<6cf185c9.0202040626.7e252796_at_posting.google.com>...
> Hi,
> at the last weekend I moved our 130G Production DB (7.3.4.5 on Solaris 2.6)
> from Single Disks to a Stripe set.
> --
> Today I detect that many sessions have to wait for enqeue
> --
> SELECT ksqsttyp "Lock",
> ksqstget "Gets",
> ksqstwat "Waits"
> FROM X$KSQST where KSQSTWAT>0;
> --
> CF 71 2
> CI 6572 1109
> SQ 5277 59
> ST 1067 179
> TM 162497 24
> TS 1295 8
> TX 67239 263
>
> My question:
> Could the CI Locks be associated with the StripSet ?
> Could the init.ora Param. DB_WRITERS=4 be associated with the StripSet ?
>
> any help will be appreciated
> Chris
Received on Tue Feb 05 2002 - 02:18:55 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US