on 04-23-2014 8:35 AM
Hello,
I had a SAP ECC6 EhP4 system installed on Windows Failover Cluster, with ASCS instance and Central Instance on the first node and the dialog instance and the second node.
I have upgraded my system to ECC6 EhP7 / NW 7.40.
SUM porcess has merged Central instance profile with Start profile.
It seems that it didn't do it for dialog instance.
I always have a start profile and an instance profile for dialog instance.
Now, when importing profiles from RZ10, I have this issue :
Log for the import of profiles
Start profile \\FRDGRHD39SAP\sapmnt\D39\SYS\profile\START_D01_FRDGRHD39A02
Could not be activated
Can you help me?
Regards
Hello,
thanks for your answers.
I will apply SAP note 1528297 and I will tell you if it will solve my issue.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello ,
I would like to suggest the following SAP notes and KBA:
1770548 - Problems when import, save or activate profil in RZ10
1325675 - Start parameter in instance profile
82655 - Instance not configured correctly
BR
T
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chris,
We had exactly the same issue after updating our SAP ERP 6.0 EHP4 systems to SAP ERP 6.0 EHP7.
Please have a look at SAP note 1528297. It describes the merge of START- and instance profile and adaption of the service definition for (A)SCS instances, but it worked for our standalone dialog instances as well. After a restart of the dialog instance with the changed profile / service definition the error during the import of the profiles in RZ10 didn't come up again.
Best regards
Arno
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One question.
While upgrading the system did you select the option "Update Dialog Instances" in the configuration phase ?
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
try to import the start profile from Dialoge instance or both cluster Nodes and activate it.
or you can see note 1528297 - Merge start profile with instance profile.
Regards
Said Shepl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
in new versions Start profile is not used anymore. There should exist only default profile, which is applied always as first during the system start. After this, the instance profile is applied for each instance.
The path for your profile should probably be /usr/sap/D39/SYS/profile (as Deepanshu wrote). But it could differ since your message is telling this path: \\FRDGRHD39SAP\sapmnt\D39\SYS\profile\START_D01_FRDGRHD39A02
Anyway, I think there is no start profile anymore, so it could not be activated.
Kind regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I still think there should be any start profile anymore in your version... Release Notes - Profile Parameters in the Application Server - What's New in SAP NetWeaver 7.4 (Rele...
Hi
Have you do the import profile on both cluster Nodes?
Regards
Sriram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you just try to put the same profile in
/usr/sap/d39/SYS/profile and try again
Regards,
Deepanshu Sharma
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.