In our test environment, we use the embedded Oracle DB and cannot move it to the new vApp due to the following errors:
2024 Jan 17 10:54:09 test-iga-vapp configureServices Stopping previously defined service improvisioning as it is no longer present on this server
2024 Jan 17 10:54:09 test-iga-vapp configureServices Processing oracle-xe
2024 Jan 17 10:54:09 test-iga-vapp configureServices Enabling service flag for: oracle-xe
2024 Jan 17 10:54:09 test-iga-vapp configureServices Initializing service oracle-xe
2024 Jan 17 10:54:09 test-iga-vapp InitSvc [INFO] Initializing Oracle Database Express 11g
2024 Jan 17 10:54:09 test-iga-vapp oracle-xe.sh Extracting archive oracle-xe.tgz
2024 Jan 17 10:54:24 test-iga-vapp oracle-xe.sh Granting permissions to the config group on /u01/app/oracle/diag/rdbms/xe/XE/trace
2024 Jan 17 10:54:24 test-iga-vapp oracle-xe.sh [INFO] Configuring firewall rule for xx.xx.xx.xx
2024 Jan 17 10:54:24 test-iga-vapp oracle-xe.sh Redirecting to /bin/systemctl start iptables.service
2024 Jan 17 10:54:24 test-iga-vapp oracle-xe.sh Failed to start iptables.service: Unit iptables.service not found.
2024 Jan 17 10:54:33 test-iga-vapp oracle-xe.sh Starting oracle-xe (via systemctl): [ OK ]
2024 Jan 17 10:54:33 test-iga-vapp oracle-xe.sh Waiting for the Instance 'XE' to start...
2024 Jan 17 10:56:50 test-iga-vapp oracle-xe.sh Waiting for the Instance 'XE' to start...
2024 Jan 17 10:56:52 test-iga-vapp oracle-xe.sh [ERROR] the Instance 'XE' did not start after 120 seconds
2024 Jan 17 10:56:52 test-iga-vapp InitSvc [ERROR] Initialization script for oracle-xe exited with error status 127
2024 Jan 17 10:56:52 test-iga-vapp configureServices [ERROR] The service oracle-xe failed to initialize (error code 127). Please inspect the log file: /opt/CA/VirtualAppliance/logs/ca_vapp_main.log
Release : 14.5 GA
Component : CA Identity Suite Virtual Appliance
Engineering created a hotfix HF_VA-14.5.0-20240130112240-DE589849.tgz.gpg for this issue.
First, we need to apply the patch before deployment on all the nodes, and then proceed with the deployment.
If you face the same issue, please create a support case and request for the above-mentioned hotfix.