Parameter changes prevent SAP from starting

[Former Member]

Hello all,

We are running SAP ERP 4.7ext 2.00 with two nodes in a Windows/MSSQL Cluster environment.

1. Last night, we made parameter changes to the central instance profile. In particular, we started with adding the parameter “enque/table_size = 16384”, activated the profile and took the SAP R/3 RP1 Resource offline. We then tried to bring it back online but it went into a failed status. We removed this parameter using a text editor, and then retried to bring the SAP Resource online again, but to no avail – it went into a failed state again.

2. We had previously made backups of the profile files created by the reinstallation of the central instance (DEFAULT, START_DVEBMGS00_ZAASAPCCI001, and RP1_DVEBMGS00_ZAASAPCCI001 – let’s call this File Set A.) and decided to use these files instead. These files had the default parameters created on installation. We were successful in bringing the SAP resource online.

3, We made a parameter change and activated the profile in SAP – it does not matter which parameter you choose, for example, changing the number of dialog work processes from the default 2 to 20 . We took the SAP R/3 RP1 Resource offline but were unable to bring it back online - it went into a failed status.

4. We then took File Set A, and using a text editor (1) made changes to the number of work processes; and (2) appended the extra parameters to them. Using these files we were now successful in bringing the SAP Resource online.

5. If we now made any changes to these files – either through SAP or by using the text editor, we are unable to restart SAP. We have to revert to step 4 above.

6. A strange anomaly we noticed is that if the profile files have the following commented lines in the beginning of the file RP1_DVEBMGS00_ZAASAPCCI001. for example:

#.******************************************************************************

#.* *

#.* Instance profile RP1_DVEBMGS00_ZAASAPCCI00 *

#.* *

#.* Version = 000007 *

#.* Generated by user = ABOOM *

#.* Generated on = 11.05.2006 , 09:04:07 *

#.* *

#.******************************************************************************

Then we are unable to restart SAP.

Is this a bug related to running a dual-node SAP cluster? We were previously able to make parameter changes (either through SAP or through the use of a text editor) and restart SAP successfully.

It is now become critical to determine the cause of this anomalous behaviour and resolve the problem. Failing this, the client wants to break the cluster and revert to a distributed SAP system installation (with separate DB and central instance hosts).

Your comments and help wil be greatly appreciated.

Regards,

Lebo

[JPReyes]

OK... you can try revert changes... go delete content of the SAP work directory and restart the system.

If it fails can you post the errors on dev_ms, dev_disp and dev_w0?

Hope this help!

Juan Reyes

[Former Member]

Hi Lebo,

Can you try to edit your profiles (the correct ones) using sappad tool (/usr/sap/<SID>/<INST-ID>/run/exe/) and save it in the same format that was used to open it.

Regards,

Mike