Also be aware that we recently discovered that MAX_REPORT_SIZE silently governs other things as well. One of them is the maximum input file size accepted for the XML script functions. This is "by design", so be extra watchful when changing MAX_REPORT_SIZE. One can notice failures to process XML files fully due to this setting usually by characteristic messages like: "
Not all blocks (Limit '120') of file '...' have been transferred".And I fully second what Pete said about not being a report repository. The reports are stored line by line, and can accumulate quickly for jobs running several times a day and/or when a program invoked via Automic is noisy. I suggest limiting the stdout of your programs as much as possible.
The report files are usually called ".TXT" and you can also put those somewhere else, it's configurable in the .ini flle. There's also .sts files, which are status files for file transfers. There was a bug where the agent would leave those files behind. I think that'll be fixed in 12.3, but I can't tell for sure because the ticket system does not show me those details at present time.
Original Message:
Sent: 07-03-2019 12:17 PM
From: Pete Wirfs
Subject: Agent XXXXXXXX.TXT files
The restriction is a configurable setting, so each datacenter can be different. You want to look up MAX_REPORT_SIZE inside of UC_HOSTCHAR_DEFAULT under client 0. Suggest you look it up in the online help as well.
This setting is an integer value representing the number of "blocks" that will be allowed. You then set the REPORT_BLKSIZE variable to control how many bytes can be stored in each block.
This product is not meant to be used as a report repository. Doing so could hurt its performance in its more important duties. So being as restrictive as your business will allow is preferable.
Original Message:
Sent: 07-03-2019 11:55 AM
From: Lester Chew
Subject: Agent XXXXXXXX.TXT files
Thanks for the reply. Do you have any idea what that size limitation is?
Original Message:
Sent: 07-02-2019 04:05 PM
From: Pete Wirfs
Subject: Agent XXXXXXXX.TXT files
There is a restriction on how large of a report can be accepted into the database. When the report exceeds that limit, it is left in the temp directory. So it depends upon the size of the particular run. The other servers might only be generating small reports that don't exceed this restriction?
Original Message:
Sent: 07-02-2019 03:00 PM
From: Lester Chew
Subject: Agent XXXXXXXX.TXT files
On this windows server, I am running 12.2.0 Windows agent. in the temp directory, there are a number of the 8.3 type files that are what I believe are jobs executions detail information. On other servers, I don't see these files hanging around on other Windows servers. So where are these files still on this one server?
I would also add that the job has the store to database option checked on this Windows server. Most jobs to have this optioned checked, so I can't believe that this is the reason why the 8dot3 files are still on the agent server.