The following are known issues deploying, updating, and managing Oracle Database Appliance DCS stack:
When deploying the appliance with VLAN, the GI configtools fail to run.
Hardware Models
Oracle Database Appliance X7-2S, X7-2M, and X7-2-HA
Oracle Database Appliance X6-2S, X6-2M, and X6-2L
Workaround
Run cleanup. If the system is X7-2-HA, run the cleanup on both nodes. The script will reboot the nodes.
#/opt/oracle/oak/onecmd/cleanup.pl
Create (deploy) the appliance without the DNS server.
This issue is tracked with Oracle bug 27597126.
When deploying the appliance, DCS-10045 error appears. There is an error retrieving the CPU cores of the second node.
Hardware Models
Oracle Database Appliance X7-2-HA
Workaround
Remove the following directory in Node0: /opt/oracle/dcs/repo/node_0
Remove the following directory in Node1: /opt/oracle/dcs/repo/node_1
Restart the dcs-agent
on both nodes.
cd /opt/oracle/dcs/bin initctl stop initdcsagent initctl start initdcsagent
This issue is tracked with Oracle bug 27527676.
In some cases, the deployment in the Web Console fails with status code 400: Unable to process JSON.
Hardware Models
Oracle Database Appliance X7-2S, X7-2M, and X7-2-HA
Oracle Database Appliance X6-2S, X6-2M, and X6-2L
Workaround
Restart the dcs-agent
, then open a new browser session to the Web Console to finish creating (deploying) the appliance.
cd /opt/oracle/dcs/bin initctl stop initdcsagent initctl start initdcsagent
This issue is tracked with Oracle bug 27535868.
Unable to create a test alert for Oracle Auto Service Request (ASR) that is configured with SNMP version 3.
When you configure an internal Oracle Auto Service Request (ASR) with SNMP version 3 and then generate a test, the test appears to success but the alert does not appear in the asr.log
file.
Hardware Models
Oracle Database Appliance X7-2S, X7-2M, and X7-2-HA
Oracle Database Appliance X6-2S, X6-2M, and X6-2L
Workaround
Configure Oracle ASR to use SNMP version 2. The command odacli test-asr
generates a test alert and updates the asr.log
file.
This issue is tracked with Oracle bug 27596890.