ORA-15099
官方文档解释为
请注意 ASM对于单盘的限制为2T。也就是说单个LUN不能大于2TB。个人建议不要大于1.7T。
ORA-15099: disk 'string' is larger than maximum size of string MBs
Cause: The specified size of the disk was too big to allow the disk to become part of the diskgroup.
Action: Specify a smaller disk size than the maximum allowed size.
这次在联通机房遇到了这个BUG。1.2T的lun不被ASMCA识别。
清空了磁盘头还是没用,到metalink一查,果然有个BUG。
在AIX上,单个LUN大于1T,ASM看到的可能要比1T大。由于时间较紧,所以只好在容量上进行妥协。
把1.2T的lun降为900G,果然可以识别了。
Bug 10072750 AIX: ASM sees 1 TB disks as larger than their actual size (ORA-15099)
This note gives a brief overview of bug 10072750.
The content was last updated on: 07-JUL-2011
Click here for details of each of the sections below.
Affects:
Product (Component) Oracle Server (Rdbms)
Range of versions believed to be affected Versions BELOW 12.1
Versions confirmed as being affected
11.2.0.2
11.2.0.1
Platforms affected
IBM AIX Power Based Systems (64bit)
Fixed:
This issue is fixed in
12.1 (Future Release)
11.2.0.3
Symptoms:
Related To:
ORA-15099
Large File / Memory Issues (Eg: 2Gb)
Automatic Storage Management (ASM)
Description
When the disk size is greater than 1 TB then the disk size
for ASM is thought to be more than the actual size.
Rediscovery Notes:
When the size of the disk is greater than 1 TB and there is problem
with create diskgroup command, with error ORA-15099, there is a
possibility that this bug is hit.
Workaround
While creating the diskgroup, manually specify the disk size
Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. For questions about this bug please consult Oracle Support.
References
Bug:10072750 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article