Check Versions of Oracle Applications Components Wednesday, November 7, 2007 , http://onlineappsdba.blogspot.com/ Checking the version of any File You can use the commands like the following: strings -a $XX_TOP/filename |grep '$Header'
Version of Oracle Applications You may never need this but in case you are looking at a new environment then the simplest way to figure out your application version is by navigating to Help-> About Oracle Applications from any of the forms sessions. Or Connect as apps user select release_name from apps.fnd_product_Groups; Version of Applications Forms (fmb,fmx) or reports (rdf) To find the version of any oracle applications files strings -a ICQTYED.fmx | grep Header Alternatively you can also use the adident command adident Header ICQTYED.fmx Version of a Java class File To find the version of a java class file $ strings | grep '$Header' Version of JDBC In your middle tier, edit the jserv.properties file located in the iAS_ ORACLE_HOME/Apache/Jserv/etc directory Locate the wrapper.classpath that is pointing to the jdbc zip file /u01/oracle/viscomn/java/jdbc14.zip Or http://.:port/OA_HTML/jsp/fnd/aoljtest.jsp Look for String ” JDBC driver version” under Connection String Version of Apache Go to the $iAS/Apache/Apache/bin directory and enter the following command:
$ httpd -version Version Of The OA Framework To find out the version of your Oracle appplication Framework Option 1 http://.:port/OA_HTML/OAInfo.jsp Option 2 adident Header %FND_TOP%/html/OA.jsp adident Header %OA_HTML%/OA.jsp Note: OA.jsp should be of the same version in both the places Version of Application Product or Patch Set Level. One of the most common things you will asked by your support engineer is the version or commonly known as the patch set level of your Oracle Applications product, while or after raising your service request. You can query this by logging on to your application database as the apps user. select patch_level from fnd_product_installations where patch_level like '%AD%'; Version of Discoverer cd $APPL_TOP/admin grep -I s_disco_ver_comma **xml Version of OJSP Log in to the application server as the applmgr user cd $OA_HTML edit the jtflogin.jsp file to add the following line OJSP Version: clear your cache and bounce your apache server soruce the jtflogin.jsp from your browser http://vis.oneapps.com:8000/OA_HTML/jtflogin.jsp OJSP Version: 1.1.3.5.2
Version of JSP
Log on to your HTTP Server node, and change to the OA_HTML directory. Using a text editor, create a file called test.jsp with only the following line:
Access this JSP from a web browser, using the URL: http://[your web server]:[your port]/OA_HTML/test.jsp Version of Portal select fnd_oracle_schema.getouvalue(’PORTAL’) from dual; FND_ORACLE_SCHEMA.GETOUVALUE(’PORTAL’) ——————————————————————————– PORTAL30 select WF_EVENT_XML.XMLVersion() XML_VERSION 2 from sys.dual; XML_VERSION -------------------------------------------------------------------------------Oracle XDK Java 9.0.4.0.0 Production Version of XML Publisher To check weather XML publisher is installed or not you can query the FND_PRODUCT_INSTALLATIONS table or you can lookup the reports in Oracle Applications Manager. You can find out the version for your XML publisher from the output of your report or from MetaInfo.class file. $OA_JAVA/oracle/apps/xdo/common/MetaInfo.class. Version of WorkFlow You can find out the version of your workflow using the following query SQL> select TEXT Version from WF_RESOURCES where TYPE = 'WFTKN' and NAME = 'WF_VERSION'; VERSION -------------------------------------------------------------------------------2.6.0
Version of Oracle Login Server begin execute immediate 'select fnd_oracle_schema.getouvalue(''LOGINSERVER'') from dual' into sso_user; begin execute immediate 'select user_name from fnd_user where user_name like upper('''||sso_user||''')' into sso_user_name; if sso_user is not null then execute immediate 'select version from '||sso_user||'.wwc_version$' into sso_ver; check_message := ' [PASS] Your Applications database contains Login Server version: '||sso_ver; dbms_output.put_line(check_message); end if; exception when no_data_found then null; end; exception
when others then null ; end;