Closed carroarmato0 closed 9 years ago
Hi,
it should work perfectly can you take look at this CentOS 6.6 vagrant box with Oracle Database 11.2.0.4 on NFS ASM ASM vagrant box https://github.com/biemond/biemond-oradb-vagrant-11.2-ASM
thanks
I'll take a closer look
on https://github.com/biemond/biemond-oradb-vagrant-11.2-ASM/blob/master/puppet/manifests/site.pp#L211
I install asm and db on https://github.com/biemond/biemond-oradb-vagrant-11.2-ASM/blob/master/puppet/manifests/site.pp#L264
but the directories are very crucial
oraInventory_dir: '/app'
global oracle vars oracle_base_dir: '/app/oracle' oracle_home_dir: '/app/oracle/product/11.2/db'
global OS vars oracle_os_user: "oracle" oracle_os_group: "dba" oracle_download_dir: "/var/tmp/install" oracle_source: "/software"
grid_base_dir: '/app/grid' grid_home_dir: '/app/grid/product/11.2/grid'
grid_os_user: "grid" grid_os_group: "asmdba"
using a common oraInventory proved to have solved the issue for me. Thank you.
It's probably not meant to work this way, but I happen to use installdb and installasm on the same node (mostly for testing purposes).
This causes both installations to happen and work correctly during the first deploy, but afterwards during the next runs, the module gets confused because it makes a comparison between the different installations and decides to re-do the installation of one of them over and over again:
So basically this is the problem: