I recently had to install an Oracle Database Appliance X11 HA and it failed when creating the appliance:<\/p>\n\n\n\n
[root@oak0 ~]# odacli create-appliance -r \/u01\/patch\/my_new_oda.json\n...\n[root@mynewoda ~]# odacli describe-job -i 88e4b5e3-3a73-4c18-9d9f-960151abc45e\n\nJob details \n----------------------------------------------------------------\n ID: 88e4b5e3-3a73-4c18-9d9f-960151abc45e\n Description: Provisioning service creation\n Status: Failure (To view Error Correlation report, run \"odacli describe-job -i 88e4b5e3-3a73-4c18-9d9f-960151abc45e --ecr\" command)\n Created: April 23, 2025 16:15:35 CEST\n Message: DCS-10001:Internal error encountered: Failed to provision GI with RHP at the home: \/u01\/app\/19.26.0.0\/grid: DCS-10001:Internal error encountered: PRGH-1002 : Failed to copy files from \/opt\/oracle\/rhp\/RHPCheckpoints\/rhptemp\/grid8631129022929485455.rsp to \/opt\/oracle\/rhp\/RHPCheckpoints\/wOraGrid192600\nPRKC-1191 : Remote command execution setup check for node mynewoda using shell \/usr\/bin\/ssh failed.\nNo ECDSA host key is known for mynewoda and you have requested strict checking.Host key verification failed...<\/code><\/pre>\n\n\n\nIt happened randomly in the past that we got this error „host key verification failed“ and we just had to rerun our „odacli create-appliance“ command again. However, this time restarting was not possible:<\/p>\n\n\n\n
[root@mynewoda ~]# odacli create-appliance -r \/u01\/patch\/my_new_oda.json\nDCS-10047:Same job is already running: Provisioning FAILED in different request.<\/code><\/pre>\n\n\n\nFollowing MOS Note „ODA Provisioning Fails to Create Appliance w\/ Error: DCS-10047:Same Job is already running : Provisioning FAILED in different request. (Doc ID 2809836.1)“ I cleaned up the ODA, updated the repository with the Grid Infrastructure clone and DB clone:<\/p>\n\n\n\n
Stop the dcs agent on both nodes:<\/p>\n\n\n\n
# systemctl stop initdcsagent<\/code><\/pre>\n\n\n\nThen, run cleanup.pl on ODA node 0.<\/p>\n\n\n\n
# \/opt\/oracle\/oak\/onecmd\/cleanup.pl -f\n...<\/code><\/pre>\n\n\n\nIf you get warnings that the cleanup cannot transfer the public key to node 1 or cannot setup SSH equivalence, then run the cleanup on node 1 as well.<\/p>\n\n\n\n
At the end of the cleanup-output you get those messages:<\/p>\n\n\n\n
WARNING: After system reboot, please re-run \"odacli update-repository\" for GI\/DB clones,\nWARNING: before running \"odacli create-appliance\".<\/code><\/pre>\n\n\n\nSo, after the reboot I updated the repository with the GI and DB Clone:<\/p>\n\n\n\n
[root@oak0 patch]# \/opt\/oracle\/dcs\/bin\/odacli update-repository -f \/u01\/patch\/odacli-dcs-19.26.0.0.0-250127-GI-19.26.0.0.zip\n...\n[root@oak0 patch]# odacli describe-job -i 674f7c66-1615-450f-be27-4e4734abca97\n\nJob details \n----------------------------------------------------------------\n ID: 674f7c66-1615-450f-be27-4e4734abca97\n Description: Repository Update\n Status: Success\n Created: April 23, 2025 14:37:29 UTC\n Message: \/u01\/patch\/odacli-dcs-19.26.0.0.0-250127-GI-19.26.0.0.zip\n...\n\n[root@oak0 patch]# \/opt\/oracle\/dcs\/bin\/odacli update-repository -f \/u01\/patch\/odacli-dcs-19.26.0.0.0-250127-DB-19.26.0.0.zip\n...\n[root@oak0 patch]# odacli describe-job -i 4299b124-1c93-4d22-bac4-44a65cbaac67\n\nJob details \n----------------------------------------------------------------\n ID: 4299b124-1c93-4d22-bac4-44a65cbaac67\n Description: Repository Update\n Status: Success\n Created: April 23, 2025 14:39:34 UTC\n Message: \/u01\/patch\/odacli-dcs-19.26.0.0.0-250127-DB-19.26.0.0.zip\n...<\/code><\/pre>\n\n\n\nChecked that the clones are available:<\/p>\n\n\n\n
[root@oak0 patch]# ls -ltrh \/opt\/oracle\/oak\/pkgrepos\/orapkgs\/clones\ntotal 12G\n-rwxr-xr-x 1 root root 6.0G Jan 28 03:33 grid19.250121.tar.gz\n-rwxr-xr-x 1 root root 21 Jan 28 03:34 grid19.250121.tar.gz.info\n-r-xr-xr-x 1 root root 5.4G Jan 28 03:42 db19.250121.tar.gz\n-rw-rw-r-- 1 root root 19K Jan 28 03:42 clonemetadata.xml\n-rw-rw-r-- 1 root root 21 Jan 28 03:43 db19.250121.tar.gz.info\n[root@oak0 patch]# <\/code><\/pre>\n\n\n\nThe same on node 1:<\/p>\n\n\n\n
[root@oak1 ~]# ls -ltrh \/opt\/oracle\/oak\/pkgrepos\/orapkgs\/clones\ntotal 12G\n-rwxr-xr-x 1 root root 6.0G Jan 28 03:33 grid19.250121.tar.gz\n-rwxr-xr-x 1 root root 21 Jan 28 03:34 grid19.250121.tar.gz.info\n-r-xr-xr-x 1 root root 5.4G Jan 28 03:42 db19.250121.tar.gz\n-rw-rw-r-- 1 root root 19K Jan 28 03:42 clonemetadata.xml\n-rw-rw-r-- 1 root root 21 Jan 28 03:43 db19.250121.tar.gz.info\n[root@oak1 ~]# <\/code><\/pre>\n\n\n\nBefore running the create-appliance again, you should first validate the storage topology on both nodes again.<\/p>\n\n\n\n
[root@oak0 ~]# odacli validate-storagetopology\nINFO : ODA Topology Verification \nINFO : Running on Node0 \nINFO : Check hardware type \nINFO : Check for Environment(Bare Metal or Virtual Machine)\nSUCCESS : Type of environment found : Bare Metal\nINFO : Check number of Controllers \nSUCCESS : Number of onboard OS disk found : 2\nSUCCESS : Number of External SCSI controllers found : 2\nINFO : Check for Controllers correct PCIe slot address\nSUCCESS : Internal RAID controller : \nSUCCESS : External LSI SAS controller 0 : 61:00.0\nSUCCESS : External LSI SAS controller 1 : e1:00.0\nINFO : Check for Controller Type in the System\nSUCCESS : There are 2 SAS 38xx controller in the system\nINFO : Check if JBOD powered on \nSUCCESS : 1JBOD : Powered-on\nINFO : Check for correct number of EBODS(2 or 4)\nSUCCESS : EBOD found : 2\nINFO : Check for External Controller 0 \nSUCCESS : Controller connected to correct EBOD number\nSUCCESS : Controller port connected to correct EBOD port\nSUCCESS : Overall Cable check for controller 0\nINFO : Check for External Controller 1 \nSUCCESS : Controller connected to correct EBOD number\nSUCCESS : Controller port connected to correct EBOD port\nSUCCESS : Overall Cable check for Controller 1\nINFO : Check for overall status of cable validation on Node0\nSUCCESS : Overall Cable Validation on Node0\nINFO : Check Node Identification status \nSUCCESS : Node Identification\nSUCCESS : Node name based on cable configuration found : NODE0\nINFO : The details for Storage Topology Validation can also be found in the log file=\/opt\/oracle\/oak\/diag\/oak0\/oak\/storagetopology\/StorageTopology-2025-04-23-14:42:34_70809_7141.log\n[root@oak0 ~]# <\/code><\/pre>\n\n\n\nValidate the storage-topology on node 1 as well. Not validating the storage topology may lead to the following error when creating the appliance again:<\/p>\n\n\n\n
OAK-10011:Failure while running storage setup on the system. Cause: Node number set on host not matching node number returned by storage topology tool. Action: Node number on host not set correctly. For default storage shelf node number needs to be set by storage topology tool itself.<\/code><\/pre>\n\n\n\nAfterwards the „odacli create-appliance“ should run through.<\/p>\n\n\n\n
Summary<\/h3>\n\n\n\n
If your „odacli create-appliance“ fails on an ODA HA environment and you cannot restart it, then run a cleanup, update the repository with the Grid Infra- and DB-clone and validate the storage-topology before doing the create-appliance again.<\/p>\n","protected":false},"excerpt":{"rendered":"
I recently had to install an Oracle Database Appliance X11 HA and it failed when creating the appliance: It happened randomly in the past that we got this error „host key verification failed“ and we just had to rerun our „odacli create-appliance“ command again. However, this time restarting was not possible: Following MOS Note „ODA […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[27,54,3,53],"class_list":["post-57","post","type-post","status-publish","format-standard","hentry","category-oracle","tag-oda","tag-odacli-create-appliance","tag-oracle","tag-oracle-database-appliance"],"_links":{"self":[{"href":"http:\/\/cbleile.de\/wordpress\/wp-json\/wp\/v2\/posts\/57","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/cbleile.de\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/cbleile.de\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/cbleile.de\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/cbleile.de\/wordpress\/wp-json\/wp\/v2\/comments?post=57"}],"version-history":[{"count":1,"href":"http:\/\/cbleile.de\/wordpress\/wp-json\/wp\/v2\/posts\/57\/revisions"}],"predecessor-version":[{"id":58,"href":"http:\/\/cbleile.de\/wordpress\/wp-json\/wp\/v2\/posts\/57\/revisions\/58"}],"wp:attachment":[{"href":"http:\/\/cbleile.de\/wordpress\/wp-json\/wp\/v2\/media?parent=57"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/cbleile.de\/wordpress\/wp-json\/wp\/v2\/categories?post=57"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/cbleile.de\/wordpress\/wp-json\/wp\/v2\/tags?post=57"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}