Re: Oracle Server will write continually to control files.

"Antoine BRUNEL" <antoinebrunel_at_nospam_yahoo.fr> wrote in message news:41e576a6$0$18705$79c14f64_at_nan-newsreader-07.noos.net...
> Hi from Paris
>
> CKPT is continuously writing into control files, in order to store the
last
> SCNs.....

Is this true even though there is no connections to the database? I would understand the IO if we have process doing transactions on the database, but I have seen this constant writing even through no one is connected.
Over time you can see other file activity related to redologs and them you see reading and writing to the control files at different offsets. Still, this is a constant activity, every 3 seconds, writes 8K to a particular file offset.

Just curious if it can be adjusted. We already tried bringing down the BE OFO minimum quiet time to the lowest time and it is still not enough.

>
> and as said, for an hot backup, you have to create a "backup controlfile"
or
> "backup controlfile to trace"....
>

This is a backup of other files which are not Oracle related in the same drive. We use BE agents to perform the hot backup of the database, including the control file.

Thanks for the feedback.

>
> "Orlando Amador" <oamador_REMOVE_ME_at_obipr.jnj.com> a écrit dans le message
> de news: cs3h0f0ja3_at_news3.newsguy.com...
> > We have a Oralce 9.2 Standard database server with multiple database
> > instances. Each instance has 2 control files, although in the same
> > directory.
> >
> > Using a file monitor we find that the server will write a block of 8K to
> > offset 24576 of the control files every 3 seconds. I wonder if this
some
> > kind of synchronization, locking, or heartbeat function in the database.
> > The accumulated IO from the writes from a single database is not a
> > problem,
> > but the accumulation from multiple database is creating problem for our
> > backup software (Veritas BackupExec with OFO).
> >
> > We figure that we can repartition this server and separate the databases
> > in
> > separate disk, but we are saving that as a last resort. I was hopping
> > someone could point me to the reason of this updates and if there is a
way
> > to configure the timing? Maybe this is a required function but it could
> > be
> > slow down a bit? This updates happens constantly, even when the
database
> > is
> > not in use and there is no connections.
> >
> > Any suggestions?
> >
> > 11:39:33 AM oracle.exe:1128 WRITE

D:\oracle\oradata\ISODEV\CONTROL01.CTL
> > SUCCESS Offset: 24576 Length: 8192
> > 11:39:33 AM oracle.exe:1128 WRITE

D:\oracle\oradata\ISODEV\CONTROL02.CTL
> > SUCCESS Offset: 24576 Length: 8192
> > 11:39:37 AM oracle.exe:1128 WRITE

D:\oracle\oradata\ISODEV\CONTROL01.CTL
> > SUCCESS Offset: 24576 Length: 8192
> > 11:39:37 AM oracle.exe:1128 WRITE

D:\oracle\oradata\ISODEV\CONTROL02.CTL
> > SUCCESS Offset: 24576 Length: 8192
> > 11:39:40 AM oracle.exe:1128 WRITE

D:\oracle\oradata\ISODEV\CONTROL01.CTL
> > SUCCESS Offset: 24576 Length: 8192
> > 11:39:40 AM oracle.exe:1128 WRITE

D:\oracle\oradata\ISODEV\CONTROL02.CTL
> > SUCCESS Offset: 24576 Length: 8192
> > 11:39:43 AM oracle.exe:1128 WRITE

D:\oracle\oradata\ISODEV\CONTROL01.CTL
> > SUCCESS Offset: 24576 Length: 8192
> > 11:39:43 AM oracle.exe:1128 WRITE

D:\oracle\oradata\ISODEV\CONTROL02.CTL
> > SUCCESS Offset: 24576 Length: 8192
> > 11:39:46 AM oracle.exe:1128 WRITE

D:\oracle\oradata\ISODEV\CONTROL01.CTL
> > SUCCESS Offset: 24576 Length: 8192
> > 11:39:46 AM oracle.exe:1128 WRITE

D:\oracle\oradata\ISODEV\CONTROL02.CTL
> > SUCCESS Offset: 24576 Length: 8192
> >
> > Saludos
> > Orlando Amador
> >
> >
> >
>
>
Received on Thu Jan 13 2005 - 16:34:12 CST