Applies to:
Siebel System Software - Version 7.5.3 [16157] to 8.1.1.8 SIA [23012] [Release V7 to V8]
Information in this document applies to any platform.
Error Message Area:Server Request Manager - SRM
Version:Siebel 7.5.3
Purpose
This document is intended to provide cause and corrective action
information about Siebel Error Message SBL-SRM-00016: Unable to
initialize the Database environment -- %1
Scope
This document is informational and intended for any user.
Details
Explanation
The process could not connect to the database using the specified configuration information.
Corrective Action
The following list includes possible causes of this error:
1) The ODBC datasource is not setup correctly,
2) The database connect string at the enterprise or server level is not correct,
3) The user name or password at the enterprise or server level is not correct,
4) The correct version of the SQL template file (e.g. comdb41.sql) is not in the bin or sqltempl directory.
If the error is not caused by any of the above reasons, increase the log level for all events and get more information.
Applies to:
Siebel CRM - Version 8.0.0.13 SIA [20448] and later
Information in this document applies to any platform.
Symptoms
8.0.0.13 Fix Pack has been applied to the Siebel 8.0.0.10 SIA system
on Linux. When Siebel Server was started on 8.0.0.13, SRBroker failed
with the error message "SBL-SRM-00016: Unable to initialize the Database
environment -- Unable to connect to DB (data ops)". It did not occur on
8.0.0.10.
Changes
As "Web server will not start for Siebel CRM version 8.0.0.13,
8.1.1.6 or 8.2.2 on Linux with OHS 10g (Doc ID 1375035.1)" mentions,
Oracle HTTP Server (OHS) has been upgraded from 10g to 11g as a part of
process.
Cause
In the SRBroker_0002_2097155.log file, following messages were recorded.
SrbLayerLog Info 4 000382b04fc84014:0 2012-06-01 19:59:47 Connecting to sadmin@SBA_80_dev_DSN - Table owner SIEBEL
DBCLog DBCLogDetail 4 000382b04fc84014:0
2012-06-01 19:59:47 Dynamically loading ODBC library functions
DBCLog DBCLogDetail 4 000382b04fc84014:0
2012-06-01 19:59:47 Successfully loaded ODBC library functions
...
DBCLog DBCLogError 1 000382b04fc84014:0 2012-06-01 19:59:47 [DataDirect][ODBC lib] Connection not open
...
GenericLog GenericError 1 000382b04fc84014:0 2012-06-01 19:59:47
(srbthrd.cpp (4005) err=2097168 sys=0) SBL-SRM-00016: Unable to
initialize the Database environment -- Unable to connect to DB (data
ops)
Note: "SBL-SRM-00016" is a generic error message and the important
one is "[DataDirect][ODBC lib] Connection not open", returned by ODBC
driver.
Based on the above messages, odbcsql was used instead of starting Siebel Server. Then it generated the same error as below.
Logging into "SBA_80_dev_DSN" as "SADMIN" ...
ODBC error 08003 in SQLConnect:
[DataDirect][ODBC lib] Connection not open
(native error 0).
Unable to login using specified ODBC parameters.
Following commands were used to narrow down the cause of the error.
$ strace -f -s 1024 -o output odbcsql /s SADMIN /p Password /s SBA_80_dev_DSN
8530 open("/opt/ibm/ldap/V6.0/lib/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
8530 open("/sbl01/bin/sbl/siebsrvr/lib/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
8530 open("/sbl01/bin/sbl/siebsrvr/mw/lib/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
8530 open("/sbl01/bin/sbl/siebsrvr/SYBSsa90/lib/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
8530 open("/usr/lib/tls/i686/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
8530 open("/usr/lib/tls/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
8530 open("/usr/lib/sse2/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
8530 open("/usr/lib/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
8530 open("/lib/tls/i686/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
8530 open("/lib/tls/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
8530 open("/lib/i686/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
8530 open("/lib/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
8530 open("/usr/lib/tls/i686/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
8530 open("/usr/lib/tls/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
8530 open("/usr/lib/sse2/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
8530 open("/usr/lib/libclntsh.so", O_RDONLY) = -1 ENOENT (No such file or directory)
$ env | grep LD_LIBRARY_PATH
LD_LIBRARY_PATH=/opt/ibm/ldap/V6.0/lib:/sbl01/bin/sbl/siebsrvr/lib:/sbl01/bin/sbl/siebsrvr/lib/odbc/merant:/sbl01/bin/sbl/siebsrvr/mw/lib:/sbl01/bin/sbl/siebsrvr/SYBSsa90/lib:/usr/lib
The output from strace revealed "libclntsh.so" could not be found in
specified path. Comparing the output from env command, it was found the
environment variable LD_LIBRARY_PATH did not include "lib" directory for
Oracle Client so that odbcsql and SRBroker could not connect to Oracle
Database.
Part of the upgrade process for OHS, the environment variable
LD_LIBRARY_PATH was modified but it did not include the new "lib"
directory for Oracle Client.
Solution
Please make sure the environemnt variable LD_LIBRARY_PATH has the "lib" directory for Oracle Client (32 bit version).
Note: After the environment varaible LD_LIBRARY_PATH was set
correctly, odbcsql still failed with the same error. Again the output
from strace showed the new error message TNS-12564 was written to
log.xml as well as sqlnet.log. Based on the error, TNS setting was
reviewed and modified by DBA then odbcsql as well as components on
Siebel Server started successfully.
Note: If Oracle Database Server is 64 bit, please make sure Siebel
Server uses 32 bit version of Oracle Client. If 64 bit version is used,
the same error would occurs on odbcsql. Please review LD_LIBRARY_PATH to
make sure 32 bit "lib" is specified and it is ahead of 64 bit "lib" in
case both need to be specified.
Applies to:
Siebel System Software - Version 7.5.3.8 [16192] to 8.1.1.8 [23012] [Release V7 to V8]
HP-UX Itanium
Product Release: V7 (Enterprise)
Version: 7.5.3.8 [16192]
Database: Oracle 9.0.1
Application Server OS: HP-UX 10.0
Database Server OS: HP 9000 Series HP-UX
This document was previously published as Siebel SR 38-2284009791.
*** Checked for relevance on 08-Dec-2010 ***
*** Checked for relevance on 29-Oct-2012 ***
Symptoms
SBL-DAT-00446, SBL-OMS-00102, SBL-OMS-00107, SBL-SRM-00016
In the server.log the following error messages are generated:
ServerLog ProcessCreate 1 2005-07-18
19:17:25 Created multithreaded server process (OS pid = 2648) for
Server Request Processor with task id 31756
ServerLog ProcessExit 1 2005-07-18 19:17:51 SRBroker 31754 TERMINATED Process was terminated
ServerLog ProcessExit 1 2005-07-18 19:17:58 SRProc 31756 TERMINATED Process was terminated
ServerLog ProcessExit 1 2005-07-18 19:17:58 BusIntBatchMgr 31749 TERMINATED Process was terminated
ServerLog ProcessExit 1 2005-07-18 19:17:59 WfProcBatchMgr 31747 TERMINATED Process was terminated
ServerLog ProcessExit 1 2005-07-18 19:17:59 WfProcMgr 31748 TERMINATED Process was terminated
ServerLog ProcessExit 1 2005-07-18 19:17:59 BusIntMgr 31750 TERMINATED Process was terminated
______________________________________________________________
The error being generated in the SR_BROKER.log is:
GenericLog GenericError 1 2005-07-18 17:18:23 Unable to verify login name SIEBEL.
GenericLog GenericError 1 2005-07-18
17:18:23 (srbthrd.cpp 44(3901) err=3200016 sys=0) SBL-SRM-00016:
Unable to initialize the Database environment -- Unable to start common
api
GenericLog GenericError 1 2005-07-18
17:18:23 (srbmtsrv.cpp 39(71) err=3200016 sys=0) SBL-SRM-00016:
Unable to initialize the Database environment -- (null)
_____________________________________________________________
Note: We are able to log into Siebel through the thin client.
Cause
.
Solution
For the benefits of other users:
There are a lot of error
logging in to the application and logon error reported in various
component log files. After setting the User Name and Password parameter
at Site Map > Server Administration > Enterprise Configuration
> Enterprise Parameters, the component start up properly from Server
Administration -> Servers -> Server Components screens. But the
logon error reoccurs whenever restart the Siebel server.
Solution:
After changing the User Name and Password parameters, select "Start Reconfiguration" then "Commit Reconfiguration".
Applies to:
Siebel CRM Service, SPE - Version 8.0 [20405] to 8.0 [20405] [Release V8]
Information in this document applies to any platform.
Symptoms
Statement of what the issue is
After a fresh installation, the Server Request Broker component fails to initialize at startup
ERROR generated in Siebel Enterprise log
-------------------------------------------------
ServerLog ComponentUpdate 2 0000290248210580:0 2008-05-07 14:18:31 SCBroker INITIALIZED Component has initialized.
GenericLog GenericError 1 00007988482104d8:0 2008-05-07 14:18:34
(scirkey.cpp (1142) err=1310772 sys=2) SBL-SVR-00052: Internal: Invalid
proc handle
ServerLog ProcessExit 1 00007988482104d8:0 2008-05-07 14:18:34 SRBroker 3584 TERMINATED Process 3584 was terminated
GenericLog GenericError 1 0000290248210580:0 2008-05-07 14:23:26
ERROR generated in Server Request Broker log
---------------------------------------------------------
ServerLog LstnObjInherit 3 0000000248210e00:0 2008-05-07 14:18:26 Inherited listening object for port 49177
ServerLog LstnObjPrivCreate 3 0000797f482104d8:0 2008-05-07 14:18:26 Created port 49180 for Server Request Broker
DBCLog DBCLogError 1 0000797f482104d8:0 2008-05-07 14:18:29 [DataDirect][ODBC Oracle driver][Oracle]ORA-12541: TNS:no listener
GenericLog GenericError 1 0000797f482104d8:0 2008-05-07 14:18:29
(srbthrd.cpp (3997) err=2097168 sys=0) SBL-SRM-00016: Unable to
initialize the Database environment -- Unable to connect to DB (data
ops)
GenericLog GenericError 1 0000797f482104d8:0 2008-05-07 14:18:29
(srbmtsrv.cpp (86) err=2097168 sys=0) SBL-SRM-00016: Unable to
initialize the Database environment -- Unable to connect to DB (data
ops)
SrbLayerLog Error 1 0000797f482104d8:0 2008-05-07 14:18:29 Main Init fails
GenericLog GenericError 1 0000797f482104d8:0 2008-05-07 14:18:29
(smimtsrv.cpp (1187) err=2097168 sys=0) SBL-SRM-00016: Unable to
initialize the Database environment -- Unable to connect to DB (data
ops)
SmiLayerLog Error 1 0000797f482104d8:0 2008-05-07 14:18:29 Terminate process due to unrecoverable error: 2097168. (Main Thread)
Cause
After reviewing the logs provided, it was determined that possible
problem areas include (a) an incorrectly defined ODBC data source and/or
(b) problems with the the Listener configuration; although wider
Database connectivity problems cannot be discounted.
DBCLog DBCLogError 1 0000797f482104d8:0 2008-05-07 14:18:29 [DataDirect][ODBC Oracle driver][Oracle]ORA-12541: TNS:no listener
"ORA-12541: TNS:no listener" is usually logged when a connection
request can not be completed because the listener is not running (or is
simply unavailable) at the specified location - see Note:21475.1 on
Metalink
Corrective Action is described as follows:
Ensure that the supplied destination address matches one of the
addresses used by the listener - compare the TNSNAMES.ORA entry with the
appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go
by way of an Interchange). Start the listener on the remote machine.
Solution
Based on a review of the logs recently uploaded, the most probable cause
of the initialization problem is an incorrectly defined ODBC Data
Source or a misconfigured listerner
It would therefore be of some help it you could carry out the following
measures and provide proof on the results obtained at each stage (screen
shots, *.cfg file (3)), if further assistance is required.
(1) Verify the ODBC Data Source is correctly defined as shown in this
bookshelf reference: 'Siebel Installation Guide for Microsoft Windows
> Configuring Siebel Enterprise Server and Related Components >
Verifying the ODBC Data Source > Verifying the ODBC Data Source for
Oracle'
and/or
(2) Test connectivity to the database, using the ODBC DataSource tool
and also verify the hostname of the Server hosting the Database Listener
by comparing TNSNAMES.ORA entry with appropriate LISTENER.ORA file.
and/or
(3) Ensure that the ODBC Data Source name also matches the Server connect string specified in siebel.cfg on the Siebel Server
Applies to:
Siebel CRM - Version 8.1.1 [21112] to 8.2.2 SIA[22320] [Release V8]
Information in this document applies to any platform.
Symptoms
Gateway server was starting but siebel server was not coming up.
Further investigation showed, SRBroker and SCBroker components were not
coming up. Following errors got reported from SRBroker log file:
DBCLog
DBCLogError 1 000016d44e640f10:0 2011-09-05 13:51:15 [DataDirect][ODBC
Oracle driver][Oracle]ORA-01017: invalid username/password; logon denied
GenericLog
GenericError 1 000016d44e640f10:0 2011-09-05 13:51:15 (srbthrd.cpp
(4022) err=2097168 sys=0) SBL-SRM-00016: Unable to initialize the
Database environment -- Unable to connect to DB (data ops)
Changes
Newly configured Enterprise.
Cause
Here as following enteries shows, siebel service entry was created by
'sadmin' user whereas enterprise was configured with 'siebel' user.
Siebel Service Entry:
----------------------------------
C:\sba81\ses\siebsrvr\BIN\siebsvc -s siebsrvr -i
<enterprise>_<siebel_server> -a "-g localhost:2320 -e
<enterprise> -s <siebel_server> -l enu -u sadmin -ep
1ltEcMU/4eSB5A==" -t 120 -h C:\sba81\ses\siebsrvr
Siebns.dat entry on enterprise username:
----------------------------------------------------
[/enterprises/SBA_81/parameters/Username]
Persistence=full
Type=string
Value="siebel"
Length=12
Solution
1) Start gateway server.
2) Navigate to <siebsrvr/bin> and connect to 'srvrmgr'
3) Execute following command:
change ent param username=sadmin
Verify same by following command:
list ent param "username"
4) Restart gateway followed with siebel server and verify the results.
Applies to:
Siebel CRM - Version: 7.5.3.17 [16285] and later [Release: V7 and later ]
Information in this document applies to any platform.
Symptoms
We notice that the status of componets list below are "Unavailable":
a. Parallel Database Extract
b. Server Request Brokerh
c. Server Request Processor
d. Synchronization Manager
And I could not restart these componets, the log which I try restart componets are in the attachments.
Cause
From the logs found below,
ServerLog ProcessExit 1 2011-12-02 00:18:58 AsgnSrvr 48191 TERMINATED Process was terminated
ServerLog ProcessExit 1 2011-12-02 00:18:58 SynchMgr 48202 TERMINATED Process was terminated
ServerLog ProcessExit 1 2011-12-02 00:18:59 WfProcBatchMgr 48189 TERMINATED Process was terminated
ServerLog ProcessExit 1 2011-12-02 00:18:59 WfProcMgr 48190 TERMINATED Process was terminated
ServerLog ProcessCreate 1 2011-12-02 00:27:19 Created server process (OS pid = 3432) for Server Manager with task id 48210
ServerLog
ProcessExit 1 2011-12-02 00:27:43 ServerMgr 48210
SBL-ADM-01042 Process exited with error - Login failed for specified
username, password, and ODBC datasource combination
From SrBroker and SRProc log files,
GenericLog GenericError 1 2011-12-06 12:49:50 [DataDirect][ODBC Oracle driver][Oracle]ORA-0
GenericLog
GenericError 1 2011-12-06 12:49:50 (srpdb.cpp 39(900) err=3200016
sys=0) SBL-SRM-00016: Unable to initialize the Database environment --
Unable to connect to DB (data)
Checked ODBCSQL Connectivity and SQLPlus connection is fine.
Issue is caused by incorrect "password" Parameter at enterprise level.
Solution
The issue is resolved by resetting the parameter named 'Password' in
Server Administration - Enterprise parameter.Now The components are in
status of running .
References
NOTE:475610.1 - How Do You Test Connectivity Through ODBC Data Sources Created by Siebel?
Applies to:
Siebel System Software - Version 7.5.2.216 [16084] and later
z*OBSOLETE: Microsoft Windows 2000
Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.2.216 [16084] FIN
Database: Oracle 8.1.7.4
Database Server OS: IBM AIX 5L 5.1
This document was previously published as Siebel SR 38-1100316401.
***Checked for relevance on 25-01-2013***
Symptoms
SBL-SRM-00016
Hello ,
This morning when restarting our 3 production servers we receive systematically the following error log in SRBroker :
2021
2003-10-20 09:17:12 0000-00-00 00:00:00 +0200 00000000 001 001f 0001 09
SRBroker 6193 2840 2836 d:\sea752\siebsrvr\log\SRBroker_6193.log
7.5.2.216 [16084] ENU
ServerLog LstnObjInherit 3 2003-10-20 09:17:12 Inherited listening object for port 49172
ServerLog LstnObjPrivCreate 3 2003-10-20 09:17:13 Created port 49237 for Server Request Broker
GenericLog GenericError 1 2003-10-20 09:17:14 Unable to start SSA ID api.
GenericLog GenericError 1 2003-10-20
09:17:14 (srbthrd.cpp 44(3697) err=3200016 sys=0) SRM-00016: Unable
to initialize the Database environment -- Unable to start common api
GenericLog GenericError 1 2003-10-20
09:17:14 (srbmtsrv.cpp 39(71) err=3200016 sys=0) SRM-00016: Unable
to initialize the Database environment -- (null)
We have the same messages in SRProc
This means that CTI is unavailable to those users.
Cause
Oracle database rollback segment was offline
Solution
Message 1
This problem was due to Oracle Rollback Segments not being online.
Hence read access was fine, but when SRBroker tried to update S_SSA_ID
(i.e. get a Siebel ROW_ID) it failed. Unfortunately no Oracle errors
were reported. The SRBrker log showed:
GenericLog GenericError 1 2003-10-20 12:22:43 Unable to
start SSA ID api. GenericLog GenericError 1 2003-10-20
12:22:43 (srbthrd.cpp 44(3697) err=3200016 sys=0) SRM-00016: Unable
to initialize the Database environment -- Unable to start common api
GenericLog GenericError 1 2003-10-20 12:22:43 (srbmtsrv.cpp
39(71) err=3200016 sys=0) SRM-00016: Unable to initialize the Database
environment - (null)
After the database administrator put the rollback segment online, the update passed and the components went online correctly.
אין תגובות:
הוסף רשומת תגובה