Here is what I got from the OS: >>cd /u02/oradata/LMSUAT [/u02/oradata/LMSUAT][oracle] >>ls -l total 1242384 -rw-r----- 1 oracle oinstall 6930432 Jun 20 19:14 control02.ctl -rw-r----- 1 oracle oinstall 209716224 Jun 17 12:17 log1.log -rw-r----- 1 oracle oinstall 209716224 Jun 19 03:00 log2.log -rw-r----- 1 oracle oinstall 209716224 Jun 20 19:12 log3.log [/u02/oradata/LMSUAT][oracle] >> >> >> >>cd /u03/oradata/LMSUAT [/u03/oradata/LMSUAT][oracle] >>ls -l total 1242384 -rw-r----- 1 oracle oinstall 6930432 Jun 20 19:14 control03.ctl -rw-r----- 1 oracle oinstall 209716224 Jun 17 12:17 log1.log -rw-r----- 1 oracle oinstall 209716224 Jun 19 03:00 log2.log -rw-r----- 1 oracle oinstall 209716224 Jun 20 19:14 log3.log [/u03/oradata/LMSUAT][oracle] >> And still the "bdf" command's output suggests that the /u02 is 3% full and /u03 is 0% full. Could those files under /u03 be sparse files? But then how the multiplexation of log files mitigate the risk of data loss in case of media failure? Thanks. ~ Amir Gheibi On Fri, Jun 19, 2009 at 3:09 PM, Mathias Magnusson < mathias.magnusson@xxxxxxxxx> wrote: > Why not also list the size of the files as the DB and as the operating > system knows it? > Maybe also a "find /u02" and "find /u3" to verify that all you have there > is logfiles? > > Mathias > > > On Fri, Jun 19, 2009 at 8:26 AM, Amir Gheibi <gheibia@xxxxxxxxx> wrote: > >> Hi listers, >> I have a HP-UX box with Oracle 10gR2 installed in it. I created a Database >> and enabled auto archive. The log files and control files are multiplexed >> and live in different disks. >> >> >> *>>sqlplus / as sysdba* >> * >> * >> *SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jun 19 14:07:15 2009* >> * >> * >> *Copyright (c) 1982, 2005, Oracle. All rights reserved.* >> * >> * >> * >> * >> *Connected to:* >> *Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit >> Production* >> *With the Partitioning, OLAP and Data Mining options* >> * >> * >> *SQL> COLUMN GROUP# FORMAT 9;* >> *SQL> COLUMN MEMBER FORMAT a30;* >> *SQL> COLUMN TYPE FORMAT a10;* >> *SQL> SELECT GROUP#, MEMBER, TYPE, IS_RECOVERY_DEST_FILE FROM V$LOGFILE;* >> * >> * >> * >> * >> *GROUP# MEMBER TYPE IS_* >> *------ ------------------------------ ---------- ---* >> * 1 /u02/oradata/LMSUAT/log1.log ONLINE NO* >> * 1 /u03/oradata/LMSUAT/log1.log ONLINE NO* >> * 2 /u02/oradata/LMSUAT/log2.log ONLINE NO* >> * 2 /u03/oradata/LMSUAT/log2.log ONLINE NO* >> * 3 /u02/oradata/LMSUAT/log3.log ONLINE NO* >> * 3 /u03/oradata/LMSUAT/log3.log ONLINE NO* >> * >> * >> *6 rows selected.* >> * >> * >> * >> * >> What I don't understand is the usage of the disk in /u02 and /u03. >> >> Here is a partial outcome of the "*bdf*" command: >> >> */dev/vg01/lvol1 209682432 4260600 203820416 2% /u01* >> */dev/vg02/lvol1 209682432 4048992 204027056 2% /u02* >> */dev/vg03/lvol1 209682432 629888 207419328 0% /u03* >> */dev/vg04/lvol1 209682432 7513480 200589552 4% /u04* >> * >> * >> /u02 is filled 2% but not /u03. >> Don't they contain the same copy of the log files? >> >> By the way, there is nothing other than those log files in /u02 and /u03. >> >> Thanks. >> >> ~ Amir Gheibi >> > >