While running an Aggregation process or a restructure in essbase have you ever encountered either of these:
- EAS quits accepting logins
- Essbase going down time and again.
- Failed Data load / Failed Data Export / Failed Level 0 export
- All of the above together :)
In all these cases, there is a huge possibility that you are facing creation of tmp files issue on your Essbase Server, specifically if you are on Linux
The Temp directory contains mostly files that are required temporarily. Many programs use this to create lock files and for temporary storage of data. Do not remove files from this directory unless you know exactly what you are doing! Many of these files are important for currently running programs and deleting them may result in a system crash. Usually it won't contain more than a few KB anyway. On most systems, this directory is cleared out at boot or at shutdown by the local system.
In MS-Dos and Windows, the temporary directory is set by the environment variable TEMP. In UNIX and LINUX, the global temporary directories are /tmp and /var/tmp.Typically, /var/tmp is for persistent files (as it may be preserved over reboots), and /tmp is for more temporary files.
Generically when the size of these temp files increases and occupies whole of your disk space (90-95%), you might run into any of the above mentioned issues.
A simple solution is in steps below:
- Stop the EAS server.
- On the box where EAS is installed, split out the two temp folders that are under Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices1\tmp
- Next, make a sibling folder to tmp called tmpeas, and change the JVMOPtion for the io tmp to point to that tmpeas folder.
- In Windows, JVMOption (value is -Djava.io.tmpdir= C:\Oracle\Middleware\user_projects\epmsystem1\tmp) for each product (HKLM\Software\Hyperion Solutions) and redirect it to value where there is enough space to hold these files.
- Restart EAS server, test and monitor to see if the issue occurs again.
Since creation of Temp files is a regular issue, and the JVMOption is only going to redirect your temp files to another location (where you can afford to keep them!!).
Another option to avoid such kind of failures in systems will be to schedule a regular clean up of such temp files in Essbase Server.
In Linux, the below script would work usefully:
#!/bin/bash
#This script will automatically delete temporary files
rm -rf /tmp/*
rm -rf/var/tmp/*
fsck -A
exit
In Windows, you can create a batch file to delete your Temp folder on a variance of certain days (here, 5 days)
REM Remove files older than 5 days
forfiles /p "<default path to temp file location on windows\Local>\Temp" /s /m *.tmp* /c "cmd /c Del @path" /d 5
Cheers,
Anvi S.