After Upgrading Siebel DB to IP 2017 or Higher When Delivering an Existing Workflow Which Has Multiple Workflow Versions, It Fails With Error SBL-DAT-00381 (Doc ID 2368349.1)

Last updated on MAY 12, 2020

Applies to:

Siebel Workflow Manager - Version 17.4 [IP2017] and later
Information in this document applies to any platform.

Symptoms

After upgrade of Siebel Database from pre IP17 to IP2017 or higher, when developers edit an existing workflow and try to deliver it to a workspace such as MAIN it fails with either(or both) of the errors below:

This is happening ONLY for Workflows Processes with multiple versions on target workspace.

If the workflow process has only a single version on the target workspace the deliver of the change to the Workflow Process works fine.

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

Cause

Solution

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

After Upgrading Siebel DB to IP 2017 or Higher When Delivering an Existing Workflow Which Has Multiple Workflow Versions, It Fails With Error SBL-DAT-00381 (Doc ID 2368349.1)

Applies to:

Symptoms

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!