My Oracle Support Banner

BPM Application Deployed in WLS Does Not Start After Cloning BPM Schemas and WLS environment (Doc ID 1313268.1)

Last updated on AUGUST 06, 2018

Applies to:

Oracle Business Process Management Suite - Version 10.3.1 and later
Information in this document applies to any platform.
***Checked for relevance on 25-Sep-2012***

Symptoms

*** Scenario Description

You want to test a HotFix in a parallel TEST environment before applying the HotFix into PROD environment.

You have cloned existing BPM PROD schemas (Directory Service and Engine) into a parallel DB instance, making sure that the schema names are exactly the same as in PROD, following Doc ID 1228639.1, changed your BPM configuration files to point to the parallel DB instance and environment before starting the Directory Service and the Engine (for example, host_name and SID in directory.xml and related Engine properties within Process Administrator).

You have re-created and re-deployed BPM applications into WLS environment.

After the applications have been deployed, some applications like PAPI-WS won't start.

The following error message could be seen in Logs:

<Apr 7, 2011 4:48:27 PM EDT> <Warning> <HTTP> <BEA-101162> <User defined listener fuego.papi.webservice.listener.PapiWsContextListener failed: java.lang.RuntimeException: Fatal error initializing PAPI Web Services.
java.lang.RuntimeException: Fatal error initializing PAPI Web Services
at fuego.papi.webservice.listener.PapiWsContextListener.contextInitialized(PapiWsContextListener.java:81)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
Truncated. see log file for complete stacktrace
fuego.directory.DirectoryRuntimeException: Exception [fuego.directory.exception.InvalidSchemaException: Directory [default] has not been correctly initialized.
Detail:Even though a Directory Service is currently present at the specified location, the expected Oracle entries could not be found. Either the schema has not been created or the existing directory corresponds to a different Oracle version.

].
at fuego.directory.DirectoryRuntimeException.wrapException(DirectoryRuntimeException.java:85)
at fuego.directory.provider.DirectorySessionImpl.getDirectoryPreferences(DirectorySessionImpl.java:623)
at fuego.directory.hybrid.ldap.LDAPDirectoryPreferences.createFromSession(LDAPDirectoryPreferences.java:35)
at fuego.directory.hybrid.generic.GenericLDAPRepository.createRepository(GenericLDAPRepository.java:58)
at fuego.directory.hybrid.generic.GenericLDAPFactory.createRepository(GenericLDAPFactory.java:36)
Truncated. see log file for complete stacktrace
fuego.directory.exception.InvalidSchemaException: Directory [default] has not been correctly initialized.
Detail:Even though a Directory Service is currently present at the specified location, the expected Oracle entries could not be found. Either the schema has not been created or the existing directory corresponds to a different Oracle version.

at fuego.directory.provider.jdbc.oracle.OraclePersistenceManager.mapSQLException(OraclePersistenceManager.java:164)
at fuego.directory.provider.jdbc.datadirect.oracle.DataDirectOraclePersistenceManager.mapSQLException(DataDirectOraclePersistenceManager.java:50)
at fuego.directory.provider.jdbc.JDBCServiceAccessor.mapSQLException(JDBCServiceAccessor.java:78)
at fuego.directory.provider.jdbc.JDBCObjectPropertiesAccessor.fetchAllDirectoryProperties(JDBCObjectPropertiesAccessor.java:442)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-00942: table or view does not exist

at weblogic.jdbc.base.BaseExceptions.createException(Unknown Source)
at weblogic.jdbc.base.BaseExceptions.getException(Unknown Source)
at weblogic.jdbc.oracle.OracleImplStatement.execute(Unknown Source)
at weblogic.jdbc.base.BaseStatement.commonExecute(Unknown Source)
at weblogic.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)
Truncated. see log file for complete stacktrace

Changes

Cloned BPM schemas and WLS environment from one host to another host

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.