Host Name / I.P Change for the AP node ( Apache / Form Node ) in 11i

Pre-Information

1. ILTEST Architecture (EBS: 11.5.10 ; O.S : AIX 5.3 )

Activity is to change the change the hostname from iltestap (192.168.20.137) to LGEILMESD02N (10.101.0.62).Before the activity stop all the services on Form and Concurrent Node, by running adstpall.sh
on 192.168.20.137 and 192.168.20.133. Also stop the database and listener.

UNIX Team Activity: Change the I.P / hostname of iltestap (192.168.20.137)

When the I.P./Hostname changed. Then up the database and listener only .

Login the Form Node (10.101.0.62) and follow the steps mentioned below.

Step 1 : Add the new host entry in the /etc/hosts file

$ cd /etc
$ vi hosts

Add the entry mentioned below

10.102.0.62 LGEILMESD02N.lgeil.com LGEILMESD02N

Step 2: Now change the host name in the .xml file .

$ cd $APPL_TOP/admin
$ cp ILTEST_iltestap.xml ILTEST_LGEILMESD02N.xml
$ vi ILTEST_LGEILMESD02N.xml

And here change the “iltestap” to “LGEILMESD02N” globally

Step 3: Run the autoconfig.

$ cd $AD_TOP/bin
$ adconfig.sh contextfile=$APPL_TOP/admin/ ILTEST_LGEILMESD02N.xml
Enter the password of apps : apps ( OR apps password of your apps )

Step 4: After the autoconfig completed successfully. Then, make custom.env file

Note: Autoconfig never makes the custom.env file. This file Need to be created manually.

$ cd $APPL_TOP
$ ls –ltr customILTEST_iltestap.env

-rw-r--r-- 1 oracle dba 126369792 Jul 4 17:36 customILTEST_iltestap.env
$ cp customILTEST_iltestap.env customILTEST_LGEILMESD02N.env

Step 5: Edit $APPL_TOP/ILTEST_LGEILMESD02N.env

$ cd $APPL_TOP
$ ls –ltr ILTEST_LGEILMESD02N.env

Vi this file (ILTEST_LGEILMESD02N.env) and edit

Find "FORMS60_PATH" and add lines

FORMS60_PATH=$FORMS60_PATH:$CUSTOM_TOP/resource:$CUSTOM_TOP/forms/US:$EAU_TOP/forms/US
export FORMS60_PATH

Below the following line

FORMS60_PATH="/u02/app/ilprodappl/au/11.5.0/resource:/u01/app/ilprodappl/au/11.5.0/resource/stub"export FORMS60_PATH

Step 6: Now, up the services on Form Node and Concurrent Node

Run adstrtal.sh on both Form and Concurrent Node and up the services. After try to open the EBS through the new url i.e.; http:.: .

New Setting :

Host File Entry
10.101.0.62 lgeilmesd02n lgeilmesd02n.lgeil.com

Proxy Settings
*lgeilmesd02n*;*lgeilmesd02n.lgeil.com*

Url
http://lgeilmesd02n.lgeil.com:8001
http://lgeilmesd02n.lgeil.com:8001/dev60cgi/f60cgi

Note: If this didn’t wok for you and you EBS shoes some error while opening the form launcher. Then stop the all on AP and DB node by running adstpall.sh (Don’t down the database & listener ) . After this change the iltestap to LGEILMESD02N in the .xml of Concurrent Node and then run the autoconfig firstly on Concurrent Node and after that on Form Node.

11g : Password can be make case sensitive

Scenario,

A database link ILMIS_FND was created on ILPROD database (oracle 9i) to access tables in ERPDBA database (11g R1) using the
connect string FNDDATA,

Link was created successfully but when
select count(*) from tab@ILMIS_FND ;
errored out with message -- Invalid username or Password.

1.tnsping FNDDATA (connect string ) found to be OK.
2.sqlplus fnd_data/****@FNDDATA too found to be ok.


Workaround
--------------------
In 11g version of Oracle Database password can be made case sensitive.
The following init parameter is to be set accordingly.

sec_case_sensitive_logon == (TRUE | FALSE)

On ERPDBA database (which is on 11g R1) the above parameter found tobe set TRUE

05:44:52 erpdb > show parameter sec_case_sensitive_logon

NAME TYPE VALUE
------------------------------------ ----------- ------------
sec_case_sensitive_logon boolean TRUE


The above parametre set to be FALSE then....

05:45:45 erpdb > alter system set sec_case_sensitive_logon=FALSE scope=BOTH;

System altered.

05:46:01 erpdb > show parameter sec_case_sensitive_logon

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
sec_case_sensitive_logon boolean FALSE


Now login was successfull using the db link ILMIS_FND.


one more Feature.......

while creating the password file using orapwd utility do the following
to make password case insensitive ..

orapwd file=orclpwd password=manager ignorecase=y

ORA-14071: invalid option for an index used to enforce a constraint

Hi ,

While enforcing the constraints for an index . "ORA-14071" error comes out as mentioned below ..

alter table esvc.ESVC_LGEIL_ITEM_AGEING
add constraint PK_ESVC_LGEIL_ITEM_AGEING primary key (INVENTORY_ITEM_ID, YYYYMM)
using index
tablespace ESVCD
pctfree 10
pctused 40
initrans 75
maxtrans 255
storage
(
initial 1M
next 1M
minextents 1
maxextents unlimited
pctincrease 0
);
ERROR at line 6:
ORA-14071: invalid option for an index used to enforce a constraint


This eror is because the user has used "PCTUSED" in the above command and only
options COMPRESS, NOCOMPRESS, PCTFREE, INITRANS,MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE,
UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL are allowed with index used to enforce a constraint .

Since the user was using the "pctused 40" . Thus this error comes out . To get out of this error remove the "pctused 40" .
It will work for you ....

Checking mainentance mode in 11i

Maintenance Mode is a new mode of operation introduced with Release 11.5.10, in which the

Oracle Applications system is made accessible only for patching activities not allowing the users

to login to any responsibility. This provides optimal performance for AutoPatch sessions, and

minimizes downtime needed.

1. Scheduling System Downtime

Administrators can schedule 'System Downtime' using Oracle Applications Manager (OAM):

Site Map --> Maintenance --> Manage Downtime Schedules

When the System has been scheduled for 'Downtime', Apache should be re-started on Restricted Mode

by using the Script (adaprstctl.sh). By doing this, users attempting to log on to Oracle Applications will

be automatically redirected to a System Downtime URL showing a message similar to the following one:

Scheduled Downtime Details
Start Time : 17:30:00 12/11/2004
Expected Up Time : 09:00:00 12/12/2004
For Updates : ecengineer84@gmail.com
The system is currently undergoing a scheduled maintenance.

This message can be customized with any text message. If No Downtime has been specified, and the users

try to access the Applications, the following message might also appear:

! Warning
The system has not been taken off maintenance mode completely.
Please contact your System Administrator.

2. Advantages

There are several practical points relating to the use of Maintenance Mode:

• You can toggle Maintenance Mode between Enabled and Disabled using the new Change Maintenance

Mode menu in AD Administration, or the equivalent function in Oracle Applications Manager.

• Although you can run AutoPatch with Maintenance Mode disabled, there will be a significant

degradation in performance.

• There is a separate logon page for Restricted Mode access while the system is in Maintenance Mode.

For more Information on Restricted Mode Access

3. Enabling and Disabling Maintenance Mode

Maintenance mode is Enabled or Disabled from adadmin.

When you Enable or Disable 'Maintenance Mode', adadmin will execute the script:

$AD_TOP/patch/115/sql/adsetmmd.sql sending the parameter 'ENABLE' or 'DISABLE' :

sqlplus /@adsetmmd.sql ENABLE | DISABLE

ENABLE - Enable Maintenance Mode .
DISABLE - Disable Maintenance Mode.

When adsetmmd.sql runs, it sets the Profile Option 'Applications Maintenance Mode'

(APPS_MAINTENANCE_MODE) to 'MAINT' to Enable 'Maintenance Mode' and to 'NORMAL' to Disable it.

4. Determining if Maintenance Mode is Running

A quick way to verify if the Environment is on Maintenance Mode or not, is by checking the value of this

Profile Option as follows:

sqlplus apps/apps

SQL> select fnd_profile.value('APPS_MAINTENANCE_MODE') from dual;

If the query returns 'MAINT', then Maintenance Mode has been Enabled and the Users will not be able to

Login. If the query returns 'NORMAL' then Maintenance Mode has been De-Activated and the Users will be

able to use the application.

Note: Maintenance Mode is only needed for AutoPatch Sessions. Other AD utilities do not require

Maintenance Mode to be enabled. Maintenance Mode must be 'Enabled' before running AutoPatch

and 'Disabled' after the patch application was completed.

When Maintenance Mode is disabled, you can still run Autopatch by using options=hotpatch on the

command line, if necessary. However, doing so can cause a significant degradation of performance.

5. Error Messages

Always remember to Disable Maintenance Mode after any Patch application. If Maintenance Mode is not

Disabled, the Application will not allow the users to use the system. Take note that Apache must be

re-started in normal mode after disabling 'Maintenance Mode' by using the Script adapcctl.sh (or adstrtal.sh)

As explained before, when 'Maintenance Mode' is enabled, a Downtime should be Scheduled from OAM and

Apache should be started on Restricted Mode by using the Script (adaprstctl.sh).

If a 'DownTime' is not Scheduled from OAM and Apache has not been re-started on Restricted Mode,

the Application will allow the users to Login, but it might experience unusual behaviors afterwards

depending on the Patch Level.

Here are some examples of the possible error messages:

• When clicking on a Responsibility from the PHP

There are no applications available for this responsibility. Please click on a different responsibility

link to display the list of available applications.

or

You are not authorized to access the function Applications Home Page. Please contact your System

Administrator.

• When trying to access to the Application via CGI directly (not supported):

There are no valid navigations for this responsibility
Cause: The menu compilation has failed.
Cause: There is not valid menu defined for this responsibility.
Cause: There are no navigable forms associated with this responsibility.
Action: Contact your system administrator. Ensure that a valid menu,
containing navigable forms, is defined for the responsibility.
Ensure that the menu is correctly compiled.

Note: In some cases, the behavior is slightly different. Instead of showing the above messages, the

Application might not show any Responsibilities listed for the user at all.

6. Step by Step Process

1. Schedule the 'System Downtime' from OAM

OAM: Site Map --> Maintenance --> Manage Downtime Schedules

At the moment of the downtime, do the following:

2. Shutdown Apache (on Normal Mode):

adapcctl.sh stop
or
adstpall.sh /

3. Enable 'Maintenance Mode' from adadmin

adadmin: Options 5, 1

4. Start Apache (on Restricted Mode)

adaprstctl.sh start

5. Apply the Patch with adpatch
6. Stop Apache (on Restricted Mode)

adaprstctl.sh stop

7. Disable 'Maintenance Mode' from adadmin

adadmin: Options 5, 2

8. Start Apache (on Normal Mode):

adapcctl.sh start
or
adstrtal.sh /