啓動siebelserver失敗，錯誤日誌如下，
SBA_81/appcnbj050/log/SRBroker_0003_3145731.log8.1.1.5 [21229] ENU
DBCLog DBCLogError 1 00063df054df691b:0 2015-02-1508:48:02 [DataDirect][ODBC Oracledriver][Oracle]ORA-01017: invalid username/passwo
rd; logon denied
DBCLog DBCLogError 1 00063df054df691b:0 2015-02-1508:48:02 [DataDirect][ODBC Oracledriver]File not found '.odbcinst.ini'.
GenericLog GenericError 1 00063df054df691b:0 2015-02-1508:48:02 (srbthrd.cpp (4022)err=2097168 sys=0) SBL-SRM-00016: Unable to in
itialize theDatabase environment -- Unable to connect to DB (data ops)
GenericLog GenericError 1 00063df054df691b:0 2015-02-1508:48:02 (srbmtsrv.cpp (86)err=2097168 sys=0) SBL-SRM-00016: Unable to ini
tialize the Databaseenvironment -- Unable to connect to DB (data ops)
SrbLayerLog Error 1 00063df054df691b:0 2015-02-15 08:48:02 Main Init fails
GenericLog GenericError 1 00063df054df691b:0 2015-02-1508:48:02 (smimtsrv.cpp (1203)err=2097168 sys=0) SBL-SRM-00016: Unable to i
nitialize theDatabase environment -- Unable to connect to DB (data ops)
SmiLayerLog Error 1 00063df054df691b:0 2015-02-15 08:48:02 Terminate process due to unrecoverableerror: 2097168. (Main Thread)
從錯誤信息初步看是帳號密碼有問題，
問題排查過程：
1.檢查SADMIN DB帳號密碼沒問題
2.sqlplusSADMIN/xxxx@sss 連接DB 沒問題
3.srvrmgr 連接GW ,沒問題
conn GW:
srvrmgr /e SBA_81 /gappcnbj066 /u SADMIN /p XXXXXX
4.檢查環境變量LD_LIBRARY_PATH
type echo$LD_LIBRARY_PATH
cat .odbc.ini
5.檢查ODBC用到的依賴的包
type ldd/app/siebel/sia811/siebsrvr/lib/SEor823.so
cat ../sys/.odbc.ini
6.檢查ODBC連接 沒問題
odbcsql /usadmin/p <pwd /s SBA_81_DSN
srvrmgr /u sadmin /p<pwd> /g <GW> /e <ent>
前面排查下來好像沒什麼問題
最後因爲錯誤是由組件SRBROKER報錯出來，所以到siebel裏檢查SRBROKER組件帳號相關參數，Admin-ServerConfirguation=>Server=> select appcnbj049 Components 查 SRBroker，找到參數username,發現appcnbj049和50下的username不一樣，49下username是SADMIN，有問題的50下是另一帳號，系統默認帳號就應該是SADMIN，不知道什麼時候改了username,於是在50下把username改爲默認的SADMIN，並相應改下參數password，
再啓動siebelserver,果然服務起來了。
以下是support的解釋：
u have set theuser/pwd at server/comp level for SRBROKER on server 50. Every time u changeSADMIN pwd u must set it hre also unless u use the "delete parameteroverride" option which will reset back to ent level
As we saw on thewebex you had the USERNAME parameter for SRBRoker component set to a non SADMINuser. This was set differently (SADMIN) on server 49. After we set USERNAME toSADMIN and password the Siebel server started correctly.
As explained on thecall as you have set the password for SRBROKER at component level each time youchange the password for SADMIN you must change the password at SRBROKERcomponent level also.
Alternatively youcan use the "delete parameter override" option to reset this toenterprise level.