DBSPACE_ALARM_SPACE when running dbspace from the WCC ECL
search cancel

DBSPACE_ALARM_SPACE when running dbspace from the WCC ECL

book

Article ID: 100150

calendar_today

Updated On:

Products

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

Issue/Introduction

After running dbspace and dbstatistics from WCC Enterprise Command Line, we are getting below details . 
Even if we change the value to 4000 from 2000 in DBSPACE_ALARM_SPACE in Autosys Admin Graphical Interface

dbstatistics
CAUAJM_I_60019 dbstatistics: Running dbstatistics at: Tue May 29 09:31:53 2018

CAUAJM_I_60020 dbspace:  Running dbspace at : Tue May 29 09:31:55 2018

CAUAJM_I_60031 The AutoSys tables have used 3354.6 MB disk space.
CAUAJM_I_50179  *** ALARM Sent! ***

D:\CA\WAAEr1136>dbspace
CAUAJM_I_60020 dbspace:  Running dbspace at : Tue May 29 09:42:31 2018

CAUAJM_I_60031 The AutoSys tables have used 3355.1 MB disk space.
CAUAJM_I_50179  *** ALARM Sent! ***

Environment

WCC 11.4 SP6 on Windows
Autosys 11.3.6 SP7 On Windows in HADS mode

Cause

Default value for variable DBSPACE_ALARM_SPACE is 2000 (2GB)

Client needs to set DBMaint with 365 days for database retention days , therefore the database size will be growing a lot

 

Resolution

The dbstatistics and dbspace commands ( which are also part of the DBMaint script) launched from the WCC Enterprise Command Line are executed via the Autosys Command Sponsor.

Added variable DBSPACE_ALARM_SPACE=4000 to below file on the Autosys Server

C:\Program Files (x86)\CA\SC\iTechnology\AutoSysCommandWrapper.<Instance>

No need to restart igateway
 

Additional Information

This variable can also be set as a system variable in Windows.

If HADS mode, the variable has to be set the same way on the Shadow machine