LindaC
asked on
Why does a 11.2 database created the redo logs with a blocksize of 512? How to verify that?
Hi experts:
Why does a 11.2 database created the redo logs with a blocksize of 512, when you can see that the filesystems blocksize are 4096? How to verify why this was created in this way?
-oracle:/home/oracle> lsfs -q /dev/oemlv_red1
Name Nodename Mount Pt VFS Size Options Auto Accounting
/dev/oemlv_red1 -- /claroproem/REDO1 jfs2 6291456 rw yes no
(lv size: 6291456, fs size: 6291456, block size: 4096, sparse files: yes, inline log: no, inline log size: 0, EAformat: v1, Quota: no, DMAPI: no, VIX: yes, EFS: no, ISNAPSHOT: no, MAXEXT: 0)
-oracle:/home/oracle> exit
SQL> SELECT BLOCKSIZE FROM V$LOG;
BLOCKSIZE
----------
512
512
512
Why does a 11.2 database created the redo logs with a blocksize of 512, when you can see that the filesystems blocksize are 4096? How to verify why this was created in this way?
-oracle:/home/oracle> lsfs -q /dev/oemlv_red1
Name Nodename Mount Pt VFS Size Options Auto Accounting
/dev/oemlv_red1 -- /claroproem/REDO1 jfs2 6291456 rw yes no
(lv size: 6291456, fs size: 6291456, block size: 4096, sparse files: yes, inline log: no, inline log size: 0, EAformat: v1, Quota: no, DMAPI: no, VIX: yes, EFS: no, ISNAPSHOT: no, MAXEXT: 0)
-oracle:/home/oracle> exit
SQL> SELECT BLOCKSIZE FROM V$LOG;
BLOCKSIZE
----------
512
512
512
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the documentation.
Copy/paste from Oracle
http://docs.oracle.com/cd/E14072_01/server.112/e10595/onlineredo002.htm
"Unlike the database block size, which can be between 2K and 32K, redo log files always default to a block size that is equal to the physical sector size of the disk. Historically, this has typically been 512 bytes (512B)."