Ansicht
Dokumentation

07472 - APYJRNCHG Issues

07472 - APYJRNCHG Issues

Vendor Master (General Section)   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

APYJRNCHG Issues

Hi Chris,

yes, you would have to reassociate the receivers with the option 9 of WRKJRN.
But if you didn't do that APYJRNCHG shouldn't work at all.
I'm surprised, that you see an SS entry, if you did y complete system-backup
where I assume, that this is done while SAP was not active and normally I
wouldn't do this with "save-while-active". If you don't use this, SS doesn't
occur!

I think, you would have to contact an IBM specialist now, because either you did
something wrong or IBM would have a problem here. Unfortunately I'm really sure,
that there was a handling error, because I never had a problem in this part of
the IBM code.

Regards

Volker

-----Original Message-----
From: Chris Sugg [mailto:cgcsuggZnmhg.com]
Sent: Donnerstag, 12. September 2002 17:43
To: DoNotReply@consolut.eu
Subject: Re: APYJRNCHG Issues


Hi Volker.

Sorry for being so slow in my response. I just go back home from
Chicago yesterday.

I am 100% sure the backup is from a full system backup from 10-AUG-02
with PRD down and the journals detached. The journal QSQJRN2404 at
seq# 401309390 was the SS entry.(I checked 3 times) The dates appear
to also be correct for the journals.(from the 10th to the 13th) I
did not start the system up until after the applying of journaling
changes failed the second time. (which worked fine.)

Should I have associated the journals again to the restored library
before the applying command? Also, I am not sure if I ran across any
entires that would have caused the roll forward to cancel such as MD,
MG, etc..

Thanks for your help and others who responed,
Chris

--- In SAP on System iZy..., "Gueldenpfennig, Volker"
<volker.gueldenpfennigZs...> wrote:
> Hi Chris,
>
> I'm sorry, but I'm pretty sure, that the database and the journal-
receivers do NOT fit together.
> If you have the problem, that it tries to create records, that are
already there, it doesn't fit! It is 99,99999% an user error here!!!
>
> Are you sure, to have taken the correct backup of the right time ?
> Didn't you do ANY updates on the backup later on ? Such as STARTSAP
(just for a test ...)? Because ANY update including STARTSAP screws
EVERYTHING up!!!!
>
> So, you only can use APYJRNCHG, if you restore the correct backup
and do the APYJRNCHG (a lot better: APYJRNCHGX as PRPQ, because it
supports DDL changes as well!!!) IMMEDIATELY after it.
> Then after all, you can start SAP or do whatever you want to try!!!
>
> Regards
>
> Volker
>
> -----Original Message-----
> From: Chris Sugg [mailto:cgcsuggZn...]
> Sent: Mittwoch, 11. September 2002 00:34
> To: SAP on System iZy...
> Subject: RE: APYJRNCHG Issues
>
>
> Hello gang.
>
> We are testing D/R at SunGard location. All has gone well until we
> got to the APYJRNCHG command. We restored a backup set of tapes
and
> then several journals following the backup. When I try to apply
the
> jrn. changes, it keeps failing when it tries to apply a record to a
> table that already exist. I am starting from the first SS seq# in
> the journal and going forward. It appears to go thru several of
the
> journals (from the 2200 page joblog log but when it fails, it is in
> the first jrnrcv.
>
> After restoring the R3PRDDATA db fro mteh system backup, the
command
> I am using is:
>
> APYJRNCHG R3PRDDATA/QSQJRN R3PRDDATA/*ALL R3PRDJRN/QSQJRN2404
> R3PRDJRN/QSQJRN2407 401309390.
>
> Does anyone have any suggestions?
>
> Thanks,
> Chris
>
>
>
> Have a look to our homepage at: http://www.consolut.net
> SAP on System i-unsubscribeZy...
>
> Your use of consolut is subject to
http://www.consolut.net



Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu

Your use of consolut is subject to http://www.consolut.net


Durban Tours - Südafrika Safari

BAL_S_LOG - Application Log: Log header data   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 5146 Date: 20240520 Time: 220110     sap01-206 ( 3 ms )