ORABPEL-9732 'Persistency service internal error: Installation failed' during startup

Problem

During the startup of the SOA managed servers, you see the following ORABPEL-9732 error and multiple "Installation failed" errors:

<Apr 1, 2018 3:30:00 PM GMT> <Notice> <Stdout> <BEA-000000> <<Apr 1, 2018 3:30:00 PM GMT> <Error> <oracle.soa.services.workflow.common> <BEA-000000> <<.> Persistency service internal error: Persistency service internal error: Installation failed.
Persistency service experienced unexpected internal error.
Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Persistency service experienced unexpected internal error.
Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
      
ORABPEL-9732

Solution

1. Restore the database.

There is a problem with the database. It could be empty tables, missing sequences, or invalid objects. Don't waste your time troubleshooting and restore the database from a working copy.

Applicable Versions

• Oracle SOA Suite 11g (11.1.1.9.0)

 

Getting "Invalid server bam_server1 SSL configuration" when starting up BAM 11.1.1.9 on SSL

Problem

All of a sudden, when we shut down and restart "bam_server1", the SSL port no longer works. This is the error that shows up when we start it up:

<Aug 9, 2018 4:49:06 AM GMT> <Critical> <Security> <BEA-090174> <The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.>  

<Aug 9, 2018 4:49:06 AM GMT> <Alert> <Security> <BEA-090717> <Invalid server bam_server1 SSL configuration>  

<Aug 9, 2018 4:49:06 AM GMT> <Error> <WebLogicServer> <BEA-000297> <Inconsistent security configuration, weblogic.management.configuration.ConfigurationException: Invalid server bam_server1 SSL configuration>  

<Aug 9, 2018 4:49:06 AM GMT> <Emergency> <Security> <BEA-090034> <Not listening for SSL, java.io.IOException: Invalid server bam_server1 SSL configuration.>

Solution

1. Check bam_server1.out and note the JVM start parameters. You will notice that they conflict with what you intend.

2. Someone may have made custom SSL settings in this files that conflicted with the configuration we made on the WebLogic Console, so check these files too:

• setDomainEnv.sh
• startManagedServer.sh

Applicable Versions

• Oracle SOA Suite 11g (11.1.1.9.0)