Actian DataConnect Best Practices: Clean up obsolete artifacts before you bring your server down!
by David Byrd
Recently I had a server almost crash. I quickly realized the disk space was extremely low. I looked at the data directories, but the core data is stored on a data drive and not the system drive. Please review the two best practices for data integrators below to see what you can do to prevent a system crash from no disk space left.
Best Practice # 1
Actian Integration processes can be deeply enriched by using the Logmessage function to record information about how you process is running. This can be critical to have posted pertinent information just before a process crashes, potentially ruining a good customer experience..
That is the good side of having robust logging. Unfortunately, the down side of robust logging is a large log file. Actian’s integration manager does a good job of trying to manage small logs, however, when a log is generated that reaches too large a threshold, it will save it in the server local directory.
The problem: There is no Cleanup of these logs.
The solution: Build a Bat file that delete all files in all sub directories like the following:
Note you will need to confirm the actual paths based on your installation.
Result: Clearing these directories of old logs gave us back 45 GB.
Best Practice # 2
Actian Integration processes can be directly in the designer. Everytime it runs this with a new configuration ( i.e. you made a change to the process ) the designer actually builds a DJAR file behind the scenes. This is the same directory where the deployment djars are built too… so be careful. All the djars built from the design have the word SNAPSHOT in it. See picture below:
The problem: There is no Cleanup of these djars.
The solution: clear the SNAPSHOT Djars:
Note you will need to confirm the actual paths based on your installation.
Result: Clearing these directories of old djars gave us back 4 GB.
No comments:
Post a Comment