UIM - Using NAS Network Transaction Logging and adogtw

book

Article ID: 224505

calendar_today

Updated On:

Products

DX Infrastructure Management

Issue/Introduction

We have configured the NAS probe to use the option "Configure Network Transaction Logging" to store on external DB.

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/nas-alarm-server/nas-im-configuration/the-nas-setup-tab.html#concept.dita_726a28e6a429cd74d83b1889e403fd9f00caace6_ConfigureNetworkTransactionLogging

 

We have a big UIM implementation and normally the nas transactionlog.db grows beyond 35GB and it consumes a lot of local disk.

The Idea is to send all the transaction logs to a DB server to save local disk space. Even with these changes I still see a transactionlod.db growing every single day using GB od data when my expectation is to have a 0GB transactionlog.db file size.

 

Is this expected? 

Cause

This is working as designed

Environment

Release : 20.3

Component : UIM NAS

Resolution

Looking at the documentation, about this option, it states:  

"Selecting Activate Network transaction logging allows you to store transaction log records in a commercial database other than the NiS"

But it doesn't say that this option can be used to completely free the space used by the local sqllite files.

The transactionlog.db is still used by NAS to replicate to the DB so alarm history is visible in the OC and on the local file itself to show the alarms in IM. 

So if that file would go down to 0, you would not see any historic alarm. 

This option is only as an additional copy if you need those stored in "in a commercial database other than the NiS"