SAP HANA BASIS PROCEDURES & SOLUTIONS

THE RIGHT TIME || OFFICAL TRAILER || 30 AUG 2020 ||

noreply@blogger.com (Venkata S Pagolu) — Fri, 28 Aug 2020 13:06:00 +0530

Deactivating SYSTEM User in Sap Hana database

noreply@blogger.com (Venkata S Pagolu) — Thu, 23 Jul 2020 10:00:00 +0530

Deactivate the SYSTEM User

As the most powerful database user, SYSTEM isn't intended to be used in production systems. Use it to make lesser privileged users for particular purposes then deactivate it.

Procedure

Execute the subsequent statement, for instance , within the SQL console of the SAP HANA studio:

ALTER USER SYSTEM DEACTIVATE USER NOW

The SYSTEM user is deactivated and may not hook up with the SAP HANA database.

You can verify that this is often the case within the USERS system view. For user SYSTEM, check the values within the columns USER_DEACTIVATED, DEACTIVATION_TIME, and LAST_SUCCESSFUL_CONNECT

Starting and Stopping the SAP HANA Database at OS level

noreply@blogger.com (Venkata S Pagolu) — Thu, 23 Jul 2020 09:39:00 +0530

Starting and Stopping the SAP HANA Database

The SAP HANA database can be started or stopped by using SAP HANA studio
or by using OS commands.

Using OS command

• Use HDB as <sid>adm
- HDB stop I HDB start

• Use sapcontrol as root
- sapcontrol -nr 00 - function Stop
- sapcontrol -nr 00 - function start
- sapcontrol -nr 00 -function GetProcessUst

On operating system level, the SAP HANA database can be started or stopped
using the commands sapcontrol or HDB

Starting SAP HANA database
Using sapcontrol
/usrsap/hostctrl/exe/sapcontrol -nr <Instance Number> - function Start

Using HDB as <sapsid>adm
/usr/sap/<SAPSID> /<Instance_Name>/ HDB start

Stopping SAP HANA database
Using sapcontrol
/usr/sap/host.ct.rl/exe/sapco nt rol - nr <Instance Number> func tion Stop

Using HDB as <sapsid>adm
/usr/sap/<SAPSID> /<Instance_Na.me>/HDB stop

Displaying process list at command line

Log on to Linux command line as root
/usr/sap/hostctrl/exe/sapcorrtrol -nr <instancenr> - function GetProcessList

Log on to Linux command line as <sid>adm
HDB info

SUM DMO table comparision checksum error

noreply@blogger.com (Venkata S Pagolu) — Tue, 10 Mar 2020 18:12:00 +0530

While using SUM DMO for SAP system migration, DMO compares tables within the process of migration. Irrespectof you chose the table compariso option, it compares the tables within the execution phase and it's going to result with checksum errors.

This article provides us the procedure to investigate and fix table comparison row count checksum error

Check the log file MIGRATE_DT_CHECKDIFF.LST which exists under the SUM log file location.

Change to the SUM log directoy

more MIGRATE_DT_CHECKDIFF.LST

BALDAT and BALHDR are the 2 tables which got checksum errors.

Proceeded as below

/usr/sap//SUM/abap/load/migrate_dt]# grep -i BALDAT *

MIGRATE_DT_CHECKDIFF.LST:BALDAT # old: 14156352 new: 14156348

MIGRATE_DT_CNT_00003_BALDAT_EXP.IN:cp "BALDAT"

MIGRATE_DT_CNT_00003_BALDAT_EXP.LOG:2 ETQ399 Counted 1 tables out of 1, written to '/usr/sap//SUM/abap/load/migrate_dt/MIGRATE_DT_CNT_00003_BALDAT_EXP.OUT'.

MIGRATE_DT_CNT_00003_BALDAT_EXP.OUT:BALDAT 14156352

MIGRATE_DT_CNT_00003_BALDAT.FLAG:# Export for bucket 00003_BALDAT finished at 2019/07/29 14:18:32.

MIGRATE_DT_CNT_00003_BALDAT.FLAG:"MIGRATE_DT_CNT_00003_BALDAT_EXP.OUT";16

MIGRATE_DT_CNT_00003_BALDAT_IMP.IN:cp "BALDAT" "BALDAT"

MIGRATE_DT_CNT_00003_BALDAT_IMP.OUT:BALDAT 14156348

MIGRATE_DT_CNT.BUC:count: refid=00003_BALDAT export=MIGRATE_DT_CNT_00003_BALDAT_EXP.IN import=MIGRATE_DT_CNT_00003_BALDAT_IMP.IN size=8897208 estruntime=8689 expntasks=1 impntasks=1

· Replace 14156352 with 14156348 in file MIGRATE_DT_CNT_00003_BALDAT_IMP.OUT.

· Before editing this file, take a copy of existing one.

[root@/usr/sap//SUM/abap/load/migrate_dt]# cp -p MIGRATE_DT_CNT_00003_BALDAT_IMP.OUT MIGRATE_DT_CNT_00003_BALDAT_IMP.OUT_ORIG

Just checking if the copy has been created

[root@/usr/sap//SUM/abap/load/migrate_dt]# ls -lart MIGRATE_DT_CNT_00003_BALDAT_IMP*

-rw-r--r-- 1 adm sapsys 21 Jul 29 14:18 MIGRATE_DT_CNT_00003_BALDAT_IMP.IN

-rw-r--r-- 1 adm sapsys 16 Jul 29 18:19 MIGRATE_DT_CNT_00003_BALDAT_IMP.OUT_ORIG

-rw-r--r-- 1 adm sapsys 16 Jul 29 18:19 MIGRATE_DT_CNT_00003_BALDAT_IMP.OUT

[root@/usr/sap//SUM/abap/load/migrate_dt]#

Now Edit the file

[root@/usr/sap//SUM/abap/load/migrate_dt]# vi MIGRATE_DT_CNT_00003_BALDAT_IMP.OUT

Content of the file

Changing it to 14156352

Save and exit

[root@/usr/sap//SUM/abap/load/migrate_dt]# cat MIGRATE_DT_CNT_00003_BALDAT_IMP.OUT

BALDAT 14156352

[root@/usr/sap//SUM/abap/load/migrate_dt]#

Now allow us to check if BALDAT checksum error is fixed by retrying the phase.

It should show checksum error only for BALHDR

[root@<hostname>/usr/sap/<SAPSID>/SUM/abap/load/migrate_dt]# view /usr/sap/<SAPSID>/SUM/abap/load/migrate_dt/MIGRATE_DT_CHECKDIFF.LST

It is showing BALHDR only

[root@<hostname>/usr/sap/<SAPSID>/SUM/abap/load/migrate_dt]# grep -i BALHDR MIGRATE_DT_CNT*

MIGRATE_DT_CNT_00038_EXP.IN:cp "BALHDRP"

MIGRATE_DT_CNT_00038_EXP.OUT:BALHDRP 0

MIGRATE_DT_CNT_00038_IMP.IN:cp "BALHDRP" "BALHDRP"

MIGRATE_DT_CNT_00038_IMP.OUT:BALHDRP 0

MIGRATE_DT_CNT_00134_EXP.IN:cp "BALHDR"

MIGRATE_DT_CNT_00134_EXP.OUT:BALHDR 2323031

MIGRATE_DT_CNT_00134_IMP.IN:cp "BALHDR" "BALHDR"

MIGRATE_DT_CNT_00134_IMP.OUT:#BALHDR 2323030

MIGRATE_DT_CNT_00134_IMP.OUT:BALHDR 2323030

Edit file MIGRATE_DT_CNT_00134_EXP.OUT replacing 2323031 with 2323030

[root@<hostname>/usr/sap/<SAPSID>/SUM/abap/load/migrate_dt]# cp -p MIGRATE_DT_CNT_00134_EXP.OUT MIGRATE_DT_CNT_00134_EXP.OUT_ORIG

[root@<hostname>/usr/sap/<SAPSID>/SUM/abap/load/migrate_dt]# ls -lart MIGRATE_DT_CNT_00134_EXP*

-rw-r--r-- 1 <SAPSID>adm sapsys 442 Jul 29 14:18 MIGRATE_DT_CNT_00134_EXP.IN

-rw-r--r-- 1 <SAPSID>adm sapsys 374 Jul 29 14:19 MIGRATE_DT_CNT_00134_EXP.OUT_ORIG

-rw-r--r-- 1 <SAPSID>adm sapsys 374 Jul 29 14:19 MIGRATE_DT_CNT_00134_EXP.OUT

[root@<hostname>/usr/sap/<SAPSID>/SUM/abap/load/migrate_dt]#

[root@<hostname>/usr/sap/<SAPSID>/SUM/abap/load/migrate_dt]# vi MIGRATE_DT_CNT_00134_EXP.OUT

Replacing 2323031 with 2323030

Save and exit

[root@<hostname>/usr/sap/<SAPSID>/SUM/abap/load/migrate_dt]# cat MIGRATE_DT_CNT_00134_EXP.OUT

BALHDR 2323030

CNVLTRL_PORTION 0

ITS_POS 0

RSDRCRM_SEG_TEST 0

TBE32T 1

/BOFU/DPPFCNTR 0

CME_ST_R3_ATTRH 0

IUUC_2RX_ALP 0

RSCNV_BUFFER_CHA 0

TDBSELVER 0

/BCV/C_CONF_XC 0

CNVLTRL_PAR_JOBS 0

ITS_SHOW 0

RSDRCRM_SEG_QSI 0

TBE34 0

/BOFU/DO_CUST 0

CME_ST_R3_DEP 0

IUUC_2RX_ACCR 0

RSCNV_BUFFER_MAP 0

TDATS 0

/BCV/C_DASHBA 48

CNVLTRL_PARAM 0

ITS_STYLES 0

RSDRCRM_SEG_PARA 0

TBEPRI 0

[root@<hostname>/usr/sap/<SAPSID>/SUM/abap/load/migrate_dt]#

Retry the phase now

It has passed the error.

Procedure of updating oracle parameters in spfile

noreply@blogger.com (Venkata S Pagolu) — Mon, 9 Mar 2020 17:42:00 +0530

Oracle has two parameter files from which it reads while it's beginning .

They are spfile (server parameter file) and pfile (parameter file). Spfile is binary format file where manual changes are not allowed.
Below document shows us the procedure on the way to change/update the oracle parameters in spfile.

This procedure is on linux operating system.

Take a backup of pfile and spfile

Create pfile from spfile

Make the changes to the pfile by editing the file

The init<orasid>.ora file has been edited by inserting the required parameters

Stop SAP only

Shutdown DB

Startup Database in mount state by giving the pfile path

Create spfile from pfile

Shutdown DB

Start DB

Start SAP

SAP Kernel Version Upgrade 720

noreply@blogger.com (Venkata S Pagolu) — Mon, 9 Mar 2020 16:47:00 +0530

This article shows us with detailed steps to upgrade SAP Kernel to 720 version.
It includes every step to be performed for the activity.
This procedure is for linux OS.

Stop the SAP system. (You do not need to stop the database.)
Login as adm
Stopsap r3 ( if it doesn’t work use hostname with stopsap command)
Ex: Stopsap r3 SAPSID

Stop SAPOSCOL
Saposcol –k (with sidadm user)

Stop sapstartsrv
Kill -2 (with sidadm user)

If exists, unregister all standalone CCMS agents (sapccmsr [-j2ee],
sapccm4x). On Unix you can see corresponding processes
sapccm4x -u pf=
sapccmsr -u pf= [-j2ee]

Remove any IPC objects that still exist
cleanipc remove

Save old kernel before deploying new Kernel
As per sapnote we'd like to execute like below command
SAPCAR -cvf ../sapexe.tar (it wasn’t worked for me. So I took tar backup of exe dir)
As sidadm change directory to /sapmnt/SID
Execute below command
tar –cvf exe.tar exe ( we can take it as SIDexe.tar).

Delete all of the files existing in the kernel directory, including the
Subdirectories. This ensures that there are not any remaining files from
the earlier release, which have a special name in Release 7.20 or
are in a different place in a subdirectory.

Log on as user adm and switch to the directory
/usr/sap//SYS/exe/run
(Check twice on which locaton you're executing rm -rf command)
rm –rf *

Unpack the new kernel with the following commands in the same dir.

/SAPCAR –xvf R3trans_221-10007264.SAR
/SAPCAR –xvf dw_utils_220-10007264.sar
/SAPCAR –xvf R3check_210-0007264.SAR
/SAPCAR –xvf R3ldctl_221-10007263.SAR
/SAPCAR –xvf R3load_221-10007263.SAR
/SAPCAR –xvf R3szchk_221-10007263.SAR
/SAPCAR –xvf sapcpe_218-10007264.sar
/SAPCAR –xvf SAPEXEDB_201-10007263.SAR
/SAPCAR –xvf SAPCAR_2-10007272.exe
/SAPCAR –xvf SAPEXE_201-10007264.SAR
/SAPCAR –xvf tp_340-20001346.sar
/SAPCAR –xvf saprouter_212-10007264.sar
/SAPCAR –xvf SAPSLDREG_210-10007264.SAR
/SAPCAR –xvf lib_dbsl_225-10007263.sar
/SAPCAR –xvf NWRFC_11-20004549.SAR
/SAPCAR –xvf DBATL720O10_25-10007263.SAR

Delete all of the local executables from all the individual instances.
To do this, switch to the local executable directory of each instance.
/usr/sap///exe and execute

(Check twice on which locaton you're executing this command)
rm -rf *

Installing SAPHOSTAGENT

For releases 7.00 and 7.01 (7.0 Enhancement Package 1), you need to also
install the package SAPHOSTAGENT.SAR within the latest 7.20 version available
(in accordance with Note 1031096).
Extract the SAPHOSTAGENT to a temporary folder. Here in this case we have already

Extract the HOST AGENT to temporary local folder.
cd /Common//Kernel_720/KERNEL_NEW/
mkdir SAPHOSTAGENT
cd SAPHOSTAGENT
/Common//Kernel_720/SAPCAR_5-20002089.EXE –xvf
/Common//Kernel_720/SAPHOSTAGENT111_111-20005731.SAR

Switch to root user
saphostexec –install
Run SAPROOT.SH

Switch to root
cd /sapmnt//exe
./saproot.sh

Run sapcpe
As executables from the local executable directories may already be
executed for the beginning before sapcpe runs, start an initial copy of the executables.

cd /usr/sap///work
sapcpe pf=/usr/sap//SYS/profile/
sapcpe pf=/usr/sap//SYS/profile/

Post Actions

Special functions for the syslog (AS ABAP and Dual-Stack systems)
Due to things described in note 1517379, you've got to line the profile
Parameter

rslg/new_layout = 9.

If a syslog file already exists within the new format because this parameter
has not been set from the very beginning, the syslog will still be written
in the new format albeit the parameter has been set within the meantime. In
that case, the existing syslog files have to be deleted.

Dynamic work processes (AS ABAP and Dual-Stack systems)

The 7.20 kernel supports the dynamic increase of the amount of
work processes at runtime. However, this function is not fully compatible
with lower ABAP versions. To prevent errors from occurring, deactivate it
by setting the following parameters:

rdisp/wp_no_restricted = 0
rdisp/configurable_wp_no = 0
rdisp/dynamic_wp_check = FALSE

Start SAP system with new Kernel
Startsap r3 (with sidadm user)

Run sgen in productive client .

Oracle-flashback-in-12c

noreply@blogger.com (Venkata S Pagolu) — Wed, 4 Mar 2020 13:16:00 +0530

This article shows us the procedure to activate and de-activate falshback option in oracle database.
You can recover the DB with flash recovery which is very fast if you activate it and it is very useful when we are performing changes in the database

Preparations

· Please ensure the following preparations and pre-requisites are met before you enable or disable flashback.
· The flashback destination which is to be used should have enough space for flashback operations. You specify this using oracle parameter DB_RECOVERY_FILE_DEST.
· Ensure the database to be in Archivelog mode to activate flashback

Check the status of database
SQL> select log_mode, flashback_on from v$database;

Flash back parameters checks and activation

There are three parameters which needs to be set online.
SQL> show parameter DB_RECOVERY_FILE_DEST;
SQL> show parameter DB_FLASHBACK_RETENTION_TARGET;
SQL> alter system set DB_RECOVERY_FILE_DEST = '/oracle//sapdata1/flashback';
SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE = ;
SQL> alter system set DB_FLASHBACK_RETENTION_TARGET = 1440;

Enabling flashback for the database and creating restore point

SQL> alter database flashback on;
SQL> create restore point ;
Issue below sql statement to check if already the Flashback process is running
SQL> select * from v$bgprocess where name='RVWR';
# ps –ef | grep rvwr
You can use the following command to check the restore points created and its size
SQL> SELECT NAME, SCN, TIME, DATABASE_INCARNATION#, GUARANTEE_FLASHBACK_DATABASE, STORAGE_SIZE FROM V$RESTORE_POINT;

DISABLE Oracle Flashback

SQL> alter database flashback off;
At now if there are any guaranteed restore point, flashback status will show as Restore Point Only unless you delete the restore point manually.

IMP: Always drop the restore points when there's a confirmation that the flashback restore point is not any more needed for the project cutover

SQL> drop restore point TOP_CUTOVER;

Perform Flashback of database

Before performing Flashback please make sure that you've got all the redo logs generated after enabling the flashback as these are needed to perform Flashback.

Stop database
SQL> shutdown immediate;

Start DB in no mount mode
SQL> startup mount exclusive;

Go back to guaranteed restore point:
SQL> FLASHBACK DATABASE TO RESTORE POINT ‘top_cutover;

Go back to different point in time:
SQL> FLASHBACK DATABASE TO SCN ;
SQL> FLASHBACK DATABASE TO TIMESTAMP to_timestamp('YYYY-MM-DD HH24:MI:SS');

Flashback recovery is like incomplete media recovery, so open DB with
SQL> alter database open resetlog

Dealing with BW Nologging indexes post BW refresh

noreply@blogger.com (Venkata S Pagolu) — Wed, 4 Mar 2020 12:26:00 +0530

This document is to elucidate the rebuild the indexes post BW refresh for the indexes which are in “Nologging” mode.

AIM:

Required to rebuild the indexes after the BW system restore. Because in BW systems there'll be many indexes which are in “Nologging” mode, at the time of recovery they're going to not recover for more details please refer the (SAP Note: 547464), because of that you will get the errors like:

Block Checking: DBA = 48887003, Block Type = Found block already

marked corrupted

Block Checking: DBA = 48887004, Block Type = Found block already

marked corrupted

Procedure:

1. Copy the SQL code from the provided SAP note to the server with extension “.sql” (eg: generate_rebuild_only_by_time.sql)

2. Execute the generate_rebuild_only_by_time.sql with the 3 or 4hrs time stamp before the backup start time which you have taken for the restore (eg: if your backup start time 2019-08-15-05:00:00 execute the script like “@generate_rebuild_only_by_time.sql 2019-08-15-02:00:00”).

3. It generates another script which looks like “generated_script.sql” in the same location where we ran that “generate_rebuild_only_by_time.sql”. script “generated_script.sql” consists the alter index commands for all the indexes which are within the “Nologging” mode.

4. Execute the “@generated_script.sql” for rebuilding all the indexes.
After succesful completion of the index rebuild, run the below reports in your BW system:

a. execute SAP report RSAR_PSA_PARTITION_CHECK with the options which as shown in the below snapshot

b. SAP_INFOCUBE_INDEXES_REPAIR

sybase shutdown commands and usage

noreply@blogger.com (Venkata S Pagolu) — Fri, 21 Feb 2020 15:57:00 +0530

This article shows us the various shutdown methods of ASE database from isql prompt

1. Normal Shutdown of ASE DB: Adaptive Server will be shut down from which the shutdown command is issued
Usage
>shutdown
>go

2. Shutdown with no wait: Adaptive Server will be shut down immediately
Usage
>shutdown with nowait
>go

3. shutdown SYB_BACKUP: Shutdown local backup server
usage
>shutdown SYB_BACKUP
>go

4. shutdown REM_BACKUP: Shutdown remote server backup
usage
>shutdown REM_BACKUP
>go

5. shutdown cluster: Shuts down the current cluster
usage
>shutdown cluster
>go

6. shutdown ase1: Instance “ase1” will be shut down leaving the cluster running
usage
>shutdown ase1
>go

Restore and recover ASE databse

noreply@blogger.com (Venkata S Pagolu) — Fri, 21 Feb 2020 15:43:00 +0530

This article helps us with the procedure of Restore and Recovery of Sybase ASE database

Before Loading (restore) and recover, ensure that no-one is connected to DB using below command

isql -Usa -STST -w300 -P -X

> (Provide password)

>sp_who

>go

Once you confirm that anyone is not connected to DB, then start loading the database
Load database from "

example

>Load database TST from "/Dumpdir/TST_bkp1.dmp"
>stripe on "/Dumpdir/TST_bkp2.dmp"
>stripe on "/Dumpdir/TST_bkp3.dmp"
>go

once database is loaded, we've two options here

1. Bring the database online

2. Recover the database.

As i might wish to means the recover option also, we'll accompany second option

recover the database using below command

>load transaction TST from "/Dumpdir/TST.trn
>with until time= 'January 16, 2019 10:32 am
>go

Up on the recovery of database, bring the database online using below command

>online database TST
>go

your database in now online.

Reconfiguring Public-key certificates

noreply@blogger.com (Venkata S Pagolu) — Thu, 20 Feb 2020 12:32:00 +0530

This article shows the procedure to re-configure public key certificates post refresh/migrations

Procedure:

Run Netweaver administrator and go to configuration management --> Security tab and select Certificates and Keys

Select the TicketKeystore entry and delete the SAPLogonTicketKeypair and SAPLogonTicketKeypair-cert entries in "Key Storage view details" section at rock bottom of the page

Create a brand new Key pair and Public Key certificate

Click Create

Enter the following information

Entry Name: SAPLogonTicketKeypair

Algorithm: DSA

Key Length: 1024

Store Certificate: Ensure checked

Click next and enter

countryName: DE

organizationalUnitName: J2EE

comonName:

Click Next

Click Finish

Export the certificate:

Select the SAPLogonTicketKeypair-cert entry and click export entry

Click on the download link

Click save (and save it to a local file)

Import certificate:

Login to SAP system and run transaction STRUST.

Import the certificate just exported (Menu path Certificate --> Import). Make sure that the file format is that the same as that wont to export the certificate

Click on Add to Certificate list.

Your public key is ready now

Edit INTEGRATION_SERVER Business

noreply@blogger.com (Venkata S Pagolu) — Thu, 20 Feb 2020 12:23:00 +0530

This document allows us to understand the procedure of editing Integration server business in SAP PI/PO system.

Procedure:

Edit Business system INTEGRATION_SERVER_<SOURCE_SID> in the SLD and adjust to use the <TARGET_PI> technical system

Access the SLD in <TARGET_PI> and select Business systems

Locate the entry INTEGRATION_SERVER_<SOURCE_SID>

Go to the small print screen and choose the integration tab

For the technical system line, click on Change

Change the system to <TARGET_PI> and select the correct client in <TARGET_PI>

Click on the save button

Fix the pipeline URL and the configuration URL to point to <TARGET_PI>. don't make any changes to the Group to be updated by the PI Apps team

Click on the associate with XI button then click save

On the installed software tab, make sure that the installed checkbox for SAP Netweaver PI product is ticked and click on save

Restore the JAVA system connections and destinations as PI refresh post action

noreply@blogger.com (Venkata S Pagolu) — Thu, 20 Feb 2020 12:19:00 +0530

This procedure is one among the post refresh action of SAP PI/PO system.
It explains on the way to restore the Java system connections (JCO) and destinations post refresh.

Run the NWA and access “Jco RFC Destinations” (Menu path à Configuration Management--> Connectivity--> Jco RFC provider).

For every connection, set the configuration details from details taken before;

Delete all the Jco connections for the <SOURCE_PI> System (*_<SOURCE_SID>), replacing them with connections for <TARGET_PI>.

Access “SLD Data Supplier Destinations” (Netweaver admin: Configuration Management-->Connectivity-->Destinations).

Update all connections with the data saved prior to the refresh. Use the ping option to test each connection

Check the connections in the ABAP engine using transaction SMGW (Goto --> Logged on Clients)

All connections should be for <TARGET_SID>

Change all spool servers to the new one

noreply@blogger.com (Venkata S Pagolu) — Thu, 20 Feb 2020 12:13:00 +0530

Spool server is the one in which all the network printers are assigned. it has to be reassigned in below cases.

system refresh
migrations
If spool server is changed

Below is the procedure to change the spool server assignment to new one.

Run Transaction SPAD and from the menu àutilities->for output devices->assign server.

Enter the following;

Output device *

Old spool server *

New spool server <click on the drop down box and select>

Display list

Reconfigure the transport system as post refresh task

noreply@blogger.com (Venkata S Pagolu) — Thu, 20 Feb 2020 12:10:00 +0530

Below procedure shows us on the way to re configure TMS within the refreshed system.

With user DDIC, logon to STMS Domain Controller in client 000
Choose System Overview
Delete from the transport domain

Logon to 000 client with DDIC user
Run transaction STMS
Enter details as appropriate
Save

On STMS Domain Controller

Run transaction STMS again
Select and approve back into the transport system.

Choose System Overview – Select , Extras -> Distribute & Activate Configuration

Also, check and correct the transport routes

Now TMS configuration is prepared within the refreshed system.

Secure store Key Phrase

noreply@blogger.com (Venkata S Pagolu) — Thu, 20 Feb 2020 12:00:00 +0530

Below command is required to see secure store key phrase during Java export.
If we don’t have the key phrase, the export taken is of no use.
This is the most pre-requisite for Java migration (export/import) procedure.

Check the key phrase as follows;

cd <Global directory>

Execute below command from the global directory

/sltools/checkKeyPhrase.sh -f /security/data/SecStore.properties

Enter the phrase when prompted and you ought to get the message "The key phrase is correct." if you've got entered the right value

This will be essential during the system copy phase

Note: If Keyphrase is not correct, we need to solve it before exporting Java DB.

SAP Host agent auto upgrade procedure

noreply@blogger.com (Venkata S Pagolu) — Tue, 18 Feb 2020 15:57:00 +0530

We should maintain latest version of saphostagent in sap environment as solman gets the info from satellite systems wit the assistance of saphostagent.

This topic is to point out the feature to upgrade saphost agent automatically without manual intervention.
Only thing is we'd like to form sure the SAR file is downloaded and staged within the auto_upgrade directory.

Procedure to enable Auto-Upgrade feature for SAP Hostagent

SAP Hostagent has an auto upgrade feature which may be enabled as per note 1473974.

Please add the subsequent Parameters to SAP Hostagent Profile file for Linux (/usr/sap/hostctrl/exe/host_profile).

hostexec/autoupgrade_delay = 1440

DIR_NEW = //SAP/SAPHOSTAGENT/Linux/auto_upgrade

service/EnableRemoteDeployment = true

service/protectedwebmethods = NONE

1440 in hostexec/autoupgrade_delay is mentioned in minutes which translates to 24 hours (24*60 = 1440)

For Windows and HP-UX, use below paths present.

*DIR_NEW=//SAP/SAPHOSTAGENT/HP-UX/auto_upgrade

*DIR_NEW=//SAP/SAPHOSTAGENT/Windows/auto_upgrade

Note: Please restart Hostagent with below command for the parameters to require effect.

As root

Change to below dir

/usr/sap/hostcontrol/exe

./saphostexec -restart

If these parameters are activated, Hostagent automatically takes care of the upgrade by checking the trail mentioned in DIR_NEW and initiated an upgrade automatically when there's a replacement version available in this directory.

SAP GUI SNC Configuration

noreply@blogger.com (Venkata S Pagolu) — Tue, 18 Feb 2020 15:39:00 +0530

Below mentioned configuration is essential to enable the secure network communications (SNC) between SAP GUI and SAP ABAP systems.

Prerequisites:

Along with SAP BASIS related transcations, we'd like below additional transactions.

SNCCONFIG

SNCWIZARD

We also need below details

SAP System ID

Fully qualified message server hostname

Installation number

CommonCryptoLib version must be at least CommonCryptoLib 8.5.2.

snapshots of SAP instance, default profiles,SNCCONFIG and STRUST settings.

Transaction RZ10 > Import the most recent version of profiles

Take backup of profiles at OS level

Procedure:

Configure SNC

Transaction RZ10 > Import the newest version of profiles

Transaction SNCWIZARD

Continue

Copy and paste the details like SNC identity parameter generated by the wizard here:

p:CN=, OU=, OU=SAP Web AS, O=SAP Trust Community, C=DE

Replace the parameter value with the subsequent format, per your client CA requirement:

p:CN=, OU=, L=, O=, SP=, C=, EMAIL=<email>

Please note:

The message server host is defined within the SAP Logon pad.

The installation number, OU=, is unique to each SAP environment.

Continue

Continue

Continue

If you are prompted to configure Kerberos Credentials, click on Skip.

Continue

Transaction STRUST opens in a separate window.

Expand folder and double-click on SNC SAPCryptolib

The self-signed SNC SAPCryptolib certificate created via SNCWIZARD earlier occurs here.

Click on to Create Certificate request

Select all and replica the certificate (without empty lines)

Paste in Notepad (without empty lines) and reserve it as “_SNC.csr”.
Exit transaction STRUST and return to SNCWIZARD

Complete

Request client signed certificate

Update DEFAULT.PFL

While expecting the signed certificate, update the subsequent parameters in DEFAULT.PFL.

Verify the file libsapcrypto.so exists on the OS level, in /usr/sap//SYS/exe/run directory.

Transaction RZ10

Parameter Required value

snc/gssapi_lib usr/sap//SYS/exe/run/libsapcrypto.so

spnego/enable 0

Save changes.

Need to restart SAP application once parameter changes are done..

Import client signed certificates (*.p7b file)

Double-click to open the *.p7b file

Expand certificates

It contains 3 certificates - Issuing, Root & Server.

All 3 certificates must be exported and combined in a single text file. Here is how …

Right click on the server certificate “<host>.<domain>.com” > All Tasks > Export in Base-64 encoded X.509 format, save each *.cer to your desktop location.

Next

Select “Base-64 encoded X.509 (.CER)” > Next

File name = Next

Finish

OK

Repeat an equivalent steps above to export "root" and "issuing" certificates

Close the certmgr screen.

Open each *.cer file with Notepad, combine all 3 certificates into 1 document , during this specific order - server, root and issuing.

Delete any extra empty lines or carriage returns.

Then, save as a text file. For example: __signed.txt

Login to SAP system

Execute transaction STRUST

Click on to switch to change mode

Expand folder and double-click on SNC SAPCryptolib

Under Own Certificate, select "Import certificate response"

Copy and insert the certificate chain - server, root & issuing, confirm there are not any empty lines at the start and end of the file.

Continue

SNC certificate is now signed.

Click on to save changes.

Restart SAP after succesful SNC configuration, Update the GUI entry and test SNC connection.

BW on HANA migration procedure

noreply@blogger.com (Venkata S Pagolu) — Tue, 18 Feb 2020 14:56:00 +0530

BW on HANA important SAP links

Below Links are considerably useful to urge the complete information on preparation, execution and post processing. Please undergo the links and obtain an summary on BW on Hana migration.

http://scn.sap.com/community/hana-in-memory/blog/2014/02/25/where-to-find-information-on-sap-bw-on-hana-migrations

http://scn.sap.com/community/netweaver/blog/2015/01/06/migrating-sap-bw-to-sap-bw-on-hana--a-guide-for-sap-basis-architects--part-1-the-workshop

https://scn.sap.com/community/standards/blog/2014/03/23/bw-on-hana--pre-migration-activity

http://scn.sap.com/community/bw-hana/blog/2014/02/19/bw-pre-and-post-upgrade-and-migration-tasks

http://sapinsider.wispubs.com/Assets/Blogs/2013/June/76-steps-in-a-BW-to-HANA-migration-Workplan

https://www.sap-press.com/implementing-sap-bw-on-sap-hana_3609/

http://scn.sap.com/docs/DOC-7856

Connection to partner 'sapserver:sapdp00' broken (NIPING); WSAECONNRESET: Connection reset by peer

noreply@blogger.com (Venkata S Pagolu) — Tue, 7 Aug 2018 18:02:00 +0530

Below info is used for troubleshooting intermittent connection issues with in SAP system.

In general, intermittent connection loss occurs with below two reasons

1. If there is a crash in the dispatcher process of the instance to which the client was connected.

2. Network Problems (Firewall idle timeout, Black Hole Router, VPN, WAN problems)

For first case, if there is a crash with dispatcher process, This triggers a TCP package with an activated RST flag, which is sent to all connected communication partners and triggers the error message described above in the SAP GUI, among others. All connections will then automatically broken.

For second case, regarding network problems, we need to perform checks with NIPING which tests the performace of packet transmission in TCP layer.

NIPING generally checks the packet transmission in TCP layer of the network where all SAP transactions takes place.

we may not see any packet loss while we ping the servers from terminal and vice-versa. but if you see errors in NIPING trace, you need to fix it based on the error. Mostly it will be of network issue and some times it may be due to OS.

To check the connectivity using NIPING tool, We need to start NIPING server at SAP level and trigger the NIPING packet transmission from the frontend terminal.

Use below commands

To do this test, it is required to start NIPING as a server in one host:

> niping -s -I 0 -T NIPING_SERVER_TRACE

In the remote host is is required to start NIPING as a client:

> niping -c -H <SAP HOST NAME> -X3 -B 10 -D 30 -T NIPING_CLIENT_TRACE

Also check dispatcher logs of all the application servers.

we need to get below details from the user

SAP GUI version and patch level
Windows version and patch level
If they had done any upgrades at frontend like windows and sapgui
If they are facing issue with any particular transactions or for every transactions
If they are facing issue during particular time
How are they connected to SAP system, using any VPN or direct client network
Are they facing issue with SAP only or with any other applications are also crashing
If they are using wired connection or wireless.

Incorrect SLD security role assignments after upgrade

noreply@blogger.com (Venkata S Pagolu) — Tue, 13 Mar 2012 21:00:00 +0530

If you experience SLD permission issues after an upgrade for users that worked fine before the upgrade, confirm that each one SLD roles are configured properly. This can be done in the following manner:

1. Log on to http://:/useradmin of the AS Java hosting your SLD.

2. within the search criteria select the entry "Role" from the dropdown menu and enter "SAP_SLD_*" as a filter.

3. Perform the subsequent steps to see the configuration of every SLD role consistent with the small print within the attached Word document:

a) Select a role.

b) within the details pane, select tab strip "Assigned Actions".

c) Compare the assigned actions with the list of actions defined in the Word document.

d) If one or more actions are absent, click button "Modify" and add the missing actions.

e) Save any changes you made.

4. Log on to http://:/sld,

navigate to "Administration" - "Settings" and click on the button "Perform Role Mapping".

This will refresh the mapping of SLD UME roles to SLD user groups to make sure that this mapping is correct, too.

PI service users locked

noreply@blogger.com (Venkata S Pagolu) — Fri, 24 Feb 2012 22:56:00 +0530

PI service users comes default with the installation and exists along side the password within the client of Integration server and exchange profile.
They are utilized in the PI environment for dialog free communication between central components of Netweaver usage type PI and also between app servers and PI

Below are the roles assigned to them

Service User	Description	Assigned Role
PILSADMIN	User for the Change Management Server	SAP_XI_CMS_SERV_USER
PIREPUSER	User for the Enterprise Services Repository	SAP_XI_IR_SERV_USER_MAIN
PIDIRUSER	User for the Integration Directory	SAP_XI_ID_SERV_USER_MAIN
PILDUSER	User for the System Landscape Directory (SLD)	SAP_BC_AI_LANDSCAPE_DB_RFC
PIAPPLUSER	User for sender applications	SAP_XI_APPL_SERV_USER
PIRWBUSER	User for the Runtime Workbench	SAP_XI_RWB_SERV_USER_MAIN
PIAFUSER	User for the Advanced Adapter Engine	SAP_XI_AF_SERV_USER_MAIN
PIISUSER	User for the Integration Server	SAP_XI_IS_SERV_USER_MAIN
PIPPUSER	User for principal propagation	SAP_XI_APPL_SERV_USER

These users will be maintained in different connections and transactions. Inorder to change the passwords, we need to change them in all those connections and transactions.

There is a typical procedure to vary the passwords of those users provided by SAP.

We need to follow the procedure from below notes for changing the passwords supported your PI version.

999962 - PI 7.10 and higher: Change passwords of PI service users

2474153 - How to change passwords of PI service users in Java Only PI system

936093 - PI: Change to passwords of PI service users

721548 - XI 3.0: Changing the passwords of the XI service users

Client deletion procedure

noreply@blogger.com (Venkata S Pagolu) — Thu, 23 Feb 2012 12:17:00 +0530

Client is a business unit in SAP system. we can see three standard clients which usually comes with the installation of SAP system. 000,001 and 066

066 is early watch client and now a days it's of no use as solman is mandatory.
So in such cases, we may have to delete the clients 066 and 001.
Below is the procedure for deleting client.

Client deletion through scc5

First log within the client you'd wish to delete with username as SAP* and password as pass if you're logging into that client for the primary time.

Use transaction code SCC5 and select the check box which says Delete entry from T000 and click on start immediately... you will get the prompt if you can continue, click continue and wait till it deletes the client.

Once the client is deleted, login to 000 Client and issue the transaction code SCC4 to see if the deleted
client is listed within the list or not... If it's unlisted then you've got successfully deleted a client.

Client deletion through R3trans

1)logon to system as SAP Admin

2)goto /user/sap/trans/bin dir

3)use standard editor to create a control file
with ctl ext(eg. delcli.ctl) with following text
clientremove
client=xxx
select*

4) run the commnd on command field
r3trans -w delcli.log -u1delcli.ctl

Notes regarding client deletion

Note 70643 - CC-TOPIC: Client Deletion (SCC5)

Note 35952 - Client deleted, space still filled in database

Reprocessing and Deletion of IDOC

noreply@blogger.com (Venkata S Pagolu) — Fri, 17 Feb 2012 17:41:00 +0530

IDOCs are Intermediate Documents which are used for the communication between two SAP systems which can be having the encoded data which SAP system only can read.

IDOCs will be getting transferred between SAP systems and will sometime fails due to the lack of resources or due to queue stuck etc.

In such situations, we'd like to reprocess the idocs. Below are the steps which shows us to re-process/flag the IDOCs in SAP system.

How to reprocess an Idoc:

1. Go to transaction BD87

2. Enter Idoc number, and make sure the dates are correct

3. Click the Execute button or press F8

4. To reprocess, select the Idoc status within the "IDOC in inbound processing" tree.

5. Click the Process button

6. the subsequent screen will give the status of the IDOC and wheter it processed sucessfully

How to flag an Idoc to be deleted:

1. Go to transaction BD87

2. Enter Idoc number, and make sure the dates are correct

3. Click the Execute button or press F8

4. To delete, select the Idoc status within the tree and click on EDIT -> RESTRICT AND PROCESS

5. Click the Execute button

6. Un-check the Bkgd Processing checkbox.

7. Click the Execute button

8. Click the Delete Flag button.

Administration of IDoc Communication

noreply@blogger.com (Venkata S Pagolu) — Fri, 17 Feb 2012 14:13:00 +0530

IDoc communication is predicated on transactional Remote call (tRFC).

You can optimize the performance of ALE processing by using the subsequent settings and procedures.

Suppressing Background Processing
If tRFC errors occurs in the standard SAP system, , a background job is generated to re-establish the connection. In certain circumstances this might end in an outsized number of background jobs being started that completely block backgrounding .

Note:
Use program RSARFCEX to restart tRFC to cancel a background job if tRFC errors occur .

Select a connection to change in ALE Customizing (transaction SALE),

Communication

Create RFC Connections (SM59)

Choose Destination ® tRFC Options and select the option Suppress Background Job at Comm. Error.

Setting Dispatch Status to OK
When an IDoc is passed to the communication layer, it's assigned a globally unique transaction identifier (TID). If the IDoc has been successfully dispatched, this information isn't automatically passed to the ALE communication layer. So that ALE processing sets the IDoc status to Dispatch OK, you ought to compare the TID numbers within the communication layer and therefore the ALE layer.

The SAP program RBDMOIND checks that the IDocs passed to the tRFC have already been sent to the receiving SAP system. If they need been sent, the IDoc status is modified to "12" - Dispatch OK

Note:
To set the IDoc dispatch status, run the program RBDOIND after the IDocs are passed to the communication layer.

Checking the tRFC Status

Use
Transactional RFC calls which transfer IDocs use the function module IDOC_INBOUND_ASYNCHRONOUS at reception (before release 4.0: INBOUND_IDOC_PROCESS).

If an IDoc in the sending system has been passed to tRFC (IDoc status "03"), but has not yet been input in the receiving system, this means that the tRFC call has not yet been executed.

Activities
To check the status of the tRFC calls, select Tools -> IDoc Interface/ALE -> Administration -> Monitoring -> Troubleshooting -> RFC Queue (SM58) and setout any additional selection criteria.

The program RSARFCEX restarts unsuccessful tRFC calls.

Note:
You cannot choose the choice is being executed in backgrounding .