Table of Contents
- Title and Copyright Information
- My Oracle Support
- What's New in this Guide
- 1 Introduction
- 2 Upgrade Overview
-
3
Upgrade Planning
- 3.1 Upgrade Check
- 3.2 Data Required for Upgrade
- 3.3 MySql User Accounts Password
- 3.4 Upgrade Maintenance Windows
- 3.5 Site Upgrade Methodology
-
4
Prerequisite Procedures
-
4.1
Prerequisite Procedures Overview
- 4.1.1 Check Required Materials
- 4.1.2 DSR ISO Administration
- 4.1.3 Data Collection - Verification of Global and Site Configuration Data
- 4.1.4 Back Up TKLCConfigData Files
- 4.1.5 Full Backup of DB Run Environment at Each Server
- 4.1.6 Software Upgrade Execution Overview
- 4.1.7 Accepting the Upgrade
- 4.1.8 Checking the Network Adapter Settings
-
4.1
Prerequisite Procedures Overview
- 5 Upgrading NOAM
- 6 Site Upgrade Execution
-
7
Backout Procedure Overview
- 7.1 Recovery Procedures
- 7.2 Backout Health Check
- 7.3 Disable Global Provisioning
- 7.4 Perform Emergency Backout
- 7.5 Perform Normal Backout
-
7.6
Backout Single Server
- 7.6.1 Active NOAM VIP: Prepare the Server for Backout
- 7.6.2 Server CLI: SSH to Server
- 7.6.3 Server CLI: Execute the Backout
- 7.6.4 Server CLI: SSH to Server
- 7.6.5 Server CLI: Restore the Full DB Run Environment
- 7.6.6 Server CLI: Verify the Backout
- 7.6.7 Server CLI: Reboot the Server
- 7.6.8 Server CLI: Verify OAM services restart (NOAM/SOAM only)
- 7.6.9 Active NOAM VIP: Verify Server State is Correct after Backout
- 7.6.10 Active NOAM VIP: Change/Correct the Upgrade State on Backed out Server to Ready
- 7.6.11 Active NOAM VIP: Verify Application Version is Correct for the Backed Out Server
-
7.7
Backout Multiple Servers
- 7.7.1 Active NOAM VIP: Prepare the Server for Backout
- 7.7.2 Server CLI: Log in to the Server(s)
- 7.7.3 Server CLI: Execute the Backout
- 7.7.4 Server CLI: Restore the Full DB Run Environment
- 7.7.5 Server CLI: Verify the Backout
- 7.7.6 Server CLI: Reboot the Server
- 7.7.7 Server CLI: Verify OAM Services Restart (NOAM/SOAM Only)
- 7.7.8 Active NOAM VIP: Verify Server State is Correct after Backout
- 7.7.9 Active NOAM VIP: Change/Correct the Upgrade State on Backed Out Server to Ready
- 7.7.10 Active NOAM VIP: Remove Upgrade Ready Status
- 7.7.11 Active NOAM VIP: Correct Upgrade Status on the Backed Out Server
- 7.7.12 Active NOAM VIP: Verify Application Version is Correct for the Backed Out Server
- 7.8 Additional Backout Steps
- 7.9 Additional Post-Backout Steps
- 7.10 Post-Backout Health Check
- 7.11 IDIH Backout
- 8 Critical and Major Alarms Analysis
-
9
Workarounds
- 9.1 Workaround to Resolve DB Site Replication Alarms
- 9.2 Workaround to Resolve Device Deployment Failed Alarm
- 9.3 Workaround to Resolve syscheck Error for CPU Failure
- 9.4 Workaround to Resolve the Server HA Switchover Issue
- 9.5 Workaround for Errors During Dual Image Upgrade
- 9.6 Workaround to Resolve Failed Upgrade
- 9.7 Workaround To Resolve Alarms while upgrading from build 8.5 to 9.0.2.0.0_99.13.0
- A Alternate Server Upgrade Procedures
- B Network IDIH Compatibility Procedures
- C Recover from a Failed Upgrade
- D Identify the DC Server
- E Limitations of Automated Server Group and Automated Site Upgrade
- F Advanced Health Check Procedure
- G Create a Link for ComAgent
- H Change SOAM VM Profile for Increased MP Capacity on an OpenStack System
- I Change SOAM VM Profile for Increased MP Capacity on a VMware system
- J Reset the SOAP Password
- K Restore the Servers with Backout Errors
- L Dual Hop Upgrade from DSR-8.x to DSR-9.0.2 Using Ansible