, , , ,

Solved: You cannot run a page which is not Self Secured when the MAC fails

Sometimes we will face below issues in R12.

Issue 1:
You have insufficient privileges for the current operation. Please contact your System Administrator.

You cannot run a page which is not Self Secured when the MAC fails.

Resolution:
 
Set the below 3 profiles to None
1) FND Function Validation Level
2) FND Validation Level
3) Framework Validation Level
JDev-2
Issue 2:
Unexpected URL parameters have been detected and will be ignored Solution:
 
Resolution:

In JDeveloper, go to menu Tools–>Embedded OC4J Server Preferences–>Global–>Startup–>Select Default Local IP Address.
JDev-3
 
 
/by
, , , ,

Oracle Apps Log Files Locations in R12

Autoconfig log file:
Apps:
$INST_TOP/appl/$CONTEXT_NAME/admin/log/$MMDDHHMM/adconfig.log

Db:
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/adconfig.log $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/NetServiceHandler.log

Startup/Shutdown Log files:

$INST_TOP/logs/appl/admin/log

Apache, OC4J and OPMN:

$LOG_HOME/ora/10.1.3/Apache 
$LOG_HOME/ora/10.1.3/j2ee 
$LOG_HOME/ora/10.1.3/opmn

Patch log:

$APPL_TOP/admin/$SID/log/
Workflow Mailer log:
$APPLCSF/$APPLLOG/FNDCPGSC*.txt

Concurrent log:

$INST_TOP/apps/$CONTEXT_NAME/logs/appl/conc/log
OAM (Oracle Application Manager) log:
$APPLRGF/oam/

Clone log:

Preclone log files in source instance

Apps:
$INST_TOP/apps/$CONTEXT_NAME/admin/log/ (StageAppsTier_MMDDHHMM.log)

Db:
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_MMDDHHMM.log)

Clone log files in target instance:

Apps :
$INST_TOP/apps/$CONTEXT_NAME/admin/log/ApplyAppsTier_.log

Db:
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTier_.log

– Alert Log File:
$ORACLE_HOME/admin/$CONTEXT_NAME/bdump/alert_$SID.log

Concurrent OUT Directory:
$APPLCSF/$APPLOUT  or $APPLCSF/out
APPL_TOP – this is the top level directory for the Applications
  • $APPLCSF – the top level directory where the concurrent manager stores the log and out files of concurrent requests
  • $APPLCSF/$APPLLOG – concurrent request log files( As describe above)
  • $APPLCSF/$APPLOUT – concurrent request out files( As describe above)
  • $APPLTMP – Applications temporary files
  • $APPLPTMP – PL/SQL temporary files   or /usr/tmp (default tmp directory)
Startup and shutdown messages:
–Startup/Shutdown error message related to tech stack (10.1.2, 10.1.3 forms/reports/web)
$INST_TOP/logs/ora/ (10.1.2 & 10.1.3)
$INST_TOP/logs/ora/10.1.3/Apache/error_log[timestamp]
$INST_TOP/logs/ora/10.1.3/opmn/ (OC4J~…, oa*, opmn.log)$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.2/network/ (listener log)
$INST_TOP/logs/appl/conc/log (CM log files)
Other log files in R12

1) Database Tier
1.1) Relink Log files :
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME /MMDDHHMM/ make_$MMDDHHMM.log

1.2) Alert Log Files :
$ORACLE_HOME/admin/$CONTEXT_NAME/bdump/alert_$SID.log

1.3) Network Logs :
$ORACLE_HOME/network/admin/$SID.log

1.4) OUI Logs :
OUI Inventory Logs :
$ORACLE_HOME/admin/oui/$CONTEXT_NAME/oraInventory/logs

2) Application Tier

$ORACLE_HOME/j2ee/DevSuite/log
$ORACLE_HOME/opmn/logs
$ORACLE_HOME/network/logs

Tech Stack Patch 10.1.3 (Web/HTTP Server)
$IAS_ORACLE_HOME/j2ee/forms/log
$IAS_ORACLE_HOME/j2ee/oafm/log
$IAS_ORACLE_HOME/j2ee/oacore/log
$IAS_ORACLE_HOME/opmn/logs
$IAS_ORACLE_HOME/network/log
$INST_TOP/logs/ora/10.1.2
$INST_TOP/logs/ora/10.1.3
$INST_TOP/logs/appl/conc/log
$INST_TOP/logs/appl/admin/log

Patching related log files in R12 :
Application Tier– adpatch log – $APPL_TOP/admin//log/
Developer (Developer/Forms & Reports 10.1.2) Patch – $ORACLE_HOME/.patch_storage
Web Server (Apache) patch – $IAS_ORACLE_HOME/.patch_storage
Database Tier opatch log – $ORACLE_HOME/.patch_storage
/by
, , ,

Purge/Delete Completed Concurrent Requests in Apps

Error:Delete/Purge COMPLETED concurrent requests

Concurrent request history should not exceed 50K rows, or else it will start impacting on performance

SQL> select count(*) from FND_CONCURRENT_PROCESSES;

COUNT(*)
———-
552

SQL> select count(*) from FND_CONCURRENT_REQUESTS;

COUNT(*)
———-
85009 ==>>> Should always be below 50K, Else run “Purge Concurrent Request”
SQL>

SQL> select count(*) from FND_CONCURRENT_REQUESTS

2 where request_date > sysdate-7;

COUNT(*)
———-
19757

SQL> col “Min request|Date” for a20;

SQL> col “Max request|Date” for a20;

SQL> select min(request_date) “Min request|Date”,max(request_date) “Max request|Date” from FND_CONCURRENT_REQUESTS;

Min request|Date Max request|Date
——————– ——————–
18-NOV-09 01-NOV-11

SQL>

To clean old history of “COMPLETED” requests, follow the below note, to purge the queue

Concurrent Processing Tables and Purge Concurrent Request and/or Manager Data Program (FNDCPPUR) [ID 104282.1]

System Administrator -> Requests -> Run

Select “Single Request”

Mode = 14 days – delete all older than 14 days. Don’t make this window to small.

To view the above submitted request, do the following

Enter the request ID and “Find”

While Running:

Status on successful completion is shown below “Completed”, “Normal”


Extract from the Log File:

FNDCPPUR module: Purge Concurrent Request and/or Manager Data
+—————————————————————————+
Current system time is 01-NOV-2011 12:57:03
+—————————————————————————+
Purged 46616 entrie(s) from FND_CONCURRENT_REQUESTS :-01-NOV-2011 13:07:22

Purged 0 entrie(s) from FND_FILE_TEMP :-01-NOV-2011 13:07:22

Purged 7082 entrie(s) from FND_CRM_HISTORY :-01-NOV-2011 13:07:25

Purged 0 entrie(s) from FND_TM_EVENTS :-01-NOV-2011 13:07:25

Purged 346 entrie(s) from FND_TEMP_FILES :-01-NOV-2011 13:07:25

Purged 0 entrie(s) from FND_ENV_CONTEXT :-01-NOV-2011 13:07:46

Purged 1 entrie(s) from FND_DUAL :-01-NOV-2011 13:07:46

Purged 2 entrie(s) from FND_CONFLICTS_DOMAIN :-01-NOV-2011 13:07:46

+—————————————————————————+
Start of log messages from FND_FILE
+—————————————————————————+

/by
, , , ,

Difference between Oracle E-Business Suite R12.1 and R12.2

A journey from Oracle E-Business Suite R12.1 to R12.2:

I will try to analyze architectural overview of the latest updates, installation and upgrade options, new configuration options, and new tools for hot-cloning and automated “lights out” cloning in R12.2.

Oracle E-Business Suite 12.1 Architecture
Oracle E-Business Suite 12.2 Architecture

Release 12.2 will replace Oracle Containers for Java (OC4J) 10g with WebLogic Server 11g

Release 12.2 Database tier will run RDBMS 11gR2 to support online patching

There will be number of updates coming in release R12.2, from a technology stack perspective, EBS 12.2 will be notable for two things:

1-Replacing Oracle Containers for Java (OC4J) 10g with WebLogic Server 11g

EBS 12.2 will use WebLogic Server from Fusion Middleware 11g in place of OC4J 10g as part of the release’s internal technology stack. Other additional new Fusion Middleware 11g components used will include WebLogic JSP and UIX 11g

2-Online Patching support via 11gR2 Edition-Based Redefinition

EBS 12.2 will use the 11gR2 Database’s Edition-Based Redefinition features to provide support for Online Patching. Edition-Based Redefinition is really exciting new technology. From the 11gR2 Application Developer’s Guide:

“Edition-based redefinition enables you to upgrade the database component of an application while it is in use, thereby minimizing or eliminating down time.

“To upgrade an application while it is in use, you copy the database objects that comprise the application and redefine the copied objects in isolation. Your changes do not affect users of the application—they continue to run the unchanged application. When you are sure that your changes are correct, you make the upgraded application available to all users.”

It is not released yet but It will include significant changes to the Application Server architecture, It will use RDBMS Version 11gR2 or higher, It will change Patching, Cloning, the User Experience

Comparison of Oracle E-Business Suite 12.1 vs 12.2 Installation Steps
Oracle E-Business Suite 12.1 installation

Database Technology Stack
Database
Apps Technology Stack
Apps File System

Oracle E-Business Suite 12.2 installation
Following will be main features planned for R12.2 installations:
Native Technology Stack Install
Database RMAN Restore
Dual File System
Optional 11g Home for Upgrades
WebLogic Server (WLS)

Graphical UI to manage WLS Domain
Administration (Start/Stop WLS Instances)
Configuration (Config and Deploy, Cluster, Host, JDBC, JMS Messaging)
Monitoring (Server & Application Performance)
Troubleshooting (Performance Tuning, Log Viewer)

Following will be main features planned for R12.2 Native Technology Stack Install:
Better integration with Oracle
Universal Installer
Faster Technology Stack Installation
Silent-mode calls to install and configure Oracle Database 11.2, WebLogic Server (WLS) and Oracle HTTP Server (OHS)
AutoConfig Integration

Following will be main features planned for R12.2 Database RMAN Restore:
Simplifies Integration with Grid Infrastructure
Seamless integration with different storage methods (OCFS2, NFS, etc)
Faster integration with Automatic Storage Management (ASM)

Following will be main features planned for R12.2 Dual File System:
Online Patching allows users to continue using the application while patching
Dual File System allows replacing files with minimum downtime
Improves High Availability

Dual Port Pool configuration
Easier port assignments
Allows port customization in runtime and patching file systems

Following will be main features planned for R12.2 Optional 11g Home for Upgrades:
Allow integration with an existing 11gR2 Oracle Home
Simplified Technology Stack Upgrade
Reduced Upgrade time

Following will be main features planned for R12.2 WebLogic Server (WLS):
Graphical User Interface
WebLogic Scripting Tool (WLST)
High Availability & Failover
Consolidated Administration, Configuration and Deployment
Monitoring & Messaging
Troubleshooting framework
Integration with OAM

/by
, , ,

Now JRE 1.7.0_67 Certified with Oracle E-Business Suite

Java Runtime Environment 1.7.0_67 (a.k.a. JRE 7u67-b01) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 11i and 12.0, 12.1, and 12.2 for Windows-based desktop clients.
Effects of new support dates on Java upgrades for EBS environments
Support dates for the E-Business Suite and Java have changed.  Please review the sections below for more details:
  • What does this mean for Oracle E-Business Suite users?
  • Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
  • Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?
All JRE 6 and 7 releases are certified with EBS upon release
Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops from JRE 1.6.0_03 and later updates on the 1.6 codeline, and from JRE 7u10 and later updates on the JRE 7 codeline.  We test all new JRE 1.6 and JRE 7 releases in parallel with the JRE development process, so all new JRE 1.6 and 7 releases are considered certified with the E-Business Suite on the same day that they’re released by our Java team.

You do not need to wait for a certification announcement before applying new JRE 1.6 or JRE 7 releases to your EBS users’ desktops.

What’s new in this release?
JRE 1.7.0_67 fixes a regression in JRE 1.7.0_65 which prevented applets launching when using a “java_ arguments” parameter. This is the only change, it does not include any further security enhancements. Oracle E-Business Suite users are unlikely to be affected by this issue so moving to this release is optional, see the Update Release Notes for further information. 
JRE 1.7.0_67 is available for download through the usual Java and Oracle Java SE Downloads public sites. If you are already running 1.7.0_65 auto-update will not be triggered to upgrade to 1.7.0_67. The standard release is also available through Patch 19295656 as well as a special release which has the auto-update function turned off through Patch 19295660. 
32-bit and 64-bit versions certified
This certification includes both the 32-bit and 64-bit JRE versions for various Windows operating systems. See the respective Recommended Browser documentation for your EBS release for details.
Where are the official patch requirements documented?
All patches required for ensuring full compatibility of the E-Business Suite with JRE 7 are documented in these Notes:

For EBS 11i: 

For EBS 12.0, 12.1, 12.2

EBS + Discoverer 11g Users 

This JRE release is certified for Discoverer 11g in E-Business Suite environments with the following minimum requirements:
Worried about the ‘mismanaged session cookie’ issue? 
No need to worry — it’s fixed.  To recap: JRE releases 1.6.0_18 through 1.6.0_22 had issues with mismanaging session cookies that affected some users in some circumstances.

The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases on the JRE 6 and 7 codelines.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22 on the JRE 6 codeline, and JRE 7u10 and later JRE 7 codeline updates.

Implications of Java 6 End of Public Updates for EBS Users
The Support Roadmap for Oracle Java is published here:
The latest updates to that page (as of Sept. 19, 2012) state (emphasis added):
Java SE 6 End of Public Updates Notice 
After February 2013, Oracle will no longer post updates of Java SE 6 to its public download sites. Existing Java SE 6 downloads already posted as of February 2013 will remain accessible in the Java Archive on Oracle Technology Network. Developers and end-users are encouraged to update to more recent Java SE versions that remain available for public download. For enterprise customers, who need continued access to critical bug fixes and security fixes as well as general maintenance for Java SE 6 or older versions, long term support is available through Oracle Java SE Support .
What does this mean for Oracle E-Business Suite users?
EBS users fall under the category of “enterprise users” above.  Java is an integral part of the Oracle E-Business Suite technology stack, so EBS users will continue to receive Java SE 6 updates from February 2013 to the end of Java SE 6 Extended Support in June 2017.
In other words, nothing changes for EBS users after February 2013. 

EBS users will continue to receive critical bug fixes and security fixes as well as general maintenance for Java SE 6 until the end of Java SE 6 Extended Support in June 2017. 

How can EBS customers obtain Java 6 updates after the public end-of-life?
EBS customers can download Java 6 patches from My Oracle Support.  For a complete list of all Java SE patch numbers, see:
Both JDK and JRE packages are contained in a single combined download after 6u45.  Download the “JDK” package for both the desktop client JRE and the server-side JDK package.  
Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
This upgrade is highly recommended but remains optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 desktop clients. 
Java 6 is covered by Extended Support until June 2017.  All E-Business Suite customers must upgrade to JRE 7 by June 2017.
Coexistence of JRE 6 and JRE 7 on Windows desktops 
The upgrade to JRE 7 is highly recommended for EBS users, but some users may need to run both JRE 6 and 7 on their Windows desktops for reasons unrelated to the E-Business Suite.
Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 7 will be invoked instead of JRE 6 if both are installed on a Windows desktop. For more details, see “Appendix B: Static vs. Non-static Versioning and Set Up Options” in Notes 290807.1 and 393931.1.
Applying Updates to JRE 6 and JRE 7 to Windows desktops
Auto-update will keep JRE 7 up-to-date for Windows users with JRE 7 installed. 
Auto-update will only keep JRE 7 up-to-date for Windows users with both JRE 6 and 7 installed. 
JRE 6 users are strongly encouraged to apply the latest Critical Patch Updates as soon as possible after each release. The Jave SE CPUs will be available via My Oracle Support.  EBS users can find more information about JRE 6 and 7 updates here:
The dates for future Java SE CPUs can be found on the Critical Patch Updates, Security Alerts and Third Party Bulletin.  An RSS feed is available on that site for those who would like to be kept up-to-date.
What do Mac users need?
Mac users running Mac OS X 10.9 can run JRE 7 plug-ins.  See this article: 
  • EBS Release 12 Certified with Mac OS X 10.9 with Safari 7 and JRE 7

Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

JRE is used for desktop clients.  JDK is used for application tier servers 
JDK upgrades for E-Business Suite application tier servers are highly recommended but currently remain optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6 for application tier servers. 

Java SE 6 is covered by Extended Support until June 2017.  All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 by June 2017. EBS customers running their application tier servers on other operating systems should check with their respective vendors for the support dates for those platforms.

References
/by