Datatombraider's Blog


GI installation using AU_SIZE=4M for the initial disk group

Filed under: Oracle — datatombraider @ 21:49

The GI installer doesn’t let you choose an au_size for the initial disk group. Usually i create disk groups with au_size=4M instead of the default 1M.

While it’s easy to use a temporary disk group for the installation and move OCR and voting disks to a 4M disk group afterwards, moving the ASM spfile is a little bit trickier because of GPNP. But there’s a workaround, unsupported of course.

just install the GI software but before running on the install node change GI/install/ on this node after making a backup:

—        2010-08-20 18:13:18.000000000 +0200
+++    2010-09-21 13:54:04.000000000 +0200
@@ -9073,6 +9073,10 @@
push @runasmca, ‘-redundancy’, $CFG->params(‘ASM_REDUNDANCY’);

+  if (isFirstNodeToStart()) {
+    push @runasmca, ‘-au_size’, 4;
+  }
if ($CFG->params(‘ASM_DISCOVERY_STRING’)) {
push @runasmca, ‘-diskString’, “‘$ASM_DISCOVERY_STRING'”;

Then run on all nodes, the disk group will be created with au_size=4M. After that revert the change.

I’ve opened ER #10136487 which is still under review by Oracle development.

Update: ER has been implemented in


Leave a Comment »

No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Create a free website or blog at