Troubleshooting
Problem
Symptom
- Some of these files (especially the CORE / DMP files) can be very large.
The file names will vary depending on what portion of the Controller architecture fails.
Example: TM1 (FAP) dump files will look similar to:
- HEAPDUMP.xxxxyyyyzzzz.phd
- JAVACORE.xxxxyyyyzzzz.txt
- CORE.xxxxyyyyzzzz.dmp
- SNAP.xxxxyyyyzzzz.trc
Cognos BI dump files will look similar to:
- BIBusTKServerMain_seh_3524_3208.dmp
Resolving The Problem
Answer: The files are the diagnostic output which are automatically created when an IBM JAVA process fails/crashes.
==================================
Question - Can their location be changed?
Answer: Yes.
There are different possible methods. Choose the method that best suits your needs:
(1) Create/modify the System Variable(s) - recommended for most situations.
Probably the easiest/simplest method is to create/use System Variables.
- For more information, see separate IBM Technote #1693195.
(2) Use the Tomcat Java configuration utility - for TM1
If the crash is coming from TM1Web, then a different method is to use the Tomcat Java configuration utility, and then modify the Java settings tab.
- For more information, see separate IBM Technote #1968185.
==================================
Question - Can they be safely deleted?
Answer: In most cases, yes.
- The only reason to keep them is to send them to IBM Support to help diagnose issues (in other words, to understand why the system crashed in the first place - which led to the creation of those files).
==================================
Question - Can dump file creation be disabled?
Answer: It is possible to disable dump file creation for the Cognos BI engine.
Steps:
1. Logon to the server where IBM Cognos BI engine is installed
- For most customers, this is the Controller application server.
2. Browse to the folder 'configuration'
- TIP: This will be in a similar location to here: C:\Program Files\IBM\cognos\ccr_64\configuration
3. Edit the following file: cclWinSEHConfig.xml
4. Locate a section similar to the following:
- <configuration>
- <env_var name="CCL_HWE_ABORT" value="2:2"/>
5. Modify the value of the environment variable setting to 0 (zero) so that it looks similar to:
- <env_var name="CCL_HWE_ABORT" value="0"/>
6. Save the file.
7. Restart the system, and test.
Related Information
Was this topic helpful?
Document Information
Modified date:
07 May 2019
UID
swg21990831