![]() ![]() "description" : "Update-dcscomponents job completed and is not part of Agent job list", Successfully ran setupAgentAuth.sh zookeeper RPM upgrade is successful. "message" : "Update-dcscomponents is successful on all the node(s):DCS-Agent shutdown is successful. Odacli update-dcscomponents -v 19.17.0.0.0 Patch location validation Decem9:57:42 AM CET Decem9:57:42 AM CET Successĭcs-admin upgrade Decem9:57:42 AM CET Decem9:57:49 AM CET Success Patching from 19.13 will normally be easy as there are not that many changes. SHARED CONTROLLER FIRMWARE QDV1RF32 QDV1RF35 Unzip bundle Decem9:55:40 AM CET Decem9:56:09 AM CET Success It will work if you come from a newer version, from 19.16 for example.īut it’s not a problem as you can first register the patch only, update the DCS components and then register the GI clone: odacli update-repository -f /u03/app/oracle/oda-sm-19.17.0.0. On ODA X9-2 system disks are now smaller, so don’t hesitate to put the file on an nfs share or in the FRA acfs volume if you have acfs configured for your databases. Prepararing the patch and updating the DCS toolsĬopy the patch files on your ODA in a temp directory. Once the patch will be registered in the ODA repository, the “Available Version” column will be updated with versions provided within the patch. SHARED CONTROLLER FIRMWARE QDV1RF32 up-to-date Start to check current version on all components: odacli describe-component | grep -v ^$Ĭomponent Installed Version Available Version I would also recommend doing a backup of most important files: tnsnames.ora and listener.ora, database list, network configuration files, aso. You should use odabr to make snapshots of the important filesystems prior patching.
0 Comments
Leave a Reply. |