SUM fails in PREP_INPUT/ASCS_CHK: No ASCS instance detected

SAP SUM Tool Error : SUM fails in PREP_INPUT/ASCS_CHK: No ASCS instance detected

No ASCS instance detected at SUM instance list

During the SAP S/4HANA or  ECC Upgrade/migration using SUM Tool.

SUM does not recognize ASCS/ERS instance:

SUM log shows below error

ASCS_CHK.LOG:

1 ETQ201 Entering upgrade-phase "PREP_INPUT/ASCS_CHK" ("20240805200335")

2 ETQ367 Connect variables are set for standard instance access: System-nr = '02', GwService = 'sapgw02' Client = '000'

1 ETQ200 Executing actual phase 'PREP_INPUT/ASCS_CHK'.

1 ETQ399 Phase arguments:

2 ETQ399 Arg[ALPFile] = ''

2 ETQ399 Arg[Options] = 'CHECK'

1 ETQ000 ==================================================

1 ETQ399 Standalone enqueue server detected.

2 ETQ011 --------------------------------------------------

2 ETQ399 SYSTEM MANAGER: Get all instances with type 'ASCS':

1 ETQ399 No ASCS instance detected at SUM instancelist.

1 ETQ399 ASCS Instance is detected at SAP profiles (ASCS host 'techrelam' and ASCS sysnum '01').

1 ETQ399 Standalone enqueue server is detected at profiles (ASCS host '' and ASCS sysnum ''), but no valid ASCS instance is found at SUM instancelist. Better reinit the SUM instancelist.

1 ETQ399 SAPCONTROL MANAGER: getSystemInstanceList with dumpfile: /usr/sap/TRP/SUM/SUM/abap/log/SAPCONTROL_INSTANCELIST.OUT

3 ETQ120 20240805200335: PID 30656 execute '/usr/sap/TRP/D02/exe/sapcontrol -prot NI_HTTP -nr 02 -function GetSystemInstanceList', output written to '/usr/sap/TRP/SUM/abap/log/SAPCONTROL_INSTANCELIST.OUT'.

3 ETQ122 20240805200335: PID 30656 exited with status 0 '' (time:     0.0/    0.0/    0.0/93MB real/usr/sys/maxmem)

1 ETQ399 SYSTEM MANAGER: enhance instance list for Instance Number: 02, Instance Host: hec53v031439

2 ETQ011 --------------------------------------------------

2 ETQ399 SYSTEM MANAGER: Get all instances with type 'ASCS':

1 ETQ399 No ASCS instance detected at SUM instancelist.

1EETQ399 Last generated error message is: The SUM instancelist has been rebuilt but no valid ASCS instance

1EETQ399Xcan be found! Check your system settings.

1EETQ204 Upgrade phase "ASCS_CHK" terminated with severe errors ("20240813200335")

When you check the status of the instances (sapcontrol -nr <inst no> -function GetSystemInstanceList), you get the following result:

  GetSystemInstanceList

  OK

  hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus

  <hostname>, <inst no>, ..., ... , ..., ABAP|GATEWAY|ICMAN|IGS, GREEN

It does not list ASCS instance in the output.

Resolution

1. Stop the System.
2. Fix permission issue of folder $(DIR_GLOBAL)/sapcontrol                                                  Observation: If you are using cluster for (A)SCS / ERS instance, this folder could be a NFS share. This folder must be accessible by all instances of same system / SID.
3. You can rectify the permission of this folder with the help of your OS / File system / Storage team.
4. Once it is rectified, you can test by creating a test file in the same location i.e $(DIR_GLOBAL)/sapcontrol. 
5. The command "sapcontrol -nr <inst no> -function GetSystemInstanceList" will now list (A)SCS instance.
6. Once the above steps are successful, Start the system, then repeat the phase in SUM.

Workaround Solution:

Scenario : If you are using a heterogeneous system migration where PAS and ASCS are running in a Windows environment and AAS is running in a Linux environment (such as in a RISE migration/conversion scenario), RISE will not provide a Windows system for migration. Consequently, the RISE team will not provide a Windows system for migration. As a result, we cannot share the /sapmnt folder from Windows to Linux, which means that the SUM tool cannot detect the ASCS instance from Linux. Therefore, we need to move the ASCS sapcontrol file from the Windows server to the Linux server.

The highlighted sapcontrol file for the ASCS instance can be identified by the instance number in the file name. This file contains the ASCS instance hostname and the PID (Process ID) for the operating system.

Note: The sapcontrol file is update every minute.

When you encounter an error with the SUM tool, copy the highlighted file from source windows system to the RISE system (Linux) folder location: /sapmnt/TRP/global/sapcontrol or /usr/sap/TRP/SYS/global/sapcontrol.

Once the file is moved from the source system to the target system, repeat the SUM phase. SUM will detect the ASCS instance and proceed to the next phase.

This all activity should executed within one minute and if you missed again replace the file from source to target.

Thank you for reading the blog!

 

How to reset Software Update Manager SUM tool

 

Usually we are using the below typical steps to reset the SUM process.

Follow the steps specified below to reset the SUM Process.

1. Go to the directory SUM\abap\bin.

2. Enter the command “\SAPup reset prepare”

3. Delete the SUM directory.

4. End all SAPup processes on the OS level before, if any exist.

5. Please try to run report RSUPGRES. This will solve UVERS inconsistency.

6. Start everything again from the beginning.

The report, mentioned in step 5, should be used carefully and only in emergency cases.

• Execute only with user DDIC in client 000.

• Start in background, the program takes about 20 and 30 minutes.

• The process should not be aborted manually!!!

• This report works for SUM SP10 and higher.

SAP SUM: SAPControl path is not valid in windows environment

 

SAP SUM: SAPControl path is not valid in windows environment

 We have encountered an error (as below) while performing the update activity using the SAP Software Update Manager in windows environment.

Solution

As error referred, login to your operating system (in this example, it’s Windows) using the <SID>adm.

Go to the system properties --> Advanced--> Environment variable--> user variable section--> click Path --> edit -->make sure the path (kernel directory location) is correctly maintained. example (E:\usr\sap\SID\SYS\exe\uc\NTADM64)

Deployment Error during SAP JAVA STACK SUM Update with ERRORCODE=-4229

 

During the SAP JAVA Stack Upgrade Executaton Phase getting below error in Solution Manager 7.2 JAVA stack upgrade.

Operating System : SUSE LINUX 12 SP04

Database               : DB2 LUW 11.1 MP4 FP4

ERROR :

An SAP NW AS Java System upgrade terminates with the following error reported in DEPLOY-COMPONENTS.log 

Deployment of archive /install/SAP/nw75_java_ads_15/MMRSERVER15_0-80000683.SCA --> bi~mmr~mmrlib.sda for component sap.com/bi~mmr~mmrlib abortedDetailed message: 1. [jcc][t4][102][10040][4.25.15] Batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null

Solution:

Workaround

Remove SECTION_LEVEL_LOB registry value from registry variable
DB2_RUNTIME_DEBUG_FLAGS.
Change:

 DB2_RUNTIME_DEBUG_FLAGS=TOLERANT_FLOAT,DISABLE_BLANK_TOLERANCE,
SECTION_LEVEL_LOB [DB2_WORKLOAD]
 To:

 DB2_RUNTIME_DEBUG_FLAGS=TOLERANT_FLOAT,DISABLE_BLANK_TOLERANCE [O]

Example:

> su - db2

 >db2set  DB2_RUNTIME_DEBUG_FLAGS

>  DB2_RUNTIME_DEBUG_FLAGS= TOLERANT_FLOAT, DISABLE_BLANK_TOLERANCE,
SECTION_LEVEL_LOB

>  db2set  DB2_RUNTIME_DEBUG_FLAGS = TOLERANT_FLOAT,DISABLE_BLANK_TOLERANCE

 

 

How to lock and unlock the SAP system during an upgrade!

How to lock and unlock the SAP system during an upgrade!

ISSUE:

• You get the message "Upgrade in progress: no login is possible" when trying to logon
•  You are trying to implement a Note in the system during the upgrade and get the message: "Changes in ACM are locked (decision taken by rule A)"

Solution:

1. To unlock the SAP system, enter the following commands. The system may be either the original SAP system or the shadow system, depending on which one the error occurred.
Original SAP system

cd //abap/bin
./SAPup unlocksys

Shadow system
 
cd //abap/bin
SAPup unlockshd

Log on to the SAP system or shadow system and correct the error.

2. To lock the original SAP system or shadow system again, enter the following commands:
Original SAP system
 
cd //abap/bin
./SAPup locksys

Shadow system
 
cd //abap/bin
SAPup lockshd
 

 

Duplicate key error in EDOPROCSPINTDET during NetWeaver upgrade

ISSUE:

While performing an upgrade using the Software Update Manager (SUM) there is an error in the phase MAIN_NEWBAS/TABIM_UPG or in MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC

The error message is with regard to duplicate key error during insert in table EDOPROCSPINTDET

In some cases, the insert fails for table EDOPROCSPINTDET~ in phase SHADOW_IMPORT_INC.
You will see the error similar to: Checks after phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC were negative!

*ERROR* : Detected the following errors:
# /usr/sap//SUM/abap/log/SAPKH61712.
: 4 ETW000 0 d / 0 i / 0 u / 3 = 100% ucf EDOPROCSPINTDET~ 
4ETW000 3 entries for EDOPROCSPINTDET~ merged (___SVNCINV 0001REQ_SENDSVN_CINV SD_INVOICE); as part of view EDOPROCSPINTDETV.
4 ETW000 client 000: 1 4 ETW000 client 001: 1
4 ETW000 client 910: 1 2EETW000 1 duplicate key error during insert into table EDOPROCSPINTDET~ occured 
4 ETW000 0 d / 0 i / 0 u / 0 = 0% ucf EDOPROCSPINTDET~
4 ETW000 0 entries for EDOPROCSPINTDET~ merged (___SVNCINV 0001SENDEDOCSVN_CINV FI_INVOICE); as part of view EDOPROCSPINTDETV.
2EETW000 1 duplicate key error during insert into table EDOPROCSPINTDET~ occured

Solution:

During upgrade:

1. Directly delete the index named EDOPROCSPINTDET~00 on the database for the shadow    table  EDOPROCSPINTDET~.
2. This issue is database engine independent.
3. Contact your database administrator for the database engine specific SQL commands. In most of the databases, the command will look like this: drop index ""."EDOPROCSPINTDET~00";.
If this syntax gives error, adapt it according to the database.
When it is possible on SAP side, you could use function module DB_DROP_INDEX in test mode for index named EDOPROCSPINTDET~001.
The major concern here is to just get rid of the index but without triggering any Dictionary activation or similar SAP-side activity - thus intending to limit interference with upgrade processing.
4. Repeat the phase in SUM.

Post-upgrade:

Check the indexes for the table EDOPROCSPINTDET in SE11.

If the index 001 is existing there, delete the index.

Save the table and activate.

SUM ERROR "M_PREMA", "V_7BR_PREMA" and "V_T7BRAP" tables error in ACT_TRANS or ACT_UPG phase

"M_PREMA", "V_7BR_PREMA" and "V_T7BRAP" tables error in ACT_TRANS or ACT_UPG phase ERROR

Symptom

During upgrade process, the ACT_UPG phase terminates with DDIC ACTIVATION errors "TABLE XXXX was not activated" as per the below error message:

Directory:    /SUM/abap/log

Name      :     ACTUPG.ELG

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

DDIC ACTIVATION ERRORS and RETURN CODE in SAPAAAA731.ABC

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   3 EDT014XActivate dependent table "M_PREMA"

   2WEAD275 Foreign key "M_PREMA"-"BUKRS" (dependency factor "REF" is

   incorrect here)

   2WEAD275 Foreign key "M_PREMA"-"OBRA" (dependency factor "REF" is

   incorrect here)

    1EEDT354 Search field "M_PREMA"-"FILIA" not contained in search help

    attachment

   3 EDT015 Dependent table "M_PREMA" was not activated

   3 EDO525XActivate dependent view "M_PREMA"

   1 EDH202 Check dependent search help "PREMA"

   1 EDH103 Search help "PREMA" is consistent

   3 EMC763 Key field "T7BRAP"-"GRPBR" missing

   2WEMC732 All fields are evaluated as key field

   3 EMC726 View must be created in the database

   3 EDO526 View was activated with warnings"M_PREMA"

    1EEDO519 "Table" "M_PREMA" could not be activated

   3 EDT014XActivate dependent table "V_7BR_PREMA"

   2WEAD275 Foreign key "V_7BR_PREMA"-"BUKRS" (dependency factor "REF" is

   incorrect here)

   2WEAD275 Foreign key "V_7BR_PREMA"-"OBRA" (dependency factor "REF" is

   incorrect here)

    1EEDT354 Search field "V_7BR_PREMA"-"FILIA" not contained in search help

    attachment

   3EDT015 Dependent table "V_7BR_PREMA" was not activated

   3 EDO525XActivate dependent view "V_7BR_PREMA"

   1 EDH202 Check dependent search help "HRPADBRA"

   1 EDH103 Search help "HRPADBRA" is consistent

   3 EMC763 Key field "T7BRAP"-"GRPBR" missing

   2WEMC732 All fields are evaluated as key field

   3 EMC726 View must be created in the database

   3 EDO526 View was activated with warnings"V_7BR_PREMA"

    1EEDO519 "Table" "V_7BR_PREMA" could not be activated

   3 EDT014XActivate dependent table "V_T7BRAP"

   1EEDT354 Search field "V_T7BRAP"-"FILIA" not contained in search help

   attachment

   3 EDT015 Dependent table "V_T7BRAP" was not activated

   3 EDO525XActivate dependent view "V_T7BRAP"

    1EEDO519 "Table" "V_T7BRAP" could not be activated

   1 ETP111 exit code : "8"

Reproducing the Issue

• Start SUM tool.
• In ACT_UPG phase, the error occurs.

Cause

The root cause of the issue is some fields were removed from the table T7BRAP. This action is delivered by standard packages however this is not reflecting in other objects like M_PREMA.

On the other hand M_PREMA is a Match code object which is obsolete.

Resolution

You can ignore this error and continue with the upgrade only for the specified tables.

Continue the upgrade by choosing the option 'Accept non-severe errors and repeat phase MAIN_SHDRUN/ACT_UPG' in SUM tool.

More details Refer Snote : 1909524