Loading initialdata error "Cannot use DROP SYNONYM with 'MQSRV'

book

Article ID: 192488

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation CA Automic Operations Manager CA Automic Oracle

Issue/Introduction

After loading the initial data with the help of the dbload utility (ucybdbld), the following error occurs.

20200603/130330.955 - U00038091 Change application directory to '..\db\'.
20200603/130330.971 - U00038081 Version of database objects: '12.1.1+hf.1.build.1364'
20200603/130330.971 - U00038036 Version check result:  
Version and status of database: '12.1'/'READY'.  
Version and content of data file: '12.3'/'UPGRADE'.  
Version of database objects: '12.1.1+hf.1.build.1364' 
Loading in mode 'UPGRADE'.
20200603/130336.191 - U00038285 Orphaned record found in table 'EV' with RunId:'1213055'. Record will be deleted.
20200603/130336.191 - U00038285 Orphaned record found in table 'EV' with RunId:'1226008'. Record will be deleted.
20200603/130336.191 - U00038285 Orphaned record found in table 'EV' with RunId:'1227007'. Record will be deleted.
20200603/130336.191 - U00038285 Orphaned record found in table 'EV' with RunId:'1228017'. Record will be deleted.
20200603/130336.191 - U00038285 Orphaned record found in table 'EV' with RunId:'1242016'. Record will be deleted.
20200603/130336.973 - U00029108 UCUDB: SQL_ERROR    Database handles  DB-HENV: 149a300  DB-HDBC: 149eab0
20200603/130336.973 - U00003591 UCUDB - DB error info: OPC: 'SQLExecDirect' Return code: 'ERROR'
20200603/130336.973 - U00003592 UCUDB - Status: '42000' Native error: '3705' Msg: 'Cannot use DROP SYNONYM with 'MQSRV' because 'MQSRV' is a table. Use DROP TABLE.'
20200603/130336.973 - U00003594 UCUDB Ret: '3590' opcode: 'EXEC' SQL Stmnt: 'DROP SYNONYM MQSRV'
20200603/130336.973 - U00003590 UCUDB - DB error: 'SQLExecDirect', 'ERROR   ', '42000', 'Cannot use DROP SYNONYM with 'MQSRV' because 'MQSRV' is a table. Use DROP TABLE.'
20200603/130336.973 - U00038068 ABORTING due to error. 

The loading process was terminated abnormally. The Database might be in an inconsistent condition. Please contact Automic Support.
20200603/161120.754 - U00003523 UCUDB: Maximum time required for a DB call: '3:838.788.351'.
20200603/161120.754 - U00003522 UCUDB: Database closed. Total time for DB calls: '4:640.143.681' seconds.
20200603/161120.754 - U00003549 UCUDB: '            2028' 'OTHERS    ' calls took '3:842.042.058' sec.
20200603/161120.754 - U00003549 UCUDB: '              10' 'SELECT    ' calls took '0:127.024.832' sec.
20200603/161120.754 - U00003549 UCUDB: '              34' 'EXECUTE   ' calls took '0:655.058.147' sec.
20200603/161120.754 - U00003549 UCUDB: '               0' 'UPDATE    ' calls took '0:000.000.000' sec.
20200603/161120.754 - U00003549 UCUDB: '               0' 'DELETE    ' calls took '0:000.000.000' sec.
20200603/161120.754 - U00003549 UCUDB: '               0' 'INSERT    ' calls took '0:000.000.000' sec.
20200603/161120.754 - U00003549 UCUDB: '              77' 'READ      ' calls took '0:008.158.742' sec.
20200603/161120.754 - U00003549 UCUDB: '            3058' 'CLOSESTMT ' calls took '0:002.885.779' sec.
20200603/161120.754 - U00003549 UCUDB: '            1015' 'TRANSACT  ' calls took '0:004.974.120' sec.

Cause

Caused by SQLDRIVERCONNECT being set in the MQDB section when Alternative Schema is not being used

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

If you had only one DB (not using Alternative Schema), then please uncomment the last line "SQLDRIVERCONNECT" in the DB UNLOAD Utility and try again. (It will be under the [MQDB] section).