Version Checks

Version of objects is often needed by support.


CONTENTS
--------

1. Oracle Applications
2. Forms
3. Reports
4. SQL or PL/SQL Scripts
5. Executables
6. Other Files
7. RDMBS
8. Database Objects
9. Operating System


1. ORACLE APPLICATIONS

a. To obtain version of form from any applications form, navigate to the form.
Then in the Menu toolbar select Help => About Oracle Applications.

NOTE:  A pop-up window will open indicating the version of:

 Oracle Applications version
 Current used module
 Oracle Forms version
 RDBMS
 Current open form

b. Also run the following command:

 sqlplus applsys/
 select release_name from fnd_product_group;


2. FORMS

a. If the form is displayed, review #1 above to get current open form version.
b. In the event the form doesn't appear then:

  (1).  Retreive the form name from another environment which has the same form.
        (i.d. NLS, test or production, etc.) or from Metalink.

  (2).  Navigate to /forms (/ eventually) directory.  The 
        corresponding file with the .fmx extension should be located here.

  (3).  See #6 below to obtain the file version.


3. REPORTS

a.  First check the report name on located at the top of the log file.
b.  Navigate to /reports(/ eventually) directory.  The
    corresponding file with the .rdf extension should be located here.
c.  See #6 below to obtain the file version.


4. SQL OR PL/SQL SCRIPTS

a.  Navigate to /admin/sql or /patch/110/sql to obtain the last version.
    The corresponding file with .sql, .pls, .pkh, or .pkb extension should be located
    here.
b.  See #6 below to get the file version.


5. EXECUTABLES

a.  Binary or executable names often do not have extensions on unix systems.
    In MS-Windows environments the extensions are usually .exe or .dll.
b.  Most of the executables are located under the

/bin

    directory.
c.  There are many methods for obtaining the version of an executable.  These methods
    are listed below:

   (1).  If an interface is displayed, go to the Menu => Help => About.
         e.g. Oracle Applications, internet browsers, tools (Oracle Forms,
         Oracle Reports, Enterprise Manager, SQL*Plus)
         'Help => About Plug-ins' will provide the Jinitiator version.

   (2).  Run the file without parameter.
         e.g. f45gen, f60gen (for Oracle Forms)
         r25convm, rwcon60 (for Oracle Reports)
         sqlplus (for SQL*Plus)
         tnsping (TNS Ping Utility)
         jre (Java Runtime Loader)
            
  
   (3).  To see properties of the file with MS-Windows Explorer.
         e.g. *.exe, *.dll files


   (4).  To find the 'Header' string, see #6 to proceed.
         e.g. ad utilities (adpatch, adrelink, etc.), fnd executables,
         binaries under /bin directories

   (5).  Run a specific command
         e.g. Appletviewer:
             java -version

         Oracle Workflow in Oracle Applications:
           sqlplus apps/ 
           @$FND_TOP/sql/wfver.sql
           or
           select TEXT from WF_RESOURCES where NAME='WF_VERSION';

   (6).  Launch Oracle Installer
  
      Several Oracle products (like RDBMS and Tools) require ORAINST to be installed.
      Below is the method to launch ORAINST and obtain the version of various products:

      (a).  Login with Oracle account
      (b).  Run Oracle Installer using:
            $ORACLE_HOME/orainst/orainst

          or

            Under MS-Windows:
            $ORACLE_HOME\bin\orainst.exe

      (c).  Answer by taking defaults to reach 'Software Asset Manager' screen.

      (d).  Right column will display installed products and versions.

            NOTE: Same information is found in the files below:
            $ORACLE_HOME/orainst/unix.rgs (Unix)
            $ORACLE_HOME\orainst\nt.rgs, windows.rgs (Win NT, MS-Windows)



6. OTHER FILES

A.  Other files on the file system may be:
 
 driver files (*.drv)
 object description files (*.odf)
 data files (*.dat)
 library and object files (*.a, *.o)
 Oracle Forms libraries (*.pll, *.plx)
 Oracle Forms menu files (*.mmb, *.mmx)
 form source files (*.fmb)
 jar file (*.jar)
 java class file (*.class)
 html, xlm files (*.htm, *.xlm)

b.  Navigate to the corresponding directory.
c.  Execute one of the following commands to obtain the version of the file
    on all platforms (beginning with Oracle Applications v. 11.x):
     adident Header

    On Unix:
     strings -a | grep Header

    On Windows (DOS box):
     find "Header"


7. RDMBS

a. See #1.a to obtain the version of the Oracle Server installed in the environment.
b. Another method for obtaining the version is by executing sqlplus.
   It displays SQL*Plus and RDBMS version.

   e.g. Oracle8 Enterprise Edition Release 8.0.6.1.

c. If the preference is to use Oracle Installer, then review #5c(6) to also obtain the
   version of several installed products.


8. DATABASE OBJECTS

a. Run the following sql statement to obtain the package version:

   select text from user_source where name='&package_name'
   and text like '%$Header%';

NOTE:  The prompt requests the package name. By providing the package name it will
       return two lines corresponding to specifications and body creation files.

       You can also obtain the pls version on the database by running:

       select name, text
       from dba_source
       where text like '%.pls%'
       and line < 10;


b. To obtain the version information in the view definition run the sql below:

   col TEXT for a40 head "TEXT"
   select VIEW_NAME, TEXT
   from USER_VIEWS
   where VIEW_NAME = '&VIEW_NAME';

c. To obtain the workflow related objects run the wfver.sql script. Review #5c(5) above
   to obtain the version of workflow packages and views.


9. OPERATING SYSTEM

a. For most Unix platforms run command:
 
   uname -a

b. For MS-WINDOWS 95/98/2000

   Start => Parameters => Control Panel => System

c. For WIN/NT, execute command:

   winver

   or

   Menu: Start => Programs => Admin Tools => WIN NT Diagnostic



RELATED DOCUMENTS
-----------------

Note 106767.1 How To Determine The Version Of An Applications Form In
Release 11?