Agile PLM Maintenance: The Top 10 Ways to Optimize Oracle Agile

Security experts all agree that the number one task you can perform to protect your system is to apply regular patches and updates. Of course, you will want to test any system-level upgrades before applying them to a production environment.

It is important to establish a regular process for testing OS-level updates and moving them to production in a timely manner. Timing is important because once a security patch is released a subsequent exploit is created and unleashed.

7. Perform Regular File Exports/Backups

Perform regular exports of your data to your development environment and always make regular backups of your database.

Using export will not take the place of a well-considered backup system it does have its advantages. You should note that Agile creates the necessary scripts as part of the database creation process making it very simple to use.

In Windows, the scripts are agile9exp.bat (uses old-school database dump) and agile9exp.bat which uses the more efficient DataPump utilities. Either will work, but after Agile 9.3.2 it is recommended that DataPump be used.  In Linux the same commands are agile9exp.sh and agile9expdp.sh.

Exports can be easily automated to occur on a regular basis streamlining the refresh process needed when chasing Averify errors or other system malfunctions.

6. Perform Regular File Manager Maintenance

Check the available disk space regularly and run Missing Files Utility and Dead File Utility on a regular basis.  Although disk space can be added on the fly, if your Agile system runs out of Vault space (File Repository) it will stop processing requests, and this will inconvenience your users. In Linux, you can use the df -k or df -h (for human readable output) to check the space on the volumes of a Linux server.

In Windows, while it is possible to check disk space using the dir command, a more accurate and easier-to-use alternative is the Disk Usage (DU) utility available for free from Microsoft. You can download Microsoft Disk Usage by clicking here.

DU has the added flexibility of formatting the output for use in batch files to generate disk usage statistics as part of an automated job on the server.

Microsoft PowerShell can also be used to track disk usage although it is a bit more complex and requires more setup.

5. Monitor Disk Usage and DB Tablespace

Monitor database tablespace usage by running Averify regularly. As you do, keep an eye on the raw storage space. Linux administrators are already familiar with the commands to monitor disk space but a little more work is required on Windows systems.

Failure to properly manage disk space can cause your Agile system to unexpectedly run out of Vault (File Repository) space or the database to become stalled resulting in user complaints and lost productivity.

4. Schedule Regular Maintenance Days

Scheduled maintenance days allow you to perform a variety of systems checks, install OS patches and deploy Agile Release Update Packs (RUPs). Most IT departments already have fixed maintenance schedules for the system infrastructure and Agile administrators can take advantage of these planned downtimes to run Averify and other system checks on the system.

Maintenance can be performed monthly and often consists of running Averify, applying patches or RUPs, fixing previously identified Averify errors, and the previously mentioned log maintenance. It is also a good time to be sure your OS is up to date.

3. Regularly Review Error Log Files

Practice proactive issue management identifying potential issues before users report a problem. A system administrator should strive to proactively identify potential or existing issues in the Agile environment and monitoring log files is a part of this.

Agile will generate error statements in the stdout.log file that are not actionable. These result from any number of complex circumstances. The key is to learn which are normal and which are worthy of further investigation. Unfortunately, the best means of learning this skill is to regularly review the log files and research messages using Oracle Technology Resources (OTR).

OTR is an amazing resource of practical advice and guidance that can enhance your troubleshooting efforts. An Agile administrator should learn to wade through the Oracle documents by constructing more explicit search terms and utilizing Powerview to limit responses to Agile-related objects.

If you are not comfortable using OTR, here are my suggestions:

• Oracle has free webinars available on the OTR site to help you get started.
• Specialists, like Domain Systems can serve as your guide through OTR
• Practice is still the best means of improvement in this area.
  
  

2. Regularly Clean Up the Log Files

Keeping log files in check reduces storage requirements and makes troubleshooting easier.

During any restart of the Agile system, make it a practice to delete the existing log files or archive them if you prefer. These logs can use significant disk space and can grow to sizes that make analysis impracticable.

1.  Agile logs are located (by default) at {AGILE_HOME}/agileDomain/server/servername/logs
2.  FileManager logs are located (by default) at {AGILE_HOME}/FileManager/logs

While the application is not started, simply open File Explorer, move to the proper folders, and delete the .log files. Agile will recreate all of the log files when you start it up.

Make this a regular part of your maintenance routine to minimize the effort of opening the files and finding the most relevant sections.

1. Run Averify Regularly

Cleaning up Averify data issues is key to keeping your data consistent and the system performing at its best. Although Averify does not fix the database, this is perhaps the most overlooked aspect of Agile system maintenance and at the same time, it is the most impactful task you can undertake. No single maintenance task has such a direct impact on the reliability, performance, and integrity of your Agile database.