My Oracle Support Banner

Would it be possible to change LOCAL_XE / Oracle XE database listener to use localhost instead of hostame? (Doc ID 2498866.1)

Last updated on JANUARY 12, 2020

Applies to:

Siebel CRM - Version 18.10 and later
Information in this document applies to any platform.

Symptoms

Siebel Installation - on version: 18.10

ACTUAL BEHAVIOR
---------------
Siebel Client - Local_XE with localhost

After installing Siebel Mobile Web Client along with LOCAL_XE Database, connection via ODBC DSN is working fine.

But after changing the HOST to localhost in tnsnames.ora & listener.ora instead of the actual hostname in both the oraclexe location and in Oracle Client, the lsnrctl stat is no longer showing the XE service:

*) with hostname (default setup):

Services Summary...
Service "CLRExtProc" has 1 instance(s).
  Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
  Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "XEXDB" has 1 instance(s).
  Instance "xe", status READY, has 1 handler(s) for this service...
Service "xe" has 1 instance(s).
  Instance "xe", status READY, has 1 handler(s) for this service...
The command completed successfully


*) with localhost:


Services Summary...
Service "CLRExtProc" has 1 instance(s).
  Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
  Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully

And also connecting to LOCAL_XE is no longer working.


Is it possible to use localhost rather than using hostname for LOCAL_XE?
 

EXPECTED BEHAVIOR
-----------------------
Expectation would be to still be able to connect running fine after making the changes described.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Setup Siebel Mobile Web Client and Oracle XE;
2. Test connectivity from ODBC and ensure that works fine;
3. Make the described changes (replace localhost instead of default hostname) in tnsnames.ora & listener.ora files under both the oraclexe location and in Oracle Client;
4. Check the Listener status.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot make such changes to the default installed files and settings.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.