Thursday, 10 November 2016

frm-92050 failed to connect to the server /forms/servlet-1

frm-92050 failed to connect to the server /forms/servlet-1:-

If we Disable the XSS filter as below it is working fine.

MSIE 8 --->Tools > Internet Options >
Security Settings -->Custom Level >
Scroll down to entry "Enable XSS Filter" > Select Disable XSS Filter button.

Thursday, 3 November 2016

how check file versions

Two ways to check version of file.
            1. Adident   
            2. Strings
 ADIDENT Utility in ORACLE application is used to find version of any file.
STEP:-1
   Syntax : adident Header filename.
   e.g If you want to find out the version of appvndrb.pls
        $ cd AP_TOP/patch/115/sql
        $ adident Header appvndrb.pls
        o/p :
         appvndrb.pls:
         $Header appvndrb.pls 120.78.12010000.83 2010/04/27 21:00:55 vinaik ship
STEP-2
 Using Strings:
  Syntax : strings -a Top_name/location of file/filename | grep '$Header'
   e.g $ strings -a $AP_TOP/patch/115/sql/appvndrb.pls | grep '$Header'
   o/p : /* $Header: appvndrb.pls 120.78.12010000.83 2010/04/27 21:00:55 vinaik ship $ */
                                              OR
      $ cd $AP_TOP/patch/115/sql
      $ strings -a appvndrb.pls | grep '$Header'
OR
grep '$Header' $INV_TOP/patch/115/sql/INVTXGGB.pls

Wednesday, 2 November 2016

how to change maintenance mode



we can run this commands fromo any saide (DB or APPS)
How to know the status of maintenance mode:=
===============================================================================

SQL> select fnd_profile.value(‘APPS_MAINTENANCE_MODE’) from dual;

How to enable maintenance mode:=
=================================================================================

SQL> @$AD_TOP/patch/115/sql/adsetmmd.sql ENABLE

How to disable maintenance mode:=
==================================================================================

SQL> @$AD_TOP/patch/115/sql/adsetmmd.sql DISABLE



or 

run adadmin

A fatal error has been detected by the Java Runtime Environment

[oracle@apps14 12c]$ dbua
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000003ac4814d70, pid=6623, tid=139971124459280
#
# JRE version: 6.0_37-b06
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.12-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [ld-linux-x86-64.so.2+0x14d70]
#
# An error report file with more information is saved as:
# /u01/database/db/tech_st/12c/hs_err_pid6623.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted (core dumped)
[oracle@apps14 12c]$ 
TRACE FILE CONTENT
Memory: 4k page, physical 8181084k(5652968k free), swap 16777212k(16777212k free                               )

vm_info: Java HotSpot(TM) 64-Bit Server VM (20.12-b01) for linux-amd64 JRE (1.6.                               0_37-b06), built on Sep 24 2012 11:47:45 by "java_re" with gcc 3.2.2 (SuSE Linux                               )

time: Fri Sep 23 17:23:02 2016
elapsed time: 0 seconds


Solution:=
=================================================================
$ export LD_BIND_NOW=1

Then Run dbca or dbua or any