Administration Server Fails to Start After a Manual Failover Error While Activating Changes in Administration Console

11-18 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter For more information on backup and recovery of Oracle Fusion Middleware components, see Oracle Fusion Middleware Administrators Guide.

11.6 Troubleshooting

This section covers the following topics: ■ Section 11.6.1, Administration Server Fails to Start After a Manual Failover ■ Section 11.6.2, Error While Activating Changes in Administration Console ■ Section 11.6.3, OAM Configuration Tool Does Not Remove URLs ■ Section 11.6.4, Portlet Unavailable After Database Failover ■ Section 11.6.5, Redirecting of Users to Login Screen After Activating Changes in Administration Console ■ Section 11.6.6, Redirecting of Users to Administration Consoles Home Page After Activating Changes to OAM ■ Section 11.6.7, Configured JOC Port Already in Use ■ Section 11.6.8, Restoring a JMS Configuration ■ Section 11.6.9, Spaces Server Does Not Start after Propagation of Domain

11.6.1 Administration Server Fails to Start After a Manual Failover

Problem: Administration Server fails to start after the Administration Server node failed and manual failover to another nodes is performed. The Administration Server output log reports the following: Feb 19, 2009 3:43:05 AM PST Warning EmbeddedLDAP BEA-171520 Could not obtain an exclusive lock for directory: ORACLE_BASEadminsoadomainaserver soadomainserversAdminServerdataldapldapfiles. Waiting for 10 seconds and then retrying in case existing WebLogic Server is still shutting down. Solution: When restoring a node after a node crash and using shared storage for the domain directory, you may see this error in the log for the Administration Server due to unsuccessful lock cleanup. To resolve this error, remove the file ORACLE_BASE admindomain_nameaserverdomain_nameserversAdminServerdataldapldapfiles EmbeddedLDAP.lok.

11.6.2 Error While Activating Changes in Administration Console

Problem: Activation of changes in Administration Console fails after changes to a server’s start configuration have been performed. The Administration Console reports the following when clicking Activate Changes: An error occurred during activation of changes, please see the log for details. [Management:141190]The commit phase of the configuration update failed with an Note: ORACLE_HOME should be backed up if any changes are made to the XEngine configuration that are part of your B2B setup. These files are located under ORACLE_HOMEsoathirdparty edifecsXEngine. To back up ORACLE_HOME, execute the following command: SOAHOST1 tar -cvpf fmwhomeback.tar MW_HOME Managing the Topology 11-19 exception: In production mode, its not allowed to set a clear text value to the property: PasswordEncrypted of ServerStartMBean Solution: This may happen when start parameters are changed for a server in the Administration Console. In this case, either provide usernamepassword information in the server start configuration in the Administration Console for the specific server whose configuration was being changed, or remove the password-encryptedpassword-encrypted entry in the config.xml file this requires a restart of the Administration Server.

11.6.3 OAM Configuration Tool Does Not Remove URLs