-
Notifications
You must be signed in to change notification settings - Fork 8
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
18c build failing at TASK [oradb-manage-db : manage-db | create/manage database] -[FATAL] ORA-03113: end-of-file on communication channel #5
Comments
I tried another time and now it stops at the manage tablespace Task
|
[oracle@racdb1 admin]$tnsping racdb is successful on both nodes though
[oracle@racdb2 oracle]$srvctl status database -db racdb
[oracle@racdb2 oracle]$sqlplus / as sysdba
I don't get why ansible play stopped |
Hi, sorry about the late answer. |
Hi, No problem Mikael. here is the hosts.yml file
and here is the Vagrantfile (added scan_name and oracle_home vars) I think I know where the problem comes from . here is the content of oravirt\extra-provision\ansible-oracle\group_vars\vbox-rac-dc1\databases.yml
oracle database dbca creation uses the variable oracle_db_name in my case rac_db but it seems to ignore the underscore durring creation (name is now racdb) . So I guess the dbca create pdb may look for a db that doesn't exists (rac_db ) . |
no it didn't fix it. |
Thanks!
I may already have a CDB and only want to create a PDB and then it doesn't make sense to run the DB provisioning step. |
Hi Mikaël,
the database creation was hanging because there was too much swapping in node 1.
|
you said ,
how can that be if you are creating the build from scratch . if I read your yaml well I see manage_db role called first then quite later manage-pdb . so at worse we can introduce a boulean var that decides on creating a db with pdb or not and call dbca once with one template responsefile. extra-provision/ansible-oracle/vbox-rac-dc1.yml
|
Great!
Yes, I have but it was slow
Yes, for this specific Vagrant project it builds everything from scratch, but the toolkit (ansible-oracle) is it's own project which can be run completely stand-alone and is just used as the provisioning step for this project I try to write my Ansible roles such that they do 1 thing. So I think that bundling the pdb creation with the create (C)DB step is bad idea. |
Hi Mikael, |
Hi @KoussHD ,
you could generate hash and override default with variable-precedence
|
thank you @yevp . It has been a while since I ran the build and deleted it few days later . But I'll give a try this weekend . |
Hi Mikael,
I have been trying your build for several times now and it still fails at the same stage .
I took the liberty to change few attributes ( ips ,hostnames,scan name,dbnames, db_home path ) in the corresponding VagrantFile and host.yml.
It seems that the failure kicks in just before or during PDB creation. As all the prior steps are processed until this task : > [oradb-manage-db : manage-db | create/manage database]
dbca creates the db but couldn't bounce the instances .(previous run had successfully installed dbs but stopped at the PDB creation)
here is the output I got at the last try :
when I check the crs status the instances are there but just not up and runing.
any idea what could be the problem here ? . I can show the host.yml and vagrant if you want .
Thanks again
The text was updated successfully, but these errors were encountered: