My Oracle Support Banner

ORABPEL Database Schema Version Mismatch After from 10.1.2 Patchset Upgrade (Doc ID 339182.1)

Last updated on OCTOBER 26, 2018

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.2.0.0 and later   [Release: AS10gR2 and later ]
Information in this document applies to any platform.
Checked for relevance on 29-Apr-2010

Symptoms

After upgrading BPEL via the BPEL patchset #2 in unpublished 4496111 you find that BPEL fails to start and is reporting a database schema version mistmatch.

A sample error in $ORACLE_HOME/integration/orabpel/domains/default/logs/domain.log or $ORACLE_HOME/logs/OC4J_BPEL*.log:

INFO> <collaxa> <ServerManager::__init> Detected datasource 'oracle'
05/10/24 16:52:27 ORABPEL-03003

Incorrect db schema version.
The database schema version "2.0.2" from the database does not match the version "2.0.3"
expected by the server.
The database schema currently in place has probably been configured for a previous release;
please re-install the database schema and try to start the server again.

Changes

This occurs when patchset #1 to  is upgraded to patchset #2<

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
  References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.