OS: SUsE z/Linux 2.4.21
DB2: Connect EE V8.1FP4

Hay everybody,

I have setup a Connect EE V8.1FP4 on a z/Linux instance. After creation of the instance (all with default params except SVCENAME of course) and registering the db2fm monitor to start and crash recover the instance I have a weird problem.

After X-hours (where X means between 1 and 30 or 40) I can login as instance user. But every command I run against the instance does fail. Better to say, the commandline utility db2 hangs and does not use CPU nor doing anything on the filesystem. External connections via this db2 gateway instance still work without disadvantages in any field.

It does not matter whether I do a:
$> db2 LIST DCS APPLICATIONS
or
$> db2 ATTACH TO $DB2INSTANCE

it works fine for a while and for no reason it suddenly hangs.
CTRL+C can not kill the command. I have to kill it with signal 9.

If I look on the OS I see all parameters well: memory, cpu, storage, accessibilty to files and folders. that is all fine.

I do not get any error in diaglog or eventlog.
If I kill all db2 processes of this instance and clean up all IPCS resources, then startup the instance again it works fine.

Did anyone experience such a behaviour?
greets
roman

-------- system configuration ----------------
Database Manager Configuration

Node type = Database Server with local and remote clients

Database manager configuration release level = 0x0a00

CPU speed (millisec/instruction) (CPUSPEED) = 5.668131e-07

Max number of concurrently active databases (NUMDB) = 8
Data Links support (DATALINKS) = NO
Federated Database System Support (FEDERATED) = NO
Transaction processor monitor name (TP_MON_NAME) =

Default charge-back account (DFT_ACCOUNT_STR) =

Java Development Kit installation path (JDK_PATH) = /opt/IBMJava2-s390-131

Diagnostic error capture level (DIAGLEVEL) = 3
Notify Level (NOTIFYLEVEL) = 3
Diagnostic data directory path (DIAGPATH) = /home/tdb2ins1/sqllib/db2dump

Default database monitor switches
Buffer pool (DFT_MON_BUFPOOL) = OFF
Lock (DFT_MON_LOCK) = OFF
Sort (DFT_MON_SORT) = OFF
Statement (DFT_MON_STMT) = OFF
Table (DFT_MON_TABLE) = OFF
Timestamp (DFT_MON_TIMESTAMP) = ON
Unit of work (DFT_MON_UOW) = OFF
Monitor health of instance and databases (HEALTH_MON) = OFF

SYSADM group name (SYSADM_GROUP) = DB2IADM1
SYSCTRL group name (SYSCTRL_GROUP) =
SYSMAINT group name (SYSMAINT_GROUP) =
SYSMON group name (SYSMON_GROUP) =

Database manager authentication (AUTHENTICATION) = SERVER
Cataloging allowed without authority (CATALOG_NOAUTH) = NO
Trust all clients (TRUST_ALLCLNTS) = YES
Trusted client authentication (TRUST_CLNTAUTH) = CLIENT
Bypass federated authentication (FED_NOAUTH) = NO

Default database path (DFTDBPATH) = /home/tdb2ins1

Database monitor heap size (4KB) (MON_HEAP_SZ) = 90
Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 2048
Audit buffer size (4KB) (AUDIT_BUF_SZ) = 0
Size of instance shared memory (4KB) (INSTANCE_MEMORY) = AUTOMATIC
Backup buffer default size (4KB) (BACKBUFSZ) = 1024
Restore buffer default size (4KB) (RESTBUFSZ) = 1024

Sort heap threshold (4KB) (SHEAPTHRES) = 20000

Directory cache support (DIR_CACHE) = YES

Application support layer heap size (4KB) (ASLHEAPSZ) = 15
Max requester I/O block size (bytes) (RQRIOBLK) = 32767
Query heap size (4KB) (QUERY_HEAP_SZ) = 1000
DRDA services heap size (4KB) (DRDA_HEAP_SZ) = 128

Workload impact by throttled utilities(UTIL_IMPACT_LIM) = 100

Priority of agents (AGENTPRI) = SYSTEM
Max number of existing agents (MAXAGENTS) = 200
Agent pool size (NUM_POOLAGENTS) = 100(calculated)
Initial number of agents in pool (NUM_INITAGENTS) = 0
Max number of coordinating agents (MAX_COORDAGENTS) = MAXAGENTS
Max no. of concurrent coordinating agents (MAXCAGENTS) = MAX_COORDAGENTS
Max number of client connections (MAX_CONNECTIONS) = MAX_COORDAGENTS

Keep fenced process (KEEPFENCED) = YES
Number of pooled fenced processes (FENCED_POOL) = MAX_COORDAGENTS
Initial number of fenced processes (NUM_INITFENCED) = 0

Index re-creation time (INDEXREC) = RESTART

Transaction manager database name (TM_DATABASE) = 1ST_CONN
Transaction resync interval (sec) (RESYNC_INTERVAL) = 180

SPM name (SPM_NAME) =
SPM log size (SPM_LOG_FILE_SZ) = 256
SPM resync agent limit (SPM_MAX_RESYNC) = 20
SPM log path (SPM_LOG_PATH) =

TCP/IP Service name (SVCENAME) = tdb2ins1
Discovery mode (DISCOVER) = SEARCH
Discover server instance (DISCOVER_INST) = ENABLE

Maximum query degree of parallelism (MAX_QUERYDEGREE) = ANY
Enable intra-partition parallelism (INTRA_PARALLEL) = NO

No. of int. communication buffers(4KB)(FCM_NUM_BUFFERS) = 1024


------- Kernel Parameters for DB2 -----------
kernel.msgmni = 512
kernel.sem = 250 128000 32 1024

Hi,

The subject line of my post says everything.

We are also facing the same problems with FP4 and that too on windows. Well FP4 has been withdrawn by IBM and FP4a has come in it's place.

What I suggest is that upgrade to FP4a but that's risky and if possible downgrade to FP3 that's really recommendable.

We have already logged a PMR with IBM and we will keep you updated on the progress of the same.

Cheers

Nitin.

Hi,

Please also refer to the thread below.

http://www.dbforums.com/t983394.html

Cheers

Nitin

Ohh... great. thxs Nitin.

Once more it was is a BugPak not a FixPak I'll update my z/Linux instance to FP4a and see if this hangups are resolved. I'll report in my experience.

Thxs again