My Oracle Support Banner

Siebel Upgrade (IRM) Fails In Upgrep Step With Error ORA-01554 and ORA-12801 (Doc ID 2224008.1)

Last updated on APRIL 07, 2023

Applies to:

Siebel Financial Services CRM - Version 17.0 [IP2017] and later
Information in this document applies to any platform.

Symptoms

Upgrep fails when running Incremental Repository merge (IRM) from Siebel 8.1.1.10 to 16.7 (the same applies when upgrading to IP17 or above)  in the step Prepare for index creation

ERROR in upgwiz.log

create unique index S_ACCELERATOR_U1 on S_ACCELERATOR
("COMMAND_ID", "NAME", "WS_ID", "WS_OBJ_VER") parallel nologging
tablespace SIEBELINDEX
2017-01-05 01:23:01 [tp][ODBC Oracle driver][Oracle]ORA-12801: error signaled in parallel query server P057
ORA-01554: transaction concurrency limit reached reason:no undo segment found with available slot params:0, 0
2017-01-05 01:23:01
2017-01-05 01:23:01 S1000: [tp][ODBC Oracle driver][Oracle]ORA-12801: error signaled in parallel query server P057
2017-01-05 01:23:01 ORA-01554: transaction concurrency limit reached reason:no undo segment found with available slot params:0, 0
2017-01-05 01:23:01
2017-01-05 01:23:01 Dropping index with the same column signature and retrying...
2017-01-05 01:23:01 create unique index S_ACCELERATOR_U1 on S_ACCELERATOR
2017-01-05 01:23:01 ("COMMAND_ID", "NAME", "WS_ID", "WS_OBJ_VER") parallel nologging
2017-01-05 01:23:01 tablespace SIEBELINDEX


The issue can be reproduced at will with the following steps:
1. Set the undo_management to manual as per the Siebel upgrade guide.
2. Run Upgrep by invoking the Database configuration wizard

Changes

 N/A

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.