Forum Stats

  • 3,875,295 Users
  • 2,266,907 Discussions
  • 7,912,141 Comments

Discussions

DB2 Extract begin now positioning delay issues

673725
673725 Member Posts: 26
edited Oct 19, 2010 10:56PM in GoldenGate
We are seeing delays starting up a (DB2 (9.5.0.3)) extract process of up to 6 hours that appear to be related to troubles with positioning itself in the DB2 transaction log when using the 'begin now' option. The extract report file will show this line:

2010-10-13 12:28:28 INFO OGG-01515 Positioning to begin time Oct 13, 2010 12:28:24 PM.

but then will only show the subsequent positioned message minutes or even hours later:

2010-10-13 12:47:30 INFO OGG-01560 Positioned to 3496288233245.

Until this positioning has finished, the extract process will not respond to ggsci commands such as attempts to stop it.

When investigating on the DB2 side, the db2diag showed these errors:

2010-10-13-12.28.28.844251-240 I203065E576 LEVEL: Warning
PID : 1707 TID : 47882228984128PROC : db2sysc 0
INSTANCE: phxinst1 NODE : 000 DB : VAP
APPHDL : 0-43653 APPID: *LOCAL.phxinst1.101013175112
AUTHID : INT33
EDUID : 28 EDUNAME: db2agent (VAP) 0
FUNCTION: DB2 UDB, recovery manager, sqlpMoveBackExtents, probe:100
MESSAGE : Log file size has changed. Guessing at log containing LSN
00000197058252CB, based on log file size 5000, calculated extent
number is 0,

2010-10-13-12.28.28.850140-240 E203642E482 LEVEL: Warning
PID : 1707 TID : 47882228984128PROC : db2sysc 0
INSTANCE: phxinst1 NODE : 000 DB : VAP
APPHDL : 0-43653 APPID: *LOCAL.phxinst1.101013175112
AUTHID : INT33
EDUID : 28 EDUNAME: db2agent (VAP) 0
FUNCTION: DB2 UDB, data protection services, sqlpALR_OpenExtent, probe:0
MESSAGE : ADM1500W DB2 is unable to locate log file "S4967295.LOG".

S4967295.LOG request appeared to be out of range compared to the LSNs showed by 'db2pd -db <dbname> -logs' (0x032F9C630000 - 0x032FA75F8000).

Any ideas?

Thanks!
Marcell

Answers

This discussion has been closed.