IP2017 srvrmgr (Without /s Parameter) Login To Database Multiple Times.

(Doc ID 2392457.1)

Last updated on APRIL 27, 2018

Applies to:

Siebel CRM - Version 17.0 [IP2017] and later
Information in this document applies to any platform.

Symptoms

Until IP2016, srvrmgr command without /s parameter attempted to login to server database only once, no matter how many Siebel Servers were running. On IP2017, it attempts to login as many times as the number of running Siebel Servers.

There are some potential issues.
- Excessive number of login operation may affect database performance. Imagine there are 10 Siebel Servers. One srvrmgr command (without /s) login to database 10 times than IP2016 and earlier version. When srvrmgr is executed repeatedly in short period, login and other database performance may see negative impact.

- In case the incorrect password (/p) is provided, it may cause Siebel administrator account locked. Let's assume database account would be locked after five consecutive "incorrect password". When there are 10 Siebel Servers, just one execution of srvrmgr command (without /s) using the incorrect password locks SADMIN account.



Here is the observation of login attempt, based on srvrmgr and oracle audit trail (sys.aud$). To make it simple, there are two running Siebel Servers and incorrect password was given for every srvrmgr command.

<IP2017>
1) srvrmgr command
1-1) [siebel17@eo7s17o12 siebsrvr]$ date; srvrmgr /u SADMIN /p badpassword /g eo7s17o12:9007 /e SIA17
Sun Apr 22 19:38:44 PDT 2018

Connected to 0 server(s) out of a total of 2 server(s) in the enterprise
srvrmgr>

1-2) [siebel17@eo7s17o12 siebsrvr]$ date; srvrmgr /u SADMIN /p badpassword /g eo7s17o12:9007 /e SIA17 /s eo7s17o12
Sun Apr 22 19:41:20 PDT 2018

Connected to 0 server(s) out of a total of 1 server(s) in the enterprise
Failed to connect server eo7s17o12: Login failed
srvrmgr:eo7s17o12>

1-3) [siebel17@eo7s17o12 siebsrvr]$ date; srvrmgr /u SADMIN /p badpassword /g eo7s17o12:9007 /e SIA17 /s ses2
Sun Apr 22 19:42:11 PDT 2018

Connected to 0 server(s) out of a total of 1 server(s) in the enterprise
Failed to connect server ses2: Handshake failed

3) database audit trail
select SESSIONID, ENTRYID, STATEMENT, USERID, USERHOST, ACTION#, RETURNCODE, NTIMESTAMP# from sys.aud$ order by sessionid, entryid;

SESSIONID ENTRYID STATEMENT USERID USERHOST ACTION# RETURNCODE NTIMESTAMP#
---------- ---------- ---------- --------------- --------------- ---------- ---------- ----------------------------------------
3-1) 3260011 1 1 SADMIN eo7s17o12 100 1017 23-APR-18 02.38.45.386124 AM
3-1) 3260012 1 1 SADMIN eo7s17o12 100 1017 23-APR-18 02.38.46.489886 AM
3-2) 3260015 1 1 SADMIN eo7s17o12 100 1017 23-APR-18 02.41.21.974982 AM
3-3) 3260016 1 1 SADMIN eo7s17o12 100 1017 23-APR-18 02.42.12.615679 AM

** Due to UTC, there are 7 hour time difference between %time% and NTIMESTAMP#.
** 3-1) (srvrmgr without /s) recorded two audit records.

 

<IP2016>
1) Content of each batch file.
1-1) E:\S16\ses\siebsrvr\BIN>type without_s.bat
echo %time%
srvrmgr.exe /u SADMIN /p badpawssword /g localhost /e SIA16

1-2) E:\S16\ses\siebsrvr\BIN>type with_EW12S16O12.bat
echo %time%
srvrmgr.exe /u SADMIN /p badpawssword /g localhost /e SIA16 /s EW12S16O12

-1 3)E:\S16\ses\siebsrvr\BIN>type with_EW12S16O122.bat
echo %time%
srvrmgr.exe /u SADMIN /p badpawssword /g localhost /e SIA16 /s EW12S16O122

2) Execution of bath files.
2-1) E:\S16\ses\siebsrvr\BIN>without_s.bat
E:\S16\ses\siebsrvr\BIN>echo 16:46:24.99
16:46:24.99

E:\S16\ses\siebsrvr\BIN>srvrmgr.exe /u SADMIN /p badpawssword /g localhost /e SIA16
...
Fatal error (2555922): Could not open connection to Siebel Gateway configuration store (%1:%2)., exiting...

2-2) E:\S16\ses\siebsrvr\BIN>with_EW12S16O12.bat
E:\S16\ses\siebsrvr\BIN>echo 16:47:19.57
16:47:19.57

E:\S16\ses\siebsrvr\BIN>srvrmgr.exe /u SADMIN /p badpawssword /g localhost /e SIA16 /s EW12S16O12
...
Fatal error (2555922): Could not open connection to Siebel Gateway configuration store (%1:%2)., exiting...

2-3) E:\S16\ses\siebsrvr\BIN>with_EW12S16O122.bat
E:\S16\ses\siebsrvr\BIN>echo 16:48:17.52
16:48:17.52

E:\S16\ses\siebsrvr\BIN>srvrmgr.exe /u SADMIN /p badpawssword /g localhost /e SIA16 /s EW12S16O122
...
Fatal error (2555922): Could not open connection to Siebel Gateway configuration store (%1:%2)., exiting...

3) database audit trail
Select SESSIONID, ENTRYID, STATEMENT, USERID, USERHOST, ACTION#, RETURNCODE, NTIMESTAMP# from sys.aud$ order by sessionid;

SESSIONID ENTRYID STATEMENT USERID USERHOST ACTION# RETURNCODE NTIMESTAMP#
---------- ------- ---------- --------------- ------------------------------ ---------- ---------- ----------------------------------------
3-1) 2590004 1 1 SADMIN WORKGROUP\EW12S16O12 100 1017 23-APR-18 11.46.26.199000 PM
3-2) 2590005 1 1 SADMIN WORKGROUP\EW12S16O12 100 1017 23-APR-18 11.47.20.730000 PM
3-3) 2590007 1 1 SADMIN WORKGROUP\EW12S16O12 100 1017 23-APR-18 11.48.18.699000 PM

** Due to UTC, there are 7 hour time difference between %time% and NTIMESTAMP#.
** Each command attempts to login to database only once, with or without /s parameter.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms