OK, I really do not know what other title I should use for this post.<\/p>\n
I have developed and presented a few times my personal approach to Oracle Home provisioning and patching. You can read more in this series<\/a>.<\/p>\n With this approach:<\/p>\n When I need to install it, I just unzip the golden image and attach it to the Central Inventory.<\/p>\n I have discovered quite longtime ago that, every time I was attaching the home to the inventory, the binaries were relinked with rac_off<\/strong>, disregarding the fact that the home that I zipped actually had RAC enabled. This is quite annoying at my work at CERN, as all our databases are RAC.<\/p>\n So my solution to the problem is to detect if the server is on a cluster, and relink on the fly:<\/p>\n This is a simplified snippet of my actual code, but it gives the idea.<\/p>\n What causes the relink with rac_off?<\/strong><\/p>\n I have discovered recently that the steps used by the runInstaller process to attach the Oracle Home are described in this file:<\/p>\n and in my case, for all my golden images, it contains:<\/p>\n So, it does not matter how I prepare my images: unless I change this file and put rac_on, the runInstaller keeps relinking with rac_off.<\/p>\n I have thought about changing the file, but then realized that I prefer to check and recompile at runtime, so I can reuse my images also for standalone servers (in case we need them).<\/p>\n Just to avoid surprises, it is convenient to check if a ORACLE_HOME is linked with RAC with this small function:<\/p>\n This is true especially for Grid Infrastructure golden images, as they have the very same behavior of RDBMS homes, with the exception that they might break out-of-place patching if RAC is not enabled: the second ASM instance will not mount because the first will be exclusively mounted without the RAC option.<\/p>\n <\/p>\n HTH.<\/p>\n —<\/p>\n Ludovico<\/p>\n","protected":false},"excerpt":{"rendered":" OK, I really do not know what other title I should use for this post. I have developed and presented a few times my personal approach to Oracle Home provisioning and patching. You can read more in this series. With … Continue reading \n
### EARLIER, IN THE ENVIRONMENT SCRIPTS\r\nif [ -f \/etc\/oracle\/olr.loc ] ; then\r\n export CRS_EXISTS=1\r\nelse\r\n export CRS_EXISTS=0\r\nfi\r\n\r\n### LATER, AFTER ATTACHING THE ORACLE_HOME:\r\npushd $ORACLE_HOME\/rdbms\/lib\r\nif [ $CRS_EXISTS -eq 1 ] ; then\r\n\tmake -f ins_rdbms.mk rac_on\r\nelse\r\n\tmake -f ins_rdbms.mk rac_off\r\nfi\r\nmake -f ins_rdbms.mk ioracle<\/pre>\n
$ORACLE_HOME\/inventory\/make\/makeorder.xml<\/pre>\n
<ohmd:MAKE\r\nMAKEPATH=\"\/usr\/bin\/make\" FILENAME=\"rdbms\/lib\/ins_rdbms.mk\" >\r\n<ohmd:TARGET ACTIONTYPE=\"INSTALL\" TARGETNAME=\"rac_off\" >\r\n<ohmd:INPUT_LIST>\r\n<ohmd:INPUT VAL=\"ORACLE_HOME=%ORACLE_HOME%\"\/>\r\n<\/ohmd:INPUT_LIST>\r\n<ohmd:COMP_LIST>\r\n<ohmd:COMP NAME=\"oracle.rdbms\" VERSION=\"18.0.0.0.0\"\/>\r\n<\/ohmd:COMP_LIST>\r\n<\/ohmd:TARGET>\r\n<\/ohmd:MAKE>\r\n<\/pre>\n
$ type isRACoh\r\nisRACoh is a function\r\nisRACoh ()\r\n{\r\n OH2CHECK=${1:-$ORACLE_HOME};\r\n ar -t $OH2CHECK\/rdbms\/lib\/libknlopt.a | grep --color=auto kcsm.o > \/dev\/null;\r\n if [ $? -eq 0 ]; then\r\n echo \"Enabled\";\r\n else\r\n echo \"Disabled\";\r\n false;\r\n fi\r\n}\r\n<\/pre>\n