Show TOC

Procedure documentationChecking, Saving, and Activating Profiles Locate this document in the navigation structure

 

Once you have finished maintaining a profile, you can check it for errors or inconsistencies, save it in the database, and then activate it.

The profile maintenance tool stores the profiles as operating system files and stores a copy of each profile in the database. The database copy is used to create the profiles at database level. This process is known as activating a profile.

Note Note

The profile maintenance tool ensures that changes to profiles are activated when the corresponding SAP instance is restarted. You cannot make changes to an SAP instance during active operation.

End of the note.

Procedure

  1. Call profile maintenance by choosing   Administration   CCMS   Configuration   Profile Maintenance  . Alternatively, call transaction RZ10.

  2. To call the individual functions in the table, execute the relevant commands specified:

    Function

    Command

    Save profiles

    Enter a profile name in the Profile field and choose   Profile   Save  .

    Check individual profiles

    Specify the name and version of the profile. Then choose   Profile   Check  .

    Check all profiles of the active server

    Choose   Utilities   Check all profiles   the active server  .

    Check all profiles used in operation modes

    Choose Utilities   l   Check all profiles   In operation modes  .

    Activate profiles

    Enter a profile name in the Profile field and choose   Profile   Activate  .

    Note Note

    Stop the instance(s) in which you want the profile changes to take effect, and restart them.

    End of the note.
Background Information About Profile Checks

If a profile has been changed, you can perform extensive checks for it. You can check the semantics, syntax, and the parameter names of the profile. The system displays the result of the profile checks as a log that contains either warnings or error messages.

The parameters in a profile are divided into classes. For each class, there is a separate check rule. The table below shows these rules and includes an example for each:

Parameter Class

Check Rule

Example

Integer value

Value smaller than default value: Error

Value larger than default by a factor of 10: Warning

rdisp/TRACE

Time value

Value smaller than 0: Error

Permissible characters: 0-9

rdisp/btctime

Boolean value

Legal values:

0, 1ON, OFFYES, NOTRUE, FALSE

Other values: Error

gw/accept_remote_trace_level

File Directory

Directory does not exist: Warning

No write authorization: Warning

rdisp/workdir

File name

File does not exist: Error

abap/rsyn

TCP computer name

Host is not known to TCP: Error

rdisp/mshost

TCP service name

Service name is not known to TCP: Error

rdisp/msserv

SAP server name

Server name is not known to SAP system: Error

rdisp/vbname

File mask

Check is not possible

enque/log_file

Strings

Check is not possible

abap/locale_ctype

Cannot be changed by customer

If particular parameters are changed by the customer: Error

transport/systemtype

Special parameters

If value does not contain a particular character string: Error

rdisp/bufrefmode

Start Parameters

If at least one program is not started: Error

More Information

Profiles start page