Ansicht
Dokumentation
03884 - RST of IFS failing
ABAP Short Reference General Material DataThis documentation is copyright by SAP AG.
RST of IFS failing
Steve,I'm just curious. Are you backing up using BRMS and multiple tape drives in
parallel? I seem to recall a message on this group from some time back that
this didn't work on V4R3.
Andrew
-----Original Message-----
From: Jones, Stephen [mailto:Steve_JonesZh...]
Sent: Thursday, 15 November 2001 4:26
To: 'Gueldenpfennig, Volker'
Cc: Sap400 (E-mail)
Subject: RE: RST of IFS failing
Thanks very much for the procedure Volker. We have cut our losses and used
the install procedure to recreate our IFS. At least now the D01 and Q01
systems are up and running.
The tapes are with IBM to determine why, when backed up with an Option 21
and no error messages, we can neither list the full SAVRST contents of the
IFS portion of the tape, nor restore the files without apparently an IBM
object exceeding its maximum size.
Again the free membership of this e-mail group has proven more valuable than
all our expensive support contracts.
Thanks Again
Steve
(ps I don't want to put ideas into anyone's heads regards that free stuff.)
-----Original Message-----
From: Gueldenpfennig, Volker [mailto:volker.gueldenpfennigZs...]
Sent: 13 November 2001 07:41
To: 'Steve_JonesZH...'
Cc: Sap400 (E-mail)
Subject: RE: RST of IFS failing
Hi Steve,
as you are on a no longer supported IBM-release, the best approach might be,
if Doreen's idea fails as well, just to create the IFS for SAP new. When the
OS, the LIC-Pgms and the libraries are installed, you could use the
following approach to create the IFS in an empty way:
For all releases beginning up to 4.0B (All of this has to be done (incl.
CRTR3SYS) when a third tier is setup)
Log on as QSECOFR
Install an appropiate kernel-library
CALL FIXR3OWNS (<Kernel-Lib> *ALL)
ADDR3SYS SID(<SID>) TEXT('description') SYSTEM(<dbhost>) JRNRCVASP(1)
ADDR3INST SID(<SID>) INSTID(<INST>) TYPE(*CENTRAL) TEXT('description')
At this point you should check the contents of the file
/usr/sap/trans/.sapconf. It may be errors for the new system in there. So
please compare these entries to the older systems and adjust perhaps a
little bit!
CRTR3SYS SID(<SID>)
CRTR3INST SID(<SID>) SEQ(*CENTRAL or <INST>)
Now you should log on as <SID>OFR
APYR3KRN SID(<SID>) KRNLIB(<KRNLIB>)
Does R3<SID>JRN exist ?
Does the journal R3<SID>DATA/QSQJRN write to R3<SID>JRN ? (WRKJRNA
R3<SID>DATA/QSQJRN)
Start the system and do some checks, if it works fine
Attention: The profiles are now in the delivery-status and the all already
exported transports have to be exported again!
For all releases beginning at 4.5B (All of this has to be done (incl.
CRTR3SYS) when a third tier is setup)
Log on as QSECOFR
Install an appropiate kernel-library
CALL FIXR3OWNS (<Kernel-Lib> *ALL)
CRTR3SYS SID(<SID>)
CRTR3INST SID(<SID>) SEQ(<INST>)
Now you should log on as <SID>OFR
APYR3KRN SID(<SID>) KRNLIB(<KRNLIB>)
Does R3<SID>JRN exist ?
Does the journal R3<SID>DATA/QSQJRN write to R3<SID>JRN ? (WRKJRNA
R3<SID>DATA/QSQJRN)
Start the system and do some checks, if it works fine
Attention: The profiles are now in the delivery-status and the all already
exported transports have to be exported again!
Then you would have to reconfigure the STMS and perhaps to export the old
still needed requests again. But, instead of being down for several more
days this might be the best approach.
Regards
Volker
[Non-text portions of this message have been removed]
Durban Tours - Südafrika Safari
Addresses (Business Address Services) rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 4640 Date: 20240425 Time: 003035 sap01-206 ( 3 ms )
