![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Predictive Self-Healing Sure Solution 2090643.1 : ODA (Oracle Database Appliance): Best Practice Checks Before an Infrastructure or Grid Home Update
Applies to:Oracle Database Appliance SoftwareOracle Database Appliance Information in this document applies to any platform. PurposeProvide the best practice steps/checks before an Oracle Database Appliance (ODA) infra/GI patching phase. ScopeBasic ODA (Oracle Database Appliance) knowledge is required. DetailsBest Practice steps before an infra/gi update - The steps1. Run oracheck to verify major not compliant setup oakcli orachk
2. Check for sufficient file system free space under /u01, /opt, / (root) and /tmp 3. Check for disk status, all them must be in "good" status oakcli show disk
oakcli show diskgroup data oakcli show diskgroup reco oakcli show diskgroup redo 4. Check what will be updated oakcli update -patch <new version> --verify
5. Check disk from ASM point of view, login as user grid on node0, you could issue the following command: export ORACLE_SID=+ASM1
asmcmd lsdsk -p The correct working disk status should be CACHED; MEMBER; ONLINE; NORMAL Check for negative Usable_file_MB, issuing the command: asmcmd lsdg
if Usable_file_MB is negative check for the reason before to proceed 6. Check that no ASM rebalance of disk are running grid> asmcmd lsdg (check if value for REBAL column is Y)
or executing the following query: SQL> select GROUP_NUMBER, OPERATION, STATE, ACTUAL, SOFAR, EST_MINUTES from gv$asm_operation;
7. Review MOS note 888888.1 for known issues and workarounds for the release you are upgrading to. References<NOTE:888888.1> - Oracle Database Appliance - 12.1.2 and 2.X Supported ODA Versions & Known IssuesAttachments This solution has no attachment |
||||||||||||
|