为什么ASM里的文件BLOCK1_OFFSET是4294967295这么一个奇怪的值呢？

武汉-SSH

select t.NAME,t.BLOCK1_OFFSET from v$datafile t
+DATA/aaa/datafile/system.262.735788807    4294967295
+DATA/aaa/datafile/undotbs1.263.735788811    4294967295
+DATA/aaa/datafile/sysaux.264.735788811    4294967295
+DATA/aaa/datafile/undotbs2.266.735788815    4294967295
+DATA/aaa/datafile/users.267.735788815    4294967295
+DATA/aaa/datafile/aaaaaa.273.735791083    4294967295
+DATA/aaa/datafile/aaa.389.735902487    4294967295
+DATA/aaa/datafile/aaaaaaa.776.768701343    4294967295
+FRA/aaa/datafile/aaaaaaa.824.769904049    4294967295
+FRA/aaa/datafile/undotbs1.1355.773922951    4294967295
+DATA/aaa/datafile/undotbs2.647.774624477    4294967295
+DATA/aaa/datafile/undotbs2.1174.774624577    4294967295

teapot

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.

2的32次方 - 1 = 4294967295

How an Oracle block# is mapped to a file offset (in bytes or OS blocks) [ID 761734.1]