Transportable tablespaces in 9.7.2

#11

Quote:

db2pd requires instance started:
C:\IBM\SQLLIB\BIN>db2pd -stack all
Unable to attach to database manager. Please ensure db2start has been
run.

Yes, you are right. Totally forgot about that.

Quote:

but db2start hangs before instance is fully started so db2pd probably
wait until db2 finishes its startup sequence. If you want i can
procmon db2pd to see what it is waiting for.

No, that's ok.

Quote:

If db2diag.0.log is longer than 0 bytes than it starts successfully.

At least there is a workaround. You always can add some characters to the
file... :-)

Quote:

I tried it, but I'm still not able to reproduce it. But I tried it on Win32.
my os is windows xp 32 bit

I also tried it on WinXP 32bit with DB2 9.7.2.

Quote:

Úroveò zachycení diagnostických chyb (DIAGLEVEL) = 3
Úroveò upozornìní (NOTIFYLEVEL) = 3
Cesta adresáøe diagnostických údajù (DIAGPATH) =
Velikost rotujícího ¾urnálu db2diag a ¾urnálu upozornìní (MB)
(DIAGSIZE) = 20

Hmm, I am using my own diagpath (d:\db2dump). I also removed my diagpath value
and tried to reproduce the problem again. Without success.

Quote:

you can send him this report anyway he might be able to find what is
going on. This depends on logfile size >0. It is not tied to logrotate
function because it hangs with (diagsize 0) too.

I can send him this report, but if he is not able to reproduce the problem,
then I doubt that he can do something. I've been trying it now on 3 different
OS with 4 different DB2 versions/releases.
I have not been able to reproduce the problem even once.

--
Helmut K. C. Tessarek
DB2 Performance and Development

/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/

#12

Quote:

I tried it, but I'm still not able to reproduce it. But I tried it on Win32.
my os is windows xp 32 bit SP3
dont waste your time on trying to re-create it issue, i found root

cause. Its simple to fix as you can see from procmon traces. Root
cause is pretty simple as you can see from my procmon trace.
http://rapidshare.com/files/397732121/Logfile.PML
its trace from db2 instance stopped, just db2dasstm running. it nicely
illustrates error. At beginning of capture, there is existing
db2diag.log file and everything is running smoothly. In middle i
deleted diag log fail and suddenly we see that it is started to fail.
You can look what happened. Wrong sequence is following.

queryopen
queryopen
createFile - creates new 0 bytes long file
lockFile offset 0, length 1, exclusive, dontwait. Fails because file
is zero sized and you cant lock 1 byte range on zero sized file.

Procedure for diag file locking needs to be changed. probably best way
will be to use file-wide locks instead of range locks, or query file
size before using range lock.

#13

same problem with 1 byte long lock on 0 sized file is on file
".db2diag.rotate.lck". It needs to be 1 byte long to make it work.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Transportable tablespaces in 9.7.2

comp.databases.ibm-db2 comp.databases.ibm-db2

Re: db2 hangs with diaglevel 4 on startup if log files are deleted - 06-10-2010 , 01:23 PM

Re: db2 hangs with diaglevel 4 on startup if log files are deleted - 06-11-2010 , 05:11 AM

Re: db2 hangs with diaglevel 4 on startup if log files are deleted - 06-16-2010 , 01:05 PM