@sapbasishana

Database Starts

As on ABAP the first step is to check and start the database. No dedicated developer trace is created in the work directory as the database has its own logs. If the database does not start correctly it should be visible within seconds and errors will be available within the DB logs.

Developer traces: Refer to your DB logs.

Startup

JSTART is called next, it takes the role of the Java instance controller which analyzes its configuration and initializes SAP signal handling and opens the control port.

There is very rarely an issue with the initial load of JSTART. If for some reason this fails you most likely have a problem with your instance profile.

Developer traces: dev_jstart

Offline Deployment

The Java instance controller reads the instance definition and creates a child process that initializes JVM and starts the OFFLINE DEPLOYMENT program which performs the deployment steps in the Java database.

In the 'business as usual' scenario this is very unlikely to end up in an error. These days most deployments are done automaticaly using SUM, the traces will be filled when the instance is stopped and started during the SUM deployment phase.

Developer traces: dev_deployment, std_deployment.out and jvm_deployment.out

Bootstrap

BOOTSTRAP synchronizes the binary data in the Java database with the local file system.

This is where you will most likely find issues during your system startup.
@sapbasishana
@KPONLINEOFFICIAL
For MORE details - contact: KPONLINETRAININGS@GMAIL.COM

#SAP #BASIS #SAPHANA #SAPECC #TRAINING #PRACTICAL #JOBORIENTED #HANDSON
#MIGRATION #S/4HANA #s4hana #IT #freshersjob #FRESHERTRAINING #freshersworld #STUDENT # ​#REALTIMETRAINING #BEGINERS #saphanatraining #saptraining #sapbtp #sapbasis #saptraining #sapbasishana

свернуть