Operation Error #21. Deployed IG but WPDS database is not created
search cancel

Operation Error #21. Deployed IG but WPDS database is not created

book

Article ID: 271907

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

IG deployment in Vaap ends but do not create the DB's as WPDS

Popup Error:

! Deployment Failed

The following errors were encountered during the deployment process:

[INFO] Removing existing cipher config and protocol config from vapp-default
[INFO] Inserting new cipher config and TLSv1.2 protocol config into vapp-default
[ERROR] 21 Failed to populate the database for Identity Governance (error code: 21)
[INFO] Populating IG database structure on the external database
[ERROR] Operation failed error #21

 

 

Environment

Release : 14.4

Cause

Initially deployed with the vApp with external oracle database and later switched to the external sql server database. There were remnants of Oracle configuration that caused this issue.

 

Resolution

Jbosscli.sh commands used in vApp that add SQLserver driver. This resolved the issue:

/subsystem=datasources/jdbc-driver=sqlserver:add(driver-name=sqlserver, driver-module-name="com.microsoft.sqlserver",driver-class-name=com.microsoft.sqlserver.jdbc.SQLServerDriver,driver-xa-datasource-class-name=com.microsoft.sqlserver.jdbc.SQLServerXADataSource)

Adjusted the attribute check-valid-connection-sql that was with the oracle string "select 1 from dual" and changed to sql string "select 1"

/subsystem=datasources/data-source=WPDS/:write-attribute(name=check-valid-connection-sql,value=SELECT 1)

Start IG and WPDS tables will be created.