Ansicht
Dokumentation
03852 - RST of IFS failing
ROGBILLS - Synchronize billing plans Vendor Master (General Section)This documentation is copyright by SAP AG.
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
Durban Tours - Südafrika Safari
General Data in Customer Master CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 2772 Date: 20240426 Time: 043114 sap01-206 ( 3 ms )
