Many of you would have noticed that while launching forms from Oracle Applications 11.5.10 using Internet Explorer (IE 7) then it might crash with following error. Though it may work perfectly fine in mozilla firefox.
This is the working fix for the issue.
Solution-1:
1) Take backup of jvm.dll located at c:\Program Files\Oracle\JInitiator 1.3.1.21\bin\hotspot directory.
2) Copy jvm.dll from C:\Program Files\Java\jre1.6.0_07\bin\client (or whichever highest version of jre you have) to c:\Program Files\Oracle\JInitiator 1.3.1.21\bin\hotspot
3) Clear browser cache and also Oracle Jar cache (Remove all files from c:\documents and settings\<username>\Oralce Jar cache)
4) Close all the browsers and restart
Enjoy !! The issue should have been resolved now !
Solution-2:
In case if you are unable to find the jvm.dll in that location or if the above solution didn’t work for you, you can download the working jvm.dll from this link.
Categories: Oracle, Oracle Applications, Oracle Applications DBA, Oracle Applications issues Tags: 7, crash, forms, IE, internet explorer, jvm, jvm.dll, launch, Oracle, oracle applications
Click here to download cmclean.sql
REM
REM FILENAME
REM cmclean.sql
REM DESCRIPTION
REM Clean out the concurrent manager tables
REM NOTES
REM Usage: sqlplus <apps_user/apps_passwd> @cmclean
REM
REM
REM $Id: cmclean.sql,v 1.4 2001/04/07 15:55:07 pferguso Exp $
REM
REM
REM +==============================+
set verify off;
set head off;
set timing off
set pagesize 1000
column manager format a20 heading ‘Manager short name’
column pid heading ‘Process id’
column pscode format a12 heading ‘Status code’
column ccode format a12 heading ‘Control code’
column request heading ‘Request ID’
column pcode format a6 heading ‘Phase’
column scode format a6 heading ‘Status’
WHENEVER SQLERROR EXIT ROLLBACK; Read more…
We can submit concurrent programs from OS command / shell prompt using CONCSUB utility. Following is the syntax of the same:
CONCSUB <APPS username>/<APPS password>
<responsibility application short name>
<responsibility name>
<username>
[WAIT=N|Y|<n seconds>]
CONCURRENT
<program application short name>
<program name>
[PROGRAM_NAME="<description>"]
[REPEAT_TIME=<resubmission time>]
[REPEAT_INTERVAL= <number>]
[REPEAT_INTERVAL_UNIT=< resubmission unit>]
[REPEAT_INTERVAL_TYPE=< resubmission type>]
[REPEAT_END=<resubmission end date and time>]
[NLS_LANGUAGE=<language of the request>]
[NLS_TERRITORY=<territory of the request>]
[START=<date>]
[IMPLICIT=< type of concurrent request>
[<parameter 1> ... <parameter n>]
Examples:
Active Users
CONCSUB apps/[apps_pwd] SYSADMIN “System Administrator” SYSADMIN WAIT=N CONCURRENT FND FNDSCURS
Prints Environment Variables
CONCSUB apps/[apps_pwd] SYSADMIN “System Administrator” SYSADMIN WAIT=N CONCURRENT FND FNDPRNEV APPL_TOP
Table Name: FND_CONCURRENT_REQUESTS
Column Name: PHASE_CODE
| Value |
Meaning |
| C |
Completed |
| I |
Inactive |
| P |
Pending |
| R |
Running |
Table Name: FND_CONCURRENT_REQUESTS
Column Name: STATUS_CODE
| Value |
Meaning |
| D |
Cancelled |
| U |
Disabled |
| E |
Error |
| M |
No Manager |
| R |
Normal |
| I |
Normal |
| C |
Normal |
| H |
On Hold |
| W |
Paused |
| B |
Resuming |
| P |
Scheduled |
| Q |
Standby |
| S |
Suspended |
| X |
Terminated |
| T |
Terminating |
| A |
Waiting |
| Z |
Waiting |
| G |
Warning |
/*+ hint */
/*+ hint(argument) */
/*+ hint(argument-1 argument-2) */
All hints except /*+ rule */ cause the CBO to be used. Therefore, it is good practise to analyze the underlying tables if hints are used (or the query is fully hinted.
There should be no schema names in hints. Hints must use aliases if alias names are used for table names. So the following is wrong:
select /*+ index(scott.emp ix_emp) */ from scott.emp emp_alias
better:
select /*+ index(emp_alias ix_emp) */ … from scott.emp emp_alias
Why using hints
Read more…
