Job log archiving

[Michael A. Lowry]

We need to store archive old job logs for quite a long time. We do not want to let the production UC4 data base grow too large though, so we need an external job log archiving solution. Is there an official solution for this? Has anyone come up with a homegrown solution?

[Daryl Brown]

You're referring to archiving the UC4 reports themselves, right?

Assuming the archive browser tool isn't sufficient, one possibility could be to just capture the pertinent stdout data within the job itself via a redirect (> / >>) or pipe ( | tee <logfile>), and then archive those logfiles however you need.

 

[Anon Anon]

The DB.Archiving tool should be pulling out the older reports and storing them in a compressed file. Which as Daryl mentioned can be viewed using the Archive Browser.

[Michael A. Lowry]

I will look into the archiving tool and the archive browser. Thanks.

[Michael A. Lowry]

I have read the documentation of UCYBDBAR. I see no straightforward way to accomplish automated archiving and pruning.

We want to set up a periodic job that exports old logs and removes them from the AE database automatically, according to the age of the log. E.g.,
“Export all logs older than 13 months, and remove the corresponding statistics and report entries from the AE database.”

The UC4.DB Archive program appears to offer some capabilities like this; but this is a GUI program that requires user interaction. We want to automate this process. Is there a way to do this?

Also, we want to load the data into an external output management system. The output of the archiving tools appears to be in a format that is conveniently readable only by the Archive Browser. The format of the indexes is documented, but not guidelines for OMS integration. Are we overlooking something?

[Pete Wirfs]

UCYBDBAR can be executed via scheduled job from the utilities folder.  We run it weekly.

I agree that the archive formats seem they would be difficult to work with.  We haven't needed to, so I don't have any practical experience with them.

[Keld Mollnitz]

Maybe this is what you are looking for?
http://community.automic.com/discussion/763/sample-database-maintenance-workflow-for-v9

[marco_lucarelli_automic]

 Hi,

We use this feature from the UCYBDBAR tool:Open Interface to Output Management Systems

You can integrate all job-reports and Extended reporttypes  automatically in a self-writtenprogram

 

[Alain Moisy]

Michael,

You can use the UCYBDBAR program to do this with some additional work of course !
1 - record the runid of the objects that you want to keep the report in a global variable or use an SQL job to retreive those runid as a list in a time interval (in an Event object i.e;)
2 - Run the UCYBDBAR program for each runid selected in the variable or from the list (PREP_PROCESS_VAR, PREP_PROCESS_REPORT, your choice) to extract the report from the DB and copy them into a text file.
3 - Archive the text files generated with an archiving tool of your choice to keep the report for a period of your choice.
4 - Cleanup old reports using the standard maintenance cycle from AE.

I have done it using a cyclic event, the only point is that this is generating a lot of additional reports but you can set the job that runs the UCYBDBAR program to NOT keep reports in the DB EXCEPT on error to be able to check problems or issues but not overload the DB with un-necessary information.

Hope this can help to find a solution.

[Michael A. Lowry]

Alain Moisy said:

Michael,

You can use the UCYBDBAR program to do this with some additional work of course !
1 - record the runid of the objects that you want to keep the report in a global variable or use an SQL job to retreive those runid as a list in a time interval (in an Event object i.e;)
2 - Run the UCYBDBAR program for each runid selected in the variable or from the list (PREP_PROCESS_VAR, PREP_PROCESS_REPORT, your choice) to extract the report from the DB and copy them into a text file.
3 - Archive the text files generated with an archiving tool of your choice to keep the report for a period of your choice.
4 - Cleanup old reports using the standard maintenance cycle from AE.

I have done it using a cyclic event, the only point is that this is generating a lot of additional reports but you can set the job that runs the UCYBDBAR program to NOT keep reports in the DB EXCEPT on error to be able to check problems or issues but not overload the DB with un-necessary information.

Hope this can help to find a solution.

I guess that’s the best option available at the present time. I was really hoping for a solution that was more tightly integrated with an external output management system.