Wednesday, 18 September 2019

What to do Changing host name on SAP R/3 host


To do Changing host name on SAP R/3 host.

Before changing host name perform in R/3:

finish all jobs and cancel already released jobs
(use transaction SM37; reason: after change of host name they have to be rescheduled with new host name)
check SM13 for any outstanding update requests and either post resp. delete them (errorneous ones)


  • stop R/3 and database
  • Actions in Operating system: UNIX host:

1. user root:

a) change host name in /etc/hosts:
CAUTION: If Yellow Pages or Name Server active change the host name in the corresponding location !

b) If old host name = system name, this must also be changed to the new host name:
check by command: uname -a
change as user root

c) Windows NT (not feasible for a domain PDC or BDC):

  • adapt network settings in the control panel
  • adapt IP name resolution resources (DNS, HOSTS file, LMHOSTS file)
  • adapt SAP service definitions in the registry
  • adapt enviroment settings for interactive session and for R/3 kernel in the registry


2. user adm on UNIX host:

a) Adapt Instance-Profiles:

  • cd /usr/sap//SYS/profile
  • check R/3 profiles: _DVEBMGS00, DEFAULT.PFL and START_DVEBMGS00


NOTE: It is assumed that instance profile maintenance is not performed with CCMS ! (see topic 6.) The following is valid for ORACLE only: For other databases please adapt accordingly.

b) User adm and ora:

  • check by "env" if variable TWO_TASK has been set
  • check profiles .cshrc and .kshrc, .dbenv.csh and .dbenv.sh


c) User adm:
change name of:

  • startsap__00 --> startsap__00
  • stopsap__00 --> stopsap__00
  • change alias for "stopsap" and "startsap" in .cshrc and .kshrc


3. Work on your front ends (most PC's):

a) update HOSTS-File
b) adapt SAPLOGON/SAPGUI configurations
c) adapt configuration of external RFC application

4. Further adaptions:
a) configuration files:

  • /usr/sap/trans/.sapconf
  • /etc/sapconf

b) environment for transport and put:
/usr/sap/trans/bin: TPPARAM
check: tp connect must be ok
/usr/sap/put/bin : TPPARAM or similar (if present).


Tuesday, 17 September 2019

SAP Outdated Operating System supported SWPM Download location in SAP Portal.



Software Provisioning Manager 1.0 supports the following provisioning scenarios for SAP systems based on SAP NetWeaver:

  • Installation of new systems, instances, and standalone engines
  • System copy of existing systems
  • Transformation of systems such as via System Rename and Dual-Stack Split
  • Deletion of systems, instances, and standalone engines


SAP is going to restrict the maintenance for operating system versions that have been initially released with SAP Kernel 7.20 but are no longer supported for SAP Kernel 7.40 and higher. The following Software Provisioning Manager operating system versions are affected:
  • AIX 64BIT: < 6.0
  • HP-UX ON PA-RISC 64BIT
  • HP-UX ON IA64 64BIT: < 11.31
  • LINUX ON IA64 64BIT
  • LINUX ON X86_64 64BIT, LINUX S390X 64BIT, LINUX PPC 64BIT: SLES9, SLES10, SLES11 (

Use this below link to download outdated OS supported SWPM from SAP Support portal.

Get the *RMOS*.SAR archive

You must download the SWPM 1.0 SP26 Media and extract your special variant of *RMOS*.SAR archive.




Monday, 16 September 2019

SAP S/4HANA 1809 FPS2 Always-On Business Functions



 SAP S/4HANA Business Functions can have the following status: always_on , customer_switchable , and always_off . This results in the following behavior during the conversion:

 If a business function was switched on in the start release system, but defined as always_off in SAP S/4HANA, on-premise edition, then a system conversion is not yet possible with this release at the current point in time.

 If a business function was switched off in the start release system, but defined as always_on in the target release, then the business function will be automatically activated during the conversion.

For a full list of always_on Business Functions in SAP S/4HANA1809 FPS2

  • /CCEE/LOC_01
  • /PLMU/COEX_IPPE_BOM
  • /PLMU/ER_1
  • /PLMU/ER_2
  • /PLMU/GSS_E2M
  • /PLMU/IPPE_INT
  • /PLMU/IPPE_INT_2
  • /PLMU/IPPE_INT_3
  • /PLMU/IPPE_INT_4
  • /PLMU/IPPE_INT_5
  • /PLMU/PI_BCV
  • /PLMU/RCP_1
  • /PLMU/RCP_2
  • /PLMU/RCP_3
  • /PLMU/RCP_3_1
  • /PLMU/RCP_3_2
  • /PLMU/RCP_3_3
  • /PLMU/WEB_UI
  • /PLMU/WEB_UI_2
  • /PLMU/WEB_UI_3
  • /SAPMP/GEN_CI_1
  • /SAPMP/PP_CMTSBVAL
  • /SAPMP/USER_PROD
  • /SCWM/EWM_S4_ADAPT
  • /STTPEC/DDIC_S4H
  • AD_GPD_CI_1
  • AD_GPD_CI_2
  • AD_MRO_CI_1
  • AD_MRO_CI_2
  • AD_MRO_CI_3
  • AUTO_CI_1
  • AUTO_DP_1
  • AUTO_DP_2
  • BSCBN_HANA_NAV
  • BSESH_HANA_SEARCH
  • CA_BP_SOA
  • CA_ECH_1
  • CA_SUPPLIER_SOA
  • CO_ALLOCATIONS
  • DA_ARCHOBJ_STANDARD_1
  • DA_ARCHOBJ_STANDARD_2
  • DA_ARCHOBJ_STANDARD_3
  • DA_ARCHOBJ_STANDARD_4
  • DFPS_MRO_PDR
  • DIMP_SDUD
  • DRF_FOUNDATION
  • EA-FIN
  • EA-FS
  • EA-GLT
  • EA-PLM
  • ERP_CA_INT_ADD_VERSN
  • ERP_CA_SIDEPANEL
  • ERP_CF_INTEGRATION_1
  • ERP_ECC_MSP_EA
  • ERP_ENTERPRISESEARCH
  • ERP_UID_01
  • ERP_UID_02
  • ERP_UID_03
  • FDT_TEST_ENTERPRISE_BF_ON
  • FIN_AA_SEGMENT_REPORTING
  • FIN_BL_EB_1
  • FIN_CO_CCMGMT
  • FIN_CO_CCPLAN
  • FIN_CO_ORPLAN
  • FIN_FSCM_CCD
  • FIN_FSCM_CCD_2
  • FIN_FSCM_CCD_3
  • FIN_FSCM_CCD_INTEGRATION
  • FIN_FSCM_CCD_INTEGRATION_3
  • FIN_FSCM_INTEGRATION
  • FIN_GL_CI_1
  • FIN_GL_CI_2
  • FIN_GL_CI_3
  • FIN_GL_ERR_CORR
  • FIN_GL_ERR_CORR_SUSP
  • FIN_INHOUSE_CASH_1
  • FIN_LOC_CI_1
  • FIN_LOC_CI_11
  • FIN_LOC_CI_13
  • FIN_LOC_CI_14
  • FIN_LOC_CI_15
  • FIN_LOC_CI_17
  • FIN_LOC_CI_18
  • FIN_LOC_CI_19
  • FIN_LOC_CI_2
  • FIN_LOC_CI_23
  • FIN_LOC_CI_25
  • FIN_LOC_CI_26
  • FIN_LOC_CI_27
  • FIN_LOC_CI_29
  • FIN_LOC_CI_30
  • FIN_LOC_CI_31
  • FIN_LOC_CI_33
  • FIN_LOC_CI_35
  • FIN_LOC_CI_36
  • FIN_LOC_CI_39
  • FIN_LOC_CI_4
  • FIN_LOC_CI_40
  • FIN_LOC_CI_41
  • FIN_LOC_CI_42
  • FIN_LOC_CI_44
  • FIN_LOC_CI_45
  • FIN_LOC_CI_46
  • FIN_LOC_CI_7
  • FIN_LOC_CI_8
  • FIN_LOC_CI_9
  • FIN_LOC_FSCM_1
  • FIN_LOC_FSCM_2
  • FIN_LOC_FSCM_3
  • FIN_LOC_FSCM_4
  • FIN_RTC_BASIC_1
  • FIN_TRM_AN
  • FIN_TRM_CCC
  • FIN_TRM_CFAR
  • FIN_TRM_CORR_FW
  • FIN_TRM_CORR_FW_2
  • FIN_TRM_CS
  • FIN_TRM_CVA
  • FIN_TRM_FX_HACC
  • FIN_TRM_FX_HACC_2
  • FIN_TRM_FX_HACC_3
  • FIN_TRM_FX_HACC_4
  • FIN_TRM_FX_HMGMT
  • FIN_TRM_FX_HMGMT_2
  • FIN_TRM_FX_HMGMT_3
  • FIN_TRM_FX_HMGMT_4
  • FIN_TRM_FXPT
  • FIN_TRM_INS_HM
  • FIN_TRM_INS_HM_2
  • FIN_TRM_LR_FI_AN
  • FIN_TRM_LR_FI_AN_2
  • FIN_TRM_LR_FI_AN_3
  • FIN_TRM_LR_FI_AN_4
  • FIN_TRM_LR_FI_AN_5
  • FIN_TRM_LR_FI_AN_6
  • FIN_TRM_MME
  • FIN_TRM_PERF_OPT
  • FIN_TRM_TRADE_FIN
  • FIN_TRM_TRADE_FIN_2
  • FIN_TRM_YCF
  • FND_ANALYTICS_TOOLS
  • FND_ANALYTICS_TOOLS_2
  • FND_EPT_PROC_ORCH_1
  • FND_SOA_REUSE_1
  • IS_AD_S2K_VER_2014
  • ISR_APPL_AGENCY_4
  • ISR_APPL_AGENCY_5
  • ISR_APPL_AGENCY_6
  • ISR_APPL_CRM_INTEG
  • ISR_APPL_USABILITY
  • ISR_GLT_COMMODITY_4
  • ISR_GLT_COMMODITY_5
  • ISR_GLT_VENDOR_FUND
  • ISR_GLT_VENDOR_FUND_2
  • ISR_RET_AGENCY
  • ISR_RET_AGENCY_2
  • ISR_RET_AGENCY_3
  • ISR_RET_COMMODITY
  • ISR_RET_COMMODITY_2
  • ISR_RET_COMMODITY_3
  • ISR_RET_COMPENSATION
  • ISR_RETAIL_CI
  • ISR_RETAIL_MATERIAL_LEDGER
  • ISR_RETAIL_USABILITY
  • JVA
  • JVA_CUTB_REVERSE
  • JVA_GL_INTEGRATION
  • JVA_INFS_VALIDREP
  • JVA_REP_SIMPL
  • LOG_BM_CC1
  • LOG_EAM_ELBK
  • LOG_EAM_POM
  • LOG_EAM_POM_2
  • LOG_EAM_ROTSUB
  • LOG_EAM_ROTSUB_2
  • LOG_EAM_WTY
  • LOG_EHS_CI_2
  • LOG_EHS_CI_4
  • LOG_EHS_DG_CI_3
  • LOG_EHS_GLM_CI_4
  • LOG_EHS_PS_CI_3
  • LOG_EHS_PS_CI_5
  • LOG_EHS_PS_CI_6
  • LOG_LE_INTEGRATION
  • LOG_MM_CI_1
  • LOG_MM_MAA_1
  • LOG_MM_OM_1
  • LOG_MM_OM_2
  • LOG_MM_OPTIMIZATIONS
  • LOG_MM_SERNO
  • LOG_MM_SIT
  • LOG_PP_CI_1
  • LOG_PP_EWM_MAN
  • LOG_PP_EWM_MAN_2
  • LOG_PP_LMAN
  • LOG_PP_LMAN_02
  • LOG_PP_MES_INT_01
  • LOG_PP_MES_INT_02
  • LOG_PP_MES_INT_03
  • LOG_PP_MIS
  • LOG_PP_PI_EHM
  • LOG_PP_PI_PMA_01
  • LOG_PP_PMA_PMC
  • LOG_PP_PROD_ORD_SPLIT
  • LOG_PP_SRN_02
  • LOG_PP_SRN_CONF
  • LOG_PP_WIP_BATCH
  • LOG_PP_WIP_BATCH_02
  • LOG_PP_XS_01
  • LOG_PP_XS_RTG_PO
  • LOG_PPH_MDPSX_READ
  • LOG_SCM_CUSTVEND_INT
  • LOG_SCM_EQUIFUNCLOC_INT
  • LOG_SCM_EWM_INT
  • LOG_SD_CI_01
  • LOG_SD_EDIMON
  • LOG_SD_JAM_INTEG_CDS
  • LOG_SD_PRICE_LIST
  • LOG_SD_PRICE_LIST_2
  • LOG_SDMM_INCO_VERSIONS
  • LOG_SEGMENTATION
  • LOG_TM_IV_INT
  • LOG_TM_ORD_INT
  • LOG_TM_ORD_INT_II
  • LOG_TM_ORD_INT_III
  • LOG_TM_ORD_INT_IV
  • LOG_WTYRCL_REPORT_OPT
  • MDG_CONSOLIDATION_CUSTOBJ_2
  • MDG_CONSOLIDATION_CUSTOMER
  • MDG_CONSOLIDATION_CUSTOMER_2
  • MDG_CONSOLIDATION_MATERIAL_2
  • MDG_CONSOLIDATION_SUPPLIER
  • MDG_CONSOLIDATION_SUPPLIER_2
  • OPS_ADVRETURNS_1
  • OPS_ADVRETURNS_2
  • OPS_QM_EXTENSION_2
  • OPS_QM_EXTENSION_3
  • OPS_QM_EXTENSIONS
  • OPS_QM_NOTIFICATION
  • OPS_QM_PLAN_INTEGRAT
  • OPS_QM_VP
  • PLM_CPDC_DMS_INT
  • PLM_MDOC_DMS_INT
  • PLM_PMEVC_1
  • PLM_RM_PRODUCT_LABELING
  • PLM_VCHLL_HANA
  • PLM_VIP_1
  • PLM_VMP_1
  • PLM_VMP_2
  • PMD_PLM_RECIPE_MANAGEMENT_1
  • PRS_GEN_UI
  • PSM_FM_BCS_AVC
  • PSM_FM_BCS_CI_1
  • PSM_FM_BCS_FMAA_DESCR
  • RE_CO_INTEGRATION
  • RE_CRE_MISC
  • RE_GEN_CI_1
  • RE_GEN_CI_2
  • RE_GEN_CI_3
  • S4H_AATP
  • SCM_APO_ON_ERP
  • SCM_APO_PPDS_PI
  • SCM_APO_VERSION_SIM
  • SCM_EHS_DG_CI_1
  • SCM_EWM_FND
  • SCM_EWM_MEAN
  • SCM_PPDS_ON_ERP
  • SCM_SAPTM_SCMB_FND
  • SD_01
  • SIMPLIFY_ON_PREMISE
  • SMC_ACTIVITY_MGT_1
  • SMC_SUPPL_DATA_MGT_1
  • SMC_SUPPL_EVAL_1
  • UI_FRW_1
  • UI_FRW_1_DOCU


Wednesday, 11 September 2019

SAP HANA Database Index Server crash due to missing LogSegment file.

Issue:

You are using HANA Reversion 49 and below. The indexserver of the SAP HANA database crashes or fail to starts with following message in crash stack dump:

Cannot open file "//logsegment_000_XXXXXXXX.dat", rc=2: No such file or directory (X=digits)

Reason and Prerequisites

You are using HANA Rev 49 and below.

You recently attempted to execute the following statement:

"ALTER SYSTEM RECLAIM LOG"

And during the execution process the statement is abnormally terminated with the following scenario:

  •     I/O Failure
  •     File System Corruption
  •     Disk Full
  •     Crash
  •     Deadlock


This potentially created an inconsistency between internal metadata and actual log segment file on the disk. In certain case index server will attempt to look for certain non-existing log segments and crash.

This workaround is only intended if there is an inconsistency where log segment file is being marked as "freed" in internal metadata but the actual file got deleted in the file system. For any other logsegment corruption issue this note does not apply to you.

To verify this please login with adm account and run:

hdblogdiag -s and compare if the file listed here got deleted on the file system.

 
Solution

To apply this workaround:

        1. Created a dummy zero byte log segment file using the following command with adm user:

    touch //logsegment_000_XXXXXXXX.dat
    2. Restart the index server. Depends on the setting, you should notice that the dummy zero byte file was inflated to 1,073,741,824 bytes. If index server crash again but with different missing log segment file with increased serial number, repeat step 1 until no furthur crash occurs.

    3. DO NOT RUN ANY UPDATE/INSERT STATEMENT RIGHT NOW. The persistency layer will look for another non existing log segment file if too much change occured and indexserver will crash again.

    4. Run "ALTER SYSTEM RECLAIM LOG" query. HANA will rebuild/realign the internal meta data.

   5. Run the following query and verify all log segment files listed in the result does physically exist in the file system:

    SELECT * FROM M_LOG_SEGMENTS
Please note this issue has been resolved in Rev 50. With the fix a warning message will be printed in the trace file instead of crash if any of the log segments marked as "freed" is missing from the file system.





More Details refer KBA:1788692

Tuesday, 10 September 2019

ST22 Runtime error DBIF_RSQL_INVALID_RSQL


Issue:

Runtime error DBIF_RSQL_INVALID_RSQL occurs.
The error analysis shows: Possible error causes:
 

1. The maximum size of an SQL statement was exceeded.

2. The statement contains too many input variables.

3. The input data requires more space than is available.
 

The developer trace file shows:

B *** ERROR => dbtran (prepare_bulk_cond): FOR ALL ENTRIES statement on table '' is too complex [dbtran.c 15294] B *** ERROR => Computed size of input values (78140) exceeds max. input buffer size (40960) [dbtran.c 15318] In later kernel releases, 7.41 and higher, the problem produces a runtime error with the code DBSQL_FAE_STATEMENT_TO_BIG, and the internal information shows something similar to:


The value of "values_sz" is 44892. This is greater than value 40960 of "buffersize".


Possible errors.

DBIF_RSQL_INVALID_RSQL, FOR ALL ENTRIES, FAE, complex, 40960, MAX_ARRAY_BUF_SIZE

Reason and Prerequisites:


DBSL parameter MAX_ARRAY_BUF_SIZE (the maximum size of the input/output buffer for array operations) for SQL Server has the value of 40960. 


Resolution:

A new DBSL patch has been provided where this value can be increased by setting profile parameter dbs/mss/array_buf_size. The parameter is specified in bytes. It is recommended to set it to a multiple of 40960.



Note: This parameter is now available in all kernel versions 7.00 and higher.






more details SAP KBA: 1414232

Sunday, 8 September 2019

SAP HANA Installation [2.0 SPS 04]: Server Installation | #TECHRELAM