problem starting db with version 9.1

db2stop your instance,
clear all processes and IPC resources the instance owner have. (ps
wiht kill -9, ipcrm)
db2start
db2 connect

would this help?

"Frank Swarbrick дµÀ£º
"
> Has anyone come upon this problem? My DB2/LUW 9.1 database seems to be
> both "started and not started". Check out the following:
>
> C:\Program Files\IBM\SQLLIB\BIN>db2 connect to sample
> SQL1032N No start database manager command was issued. SQLSTATE=57019
>
> C:\Program Files\IBM\SQLLIB\BIN>db2start
> SQL1026N The database manager is already active.
>
> C:\Program Files\IBM\SQLLIB\BIN>db2stop
> SQL1064N DB2STOP processing was successful.
>
> C:\Program Files\IBM\SQLLIB\BIN>db2start
> SQL1063N DB2START processing was successful.
>
> C:\Program Files\IBM\SQLLIB\BIN>db2 connect to sample
> SQL1032N No start database manager command was issued. SQLSTATE=57019
>
> C:\Program Files\IBM\SQLLIB\BIN>
>
> Any thoughts? This is DB2 Express-C on Windows XP Professional:
> ============================================================
> About DB2 Administration Tools Environment
> ============================================================
> DB2 administration tools level:
> Product identifier SQL09010
> Level identifier 02010107
> Level DB2 v9.1.0.356
> Build level s060629
> PTF NT32
> ============================================================
> Java development kit (JDK):
> Level IBM Corporation 1.5.0
> ============================================================
>
> Frank
 >> Stay informed about: problem starting db with version 9.1 

mike wrote:
> Frank Swarbrick wrote:
>> Has anyone come upon this problem? My DB2/LUW 9.1 database seems to be
>> both "started and not started". Check out the following:
>>
>> C:\Program Files\IBM\SQLLIB\BIN>db2 connect to sample
>> SQL1032N No start database manager command was issued. SQLSTATE=57019
>>
>> C:\Program Files\IBM\SQLLIB\BIN>db2start
>> SQL1026N The database manager is already active.
> ...
>
> What is in the db2diag.log file ?
>
> If you cannot see anything in there, set DIAGLEVEL to 4 and retry
> bouncing the instance.
>

Well, here's the db2diag.log info for my db2start. Doesn't tell me
anything, but...

2006-12-18-17.00.44.015000-420 I1H929 LEVEL: Event
PID : 6104 TID : 6268 PROC : db2start.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
START : New Diagnostic Log file
DATA #1 : Build Level, 128 bytes
Instance "DB2" uses "32" bits and DB2 code release "SQL09010"
with level identifier "02010107".
Informational tokens are "DB2 v9.1.0.356", "s060629", "NT32", Fix Pack "0".
DATA #2 : System Info, 1564 bytes
System: WIN32_NT SWARCLAIRE Service Pack 2 5.1 x86 Family 15, model 47,
stepping 0
CPU: total:1 online:1 Cores per socket:1 Threading degree per core:1
Physical Memory(MB): total:1023 free:214 available:214
Virtual Memory(MB): total:2461 free:1394
Swap Memory(MB): total:1438 free:1180
Information in this record is only valid at the time when this file was
created (see this record's time stamp)

2006-12-18-17.00.44.000000-420 I933H1538 LEVEL: Event
PID : 6104 TID : 6268 PROC : db2start.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
DATA #1 : String, 40 bytes
C:\PROGRA~1\IBM\SQLLIB\\bin\DB2STAR2.EXE
DATA #2 : Hexdump, 256 bytes
0x0012ADB4 : 433A 5C50 524F 4752 417E 315C 4942 4D5C C:\PROGRA~1\IBM\
0x0012ADC4 : 5351 4C4C 4942 5C5C 6269 6E5C 4442 3253 SQLLIB\\bin\DB2S
0x0012ADD4 : 5441 5232 2E45 5845 0000 0000 0000 0000 TAR2.EXE........
0x0012ADE4 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0012ADF4 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0012AE04 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0012AE14 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0012AE24 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0012AE34 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0012AE44 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0012AE54 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0012AE64 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0012AE74 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0012AE84 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0012AE94 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0012AEA4 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2006-12-18-17.00.44.593000-420 I2473H397 LEVEL: Info
PID : 7720 TID : 7476 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleAllocateAndInitializeKRCB,
probe:789
MESSAGE : Default agentsReuseApplHeap setting:
DATA #1 : Hexdump, 4 bytes
0x038C075C : 0000 0000 ....

2006-12-18-17.00.44.703000-420 I2872H352 LEVEL: Info
PID : 7720 TID : 8056
FUNCTION: DB2 Common, Cryptography, cryptContextRealInit, probe:100
DATA #1 : String, 20 bytes
ICC VERSION: 1.4.1.0
DATA #2 : String, 49 bytes
ICC INSTALL PATH: C:\PROGRA~1\IBM\SQLLIB\\bin\icc
DATA #3 : String, 18 bytes
ICC FIPS MODE: YES

2006-12-18-17.00.44.796000-420 I3226H303 LEVEL: Info
PID : 7720 TID : 8056
FUNCTION: DB2 Common, Security, Users and Groups, secLoadGroupPlugin,
probe:10
DATA #1 : String, 87 bytes
Loaded plugin library
C:\PROGRA~1\IBM\SQLLIB\\security\plugin\IBM\group\IBMOSgroups.dll

2006-12-18-17.00.44.796000-420 I3531H243 LEVEL: Info
PID : 7720 TID : 8056
FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
DATA #1 : String, 32 bytes
db2secGroupPluginInit successful

2006-12-18-17.00.44.859000-420 I3776H313 LEVEL: Info
PID : 7720 TID : 8056
FUNCTION: DB2 Common, Security, Users and Groups,
secLoadServerAuthPlugin, probe:10
DATA #1 : String, 92 bytes
Loaded plugin library
C:\PROGRA~1\IBM\SQLLIB\\security\plugin\IBM\server\IBMOSauthserver.dll

2006-12-18-17.00.44.859000-420 I4091H248 LEVEL: Info
PID : 7720 TID : 8056
FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
DATA #1 : String, 37 bytes
db2secServerAuthPluginInit successful

2006-12-18-17.00.46.453000-420 I4341H342 LEVEL: Info
PID : 7720 TID : 8056 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr, probe:160
MESSAGE : DIA3218I "1" TCP/IP connection manager(s) was/were successfully
started.

2006-12-18-17.00.46.453000-420 I4685H322 LEVEL: Info
PID : 7720 TID : 8056 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcp_start_listen, probe:80
MESSAGE : DIA3000I "TCPIP" protocol support was successfully started.

2006-12-18-17.00.49.718000-420 I5009H313 LEVEL: Info
PID : 7720 TID : 8056 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, syncpoint manager, sqlcspm_start, probe:0
MESSAGE : DIA3000I "DRDA SPM" protocol support was successfully started.

2006-12-18-17.00.49.750000-420 E5324H852 LEVEL: Event
PID : 7720 TID : 7476 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
MESSAGE : ADM7513W Database manager has started.
START : DB2 DBM
DATA #1 : Build Level, 128 bytes
Instance "DB2" uses "32" bits and DB2 code release "SQL09010"
with level identifier "02010107".
Informational tokens are "DB2 v9.1.0.356", "s060629", "NT32", Fix Pack "0".
DATA #2 : System Info, 1564 bytes
System: WIN32_NT SWARCLAIRE Service Pack 2 5.1 x86 Family 15, model 47,
stepping 0
CPU: total:1 online:1 Cores per socket:1 Threading degree per core:1
Physical Memory(MB): total:1023 free:159 available:159
Virtual Memory(MB): total:2461 free:1239
Swap Memory(MB): total:1438 free:1080

2006-12-18-17.00.49.828000-420 E6178H535 LEVEL: Info (OS)
PID : 6104 TID : 6268 PROC : db2start.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqlofindf, probe:100
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.
CALLED : OS, -, unspecified_system_function
OSERR : 2 "The system cannot find the file specified."
DATA #1 : File name, 37 bytes
C:\PROGRA~1\IBM\SQLLIB\DB2\ctrl\*.ick

2006-12-18-17.00.49.828000-420 E6715H535 LEVEL: Info (OS)
PID : 6104 TID : 6268 PROC : db2start.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqlofindf, probe:100
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.
CALLED : OS, -, unspecified_system_function
OSERR : 2 "The system cannot find the file specified."
DATA #1 : File name, 37 bytes
C:\PROGRA~1\IBM\SQLLIB\DB2\ctrl\*.dck

2006-12-18-17.00.49.828000-420 I7252H666 LEVEL: Info
PID : 6104 TID : 6268 PROC : db2start.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1063 sqlerrml: 0
sqlerrmc:
sqlerrp : SQL09010
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) ( (9) (10) (11)
sqlstate:

2006-12-18-17.00.50.328000-420 I7920H398 LEVEL: Info (OS)
PID : 3936 TID : 5240
FUNCTION: DB2 Common, OSSe, OSSHIPCSemaphore::attach, probe:40
MESSAGE : ECF=0x9000001A File doesn't exist
CALLED : OS, -, OpenSemaphore OSERR:
ERROR_FILE_NOT_FOUND (2)
ARG #3 : String, 65 bytes
Global\OSSEIPC105CPROGRA~1IBMSQLLIBDB2hmonCacheDB20ossipcres.ftok

2006-12-18-17.00.50.328000-420 I8320H245 LEVEL: Info
PID : 3936 TID : 5240
FUNCTION: DB2 Common, OSSe, oss_directory_delete_recursive, probe:70
MESSAGE : ECF=0x90000019 A component of the path is not a directory

2006-12-18-17.00.50.343000-420 I8567H352 LEVEL: Info (OS)
PID : 3936 TID : 5240
FUNCTION: DB2 Common, OSSe, OSSHIPCMemory::attach, probe:50
MESSAGE : ECF=0x90000047 The specified memory is not found and IPC_CREAT
flag is not specified.
CALLED : OS, -, OpenFileMapping OSERR:
ERROR_FILE_NOT_FOUND (2)

2006-12-18-17.00.50.343000-420 I8921H422 LEVEL: Info
PID : 3936 TID : 5240
FUNCTION: DB2 Common, OSSe, OSSHIPCMemory::attach, probe:50
MESSAGE : ECF=0x90000047 The specified memory is not found and IPC_CREAT
flag is not specified.
DATA #1 : String, 70 bytes
Global\OSSEIPC104CPROGRA~1IBMSQLLIBDB2hmonCacheDB20ossipcres.ftok_dstf
DATA #2 : Hex, 4 bytes
0x0
DATA #3 : Hex, 4 bytes
0x0

2006-12-18-17.00.51.093000-420 I9345H664 LEVEL: Info
PID : 3936 TID : 5240 PROC : db2fmp.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1427 sqlerrml: 0
sqlerrmc:
sqlerrp : SQL09010
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) ( (9) (10) (11)
sqlstate:

2006-12-18-17.00.51.140000-420 I10011H358 LEVEL: Info
PID : 3936 TID : 5240
FUNCTION: DB2 Common, Cryptography, cryptContextRealInit, probe:100
DATA #1 : String, 20 bytes
ICC VERSION: 1.4.1.0
DATA #2 : String, 55 bytes
ICC INSTALL PATH: C:\Program Files\IBM\SQLLIB\\bin\\icc
DATA #3 : String, 18 bytes
ICC FIPS MODE: YES

2006-12-18-17.00.51.234000-420 I10371H387 LEVEL: Info
PID : 3936 TID : 5240 PROC : db2fmp.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, Health Monitor, hmonStartMainHmonThread, probe:130
MESSAGE : Health monitor was started successfully
DATA #1 : Hexdump, 4 bytes
0x0012F6B0 : 0000 0000 ....
 >> Stay informed about: problem starting db with version 9.1 

Some of those entries look suspicious to me, though I cannot say if the
instance is correctly started or not.

e.g

2006-12-18-17.00.50.328000-420 I7920H398 LEVEL: Info (OS)
PID : 3936 TID : 5240
FUNCTION: DB2 Common, OSSe, OSSHIPCSemaphore::attach, probe:40
MESSAGE : ECF=0x9000001A File doesn't exist
CALLED : OS, -, OpenSemaphore OSERR:
ERROR_FILE_NOT_FOUND (2)
ARG #3 : String, 65 bytes
Global\OSSEIPC105CPROGRA~1IBMSQLLIBDB2hmonCacheDB20ossipcres.ftok

2006-12-18-17.00.50.328000-420 I8320H245 LEVEL: Info
PID : 3936 TID : 5240
FUNCTION: DB2 Common, OSSe, oss_directory_delete_recursive, probe:70
MESSAGE : ECF=0x90000019 A component of the path is not a directory

2006-12-18-17.00.50.343000-420 I8567H352 LEVEL: Info (OS)
PID : 3936 TID : 5240
FUNCTION: DB2 Common, OSSe, OSSHIPCMemory::attach, probe:50
MESSAGE : ECF=0x90000047 The specified memory is not found and
IPC_CREAT
flag is not specified.
CALLED : OS, -, OpenFileMapping OSERR:
ERROR_FILE_NOT_FOUND (2)


This is DB2-express on Win-XP PRO, according to your first post on this
topic.

Is this a standalone windows, or a member of a domain ?

Before you installed DB2-express on this box, was there already some
previous installation of some flavour of db2 on the box ?

Were there any messages or errors during installation ?
 >> Stay informed about: problem starting db with version 9.1 

mike 12/19/06 12:39 AM >>>
>Some of those entries look suspicious to me, though I cannot say if the
>instance is correctly started or not.
>
>e.g
>
>2006-12-18-17.00.50.328000-420 I7920H398 LEVEL: Info (OS)
>PID : 3936 TID : 5240
>FUNCTION: DB2 Common, OSSe, OSSHIPCSemaphore::attach, probe:40
>MESSAGE : ECF=0x9000001A File doesn't exist
>CALLED : OS, -, OpenSemaphore OSERR:
>ERROR_FILE_NOT_FOUND (2)
>ARG #3 : String, 65 bytes
>Global\OSSEIPC105CPROGRA~1IBMSQLLIBDB2hmonCacheDB20ossipcres.ftok
>
>2006-12-18-17.00.50.328000-420 I8320H245 LEVEL: Info
>PID : 3936 TID : 5240
>FUNCTION: DB2 Common, OSSe, oss_directory_delete_recursive, probe:70
>MESSAGE : ECF=0x90000019 A component of the path is not a directory
>
>2006-12-18-17.00.50.343000-420 I8567H352 LEVEL: Info (OS)
>PID : 3936 TID : 5240
>FUNCTION: DB2 Common, OSSe, OSSHIPCMemory::attach, probe:50
>MESSAGE : ECF=0x90000047 The specified memory is not found and
>IPC_CREAT
>flag is not specified.
>CALLED : OS, -, OpenFileMapping OSERR:
>ERROR_FILE_NOT_FOUND (2)
>
>
>This is DB2-express on Win-XP PRO, according to your first post on this
>topic.

Express-C, actually, and yes on Win WP Pro.

>Is this a standalone windows, or a member of a domain ?

Standalone. My home computer.

>Before you installed DB2-express on this box, was there already some
>previous installation of some flavour of db2 on the box ?

Yes, I had Express-C version 8.2 (I think).

>Were there any messages or errors during installation ?

Actually, I did have some problems, though I had version 9.1 working for
several months before this problem arose. I can't explain exactly what my
install problem was, but basically when another family member (w/o Admin
rights) logged on, it seemed to be attempting the installation again, but
got caught up in some sort of weird loop. I kept trying to cancel this
'install', but it would just restart automatically a few minutes later.
Very bizarre. I can't remember exactly what I did to get this stopped. I
think I may have uninstalled it and started over. Sounds like I'm in for
that again!

Thanks,
Frank


---
Frank Swarbrick
Senior Developer/Analyst - Mainframe Applications
FirstBank Data Corporation - Lakewood, CO USA
 >> Stay informed about: problem starting db with version 9.1