SNC PROD ENVIRONMENT DETAILS:

 We have 3 application servers that uses only one DB server.

 All these 3 application servers have only one BKP server.
 The DB server has one Data recovery server.

EBS: -

Database:

 SLI1610 Data Recovery Server: SLI1934

Super user: orapr

Application:

 SLI1907
 SLI1908 Backup server: SLI2100
 SLI1909

Super user: applpr

Url: https://ebs.snclavalin.com/OA_HTML/AppsLogin

Others: -

 KTM : SLI2303 (Windows)

 Capture : SLI2304 (Windows)
 Markview : SLI2335 (Linux)

Urls:

 http://sli2335.sli.bz:7001/console/login/LoginForm.jsp
 http://sli2335.sli.bz:8001/markview/mvt_mv_home.home
MinerPRD(Brazil):

 ebs2.minerconsult.com (APP)
 bd2.minerconsult.com (DB)

Url: http://ebs2.minerconsult.com:8000/OA_HTML/AppsLocalLogin.jsp

Locks in SNC:

The blocking sessions can happen when two or more users trying to access same object at
same time.

In this scenario priority should be given to the user ADMSCHEDULER and other cases as per
below guidelines.

Case1: if ADMSCHEDULER is blocked by any other user, if user session is INACTIVE then
“Kill the session” else if user session is “ACTIVE” and it is doing a ‘select’ on background
then “kill the session” else ask user to kill session himself. If no response from the user for
15 mins then “Kill the session”
Case2: if a user is blocked by another user, if first user session is INACTIVE then “Kill the
session” else if user session is “ACTIVE” and he/she blocked more users then ask user to kill
session. If no response from the user for 15 mins, then escalate it to Daniel.

For all other cases we need user response to act.

ADM SCHEDULER Error: