在前一個BLOG里面說到了怎么計算數(shù)據(jù)文件的大小，ls –l /8192-1，其實這里的8192是不正確的，只是通用情況下是這樣的，下面是MOS給的官方文檔，關于每種平臺下面的OS塊的大小
為增城等地區(qū)用戶提供了全套網(wǎng)頁設計制作服務，及增城網(wǎng)站建設行業(yè)解決方案。主營業(yè)務為成都網(wǎng)站建設、成都網(wǎng)站設計、增城網(wǎng)站設計，以傳統(tǒng)方式定制建設網(wǎng)站，并提供域名空間備案等一條龍服務，秉承以專業(yè)、用心的態(tài)度為用戶提供真誠的服務。我們深信只要達到每一位用戶的要求，就會得到認可，從而選擇與我們長期合作。這樣，我們也可以走得更遠！歡迎大家加入ORACLE超級群：17115662 免費解決各種ORACLE問題,以后BLOG將遷移到http://www.htz.pw
How an Oracle block# is mapped to a file offset (in bytes or OS blocks) (文檔 ID 761734.1)
修改時間:2011-2-15
類型:HOWTO
In this Document
Goal
Solution
Generic Platform Formula:
Alternate Platform Specific Formula (i.e. AIX and HP Tru64):
APPLIES TO:
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.1.0.8 - Release: 10.2 to 11.1
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.1.0.8 [Release: 10.2 to 11.1]
Information in this document applies to any platform.
GOAL
This document is about how an Oracle block number is mapped to a file offset (in bytes or OS blocks) for Generic OS platforms and includes an alternate formula for specific OS platforms like AIX and HP Tru64. These are the only 2 platforms where the Volume Manager reserves space for Metadata in the Oracle datafile.
For Oracle 10g and 10gR2 there are only two platforms with logical volume Metadata on raw devices: AIX and HP Tru64.
HP Tru64 is no longer supported on Oracle 11g, so AIX is the only one in 11g.
SOLUTION
Every Oracle file has an Operating System file header block ("BLOCK 0") created and maintained by Oracle, which is the size of a standard Oracle block. If multiple block sizes are being used then V$DATAFILE.BLOCK_SIZE should be queried for the file# in question.
"BLOCK 0" can be know as the "Oracle OS Header Block" or "Database Block# 0".
"BLOCK 1" is the Oracle Header Block that contains generic information for the File.
From the documentation: V$DATAFILE.BLOCK1_OFFSET is the "Offset from the beginning of the file to where the Oracle generic information begins.".
"BLOCK 1" offset = v$datafile.block1_offset
V$DATAFILE.BLOCK1_OFFSET do not make much sense for ASM. The value displayed is UB4MAXVAL (4-byte unsiged int max) for ASM when it cannot be computed.
Generic Platform Formula:
A general formula to locate the byte offset in any platform is:
block1_offset = v$datafile.block1_offset
oracle_block_size = v$datafile.block_size
offset = block1_offset + (oracle_block_number - 1) * oracle_block_size
Another way to calculate this offset is using the platform specific information:
Alternate Platform Specific Formula (i.e. AIX and HP Tru64):
Platform specific formula for a file offset to locate an Oracle block in a RAW Device:
offset = raw_device_block0_offset + (oracle_block_number * oracle_block_size)
AIX:
On AIX raw device, the logical volume metadata uses 4096 bytes. That would be the block0_offset on this platform. On HP Tru64 it is 65536 bytes.
raw_device_block0_offset = 4096
file_system_block0_offset = 0
Example:
Calculate the byte offset using the platform specific formula for block 30 in a RAW Device in AIX
oracle_block_size = 8192 (v$datafile.block_size)
oracle_block_number = 30
AIX raw_device_block0_offset = 4096
offset = 4096 + (30*8192) = 249856
Notes:
The above formulas are given in bytes.
file_system_block#_offset refers to any file systems like veritas, zfs, etc.
raw_device_block0_offset is the byte offset to locate the Oracle "BLOCK 0" in a raw device.
file_system_block0_offset is the byte offset to locate the Oracle "BLOCK 0" in a file system.
Formula To produce an offset in 4096 blocks in a RAW device in AIX:
offset
HP Tru64:
For HP Tru64 use:
raw_device_block0_offset = 65536
file_system_block0_offset = 0
另外有需要云服務器可以了解下創(chuàng)新互聯(lián)cdcxhl.cn，海內(nèi)外云服務器15元起步，三天無理由+7*72小時售后在線，公司持有idc許可證，提供“云服務器、裸金屬服務器、高防服務器、香港服務器、美國服務器、虛擬主機、免備案服務器”等云主機租用服務以及企業(yè)上云的綜合解決方案，具有“安全穩(wěn)定、簡單易用、服務可用性高、性價比高”等特點與優(yōu)勢，專為企業(yè)上云打造定制，能夠滿足用戶豐富、多元化的應用場景需求。
重慶分公司
重慶分公司
