Proper command to startsap manually from command line

Proper command to startsap manually from command line.

startsap.exe name=<SID> nr=<system no> SAPDIAHOST=<host name> pf=d:\usr\sap\

<sid>\SYS\profile\START_DVEBMGS<no>_hostname

How to recover SAPMMC without re-installing CI?

How to recover SAPMMC without re-installing CI?

Open you MMC console.

Goto file-->ADD/Remove snap-in

Click on ADD

Choose SAP Systems Manager

Again Click on ADD

Click Next

Here give your SID in the system field

fill instance field like this <hostname> <instance no>

Mind space between hostname and instance no

Also check SAPservice<SID> service is running or not

KERNAL UPGRADATION IN WINDOWS

KERNAL UPGRADATION IN WINDOWS

1.        Schedule the downtime .

2.        Download the executables from Market place in the .SAR  Format  from service.sap.com/swdc.

3.         There are two types of kernel files DB Independent and DBdependent Files

        SAPEXE xxxxxxxxxxxxxxxxxxxxxx .SAR (DB Independent)

         

         SAPEXE_DB xxxxxxxxxxxxxxxxxxxxxx .SAR (DB dependent)

4.        Decompress the files using

            SAPCAR  -XVF  SAPEXE xxxxxxxxxxxxxx.SAR

            SAPCAR  -XVF  SAPEXE_DB xxxxxxxxxxxxxx.SAR

5.        Extract the files to Newly created to “new run” directory run directory

6.        Take backup of old kernel executable (Existing  kernel executable).

\usr\sap\SID\sys\exe\run

7.        Stop all the services( Stop the instances)

                   

          Services :   SAPOSCOL, SAP<SID>-<NR>, SAPROUTER.

8. copy the executables from NEWRUN executables and replace the executables in the       old run executables(old run directory).

9.start the services, instances

10. check all the startup logs to resolve the startup problems

11. if the still could not be started then COPY  “OLDRUN” AS BEFORE.

NOTE: there is a no sequence required for kernel upgrade.

Common Reasons for cancellation of SAP Background Jobs

Common Reasons for cancellation of SAP Background  Jobs

1. User and password Issues (Authentication/ Authorization) user lock, userid expiry, password change, lack of roles

etc.

2. File system problems: BTC reads from the file system to update the database. File not opened, or corrupted, file

sharing issues, file came with different characters, file not found as well.

3. Variants are not properly defined.

4. Dead locks issue (Lock mechanism congested)

5. Update mechanism failed

6. Table space over flow (ORA-1653; ORA-1654)

7. Table space max extent reached (ORA-1631; ORA-1632)

8. Archive struck (ORA-255; ORA-272)

9. The memory is not sufficient and errors

(No Roll Area, PXA (Buffer), Page Errors)

10. Problem in the program and inputs (Indefinite loops like 1/0)

11. Dependent jobs/ events failure

12. Target systems are not available to process the jobs.