We had a 2 node cluster installation (11.2.0.2) (ASM + GI standard installation). This supported our 2 node rac (2 rac databases on this boxes).
To this combination we added a 3rd database which was non-rac. The database files were on NAS and just like any of our single database (non-rac) databases, we had the following mount options
rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,tcp 0 0
When we tried to mount the asm diskgroup that supported this database, the asm alert log reported an issue with mount options and the diskgroup would not mount. The exact error was
WARNING:NFS file system /db/of3uat mounted with incorrect options(rw,vers=3,rsize=32768,wsize=32768,hard,proto=tcp,timeo=600,retrans=2,sec=sys,addr=vfiler9-3248)
WARNING:Expected NFS mount options: rsize>=32768,wsize>=32768,hard,noac/actimeo=0
Searched on metalink and found note 1367321.1. Per this note (though no exact hit) it was ok to get the above warning.
But metalink note 359515.1 had the solution (athough not directly mentioned in the note).
Per this noted, if you are on non-rac, the mount options you need to use for datafiles were
rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,tcp
and for rac it was
rw,bg,hard,nointr,rsize=32768, wsize=32768,tcp,actimeo=0, vers=3,timeo=600
So eventhough we are trying to bring up a non-rac database, since we are using the GI + ASM infrastructure that was originally installed for rac databases, we had to mount the file system that supported the non-rac database also using the same options that are used for rac (rw,bg,hard,nointr,rsize=32768, wsize=32768,tcp,actimeo=0, vers=3,timeo=600)
When this change was made, we were able to mount the diskgroup without any issues.
To this combination we added a 3rd database which was non-rac. The database files were on NAS and just like any of our single database (non-rac) databases, we had the following mount options
rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,tcp 0 0
When we tried to mount the asm diskgroup that supported this database, the asm alert log reported an issue with mount options and the diskgroup would not mount. The exact error was
WARNING:NFS file system /db/of3uat mounted with incorrect options(rw,vers=3,rsize=32768,wsize=32768,hard,proto=tcp,timeo=600,retrans=2,sec=sys,addr=vfiler9-3248)
WARNING:Expected NFS mount options: rsize>=32768,wsize>=32768,hard,noac/actimeo=0
Searched on metalink and found note 1367321.1. Per this note (though no exact hit) it was ok to get the above warning.
But metalink note 359515.1 had the solution (athough not directly mentioned in the note).
Per this noted, if you are on non-rac, the mount options you need to use for datafiles were
rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,tcp
and for rac it was
rw,bg,hard,nointr,rsize=32768, wsize=32768,tcp,actimeo=0, vers=3,timeo=600
So eventhough we are trying to bring up a non-rac database, since we are using the GI + ASM infrastructure that was originally installed for rac databases, we had to mount the file system that supported the non-rac database also using the same options that are used for rac (rw,bg,hard,nointr,rsize=32768, wsize=32768,tcp,actimeo=0, vers=3,timeo=600)
When this change was made, we were able to mount the diskgroup without any issues.
No comments:
Post a Comment