DB LOAD fails with: 'Invalid object name.'

Document ID : KB000115674
Last Modified Date : 05/10/2018
Show Technical Document Details
Issue:
When upgrading a database (for example, from v10 to V12) or running DB Load, the following or similar error is experienced:

U00029108 UCUDB: SQL_ERROR Database handles DB-HENV: f8ee10 DB-HDBC: 156088f0 
U00003591 UCUDB - DB error info: OPC: 'SQLNumResultCols' Return code: 'ERROR' 
U00003592 UCUDB - Status: '42S02' Native error: '208' Msg: 'Invalid object name 'PMIA'.' 
U00003592 UCUDB - Status: '42000' Native error: '8180' Msg: 'Statement(s) could not be prepared.' 
U00029160 UCUDB: previous error message can be ignored. 

U00029108 UCUDB: SQL_ERROR Database handles DB-HENV: f8ee10 DB-HDBC: 156088f0 
U00003591 UCUDB - DB error info: OPC: 'SQLNumResultCols' Return code: 'ERROR' 
U00003592 UCUDB - Status: '42S02' Native error: '208' Msg: 'Invalid object name 'PMIAM'.' 
U00003592 UCUDB - Status: '42000' Native error: '8180' Msg: 'Statement(s) could not be prepared.' 
U00029160 UCUDB: previous error message can be ignored. 

Other potentially affected objects may be (not a comprehensive list):

U00003592 UCUDB - Status: '42S02' Native error: '208' Msg: 'Invalid object name 'PMID'.' 

U00003592 UCUDB - Status: '42S02' Native error: '208' Msg: 'Invalid object name 'PMMA'.' 

U00003592 UCUDB - Status: '42S02' Native error: '208' Msg: 'Invalid object name 'PMMAV'.' 

U00003592 UCUDB - Status: '42S02' Native error: '208' Msg: 'Invalid object name 'PMMD'.'
Environment:
Database: MSSQL
Cause:
Missing Database User permissions.
Resolution:
Referencing our Documentation:

https://docs.automic.com/documentation/webhelp/english/AWA/12.0/DOCU/12.0/AWA%20Guides/help.htm#AE_AWA_Source/Installation/ucaakf.htm%3FTocPath%3DInstallation%2520Guide%7CInstalling%2520the%2520Automation%2520Engine%7CNew%2520Installation%7CInstallation%2520Procedure%7CSetting%2520up%2520the%2520Database%7CMS%2520SQL%2520Server%7C_____0

The following rights must be assigned:

Section 3. Creating a Database User
  • Highlight the AE database in the Database access tab and select db_backupoperator, db_datareader, db_datawriter, db_ddladmin, db_owner and public in the database roles.
Once these permissions are in place, this error should no longer present during a correctly performed upgrade/Database Load.