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>

Activating Emergency User (SAP*) on AS Java

Pre-requisite:
<sid>adm will be used to launch the configtool.
DISPLAY environment has to be set for the <sid>adm user.


Procedure :
 1. Navigate to /usr/sap/<SID>/J*/j2ee/configtool/

 2. Run the executable configtool.sh

 3. Choose to switch to configuration Editor Mode .

 

 4. On the Display Configuration tab page, choose  cluster_config  > system  > custom_global  > cfg  > services >  com.sap.security.core.ume.service >  Propertysheet properties.

 5. Switch to Edit mode. 

 6. Set values for properties as below

          Property =  ume.superadmin.activated

          Value = true

          Property  = ume.superadmin.password

          Value = <password>

Note : The SAP* user is now activated. While it is activated, all other users are deactivated. You can only log on with the SAP* user.

  7. Save

  8. Restart the AS Java.

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

Comparison method violates its general contract in SLD Log

Error :

RZ70 data is not reflecting in SLD
SLD log is showing Comparison method violates its general contract

Procedure :

     1. Open the java offline config tool (/usr/sap/<SID>/<InstanceID>/j2ee/configtool).
     2. Navigate to cluster-data --> template - Usage_Type_All_in_One -->instance - IDXXXXX (HOST).
     3. Select the tab VM Parameters.
     4. Click on New Button.

     5. Add the parameter -Djava.util.Arrays.useLegacyMergeSort and value true (without quotes)
select the Enabled checkbox is checked.
    6. Restart all the Java Application Server
    7. Go to dev_server0 log file and check the parameter -Djava.util.Arrays.useLegacyMergeSort is available in the log
    8. Run the data supplier again.

HANA 1.0 SPS 12 Installation on Linux System

Procedure :

1. To start the HANA Installer , run ./hdbsetup

2. To start the installation , choose Install the SAP HANA Database

3. Provide the HANA SID, Instance no. , Database mode and System usage according to the requirement of the system.

4. Provide the username and password for the <sid>adm user.

5. Check the data volume and log volume path

6. Provide the SYSTEM user password

7.  Check the summary for the installation

8.  Monitor the progress of the Installation

9. After the successful Installation check the logs for any error.

OS Pre-requisite Check on RHEL 6.X, 7.X for Databases (Oracle and Sybase)

• Check the Created Mount Points

                 $ df -h   (For Oracle Only)

• 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 (EL6)

                      # SAP settings

                      kernel.msgmni=1024
                      kernel.sem=1250 256000 100 1024
                      vm.max_map_count=2000000
  
                To do this append the following lines to /etc/sysctl.conf (EL7)

                      # SAP settings

                      kernel.sem=1250 256000 100 1024

                      vm.max_map_count=2000000

                For Sybase Please add below parameters as well

                      kernel. randomize_va_space=0
                      kernel. exec-shield=0

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

• Install the OS Software Package for Oracle (EL6)

                   bc
                   binutils-2.20.51.0.2-5.36.el6 (x86_64)
                   compat-libcap1-1.10-1 (x86_64)
                   compat-libstdc++-33-3.2.3-69.el6 (x86_64)
                   compat-libstdc++-33-3.2.3-69.el6 (i686)
                   e2fsprogs-1.41.12-14.el6 (x86_64)
                   e2fsprogs-libs-1.41.12-14.el6 (x86_64)
                   glibc-2.12-1.107.el6 (i686)
                   glibc-2.12-1.107.el6 (x86_64)
                   glibc-devel-2.12-1.107.el6 (i686)
                   glibc-devel-2.12-1.107.el6 (x86_64)
                   ksh
                   libaio-0.3.107-10.el6 (x86_64)
                   libaio-0.3.107-10.el6 (i686)
                   libaio-devel-0.3.107-10.el6 (x86_64)
                   libaio-devel-0.3.107-10.el6 (i686)
                   libX11-1.5.0-4.el6 (i686)
                   libX11-1.5.0-4.el6 (x86_64)
                   libXau-1.0.6-4.el6 (i686)
                   libXau-1.0.6-4.el6 (x86_64)
                   libXi-1.6.1-3.el6 (i686)
                   libXi-1.6.1-3.el6 (x86_64)
                   libXtst-1.2.1-2.el6 (i686)
                   libXtst-1.2.1-2.el6 (x86_64)
                   libgcc-4.4.7-3.el6 (i686)
                   libgcc-4.4.7-3.el6 (x86_64)
                   libstdc++-4.4.7-3.el6 (i686)
                   libstdc++-4.4.7-3.el6 (x86_64)
                   libstdc++-devel-4.4.7-3.el6 (i686)
                   libstdc++-devel-4.4.7-3.el6 (x86_64)
                   libxcb-1.8.1-1.el6 (i686)
                   libxcb-1.8.1-1.el6 (x86_64)
                   libXrender (i686)
                   libXrender (x86_64)
                   libXrender-devel (i686)
                   libXrender-devel (x86_64)
                   make-3.81-20.el6 (x86_64)
                   smartmontools-5.43-1.el6 (x86_64)
                   sysstat-9.0.4-20.el6 (x86_64)

• Update the user and group limit for Oracle (EL6)

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

                  @dba       hard    nofile    32800
                  @dba       soft    nofile    32800

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

                  @dba    soft    nproc    unlimited

• Install the OS Software Package for Oracle (EL7)

                 

                   bc
                   binutils-2.23.52.0.1-12.el7 (x86_64)
                   compat-libcap1-1.10-3.el7 (x86_64)
                   compat-libstdc++-33-3.2.3-71.el7 (i686)
                   compat-libstdc++-33-3.2.3-71.el7 (x86_64)
                   glibc-2.17-36.el7 (i686)
                   glibc-2.17-36.el7 (x86_64)
                   glibc-devel-2.17-36.el7 (i686)
                   glibc-devel-2.17-36.el7 (x86_64)
                   ksh
                   libaio-0.3.109-9.el7 (i686)
                   libaio-0.3.109-9.el7 (x86_64)
                   libaio-devel-0.3.109-9.el7 (i686)
                   libaio-devel-0.3.109-9.el7 (x86_64)
                   libgcc-4.8.2-3.el7 (i686)
                   libgcc-4.8.2-3.el7 (x86_64)
                   libstdc++-4.8.2-3.el7 (i686)
                   libstdc++-4.8.2-3.el7 (x86_64)
                   libstdc++-devel-4.8.2-3.el7 (i686)
                   libstdc++-devel-4.8.2-3.el7 (x86_64)
                   libxcb-1.9-5.el7 (i686)
                   libxcb-1.9-5.el7 (x86_64)
                   libX11-1.6.0-2.1.el7 (i686)
                   libX11-1.6.0-2.1.el7 (x86_64)
                   libXau-1.0.8-2.1.el7 (i686)
                   libXau-1.0.8-2.1.el7 (x86_64)
                   libXi-1.7.2-1.el7 (i686)
                   libXi-1.7.2-1.el7 (x86_64)
                   libXtst-1.2.2-1.el7 (i686)
                   libXtst-1.2.2-1.el7 (x86_64)
                   libXrender (i686)
                   libXrender (x86_64)
                   libXrender-devel (i686)
                   libXrender-devel (x86_64)
                   make-3.82-19.el7 (x86_64)
                   smartmontools-6.2-4.el7 (x86_64)
                   sysstat-10.1.5-1.el7 (x86_64)

• Update the user and group limit for Oracle (EL7)

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

                  @sapsys    hard    nofile    32800
                  @sapsys    soft     nofile    32800
                  @dba         hard    nofile    65800
                  @dba         soft     nofile    65800

                  @oinstall         hard    nofile    65800

                  @oinstall        soft     nofile    65800

                  @sapsys    soft    nproc    unlimited

                  @dba    soft    nproc    unlimited
                  @oinstall    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.

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

How to open Standby database in snapshot mode for Oracle

Procedure :

Convert Standby Database in Snapshot Standby

1. Check the Database role
      SQL > select status,instance_name,database_role,open_mode from v$database,v$instance;

2. Check the current applied log sequence.

       SQL > select thread#,max(sequence#) from v$archived_log group by thread#;

3. Cancel the log application in Standby Database and start the database in mount mode
      SQL > alter database recover managed standy database cancel;
      SQL > startup mount;

4. Convert Standby Base to Snapshot mode
        SQL > alter database convert to snapshot standby;

5. Open the database
        SQL > alter database open;

Convert Snapshot Database to Standby Database

1. Check the Database role
       SQL > select status,instance_name,database_role,open_mode from v$database,v$instance;

2. Shutdown the system and start it in mount mode.
         SQL > shutdown immediate;
         SQL > startup mount;

3. Convert Snapshot mode to Standby Base
        SQL > alter database convert to physical standby;

4. Stop the system and then start it in mount mode
        SQL > shutdown immediate;
        SQL > startup mount;

5. Check the status of the database.
        SQL > select status,instance_name,database_role,open_mode from v$database,v$instance;

Suggestion :
After opening the database, application can be started.
Always check the log sequence number before and after changing the database mode.

Configure the RZ70 for sending data via RFC (SLD_UC and SLD_NUC)

Problem :

Error "TP_REG_ACCESS_DENIED (thRc=748)" when opening an RFC connection


Procedure :

1. Configuration in SLD

        Go to: SLD UI -> "Administration" -> "Settings" -> Section: "datasupplier"

Note :
Exactly this hostname and service name should be specified on ABAP side, in the RZ70.

2. Configuration in RZ70

3. Configuration in the SLD's gateway

                    3.1. gw/acl_mode = 1 must be set in the instance profile of SLD's gateway.

                    3.2. The reginfo file must contain suitable rules for registering SLD_UC or SLD_NUC TP program to register on the SLD's gateway

                         [ABAP]
                         -via SAP GUI connection:
                          "smgw"-> "Goto" -> "Expert Functions" -> "External Security" -> "Display reginfo"

                         [Java ]
                         -at os (gwmon.exe)

                           gwmon nr=<sysnum>
                              -->m  (menue)
                               -->9 (security informations)
                                -->3 (display reginfo)


 REGINFO file format

                      #VERSION=2
                      P TP=SLD_UC HOST=<SLD Application server host> CANCEL=<SAME AS "HOST">,local  ACCESS=<ALL systems pushing information to SLD Server>
                      P TP=SLD_NUC HOST=<SLD Application server host> CANCEL=<SAME AS "HOST">,local ACCESS=<ALL systems pushing information to SLD Server>
                      ... .
                      P TP=* HOST=local CANCEL=local ACCESS=local
                      P TP =*HOST=internal CANCEL=internal ACCESS=internal

               3.3. After modifying the reginfo file, gateway security must be reread:

                        [ABAP]
                        -via SAP GUI connection:
                           "smgw" -> "Goto" -> "Expert Functions" -> "External Security" -> "Reread"

                        [Java ]
                        -at os (gwmon.exe)
                            gwmon nr=<sysnum>
                            -->m  (menue)
                             -->9 (security informations)
                              -->4 (refresh security)

4. Restart the SLD.

Suggestion:
Delete the rfc SLD_UC and SLD_NUC from SM59 before sending the data.

Program SLD_UC / SLD_NUC not registered

Problem :

• Program SLD_UC or SLD_NUC and SLD are not pointing to the same Gateway where SLD is running.
• Missing Configuration in SLD Data Supplier

Procedure :

Set parameters "Gateway Host" and "Gateway Service" to the same Gateway as set in the RFC Destination SLD_UC / SLD_NUC

1. SLD > Administration > Settings > Tab "Parameters"

2. Save and then Restart the SLD.

3. Check SLD_UC or SLD_NUC program has been registered successfully.

gwmon pf=<Path of the Gateway Service Profile>

Choose option 3 (display client table)

Suggestion :

Always make sure you will give hostname only in Gateway host.

Do not give FQDN to the Gateway host.

Port 33$$ is accessible from satellite system and SLD Server.