Monitoring

Showing 69

To monitor system resource usage at database level in a pureScale environment

All current monitoring facilities can not meet customer requirements to monitor overall system resource consumed for a specific database, in a database consolidation scenario of pureScale. PMR#: TS000078803

over 5 years ago in Db2 / Monitoring 0 Not under consideration

2 VOTE

Allow better monitoring of DB2 Thread/Connection types

Currently there are various ZPARMs to "control" thread management (CTHREAD,MAXDBAT,CONDBAT,IDFORE,IDBACK,etc). These ZPARMS are upper bound limits of the number of each type of thread/connection that DB2 is configured with. There is very little in...

over 3 years ago in Db2 / Monitoring 0 Not under consideration

4 VOTE

Invoke the DB2 call-out scripts (COS) for ALL First Occurrence Data Collection (FODC) events

Currently the DB2 call-out scripts (COS) will not be invoked for all ALL First Occurrence Data Collection (FODC) events. For instance the only time that FODC_AppErr% events will invoke the db2cos script is when the condition happens on a sub-agent...

over 7 years ago in Db2 / Monitoring 0 Not under consideration

2 VOTE

Enhancement regarding the .ftok file and the DB2 instance.

I will suggest the following:1. Let Db2 log a simple message 'The .ftok file is missing, last seen ' when the instance started.2. Also, suggest to execute ~/sqllib/bin/db2ftok or go ahead and execute it

over 4 years ago in Db2 / Monitoring 0 Not under consideration

1 VOTE

DB2 listener not activated after DB process killed by OS and restarted automatically by TSA in HADR environment

We had DB2 HADR primary/standby configuration. Due to one application job,DB2 consumes all memory and OS killed db2sysc process. db2 restarted automatically by TSA but listener wasn't activated . There was no evidence in logs which process was usi...

over 2 years ago in Db2 / Monitoring 0 Not under consideration

3 VOTE

Make USAGE LIST only display TBSCAN

Enhance USAGE LIST to only track a table (which already exists since DB2 10.1) but for statements causing TBSCANs

about 8 years ago in Db2 / Monitoring 0 Not under consideration

1 VOTE

Begin / End COMMIT instrumentation for DRDA, CICS/IMS

Complex CICS/IMS or DRDA transactions (involving multiple programs with an implicit Commit at the end) are incorrectly presented on the Omegamon Accounting Report/Trace. By design the costs of the tough SYNC (COMMIT) operation are added to the las...

almost 3 years ago in Db2 / Monitoring 0 Not under consideration

2 VOTE

Lock event monitor does not log hex values of prepared statements

When using the lock event monitor to track prepared statements involved in lock timeouts/deadlocks, it was observed that parameter marker values for hex entries are not logged even though the option for history and values is enabled. This works fi...

almost 7 years ago in Db2 / Monitoring 0 Not under consideration

1 VOTE

Lack of information about Queries from Federated DBs - particulary from DB2 z/OS

From DSM we should be able to see the transactions from federated databases. In the case when we are having some federated transaction contention we are not able to see on the source database on DSM getting more difficulty to diagnose a performanc...

over 3 years ago in Db2 / Monitoring 0 Not under consideration

2 VOTE

db will be blocked and hang after mon_heap is run out

agents will be blocked and will hang after mon_heap is run out when database turns on event monitor. Now it is works as design, yet customer hope we can change the design and decouple between event monitor and the agents executing some SQLs. So ag...

over 7 years ago in Db2 / Monitoring 0 Not under consideration

Please enter your email address

FILTER BY CATEGORY