Tuesday, October 27, 2009

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.


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

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:

Default Value = %s_at%/my/11.5.0
Title = My Product top
Description = This is my product 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.

Wednesday, October 21, 2009

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

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

I found a good one by using NOT EXISTS clause

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

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

Tuesday, October 6, 2009

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".

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.