How to relink all binaries after a OS Upgrade to ensure that everything is working as expected on a Release 11i or a Release 12 Installation on Unix ?

To get everything relinked and to ensure that the adadmin Utility was relinked before it is used, follow these steps :

Release 11i (Autoconfig enabled) :

Technology Stack Binaries inclusive Database :

Source the RDBMS ORACLE_HOME Environment
Execute the script $ORACLE_HOME/appsutil/install/adlnkoh.sh
Source the iAS ORACLE_HOME Envrionment
Execute the script $ORACLE_HOME/bin/adlnkiAS.sh
Source the APPS Environment
Execute the script $ORACLE_HOME/bin/adlnk806.sh

Oracle E-Business-Suite Binaries :
1. Source the APPS Environment

2. Execute following command :
adrelink.sh force=y "ad adadmin"
If you are using the command
adrelink.sh force=y "ad all"you are relinking all binaries under the $AD_TOP/bin - otherwise the AD Utilities are relinked via the adadmin Utility.

3. Execute adadmin
select --> '2. Maintain Applications Files menu'
select --> '1. Relink Applications programs'
--> select all modules to relink

Before starting the Instance, please open a new shell and source the Environment.
Release 12 :

Technology Stack Binaries inclusive Database :

Source the RDBMS ORACLE_HOME Environment
Execute the script $ORACLE_HOME/appsutil/clone/adlnkoh.sh
Source the APPS Envrionment
Execute the script $IAS_ORACLE_HOME/appsutil/clone/adlnkweboh.sh
Source the APPS Environment
Execute the script $ORACLE_HOME/appsutil/clone/adlnktools.sh

Oracle E-Business-Suite Binaries :

1. Source the APPS Environment

2. Execute following command
adrelink.sh force=y "ad adadmin"

If you are using the command
adrelink.sh force=y "ad all"

you are relinking all binaries under the $AD_TOP/bin - otherwise the AD Utilities are relinked via the adadmin Utility.

3. Execute adadmin
select --> '2. Maintain Applications Files menu'
select --> '1. Relink Applications programs'
--> select all modules to relink

Before starting the Instance, please open a new shell and source the Environment.

Requests Stuck with Inactive No Manager - Routine AFPESA Cannot Construct the Name of an Executable File

All the Concurrent Requests are showing up with Phase Inactive and Status No Manager.
The Standard Manager is not able to process any request because each manager process dies immediately after starting up. The log file of the manager process shows the following error:

List of errors encountered:
.............................................................................
_ 1 _Routine AFPESA cannot construct the name of an executable file foryour concurrent request 2181143.

Check that the file name components are correct and valid on yoursystem. Check that the environment for the person who started the conc
.............................................................................

The problem typically occurs on a cloned environment that has been created.

Cause

The problem is due to an incorrect environment setup. The custom PROD_TOP is not defined in the environment files.
Solution

Any custom product_top needs to be defined correctly in the Context File. The following extract describes how to add a custom product_top to the Context File by using Oracle Applications Manager:

Creating a customer owned AutoConfig template file
You can create an AutoConfig template file of your own. This will enable you to develop custom applications that AutoConfig configures and maintains.
Perform the following tasks in the order listed:

Define a product_top
Use the Oracle Applications Manager Context Editor to add your custom product_top to the context file. Refer to the Help pages available on your Oracle Applications Manager site. The relevant information for adding custom context variables is located in the "System Configuration" -> "AutoConfig" -> "Custom Parameters" section. Choose the variable type "PRODUCT_TOP" when adding the product_top variable.

For example, define "MY_TOP" as your product_top as follows:

OA_VAR = MY_TOP
Default Value = %s_at%/my/11.5.0
Title = My Product top
Description = This is my product top
OA_TYPE = PROD_TOP

Note: You must have Oracle Applications Manager (OAM) H or higher installed to manage custom variables. Refer to Oracle Applications Manager 11i Availability for instructions on installing OAM.
AutoConfig needs be run after adding the custom product_top to the Context File.
Alternatively, a product_top can added manually to the environment file instead of defining it in the Context File.

RMAN does not display the output

If you specify the LOG option at the command line, then RMAN displays command input but does not display the RMAN output.
The easiest way to send RMAN output both to a log file and to standard output is to use the UNIX tee command or its equivalent on another operating system.
For example:
% rman tee rman.log
RMAN>

SQL> select * from dual where 1=0;
no rows selected
SQL>

I found a good one by using NOT EXISTS clause

SQL> select * from dual where 1=0
UNION
select 'no data found' from dual where not exists (select * from dual where 1=0);
DUMMY
no data found
1 row selected.
SQL>

In this way, both input and output are visible within the RMAN command-line interface.

Quick Pay Fails With Error Assertion failure detected at location py3vntsetup:1a

The Quick Pay process errors with 'Assertion failure detected at location py3vntsetup:1a'. Additional errors in the log file show "Library error: libqutil.so: cannot open shared object file: No such file or directory".

cause:
The parameter LD_LIBRARY_PATH is not setup correctly.

-- To implement the solution, please execute the following steps::

1.Modify the file $APPL_TOP/admin/adovars.env to include the complete pathof $PAY_TOP/vendor/quantum/lib as the first entry for LD_LIBRARY_PATH.If PY_LIB_PATH is set in the adovars.env file, Payroll application will no longer use LD_LIBRARY_PATH if PY_LIB_PATH is defined in the instance. Therefore, ensure that the PY_LIB_PATH path should always have the LD_LIBRARY_PATH included in it.

2. Bounce the concurrent managers.

3. Test Quick Pay.

Configuring smtp in Linux

Configuring smtp in Linux

1. Ask mail administrator to add the linux server from which we need to send mail to mail server

2. comment out following line in /etc/mail/sendmail.mc

dnl This changes sendmail to only listen on the loopback device 127.0.0.1
dnl and not on any other network devices. Comment this out if you want
dnl to accept email over the network.

dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')

3. Compile the changes we made,

m4 /etc/mail/sendmail.mc > /etc/mail/sendmail.cf

4. Start the sendmail service

service sendmail start

5. Test the mail using the following,

echo "Hello World" mail -s "Test from NG Monitor" jayakumar@newgenusa.com

6. The mail status can be checked through the following command
mail queue

Concurrent Requests Remain in Pending/Standby Status

Concurrent Requests Remain in Pending/Standby Status.

fact: Oracle Application Object Library
symptom: Concurrent requests remain in pending standby status
symptom: Conflict resolution manager will not manage concurrent requests
symptom: Conflict resolution manager hangs
symptom: FND_CONFLICTS_DOMAIN table locked

cause:
A concurrent request errored out just prior to first lockup and a user terminated another job prior to the second lockup. In the first case, the FNDLIBR did not exit properly and had to be killed. In the second case, the terminated concurrent request did not exit properly and had to be killed (but its status was set to "Completed Terminated" by the standard manager which processed it).

Fix:
1. Kill the problem requests at the OS level with kill -9 command.
2. Restart the concurrent manager

How to rejoin new ORACLE_HOME with an installed EBS Instance?

If the database is currently running, do the following :

Remove ORACLE_HOME info from NetServices Toplogy model :

1. Set env from old $ORACLE_HOME
2. Start Listener and database
3. cd $ORACLE_HOME/appsutil/bin
Execute following command :
perl adgentns.pl contextfile=old $ORACLE_HOME/appsutil/_.xml -removesystem
4. Shutdown Database and listener

Update new ORACLE_HOME :
5. Copy OLD $ORACLE_HOME/appsutil directory to new $ORACLE_HOME
6. Copy OLD $TNS_ADMIN directory to new $ORACLE_HOME
7. Edit new $TNS_ADMIN/*.ora files and update ORACLE_HOME path in following files :
tnsnames.ora
sqlnet.ora
listener.ora
8. Copy OLD $ORACLE_HOME/*.env to new $ORACLE_HOME
9. Edit /*.env files and update paths within10. Run /_.env
11. Rename any existing /dbs/initSID.ora or spfile
12. cd $ORACLE_HOME/appsutil/bin

Build a new context file via following command :

./adclonectx.pl contextfile=/appsutil/_.xml validate=no

Enter the values to reflect new ORACLE_HOME

13. Run AutoConfig via following commands :

a) cd $ORACLE_HOME/appsutil/bin

b) ./adconfig.sh contextfile=/appsutil/SID_hostname.xml

NOTE: It will fail because database is down, but we want it to create configuration files

15. Start listener
16. Start Database