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

Managing the Topology 12-27 Solution: Incomplete policy migration results from an unsuccessful start of the first SOA server in a cluster. To enable full migration, edit the jazn-policy element the system-jazn-data.xml file to grant permission to bpm-services.jar: grant grantee codesource urlfile:{oracle.home}soamodulesoracle.soa.workflow_11.1.1bpm-services.jar url codesource grantee permissions permission classjava.security.AllPermissionclass permission permissions grant 12.8.4 SOA, IPM, or UCM Servers Fail to Start Due to Maximum Number of Processes Available in Database Problem: A SOA, IPM, or UCM server fails to start. The domain has been extended for new types of managed server for example, UCM extended for IPM or the system has been scaled up added new servers of the same type. The SOA, IPM, or UCM server output log reports the following: Warning JDBC BEA-001129 Received exception while creating connection for pool SOADataSource-rac0: Listener refused the connection with the following error: ORA-12516, TNS:listener could not find available handler with matching protocol stack Solution: Verify the number of processes in the database and adjust accordingly. As the SYS user, issue the SHOW PARAMETER command: SQL SHOW PARAMETER processes Set the initialization parameter using the following command: SQL ALTER SYSTEM SET processes=300 SCOPE=SPFILE Restart the database.

12.8.5 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_BASEadminedg_domainaserveredg_ domainserversAdminServerdataldapldapfiles. Waiting for 10 seconds and then retrying in case existing WebLogic Server is still shutting down. Note: The method that you use to change a parameters value depends on whether the parameter is static or dynamic, and on whether your database uses a parameter file or a server parameter file. See the Oracle Database Administrators Guide for details on parameter files, server parameter files, and how to change parameter values. 12-28 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite 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_nameserversAdminServerdataldap ldapfilesEmbeddedLDAP.lok.

12.8.6 Error While Activating Changes in Administration Console

Problem: Activation of changes in Administration Console fails after changes to a servers 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 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, provide usernamepassword information in the server start configuration in the Administration Console for the specific server whose configuration was being changed.

12.8.7 SOA or IPM Server Not Failed Over After Server Migration