Seven Siebel Local XE Database Setup Challenges and Solutions

Siebel IP 15.5 introduced the Oracle Local XE Database, bringing with it a number challenges. Boxfusion Siebel Consultant, Amardeep Parmar, explains how to avoid these challenges for a smoother Siebel installation.

Introduction #

Siebel Innovation Pack 15.5 introduced the Oracle Database XE (Local XE) for developers to use in place of the old SQL Anywhere database, and this has formed the standard for IP16 and releases beyond. However, there have been a few inevitable teething issues, with the potential to cause delays to development for Siebel implementations.

While working with a number of clients around the world, we’ve observed first-hand some of the struggles resulting from what should be a minor transition. Here are some top tips to solve a variety of challenges you may find when installing Local XE and how to fix them, so that you can quickly move on to the key task of delivering transformative changes for your business with the latest Innovation Pack.

(Please note: this blog post is aimed at Siebel developers and therefore assumes a basic level of technical knowledge. This blog will not cover the detailed installation steps or extraction process, but you can find this information in the Oracle Bookshelf library).

1. Incorrect Oracle Client Version #

To begin with, it is worth taking into account that IP15.5 requires an Oracle 11g client, whereas IP16 requires an Oracle 12c client (by Oracle recommendation). It is simple to miss the recommendation and be left bewildered, thus it is important to check the versions at the start of the installation process.

2. Error Message: ORA-12541: TNS: No listener #

This will often occur when trying to connect to the Local XE database and, in most cases, this is caused by the XE Services not running. To resolve this issue, find 'OracleServiceXE' and 'OracleXETNSListenerXE' in Local Services and ensure they are running. If the Services are not visible or don’t start, you may need to uninstall and re-install from scratch.

3. Error Message: ORACLE ORA-12557: TNS: Protocol adapter not loadable #

This is another error that can prevent the establishment of a connection to the Local XE. This error can occur when users have installed previous instances of Oracle products that have set the ‘ORACLE_HOME’ system variable. If the variable is removed, the Local XE connection will work. If other Oracle products are still in use that require ‘ORACLE_HOME’ to be set, then the XE install path must be added to the comma-separated list of paths already present in the value of that variable.

4. Error Message: ORA-12170: TNS: Connect timeout occurred #

This is another error that prevents a connection to the Local XE. Large projects are especially at risk of this issue arising because developers may share their tnsnames.ora files with each other. The XE service runs on each individual computer and will therefore use specific IPs and hostnames that other developers won't be able to access. Ensure that your TNS entry refers to your computer as its host; either by using ‘LOCALHOST’, ‘127.0.01’ or the computer name.

5. Error Message: Data import failed. Please check <logfile> for details #

This issue occurs during the data import from the server to the XE database itself. It will occur when there is a mismatch between the database schema and the repository definitions. A good example would be when columns are deactivated in Tools but not removed from the database itself. The resolution of this issue is through correcting the problem columns and ensuring the integrity of the database schema.

6. Local XE Missing from CFG #

For long-time users of Siebel, it may be easy to think that the local data source in the tools and client CFG would be set up to point to Local XE by default. However, the local data source is set up to handle the old SQL Anywhere databases. The local XE data source should be added into the CFG, so that the server data source is using the correct connect string.

7. ODBC Registry Settings Not Set #

These four registry settings for Oracle ODBCs can be the issue in many administration tasks. Ensure that you add the four parameters below to the ODBC registry entry (users must have administrator-level access to add the parameters). The effects take place instantly, so there is no need to waste valuable development time restarting the computer.

• ColumnsAsChar = 1
• ColumnSizeAsCharacter = 1
• PacketSize = 0
• EnableScrollableCursors = 0

Conclusion #

The setup process for Oracle Local XE is new to many and there are several stumbling blocks that can really stunt the smooth transition between the systems, using up valuable time trying to trace back to the source of the issue.

However, bear in mind these common errors with the simple solutions mentioned above, and you’ll be on your way to a hassle-free installation.