Ansicht
Dokumentation
00744 - Need APYJRNCHG assistance...Disaster recovery
BAL_S_LOG - Application Log: Log header data PERFORM Short ReferenceThis documentation is copyright by SAP AG.
Need APYJRNCHG assistance...Disaster recovery
Hi Robert,here is one document I made myself for such emergency cases:
(when you need more help, please send an e-mail, then I will respond via
phone. I'm currently in Palo Alto, CA.)
APY-/RMVJRNCHG-Command
(Journal, journaling, Commit-Control, Rollback)
The redbook covers this at: chapter 8.7.5.2
This currently doesn't work in the version 02 but will be enhenced in the
next release.
How to use APYJRNCHG ?
APYJRNCHG JRN(R3<SID>DATA/QSQJRN) FILE((*ALL)) RCVRNG(R3<SID>DATA/From-RCV
R3SIDDATA/To-RCV) FROMENT(From-Entry) TOENT(To-Entry) CMTBDY(*YES)
From-RCV: This is the first receiver, that is used (the receiver, where the
first entry is in); this is the first receiver.
To-RCV: This is the last receiver, that is used (the receiver, where the
last entry is in) ; this is the last receiver.
From-Entry: Use really a fixed (and correct !) entry and not *LASTSAVE or
similar things. This mostly fails due to some things I don't know. So,
figure out, where you do want to start and use this entry.
To-Entry: Use really a fixed (and correct !) entry and not *LAST or similar
things. This mostly fails due to some things I don't know. So, figure out,
where you do want to end with the applying.
The Commit-Boundary is absolutely necessary for R3, because otherwise, the
system will be inconsistent afterwards!
You really should keep in mind, that here are the from- and to-parameters
completely changed to the RMVJRNCHG!
How to use RMVJRNCHG ?
RMVJRNCHG JRN(R3<SID>DATA/QSQJRN) FILE((*ALL)) RCVRNG(R3<SID>DATA/From-RCV
R3SIDDATA/To-RCV) FROMENT(From-Entry) TOENT(To-Entry) CMTBDY(*YES)
From-RCV: This is the first receiver, that is used (the receiver, where the
first entry is in) ; this is the last receiver.
To-RCV: This is the last receiver, that is used (the receiver, where the
last entry is in) ; this is the first receiver.
From-Entry: Use really a fixed (and correct !) entry and not *LASTSAVE or
similar things. This mostly fails due to some things I don't know. So,
figure out, where you do want to start and use this entry.
To-Entry: Use really a fixed (and correct !) entry and not *LAST or similar
things. This mostly fails due to some things I don't know. So, figure out,
where you do want to end with the applying.
The Commit-Boundary is absolutely necessary for R3, because otherwise, the
system will be inconsistent afterwards!
You really should keep in mind, that here are the from- and to-parameters
completely changed to the APYJRNCHG!
One example, how a real recovocery could happen, when you try to restore an
old backup and then to use APYJRNCHG
Complete Restore of the database: (normally with user QSECOFR!)
- Check the systemvalue QJOBMSGQFL. It should be on *WRAP or *PRTWRAP! No ?
=> Change it, signoff and logon again!
- CHGJOB JOBMSGQFL(*PRTWRAP)
- Check with DSPJRN, if there are in the recovery timeframe no "bad" F
Codes!
DSPJRN JRN(R3SIDDATA/QSQJRN) RCVRNG(R3SIDJRN/QSQJRN3038
R3SIDJRN/QSQJRN3041)
FROMTIME(15082000 235000) JRNCDE((F))
- clrlib r3siddata
- Stop all processes, that do still have locks on the lib R3SIDDATA
( WRKOBJLCK OBJ(R3SIDDATA) OBJTYPE(*LIB) )
- dltlib r3SIDdata
- RSTLIB SAVLIB(R3SIDDATA) DEV(TAP01) MBROPT(*ALL) ALWOBJDIF(*ALL)
or
SBMJOB CMD(RSTLIB SAVLIB(R3SIDDATA) DEV(TAP01) MBROPT(*ALL)
ALWOBJDIF(*ALL))
JOB(RSTLIB) LOG(*JOBD *JOBD *MSG) JOBMSGQFL(*PRTWRAP)
- DLTR3PKG SID(SID) PKGTYPE(*ALL) (with SIDOFR!)
or
SBMJOB CMD(DLTR3PKG SID(SID) PKGTYPE(*ALL)) JOB(DLTSQLPKG) JOBQ(QS36EVOKE)
(This can be done already during the RSTLIB in order to save time!)
- Investigate what *JRNRCVs are necessary for the recovery-timeframe:
DSPLIB R3SIDJRN
Then search with option 8 the start point of time of each *JRNRCV:
Search with option 8 for that start point of time, that is the last one
before the backup (QSQJRNfirst) and search
for the last one before the crash point of time (QSQJRNlast). These are
your 2 *JRNRCV, that will be used later
on for the first and the last *JRNRCV.
(This can be done already during the RSTLIB in order to save time!)
- Now the "old" Journalreceiver have to reattached to thew new restored
Journal in lib R3SIDDATA with the
command WRKJRN + Enter
Then you should select in the next screen QSQJRN as journal and R3SIDDATA
as Lib. Use Option 9 in order
to reattach the old receiver to the journal. Otherwise the command
APYJRNCHG will fail afterwards!!!
(This can be done already during the RSTLIB in order to save time?)
- Find out the from-sequencenumber:
DSPJRN JRN(R3SIDDATA/QSQJRN) RCVRNG(R3SIDJRN/QSQJRNfirst
R3SIDJRN/QSQJRNlast) FROMTIME(backup time)
Scroll as far, as the backup starts. When you did a "save while active"
backup, please use the sequence-number
of the F Code SS, that indicates the commit point during your backup!
- Find out the to-sequencenumber:
DSPJRN JRN(R3SIDDATA/QSQJRN) RCVRNG(R3SIDJRN/QSQJRNlast
R3SIDJRN/QSQJRNlast) FROMTIME(crash time)
Select one sequencenumber, that is in the timeframe before your crash!
- Issuing of the APYJRNCHG:
APYJRNCHG JRN(R3SIDDATA/QSQJRN) FILE((R3SIDDATA/*ALL *ALL))
RCVRNG(R3SIDJRN/QSQJRNfirst R3SIDJRN/QSQJRNlast)
FROMENT(from entry) TOENT(to entry) CMTBDY(*YES)
- Now, at the end, please check the authority of your database:
EDTOBJAUT R3SIDDATA *LIB
Then, please grant SAP00/SID00 the *CHANGE authority (F6) and compare the
result wioth one of your other
systems in order to adjust it to the correct values!
- STARTSAP (with SIDOFR)
What Journal-entries are generating problems during APY- or RMVJRNCHG ?
(AS/400e series, Backup and Recovery, Version 4, Document Number
SC41-5304-02)
6.3.10.7 Actions of the APYJRNCHG or RMVJRNCHG Command by Journal Code
Table 25-2 in topic 6.3.10.7 shows the actions that are taken by the
APYJRNCHG or RMVJRNCHG command by journal code and entry type. If All is
specified for the Entry Type, it indicates that all entry types for that
journal code have the specified actions taken by the APYJRNCHG or
RMVJRNCHG command.
+------------------------------------------------------------------------+
¦ Table 25-2. Actions by Journal Code and Entry Type ¦
+------------------------------------------------------------------------¦
¦ Journal ¦ ¦ ¦ ¦
¦ Entry ¦ ¦ ¦ ¦
+--------------+----------------------+------------------+---------------¦
¦ Code ¦ Type ¦ Operation ¦ APYJRNCHG ¦ RMVJRNCHG ¦
+------+-------+----------------------+------------------+---------------¦
¦ A ¦ All ¦ ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ C ¦ All ¦ ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ D ¦ All ¦ ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ AY ¦ Journaled changes ¦ Ends ¦ Ends ¦
¦ ¦ ¦ applied ¦ ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ CE ¦ Change end of data ¦ Member end of ¦ Ends ¦
¦ ¦ ¦ ¦ data changed(2) ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ CL ¦ Member closed ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ CH ¦ File changed ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ CR ¦ Member cleared ¦ Member cleared ¦ Ends ¦
¦ ¦ ¦ ¦ of all ¦ ¦
¦ ¦ ¦ ¦ records(2) ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ DE ¦ Member deleted ¦ Ignores ¦ Ignores ¦
¦ ¦ ¦ record count ¦ ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ EJ ¦ End journaling ¦ Ends ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ EP ¦ End journaling ¦ Ignores ¦ Ignores ¦
¦ ¦ ¦ access paths ¦ ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ FD ¦ Member forced to ¦ Ignores ¦ Ignores ¦
¦ ¦ ¦ auxiliary storage ¦ ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ FI ¦ Internal format ¦ Ignores ¦ Ignores ¦
¦ ¦ ¦ information ¦ ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ IU ¦ Object ¦ Ignores ¦ Ignores ¦
¦ ¦ ¦ synchronized(1) ¦ ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ IU ¦ Object not ¦ Ends ¦ Ends ¦
¦ ¦ ¦ synchronized(1) ¦ ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ IZ ¦ Member initialized ¦ Initialized ¦ Initialized ¦
¦ ¦ ¦ ¦ records inserted ¦ records ¦
¦ ¦ ¦ ¦ in member ¦ deleted from ¦
¦ ¦ ¦ ¦ ¦ member ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ JM ¦ Start journaling ¦ Ignores ¦ Ends ¦
¦ ¦ ¦ member ¦ ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ JP ¦ Start journaling ¦ Ignores ¦ Ignores ¦
¦ ¦ ¦ access paths ¦ ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ MD ¦ Member deleted ¦ Ends ¦ Ends ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ MF ¦ Member saved with ¦ Ends ¦ Ends ¦
¦ ¦ ¦ storage freed ¦ ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ MM ¦ Member moved ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ MN ¦ Member renamed ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ MR ¦ Member restored ¦ Ends ¦ Ends ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ MS ¦ Member saved ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ OP ¦ Member opened ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ PD ¦ Access path deleted ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ PM ¦ Logical owning ¦ Ignores ¦ Ignores ¦
¦ ¦ ¦ member of access ¦ ¦ ¦
¦ ¦ ¦ path moved ¦ ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ PN ¦ Logical owning ¦ Ignores ¦ Ignores ¦
¦ ¦ ¦ member of access ¦ ¦ ¦
¦ ¦ ¦ path renamed ¦ ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ RC ¦ Journaled changes ¦ Ends ¦ Ends ¦
¦ ¦ ¦ removed ¦ ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ RG ¦ Member reorganized ¦ Ends ¦ Ends ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ SA ¦ Start of APYJRNCHG ¦ Ends ¦ Ends ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ SR ¦ Start of RMVJRNCHG ¦ Ends ¦ Ends ¦
+------+-------+----------------------+------------------+---------------¦
¦ F ¦ SS ¦ Start of save active ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ I ¦ All ¦ ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ J ¦ All ¦ ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ L ¦ All ¦ ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ M ¦ All ¦ ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ O ¦ All ¦ ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ P ¦ All ¦ ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ R ¦ BR ¦ Before-image updated ¦ Ignores ¦ Record ¦
¦ ¦ ¦ for rollback ¦ ¦ updated with ¦
¦ ¦ ¦ operation ¦ ¦ before-image ¦
+------+-------+----------------------+------------------+---------------¦
¦ R ¦ DL ¦ Record deleted ¦ Record deleted ¦ Record ¦
¦ ¦ ¦ ¦ ¦ updated with ¦
¦ ¦ ¦ ¦ ¦ before-image ¦
+------+-------+----------------------+------------------+---------------¦
¦ R ¦ DR ¦ Record deleted for ¦ Record deleted ¦ Record ¦
¦ ¦ ¦ rollback operation ¦ ¦ updated ¦
+------+-------+----------------------+------------------+---------------¦
¦ R ¦ PT ¦ Record written to ¦ Record written ¦ Record ¦
¦ ¦ ¦ member ¦ to member ¦ deleted from ¦
¦ ¦ ¦ ¦ ¦ member ¦
+------+-------+----------------------+------------------+---------------¦
¦ R ¦ PX ¦ Record added ¦ Record added ¦ Record ¦
¦ ¦ ¦ directly to member ¦ ¦ deleted from ¦
¦ ¦ ¦ ¦ ¦ member ¦
+------+-------+----------------------+------------------+---------------¦
¦ R ¦ UB ¦ Record updated ¦ Ignores ¦ Record ¦
¦ ¦ ¦ (before-image) ¦ ¦ updated with ¦
¦ ¦ ¦ ¦ ¦ before-image ¦
+------+-------+----------------------+------------------+---------------¦
¦ R ¦ UP ¦ Record updated ¦ Record updated ¦ Ignores ¦
¦ ¦ ¦ (after-image) ¦ with after-image ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ R ¦ UR ¦ After-image updated ¦ Record updated ¦ Ignores ¦
¦ ¦ ¦ for rollback ¦ with after-image ¦ ¦
¦ ¦ ¦ operation ¦ ¦ ¦
+------+-------+----------------------+------------------+---------------¦
¦ S ¦ All ¦ ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ T ¦ All ¦ ¦ Ignores ¦ Ignores ¦
+------+-------+----------------------+------------------+---------------¦
¦ U ¦ User-s¦eUsereentry ¦ Ignores ¦ Ignores ¦
+------------------------------------------------------------------------¦
¦ (1) The Flag field in the journal entry indicates whether the ¦
¦ file is synchronized (0 = file was synchronized; 1 = file ¦
¦ was not synchronized). ¦
¦ ¦
¦ (2) Applying journaled changes stops at this entry if ¦
¦ referential constraints that this entry violates are active ¦
¦ during the apply operation. ¦
+------------------------------------------------------------------------+
Regards
Volker Gueldenpfennig
-----Original Message-----
From: rclay [mailto:rclayZk...]
Sent: Monday, February 12, 2001 9:20 AM
To: SAP400 Mailing List (E-mail)
Subject: Need APYJRNCHG assistance...Disaster recovery
Hello, group.
I need some assistance. For reasons too numerous to mention, we are
currently in disaster recovery mode. have restored everything back into
the system and I am attempting to apply the changes from the journal
receivers but nothing seems to work. This is my first attempt and I would
appreciate anyone's help. If you have any experience, please call me at
919-572-2148.
Thanks in advance.
Regards,
Robert Clay
Database/Systems Administrator
Kerr Drug
2522 South Tri-Center Blvd.
Durham, North Carolina 27713
Telephone: 919-544-3896 Fax: 919-544-3796
rclayZk...
To unsubscribe from this group, send an email to:
SAP on System i-unsubscribeZegroups.com
Durban Tours - Südafrika Safari
TXBHW - Original Tax Base Amount in Local Currency CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.
Length: 16465 Date: 20240425 Time: 101413 sap01-206 ( 4 ms )
