By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,334 Members | 1,290 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,334 IT Pros & Developers. It's quick & easy.

LOGARCHMETH1 TSM logarchopt1 db2uext2

P: n/a
Hi,

I was trying to do the following:

update db cfg for oltprd using VENDOROPT "'-SErvername=aixstl20'"
update db cfg for oltprd using LOGARCHMETH1 TSM
update db cfg for oltprd using logarchopt1 "'-SErvername=aixstl20'"
rollforward db oltprd to end of logs

and received the following:

SQL1268N Roll-forward recovery stopped due to error "SQL1042" while
retrieving log file "S0006926.LOG" for database "OLTPRD" on node "0".

I thought the issue may be with db2uext2 exit. Looking at the code I
can't see how the information is past to the db2uext2. Is it used in
this scenario? If so how is the information pasted and is there a new
sample. If not why does the option work for the restore command but I
am having trouble with the rollforward.

thanks for any help.

Peter

Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Ian
Peter wrote:
Hi,

I was trying to do the following:

update db cfg for oltprd using VENDOROPT "'-SErvername=aixstl20'"
update db cfg for oltprd using LOGARCHMETH1 TSM
update db cfg for oltprd using logarchopt1 "'-SErvername=aixstl20'"
rollforward db oltprd to end of logs

and received the following:

SQL1268N Roll-forward recovery stopped due to error "SQL1042" while
retrieving log file "S0006926.LOG" for database "OLTPRD" on node "0".

I thought the issue may be with db2uext2 exit. Looking at the code I
can't see how the information is past to the db2uext2. Is it used in
this scenario? If so how is the information pasted and is there a new
sample. If not why does the option work for the restore command but I
am having trouble with the rollforward.


The userexit program (db2uext2) is not used with LOGARCHMETH1 = TSM.

Also, the -servername option is only required if you are pulling log
files from an alternate TSM server (i.e. your log files are getting
sent to a TSM server other than the default defined in dsm.sys or
dsm.opt).
That said, SQL1042C is a more serious error (not something as simple as
"log file not found". You need to investigate further (what shows up in
your db2diag.log)?

Nov 12 '05 #2

P: n/a
I am getting the image and logs from a different server, hence tje
-servername command.

Worked with the restore but with the rollfward it failed. Hence my
questions. Did look in dn2diag.log and it had the following
2005-10-25-13.49.12.549330+600 E82525C388 LEVEL: Warning
PID : 1622238 TID : 1 PROC : db2agent
(OLTPRD)
INSTANCE: db2inst1 NODE : 000 DB : OLTPRD
APPHDL : 0-126 APPID: *LOCAL.db2inst1.051025034907
FUNCTION: DB2 UDB, data protection, sqlufrol, probe:980
MESSAGE : ADM1602W Rollforward recovery has been initiated.

2005-10-25-13.49.12.550487+600 E82914C431 LEVEL: Warning
PID : 1622238 TID : 1 PROC : db2agent
(OLTPRD)
INSTANCE: db2inst1 NODE : 000 DB : OLTPRD
APPHDL : 0-126 APPID: *LOCAL.db2inst1.051025034907
FUNCTION: DB2 UDB, data protection, sqlufrol, probe:1210
MESSAGE : ADM1603I DB2 is invoking the forward phase of the database
rollforward recovery.

2005-10-25-13.49.12.570631+600 I83346C471 LEVEL: Warning
PID : 1622238 TID : 1 PROC : db2agent
(OLTPRD)
INSTANCE: db2inst1 NODE : 000 DB : OLTPRD
APPHDL : 0-126 APPID: *LOCAL.db2inst1.051025034907
FUNCTION: DB2 UDB, recovery manager, sqlpForwardRecovery, probe:720
DATA #1 : String, 103 bytes
Invoking database rollforward forward recovery,
lowtranlsn 000000069E29163F minbufflsn 000000069E28AA79

2005-10-25-13.49.12.798993+600 I83818C410 LEVEL: Warning
PID : 1622238 TID : 1 PROC : db2agent
(OLTPRD)
INSTANCE: db2inst1 NODE : 000 DB : OLTPRD
APPHDL : 0-126 APPID: *LOCAL.db2inst1.051025034907
FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:2000
MESSAGE : Using parallel recovery with 3 agents 61 QSets 183 queues and
2 chunks

2005-10-25-13.49.12.865178+600 I84229C398 LEVEL: Warning
PID : 1319050 TID : 1 PROC : db2redom
(OLTPRD)
INSTANCE: db2inst1 NODE : 000 DB : OLTPRD
APPHDL : 0-126 APPID: *LOCAL.db2inst1.051025034907
FUNCTION: DB2 UDB, recovery manager, sqlpParallelRecovery, probe:880
MESSAGE : Resetting max shredder memory to 2796914 from 0

2005-10-25-13.49.13.467188+600 I84628C325 LEVEL: Warning
PID : 1491148 TID : 1 PROC : db2logmgr
(OLTPRD)
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgRetrieveLogFile, probe:4180
MESSAGE : Log file 6926 on chain 0 retrieved successfully from
USEREXIT.

2005-10-25-13.49.13.468235+600 I84954C366 LEVEL: Error
PID : 1638440 TID : 1 PROC : db2lfr
(OLTPRD)
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, recovery manager, sqlplfrOpenExtentRetrieve,
probe:210
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.

2005-10-25-13.49.13.512907+600 I85321C295 LEVEL: Warning
PID : 1548292 TID : 1 PROC : db2loggr
(OLTPRD)
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, recovery manager, sqlpgSwitchFromRedoToUndo,
probe:1840
MESSAGE : Retrieving log extent 6926.

2005-10-25-13.49.13.802664+600 I85617C325 LEVEL: Warning
PID : 1491148 TID : 1 PROC : db2logmgr
(OLTPRD)
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgRetrieveLogFile, probe:4180
MESSAGE : Log file 6926 on chain 0 retrieved successfully from
USEREXIT.

2005-10-25-13.49.13.803077+600 I85943C348 LEVEL: Error
PID : 1548292 TID : 1 PROC : db2loggr
(OLTPRD)
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, recovery manager, sqlpgSwitchFromRedoToUndo,
probe:1870
MESSAGE : rc -2045837302 when trying to open log extent 6926, index 0
TailIndex
0

2005-10-25-13.49.13.808996+600 I86292C335 LEVEL: Error
PID : 1548292 TID : 1 PROC : db2loggr
(OLTPRD)
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, recovery manager, sqlpgSwitchFromRedoToUndo,
probe:1871
MESSAGE : startOfCurFileLsn: 000000069E17800C,logfhdr.nextLsn:
000000069E28AA79

2005-10-25-13.49.13.809236+600 I86628C338 LEVEL: Error
PID : 1548292 TID : 1 PROC : db2loggr
(OLTPRD)
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgasn, probe:650
RETCODE : ZRC=0x801000BB=-2146434885=SQLPR_MISSING_LOGFILES
"rollforward missing log files"

2005-10-25-13.49.13.826140+600 I86967C399 LEVEL: Error
PID : 1319050 TID : 1 PROC : db2redom
(OLTPRD)
INSTANCE: db2inst1 NODE : 000 DB : OLTPRD
APPHDL : 0-126 APPID: *LOCAL.db2inst1.051025034907
FUNCTION: DB2 UDB, data protection, sqlpgPostLoggrWithoutLatching,
probe:930
MESSAGE : db2logger: rc=-2146434885 sem rc=0 type=27

2005-10-25-13.49.13.826552+600 I87367C160 LEVEL: Error
PID:1319050 TID:1 NODE:000 Title: SQLP_DBCB
Dump File:/home/db2inst1/sqllib/db2dump/13190501.000

2005-10-25-13.49.13.856935+600 I87528C436 LEVEL: Error
PID : 1319050 TID : 1 PROC : db2redom
(OLTPRD)
INSTANCE: db2inst1 NODE : 000 DB : OLTPRD
APPHDL : 0-126 APPID: *LOCAL.db2inst1.051025034907
FUNCTION: DB2 UDB, recovery manager, sqlpPRecReadLog, probe:3980
RETCODE : ZRC=0x801000BB=-2146434885=SQLPR_MISSING_LOGFILES
"rollforward missing log files"

2005-10-25-13.49.13.885745+600 I87965C439 LEVEL: Error
PID : 1622238 TID : 1 PROC : db2agent
(OLTPRD)
INSTANCE: db2inst1 NODE : 000 DB : OLTPRD
APPHDL : 0-126 APPID: *LOCAL.db2inst1.051025034907
FUNCTION: DB2 UDB, recovery manager, sqlprDoForwardPhase, probe:330
RETCODE : ZRC=0x801000BB=-2146434885=SQLPR_MISSING_LOGFILES
"rollforward missing log files"

2005-10-25-13.49.13.886227+600 I88405C440 LEVEL: Error
PID : 1622238 TID : 1 PROC : db2agent
(OLTPRD)
INSTANCE: db2inst1 NODE : 000 DB : OLTPRD
APPHDL : 0-126 APPID: *LOCAL.db2inst1.051025034907
FUNCTION: DB2 UDB, recovery manager, sqlpForwardRecovery, probe:1230
RETCODE : ZRC=0x801000BB=-2146434885=SQLPR_MISSING_LOGFILES
"rollforward missing log files"

Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.