How to change the Oracle EBusiness Suite url

How to change the Oracle EBusiness Suite url 

Normally while you install oracle R12 it takes the hostname as url name. So, you can access the oracle apps instance as http://:/OA_HTML/AppsLogin

An example is http://machinename.domainname:8000/OA_HTML/AppsLogin

The following article will explain you how you can change the url to other name instead of hostname of the machine.

Here I am assuming the hostname of the server is HOSTNAME and currently the instance is accesible  from http://HOSTNAME.domainname:8000/OA_HTML/AppsLogin 
and we'll change the url to 
http://URLNAME.domainname:8000/OA_HTML/AppsLogin 

• Set the apps environment file. 
• Check the CONTEXT_FILE name
• Take a backup of the context file

Now change the following values in context file accordingly .


1. s_webentryhost

This is the name of the host that receives the first HTTP request from the desktop client. Previously it was set as hostname of the server [HOSTNAME]. Change this value to URLNAME.



2. s_webentrydomain

This is domain name of the host that receives the first HTTP request from the desktop client
Change the domain name if required.


3. s_login_page

This is the URL used to access the Applications logon page.
Change it from the old value http://HOSTNAME.domainname:8000/OA_HTML/AppsLogin  to new value http://URLNAME.domainname:8000/OA_HTML/AppsLogin .



4. s_external_url

This is URL that third party tools use to connect to the E-Business Suite System. 
old value = http://HOSTNAME.domainname:8000/
new value = http://URLNAME.domainname:8000/



After changing the values, do the following.

• Run the AutoConfig utility on all the application tier Servers
• Restart application server processes
• Test sign on from the web entry point

Resize Operation Completed For File#

Resize Operation Completed For File# (Doc ID 1982901.1)
---------------------------------------------------------------------

APPLIES TO:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.
***Checked for relevance on 13-Jun-2016***

SYMPTOMS

File Extension Messages are seen in alert log.There was no explicit file resize DDL as well.

Resize operation completed for file# 45, old size 26M, new size 28M
Resize operation completed for file# 45, old size 28M, new size 30M
Resize operation completed for file# 45, old size 30M, new size 32M
Resize operation completed for file# 36, old size 24M, new size 26M

In a busy system with lots of DML (insert/update/delete),the alert log could be flooded with many such file extension messages.

CAUSE

These file extension messages were result of diagnostic enhancement through unpublished to record automatic datafile resize operations in the alert log with a message of the form:

 "File NN has auto extended from x bytes to y bytes"

This can be useful when diagnosing problems which may be impacted by a file resize. 

SOLUTION

In busy systems, the alert log could be completely flooded with file extension messages. A new Hidden parameter parameter "_disable_file_resize_logging" has been introduced through bug 18603375 to stop these messages getting logged into alert log.

(Unpublished) Bug 18603375 - EXCESSIVE FILE EXTENSION MESSAGE IN ALERT LOG 

Set the below parameter along with the fix.

SQL> alter system set "_disable_file_resize_logging"=TRUE ; (Its default value is FALSE)

The bug fix 18603375 is included in 12.1.0.2 onwards.