The /var/opt/teradata filesystem is filling up with BARLog (dsmain) in Teradata
Problem:
The /var/opt/teradata filesystem is filling up with BARLog (dsmain) log files.
# df -kh /var/opt/teradata/
Filesystem Size Used Avail Use% Mounted on
/dev/hda7 276G 260G 2.4G 100% /var/opt/Teradata
# du -ch /var/opt/teradata/tdtemp/bar|grep total
233G total
# ls -lrth /var/opt/teradata/tdtemp/bar/
total 233G
-rw-rw-r--+ 1 teradata tdtrusted 201M Nov 9 10:28 BARLog_26623_34_4_4.txt-2018110910290975
-rw-rw-r--+ 1 teradata tdtrusted 202M Nov 9 10:28 BARLog_26623_34_3_3.txt-2018110910290975
-rw-rw-r--+ 1 teradata tdtrusted 200M Nov 9 10:28 BARLog_26623_34_2_2.txt-2018110910290975
-rw-rw-r--+ 1 teradata tdtrusted 202M Nov 9 10:28 BARLog_26623_34_1_1.txt-2018110910290975
-rw-rw-r--+ 1 teradata tdtrusted 52M Nov 9 10:33 BARLog_26623_34_4_4.txt-2018110911244923
-rw-rw-r--+ 1 teradata tdtrusted 52M Nov 9 10:33 BARLog_26623_34_3_3.txt-2018110911244923
-rw-rw-r--+ 1 teradata tdtrusted 52M Nov 9 10:33 BARLog_26623_34_2_2.txt-2018110911244923
-rw-rw-r--+ 1 teradata tdtrusted 52M Nov 9 10:33 BARLog_26623_34_1_1.txt-2018110911244923
-rw-rw-r--+ 1 teradata tdtrusted 56M Nov 9 10:33 BARLog_26623_34.txt-2018110911223957
-rw-rw-r--+ 1 teradata tdtrusted 89M Nov 9 11:32 BARLog_26623_34_4_4.txt-2018110911402270
-rw-rw-r--+ 1 teradata tdtrusted 89M Nov 9 11:32 BARLog_26623_34_3_3.txt-2018110911402269
-rw-rw-r--+ 1 teradata tdtrusted 89M Nov 9 11:32 BARLog_26623_34_2_2.txt-2018110911402269
-rw-rw-r--+ 1 teradata tdtrusted 89M Nov 9 11:32 BARLog_26623_34_1_1.txt-2018110911402269
-rw-rw-r--+ 1 teradata tdtrusted 93M Nov 9 11:32 BARLog_26623_34.txt-2018110911400293
-rw-rw-r--+ 1 teradata tdtrusted 447M Nov 9 12:41 BARLog_26623_34_4_4.txt-2018110912561095
-rw-rw-r--+ 1 teradata tdtrusted 447M Nov 9 12:41 BARLog_26623_34_3_3.txt-2018110912561095
…..
……
….
-rw-rw-r--+ 1 teradata tdtrusted 156M Apr 21 23:19 BARLog_26623_34_2_2.txt-2019042204214564
-rw-rw-r--+ 1 teradata tdtrusted 157M Apr 21 23:19 BARLog_26623_34_1_1.txt-2019042204214564
-rw-rw-r--+ 1 teradata tdtrusted 51M Apr 22 04:25 BARLog_26623_34.txt-2019042204271312
-rw-rw-r--+ 1 teradata tdtrusted 51M Apr 22 04:25 BARLog_26623_35_4_4.txt-2019042304242272
-rw-rw-r--+ 1 teradata tdtrusted 52M Apr 22 04:25 BARLog_26623_35_3_3.txt-2019042304242272
-rw-rw-r--+ 1 teradata tdtrusted 51M Apr 22 04:25 BARLog_26623_35_2_2.txt-2019042304242272
-rw-rw-r--+ 1 teradata tdtrusted 51M Apr 22 04:25 BARLog_26623_35_1_1.txt-2019042304242272
-rw-rw-r--+ 1 teradata tdtrusted 97M Apr 22 19:02 BARLog_26623_34_4_4.txt-2019042223001460
-rw-rw-r--+ 1 teradata tdtrusted 98M Apr 22 19:02 BARLog_26623_34_3_3.txt-2019042223001459
-rw-rw-r--+ 1 teradata tdtrusted 98M Apr 22 19:02 BARLog_26623_34_2_2.txt-2019042223001459
-rw-rw-r--+ 1 teradata tdtrusted 98M Apr 22 19:02 BARLog_26623_34_1_1.txt-2019042223001459
-rw-rw-r--+ 1 teradata tdtrusted 77M Apr 22 23:02 BARLog_26623_34_4_4.txt-2019042304231743
-rw-rw-r--+ 1 teradata tdtrusted 78M Apr 22 23:02 BARLog_26623_34_3_3.txt-2019042304231743
-rw-rw-r--+ 1 teradata tdtrusted 78M Apr 22 23:02 BARLog_26623_34_2_2.txt-2019042304231743
-rw-rw-r--+ 1 teradata tdtrusted 79M Apr 22 23:02 BARLog_26623_34_1_1.txt-2019042304231743
-rw-rw-r--+ 1 teradata tdtrusted 66M Apr 23 04:27 BARLog_26623_34.txt-2019042304284417
-rw-rw-r--+ 1 teradata tdtrusted 276M Apr 23 04:28 BARLog_26623_35_4_4.txt
-rw-rw-r--+ 1 teradata tdtrusted 277M Apr 23 04:28 BARLog_26623_35_3_3.txt
-rw-rw-r--+ 1 teradata tdtrusted 274M Apr 23 04:28 BARLog_26623_35_2_2.txt
-rw-rw-r--+ 1 teradata tdtrusted 276M Apr 23 04:28 BARLog_26623_35_1_1.txt
-rw-rw-r--+ 1 teradata tdtrusted 48M Apr 23 04:28 BARLog_26623_35.txt
-rw-rw-r--+ 1 teradata tdtrusted 43M Apr 23 04:41 BARLog_26623_34_4_4.txt
-rw-rw-r--+ 1 teradata tdtrusted 43M Apr 23 04:41 BARLog_26623_34_3_3.txt
-rw-rw-r--+ 1 teradata tdtrusted 43M Apr 23 04:41 BARLog_26623_34_2_2.txt
-rw-rw-r--+ 1 teradata tdtrusted 43M Apr 23 04:41 BARLog_26623_34_1_1.txt
-rw-rw-r--+ 1 teradata tdtrusted 102M Apr 23 04:41 BARLog_26623_34.txt
-rw-rw-r--+ 1 teradata tdtrusted 1.2M Apr 23 04:41 BARLog_26623_40.txt
Cause:
Teradata systems that utilize the DSA backup restore solution logs messages in files located under "/var/opt/teradata/tdtemp/bar". This logs can grow quite large if the backup job logging level is set to “DEBUG” or “INFO”
Solution:
The purging of older log files will be addressed by RFC DR 174343, but at this time when Teradata will be implemented auto purging is unknown.
1. Delete the old log file.
2. If Logging Level set to “DEBUG” or “INFO” then set it to “Warning” or “Error” because extensive logging information is typically useful for support personnel when needed. So unnecessary excessive logging can take storage.
Logging level:
Error: Default. Enables minimal logging. Provides only error messages.
Warning: Adds warning messages to error message logging.
Info: Adds informational messages to warning and error message logging.
Debug: Full logging. All messages, including debug, are sent to the job log.
Notice:
This setting can affect performance.