APP-PO-14142: get_po_parameters-10: ORA-01422 When Open Purchasing Form

Problem

Following Error Occur when open a purchasing form

Solution

1. Connect apps user and run below query.

select object_name,policy_name, package,function,enable
from sys.all_policies
where object_name = upper('PO_DOCUMENT_TYPES_B')
union
select object_name,policy_name, package,function,enable
from sys.all_policies
where object_name = upper('PO_DOCUMENT_TYPES_TL')
union
select object_name,policy_name, package,function,enable
from sys.all_policies
where object_name = upper('PO_SYSTEM_PARAMETERS')
union
select object_name,policy_name, package,function,enable
from sys.all_policies
where object_name = upper('FINANCIALS_SYSTEM_PARAMETERS');

If query does not return above four policies, then add those

2. Run below script via apps user

SQL>revoke EXEMPT ACCESS POLICY from APPS;

3. Verify the issue by running following query.

select count(*) from po_document_types;

If above query return 0 rows, then issue will be resolved

Reference : 
Choosing Approval Assignments Form From Menu - Nothing Happens - Form Does Not Open (Doc ID 1063223.1)

R12 Error : ORA-1691: unable to extend lobsegment

Problem

Following error occurred while attached and save the attachment on oracle forms in R12.
ORA-1691: unable to extend lobsegment APPLSYS.SYS_LOB0000033088C00004$$ by 2362205 in tablespace APPLSYSD

Solution

Check if there enough free space in tablespaces. if so please follow the steps

1. Verify NEXT_EXTENT & MAX_EXTENTS value of the segment highlighted in error

SQL> select BYTES,EXTENTS,NEXT_EXTENT,MAX_EXTENTS from dba_segments where segment_name='SYS_LOB0000033088C00004$$';

     BYTES    EXTENTS NEXT_EXTENT MAX_EXTENTS
---------- ---------- ----------- -----------
3.8703E+10         33  1.9351E+10         505

NEXT_EXTENT found to be very huge (19 GB) which is the root cause of this issue

2.Reduce segment NEXT_EXTENT size from 19 GB to 1 MB

SQL> select owner, table_name, column_name, SEGMENT_NAME  from dba_lobs where segment_name='SYS_LOB0000033088C00004$$';

OWNER          TABLE_NAME       COLUMN_NAME       SEGMENT_NAME
-----------------------------------------------------------------------------
APPLSYS        FND_LOBS          FILE_DATA      SYS_LOB0000033088C00004$$

SQL> alter table applsys.FND_LOBS modify lob ("FILE_DATA") (STORAGE (NEXT 1048576));

Table altered.

SQL> select BYTES,EXTENTS,NEXT_EXTENT,MAX_EXTENTS from dba_segments where segment_name='SYS_LOB0000033088C00004$$';

     BYTES    EXTENTS NEXT_EXTENT MAX_EXTENTS
---------- ---------- ----------- -----------
3.8703E+10         33     1048576         505

NEXT_EXTENT is greater than 1 GB & Contiguous free space of the datafile which segment is located may not accommodate next few extents which will lead to allocation of next extent in new datafile. Please verify if other datafiles in the same tablespace has sufficient contiguous space available . If not then add a datafile with size equal to or greater than NEXT_EXTENT else reduce NEXT_EXTENT size

Reference : 
Ora-1691: Unable To Extend Lobsegment Applsys.Sys_lob0000033489c00004$$ By 92170 (Doc ID 378377.1)

How To Re-attach Oracle Homes To The Central Inventory in R12.2

Problem 

Accidentally deleted oraInventory directory. 

Solution

In 12.2, application tier has 4 homes and a DB home. have to re‐attach all oracle homes. each oracle_home_name must be unique. 

For Application Tier (need to run on each file system) 

/u01/VIS/fs1/FMW_Home/oracle_common/oui/bin/runInstaller 
‐silent ‐attachHome ‐invPtrLoc /etc/oraInst.loc 
ORACLE_HOME="/u01/VIS/fs1/FMW_Home/oracle_common" 
ORACLE_HOME_NAME= "OH481075858" CLUSTER_NODES="{}" 

/u01/VIS/fs1/FMW_Home/webtier/oui/bin/runInstaller 
‐silent ‐attachHome ‐invPtrLoc /etc/oraInst.loc 
ORACLE_HOME="/u01/VIS/fs1/FMW_Home/webtier"
ORACLE_HOME_NAME="OH657355352" CLUSTER_NODES="{}" 

/u01/VIS/fs1/EBSapps/10.1.2/oui/bin/runInstaller 
‐silent ‐attachHome ‐invPtrLoc /etc/oraInst.loc 
ORACLE_HOME="/u01/VIS/fs1/EBSapps/10.1.2"
ORACLE_HOME_NAME="VIS_TOOLS__u01_VIS_fs1_EBSapps_10_1_2" 

/u01/VIS/fs1/FMW_Home/Oracle_EBS‐app1/oui/bin/runInstaller 
‐silent ‐attachHome ‐invPtrLoc /etc/oraInst.loc 
ORACLE_HOME="/u01/VIS/fs1/FMW_Home/Oracle_EBS‐app1" 
ORACLE_HOME_NAME="u01_VIS_fs1_Oracle_EBS_app" 

For DB home 

/u01/VIS/db/tech_st/11.2.0/oui/bin/runInstaller 
‐silent ‐attachHome ‐invPtrLoc /etc/oraInst.loc
ORACLE_HOME="/u01/VIS/db/tech_st/11.2.0"
ORACLE_HOME_NAME="OraDb11g_home1" 

After successfully attach above oracle homes you can find the entries from oraInventory/ContentsXML/inventory.xml file

fs1

<HOME NAME="OH481075858" LOC="/u01/VIS/fs1/FMW_Home/oracle_common" TYPE="O" IDX="5">

<HOME NAME="OH657355352" LOC="/u01/VIS/fs1/FMW_Home/webtier" TYPE="O" IDX="6">

<HOME NAME="VIS_TOOLS__u01_VIS_fs1_EBSapps_10_1_2" LOC="/u01/VIS/fs1/EBSapps/10.1.2" TYPE="O" IDX="7"/>

<HOME NAME="u01_VIS_fs1_Oracle_EBS_app" LOC="/u01/VIS/fs1/FMW_Home/Oracle_EBS‐app1" TYPE="O" IDX="8"/>

fs2

<HOME NAME="OH781075858" LOC="/u01/VIS/fs2/FMW_Home/oracle_common" TYPE="O" IDX="5">

<HOME NAME="OH957355352" LOC="/u01/VIS/fs2/FMW_Home/webtier" TYPE="O" IDX="6">

<HOME NAME="VIS_TOOLS__u01_VIS_fs2_EBSapps_10_1_2" LOC="/u01/VIS/fs2/EBSapps/10.1.2" TYPE="O" IDX="7"/>

<HOME NAME="u01_VIS_fs2_Oracle_EBS_app" LOC="/u01/VIS/fs2/FMW_Home/Oracle_EBS‐app1" TYPE="O" IDX="8"/> 

Database

<HOME NAME="OraDb11g_home1" LOC="/u01/VIS/db/tech_st/11.2.0"  TYPE="O" IDX="1"/>

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

Problem

Concurrent program completed with following warning

APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. Cannot write to the communication channel

Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. Cannot write to the communication channel.

Solution

1. Log into Applications with the System Administrator responsibility.

2. Navigate to Concurrent -> program -> define

3. Query the concurrent program. 

4. In the Output options are listed, clear the check box before the word “Print” and Leave the “Save” option selected to avoid the warning when running the program because it was unable to delete the output file which was never created.

4. Save the Changes.

Re-create lost Context file in R12

We can retrieve both application and Database tier context file by running adclonectx.pl script. Execute the following command on the applications tier.

perl <COMMON_TOP>/clone/bin/adclonectx.pl retrieve

The above command can be used only when the <INST_TOP> is still intact. In case the <INST_TOP> has also been lost accidentally, the context file may be retrieved as follows

perl <ORACLE_HOME>/appsutil/clone/bin/adclonectx.pl retrieve

On being prompted for the context file to be retrieved, select the option of retrieving the context file which you need (APPL_TOP or Database) to retrieve it to the default location specified by the script.


 The adbldxml.pl utility can be used to generate the context file on the database tier only. It is commonly used when migrating AutoConfig to a database tier not created using Rapid Install or when upgrading a database tier from Applications 11i to EBusiness Suite Release 12. This utility is not supported on the applications tier.

perl <ORACLE_HOME>/appsutil/bin adbldxml.pl appsuser=apps

Steps to change Apps password for EBS 12.2

Follow all the below steps to change apps password in 12.2 instance. Passwords for all the 3 schemas APPS, APPLSYS and APPS_NE will be changed together while changing APPLSYS password

1. Shut down the application tier services

2. Change the APPLSYS password

FNDCPASS apps/<apps_pw> 0 Y SYSTEM/<system_pw> SYSTEM APPLSYS <new_password>

3.Run Autoconfig on Application Tier with newly changed password

4. Start the Adminserver

cd $ADMIN_SCRIPTS_HOME
./adadminsrvctl.sh start

5. Change the "apps" password in WLS Datasource as follows

• Log in to WLS Administration Console.

•  Click Lock & Edit in Change Center

•  In the Domain Structure tree, expand Services, then select Data Sources

•  On the "Summary of JDBC Data Sources" page, select EBSDataSource

•  On the "Settings for EBSDataSource" page, select the Connection Pool tab.

• Enter the new password in the "Password" and "Confirm Password" field
•  Click Save
                                                                                                               
•  Click Activate Changes in Change Center

Reference
Steps to change the APPS, APPLSYS, and APPS_NE password using FNDCPASS or AFPASSWD for EBS 12.2 (Doc ID 1674462.1)

How to find Oracle EBS Weblogic Server Admin Port and URL

Weblogic admin port

Method 1

Open the Application tier context file
vi $CONTEXTFILE

Check the value of 'WLS Admin Server Port' from "s_wls_adminport" parameter


Method 2

Open the EBS domain config file
vi $EBS_DOMAIN_HOME/config/config.xml

Check the 'listen-port' value of the 'AdminServer' 


Weblogic console URL

http://<server name>. <domain name> : <weblogic Admin Port>/console 

Ex: http://oracle.test.com:7002/console