Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

(3 Ratings)
facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

FAQ: What are the possible reasons for a core file not being generated when an Informatica process terminates unexpectedly?
Answer

The following are the primary reasons why a core file might not be generated (This list pertains to Solaris OS and Linux, unless specified otherwise):

  • The current user does not have permission to write in the current working directory of the process.

  • The current user has write permission on the current working directory, but there is already a file named core that has read-only permission.

  • The current directory does not have enough space remaining.

  • The current directory has a subdirectory named core.

  • The current working directory is remote. It might be mapped by Network File System (NFS) and NFS failed just at the time the core dump was about to be created.

  • Solaris OS only: The coreadm tool has been used to configure the directory and name of the core file, but any of the above reasons apply for the configured directory or filename.

  • The core file size limit is too low. Check your core file limit using the ulimit -c command (Bash shell) or the limit -c command (C shell). If the output from this command is not unlimited, the core dump file size might not be large enough. If this is the case, you will get truncated core dumps or no core dump at all. In addition, ensure that any scripts that are used to launch the VM or your application do not disable core dump creation.

  • The process is running a setuid program and therefore the operating system will not dump core unless it is configured explicitly.

  • Java specific: If the process received SIGSEGV or SIGILL but no core dump, it has possibly been handled by the process.

    Example

    HotSpot VM uses the SIGSEGV signal for legitimate purposes, such as throwing NullPointerException, deoptimization, and so forth. The signal is unhandled by the Java VM only if the current instruction (PC) falls outside Java VM generated code. These are the only cases in which HotSpot dumps core.

  • Java specific: The JNI Invocation API was used to create the VM. The standard Java launcher was not used. The custom Java launcher program handled the signal by just consuming it and produced the log entry silently. This situation has occurred with certain Application Servers and Web Servers. These Java VM embedding programs transparently attempt to restart (fail over) the system after an abnormal termination. In this case, the fact that a core dump is not produced is a feature and not a bug.

More Information

Applies To
Product(s): Data Explorer; Data Quality; Metadata Manager; PowerCenter; PowerExchange; Support Console
Product Version(s): Data Explorer; Data Quality; Informatica 9.x; PowerCenter; PowerCenter 8.x; PowerCenter 9.x
Database:
Operating System(s): AIX; HP-UX; HP-UX Itanium; Redhat Linux; SUSE Linux ES; Solaris
Other Software:

Reference

Attachments

Last Modified Date:9/2/2015 5:03 AMID:21451
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)