You must also set ASYNC_WRITE to false. Oracle on Solaris uses async
I/O by default and hence only needs one DBWR. If you set ASYNC_WRITE to
false, then having more than one DBWR is appropriate.
See Chapter 12 in the "Oracle7 for Solar 2.x Installation Guide
Release 7.1.6". I don't know where they have put this info in later
books, it seems to have disappeared.
I have never seen a case where the DBWR gets swamped while using async
I/O. Are you sure you are not seeing symptoms of some other I/O
bottleneck ?
--
Scott Kelley (skelley_at_online.disney.com)
Webmaster/Database Admistrator for Disney Online
voice: 818 623 3406 pager: 800 SKY 8888 pin #1140267
/*I don't know what I'm talking about and neither does the Disney Co.*/
Wang ZhenXI wrote:
>
> Hi,
>
> I have a test instance on Oracle7.2.2.4 running on Solaris2.5.1.
> Currently it has one DBWR process performing I/O on 3 RAID-1
> disks, whenever there is large amount of the write hiccup syndrome
> can be observed. So I inserted a DB_WRITERS = 3 parameter into
> the init.ora file.When the instance restarts with the new setting, I
> still see one DBWR process. The setting works for Oracle7.0 and HP-UX.
> So what went wrong ?
>
> Thanks
>
> Wang ZhenXi
Received on Thu Feb 20 1997 - 00:00:00 CST
