APP-FND-00798: Invalid reference JA_IN_REGIMES
Getting error INVALID REFERENCE JA_IN_REGIMES IN VALUE SET ATTACHED TO SEGMENT while Opening Purchasing/Payable Lookups (Doc ID 1982243.1)
==============================================

Validate Application Accounting Definition after patch application. (Doc ID 1986653.1)

=============================
fs_clone failed because of the following error.
[UNEXPECTED]/u11/home/pdhuat/fs1/inst/apps/pdhuat_pdhx01appd05/admin/install/txkCloneAcquirePort.pl does not exist. Cannot continue
    [UNEXPECTED]Error 1 occurred while Blocking ports on pdhx01appd05

Missing perl executable "txkCloneAcquirePort.pl" was generated by running Autoconfig on RUN file system.
fs_clone went on fine.
==============================================================
ADOP (C.Delta.6)
Session Id: 3
Command: status
Output: /u11/home/pdhuat/fs_ne/EBSapps/log/status_20151101_061756/adzdshowstatus.out
===============================================================
Node Name       Node Type  Phase           Status          Started              Finished             Elapsed
--------------- ---------- --------------- --------------- -------------------- -------------------- ------------
pdhx01appd05    master     FS_CLONE        COMPLETED       2015/11/01 04:42:47  2015/11/01 06:16:52  1:34:05
File System Synchronization Type: Full
==============================================================
Patch 17919161 failing with materialized view error. Spin SR has been created for this issue.
SR 3-11637434921 : upgrade :Patch 17919161 Multiple workers failing on ORA-38818: illegal reference to editioned object.
Start time for statement above is Sat Oct 31 17:40:51 EDT 2015
Exception occured  ORA-38818: illegal reference to editioned object MTH.MTH_GREGORIAN_CALENDAR#
ORA-06512: at "APPS.AD_MV", line 252
ORA-06512: at "APPS.AD_MV", line 355
ORA-06512: at line 1
For your information I just verified and compiled the materialized view which was in compilation error. Some of the materialized view produced the following error.
SQL> ALTER MATERIALIZED VIEW MTH_RES_REQ_IT_MV COMPILE;
ALTER MATERIALIZED VIEW MTH_RES_REQ_IT_MV COMPILE                                        *
ERROR at line 1:
ORA-38818: illegal reference to editioned object MTH.MTH_GREGORIAN_CALENDAR#
Use the following query to view all the materialized view.
SELECT 'ALTER MATERIALIZED VIEW'''||MVIEW_NAME||'COMPILE;'''FROM DBA_MVIEWS;
Request OWC in oracle SR to explain the issue in detailed.
Support asked us to skip the worker for now and continue . I have done that , but there are too many MVs  failing with the same error.
Issue is that MV is a non-editioned object and it cannot depend on an editioned object.
As a workaround I have upgraded the failed MVs using "ad_zd_mview.upgrade" procedure and restarted patching as shown below. Patch is running fine for now.
I have asked support to provide a consolidated fix for all the MVs that that are depending on editioned objects.
SQL> exec ad_zd_mview.upgrade('APPS', 'MTH_EQUIP_OP_SUM_DD_MV');
================================================
Prepare phase was failing because of the following 3 tables
[ERROR]     Failed to execute SQL statement :
       begin
        ad_zd_seed.prepare('FND_PROFILE_OPTION_VALUES');
        ad_zd_seed.prepare('WF_RESOURCES');
        ad_zd_seed.prepare('IBY_BEPINFO');
      end;
[ERROR]     Error Message :
[UNEXPECTED]Error while runPendingClone sub-routine is called
I tried to run those three commands from PATCH file system but encountered the following errors
ORA-20001: Synonym does not point to a seed data table: FND_PROFILE_OPTION_VALUES
ORA-20001: Synonym does not point to a seed data table: WF_RESOURCES
ORA-20001: Synonym does not point to a seed data table: IBY_BEPINFO
This was because those tables were not upgraded by "AD_ZD_SEED.UPGRADE" procedure, while trying to upgrade them manually using the following command, we faced another issue due to the existence of PATCH edition
SQL> EXEC AD_ZD_SEED.UPGRADE('FND_PROFILE_OPTION_VALUES');
BEGIN AD_ZD_SEED.UPGRADE('FND_PROFILE_OPTION_VALUES'); END;
*
ERROR at line 1:
ORA-20001: Cannot PATCH table from Run Edition while Patch Edition exists
Hence , I have dropped the PATCH edition using abort phase and ran those commands as shown below, they went on fine
SQL> EXEC AD_ZD_SEED.UPGRADE('FND_PROFILE_OPTION_VALUES');
PL/SQL procedure successfully completed.
SQL> EXEC AD_ZD_SEED.UPGRADE('WF_RESOURCES');
PL/SQL procedure successfully completed.
SQL> EXEC AD_ZD_SEED.UPGRADE('IBY_BEPINFO');
PL/SQL procedure successfully completed.
SQL>
Now , I have triggered prepare phase, it went on fine and completed successfully.
========================
ADOP (C.Delta.6)
Session Id: 6
Command: status
Output: /u11/home/pdhuat/fs_ne/EBSapps/log/status_20151101_081951/adzdshowstatus.out
========================
Node Name       Node Type  Phase           Status          Started              Finished             Elapsed
--------------- ---------- --------------- --------------- -------------------- -------------------- ------------
pdhx01appd05    master     PREPARE         COMPLETED       2015/11/01 07:59:05  2015/11/01 08:16:51  0:17:46
                           APPLY           NOT STARTED
                           FINALIZE        NOT STARTED
                           CUTOVER         NOT STARTED
                           CLEANUP         NOT STARTED
File System Synchronization Type: None
=============================================================
Apache Lock File Issues
In setting a second and third Mid-Tier nodes, we've successfully completed the configuration of a shared APPL_TOP and shared Tech Stack. Redhat GFS was used for the shared filesystem. The only issue faced with the shared filesystem, was that Apache would fail to startup due to the "adapcctl.sh" startup script timing out. After carefully diagnosing the issue (using the "strace" command to see where the "httpd" processes were hanging), we identified that the issue resulted in Apache trying to lock files on the GFS mountpoints. This appeared to be a generic issue with most shared filesystem when locking files take place (which is in fact an Apache requirement). The issue was fixed by configuring Apache parameters "s_lock_pid_dir", "s_pids_dir" and "s_web_pid_file" (in the context xml file) to point to local mount point "/var/tmp" (instead of pointing to shared mountpoints). These changes were made to all context xml filesfor all nodes in the cluster.
R12 Login Page not Working After Applying the 12.0.4 Patch
After applying the 12.0.4 patch, for some reason, the R12 login page stopped working properly, more specifically, the R12 login page would loop between "/OA_HTML/AppsLogin" and "/OA_HTML/RF.jsp?" and consequently, the login page would not come up at all. After thorough troubleshooting, we determined that the FND tables and WF tables were not completely synchronized, thus making the "RF.jsp" go back to the AppsLogin page as user "GUEST" which in fact, does not have necessary responsibilities against WF tables. The problem was then fixed by running the "WF_LOCAL_SYNCH.VALIDATEUSERROLES" procedure.
Intermittent Issues
At one point, we were faced with two types of intermittent issues. The first was with respect to a report customization where the "Payables Open Interface Import" program used to fail intermittently with error "REP-0069: Internal error, REP-50002: Server is shutting down". After researching this issue, we've identified patch 6116405 from Metalink Note 549910.1 "Error REP-0069 and REP-50002 while Generating Reports through Concurrent Managers", which in the end, fixed the issue.
The other intermittent issue dealt with Apache producing errors of the form "404 not found in OA Framework pages". After carefully researching and diagnosing the issue, we narrowed it down to OC4J not behaving correctly and further more, identified that the error would occur only when OC4J oacore jvms were increased from 1 to 3. We then tracked down Metalink Note 731115.1,specifying to apply patch 7311892 to the 10.1.3 Oracle Home and also to add set context file parameter "s_oacore_jvm_start_options" to "-Doracle.ons.numprocs=", and of course to also run Autoconfig to propgagate all changes. This fixed the Apache errors of the form "404 not found in OA Framework pages".
=========================================
1.Oracle pre-clone fails with the following error.
START: Creating WLS config archive.
Script Executed in 1321 milliseconds, returning status 255
ERROR: Script failed, exit code 255
To implement the solution, please execute the following steps:
1. Stop all services from patch and run editions
    You can use EBSapps.env to ensure that you are on the correct file edition
2. Restart your environment
3. Rerun adpreclone
2.clone files with below error:
#############################################################
Started ApplyAppsTier at Mon Aug 31 15:13:39 EDT 2015
Version:
        ApplyAppsTier.java      :       120.11.12020000.6
#############################################################
Found the directory : /u01/oracle/AXBEBSU/fs1/FMW_Home
Exiting cloning as FMW Home already exists..
FIX: remove or move  FMW_Home and rerun rapid clone
3.Clone fails with following error.
#############################################################
Started ApplyAppsTier at Mon Aug 31 15:18:25 EDT 2015
Version:
        ApplyAppsTier.java      :       120.11.12020000.6
#############################################################
Below Oracle Homes are already registered in the global inventory:
/u01/oracle/AXBEBSU/fs1/FMW_Home/Oracle_EBS-app1
/u01/oracle/AXBEBSU/fs1/FMW_Home/webtier
/u01/oracle/AXBEBSU/fs1/FMW_Home/oracle_common
Fix: Make sure EBS environment is unset before running rapid clone.