Hi,

The DB2 is installed in a Windows 2000, yesterday installed the SP4 for windows 2000, and this crahs the db2.

First a db was market with "bad", I restore this DB.
And now, when I run a stored procedure:
---------------
db2 => call ventas4(2003,10)
SQL1224N A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command. SQLSTATE=55032
----------------




In the db2diag:
-----------------
2003-11-08-18.30.01.092000 InstanceB2 Node:000
PID:1652(db2syscs.exe) TID:2776 Appid:none
oper system services sqloSSemClose Probe:20

Unexpected system error 0x6 has occurred.
This has been mapped to ZRC 0x83000006.

PID:1652 TID:2776 Node:000 Title: SYSTEM ERROR DESCRIPTION
The handle is invalid.


2003-11-08-18.30.01.154000 InstanceB2 Node:000
PID:1652(db2syscs.exe) TID:2776 Appid:none
oper system services sqloSSemClose Probe:20

Unexpected system error 0x6 has occurred.
This has been mapped to ZRC 0x83000006.

PID:1652 TID:2776 Node:000 Title: SYSTEM ERROR DESCRIPTION
The handle is invalid.

Sorry, the error is sql1224, an NOT 1024.

Sorry, the error is sql1224, an NOT 1024.

Did you try connecting the second time ?

If it fails, stop and start the instance ...

Check your dbm parameter, KEEPDARI ...

db2 get dbm cfg | find "KEEPDARI"

IF this is set to yes, then change it to NO

db2 update dbm cfg using KEEPDARI NO

Change this parameter before you stop/start the instance ...

Generally it is advisable to keep this parameter to YES on prod, but useful to have it NO in dev as the procs will be changing often ...

HTH

Sathyaram

Hi Sathyaram,

Thanks for your replay.
I update the dbm parameter keepdari to NO, but not found.

When I get the error the instance no stop. The DB2 is Stop, no the instance.

any idea?

Thanks again.

Abel.
Sorry by my english.