2026년 8월 20일 목요일

ha script

 ########################################################################

# (c) Copyright 2006-2009, 2016-2017, 2020 Hewlett Packard Enterprise Development LP

# @(#) Serviceguard UPCC Package Configuration Script Template

# @(#) Product Name                :  HPE Serviceguard

# @(#) Product Version             :  A.12.80.03

# @(#) Patch Name                  :  

#

# **********************************************************************

# *                                                                    *

# *  This script is a template that can be used when creating a        *

# *  customer defined script.                                          *

# *                                                                    *

# *  Once created, this script can be configured into the package      *

# *  configuration file with the "external_script" and                 *

# *  "external_pre_script" parameters. Note that the respective        *

# *  "sg/external" and the "sg/external_pre" module need to be         *

# *  specified in the package configuraton file in order to            *

# *  configure these parameters. The master control script will        *

# *  then invoke the script at the pre-defined entry point among       *

# *  Serviceguard provided scripts depending on the parameter used.    *

# *                                                                    *

# *  This script replaces the existing "customer_defined_run_cmds()"   *

# *  and  "customer_defined_halt_cmds()" functions in the pre-11.18    *

# *  control script.                                                   *

# *                                                                    *

# *                            ---------                               *

# *                            I N P U T                               *

# *                            ---------                               *

# *  The script should expect the following parameters when called     *

# *  by the master control script:                                     *

# *                                                                    *

# *      $1 : script action or operation - start, stop or validate     *

# *      $2 : a temporary file name containing the package specific    *

# *           environment variables. This parameter is optional for    *

# *           "start" and "stop" action.                               *

# *                                                                    *

# *                           -----------                              *

# *                           O U T P U T                              *

# *                           -----------                              *

# *  The script should exit with the following values:                 *

# *                                                                    *

# *      0  : if success                                               *

# *      1  : When the package should not be restarted as a result of  *

# *           failure in this script.                                  *

# *      2  : When package should not restart on the local node, but   *

# *           can be restarted from another node.                      *

# *                                                                    *

# *             -----------------------------------------              *

# *             E N V I R O N M E N T   V A R I A B L E S              *

# *             -----------------------------------------              *

# *  The following environment variables are exported by the package   *

# *  manager or the master control script:                             *

# *                                                                    *

# *      SG_PACKAGE        : name of the package to operate on         *

# *                          (available at package run and halt        *

# *                          time only. At package validation time,    *

# *                          SG_PACKAGE_NAME can be used as a          *

# *                          substitute.)                              *

# *      SG_NODE           : name of the node the script is invoked on *

# *                          (available at package run and halt        *

# *                          time only, not at package validation      *

# *                          time.)                                    *

# *      SG_SCRIPT_LOG_FILE: name of the package log file              *

# *                          (available at package run and halt        *

# *                          time only, not at package validation      *

# *                          time.)                                    *

# *      SG_UTILS          : name of the utility function file         *

# *                          located at:                               *

# *                          $SGCONF/scripts/mscripts/utils.sh         *

# *                          (exported by the master control script)   *

# *      SG_ENV_FILE       : temporary file which contains the         *

# *                          package parameters in a posix shell       *

# *                          format. The file can be passed in as      *

# *                          an argument, or generated by the          *

# *                          function sg_source_pkg_env, that invokes  *

# *                          the command cmgetpkgenv (see man page     *

# *                          for details).                             *

# *                          (exported by the master control script)   *

# *                                                                    *

# *                ---------------------------------                   *

# *                U T I L I T Y   F U N C T I O N S                   *

# *                ---------------------------------                   *

# *  The following utility functions are sourced in from $SG_UTILS     *

# *  ($SGCONF/scripts/mscripts/utils.sh) and available for use:        *

# *                                                                    *

# *      sg_log <log level> <log msg>                                  *

# *                                                                    *

# *          By default, only log messages with a log level of 0 will  *

# *          be output to the log file. If parameter "log_level" is    *

# *          configured in the package configuration file, then log    *

# *          messages that have a log level that is equal to or        *

# *          greater than the configured log level will be output.     *

# *                                                                    *

# *          In addition, the format of the time stamp is prefixed in  *  

# *          front of the log message.                                 *    

# *                                                                    * 

# *                                                                    *

# *      sg_source_pkg_env <operation> [<pkg environment file>]        *

# *                                                                    *

# *          source in the package specific environment variables      *

# *                                                                    *

# **********************************************************************

#

########################################################################


###########################

# Source utility functions. 

###########################


if [[ -z $SG_UTILS ]]

then

    . /etc/cmcluster.conf

    SG_UTILS=$SGCONF/scripts/mscripts/utils.sh

fi


if [[ -f ${SG_UTILS} ]]; then

    . ${SG_UTILS}

    if (( $? != 0 ))

    then

        echo "ERROR: Unable to source package utility functions file: ${SG_UTILS}"

        exit 1

    fi

else

    echo "ERROR: Unable to find package utility functions file: ${SG_UTILS}"

    exit 1

fi


###################################################################

#

# Get the environment for this package through utility function

# sg_source_pkg_env().

#

###################################################################


sg_source_pkg_env $*


#########################################################################

#

# validate_command

#

# This function should define actions to take when the package is

# being validated during cmcheckconf/cmapplyconf on all the configured

# package nodes.

#

#########################################################################


function validate_command

{


    # Output messages will only be displayed in STDOUT, if there is

    # any error condition while executing the master control script

    # with a "validate" parameter from cmcheckconf/cmapplyconf command


    sg_log 5 "validate_command"


    # ADD your package validation steps here


    return 0

}



#########################################################################

#

# start_command

#

# This function should define actions to take when the package starts

#

#########################################################################


function start_command

{


    sg_log 5 "start_command"


    # ADD your package start steps here



       if [ "${HOSTNAME}" = "gerpap1" ]; then


         su - sgpadm -c "/usr/sap/SGP/SYS/exe/uc/linuxx86_64/sapcontrol -nr 00 -prot NI_HTTP -function StartService SGP"

         sleep 5

         su - sgpadm -c "/usr/sap/SGP/SYS/exe/uc/linuxx86_64/sapcontrol -nr 00 -prot NI_HTTP -function Start"


       fi   


    sleep 30

    su - sgpadm -c "sapcontrol -nr 02 -function RestartInstance"


    return 0

}


#########################################################################

#

# stop_command

#

# This function should define actions to take when the package halts

#

# It's recommended that the actions performed in this function should be 

# made idempotent, that is if the halt action has already been performed 

# successfully before, it should not generate an error, but exit successfully.

#

# All SG provided scripts are currently idempotent.

#

#########################################################################


function stop_command

{


    sg_log 5 "stop_command"


        if [ "${HOSTNAME}" = "gerpap1" ]; then


          su - sgpadm -c "/usr/sap/SGP/SYS/exe/uc/linuxx86_64/sapcontrol -nr 00 -prot NI_HTTP -function Stop"

          sleep 5

          su - sgpadm -c "/usr/sap/SGP/SYS/exe/uc/linuxx86_64/sapcontrol -nr 00 -prot NI_HTTP -function StopService"

          su - sgpadm -c "/usr/sap/SGP/SYS/exe/uc/linuxx86_64/cleanipc 00 remove"


         fi  


    # ADD your package halt steps here


    return 0

}


################

# main routine

################


sg_log 5 "customer defined script"


#########################################################################

#

# Customer defined external script must be specified with three required 

# entry points: start, stop, and validate. 

#

# It's not recommended to add additional entry points to the script

# due to potential name space collision with future Serviceguard releases.

#

#########################################################################


typeset -i exit_val=0


case ${1} in

     start)

           start_command $*

           exit_val=$?

           ;;


     stop)

           stop_command $*

           exit_val=$?

           ;;


     validate)

           validate_command $*

           exit_val=$?

           ;;


     *)    

           sg_log 0 "INFO: Unknown operation: $1"

           ;;

esac


exit $exit_val


SUM Downtime 수행시간 비교

 << 1차 업그레이드 테스트 SUM Downtime >>





<< 운영 업그레이드  SUM Downtime >>





1차 업그레이드 테스트 대비 약 15시간 이상 단축 시킴


QA 시스템 구축시 사전 export / import 스크립트

 export

client=ALL

file='/usr/sap/trans_tgd/syscopy/EXP.dat'

delete from RFCDESSECU

select * from RFCDESSECU

delete from RFCATTRIB

select * from RFCATTRIB

delete from RFCCHECK

select * from RFCCHECK

delete from RFCGO

select * from RFCGO

delete from RFCTA

select * from RFCTA

delete from RFCDES

select * from RFCDES

delete from RFCDOC

select * from RFCDOC

delete from RFCSTXTAB

select * from RFCSTXTAB

delete from RFCSYSACL

select * from RFCSYSACL

delete from RFCTRUST

select * from RFCTRUST

delete from RFCTYPE

select * from RFCTYPE

delete from RFCCMC

select * from RFCCMC

delete from RSECACTB

select * from RSECACTB

delete from RSECTAB

select * from RSECTAB

delete from DBCON

select * from DBCON

delete from DBCONUSR

select * from DBCONUSR

delete from devaccess

select * from devaccess

delete from rzllitab

select * from rzllitab

delete from rzlliclass

select * from rzlliclass

delete from sxroute

select * from sxroute






import 
client=ALL
file='/usr/sap/trans_tgd/syscopy/EXP.dat'

SAP 작업 노트

 




/H/116.121.26.185/S/sapdp99/H/169.145.197.110/S/sapdp99/H/notesdownloads.sap.com

/H/116.121.26.185/S/sapdp99/H/169.145.197.110/S/sapdp99/H/documents.support.sap.com


/H/116.121.26.185/S/sapdp99/H/169.145.197.110/S/sapdp99/H/apps.support.sap.com




The TCIs are available in the following SPs of respective releases. If a system is in any of the following SPs or 

above SPs, then implementing the bootstrap is not needed:



S0022909736 / 1QAZ@WSX









SAPGUI 770 => S4HANA 2025 테스트

SAPGUI 800 32 bit







Implement the note to get the S/4HANA Simplification Item Checks.


Process to implement this note and the TCI's:

(Please note that this is a step by step approach - the correct order is important)


Ensure the SPAM version is 71 or above.

a) Perform the preparation tasks described in the attachment "TCI_for_Customer.pdf" from note 2187425.

b) Please also activate the rollback functionality of the TCI's (also described in the attachment "TCI_for_Customer.pdf").

Please read this point carefully:

-If the system has no direct access to SAPOSS (this is the case if you cannot download notes in SNOTE directly and you need to upload notes manually)

-and if your SAP_BASIS  version is lower than 731 (SAP_BASIS < 731):

Only if both above conditions are true then download (and do not implement) note 1995550 and note 2408383 after TCI enablement (this solves an error that can happen during the conversion and needs to be done independently to the TCI enablement). Please no not implement the notes 1995550 and 2408383 in SAP_BASIS < 731, only download it.

Ignore this step if any of the both conditions from this step 3 do not fit.

Implement note 2499199 if applicable after TCI enablement.

If SAP Download Service is enabled you can skip the points 5. and 6. and continue with 7.

Otherwise download the correction instructions of note 3674234 that are relevant for your corresponding SAP_APPL and ECC-DIMP or S4CORE release as a local file to your PC (you'll find either S4CORE alone or SAP_APPL and ECC-DIMP component in your system). Required are the .SAR files e.g.: "K61800CCPSAPAPPL.SAR"

Upload the .SAR files from 5. to your system via the transaction SPAM (from front end server) or via SNOTE->GoTo->Upload TCI. Then continue with step 7 (cause the files will be implemented via the SAP note). 

De-Implement SAP note 2502552 (if already implemented).

Download and implement the TCI 3674234 afterwards via SNOTE.

Implement SAP note 2502552 now (after 3674234).

Afterwards you can execute the report "/SDF/RC_START_CHECK" to get the check results of the SAP S/4HANA conversion checks for SAP S/4HANA 1809 and above. The report is delivered with note 2399707.

For the most accurate results please execute the report in client 000.





Solution

Implement this note for the Version 13 of the SI-Check Classes. Please also implement note 2502552 afterwards and 2399707 for the entire scope of the checks (they all belong together)


See the description of note 2502552 for details on how to implement this TCI-note.


Download the correction instruction from this note to your computer and upload it via SPAM -> "Support Package" -> "Load Packages" -> "From Front End" / or SNOTE -> Goto -> "Upload TCI" to the SAP system. Download only the packages that are relevant for your corresponding software component version of SAP_APPL and ECC-DIMP or S4CORE


This is the 13h TCI note with the checks for the SI-Check Framework. This TCI's do also contain the entire corrections delivered with the previous TCI notes. The previous TCI notes will become obsolete when implementing this note.

(Previous notes are 2418800, 2503309, 2538018, 2598422, 2617167, 2708143, 2741379, 2761703, 2910131, 3028788, 3143951, 3304656)





097 Error when verifying the digital signature of SAP Note file &

098 Digitally signed SAP Note & uploaded in version &

166 Invalid SAP Note file type (&)

167 Could not get path to executable SAPCAR file

168 SAP note file too big

169 No authorization to write to &1

170 Path &1 is invalid

171 Error when reading the ZIP content of the file &

172 Could not delete file &

173 Error when verifying issuer of digital signature of note file &

174 Error when verifying type of digital signature of note file &

175 Could not read files from path &1

176 Uploaded SAR file does not have an SAP Note number

177 No application log can be displayed for SAP Note &

178 Enter the SAP Note number

179 All files with reference to note deleted from directory &

180 No files with reference to note found for deletion in directory &

181 Cannot expand application server directory &




Please follow the below instruction to create the structure in SCWN Package.


1. Go to transaction SE11 and select the Data type radio button.

2. Enter the name CWBNTKEYTSTAMP and clock on create button.

3. From the popup choose structure and press ok.

4. Enter the short description as "Key for OSS Notes with       Timestamp"

5. Enter the fields as below


   Component        Component type

   .INCLUDE         CWBNTKEYVS

   TSTAMP TIMESTAMP


6. Enter the enhancement category as Can not be Enhanced.

7. Activate the structure. You can click ok activate icon on press ctrl + F3.




Changes to message class SCWN---------------------------------------------------------------

Step 1: Go to SE91 transaction

Step 2: Input SCWN to Message class field

Step 3: Click on Change

Step 4: If a popup comes select Maint. in orig. lang.

Step 5: Go to Message number 92 and add 'Fehler beim Abrufen der Hinweis informationen

aus SAP-Support-Backend.' to Message Short Text

Step 6: Go to Message number 93 and add 'Verbindung zum SAP-Backend wegen fehlender

SNOTE-Konfig. nicht möglich.' to Message Short Text

Step 7: Go to Message number 94 and add 'RFC-Destination &1 nicht konfiguriert.' to

Message Short Text

Step 8: Click on Save.

Step 9: Provide a TR to save changes when prompted.



Please perform the following post manual activities.


Create Text Elements for report SAPLSCWU

Go to transaction SE38

Enter the program as SAPLSCWU

Choose ‘Text Elements’ radio button and click on ‘Change’


                    Enter the following text elements and activate


                    002 Destinations


                    004 and


                    005 downloaded




Replace the following existing messages in SCWN Message class with the message text as given below.

Go to transaction SE91

Enter the message class name as ‘SCWN’ and click on change

Enter the message text as below for corresponding message numbers:

Message Number   Message Short Text

823 - Digitally signed SAP Note &1 downloaded in version &2 using RFC &3


824 - Digitally signed SAP Note &1 downloaded in version &2 using HTTPS &3 &4


825 - Dig.signed SAP Note &1 downloaded in version &2 using download service &3




Create the following Messages

1. Goto Transaction SE91

2. Enter Message Class SCWN and Message Number: 853

Click on Change

3. Enter the below text

Objekt &1 &2 im Transport kann wegen Inkonsistenz nicht gesperrt warden

4. Save the message

5. Add the below text for 854 message number

Obj. &1 &2 in off. Transport &3 gesperrt u. nicht in Transp. &4 sperrbar

6. Save the message




Please follow the Step-by-Step instructions from this note to ensure correct

implementation.

>>SPAM Version < 70:

Please note that the TCI enablement (Step 1. - Step 2a) needs to be done separately in

each system into which this SAP Note is being implemented.

Steps 2b. - 9. will be recorded in transport requests and are transportable.

If step 3 is relevant for you, please also perform this on every system.

>>SPAM Version >= 70:

From SPAM Version 70 on also the TCI enablement is transportable. This means, that you

do not need to do all the steps separately in every system.

The TCI Enablement only needs to be done once. If you have done it already it does not

need to be done again.






mount -t nfs -o vers=4 -v s4hanatest2:/usr/sap/trans /usr/sap/trans

mount -t nfs -o vers=4 -v s4hanatest2:/sapmnt/SGP/global /sapmnt/SGP/global


mount -t nfs -o vers=4 -v s4hanatest2:/sapmnt/SGP /sapmnt/SGP


mount -t nfs -o vers=4 -v s4hanatest2:/hana/db_backup /hana/db_backup


mount -t nfs -o vers=4 -v dellr940:/hana/db_backup /hana/db_backup



mount -t nfs -o vers=4 -v s4hanatest3:/hana/hdv_backup /hana/hdv_backup


mount -t nfs -o vers=4 -v s4hanatest2:/backup/DB_HGP /backup/DB_HGP


kolon01



Dnjstlr@79










1) SUM 완료 후  Batch job 릴리즈할 때  SDMI 가 수행되는 것인가?

- SDMI 배치잡은 총 수행시간 체크

- 수행시 리소스 체크


2) 임시 서버를  기존 운영 시스템에 AAS로 구성하여 SUM AP로 활용??

- CPU 스펙이  기준  운영 AP서버보다 훨씬 좋기 때문에 SUM AP로 활용하는 것이 좋겠음

- 물론, 운영 서비스 부하의 영향을 최소화 하기 위한 목적

- SUM 수행시 ASCS Split 하지 않고, 기존 ASCS 유지하도록 옵션 설정 필요함.

3) standard와 nZDM간의 downtime 차이 ??

- 2차 업그레이드시 Standard 방식으로 수행?

- 아니면, 별도로 업그레이드 테스트? <= 일정상 가능할까?

4) nZDM의 영향도 체크 SUMTOOLBOX 설치

- 관련 레포트 수행시 ABAP Dump 떨어짐

5) FnC 업그레이드시 HA 및 이중화를 그대로 유지하였음.

- ERS 셧다운시 HA 작동하지 않나?

- ERS 셧다운 어떻게 했나?

- 기존 운영 AP 서버들 3대 모드 셧다운 후 SUM AP만 살리고 업그레이드 진행할 예정

- sap mount 경로와 trans 경로를 공유하여 SUM AP를 구성하기 때문에 S4HANA 업그레이드시 커널도 자연스레 교체됨.

  굳이 운영 AP로 switch 하기 위한 별도 작업이 필요없음

  

 


2차 업그레이드 테스트시

ASCS 구성 그대로 유지 

ASCS Split 하지 말 것


SUM AP와 PAS간의  sapmnt, trans 경로 공유


SandBox 구성 후 Batch job 삭제 


HANA DB의 system 계정을 'JDsap2016' 로 변경






FNL_BATADM

WJCOMPANY

GIHOCHO

BIZZI_BATCH

ALEREMOTE

CREER

BAESW

MINHNHAT

WINNER

GLO_BATCH2

AHAN

FENGLJ

PHCJ0341

SR638

JHP0118

PPADMIN

EUM1217

ROSEMINE77

FH_SD

CHANG338

ALEREMOTE

ROSEMINE77

SANGLEE

KAYOUN0513

WF-BATCH

WOOGIMMI5031




select * from usr02 where mandt = '100' and uflag='64';

select * from usr02 where bname in ('SAP*','DDIC','BCADMIN') or bname like 'KOLON%' order by mandt, bname;

select mandt, ustyp, count(*) from usr02 group by mandt, ustyp order by mandt, ustyp;

select mandt, bname, ustyp from usr02 where ustyp = 'S' order by mandt, bname;



select * 

from usr02

where mandt in ('100','200','300')

and uflag = 0

and (bname not in ('SAP*','DDIC','BCADMIN')

or bname not like 'KOLON%' )

order by mandt, bname;



-- 100 client user lock

update usr02

set uflag=64

where mandt = '100'

and uflag = 0

and (bname not in ('SAP*','DDIC','BCADMIN')

or bname not like 'KOLON%' );


-- 200 client user lock

update usr02

set uflag=64

where mandt = '200'

and uflag = 0

and (bname not in ('SAP*','DDIC','BCADMIN')

or bname not like 'KOLON%' );


-- 300 client user lock

update usr02

set uflag=64

where mandt = '300'

and uflag = 0

and (bname not in ('SAP*','DDIC','BCADMIN')

or bname not like 'KOLON%' );






 UPSERT SHDB_PFW_CONF VALUES 

   ( '<client>' , 'MyApplication', 'RESOURCE PROVIDER', 'SERVER_GROUP', 'C', 40, 0, 'MyServerGroup', 'N' ) 

   WITH PRIMARY KEY

   

   

find . -mtime +5 -type f -ls -exec rm {} \;




Dispatcher adviced to Cancel processing due to exceptions raised in parallel processes. 

Details in CX_SHDB_PFW_EXCEPTION->P_COLLECTED_EXCE

An exception or a cancellation of a package migration was raised

The responsible component for the migration error is CA-GTF-OC




tar -cvpf usr_sap_SGP.tar /usr/sap/SGP

tar -cvpf home_sgpadm.tar /home/sgpadm

tar -cvpf sapmnt_SGP.tar /sapmnt/SGP




tar -xvpf sapmnt_SGP.tar /sapmnst/SGP







insert into SHDB_PFW_CONF (CLIENT, APPL_NAME, COMPONENT, PARAM, VALUE, CHANGEABLE )

VALUES ( '100','NSDM_XPRA_MATDOC_BERID','PACKAGE PROVIDER','[{"TABNAME":"ZV_XPRA_MATDOC","SIZE":10000},{"TABNAME":"MATDOC","SIZE":10000}]','N');




dd if=/dev/zero of=/hana/swapfile2 bs=1k count=10485760




다운 타임 줄이기

1) 쉐도우 인스턴스에셔 NSDM_XPRA_MATDOC_BERID 프로그램 돌려보기

2)  파라미터 테이블 설정하기

3) SAP Note 3094048  적용하기







select 

A.TRKORR

, B.AS4TEXT

, A.STRKORR

, A.TRSTATUS

, A.TARSYSTEM

, A.AS4USER

, A.AS4DATE

, A.AS4TIME

from E070 A

inner join E07T B

on A.TRKORR = B.TRKORR

where TRKORR like 'SGDK%' and TRSTATUS <> 'R' order by TRKORR;





http://gerpapd.cjwise.net:8020/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=310&sap-language=EN#Shell-home








Currently, several issues requiring remote support have arisen in our project. 

We are in the process of setting up a remote connection, but the following error is occurring.


---------------------------

connection to partner '116.121.26.185:3299' broken


Location        SAProuter 40.4 (using third-party library) on ls6928

Time        Fri May  8 07:52:51 2026

Component    NI (network interface)

Release        753

Version        40

Module        /net/usr.work/dblue/i823274/bas/753_REL/src/base/ni/nixxi.cpp

Line        5177

Method        NiIRead: P=116.121.26.185:3299; L=169.145.197.109:55592

Return Code    -95

System Call    recv

Counter        8667


---------------------------





select mandt, bname, ustyp, uflag

from usr02

where mandt = '300'

and uflag=64

order by bname,  ustyp, uflag;




select *

from usr02

where ustyp = 'A'

and uflag = 0

and bname not in

( 'DDIC'

, 'SAP*'

, 'BCADMIN'

,upper('ejkim_bp')

,upper('hsyoon_bp')

,upper('yikim_bp')

,upper('mjpark_bp')

,upper('jwkim_bp')

,upper('bkjun_bp')

,upper('wsyun_bp')

,upper('shhwang_bp')

,upper('hjyang_bp')

,upper('ykkim_bp')

)

order by mandt, bname


-- 개발 시스템 (SGD) 잠금 대상 SAP Dialog 타입 User 17,238




update usr02

set uflag = 64

where ustyp = 'A'

and uflag = 0

and bname not in

( 'DDIC'

, 'SAP*'

, 'BCADMIN'

,upper('ejkim_bp')

,upper('hsyoon_bp')

,upper('yikim_bp')

,upper('mjpark_bp')

,upper('jwkim_bp')

,upper('bkjun_bp')

,upper('wsyun_bp')

,upper('shhwang_bp')

,upper('hjyang_bp')

,upper('ykkim_bp')

);





## SUM AP가 필요한 이유


Downtiome 단축


SUM AP 서버 Spec

CPU : 224 core


운영 서비스 영향 최소화


SAP mount 경로 공유 ( SAP Kernel 공유 )

Trans 경로 공유  ( /usr/sap/trans )





## Add for SUM Downtime

ztta/roll_extension = 60000000000

ztta/roll_extension_dia = 60000000000

ztta/roll_extension_nondia = 60000000000

abap/heap_area_dia = 20000000000

abap/heap_area_nondia = 40000000000

EM/TOTAL_SIZE_MB = 1024000




ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('inifile_checker', 'replicate') = 'true' with reconfigure;




KOLON01

KOLON02

KOLON03

KOLON04

KOLON05

KOLON06

KOLON07

KOLON08

KOLON09

KOLON10



sync

echo 1 > /proc/sys/vm/drop_caches


sync

echo 2 > /proc/sys/vm/drop_caches



sync

echo 3 > /proc/sys/vm/drop_caches




UPDATE uvers SET PUTSTATUS='+' WHERE PUTSTATUS='U';



UPDATE uvers SET PUTSTATUS='U' WHERE PUTSTATUS='+' and compone <> 'SAP_HR';




select * from uvers;



select name1, name2, namecombined, length(name1), length(name2), length(namecombined)

from KNA1

where length(namecombined) = ( select max(length(namecombined)) from KNA1 );


select length(name1) as a, length(name2) as b, length(name1 || '_' || name2) as c

from ADRC

order by c desc;






DD


date


root 파티션  날린 후

Raid 재구성






dd if=/dev/zero of=/dev/sdb bs=4M status=progress


<< 디스크 초기화 작업 순서>>


date; fdisk -l; date

date; df -h; date



date; df -h; date

date; pvs; date

date; vgs; date

date; lvs; date

date;dd if=/dev/zero of=/dev/sdd bs=4M status=progress;date

date; df -h; date

date; pvs; date

date; vgs; date

date; lvs; date



date; df -h; date

date; pvs; date

date; vgs; date

date; lvs; date

date;dd if=/dev/zero of=/dev/sdb bs=4M status=progress;date

date; df -h; date

date; pvs; date

date; vgs; date

date; lvs; date



date; df -h; date

date; pvs; date

date; vgs; date

date; lvs; date

date;dd if=/dev/zero of=/dev/sda bs=4M status=progress;date

date; df -h; date

date; pvs; date

date; vgs; date

date; lvs; date





date; df -h; date

date; pvs; date

date; vgs; date

date; lvs; date

date;dd if=/dev/zero of=/dev/sdb bs=4M status=progress;date

date; df -h; date

date; pvs; date

date; vgs; date

date; lvs; date



OS할때 (OS가깨져서 OS 접속불가 를 remote console로 보면될거같아요)

 - UFEI에서 F1누르면 나오는 management에서 raid깨는 메뉴







2025 업그레이드 이후 보안쪽 강화로 인한 영향 관련 노트 및 기능

(HTTPS를 포함한)


SAP Note, 릴리즈 노트 등 확인







/UI5/UPD_ODATA_METADATA_CACHE  ( Daily )

/UI2/EAM_BUILD_CACHE ( Daily )





TLS 버전 1.3

HTTPS 프로토콜 강제 => SSL => 인증서 설정 필수





RFC Destination 관련 테이블 :

RFCDES

RFCATTRIB

RFCCHECK

RFCDESSECU

RFCDOC

RFCSYSACL



Secure Storage 관련 테이블 :

RSECACTB

RSECTAB





export

client=ALL

file='/usr/sap/trans_qas/syscopy/EXP_TEST.dat'

delete from rfcdes_test;

select * from rfcdes_test;


R3trans -w exp2.log /usr/sap/trans_qas/syscopy/exp2.sh



R3trans -w exp.log /usr/sap/trans_tgd/syscopy/exp.sh





R3trans -w imp.log /usr/sap/trans_tgd/syscopy/imp.sh


import 

client=ALL

file='/usr/sap/trans_qas/syscopy/EXP_TEST.dat'



Application log 테이블 정리 (BALHDR, BALDAT )

SAP Note 3039724

https://me.sap.com/notes/0003039724

- 메일 보냄

- Application log data가 무엇인지

- Application log data를 삭제했을 경우 영향도

- 연도가 없는 것은 어떤 데이터 인지

- Application log data 삭제시 시스템 부하

- Application 로그 데이터 정리 안하기로 함 ( 전병호님 결정 )




SUM 작업 스크립트 ( O )

개발 시스템 업그레이드 에러 인시던트 등록 ( O )

Fiori Activation ( O )

운영 시스템 사전 반영 사항 정리 ( O )

 추가 사항

 - 배치잡 그룹 설정 추가 ( SM61 )

 - 다운타임 최적화 DB 파라미터 설정 추가 

 - SI-CHECK

 - CTS 파일 업로드 

Cutover activity Plan 수정 ( O )

다운타임 분석 결과서 작성 ( O  )

ENSA2 관련 확인 => 오민석님께 메일 보냄 => ERS는 HA가 안되고 있음. ASCS만 되어 있음.


fiori관련 webdispatcher URL 설정 확인 

Fiori SSO 확인 => 운영시스템은 Fiori 접근시 webdispatcher를 통함. webdispatcher에 인증서가 import 되어 있음.


SUM 이후  커널 디렉토리  symbolic 링크 연결 확인 

 - SAP 인스턴스 ( Dialog, ASCS, ERS ) 기동시  sapmnt exe 디렉토리에서  /usr/sap/.../exe 디렉토리로 복사



다운 타임시 HANA Replication 유지 여부 결정 (  Downtime 시 원복을 위해 이중화 끊고 작업 )

다운 타임시 AP 클러스터 내려놓는다고 함. ( 오민석님 )



Cut Over Activity Plan 수정

원복 계획 추가  ( 이중화 해제 후 standby node 활용 )




DIR_CT_RUN 링크 재생성?


RFCDES export & import

User master record  Export



SUM AP 셧다운 시기 (  umount /sapmnt/SGP, /usr/sap/trans )




sm51 에서 AAS 간 통신이 안되는 건, /etc/hosts 파일에 서버명이 등록이 안되어 있을 확률이 큼

ASCS 서버의 /etc/hosts 파일에 AA 정보를 추가하고, AAS 재기동하면 됨.

운영 AP 서버들에 SUM AP hostname 추가


- ENQ 및 ERS 관련 파라미터를 2025 기준으로 변경해야 함

   1.  ERS 설치 (O) 

   2. SUM 수행 테스트 (O)

SPAU CTS는 QASK920068

    



SGD DB 백업 (O)


CTS 적용 일자에 따라 파일 분리 ( O )


피오리 /UI5/APP_INDEX_CALCULATE  배치잡 릴리즈 확인


JDsap2016




SPAU, Fow + 3차 (overwrite 옵션 추가) + 4차 (overwrite 옵션 추가 ) + 개발 CTS + 미완료 CTS 72건 (overwrite 옵션 추가) 




sync

$echo 1 > /proc/sys/vm/drop_caches


sync

echo 2 > /proc/sys/vm/drop_caches



sync

echo 3 > /proc/sys/vm/drop_caches





JDsap2016@




$ hdbnsutil -sr_register --name=secondarysgp --remoteHost=gerpdb1 --remoteInstance=00 --replicationMode=sync --operationMode=logreplay ( Standby )

$ hdbnsutil -sr_state ( Primary, Standby )







https://me.sap.com/notes/0003039724


https://me.sap.com/notes/2057897


( 헤더 정보가  없는 BALDATA 테이블의 Orphan 레코드 제거 )


https://iheedol.tistory.com/entry/SAP-%EC%96%B4%ED%94%8C%EB%A6%AC%EC%BC%80%EC%9D%B4%EC%85%98-%EB%A1%9C%EA%B7%B8-BALHDRBALDT-%EC%82%AD%EC%A0%9C




10.64.0.207 s4hanatest2.cjwise.net s4hanatest2

192.168.101.250 gerpsumap.cjwise.net gerpsumap






SAP 서비스 중지

# su - sgpadm 

$ stopsap r3 (gerpap3 SAP 수동 중지)

- Service Guard 중지 및 유지 보수 모드 활성화

[gerpap1, gerpap2]

#cmhaltcl -f 

#cmviewcl //모든 서버 status down 확인

#ip a //vip down 확인


 - gerpap1, gerpap2 , gerpap3 수동 셧다운

 

 


SAP 지식 링크 모음

 SAP 지식 링크 모음


Bookmarks

북마크바

SUM

Downtime-optimized Conversion Approach
Document History | SAP Help Portal
3669180 - SUM 2.0 SP 25를 통해 SAP S/4HANA로의 다운타임 최적화 변환 실행 및 모니터링 - SAP for Me
2547309 - SUM 2.0을 사용한 다운타임 최적화 DMO - SAP for Me
Downtime-Optimized Conversion to SAP S/4HANA Using Software Update Manager 2.0 | SAP Help Portal
DMO: downtime optimization by migrating app tables... - SAP Community
2153242 - 다운타임 최적화 DMO를 사용하는 SUM의 테이블 크기 및 다운타임 추정 - SAP for Me
Software Update Manager Toolbox is Available Now - SAP Community
Solved: In-place migration upgrade using SUM with DMO - SAP Community
3620660 - 통합 노트 - Software Update Manager 2.0 SP25 [lmt_021] - SAP for Me
3690314 - Software Update Manager 툴박스 - 릴리스 2025 12/12 - SAP for Me
3092738 - Software Update Manager 툴박스 - 중앙 SAP Note - SAP for Me
SUM Toolbox | SAP Help Portal
3092738 - Software Update Manager Toolbox - Central SAP Note - SAP for Me
3690314 - Software Update Manager Toolbox - Release 12/2025 - SAP for Me
SAP 운영자 ST03 :: [Trouble Shooting] SUM 2.0 실행 시 아무런 페이지가 안 뜨는 경우
1826767 - 'Could not check credentials...Connection refused' when upgrading HANA using SUM - SAP for Me
Software Update Manager 2.0 | SAP Help Portal
3717026 - STBX: Enhanced Impact Analysis and ZDIMPANA export - SAP for Me
3723837 - STBX: Impact Analysis check for imports on table level - SAP for Me
Silent Data Migration (SDMI) in SAP S/4HANA - SAP Community
1678565 - ABAP 기반 솔루션을 위한 nZDM(니어 제로 다운타임 유지보수)의 선행조건과 제한사항 - SAP for Me
1678564 - ABAP 기반 솔루션을 위한 nZDM(니어 제로 다운타임 유지보수)의 제한사항, 데이터베이스 고유 설정 및 문제 해결 - SAP for Me
1988188 - 삭제된 클라이언트에서 전송 요청을 삭제하는 방법 - SAP for Me
652310 - LBWE: 추출 구조 변경 메시지 MCEX 140 - SAP for Me
640066 - 업그레이드: XPRA RMCSBWXP_COM이 있는 리턴 코드 6 - SAP for Me
396647 - FAQ: V3 업데이트: 질문과 답변 - SAP for Me
67014 - 업데이트 요청 재구성 - SAP for Me
1759080 - SUM과 고객 전송 통합의 선행조건 및 제한사항 - SAP for Me
2450902 - 고객 전송 통합 마법사 - SAP for Me
1962922 - The meaning of the option "Accept errors and repeat phase MAIN_SHDRUN/ACT_UPG" in the upgrade phase ACT_UPG/ACT_TRANS - SAP for Me
SAP System Upgrade and SAP S/4HANA Conversion
3198780 - SUM 단계 PARCONV_UPG 오류: "중복 뷰 이름을 사용할 수 없음" - SAP for Me
3542421 - Error in phase MAIN_NEWBAS/PARCONV_UPG due to duplicate table name SRF_AGENCY - SAP for Me
1901463 - 업그레이드 중에 수정을 수행하기 위해 SAP 시스템의 잠금을 해제하는 방법 - SAP for Me
1947874 - XPRAS_AIMMRG 단계의 성능 분석 - SAP for Me
2351294 - S/4HANA 시스템 전환/업그레이드: 기술적 다운타임을 단축하기 위한 조치 - SAP for Me
3696070 - NSDM_XPRA_MATDOC_BERID performance setting - SAP for Me
3024983 - Technical adjustments in NSDM_MATDOC_BERID & NSDM_XPRA_MATDOC_BERID - SAP for Me
1970888 - How To: 업데이트/업그레이드 중 SPDD/SPAU 처리 - SAP for Me
Minimizing downtime of System Conversion to SAP S/4HANA with down
1838153 - NetWeaver 시스템 업그레이드 중 오류가 발생할 때 로그를 가져오는 방법 - SAP for Me
3043498 - Maintenance Planner에서 검증하는 동안 소프트웨어 컴포넌트 버전 무시 - SAP for Me
2335014 - DBTABLOG | Reduce size - SAP for Me
Optimizing DMO Performance - SAP Community
2547309 - Downtime-optimized DMO with SUM 2.0 - SAP for Me
3620679 - Database Migration Option (DMO) of SUM 2.0 SP25 - SAP for Me
2939305 - Software Update Manager 재설정 이 옵션은 절차의 현재 단계에서 수행할 수 없습니다. - SAP for Me
1705774 - Error in phases MAIN_SWITCH/JOB_RSVBCHCK2 or MAIN_SWITCH/JOB_RSVBCHCK_D; Checks after phase MAIN_INIT/JOB_RSVBCHCK* were negative. - SAP for Me
1563660 - sapcontrol, user authorization issues (SUM) - SAP for Me
SUM Upgrades Configuration : Tuning/Process Counts - SAP Community
Best Practices for Upgrading SAP Systems - SAP Community
1904239 - SUM options to change parameters entered in INITPUT and INITSUBST phases - SAP for Me
3090543 - CO-PA: Inactive Nametabs for RKE2_ Data elements after upgrade - SAP for Me
DMOVE2S4: Isolating the Additional Application Server | SAP Help Portal
Important Entries for the Configuration Roadmap Step | SAP Help Portal
3422822 - Handling parameter checks errors and warnings. - SAP for Me
2312315 - SUM fails to start an instance in phase MAIN_UPTRANS/STARTUP_PUPG - SAP for Me
STARTSAP_PUPG or STARTSAP_TBUPG phase | SAP Help Portal

OS&DB 버전

2369910 - Linux의 SAP 소프트웨어: 일반 정보 - SAP for Me
리눅스 NFS 서버, 클라이언트 설치 및 확인 — 기록하는 습관.
tar압축 - 권한까지 포함한 하위디렉토리 압축하기 :: Faction 8T
[Linux] tar --exclude 압축 .. : 네이버블로그

ERP Admin

언어팩 설치

Notes - SAP for Me
SAP 신규 언어팩 설치 방법__How to Install a New Language Pack in SAP
18601 - Frequently asked questions about language transport - SAP for Me
2494843 - How to find language medias that are not listed in note 330104 - SAP for Me
2456868 - Troubleshooting language installation and translation issues - CTS-LAN-WIKI - SAP for Me
1156507 - Language supplementation, RSREFILL, and client maintenance - SAP for Me
110910 - Deleting the language load - SAP for Me

권한

2219873 - Troubleshooting authorization errors - SAP for Me
Find failed authorization object in ST01 and SU53 - SAP Community
2985997 - Explanation of components below BC-SEC - SAP for Me
SAP GUI - Transaction Code - SU53 - SAP Community

메모리

RSMEMORY 프로그램을 사용한 SAP 메모리 할당 조정__Adjusting SAP Memory allocation Using RSMEMORY Program
2180736 - TSV_TNEW_PAGE_ALLOC_FAILED (or similar, memory related) short dumps - SAP for Me
2085980 - New features in memory management as of Kernel Release 7.40 - SAP for Me
SAP Memory 전체적인 구조 및 관리__SAP Memory Structure and Management
SAP Memory Management (BC-CST-MM) | SAP Help Portal
1137734 - Assignment of memory areas, shared memories, and pools - SAP for Me
2660701 - Memory disclaiming in heap - SAP for Me
3285104 - Default setting for heap monitoring - SAP for Me
941735 - SAP memory management system for 64-bit Linux systems - SAP for Me
2180736 - TSV_TNEW_PAGE_ALLOC_FAILED (or similar, memory related) short dumps - SAP for Me
3259122 - SYSTEM_NO_ROLL - Troubleshooting - SAP for Me
1926986 - Best practice formulas in profile maintenance - SAP for Me
SAP Memory 전체적인 구조 및 관리__SAP Memory Structure and Management
2442188 - Analyzing and Configuring Memory to Increase Performance - Guided Answers - SAP for Me

3303172 - 슈퍼 유저 SAP 활성화* - SAP for Me
2448562 - Support Package Manager는 전송 기반 정정 지시(TCI, Transport based Correction Instructions)를 사용하여 큐를 확인할 수 없습니다. - SAP for Me
1104735 - UNIX에서 새 인스턴스별 디렉토리로 업그레이드 - SAP for Me
1957798 - Update SAP kernel failed with error "2, No such file or directory" in sapcpe.log - SAP for Me
2465519 - 패키지 전송 계층 변경(일괄) - SAP for Me
Mass Tadir changes using SE03 - SAP Community
401162 - Linux: TCP/IP 포트 충돌 방지 및 문제 시작 - SAP for Me
Doing a mass update of transport target - SAP Community
Managing an Enqueue Replication Server (ERS)
2180934 - "보류" RFC의 작업 프로세스 분석 또는 CPIC 중지 상태 - SAP for Me
3604933 - EXE의 데이터베이스 오류 100 - SAP for Me
# [SAP] Import options
Basis Technology - SAP Community
1902258 - 데이터베이스 키 파일 툴의 보안 저장소 - SAP for Me
3045494 - [How to]Troubleshooting on DB02/DBACOCKPIT/ST04 -> Diagnostics: Missing Tables and Indexes - SAP for Me
SAP BC 프로그램/ 펑션/ 테이블/ 티코드
[SAP BC 가이드 11] SAP Monitoring & Performance Checks : 네이버 블로그
2129291 - Session Priority and Work Process Quota in SAP Kernels >= 7.4x - SAP for Me
SAP CTS & STMS 배포 방법 정리 (Import 옵션, Landscape)
1436329 - Application log, parallel deletion, and performance - SAP for Me
2770800 - 어플리케이션 로그 삭제 테이블이 매우 오래 걸립니다. - SAP for Me
2507213 - SBAL_DELETE 실행이 너무 깁니다. - SAP for Me
195157 - 어플리케이션 로그: 로그 삭제 - SAP for Me
DIR_CT_RUN : 네이버 블로그
SAP NetWeaver 7.5 Adobe Document Services(ADS) 구성 가이드
PFCG 역할을 일괄적으로 생성하는 표준 트랜잭션
2535858 - Role profile not generated in the Plug-in system, message 'Generated profiles are not current' occurs in GRC - SAP for Me
2220928 - SUPC: Profile generation fails - SAP for Me
1723881 - Application of client-specific customizing settings to role maintenance - SAP for Me
Import Process
SAP 품질 시스템 재구성 가이드 (클라이언트 카피)__SAP QAS System Refresh Guide (Client Copy)
3435216 - SESSIONMEM_QUOTA_WARNING - SAP for Me
3692281 - Long runtime in Generation of Programs and Screens/Dynpros and RDDDIC3L while the import is running - SAP for Me
3606550 - Large memory consumption, dump TSV_TNEW_PAGE_ALLOC_FAILED regarding TMSADM - SAP for Me
1924741 - It takes a long time to refresh a system's import queue - SAP for Me
2939148 - Reduce size of import buffer file - SAP for Me
3275786 - FLP Logon page certificate pop-up - SAP for Me
1664950 - Error while communicating with the server - EPM Add-in - SAP for Me
SAP 품질 시스템 재구성 가이드 (시스템 카피)__SAP QAS System Refresh Guide (System Copy)
SAP R3trans 를 사용한 테이블 Export/Import__ R3trans Table Export / Import Guide
3744832 - SU01: DBSQL_DUPLICATE_KEY_ERROR when creating users or adding roles to users; dump in SAPLSUID_IDENTITY - SAP for Me
1597172 - SU01 SAPSQL_ARRAY_INSERT_DUPREC or DBSQL_DUPLICATE_KEY_ERROR dump when copying users - SAP ERP & SAP S/4 HANA - SAP for Me
197012 - ME21N, document overview, standard variant saved for purchase requisitions - SAP for Me
2367439 - Avoid manual restart of ICM process - SAP for Me
3236399 - FAQ - Technical Job Repository (SJOBREPO) - SAP for Me
3672521 - Jobs in the Technical Job Repository (SJOBREPO) in SAP S/4HANA 2025 - SAP for Me
SAP 기본 배치잡 설명 및 설정__Explanation and Setup of SAP Standard Batch Job

BALDAT 테이블 정리

3039724 - BALHDR 및 BALDAT: 어플리케이션 로그 테이블 크기 증가 [FAQ] - SAP for Me
2057897 - Application Log: orphan records in BALDAT - SAP for Me
iHeedol :: SAP 어플리케이션 로그 (BALHDR,BALDT) 삭제

HANA System Replication

2661878 - HANA 시스템 복제 로그 리플레이 - 대규모 시스템에 대한 권장사항 설정 - SAP for Me
SAP HANA DB 시스템 복제 모드 및 작동 모드__System Replication Modes and Operation Modes for SAP HANA DB

SDMI

2664638 - 클라이언트에서 SDMI 사용자 생성 및 지정 - SAP for Me
Silent Data Migration Infrastructure (SDMI) | SAP Help Portal
2916801 - 사일런트 데이터 마이그레이션(SDMI) 구성 옵션 - SAP for Me
2907976 - 사일런트 데이터 마이그레이션(SDMI) - FAQ - SAP for Me
2821421 - SDM_USER: SAP_ALL 프로파일 없이 생성 허용 - SAP for Me
2850918 - SAP S/4HANA에서 사일런트 데이터 마이그레이션(SDMI)에 필요한 권한 - SAP for Me
3635357 - SAP S/4HANA 2025의 사일런트 데이터 마이그레이션 프레임워크의 SDMI 클래스(세부사항, 수정, 특별 처리 노트) - SAP for Me
3445802 - Silent Data Migration (SDMI) New Rows after Migration – FAQ - SAP for Me
2968371 - SDMI: 미완성 SDMI를 찾는 방법과 이를 트리거하는 방법 - SAP for Me
2499529 - 작업 저장소 스케줄러 사용/사용 안 함 - SAP for Me
Solved: How to execute/re-run the SDMI Class to migrate th... - SAP Community
3679170 - 시스템 업데이트 후 개별 백그라운드 작업 일정 조정 - SAP for Me
S/4HANA Upgrade 1809 to 2020 - SDMI Lessons Learne... - SAP Community
3236399 - FAQ - 기술 작업 저장소(SJOBREPO) - SAP for Me
3361109 - R_JR_BTCJOBS_GENERATOR 개요: 관리, 기능 - SAP S/4HANA 기술 작업 저장소 - SAP for Me
3679170 - Reschedule individual background jobs after system update - SAP for Me
2494541 - Background job R_JR_BTCJOBS_GENERATOR failed to be scheduled in S/4HANA system - SAP for Me
3376637 - ACDOCA 마이그레이션 클래스 중 자동 데이터 마이그레이션 실패(시간 초과) - SAP for Me
3235662 - 분석 및 FAQ: SDMI CL_SDM_ACDOCA_RFCCUR_CBTTYPE, CL_SDM_BSEG_RFCCUR_FCSL 또는 CL_FINS_SDM_ACDOCA_NETDT 실행 시 문제 발생 - SAP for Me
2968371 - SDMI: How to find unfinished SDMIs and how to trigger them - SAP for Me
3638684 - Software Update Manager(SUM)에서 스킵하도록 선택했음에도 불구하고 기술적 다운타임 중에 실행되는 사일런트 데이터 마이그레이션 - SAP for Me
S4HANA SPS Update SDMI (Silent Data Migration) CL_... - SAP Community
3227915 - PFW: 모든 PFW 어플리케이션에 대해 PartitionStriping을 기본값으로 활성화 - SAP for Me
2731999 - 기술 작업 저장소(SJOBREPO)의 사용자 정의 단계 사용자 지정 - SAP for Me
3638684 - Software Update Manager(SUM)에서 스킵하도록 선택했음에도 불구하고 기술적 다운타임 동안 사일런트 데이터 마이그레이션 실행 - SAP for Me
S/4HANA Silent Data Migration Infrastructure (Quic... - SAP Community
3430981 - FAQ: Problems with finished or cancelled SDM's: CL_SDM_ACDOCA_RFCCUR_CBTTYPE, CL_SDM_BSEG_RFCCUR_FCSL or CL_FINS_SDM_ACDOCA_NETDT - SAP for Me
3445802 - Silent Data Migration (SDMI) New Rows after Migration – FAQ - SAP for Me
3726256 - SDMI error in SI-Check - SAP for Me
3609262 - New field called as NameCombined is introduced in table KNA1 & LFA1 along with SDM to do data migration - SAP for Me
3635357 - SDMI Classes in the Silent Data Migration Framework in SAP S/4HANA 2025 (Details, Corrections, Special Handling Notes) - SAP for Me
3752682 - SDMI monitor (SDM_MON) shows "new rows after migration" for class cl_sdm_fcml4h_ledger_mldoc after upgrade to SAP S/4HANA 2025 - SAP for Me

nZDM

Phases Specific to Downtime-Optimized Conversion | SAP Help Portal
2707731 - SAP S/4HANA용 SUM의 제로 다운타임 옵션의 선행조건 및 제한사항 - SAP for Me
3204621 - PFW 지원 파일 생성 방법 - SAP for Me
System Conversion to SAP S/4HANA: Downtime Reducti... - SAP Community
3535698 - How to restrict the application servers used by the SHDB Parallelization Framework - SAP for Me
Background job stuck in Status "On Hold" with Reas... - SAP Community
Technical details on S/4HANA ZDO(Zero Downtime upg... - SAP Community
3094048 - NSDM_XPRA_MATDOC_BERID 대형 MATDOC에 대한 추가 지원 - SAP for Me
3024983 - NSDM_MATDOC_BERID & NSDM_XPRA_MATDOC_BERID의 기술적 조정 - SAP for Me
Introducing the new CRR Control Center to monitor ... - SAP Community
Error Handling for the Replication Process Monitor | SAP Help Portal

TCI

2187425 - SAP Note 전송 기반 정정 지시(TCI)에 대한 정보 - SAP for Me
2408073 - SAP Note Assistant에서 디지털 서명된 노트 처리 - SAP for Me
3025673 - 500 CSADMIN 액세스 또는 SAP Content Sever URL 테스트 중 내부 서버 오류 발생 - SAP for Me
Enabling and Using SNOTE for Digitally Signed SAP ... - SAP Community

이중화

1945676 - hdbnsutil -sr_unregister의 올바른 사용 - SAP for Me
SAP HANA System Replication 설정 :: Continue to Challenge
3722351 - system_replication_communication listeninterface가 ".local"(으)로 설정되어 SAP HANA 시스템 복제 등록 중 연결 거부 오류 발생 - SAP for Me
3274590 - 자주 발생하는 'rc=111: nameserver와 indexserver 사이에 연결 거부' 오류가 발생했습니다. - SAP for Me
3439776 - error "unable to contact primary site host Trying old-style port" when trying to re-register a secondary that was working before being unregistered - SAP for Me
3099639 - System Replication setup error, unable to contact primary site host Trying old-style port - SAP for Me
3439776 - error "unable to contact primary site host Trying old-style port" when trying to re-register a secondary that was working before being unregistered - SAP for Me
3099639 - System Replication setup error, unable to contact primary site host Trying old-style port - SAP for Me
How to configure HANA network communication channe... - SAP Community
SAP HA solutions and Simplified Approach for S/4HA... - SAP Community
SAP S/4 HANA - Enqueue Replication 2 High Availability Cluster | SUSE Linux Enterprise Server for SAP applications 15 SP4
Managing HPE Serviceguard Extension for SAP for Linux Version A.15.30.01
Parameter Reference of Standalone Enqueue Server 2 | SAP Help Portal
Profile Parameters of Standalone Enqueue Server 2 | SAP Help Portal
S4HANA 2025 Configuration of the Enqueue Server 2 | SAP Help Portal
Comparison of Old and New Profile Parameters | SAP Help Portal
Solved: ENSA2 - enq/io/max_threads - SAP Community
Configuration of the Enqueue Replicator 2 | SAP Help Portal
Failover | SAP Help Portal
2630416 - Support for Standalone Enqueue Server 2 - SAP for Me
2146940 - Desupport of Enqueue Work Process - SAP for Me
High Availability with Standalone Enqueue Server 2 - SAP Community
2464065 - Check of automatic maintenance mode for HA solutions - SAP for Me

SAP HANA DB

2183363 - SAP HANA 내부 네트워크 구성 - SAP for Me
2800055 - FAQ: SAP HANA Kernel Sentinel - SAP for Me
3544498 - SAP HANA SYSTEM Replication Failure After Setting enable_ssl Parameter - SAP for Me
3670124 - Modifying Column Types or Lengths Using ALTER TABLE Statements Slower Than Expected in SPS08 - SAP for Me
EXPORT INTO Statement (Data Import Export) | SAP Help Portal
EXPORT Statement (Data Import Export) | SAP Help Portal
3428763 - Bookmark of frequently used SAP GUI transaction codes for SAP HANA related investigations - SAP for Me

SUMTOOLBOX

2402270 - Software Update Manager 유지보수 시나리오를 위한 영향 분석 실행 - SAP for Me

피오리

Rapid Activation of SAP Fiori | SAP Help Portal
SAP Fiori for SAP S/4HANA – Foundational SAP Notes... - SAP Community
3608355 - Composite SAP note: Rapid Activation for SAP Fiori in SAP S/4HANA 2025 - SAP for Me
2902673 - SAP S/4HANA에서 SAP Fiori를 위한 빠른 활성화 - 개요 - SAP for Me
3686717 - Composite SAP note: Rapid Activation for SAP Fiori in SAP S/4HANA 2025 FPS01 - SAP for Me
Upgrade Support of SAP Fiori for SAP S/4HANA | SAP Help Portal
SAP Fiori for SAP S/4HANA – Upgrade Faster – Why &... - SAP Community
New Installation of SAP S/4HANA 2023 FPS1 – Part 4... - SAP Community
HTTP 500 "Unknown error" / "Message E MD5 027 cannot be processed in plugin mode HTTPS" | SAP Help Portal
Home
Fiori App Reference Library
SAP Fiori Apps Reference Library
3339909 - Fiori 설정: 카탈로그의 컨텐트 활성화 - SAP for Me
3366013 - SAP Fiori(/n/ui2/flp)가 S/4HANA 또는 SAP Fiori 프론트엔드 서버 업그레이드 후 자격 증명을 요청하고 있습니다. - SAP for Me
1789344 - How to disable HTTP -> HTTPS switch for an ICF service - SAP for Me
2807979 - How to setup Adaptation Transport Organizer for S/4HANA On Premise or Private Cloud system via S_ATO_SETUP - SAP for Me
Configuration Information: Adaptation Transport Organizer | SAP Help Portal
2998830 - Fiori Launchpad Long URL(/sap/bc/ui5_ui5/ui2/ushell/shells/FioriLaunchpad.html) is not using SAML configuration and it works same for short URL(/sap/bc/ui2/flp) - SAP for Me
2528187 - The URL is opened in transaction code /UI2/FLP has changed on SAP_UI 751 SP 0003 - SAP for Me
2475427 - How to customize the Fiori Launchpad URL - SAP for Me
How to maintain the table HTTPURLLOC | SAP Help Portal
3258944 - SAP GUI for Windows: New browser extension "SAP GUI connector for Microsoft Edge" for Microsoft Edge - SAP for Me
Customizing the Launchpad URL | SAP Help Portal
2283716 - Key User Application is not configured - SAP for Me
2787809 - ATO: Enable Extensibility Template Development in SAP S/4HANA Cloud, public edition - SAP for Me
2807979 - S_ATO_SETUP을 통해 S/4HANA 온프레미스 또는 프라이빗 클라우드 시스템을 위한 적용 전송 구성을 설정하는 방법 - SAP for Me
2636754 - Configuration steps for embedded Analytics in ABAP based Applications - SAP for Me
2303900 - Latest Information about BW Setup in S/4HANA Systems - SAP for Me
Activating SAP S/4HANA Embedded Analytics
3604376 - Task "Install Essential BW Content" on the tasklist "SAP_BW_SETUP_INITIAL_S4HANA". - SAP for Me
BW Configuration Steps for Embedded Analytics | SAP Help Portal
2710887 - WebGUI: Error "RSEC: Record "/HMAC_INDEP/CL_HTTP_SERVER_NET============CP" has KeyID "x" which does not exist in SecStoreFS [rsecxdb.c ...]" In Dev trace - SAP for Me
440231 - SU25 | FAQ: Upgrade postprocessing for Profile Generator - SAP for Me
3368272 - Fiori Launchpad shows no tiles when accessed using protocol HTTP or using protocol HTTPS through SAP Web Dispatcher - SAP for Me
2545066 - EAM/UM: Performance of SAP Menu - SAP for Me
Scheduling Caching of SAP Menu Entries | SAP Help Portal
Cache Buster for OData Metadata of SAP Fiori Apps | SAP Help Portal
2913405 - SAP GUI for Windows: Dependencies to browsers / browser controls - SAP for Me
2510380 - How to switch HTTP/HTTPs protocol when opening Fiori Launchpad with T-Code /UI2/FLP - SAP for Me
3453463 - How to avoid the 500 internal error with SAP GUI connector when using /UI2/FLP - SAP for Me
2217489 - Maintenance and Update Strategy for SAP Fiori Front-End Server - SAP for Me
3340880 - SAP Fiori front-end server 2023 for SAP S/4HANA - SAP for Me
Best Practices for Developers - Documentation - Demo Kit - SAPUI5 SDK
3574267 - SAP Fiori front-end server 2025 for SAP S/4HANA - SAP for Me
3636986 - SAPUI5 maintenance strategy for SAP_UI - SAP for Me
3327306 - Edge HTML control: Blank page is displayed when HTML application is opened outplace in Edge browser / extension "SAP GUI connector for Microsoft Edge" does not seem to work - SAP for Me
SAP Design System
SAP Fiori Design Guidelines – Version 1.90 Now Ava... - SAP Community

SSO

SAML2 Configuration for SAP ABAP Platform - SAP Community
SAML 2.0 Bearer Assertion Flow for OAuth 2.0 Client | SAP Help Portal
2801396 - SAP Global Trust List - SAP for Me
ABAP Platform | SAP Help Portal
SAP GUI connector for Microsoft Edge - Microsoft Edge Addons
3382644 - How to avoid "About:blank" Edge browser window using Webview2 runtime without SAP GUI Connector for Edge - SAP for Me
Setting Up SSO for SAP Fiori Landscapes | SAP Help Portal
User Authentication and Single Sign-On (SSO) | SAP Help Portal
3366013 - SAP Fiori (/n/ui2/flp) is asking for credentials after S/4HANA or SAP Fiori Front-end Server upgrade - SAP for Me
2694092 - HTTP error 500 from myssocntl service - SAP for Me
3268335 - Single Sign On (SSO) is not working on the first call of web-based transaction through SAP GUI when Edge browser control is enabled - SAP for Me
2913405 - SAP GUI for Windows: Dependencies to browsers / browser controls - SAP for Me
701205 - Single Sign-On using SAP Logon Tickets - SAP for Me
1562004 - Option: Issueing assertion tickets without logon tickets - SAP for Me
2729853 - Web Browser warning "Connection is insecure" trying to access Fiori, WebDynpro, NWBC, BSP, Webgui, SolMan, SUM, S4/HANA or Netweaver WebUI with https:// URL - SAP for Me
2483210 - HTTP 500 error occurs when calling SAPGUI transactions - the call is stuck in the /sap/public/myssocntl service - SAP for Me
How to configure SSO with Fiori Launchpad and Goog... - SAP Community
2616249 - T-코드 /UI2/FLP를 사용하여 Fiori LaunchPad를 여는 동안 SSO를 구현하는 방법 - SAP for Me
2530317 - Fiori: SSO not working after running a Web dynpro or transaction app - SAP for Me
How to Configure Fiori Launchpad and Web Dispatcher to Support SAML2 Using SAP Cloud Identity Provider | SAP Help Portal
2460180 - SSO failed in transaction NWBC, SOAMANAGER, SOLMAN_SETUP, SM_WORKCENTER, DBACockpit, ILM_SB, FLP etc. - SAP for Me
3412687 - SAP GUI connector - 500 internal error when opening web transactions - SAP for Me
3464160 - SAP GUI connector - 500 internal error when opening web transactions - SAP for Me
3441258 - SAP GUI for Window Edge control: Points to remember while using Edge browser extension "SAP GUI connector for Microsoft Edge" - SAP for Me
1531399 - Enabling SSL for Session Protection - SAP for Me
1532777 - Collective Note: ABAP Session Protection Recommendations - SAP for Me

트러블슈팅

(Conn)(GW) Connection refused | SAP Help Portal
게이트웨이 통신 에러 관련 2684713 - Error when opening an RFC connection CM_PRODUCT_SPECIFIC_ERROR (cmRc=20) in step Maintain RFCs in Managed Systems Configuration - SAP for Me
3072670 - ICM hangs during instance startup - SAP for Me

SAP Webdispatcher

SSL Parameters for ICM and Web Dispatcher | SAP Help Portal
icm/HTTPS/forward_ccert_as_header | SAP Help Portal
Forward SSL Certificates for X.509 Authentication | SAP Help Portal
icm/ssl_config_<xx> | SAP Help Portal
icm/HTTP/redirect_<xx>
wdisp/add_xforwardedfor_header | SAP Help Portal
2483210 - HTTP 500 error occurs when calling SAPGUI transactions - the call is stuck in the /sap/public/myssocntl service - SAP for Me
icm/HTTP/redirect_<xx> | SAP Help Portal
2009878 - Purpose of the PSE Files in PSE Management of SAP Web Dispatcher - SAP for Me
2339387 - Warning "There is a problem with this website's security certificate" when accessing AS ABAP via HTTPS URL - SAP for Me
1915937 - Address family not supported by protocol - SAP for Me
How to Configure Fiori Launchpad and Web Dispatcher to Support SAML2 Using SAP Cloud Identity Provider | SAP Help Portal
SAP Web Dispatcher: Setup of Communication | SAP Help Portal
908097 - SAP Web Dispatcher: 릴리스, 설치, 패치, 문서 - SAP for Me
2607849 - Logon screen is prompted repeatedly after enter Logon credentials when accessing through Web Dispatcher - SAP for Me

BPC&AO&EPM

BPC 10 for NetWeaver Authentication Scenarios - SAP Community

Security & TLS

3318423 - Is TLS 1.3 Supported by SAP Kernel for ABAP and SAP S/4HANA? - SAP for Me
2926224 - Collection Note: New security settings for SAP S/4HANA and SAP BW/4HANA using SL Toolset and SUM - SAP for Me

Solved: Change of SAPSYS Group - SAP Community