Sets whether Essbase saves a core dump to a file when an abnormal termination of an agent or server process occurs. UNIX only.
CRASHDUMP TRUE | FALSE
TRUE—Creates a directory containing a core file for each abnormal termination.
FALSE—No core file is created. This is the default value.
CRASHDUMP helps diagnose abnormal program terminations. For each agent crash, when CRASHDUMP is set to TRUE, Essbase creates a file named core. It places the core file in an ESSBASE.abc directory under ESSBASEPATH, where abc displays the date and time. For example:
ESSBASE.Mon_Jun_3_18_16_17_2003/core
In each instance of a server crash, when CRASHDUMP is set to TRUE, Essbase creates the core file in a directory under ARBORPATH/app/appName, where appName is the name of the application. The name of the new directory is ESSSVR.abc, where abc displays the date and time. For example:
/EssbaseServer/app/Sample/ESSSVR.Mon_Jun_3_18_16_17_2003/core
If the an agent or server process is automatically shut down, the core file contains a core dump of that moment. If an agent or server process is shut down manually, the core file may be empty.
Look for the core file any time you experience abnormal Essbase program terminations. If the file is not empty, provide it to Support and then remove it and its directory from the computer. If the core file is empty, remove it and its directory from the computer.
In normal operations without abnormal terminations, core files are not created.
CRASHDUMP TRUE