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

Restoring Journals on an iSeries Box

P: n/a
I restored my DB2 journals from a primary AS/400 to a backup AS/400 and want
to replay the journals for recovery purposes, I discovered that the chain
link was broken jumping from one receiver to the other, is there a quick and
easy way not to break the link? Also, does it have to do something with the
ASP that it is in? It is in ASP1 by default and was not restored in ASP1 on
the secondary box.

Any help will be appreciated.

Thanks,

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


P: n/a
RdR
Hi QSECOFR,

Based on the information you gave, I believe you really do not have "broken
chains" even if you see journal receivers not in sequence. First of all,
when you restore journals from one machine to another, the journal receiver
names and its sequence numbers may be different from the original names in
the original machine. And it is also common that when a receiver name or
sequence number reaches its max (meaning no other number higher but to go
back to zero), then this is where the :broken chains" seem to appear. Just
to be on the safe side, do a wrkjrnrcv command or a wrkjrna command, and
look at each journal receiver, each receiver should have a beggining and
ending sequence number. I am quite sure that one of the receivers that
appears to have a "broken chain" or the one that you think has a broken
chain will point to an ending sequence number which may not follow the
original sequence or to another journal receiver with a number that appears
to break the chain. And to further confirm this, look in your QAUDJRN any
references to a CHGJRN command with a RESET on it and most probably point to
the receiver that seems to have broken the chain.

Seems like you are using a tool to replay the journals, if ever there is
really a broken link, see if this tool has a "Set Journal Position" utility
so that you can continue from where you left off if ever there is small
chance that you have Journal Corruption (WRKJRNA will show this too).

Hope this helps,

RdR
"QSECOFR" <jo*********@midrange.com> wrote in message
news:8K******************@nnrp1.uunet.ca...
I restored my DB2 journals from a primary AS/400 to a backup AS/400 and want to replay the journals for recovery purposes, I discovered that the chain
link was broken jumping from one receiver to the other, is there a quick and easy way not to break the link? Also, does it have to do something with the ASP that it is in? It is in ASP1 by default and was not restored in ASP1 on the secondary box.

Any help will be appreciated.

Thanks,

QSECOFR

Nov 12 '05 #2

P: n/a
RdR
Hi QSECOFR,

About the ASP (Auxiliary Storage Pool), that does not matter if you are
OS/400 Version 4.x and above, I do not think restoring to a different ASP
will matter because the journal attributes should point to the correct ASP.
I do not think that has anything to do with the broken journal receiver
chains.

RdR
"QSECOFR" <jo*********@midrange.com> wrote in message
news:8K******************@nnrp1.uunet.ca...
I restored my DB2 journals from a primary AS/400 to a backup AS/400 and want to replay the journals for recovery purposes, I discovered that the chain
link was broken jumping from one receiver to the other, is there a quick and easy way not to break the link? Also, does it have to do something with the ASP that it is in? It is in ASP1 by default and was not restored in ASP1 on the secondary box.

Any help will be appreciated.

Thanks,

QSECOFR

Nov 12 '05 #3

P: n/a
Hi RdR,

Thanks for all the help, you were right, that just saved me hours and hours
of trying to fix a problem which is really not a problem. I appreciate it
very much. Thanks so much.

John
"RdR" <ro*@delrosario.ca> wrote in message
news:oN********************@rogers.com...
Hi QSECOFR,

About the ASP (Auxiliary Storage Pool), that does not matter if you are
OS/400 Version 4.x and above, I do not think restoring to a different ASP
will matter because the journal attributes should point to the correct
ASP.
I do not think that has anything to do with the broken journal receiver
chains.

RdR
"QSECOFR" <jo*********@midrange.com> wrote in message
news:8K******************@nnrp1.uunet.ca...
I restored my DB2 journals from a primary AS/400 to a backup AS/400 and

want
to replay the journals for recovery purposes, I discovered that the chain
link was broken jumping from one receiver to the other, is there a quick

and
easy way not to break the link? Also, does it have to do something with

the
ASP that it is in? It is in ASP1 by default and was not restored in ASP1

on
the secondary box.

Any help will be appreciated.

Thanks,

QSECOFR


Nov 12 '05 #4

P: n/a
Hi RdR,

Thanks for all the help, you were right, that just saved me hours and hours
of trying to fix a problem which is really not a problem. I appreciate it
very much. Thanks so much.

John

"RdR" <ro*@delrosario.ca> wrote in message
news:oo********************@rogers.com...
Hi QSECOFR,

Based on the information you gave, I believe you really do not have
"broken
chains" even if you see journal receivers not in sequence. First of all,
when you restore journals from one machine to another, the journal
receiver
names and its sequence numbers may be different from the original names in
the original machine. And it is also common that when a receiver name or
sequence number reaches its max (meaning no other number higher but to go
back to zero), then this is where the :broken chains" seem to appear. Just
to be on the safe side, do a wrkjrnrcv command or a wrkjrna command, and
look at each journal receiver, each receiver should have a beggining and
ending sequence number. I am quite sure that one of the receivers that
appears to have a "broken chain" or the one that you think has a broken
chain will point to an ending sequence number which may not follow the
original sequence or to another journal receiver with a number that
appears
to break the chain. And to further confirm this, look in your QAUDJRN any
references to a CHGJRN command with a RESET on it and most probably point
to
the receiver that seems to have broken the chain.

Seems like you are using a tool to replay the journals, if ever there is
really a broken link, see if this tool has a "Set Journal Position"
utility
so that you can continue from where you left off if ever there is small
chance that you have Journal Corruption (WRKJRNA will show this too).

Hope this helps,

RdR
"QSECOFR" <jo*********@midrange.com> wrote in message
news:8K******************@nnrp1.uunet.ca...
I restored my DB2 journals from a primary AS/400 to a backup AS/400 and

want
to replay the journals for recovery purposes, I discovered that the chain
link was broken jumping from one receiver to the other, is there a quick

and
easy way not to break the link? Also, does it have to do something with

the
ASP that it is in? It is in ASP1 by default and was not restored in ASP1

on
the secondary box.

Any help will be appreciated.

Thanks,

QSECOFR


Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.