cancel
Showing results for 
Search instead for 
Did you mean: 

START Profile could not be activated

Former Member
0 Kudos

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

Accepted Solutions (0)

Answers (8)

Answers (8)

Former Member
0 Kudos

Hello,

thanks for your answers.

I will apply SAP note 1528297 and I will tell you if it will solve my issue.

Regards

Former Member
0 Kudos

Hello Durecu,

Thank you fro your replay! The feadback would be also well come

Kind regards,

Tamas Istenes SAP Support Engineer

AGS Primary Support, Global Support Center Hungary

Former Member
0 Kudos

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

arno_riegel
Explorer
0 Kudos

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

Reagan
Advisor
Advisor
0 Kudos

One question.

While upgrading the system did you select the option "Update Dialog Instances" in the configuration phase ?

Regards

RB

Former Member
0 Kudos

Hello,

yes, I have selected it.

Regards

said_shepl
Participant
0 Kudos

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

Former Member
0 Kudos

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

Former Member
0 Kudos

Hello,

/usr/sap/D39/SYS/profile is the same as \\FRDGRHD39SAP\sapmnt\D39\SYS\profile.

I tried to merge both instance and start profile and to delete start profile file but when importing in RZ10, it tries to find START profile and couldn't....

Regards

Former Member
0 Kudos

Hello

In RZ10, in the profile window press F4 , select the start profile, then in the "Edit profile" underneath select "Administration data" and "change".

Under Administration data" >> "Activation in operating system" file Check the path of the start profile and if it's wrong - fix it.

Regards

Former Member
0 Kudos

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...

Former Member
0 Kudos

Hello,

I can't see start profile anymore in RZ10, only DEFAULT and instances profile (CI and DI)

Regards

Former Member
0 Kudos

Hello,

I agree about that. It seems that SUM process merged profiles only for CI and not for DI.

regards

Sriram2009
Active Contributor
0 Kudos

Hi

Have you do the import profile on both cluster Nodes?

Regards

Sriram

Former Member
0 Kudos

Hello,

profile files are on a shared directory.

Regards

Sriram2009
Active Contributor
0 Kudos

Hi chri

Kindly check the follows

1. In both Cluster nodes SAP instance are on?

2. In fail over cluster resources are online?

3. In both cluster node profiles are imported by using transaction Code RZ10 ?

Regards

Sriram

Former Member
0 Kudos

Hi,

yes, SAP instance are on in both cluster node.

Fail over cluster resources are online.

Do I need to switch resources to second node to import profiles whereas profile files are on shared directory?

Regards

Sriram2009
Active Contributor
0 Kudos

Hi

Yes you can do that.

Regards

Sriram

Former Member
0 Kudos

Hello,

I tried to do that...but I had the same issue.

Regards

Sriram2009
Active Contributor
0 Kudos

Hi

Any error message?

Regards

Sriram

Former Member
0 Kudos

Hello,

yes, the same one :

Log for the import of profiles

Start profile \\FRDGRHD39SAP\sapmnt\D39\SYS\profile\START_D01_FRDGRHD39A02

Could not be activated

Regards

Former Member
0 Kudos

Can you just try to put the same profile in

/usr/sap/d39/SYS/profile and try again

Regards,

Deepanshu Sharma    

Former Member
0 Kudos

Hello,

the Start prifile is still in this directory.

Regards