Failed Installation generates MDBTools install error=1
search cancel

Failed Installation generates MDBTools install error=1

book

Article ID: 376090

calendar_today

Updated On:

Products

CA Service Desk Manager CA Service Management - Service Desk Manager

Issue/Introduction

Product install or RU update installation fails.

The following messages are seen in the logs

install.log

DEBUG [DeployThread: Configuring CA Service Management Common Tables] [InstallCDB] 08-12,16:44:37 MDBTools install error=1
DEBUG [DeployThread: Configuring CA Service Management Common Tables] [InstallCDB] 08-12,16:44:37 Setupmdb exit /B return code=1
DEBUG  [DeployThread: Configuring CA Service Management Common Tables] [ActiveProcessHolder] Exit Monitor. Process ID (PID): 4548
DEBUG [DeployThread: Configuración de las tablas comunes de CA Service Management] [InstallCDB] Command terminated with error
DEBUG [DeployThread: Configuración de las tablas comunes de CA Service Management] [InstallCDB] Command terminated with exit code: 1
DEBUG [DeployThread: Configuración de las tablas comunes de CA Service Management] [InstallCDB] Exit code of CDB script : 1

install_<mdb>.log

INFO - MDBTools_0116I - Reconciling the database with the MDB schema information
INFO - MDBTools_0319I - Reconciliation detected that trigger 't_usp_record_lock.xml' is missing from the database
INFO - MDBTools_0104I - Total time: 0H:0M:6S.
MDBTools install error=1 
Setupmdb exit /B return code=1 

Environment

CA Service Management 17.4 GA and later

Oracle 19c MDB database

Cause

SQL operations are failing during installation

Resolution

SQL Errors may be logged during the MDB install phase at the DEBUG level which is not enabled by default

Require to enable DEBUG logging for the MDBTools installation to gather additional information

Retrieve the logs from %TEMP%\casm\mdb\install_<MDB>.log and provide for analysis

Additional Information

The most likely resolution will be having to increase the size of the column TABLE_NAME in TEMP_MDBTOOLS_PERMISSIONS table.

If modifying the database is necessary, please ensure you have taken the necessary backups and involve the DBA.