SAP Profile Parameter

 

In SAP system  there are two types of parameter profiles are defined at /sapmnt/<SID>/profile they are named as Default profile and Instance profile .Further there are two Instance profile in the system PAS profile and ASCS profile.

Name Convention of the files :

1. Default Profile -- DEFAULT.PFL

2. PAS \ Application Server Profile -- <SID>_<Instance_Name>_<Hostname>

3. ASCS \ SCS Profile -- <SID>_<ASCSXX>_<Hostname> or <SID>_<SCSXX>_<Hostname>

Parameters defined in these profiles has been used to define the functionality of an sap system like number of work processes, buffer size, lock table size, Enable SAP* etc. All the profiles can be managed from either from RZ10 or OS level directly. 

RZ10 keeps the changes of profile in form of  version management of profile which helps us to easily revert the changes to the latest working version of the profile whenever required.

Parameter that need to be changed at application level then we change in specific Instance profile of the system and changes required at system level then we do the changes in Default Profile.

There are two type of parameter that are defined in SAP system

1. Static Parameter

2. Dynamic Parameter

Static Parameter needs restart of the system to reflect the changes, Whereas dynamic parameters can updated at the runtime as per requirement and by resting the system it will be reverted to original.

From RZ11 we can easily find out parameter is static or dynamic.

Delete ST03/ST03N old system data

Procedure:

1. Run the Tcode : SE37 and execute the functional module SWNC_COLLECTOR_CLEAN_SWNCMONI

2. Set the value of reset 'X' and Execute

3. Run the Tcode ST03 or ST03N , you will get the message "NO SYSTEM LOAD DATA AVAILABLE"

4. Now schedule the Job "SAP_COLLECTOR_FOR_PERFMONITOR" from SM36.

5. After the successful job finish , you will get the data in ST03

List of Available icon in SAP

Procedure :

1. Tcode : SE38 --> RSTXICON -->EXECUTE

2. Choose Icon as ABAP List --> EXECUTE

3. Icon list is displayed, to use the icon in SAP GUI logon screen . User code @08@

Change the logon screen message in SAP GUI

Procedure :

1. Check the current message on logon screen

2.  TCODE: SE61 --> Select Document Class "General text" --> select  language --> Document               Name as "ZLOGIN_SCREEN_INFO". Create a new one if it not exist or select Change to modified

3. Create a message as required

4. Save and Exit

How to activate SAP* in ABAP system

Procedure:

1. To Activate the SAP* in abap system set the parameter login/no_automatic_user_sapstar=0 in RZ10.

2. Take the restart of the application server.

If  SAP* is enable but still unable to login fllow the below procedure.

1. Logon to database server and switch to database user.

2. Start the sqlplus with the command:
        root > sqlplus / as sysdba

3. View the entries of the SAP* with following command:
   SQL > select * from "<SCHEMA_NAME>".usr02 where mandt = '<CLIENT_NO>' and bname = 'SAP*';

4. Delete the SAP* user
   SQL > delete from "<SCHEMA_NAME>".usr02 where mandt = '<CLIENT_NO>' and bname = 'SAP*';
   SQL > commit;

Note :

<SCHEMA_NAME> = SAPSR3 in Oracle

<SCHEMA_NAME> = SAPABAP1 or SAPHANADB in HANA

Unified Rendering Update with TCI for WD ABAP

Procedure :

The Unified Rendering engine is incrementally patched on the ABAP side. When you apply the notes there will be numerous prerequisites. These prerequisites will apply one by one the changes to the ABAP engine. All the notes together will bring the system to the complete and actual stack level.

Implementing the UR notes may take time, and you need to be careful to always activate all the objects listed at the application, otherwise the UR framework can become inconsistent and syntax errors can occur in UR classes.


1. Open the SAP Note : 2090746 and search for the relevant component SAP_BASIS or SAP_UI
2. Open the UR SAP note from the table which is relevant for your SAP_BASIS or SAP_UI release.
3. Download the that relevant UR SAP Note using Transaction SNOTE
4. Upload the relevant TCI using SPAM or SAINT.
5. Now Apply the downloaded UR note to the SAP System.

Post Processing:

1. Once all the notes are applied, make sure that you delete the server and client cache
2. Run report: WDG_MAINTAIN_UR_MIMES.
3. Compare the two values labeled "urchangelist". Both must show the same number.

4. If they do not show the same value, please execute the option 'Deploy Mimes' and check if this resolves the issue.

Note:
Ensure you have full backup of the system, before applying TCI.
Minimum SPAM Version should be 70.

SSFS Configuration for Oracle Database for Linux Systems

Concept :

Earlier the connection from the SAP ABAP system worked in such a way that OPS$ connection
was authorized by the OS user to permit access to table OPS$.<SID>ADM.SAPUSER only. It contains the actual database user used for the connection with the encrypted password.

SSFS (Secure Storage File System) will contain the encrypted file store at OS level, to connect to database from SAP ABAP System.

SSFS connections are only applicable for the ABAP system only.


Solution :

1. Create the director under the path /usr/sap/<SID>/SYS/global/security/ with <SID>adm

• mkdir -p /usr/sap/<SID>/SYS/global/security/rsecssfs/data
• mkdir -p /usr/sap/<SID>/SYS/global/security/rsecssfs/key

2. Set the environment variable for the <SID>adm user (.sapenv_<hostname>.csh and .sapenv.csh)

• setenv RSEC_SSFS_DATAPATH  /usr/sap/<SID>/SYS/global/security/rsecssfs/data
• setenv RSEC_SSFS_KEYPATH  /usr/sap/<SID>/SYS/global/security/rsecssfs/key
• setenv rsdb_ssfs_connect  1

3. Set the profile parameter (DEFAULT.PFL)

• rsec/ssfs_datapath = $(DIR_GLOBAL)$(DIR_SEP)security$(DIR_SEP)rsecssfs$(DIR_SEP)data
• rsec/ssfs_keypath  = $(DIR_GLOBAL)$(DIR_SEP)security$(DIR_SEP)rsecssfs$(DIR_SEP)key
• rsdb/ssfs_connect = 1

4. Set the SSFS Credential

• rsecssfx put DB_CONNECT/DEFAULT_DB_USER SAPSR3 -plain
• rsecssfx put DB_CONNECT/DEFAULT_DB_PASSWORD <SCHEMA_PASSWORD>

5. Check the R3trans -d

6. Delete the table SAPUSER

                 > sqlplus
                SQL> connect system/<pwd>
                SQL> drop table ops$<sid>adm.sapuser;

7. Delete the REMOTE_AUTH parameter

              > sqlplus

                SQL> connect system/<pwd>

                SQL> alter system reset remote_os_authent scope=spfile;

OS Pre-requisite Check on RHEL 6.X, 7.X for SAP Installation

• Check the Created Mount Points

                 $ df -h

• Check Hostname

                $ hostname -s

• Check Full Qualified Domain Name

                $ hostname -f

• Update the Linux Kernel Parameter

                 To do this append the following lines to /etc/sysctl.conf  (For EL6)

                      # SAP settings

                      kernel.msgmni=1024

                      kernel.sem=1250 256000 100 1024
                      vm.max_map_count=2000000
                      vm.swappiness=1

                To do this append the following lines to /etc/sysctl.d/sap.conf  (For EL7)

                       # SAP settings (For EL7)

                      kernel.sem=1250 256000 100 1024

                      vm.max_map_count=2000000
                      
                     

                 Note : Run the command "sysctl -p" to activate the modified kernel parameters.

• Install the OS Software Package for SAP Application Server (EL6 and EL7)

                   libuuid-2.17.2-12.24.el6.x86_64 or Latest

                   uuidd-2.17.2-12.24.el6.x86_64 or Latest

                   libstdc++-4.4.7-17.el6.x86_64 or Latest

                   libstdc++-devel-4.4.7-17.el6.x86_64 or Latest

                   gcc-4.4.7-17.el6.x86_64 or Latest

                   glibc-2.17.2-12.24.el6.x86_64 or Latest

                   xorg-x11-apps-7.7-6.el6.x86_64 or Latest

                   compat-sap-c++-6 6.3.1 x86_64 or Latest
                   gcc-c++-4.4.7-23.el6.x86_64 or Latest
                   compat-libstdc++-33-3.2.3-69.el6.x86_64 or Latest

• Update the user and group limit

                   To do this append the following lines to /etc/security/limits.conf  (For EL6)

                  @sapsys           hard              nofile             32800

                  @sapsys           soft               nofile             32800

                   To do this append the following lines to /etc/security/limits.d/90.nproc.conf

                  @sapsys          soft              nproc            unlimited

                  To do this append the following lines to /etc/security/limits.d/99-sap.conf  (For EL7)

                  @sapsys           hard              nofile             32800

                  @sapsys           soft               nofile             32800

                @sapsys           soft              nproc            unlimited

Suggestion

Do not installation separate JAVA jdk/jre on SAP JAVA Application Server.

Always reboot the system after completing the pre-requisite.

Do not forgot to add swap space as per the SAP guidelines before starting the OS pre-requisite.

Always use the latest Software Provisioning Manager (SWPM) version for the installation.

Hostname should not be more than 13 characters.

Note : These pre-requisite are related to SAP Application Server only for the  pre-requisite related to database please visit the Page

Enabling RZ70 for HTTP(S) data transfer

Details :

ABAP SLD data supplier (RZ70) uses RFC today and it can only be configured for one target SLD.  You want to use HTTP(S) destinations
i) Instead of RFC
ii) Addition to the single RFC destination


Procedure :

1. Implement the SAP Note : 2188401
2. Run report 'RSLDHTTPCONF' in transaction SA38 to configure the new HTTP(S) option.

3. Now Send the data from RZ70.

Reset Schema User (SAPSR3) Password using brtools

Error :

Unable to login with Schema User password or forgot the SAPSR3 password

Procedure:

brconnect -u system/<system_user_password> -f chpass -o SAPSR3 -p <password>


Note:

If you forgot the password of system user , it can be reset with the below sqlplus command

SQL> alter user system identified by <password>;
SQL> commit;

SSFS Schema password Update

Error:

R3trans -s fails with error

ORA-01017: invalid username/password; logon denied brtools



Procedure :

rsecssfx put DB_CONNECT/DEFAULT_DB_USER <SCHEMA_NAME> -plain
rsecssfx put DB_CONNECT/DEFAULT_DB_PASSWORD <password>

Export DB tables using BRTOOLS

Pre-Requisite :

Login with os user ora<sid> or oracle.
Create a directory, which have access of oracle or ora<sid> user.
Change the permission of the table export directory to 775.

Procedure :

Start the brtools with command    $ brtools

• Choose the Segment Management of Choice 3

• For the Table Export choose the option 3

• Provide the Table Name and Export dump directory location with the option 6 and 7 respectively.

• Press Continue to check the export option.

• Again Press Continue to start the export of the table and will create the export file with <file_name>.dmp 

Suggestion :

Always make sure that you have updated version of brtools available in your system.
Do not manually set the permission of brtools executable.
Before import or export activity always make sure that you have full backup of the system

UUIDD daemon (uuidd) not found

     Error :

     Reason :

     UUID daemon is not running or its package is not installed.

    Solution :

             SLES 11 or above

                1. Install RPM package sapconf

                2. Run the UUID daemon permanently with commands 'systemctl enable uuidd' and 'systemctl start uuidd' (as root)

             RHEL 4 and above

                1. Install the uuidd RPM package.

                2. Run the UUID daemon permanently with command 'service uuidd start', respective 'chkconfig uuidd on' (as root).

Import DB tables using BRTOOLS

Pre-Requisite :

Login with os user ora<sid> or oracle.
Create a directory, which have access of oracle or ora<sid> user.
Change the permission of the table import directory to 775.
Delete the data of the table from SE14 before importing.

Procedure :

Start the brtools with command   $ brtools

• Choose the Segment Management of Choice 3

• For the Table Export choose the option 4

• Provide the Dump file location with data dump

• Press Continue to check the import option.

• Again Press Continue and change the option 4 - replace and 7 - force 

• Press Continue to start the import

Suggestion :

Always make sure that you have updated version of brtools available in your system.
Do not manually set the permission of brtools executable.
Before import or export activity always make sure that you have full backup of the system
Always count the table rows before and after the import to table.

Register program at OS Level for TCP/IP RFC

Procedure :

rfcexec -t -a <program ID> -g <gateway host> -x <gateway service> -s <SID>


Program ID = Name of the Program
Gateway Host = Hostname where Program is registering
Gateway Service = Gateway Service where Program is registering


Register Program as a Daemon Service (Background):

nohup rfcexec -t -a <program ID> -g <gateway host> -x <gateway service> -s <SID> &