[AWA] Unable to start server process due to database filegroup full
search cancel

[AWA] Unable to start server process due to database filegroup full

book

Article ID: 112167

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Unable to log in Automic Workload Automation, CPs & WPs are stopped.
Unable to start Server processes (CP & WP), error message found in log:
U00003532 UCUDB: Checking data source ...
U00029108 UCUDB: SQL_ERROR    Database handles  DB-HENV: 1307110  DB-HDBC: 13071f0
U00003591 UCUDB - DB error info: OPC: 'SQLExecDirect' Return code: 'ERROR'
U00003592 UCUDB - Status: '42000' Native error: '1101' Msg: 'Could not allocate a new page for database 'Automic' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.'
U00003590 UCUDB - DB error: 'SQLExecDirect', 'ERROR   ', '42000', 'Could not allocate a new page for database 'Automic' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.'
U00003531 UCUDB: Error while checking data source (e.g. code conversion or driver problem, see log file).
U00003590 UCUDB - DB error: 'SQLExecDirect', 'ERROR   ', '42000', 'Could not allocate a new page for database 'Automic' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or settiùÂY])'
U00003410 Server 'AE_TST#CP001' version '11.2.2+hf.3.build.673' ended abnormally.

 

Environment

Windows Server 2012
MS SQL Database
Automic Workload Automation v11.2.2+hf3.build.673

Cause

The issue was caused by space allocated to 'Automic' database is full or the disk space is insufficient.

Resolution

Please kindly check your disk space or have your DBA revise the space allocated for 'Automic' database.
As soon as the space is made available, the engine should be able to start and you can login.