|
Siebel Installation Guide for UNIX > Verifying and Troubleshooting Your Installation >
Troubleshooting Installation and Configuration for Siebel Enterprise Server
This topic presents troubleshooting information related to installation and configuration of Siebel Enterprise Server components. Related Topics
Starting the Siebel Gateway Name Server
Configuring the Siebel Gateway Name Server for Automatic Start
Configuring the Siebel Server for Automatic Start
Verifying Installation for the Siebel Enterprise Server
Verifying That the Siebel Gateway Name Server Has Started
Troubleshooting Installation and Configuration for the Siebel Gateway Name Server
This topic describes potential errors that can result from a faulty installation or configuration of Siebel Gateway Name Server. Such problems can have any of several causes, the most common of which are listed in Table 13. NOTE: If you cannot start the Siebel Gateway Name Server, then you will not be able to configure a Siebel Enterprise or configure and start a Siebel Server.
Table 13. Troubleshooting Siebel Gateway Name Server Installation and Configuration
|
|
|
The Siebel Gateway Name Server does not start. |
You might not have privileges as the Siebel service owner. |
Review the instructions in Creating the Siebel Service Owner Account. |
The Siebel Gateway Name Server does not start. |
Failure to start the Siebel Gateway Name Server can be caused by a number of problems including, but not limited to:
- Incorrectly set LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris) environment variable
- Incorrect permissions set on shared libraries
- Missing shared libraries
|
Use the ldd command to show missing libraries. Make sure that $SIEBEL_HOME/lib is included and set before LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris). If there are library conflicts, then set $SIEBEL_HOME/lib as the first element of the shared library path environment variable. Check the LIBPATH, SHLIB_PATH, or LD_LIBRARY_PATH settings in all applicable files, including cfgenv.csh (for C shell) or cfgenv.sh (for Bourne or Korn shell), and siebenv.csh or siebenv.sh. Make sure that siebenv.csh and siebenv.sh were correctly generated. |
Troubleshooting Installation and Configuration for the Siebel Server
This topic describes potential errors that can result from a faulty installation or configuration of Siebel Server. Such problems can have any of several causes, the most common of which are listed in Table 14.
Table 14. Troubleshooting Siebel Server Installation and Configuration
|
|
|
The Siebel Server cannot be installed. |
Insufficient user privileges |
For information about setting up appropriate administrative user privileges to install, see Setting Permissions and Ownership and Creating the Siebel Service Owner Account. |
Trying to install or configure the Siebel Server out of sequence |
For the required installation and configuration sequence, see Overview of Installing Siebel Business Applications. |
Failure to install required hardware or software |
Installation errors related to software requirements are logged in the Siebel Enterprise Server installer log file. For requirements, see the Certifications tab on My Oracle Support. |
Environment variables not set properly |
For more information about environment variables, see Managing Environment Variables. |
Faulty network connection |
Sometimes a faulty network connection can result in the system administrator being unable to install to the $SIEBEL_HOME directory in which he or she has write privileges. Verify that your network connection is stable. |
The Siebel Server does not start. |
Failure to start the Siebel Server can be caused by a number of problems including, but not limited to:
- Incorrectly set LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris) environment variable
- Incorrect permissions set on shared libraries
- Missing shared libraries
|
Use the ldd command to show missing libraries. Make sure that $SIEBEL_HOME/lib is included and set before LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris). If there are library conflicts, then set $SIEBEL_HOME/lib as the first element of the shared library path environment variable. Check the LIBPATH, SHLIB_PATH, or LD_LIBRARY_PATH settings in all applicable files, including cfgenv.csh (for C shell) or cfgenv.sh (for Bourne or Korn shell), siebenv.csh or siebenv.sh, and dbenv.csh or dbenv.sh. Make sure that siebenv.csh, siebenv.sh, dbenv.csh, and dbenv.sh were correctly generated. |
Application Object Manager component does not start. |
Heavily used servers running more than 50 instances of Object Manager components can experience a condition where some of the Object Managers do not start correctly and log the following error message: Got error 1801210 when dequeuing a connection request (62)
|
Change TCP stack parameters. For more information about sizing Application Object Manager components, see Siebel Deployment Planning Guide, Siebel Performance Tuning Guide, and other relevant documents on Oracle Technology Network or My Oracle Support. |
The Siebel Server does not start after configuration. |
Siebel Gateway Name Server not started |
Verify that the Siebel Gateway Name Server was started. Start it if it was stopped. |
Invalid input values during configuration |
Verify that the input values during configuration were valid. |
Insufficient system privileges |
Verify that you have sufficient system privileges to start the service. For more information, see Creating the Siebel Service Owner Account. |
Troubleshooting the ODBC Data Source Connection
This topic describes troubleshooting steps for your ODBC data source connection. NOTE: If your database is IBM DB2 for z/OS, then see Implementing Siebel Business Applications on DB2 for z/OS.
Troubleshooting Connection Problems on Oracle Database
Complete the following instructions to troubleshoot Oracle Database connection problems on AIX, HP-UX, Linux, or Oracle Solaris. See also Configuring Siebel Server Connectivity to the Siebel Database. If you are unable to verify if your ODBC connection to your Oracle Database is working, then verify that the value of the environment variable TNS_ADMIN is the exact path of tnsnames.ora. To troubleshoot a failed ODBC connection for Oracle Database on AIX, HP-UX, Linux, or Oracle Solaris
- Verify that the Oracle connect string entered as part of Siebel Enterprise configuration is valid.
- If the connect string entered is correct, then check the ODBCINI environment variable to verify that it was set by entering the following command:
echo ${ODBCINI}
The following response appears:
$SIEBEL_ROOT/sys/.odbc.ini
- If the ODBCINI environment variable was correctly set, then verify that the .odbc.ini file is valid by reviewing it for the presence of the following parameters:
[EnterpriseName_DSN]
ServerName=ora11g
Driver=$SIEBEL_ROOT/lib/SEor825.so
ColumnsAsChar=1
ColumnSizeAsCharacter=1
CAUTION: The ColumnsAsChar and ColumnSizeAsCharacter parameter settings are required in order for the ODBC driver to behave correctly.
- If the .odbc.ini file is valid, then verify that the library path includes the path for the ODBC driver on your operating system by entering the following command:
AIX. Use echo ${LIBPATH}.
HP-UX. Use echo ${SHLIB_PATH}.
Linux and Oracle Solaris. Use echo ${LD_LIBRARY_PATH}.
The following response appears:
$SIEBEL_HOME/lib
NOTE: Siebel Business Applications support the Oracle 32-bit client. Therefore, if you have installed the Oracle 64-bit client on your Siebel Server, then you must include $ORACLE_HOME/lib32 in your definition for the LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris) environment variable. (If you require $ORACLE_HOME/lib for non-Siebel applications, then make sure that $ORACLE_HOME/lib32 is placed in front of $ORACLE_HOME/lib.)
- If the response illustrated for your operating system in Step 4 was correct and you are verifying a Unicode installation, then make sure that the following environment variable is set according to the recommendations from your database platform vendor.
SIEBEL_UNIXUNICODE_DB=ORACLE
This variable is also set in the siebenv.csh (for C shell) and siebenv.sh (for Bourne or Korn shell) scripts.
|
