Share the content if you found it is useful (You can share using 300 community websites) click "share" at the end of the post.

You are encouraged to leave a comment.








Thursday, August 18, 2011

Sun JRE1.6.0 update 27 has been certified for E Biz

Some questions following our last JRE certification indicated that there's still lingering confusion about which JRE releases are safe to use with E-Business Suite environments. 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. In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22: for example, JRE 1.6.0_23, 1.6.0_24, 1.6.0_25, and 1.6.0_26.

As of today, you 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.

All JRE 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 higher. We test all new JRE releases in parallel with the JRE development process, so all JRE 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 releases to your EBS users' desktops. If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

What's new in Java 1.6.0_27?

See the 1.6.0_27 Update Release Notes for details about what has changed in this release. This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

JRE 1.6.0_27 provides the following fixes and functionality change that may affect Oracle E-Business Suite customers:

  • The browser window opening behind the Forms window issue is now fixed for Windows Vista and Windows 7 users running IE.
  • Selecting the "Close Window" Link through Internet Explorer will no longer display a modal window with the prompt, "The webpage you are viewing is trying to close the tab, Do you want to close this tab?".
  • Due to JRE6u27 now adhering more strictly to the IE browser settings, "File Export" and certain "Form Attachments" will now fail through IE without the correct browser setting for IE6, IE7 & IE8 users.

This JRE release has been certified with both Oracle E-Business Suite Release 11i and 12. We recommend this release for all E-Business Suite users.

Tuesday, August 09, 2011

IE9 is certified with Oracle E Business Suite

Internet Explorer 9 Certified with Oracle E-Business Suite

MS IE logoMicrosoft 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

EBS 12.0 Prerequisites

  • Oracle Applications Technology R12.ATG_PF.A.DELTA.6 (patch 7237006) or higher.
  • Oracle Forms Version 10.1.2.3 or higher.
  • Java plug-in JRE 1.6.0_03 or higher.

EBS 11i Prerequisites

  • Oracle Applications patch 10 (11.5.10) plus Maintenance Pack 11.5.10 CU2 or higher
  • Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (RUP 6) (patch 5903765) or higher.
  • Oracle Developer 6i patchset 19 (6.0.8.28.x) (see Note 125767.1)
  • Java plug-in JRE 1.6.0_03 or higher.
  • MLR patch 8888184 or higher (AIX Users should apply MLR patch 10043867 which replaces 8888184)
for More information.. please visit:

http://blogs.oracle.com/stevenChan/entry/internet_explorer_9_certified_with?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+OracleE-BusinessSuiteTechnology+(Oracle+E-Business+Suite+Technology)


To change ORACLE logo in Forms R12 Instances

Steps to Change the ORACLE Logo in the Forms of R12 Instances:

The idea here is to replace the logo in frmall.jar. Then reload it.

cp $ORACLE_HOME/forms/java/frmall.jar $ORACLE_HOME/forms/java/frmall.jar_BAK


cp $ORACLE_HOME/forms/java/frmall.jar /tmp

cd /tmp

jar -xvf frmall.jar

rm -rf META-INF/

Rename the logo of your logo of size (125X30 pixels) to oracle_logo_light.gif


copy your own oracle_logo_light.gif to oracle/forms/icons/oracle_logo_light.gif in the /tmp folder.
cd /tmp


jar -cvf frmall.jar *


cp frmall.jar $ORACLE_HOME/forms/java/frmall.jar

adadmin (jar regenerate) and use the FORCE option

(selection option 1, regenerate Product JAR file, and

Do you wish to force regeneration of all jar files? [No] ? Yes

Retest the issue by opening the forms.



Cheers...


Friday, August 05, 2011

Trace Level 8 and SQLTXPLAIN

One of my Service Request needs to be updated with Trace Level 8 and SQLTXPLAIN:

I got the sql which took longer wait event through enabling the trace at the forms level.

Enabling Trace level 8 at backend:

ALTER SESSION SET EVENTS '10046 trace name context forever, level 8';

Session Altered

Run the query.

SQL> ALTER SESSION SET EVENTS '10046 trace name context off';

Session altered.


To obtain the trace file use the following SQL

SET LINESIZE 100
COLUMN trace_file FORMAT A60

SELECT s.sid,
s.serial#,
pa.value || '/' || LOWER(SYS_CONTEXT('userenv','instance_name')) ||
'_ora_' || p.spid || '.trc' AS trace_file
FROM v$session s,
v$process p,
v$parameter pa
WHERE pa.name = 'user_dump_dest'
AND s.paddr = p.addr
AND s.audsid = SYS_CONTEXT('USERENV', 'SESSIONID');
This will provide you the trace file location.


SQLTXPLAIN:

  1. Download the file sqlt.zip file from Note 215187.1 and unzip it to an empty local or server directory. This will create the "sqlt" directory and a number of subdirectories.
  2. In the sqlt/install directory run the script "sqcreate.sql"
    • Navigate to the sqlt/install directory
    • Start SQL*Plus connecting INTERNAL (SYS) as SYSDBA
    • Execute script sqcreate.sql and respond to values requested
EXAMPLE:
$ sqlplus / as sysdba
SQL> start sqcreate.sql


During the run, it will ask for the Connect Descriptor like @PROD, give your SID with @symbol.
It will ask for the sqltxplain Tablespace (Provide the tablespace name other than SYSTEM and SYSAUX). Later provide the schema password for the sqltxplain. It will create views and tables related with SQLTXPLAIN.

Create the sql to be analyzed as txt file. (eg. sqltxt.txt)

and move to the directory $ORACLE_HOME/sqlt/run

connect as apps and with apps password.

Run
@sqltxplain sqltxt.txt

It will run for a moment and asks you the password for SQLTXPLAIN schema password. Providing that will enable the script to export the output files to a dmp file and later it will zip them as a single file.

Move the zip file to your local computer and upload to SR.

Now, you will be having the sql with trace level 8 and SQLTXPLAIN.

Cheers!!!
Related Posts Plugin for WordPress, Blogger...

Let us be Friends...

Share |

Popular Posts

Recent Comments