6 Advanced Post Upgrade Configurations and Troubleshooting
If the upgrade process fails, you must close the Upgrade Assistant, correct the issue, and then restart the Upgrade Assistant.
If the upgrade process fails after the upgrade process has started, you must drop the cloned repository and start from a freshly cloned repository in addition to correcting the underlying issue. There is no way to restart the failed upgrade process.
See Troubleshooting Your Upgrade in Upgrading with the Upgrade Assistant.
Troubleshooting Upgrade Performance Errors
The number of sessions present in a repository affects upgrade performance. Oracle recommends that you archive and purge your session logs to improve upgrade performance. See Purging the Logs in Administering Oracle Data Integrator.
Troubleshooting DB2 Database Transaction Log Errors
When using a DB2 database, the database transaction log may become full during ODI upgrade.
db2 'update database config for database_alias using LOGFILSIZ 10000'
db2 'update database config for database_alias using LOGPRIMARY 50'
Changing Domain Mode Post Upgrade
After the upgrade, your domain retains its original pre-upgrade domain
security mode settings. If you want to change the domain mode, to enable enhanced security,
for example, you must explicitly change the settings using the WebLogic Remote Console or by
modifying the DomainMBean
.
If your domain is currently set to Production Mode, and you want to enable added security, then after the upgrade use the WebLogic Remote Console to change the domain mode and enable the Secured Production Mode. Change the Domain Mode in Oracle WebLogic Remote Console Online Help.
Caution:
Changes to the domain mode require a full domain restart - a rolling restart is not sufficient. You must stop all managed servers before you attempt to change the domain mode.
When upgrading a domain to 14c (14.1.2.0.0), if there is no explicit secure mode setting, then the Reconfiguration Wizard will explicitly set secure mode to disabled in the upgraded domain. This is to preserve the behavior that was present in the original domain. If there is an explicit secure mode setting, it will be preserved in the upgraded domain. For more information, see Understand How Domain Mode Affects the Default Security Configuration in Securing a Production Environment for Oracle WebLogic Server.
Note:
Secured Production Mode enforces more restrictive and stringent security settings to ensure less vulnerability to threats. To make sure that your domain is secure, after enabling Secured Production Mode, you will have to choose the security configuration options that are appropriate for the environment in which the domain runs, such as obtaining and storing certificates, protecting user accounts, and securing the network on which the domain runs. If these options are not properly configured, you will be blocked from using WebLogic Server.
After you have created your WebLogic domain, several key steps remain to ensure its integrity such as selecting appropriate security configurations. For more information, see Securing the Domain After You Have Created It in Administering Security for Oracle WebLogic Server.