Exadata tools like dbaascli and exadbcpatchmulti are very handy and time saving. However when they don't work it can be frustrating and cause hours of work, or worse it can mean having to create an SR.
# dbaascli patch tools apply --patchid LATEST
-bash: /bin/dbaascli: No such file or directory
What do you do when dbaascli is not recognized on your system? You have to manually reinstall. Of main importance is knowing your storage container URL. It is stored at
/var/opt/oracle/exapatch/exadbcpatch.cfg
It looks like:
(Make sure you keep this URL stored somewhere, so if you lose it from the .cfg file, you will be able to manually restore it)
As long as you have your URL you can follow the below directions to manually re-install dbaastools. (URLs given are for demonstration and will be different in your case)
(as root)
cd /tmp
curl -O https://storage.us1.ocm.ID.oraclecloudatcustomer.com/v1/Storage-idcs-cloudinfra-us1/dbaas_patch/19.1.1.1.0/200204/dbaastools_exa.rpm
ls -lrt dbaastools_exa.rpm <<< Please make sure it got download and then proceed further.
rpm -qa --last | grep dbaastools_exa
rpm -ev dbaastools_exa
rpm -ivh dbaastools_exa.rpm
rpm -qa --last | grep dbaastools_exa
►► Once tool upgrade is completed modify Config file (check all nodes if RAC)
chmod 755 /var/opt/oracle/exapatch/exadbcpatch.cfg
vi /var/opt/oracle/exapatch/exadbcpatch.cfg
chmod 555 /var/opt/oracle/exapatch/exadbcpatch.cfg
►►Once above is done - run following command to verify from the first Node only
dbaascli patch tools list
/var/opt/oracle/misc/platforminfo
rpm -qa --last | grep -i dbaastools_exa
Comments