9 Workarounds
9.1 Workaround to Resolve DB Site Replication Alarms
The following procedure resolves DB site replication alarms if encountered
during the upgrade. This procedure restarts the inetrep process on the server that has a
DB replication failure alarm. Database (DB) replication failure alarms may display
during an Auto Site Upgrade or during an event that resets multiple servers in parallel.
The DB on the child servers is not updated until resolved.
- Server CLI: Log in to the server.
- Server CLI: Check if the replication links are up.
- Server CLI: Resolve replication issue
9.2 Workaround to Resolve Device Deployment Failed Alarm
This procedure resolves the device deployment failed alarm i.e. 10054. If this
procedure fails, it is recommended to contact My Oracle Support (MOS) and ask for
assistance.
9.2.2 NOAMP VIP GUI: Identify Server(s) and Interface(s) with Alarm
Navigate to current alarm details and identify the server and interface where
the 10054 - Device Deployment Failed alarm is displayed.
- Navigate to Alarms & Events, then View Active.
- Look for the 10054 alarm and make a list of the server(s) and interface(s).
9.3 Workaround to Resolve syscheck Error for CPU Failure
This procedure details the workaround to resolve syscheck error for CPU
failure.
9.4 Workaround to Resolve the Server HA Switchover Issue
The following procedure resolves the HA switchover issue. It restarts the cmha
process on the server that has HA switchover issue.
- Server CLI: Log in to the server.
- Server CLI: Resolve HA switchover issue(s).
- Repeat this procedure on each affected server.
9.5 Workaround for Errors During Dual Image Upgrade
Fatal Errors
During any fatal errors the server will not be recoverable and must be rebuilt. Rebuild the server with the same DSR release of its mate server.
Failures
During typical failures the system can be recovered by running the following commands and then restart the server./var/TKLC/backout/diUpgrade --clearError
sudo /usr/TKLC/appworks/sbin/backout_restore
sudo init 6
Early Check Failure
In case the upgrade fails due to an early check, restart the server before retrying the upgrade.
9.6 Workaround to Resolve Failed Upgrade
Error: Upgrade failed from 9.x to 9.0.2 with error: "Server could not restart the application to complete the upgrade".
Following are the steps to resolve a failed upgrade:
Figure 9-1 Failed upgrade

- Set Max HA Role to Active for the failed server on HA screen.
- Restart the server on the server screen.
9.7 Workaround To Resolve Alarms while upgrading from build 8.5 to 9.0.2.0.0_99.13.0
Following are the alarms received while upgrading from the build 8.5 to 9.0.2.0.0_99.13.0:
- 14152 MAJOR Failed to transfer file from remote host, see trace log for details.
- 31214 MINOR Scheduled Process Fault.
Resolution
To resolve the alarm, run the following command
sudo irem RecentAlarmEv.0 where "eventNumber=14152"
.