Prev: DB2 V10 and z800
Next: Question on DB2MON
From: hsn_ on 4 Jun 2010 10:47
I can not get them to work. It always fails in DDL Extract phase. Do i
need to (re)bind some package?
Error code is:
SQL2590N Po¾adovanou operaci RESTORE nebylo mo¾né dokonèit, proto¾e
do¹lo k
chybì pøenosu schématu. Kód pøíèiny: "16".

diag log is:

2010-06-04-16.21.19.718000+120 I415102H474 LEVEL: Info
PID : 3892 TID : 1428 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SYSTG001
APPHDL : 0-737 APPID: *LOCAL.DB2.100604142108
AUTHID : MAJITEL
EDUID : 1428 EDUNAME: db2agent (SYSTG001)
FUNCTION: DB2 UDB, database application extension for utili,
transport, probe:75
88
MESSAGE : Transport:Begin Extract DDL phase

2010-06-04-16.21.31.250000+120 E415578H636 LEVEL: Warning
PID : 3892 TID : 1428 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SYSTG001
APPHDL : 0-737 APPID: *LOCAL.DB2.100604142108
AUTHID : MAJITEL
EDUID : 1428 EDUNAME: db2agent (SYSTG001)
FUNCTION: DB2 UDB, data management, sqldEndNoLogList, probe:1
MESSAGE : ADM5530W The COMMIT processing of table
"SYSTOOLS.DB2LOOK_INFO" that

used NOT LOGGED INITIALLY has been initiated. It is
recommended that

you take a backup of this table's table space(s).

2010-06-04-16.21.33.468000+120 E416216H736 LEVEL: Warning
PID : 3892 TID : 1428 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SYSTG001
APPHDL : 0-737 APPID: *LOCAL.DB2.100604142108
AUTHID : MAJITEL
EDUID : 1428 EDUNAME: db2agent (SYSTG001)
FUNCTION: DB2 UDB, catcache support, sqlrlc_check_available_memory,
probe:100
MESSAGE : ADM4000W A catalog cache overflow condition has occurred.
There is
no error but this indicates that the catalog cache has
exceeded the
configured maximum size. If this condition persists, you
may want to

adjust the CATALOGCACHE_SZ DB configuration parameter.

2010-06-04-16.21.33.796000+120 I416954H529 LEVEL: Error
PID : 3892 TID : 1428 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SYSTG001
APPHDL : 0-737 APPID: *LOCAL.DB2.100604142108
AUTHID : MAJITEL
EDUID : 1428 EDUNAME: db2agent (SYSTG001)
FUNCTION: DB2 UDB, database application extension for utili,
transport_extractDD
LtoFile, probe:6083
MESSAGE : Transport:Invalid command type
DATA #1 : unsigned integer, 4 bytes
0

2010-06-04-16.21.33.812000+120 I417485H472 LEVEL: Info
PID : 3892 TID : 1428 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SYSTG001
APPHDL : 0-737 APPID: *LOCAL.DB2.100604142108
AUTHID : MAJITEL
EDUID : 1428 EDUNAME: db2agent (SYSTG001)
FUNCTION: DB2 UDB, database application extension for utili,
transport, probe:76
95
MESSAGE : Transport:End Extract DDL phase

2010-06-04-16.21.33.812000+120 I417959H594 LEVEL: Error
PID : 3892 TID : 1428 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SYSTG001
APPHDL : 0-737 APPID: *LOCAL.DB2.100604142108
AUTHID : MAJITEL
EDUID : 1428 EDUNAME: db2agent (SYSTG001)
FUNCTION: DB2 UDB, database utilities,
sqludExtractAndSaveDDLForTransport, probe
:2743
MESSAGE : SQL10007N Message "2146303891" could not be retrieved.
Reason code:

"4".
DATA #1 : String, 43 bytes
Transport: Error calling TRANSPORT(EXTRACT)

2010-06-04-16.21.33.812000+120 E418555H850 LEVEL: Severe
PID : 1832 TID : 1448 PROC : db2bp.exe
INSTANCE: DB2 NODE : 000
APPID : *LOCAL.DB2.100604142108
EDUID : 1448
FUNCTION: DB2 UDB, database utilities,
sqludTransportExtractDDLStagingDB, probe:
1183
MESSAGE : ZRC=0xFFFFF5E2=-2590
DATA #1 : String, 44 bytes
Error during transport DDL extraction phase.
DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -2590 sqlerrml: 4
sqlerrmc: 16
sqlerrp : SQL09072
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
From: Helmut Tessarek on 7 Jun 2010 15:41
Please increase the size of CATALOGCACHE_SZ. Also increase the AGENT_STACK_SZ
database manager configuration parameter to at least 128.
The default value is too low.

If this does not help, please set DIAGLEVEL to 4 and run 'db2diag -A' to clear
the log.
Run the transport operation again, zip the db2diag.log and attach it to your
next post. It might be that you will have to open a PMR. But let's go there
after I checked your next db2diag.log.

On 4.6.2010 10:47, hsn_ wrote:
> 2010-06-04-16.21.33.468000+120 E416216H736 LEVEL: Warning
> PID : 3892 TID : 1428 PROC : db2syscs.exe
> INSTANCE: DB2 NODE : 000 DB : SYSTG001
> APPHDL : 0-737 APPID: *LOCAL.DB2.100604142108
> AUTHID : MAJITEL
> EDUID : 1428 EDUNAME: db2agent (SYSTG001)
> FUNCTION: DB2 UDB, catcache support, sqlrlc_check_available_memory,
> probe:100
> MESSAGE : ADM4000W A catalog cache overflow condition has occurred.
> There is
> no error but this indicates that the catalog cache has
> exceeded the
> configured maximum size. If this condition persists, you
> may want to
>
> adjust the CATALOGCACHE_SZ DB configuration parameter.



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

/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
From: hsn_ on 8 Jun 2010 04:46
Increasing stack size didnt helped.

After setting DIAGLEVEL to 4 and deleting old diag log files, db2 does
not start anymore. I am attaching trace of db2start. It looks like
there is lock conflict on db2 diag log file. But funny thing is that
db2start is conflict with itself (pid is same, maybe thread is
different), its exclusively locked by same process which is trying to
grab lock. OS: Windows XP

http://rapidshare.com/files/396595597/db2start.zip
From: Helmut Tessarek on 8 Jun 2010 12:44
Hi,

> After setting DIAGLEVEL to 4 and deleting old diag log files, db2 does
> not start anymore. I am attaching trace of db2start. It looks like
> there is lock conflict on db2 diag log file. But funny thing is that
> db2start is conflict with itself (pid is same, maybe thread is
> different), its exclusively locked by same process which is trying to
> grab lock. OS: Windows XP

I was not able to reproduce your problem. I set diaglevel to 4 and did a
'db2diag -A'. db2stop and db2start worked without a problem.
I also deleted the db2diag.log. db2stop and db2start worked as well.

> http://rapidshare.com/files/396595597/db2start.zip

what kind of file is this? an export from the event log? a trace is done via
the db2trc program.

Anyway, I think you should open a PMR. Your problem does not make any sense to
me and I'm not a Windows person.

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

/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
From: hsn_ on 9 Jun 2010 03:09
> what kind of file is this? an export from the event log? a trace is done via
> the db2trc program.
Its CSV export from procmon. procmon is something like systrace for
windows. It records kernel calls made by application.

I am looking into our bug database and one customer had this problem
too, diaglevel 4 on windows and db2 does not start anymore.
Its timing dependant race condition - most likely 2 threads in
db2starts fights against lock on diag file. It appears on diaglevel 4
more because its needed to grab diag lock sooner due to more extensive
log output.
>
> Anyway, I think you should open a PMR. Your problem does not make any sense to
> me and I'm not a Windows person.
This error should be in unix version too, unless in unix locks are
process-wide instead of file descriptor or thread wide.
 |  Next  |  Last
Pages: 1 2
Prev: DB2 V10 and z800
Next: Question on DB2MON