APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN

Concurrent programs errors out with APP-FND-00500 in 11i/R12

 

Symptom:

 

APP-FND-00500:  AFPPRN received a return code of failure from routine FDUPRN

Cannot read file <full path>/<filename>.out

Application Object Library encountered an error while reading the file

<filename>.out does not exist on the file system

 

Cause:

 

If a report does not produce an output file but the concurrent program definition is set up so that it tries to print anything by default, then an FND-00500 error will occur.

 

Solution: 

 

This specific error can be ignored, but the more prudent solution is to modify the concurrent program definition in order that it does not try to print anything by default.

 

1. Log into Applications with the System Administrator responsibility.

 

2. Navigate to Concurrent/program/define and query up the concurrent  program.

 

3. In the lower right corner where the output options are listed, clear the  check box next to the word “print”.  Leave the “save” option selected to avoid an APP-00088 when running the program because it was unable to delete the output file which was never created.

 

4. From the menu bar of this same form, select “Action/Save and Proceed”.

Ref # 156570.1 & 101064.1

Sun JRE 1.6.0_27 is now Certified with Oracle E-Business Suite 11i/R12

As of today, We can also apply Sun  Java Runtime Environment 1.6.0_27 (a.k.a. JRE 6u27-b07).  JRE 1.6.0_27 is certified with E-Business Suite Release 11i and 12.

Ref # Upgrading Sun JRE (Native Plug-in) with Oracle Applications 11i for Windows Clients (Metalink Note 290807.1)

http://blogs.oracle.com/stevenChan/entry/sun_jre_1_6_02

Oracle Virtual Box 4.1.2 software Now Available on virtualbox.org

On Aug 15, 2011, Oracle 4.1.2 was released and the installation files are in http://www.virtualbox.org/wiki/Downloads. The releases are availabe for x86 and x86_64 platforms, it is free to download, install and use.

List of the Workload Repository Views (AWR)

Please find below the list of  the workload repository views with their description,

V$ACTIVE_SESSION_HISTORY – Displays the active session history (ASH) sampled every second.

V$METRIC – Displays metric information.

V$METRICNAME – Displays the metrics associated with each metric group.

V$METRIC_HISTORY – Displays historical metrics.

V$METRICGROUP – Displays all metrics groups.

DBA_HIST_ACTIVE_SESS_HISTORY – Displays the history contents of the active session history.

DBA_HIST_BASELINE – Displays baseline information.

DBA_HIST_DATABASE_INSTANCE – Displays database environment information.

DBA_HIST_SNAPSHOT – Displays snapshot information.

DBA_HIST_SQL_PLAN – Displays SQL execution plans.

DBA_HIST_WR_CONTROL – Displays AWR settings.

 

Oracle Linux 5.7 DVDs Now Available on e-delivery

On Aug 6, 2011, Oracle 5.7 was released and the installation DVD images are on edelivery.oracle.com/linux. Both the releases are availabe for x86 and x86_64 platforms, it is free to download, install and use for education/demo purposes.
 
More at : http://blogs.oracle.com/linux/entry/oracle_linux_5_update_7

Internet Explorer 9 is now Certified with Oracle E-Business Suite (11i/R12)

Microsoft Internet Explorer 9 is now certified as a desktop client browser for Oracle E-Business Suite Release 11i and 12.  The certified desktop operating systems are:

• Windows Vista Service Pack 1 (SP1) or Service Pack 2 (SP2)
• Windows 7
• Windows 7 Service Pack 1 (32-bit or 64-bit)

EBS 12.1 Prerequisites

• EBS 12.1.1 or higher
• Java Plug-in JRE 1.6.0_03 or higher

Steps to get the actual execution plan for a SQL statement between two AWR snapshots?

The following are the steps to get the actual explain plan statement of a query ran between two snapshots when the cursor is not available in memory.

1) Query  the SQL_ID from V$SQL

2) Run the following script: $ORACLE_HOME/rdbms/admin/awrsqrpt.sql

3) Specify the begin/end snapshots and the sql_id

4) Review the output for the actual explain plan of the sql

 

Oracle E Business Suite Environment Naming Convention (11i/R12)

Oracle E-Business Suite (11i/R12) is typically installed under two operating system users: oracle and applmgr. The oracle user owns the Oracle technology stack and database, and is a member of the dba group. The applmgr owns the Oracle E-Business Suite technology stack, and is a member of the oaa group. An implementer account is created for the Oracle Implementer (OI)and the interface account is created for file transfers.

The naming conventions for Oracle E-Business Suite are as follows:

Customer short code: This four-character code uniquely identifies the customer’s system. It is combined with the first letter of the environment type to form the database system identifier (SID), mount points, and user names.

Database SID: This is usually made by concatenating the first letter of the environment type, the customer short code, and the letter i. However, when the customer has additional instances, the SID is created with the first three digits of the short code plus the instance number.

Environment type: This can be the Test, Development, or additional non-production environments. Each environment uses different port numbers.

Mount point: The mount point for the applications environment is the same as the database SID (The mount point is always entered in lowercase)

User names: The names are defined as follows:

– The oracle user name is made by concatenating or with the database SID.
– The applmgr user name is made by concatenating ap with the database SID.
– The interface user name is made by concatenating inf with the database SID.
– The BOL-SETUP user name is assigned the Applications Administrator responsibility for Oracle E-Business Suite for implementation use. Prior to go-live, the application administrator responsibility should be assigned to a named application user. The user BOL-SETUP will be end dated at go-live.
 
Example:

Enviroment PROD –
Oracle SID : pabcdi
oracle user: orpabcdi
applmgr user: appabcdi
interface user: infpabcdi
 
Enviroment DEV –
Oracle SID : dabcdi
oracle user: ordabcdi
applmgr user: apdabcdi
interface user: infdabcdi
 
Enviroment TEST –
Oracle SID : tabcdi
oracle user: ortabcdi
applmgr user: aptabcdi
interface user: inftabcdi

Viewing contents of master table using keep_master parameter in impdp

We can use a parameter called keep_master in the impdp command to read the master table created for the job. This table will be useful in finding some useful information apart from the generated sql,

SQL> set line 200;
SQL> set pagesize 9999;
SQL> col OWNER form a 40;
SQL> col owner form a40;
SQL> col DIRECTORY_NAME format a30;
SQL> col DIRECTORY_PATH format a100;
SQL> /

OWNER                                    DIRECTORY_NAME                 DIRECTORY_PATH
—————————————- —————————— ————————————————————————————
SYS                                      DATA_PUMP_DIR                  /oracle/home/product/10.2.0/Db_1/admin/OFSASG/dpdump/
SYS                                      ORACLE_OCM_CONFIG_DIR          /oracle/home/product/10.2.0/Db_1/ccr/state

SQL>

Database Rolling Upgrade Shell Script from Oracle called physru

The script can be downloaded from MOS note # 949322.1 as the script could get updated regularly

The Bourne shell script, called physru, performs a physical standby rolling upgrade for Oracle RDBMS versions 11gR1 and higher. A physical standby rolling upgrade typically involves numerous SQL operations and validations. The physru script greatly reduces the number of steps, leaving the following remaining steps for the user:

1. Calling DBUA or catupgrd.sql to upgrade the standby database.

2. Starting the upgraded standby database in the new Oracle home.

3. Starting the former primary database in the new Oracle home.

4. Starting and stopping RAC instances.

5. Disabling and enabling of RAC.