on 09-02-2013 2:03 PM
Hi,
In processing upgrade to EHP6, we are facing a problem after phase MAIN_NEWBAS/XPRAS_AIMMRG during Execution phase:
Checks after phase MAIN_NEWBAS/XPRAS_AIMMRG were negative!
Last error code set: Detected 38 errors summarized in 'XPRASUPG.ELG'<br/> Calling '/usr/sap/SID/SYS/exe/run/tp' failed with return code 8, check /usr/sap/SID/SUM/abap/log/SAPup.ECO for details
In the logfile
/usr/sap/CH7/SUM/abap/log/SAPR731XPRA90000113.SID
we can see the following:
A2 EFINB_TR 097 Transport tool FINBASIS: Client cascade for client "001" started
A2EEFINB_TR 042 RFC error with destination "CH7_001" -> see long text"Upgrade runs - No login""possible"
A2EEFINB_TR 032 No suitable RFC destination could be found"001"
A2 EFINB_TR 098 Transport tool FINBASIS: Client cascade for client "001" finished
The RFC destination exists indeed, but the connection isn't possible because of the upgrade (No login possible).
Now the upgrade was stopped because this phase needs a working RFC destination. And the RFC Communication can't work because no login is possible due to upgrade.
How to solve this dilemma?
Many thanks
Regards
Hi,
The error 'No suitable RFC ...' indicates (as long text of the message
says) that FINBASIS Transport Tool should call application import
logic from proper client. In order to do it it needs RFC destination
to access application client within system where the import is executed.
If you experience troubles with RFC destination then check in detail
notes 644610, 912369. Those notes
contain detailed explanation what and why is needed for proper RFC
destinations settings of FINBASIS Transport Tool.
Please confirm if you have created a FINBTR@<SID>CLNT<(><<)>(>
<<(><<)>)>client> for
every client that encountered the error "No suitable RFC destination
could be found".
As per SAP note 912369
"in case that you receive error message FINB_TR 032 during XPRA
execution (during upgrade) and clients are not yet implemented
in your system then it is necessary to set the RFC destination
for client 001"
Usually from upgrade point of view these RFC issues can be ignored and
proceeded.
Regards,
Aidan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Key here is that you use only "DDIC" user for those RFC's , if you use any other users it fails.
Every user is locked except for DDIC during the upgrade.
Hope this helps.
REF : 912369 - FINB_TR_DEST, after import failures, transport errors
Thanks,
Uday
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
Just create a new RFC destination with name FINBTRDEST001 of type R3. This RFC should be pointing to client 001.
Post this check the results.
Hope this helps.
Regards,
Deepak Kori
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.