slow connection to DB2/LINUX 8.2.3

[jku]

Hello,

after installing DB2 V8.2.3 on OpenSuse 10.1 (in vmware)
we have created a database instance with the restore command:
db2 "restore database $OLD_DB user db2inst1 using db2inst1 from
$BACKUP_DIRECTO RY taken at $TS into $DB".

We have activated the database but the first connection is still slow.
db2 connect to <db_name>

In the db2diag.log there are the following entries:
2006-11-14-22.53.17.852588 +060 E6171935G798 LEVEL: Error (OS)
PID : 3811 TID : 2955049888 PROC : db2hmon
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloPdbConnectS ocket, probe:20
MESSAGE : ZRC=0x810F0019=-2129723367=SQLO _CONN_REFUSED "Connection
refused"
CALLED : OS, -, connect OSERR: ECONNREFUSED
(111)
DATA #1 : String, 32 bytes
Unable to connect socket on path
DATA #2 : socket, 4 bytes
6
DATA #3 : sockaddr, 41 bytes
0xB021CBE4 : 0100 2F68 6F6D 652D 6C6F 6361 6C2F 6461
.../home-local/da
0xB021CBF4 : 7375 7372 2F64 6173 2F74 6D70 2F64 6173
susr/das/tmp/das
0xB021CC04 : 6E61 6D65 6470 6970 65 namedpipe
DATA #4 : File name, 39 bytes

DAS server is not running. Is this server needed?

Thank you!
Jörn

[www.spaceboot.eu]

The first connection to a db will always be slow because it needs to
start services, open files, create logs, allocate memory, ... Stuff you
don't need to do for a second connect.
Check if subsequent connects are as slow as the first, and if not, you
could force a 'dummy' connect after each db2start, so your users won't
notice.
jku schreef:

Hello,

after installing DB2 V8.2.3 on OpenSuse 10.1 (in vmware)
we have created a database instance with the restore command:
db2 "restore database $OLD_DB user db2inst1 using db2inst1 from
$BACKUP_DIRECTO RY taken at $TS into $DB".

We have activated the database but the first connection is still slow.
db2 connect to <db_name>

In the db2diag.log there are the following entries:
2006-11-14-22.53.17.852588 +060 E6171935G798 LEVEL: Error (OS)
PID : 3811 TID : 2955049888 PROC : db2hmon
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloPdbConnectS ocket, probe:20
MESSAGE : ZRC=0x810F0019=-2129723367=SQLO _CONN_REFUSED "Connection
refused"
CALLED : OS, -, connect OSERR: ECONNREFUSED
(111)
DATA #1 : String, 32 bytes
Unable to connect socket on path
DATA #2 : socket, 4 bytes
6
DATA #3 : sockaddr, 41 bytes
0xB021CBE4 : 0100 2F68 6F6D 652D 6C6F 6361 6C2F 6461
../home-local/da
0xB021CBF4 : 7375 7372 2F64 6173 2F74 6D70 2F64 6173
susr/das/tmp/das
0xB021CC04 : 6E61 6D65 6470 6970 65 namedpipe
DATA #4 : File name, 39 bytes

DAS server is not running. Is this server needed?

Thank you!
Jörn

[Lennart]

www.spaceboot.eu wrote:

The first connection to a db will always be slow because it needs to
start services, open files, create logs, allocate memory, ... Stuff you
don't need to do for a second connect.
Check if subsequent connects are as slow as the first, and if not, you
could force a 'dummy' connect after each db2start, so your users won't
notice.

But he activated the database and that should take care of this, or am
I missing something?
/Lennart

[Greg Nash]

How about NUM_INITAGENTS - Initial number of agents in pool? I believe
it defaults to zero, but if it's nonzero then some agents are primed and
ready for action, reducing delays on the first connections.
(Does that make them secret agents? I always thought this was an
amusing parameter :-)

Lennart wrote:

www.spaceboot.eu wrote:

>>The first connection to a db will always be slow because it needs to
start services, open files, create logs, allocate memory, ... Stuff you
don't need to do for a second connect.
Check if subsequent connects are as slow as the first, and if not, you
could force a 'dummy' connect after each db2start, so your users won't
notice.

But he activated the database and that should take care of this, or am
I missing something?
/Lennart