Error in creating Task Persistence database schema: ORA-00955: name is already used by an existing object
search cancel

Error in creating Task Persistence database schema: ORA-00955: name is already used by an existing object

book

Article ID: 36988

calendar_today

Updated On: 01-10-2025

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Risk Analytics CA Secure Cloud SaaS - Arcot A-OK (WebFort) CLOUDMINDER ADVANCED AUTHENTICATION CA Secure Cloud SaaS - Advanced Authentication CA Secure Cloud SaaS - Identity Management CA Secure Cloud SaaS - Single Sign On

Issue/Introduction

Cannot start Identity Mnaner/Jboss Services.

From sthe erver.log file appears the following

INFO [ims.Main] (ServerService Thread Pool -- 115) * Startup Step 1 : Attempting to start ServiceLocator.

ERROR [ims.tmt.CreateDatabaseSchema] (ServerService Thread Pool -- 115)

Error in creating Task Persistence database schema.: java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object  

Cause

The problem was caused after deploying new JAR files. With DBA tools it was identified which tables were trying to be created at the startup stage.

The Tasks Persistence Database is created when you start the Identity Manager server (Jboss, for example).

The problem is due to one or more objects currently present in the database with the same name of a table or object that is being creating by the Task Persistence DB scripts.



Resolution

Identify which table or object is trying to be created but is failing. If the startup logs do not show the objects, contact your DBA for assistance in using DBA tools to identify which objects are failing to create at the Identity Manager startup.

Delete the problematic tables from the database. For example in one case, these tables needed to be deleted.

TMP_BULKLOADER12_5

ARCHIVE_TMP_BULKLOADER12_5

Restart the Identity Manager application server. The startup will initiate another task persistence DB creation.