DBMaint process not running automatically but can be ran manually

book

Article ID: 185592

calendar_today

Updated On:

Products

CA Workload Automation AE - Scheduler (AutoSys) CA Workload Automation AE

Issue/Introduction

Although DBMaint.bat is scheduled to run daily, it's failing and not producing any output.

Please note the dbmaint.out file is not being created.

The only error we can find is in the event demon log file and it states that an error was encountered.

When we run DBMaint manually it works fine and completes successfully.

 

Cause

The encountered problem was related to spaces in the path to DBMaint causing to run into the following known problem for AE fixed in SP8

DBMAINT FAILS WHEN DBMAINTCMD VALUE INCLUDES AN ENVIRONMENT VARIABLE WITH SPACES

Problem Number: 4714

CA Workload Automation Scheduler fails to run the database maintenance activity on Windows machine when the product is installed on a drive that does not support 8dot3name file naming convention and the DBMaintCmd variable has an environment variable with spaces in the value of the environment variable.





Environment

Release : 11.3.6 SP7

Component : CA Workload Automation AE (AutoSys) 












Resolution

The recommended solution is to install the CUM1 patch on the top of the 11.3.6 SP7 Release:

SO05574: WIN-CA WORKLOAD AUTOMATION AE 11.3.6 SP7 CUM1

You can find the “Workload Automation AE 11.3.6 Solutions & Patches” under:

https://techdocs.broadcom.com/us/product-content/recommended-reading/technical-document-index/ca-workload-automation-ae-autosys-edition-r1136-solutions-patches.html


Another possible solution is to upgrade from 11.3.6 SP7 to SP8 Release as it contains the fix as well.

The workaround solution is to update the config file under %AUTOUSER% directory to use the full path to DBMaint.bat and enclose it in quotes.