Assuming the RDBMS is up and running, first make sure the database client connects to the Siebel database instance from the command line interface. For example, if Oracle is the RDBMS, then:
- Check the $TNS_ADMIN/tnsnames.ora ($TNS_ADMIN\tnsnames.ora on Windows)
eg.,% cat $TNS_ADMIN/tnsnames.ora
siamst =
(DESCRIPTION =
(ADDRESS_LIST =
(SDU = 15360)
(TDU = 15360)
(ADDRESS = (PROTOCOL = TCP)(HOST = ben07)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = siamst)
)
) - Make sure you can ping the listener running on the database server
eg.,% tnsping siamst
TNS Ping Utility for Solaris: Version 11.1.0.6.0 - Production on 15-FEB-2008 11:06:02
Copyright (c) 1997, 2007, Oracle. All rights reserved.
Used parameter files:
/export/home/oracle/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (SDU = 15360) (TDU = 15360)
(ADDRESS = (PROTOCOL = TCP)(HOST = ben07)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = siamst)))
OK (10 msec) - Finally using the command line utility, sqlplus, connect to the Oracle database instance with the table owner for the Siebel database schema. The following example assumes 'oraperf' is the table owner for the Siebel database schema.
eg.,% sqlplus oraperf/oraperf@siamst
SQL*Plus: Release 11.1.0.6.0 - Production on Fri Feb 15 11:11:54 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL> set head off
SQL> select * from s_app_ver;
0-70 01-JAN-80 0-1 16-FEB-01 0-1
16 0 V8.0
13 29
43 Y 0
Database Schema for Siebel 2005 43r88_HEM17_06_SIA
1 0
88
71
HQ
SQL> quit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options - If the above step fails to connect to the Oracle database instance, check the connect string, table owner etc., fix them if needed and repeat the above step.
Usually the above steps are good enough to test the database connectivity. However it is recommended to test the database connectivity using Siebel's odbcsql utility as well, just to make sure that there won't be any trouble for the Siebel servers in communicating with the database server.
- Set the required environment variables
eg.,% source $SIEBEL_HOME/siebenv.sh (csh)
% . $SIEBEL_HOME/siebenv.sh (ksh) - Bring up the odbcsql command line interface (CLI), connect to the Oracle database instance using the table owner login/password
eg.,% odbcsql
ODBCSQL - ODBC SQL Interface program
Copyright (c) 2001 Siebel Systems, Inc. All rights reserved.
Type help for usage information.
ODBC> set source=siebsrvr_siebel
ODBC> login oraperf/oraperf
SQL DBMS: Oracle version 10.02.0000 Oracle 10.2.0.1.0
ODBC driver: SEor821.so version 05.10.0017 (B0011, U0004)
(login time: 0.73s)
ODBC> quit
Outstanding transaction committed.
Alternatively it can be tested in a single line as shown below:% odbcsql /s siebsrvr_siebel /u oraperf /p oraperf
ODBCSQL - ODBC SQL Interface program
Copyright (c) 2001 Siebel Systems, Inc. All rights reserved.
Type help for usage information.
Logging into "siebsrvr_siebel" as "oraperf" ...
SQL DBMS: Oracle version 10.02.0000 Oracle 10.2.0.1.0
ODBC driver: SEor821.so version 05.10.0017 (B0011, U0004)
(login time: 0.67s)
ODBC> quit
Outstanding transaction committed.
If it fails to connect, double check the connect string specified during the installation of Siebel server.
____________________________
Technorati Tags:
Oracle | 
Siebel | 
CRM | 
Database
0 comments:
Post a Comment