-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
19c RAC on OL8 running on Mac #1
Comments
HI @mikedesouza ,
If I was you I'd try either of the below :
see vagrant Note here HTH
|
Thanks mate appreciate the reply will do that |
Hi
just tried running ol8_19 repo on Mac os , the only changes i made are
asm_disk_1: /Users/md/vagrant/rac/ol8_19/asm_disk_1.vdi
asm_disk_2: /Users/md/vagrant/rac/ol8_19/asm_disk_2.vdi
asm_disk_3: /Users/md/vagrant/rac/ol8_19/asm_disk_3.vdi
asm_disk_4: /Users/md/vagrant/rac/ol8_19/asm_disk_4.vdi
Dns server was fine
default: dnsmasq-2.79-13.el8.x86_64
default:
default: Complete!
default: Created symlink /etc/systemd/system/multi-user.target.wants/dnsmasq.service → /usr/lib/systemd/system/dnsmasq.service.
Node 2 was fine
default: Host key verification failed.
default: ******************************************************************************
default: Set Hostname. Tue Jan 5 10:58:18 UTC 2021
default: ******************************************************************************
default: ******************************************************************************
default: Passwordless SSH Setup for root. Tue Jan 5 10:58:18 UTC 2021
default: ******************************************************************************
default: Host key verification failed.
Node 1 had some issues
see attachments
default: /vagrant/scripts/oracle_create_database.sh: line 50: /u01/app/oracle/product/19.0.0/dbhome_1/bin/sqlplus: Permission denied
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
node1_errors.txt
The text was updated successfully, but these errors were encountered: