Guru Of Geeks

All platform users This document describes problem scenarios that can occur when using XMeta. For each scenario, the typical characteristics or symptoms of the scenario are described and a list of Must Gather information is provided. Scenario: Database Deadlock A database deadlock occurs when two (or more) database transactions each hold a resource that the other is attempting to acquire. Database deadlocks are automatically detected by the database and at least one of the transactions involved in the deadlock is terminated. The JDBC driver returns an exception in response to the termination. XMeta detects this exception and returns a DatabaseDeadlockException to the application. It is important to recognize that in any non-trivial, multi-user database-based system, deadlocks will occur. While XMeta makes every effort to reduce the likelihood of deadlocks, there are certain scenarios where deadlocks cannot be avoided. Characteristics The most obvious symptom of a database ...

PX configuration files The PX configuration file describes the machine resources available to the PX engine, including the number of nodes (physical and virtual), and scratch and permanent disk resources, etc. A default configuration file is created at installation time, located at:  <IS_HOME>/Server/Configurations/default.apt A job can override this configuration file location by setting the environment variable APT_CONFIG_FILE (recommended by the ACG Best Practices). This allows the file to be placed anywhere in the file system. However, most installations store configuration files in IS_HOME/Server/Configurations. Since configuration files are small, collect all of the files in IS_HOME/Server/Configurations. Exported job  The Designer allows a job (such as a failing job) to be exported to a .dsx file. IBM Support uses this file to understand the problem or reproduce it. You must specify the name of the .dsx file at the time of the export. Director log  The log...

Windows only Files and Data to collect Description Information Server 8.1 only < USER_HOME> \ismanager_workspace                        \.metadata\.plugins\org.eclipse.ui.workbench\log Client Eclipse log file

Reporting framework is part of the Information Services Framework (ISF) common services that provides life-cycle management for all Reporting artifacts such as deployment, report creation/modification, report execution/scheduling and viewing of report results. All platform users Files and Data to collect Description <WAS_IS_PROFILE> \logs\*.* All the WebSphere Application Server log files <WAS_IS_PROFILE> \javacore.XXX.txt <WAS_IS_PROFILE> \heapdump.XXX.phd Java Core and heap dump files created by  OutOfMemoryErrors: there may be several, collect the most recent ones     SERVER Machine and WebSphere Application Server Cluster Nodes <JREPORT_HOME>\logs\*.* <JREPORT_HOME>\bin\*.* JReport log files. Note : In a WebSphere Application Server clustered environment, JReport log files may be found on each remote machine where a cluster node resides.

All platform users Files and Data to collect Description Information Server 8.0.1 and 8.1 < IS_HOME >\Clients\istools\cli\orbtrc.<DATE>.txt Not always present < IS_HOME >\Clients\istools\cli\orbmsg.<DATE>.txt Not always present < IS_HOME >\Clients\istools\manager\orbtrc.<DATE>.txt Not always present < IS_HOME >\Clients\istools\manager\orbmsg.<DATE>.txt Not always present Information Server 8.1 only < USER_HOME> \ istool_workspace \.metadata\.log Client Eclipse log file

All platform users

Windows only users