/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 수동 셧다운
댓글 없음:
댓글 쓰기