dbaspot
Tags Register FAQ Calendar Search Today's Posts Mark Forums Read

EEXIST (17) "Do not specify an existing file." - db2-udb

This is a discussion on EEXIST (17) "Do not specify an existing file." - db2-udb ; Dear All, Anyone help out me in this issue. Below I copied the completed db2diag.log detail. Here it is giving the Level : Warning (OS). For this type of issue from where i can get help any Manual as reference.... ...


Home > Database Forum > Other Databases > db2-udb > EEXIST (17) "Do not specify an existing file."

Reply

 

LinkBack Thread Tools Display Modes
  #1  
Old 06-09-2009, 11:06 PM
Database Newbie
 
Join Date: Jun 2009
Posts: 1
abbas118 is on a distinguished road
Red face EEXIST (17) "Do not specify an existing file."

Dear All,

Anyone help out me in this issue. Below I copied the completed db2diag.log detail. Here it is giving the Level : Warning (OS). For this type of issue from where i can get help any Manual as reference....

2009-06-02-09.00.17.964553+480 I1C1089 LEVEL: Event
PID : 1417272 TID : 1 PROC : db2start
INSTANCE: db2kki NODE : 000
FUNCTION: DB2 UDB, RAS/PD component, _pdlogInt, probe:120
START : New db2diag.log file
DATA #1 : Build Level, 124 bytes
Instance "db2kki" uses "32" bits and DB2 code release "SQL08027"
with level identifier "03080106".
Informational tokens are "DB2 v8.1.1.128", "s061108", "U810098", FixPak "14".
DATA #2 : System Info, 220 bytes
System: AIX Kekukur 3 5 00C485EE4C00
CPU: total:20 online:8 Threading degree per core:2
Physical Memory(MB): total:12288 free:4596
Virtual Memory(MB): total:25088 free:16749
Swap Memory(MB): total:12800 free:12153
Kernel Params: msgMaxMessageSize:4194304 msgMaxQueueSize:4194304
shmMax:2147483648 shmMin:1 shmIDs:131072 shmSegments:16
semIDs:131072 semNumPerID:65535 semOps:1024 semMaxVal:32767
semAdjustOnExit:16384
Information in this record is only valid at the time when this file was
created (see this record's time stamp)

2009-06-02-09.00.17.963872+480 I1091C1508 LEVEL: Event
PID : 1417272 TID : 1 PROC : db2start
INSTANCE: db2kki NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
DATA #1 : String, 37 bytes
/pki/users/db2kki/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0x2FF1D748 : 2F70 6B69 2F75 7365 7273 2F64 6232 706B /pki/users/db2pk
0x2FF1D758 : 692F 7371 6C6C 6962 2F61 646D 2F64 6232 i/sqllib/adm/db2
0x2FF1D768 : 7374 6172 3200 4E4F 4D53 4700 0000 0000 star2.NOMSG.....
0x2FF1D778 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF1D788 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF1D798 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF1D7A8 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF1D7B8 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF1D7C8 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF1D7D8 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF1D7E8 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF1D7F8 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF1D808 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF1D818 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF1D828 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF1D838 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2009-06-02-09.00.19.833921+480 E2600C431 LEVEL: Warning (OS)
PID : 712740 TID : 1 PROC : db2spmrsy 0
INSTANCE: db2kki NODE : 000
APPHDL : 0-6
FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80
CALLED : OS, -, unspecified_system_function
OSERR : EEXIST (17) "Do not specify an existing file."
DATA #1 : File name, 42 bytes
/pki/users/db2kki/sqllib/spmlog/SPMLOG.LCF

2009-06-02-09.00.19.886828+480 E3032C1020 LEVEL: Event
PID : 1282198 TID : 1 PROC : db2star2
INSTANCE: db2kki NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
MESSAGE : ADM7513W Database manager has started.
START : DB2 DBM
DATA #1 : Build Level, 124 bytes
Instance "db2kki" uses "32" bits and DB2 code release "SQL08027"
with level identifier "03080106".
Informational tokens are "DB2 v8.1.1.128", "s061108", "U810098", FixPak "14".
DATA #2 : System Info, 220 bytes
System: AIX Tekukur 3 5 00C485EE4C00
CPU: total:20 online:8 Threading degree per core:2
Physical Memory(MB): total:12288 free:4484
Virtual Memory(MB): total:25088 free:16636
Swap Memory(MB): total:12800 free:12152
Kernel Params: msgMaxMessageSize:4194304 msgMaxQueueSize:4194304
shmMax:2147483648 shmMin:1 shmIDs:131072 shmSegments:16
semIDs:131072 semNumPerID:65535 semOps:1024 semMaxVal:32767
semAdjustOnExit:16384

2009-06-02-09.04.20.450345+480 I4053C370 LEVEL: Warning
PID : 1196202 TID : 1 PROC : db2agent (CERTCRDB) 0
INSTANCE: db2kki NODE : 000 Database : CERTCRDB
APPHDL : 0-25 APPID: GA0A0AF7.OB19.090602010420
FUNCTION: DB2 UDB, base sys utilities, sqledint, probe:30
MESSAGE : Crash Recovery is needed.

2009-06-02-09.04.20.567461+480 I4424C433 LEVEL: Warning
PID : 1196202 TID : 1 PROC : db2agent (CERTCRDB) 0
INSTANCE: db2kki NODE : 000 DB : CERTCRDB
APPHDL : 0-25 APPID: GA0A0AF7.OB19.090602010420
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410
MESSAGE : Crash recovery started. LowtranLSN 000000186FA0B2F2 MinbuffLSN
000000186F8082BB

2009-06-02-09.04.20.568908+480 I4858C412 LEVEL: Warning
PID : 1196202 TID : 1 PROC : db2agent (CERTCRDB) 0
INSTANCE: db2kki NODE : 000 DB : CERTCRDB
APPHDL : 0-25 APPID: GA0A0AF7.OB19.090602010420
FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:2000
MESSAGE : Using parallel recovery with 9 agents 5 QSets 40 queues and 2 chunks

2009-06-02-09.04.20.589423+480 I5271C402 LEVEL: Warning
PID : 528628 TID : 1 PROC : db2redom (CERTCRDB) 0
INSTANCE: db2kki NODE : 000 DB : CERTCRDB
APPHDL : 0-25 APPID: GA0A0AF7.OB19.090602010420
FUNCTION: DB2 UDB, recovery manager, sqlpParallelRecovery, probe:880
MESSAGE : Resetting max shredder memory to 0 from 3243926

2009-06-02-09.04.21.417646+480 I5674C443 LEVEL: Warning
PID : 1196202 TID : 1 PROC : db2agent (CERTCRDB) 0
INSTANCE: db2kki NODE : 000 DB : CERTCRDB
APPHDL : 0-25 APPID: GA0A0AF7.OB19.090602010420
FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:4000
MESSAGE : DIA2051W Forward phase of crash recovery has completed. Next LSN is
"000000186FB98795".

2009-06-02-09.04.21.465330+480 I6118C398 LEVEL: Warning
PID : 1196202 TID : 1 PROC : db2agent (CERTCRDB) 0
INSTANCE: db2kki NODE : 000 DB : CERTCRDB
APPHDL : 0-25 APPID: GA0A0AF7.OB19.090602010420
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:3170
MESSAGE : Crash recovery completed. Next LSN is 000000186FB98795

2009-06-02-09.09.06.778049+480 I6517C363 LEVEL: Warning
PID : 1380380 TID : 1 PROC : db2loggr (CERTCRDB) 0
INSTANCE: db2kki NODE : 000 DB : CERTCRDB
FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1390
MESSAGE : ExtNum 24435, state 401, baselsn 000000186F9D8000 nextlsn
000000186FBE4FDE

2009-06-02-09.28.39.854625+480 I6881C363 LEVEL: Warning
PID : 1343722 TID : 1 PROC : db2loggr (CERTCRDB) 0
INSTANCE: db2kki NODE : 000 DB : CERTCRDB
FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1390
MESSAGE : ExtNum 24436, state 401, baselsn 000000186FDC0000 nextlsn
000000186FDF26AB

2009-06-02-09.34.59.019623+480 I7245C363 LEVEL: Warning
PID : 1298558 TID : 1 PROC : db2loggr (CERTCRDB) 0
INSTANCE: db2kki NODE : 000 DB : CERTCRDB
FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1390
MESSAGE : ExtNum 24437, state 401, baselsn 00000018701A8000 nextlsn
00000018701ED2BE

2009-06-02-10.03.39.834512+480 I7609C363 LEVEL: Warning
PID : 1454132 TID : 1 PROC : db2loggr (CERTCRDB) 0
INSTANCE: db2kki NODE : 000 DB : CERTCRDB
FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1390
MESSAGE : ExtNum 24438, state 401, baselsn 0000001870590000 nextlsn
00000018705A4894

2009-06-02-10.14.07.007441+480 I7973C363 LEVEL: Warning
PID : 1523786 TID : 1 PROC : db2loggr (CERTCRDB) 0
INSTANCE: db2kki NODE : 000 DB : CERTCRDB
FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1390
MESSAGE : ExtNum 24439, state 401, baselsn 0000001870978000 nextlsn
00000018709BD644
Reply With Quote
Reply

Thread Tools
Display Modes



All times are GMT -4. The time now is 03:32 AM.