- Oracle Application Server 10g Release 3 Download
- Oracle Application Server Latest Version
- Oracle Application Server Version For Windows 10
Because Oracle Database continues to evolve and can require maintenance, Oracle periodically produces new releases. Not all customers initially subscribe to a new release or require specific maintenance for their existing release. As a result, multiple releases of the product exist simultaneously.
As many as five numbers may be required to fully identify a release. The significance of these numbers is discussed in the sections that follow.
- During the installation of some application software, we build the necessary schema objects in Oracle if they don't exist. Additionally, we point out any potential problems to the user doing the install. Some of these problems vary with the Oracle server platform.
- Actions Maintaining/Patching Oracle Application Server 10g (10.1.2) The remainder of this document outlines all the patches and alerts that you should be applying after installation, depending on the what version or patches you may already have installed.
- Oracle WebLogic Server is a Java EE application server currently developed by Oracle Corporation.Oracle acquired WebLogic Server when it purchased BEA Systems in 2008.
Nov 15, 2010 How do I know which version of Oracle EBS r12 I have? R12.0.1, r12.1? How do I know which version of Oracle EBS 11i? Is there a table I can query?
Release Number Format
To understand the release nomenclature used by Oracle, examine the following example of an Oracle Database server labeled 'Release 10.1.0.1.0'.
Figure 1-1 Example of an Oracle Database Release Number
Description of 'Figure 1-1 Example of an Oracle Database Release Number'
Note:
Starting with release 9.2, maintenance releases of Oracle Database are denoted by a change to the second digit of a release number. In previous releases, the third digit indicated a particular maintenance release.Major Database Release Number
The first digit is the most general identifier. It represents a major new version of the software that contains significant new functionality.
Database Maintenance Release Number
The second digit represents a maintenance release level. Some new features may also be included.
Application Server Release Number
The third digit reflects the release level of the Oracle Application Server (OracleAS).
Component-Specific Release Number
The fourth digit identifies a release level specific to a component. Different components can have different numbers in this position depending upon, for example, component patch sets or interim releases.
Platform-Specific Release Number
The fifth digit identifies a platform-specific release. Usually this is a patch set. When different platforms require the equivalent patch set, this digit will be the same across the affected platforms.
Checking Your Current Release Number
To identify the release of Oracle Database that is currently installed and to see the release levels of other database components you are using, query the data dictionary view
PRODUCT_COMPONENT_VERSION
. A sample query follows. (You can also query the V$VERSION
view to see component-level information.) Other product release levels may increment independent of the database server.It is important to convey to Oracle the results of this query when you report problems with the software.
This appendix describes how to view Oracle Application Server release numbers.
It contains the following topics:
Note: Oracle recommends you keep a log of all interim patches applied to your Oracle Application Server installations. |
I.1Release Number Format
To understand the release level nomenclature used by Oracle, examine the example of an Oracle release number shown in Figure I-1.
Figure I-1 Example of an Oracle Release Number
Description of 'Figure I-1 Example of an Oracle Release Number'
In Figure I-1, each digit is labeled:
- Major Oracle Platform NumberThis is the most general identifier. It represents a major new edition (or version) of an application, such as Oracle database server or Oracle Application Server, and indicates that the release contains significant new functionality.
- Database Maintenance Release NumberThis digit represents a maintenance release level. Some new features may also be included.
- Application Server Release NumberThis digit reflects the release level of Oracle Application Server.
- Component Specific Release NumberThis digit identifies a release level specific to a component. Different components can have different numbers in this position depending upon, for example, component patch sets or interim releases.
- Platform Specific Release NumberThis digit identifies a platform-specific release.
I.2Viewing Oracle Application Server Installation Release Numbers
All Oracle Application Server installations have a release number. This number is updated when you apply a patch set release or upgrade the installation.
You can view the release number of an Oracle Application Server installation using Oracle Universal Installer, as follows:
- Launch Oracle Universal Installer:
- Click Installed Products to open the Inventory Page.
- In the Inventory Page, expand Oracle Homes. You will see entries for all installations on your host.
- Expand the Oracle home entry for the installation you are interested in.
- You will see an entry with the release number for your original installation, followed by entries for any patch sets that have been applied.
I.3Viewing Component Release Numbers
All Oracle Application Server components have a release number and many contain services that have release numbers. These numbers may be updated when you apply a patch set release or upgrade the installation.
You can view the release number of components and their services in the following ways:
On the Filesystem
You can view component release numbers as follows on UNIX:
Using Oracle Universal Installer
If you installed Oracle Application Server using Oracle Universal Installer, you can view component release numbers as follows:
- Launch Oracle Universal Installer:
- Click Installed Products to open the Inventory Page.
- In the Inventory Page, expand Oracle Homes. You will see entries for all installations on your host.
- Expand the Oracle home entry for the installation you are interested in.
- You will see an entry with the release number for your original installation, followed by entries for any patch sets that have been applied.
- Expand the initial entry to view the component release numbers at installation time. If you have subsequent patch set entries, expand them to see the component release numbers updated for each patch set.
I.4Viewing Oracle Internet Directory Release Numbers
Oracle Internet Directory has a server release number, which is the version of the binaries. It also has schema and context versions. All of these numbers correspond to the Oracle Application Server installation release number through the third digit. These numbers may be updated when you apply a patch set release or upgrade the installation.
Viewing the Oracle Internet Directory Server Release Number
The Oracle Internet Directory server release number is the version of the binaries. You can view the Oracle Internet Directory server release number as follows:
- Make sure the
ORACLE_HOME
environment variable is set. - Run the following command:
Viewing the Oracle Internet Directory Schema and Context Versions
You can view the Oracle Internet Directory schema and context versions in this file:
Oracle Application Server 10g Release 3 Download
The contents of this file are kept up-to-date, however, you can also query the schema and context release from Oracle Internet Directory, just to be sure.
To view the schema version:
- Make sure the
ORACLE_HOME
environment variable is set. - Run the following command:The output will be in this form:
To view the context version:
- Make sure the
ORACLE_HOME
environment variable is set. - Run the following command:The output will be in this form:
I.5Viewing Metadata Repository Release Numbers
Metadata Repositories have the following release numbers:
- Database release numberThis is the Oracle Database 10g database release number.
- Metadata Repository Container release numberThis is the release number for the Metadata Repository. The number is equal to the Oracle Application Server installation release number.
- Schema release numbersThe Oracle Application Server schemas in the Metadata Repository have release numbers. These numbers do not necessarily correspond to Oracle Application Server release numbers or database release numbers.
Viewing the Database Release Number
The Metadata Repository is an Oracle Database 10g database that has a release number. This number is updated when you apply a patch set release or upgrade the database.
You can view the Metadata Repository release number using SQL*Plus as follows (you can be connected to the database as any user to issue these commands):
Viewing Metadata Repository Container and Schema Release Numbers
You can view the Metadata Repository Container release number, as well as schema release numbers, using SQL*Plus as follows (you must log in as a user with SYSDBA privileges):
IAS_VERSIONS
is a public synonym to a view owned by the INTERNET_APPSERVER_REGISTRY
user. If the preceding query returns an error, it may be because:- There was an error in seeding one or more components
- Not all of the components whose underlying tables are read by the view are present in the database
Either case indicates that the database is not properly seeded to be a Metadata Repository.
To get the same result by querying the underlying table:
I.6 Using the OPatch Utility
The OPatch utility is a tool that allows the application and rollback of interim patches to Oracle products, such as Oracle Application Server. For the latest information about the opatch utility, and to check for updates, refer to Oracle MetaLink at
I.6.1 Requirements
The OPatch utility has the following requirements:
- Perl environment, included with Oracle Application Server or downloaded with a patch set.
- The Oracle home environment variable (ORACLE_HOME) must point to a valid Oracle home directory and match the value used during installation of the Oracle home directory.
- If the
-invPtrLoc
command-line argument was used during installation, then it must be used when using the OPatch utility. Oracle recommends the use of the default central inventory for a platform. - The
jar
,java
,ar
,cp
, andmake
commands must be available in the PATH statement. The commands are not available for all platforms. - The library path must be set correctly for Oracle Real Application Clusters environments. Refer to the FAQ document in the
opatch/doc
directory for additional information.
See Also: For the latest information about the OPatch utility, and to check for updates, refer to OracleMetaLink at |
I.6.2 Running the OPatch Utility
The OPatch utility is located in the
ORACLE_HOME/OPatch
directory. It is run with options and command-line arguments. The following command shows the syntax for the OPatch utility:In the preceding command, the following variables are used:
command_line_arguments
: The command-line arguments for the option. Values are described in the following sections.option
: The OPatch option. Values are described in the following table:Option Description apply Installs an interim patch. Refer to Section I.6.2.1 for more information. lsinventory Lists what is currently installed on the system. Refer to Section I.6.2.2 for more information. query Queries a given patch for specific details. Refer to Section I.6.2.3 for more information. rollback Removes an interim patch. Refer to Section I.6.2.4 for more information. version Prints the current version of the patch tool. Refer to Section I.6.2.5 for more information.
To view additional information for any option, use the following command:
If using Perl, then use the following command:
I.6.2.1 apply Option
The
apply
option applies an interim patch to a specified Oracle home. The ORACLE_HOME environment variable must be set to the Oracle home to be patched. The following syntax is used for this option:The following table lists the command-line arguments available for use with the
apply
option:Argument | Description |
---|---|
delay | Specifies how many seconds to wait before attempting to lock the inventory in the case of a previous failure. |
force | Removes conflicting patches from the system. If a conflict exists which prevents the patch from being applied, then the -force command-line argument can be used to apply the patch. |
invPtrLoc | Specifies the location of the oraInst.loc file. This command-line argument is needed when the -invPtrLoc argument was used during installation. Oracle recommends the use of the default central inventory for a platform. |
jdk | Specifies the location of a particular JDK (jar) to use instead of the default location under the Oracle home directory. |
jre | Specifies the location of a particular JRE (Java) to use instead of the default location under the Oracle home directory. |
local | Specifies that the OPatch utility patch the local node and update the inventory of the local node. It does not propagate the patch or inventory update to other nodes. This command-line argument can be used on Oracle Real Application Clusters environments and non-clustered environments. If an entire cluster is shutdown before patching, then this argument can be used for non-rolling patches. |
minimize_downtime | Specifies the order of nodes to be patched by the OPatch utility. This command-line argument only applies to Oracle Real Application Clusters environments. It cannot be used with the -local command-line argument or a rolling patch. |
no_bug_superset | Specifies to error out if the current patch bugs-to-fix is a superset or the same as an installed patch bugs-fixed in the Oracle home directory. |
no_inventory | Bypasses the inventory for reading and updates. This command-line argument cannot be used with the -local command-line argument. This command-line argument puts the installation into an unsupported state. |
oh | Specifies the Oracle home directory to use instead of the default. |
opatch_post_end | Marks the end of the post options. This command-line argument is used with the post command-line argument. If this argument is not used, then everything after post is passed into post . |
opatch_pre_end | Marks the end of the pre options. This command-line argument is used with the pre command-line argument. If this argument is not used, then everything after pre is passed into pre . |
post | Specifies the parameters to be passed inside the post script besides the standard parameters. |
pre | Specifies the parameters to be passed inside the pre script besides the standard parameters. |
retry | Specifies how many times the OPatch utility should try when there is an inventory lock failure. |
patch_location | Specifies the directory of the interim patch. This should be a directory with the same name as the patch. |
silent | Suppresses user interaction, and defaults any answers to 'yes.' |
verbose | Prints output to the screen as well as to the log file. |
Note: If a patch consists of SQL changes, then they are only staged. Follow the instructions included with the patch to apply the patch manually on the affected instances. For some products, such as OracleAS Portal, the SQL application may be implemented as a post-staging action by the tool. These patches cannot be rolled back. |
I.6.2.2 lsinventory Option
![Oracle application server version for windows 10 Oracle application server version for windows 10](/uploads/1/2/6/2/126247130/184051914.jpg)
The
lsinventory
option reports what has been installed on the system for a particular Oracle home directory, or for all installations. The following syntax is used for this option:The following table lists the command-line arguments available for use with the
lsinventory
option:Argument | Description |
---|---|
all | Reports the name and installation directory for each found Oracle home directory. |
detail | Reports the installed products and other details. This command-line argument cannot be used with the -all command-line argument. |
invPtrLoc | Specifies the location of the oraInst.loc file. This command-line argument is needed when the invPtrLoc command-line argument was used during installation. Oracle recommends the use of the default central inventory for a platform. |
jre | Specifies the location of a particular JRE (Java) to use instead of the default location under the Oracle home directory. |
oh | Specifies the Oracle home directory to use instead of the default directory. |
The following is a sample output of
opatch lsinventory -detail
:I.6.2.3 query Option
The
query
option queries a specific patch for specific details. It provides information about the patch and the system being patched. The following syntax is used for this option:The following table lists the command-line arguments available for use with the
query
option:Argument | Description |
---|---|
all | Retrieves all information about a patch. This is equivalent to setting all command-line arguments. |
get_base_bug | Describes the base bugs fixed by a patch. |
get_component | Describes the Oracle components, optional or required, for a patch. |
get_date | Provides the build date of a patch. |
get_os | Provides the operating system description supported by a patch. |
get_system_change | Describes the changes that will be made to the system by a patch. This command-line argument is not available. |
is_rolling | Specifies if the patch is a rolling patch for Oracle Real Application Clusters. The set of patches need not be applied to the whole cluster at the same time. The patches can be applied to a select set of nodes at a time. |
I.6.2.4 rollback Option
The
rollback
option removes a specific interim patch from the appropriate Oracle home directory. The following syntax is used for this option:The following table lists the command-line arguments available for use with the
rollback
option:Argument | Description |
---|---|
delay | Specifies how many seconds the OPatch utility should wait before attempting to lock inventory again, if the -retry command-line argument is used with the apply option. |
id | Indicates the patch to be rolled back. Use the -lsinventory option to display all patch identifiers. To successfully rollback a patch, the patch identifier must be supplied. |
invPtrLoc | Specifies the location of the oraInst.loc file. This command-line argument is needed when the -invPtrLoc command-line argument was used during installation. Oracle recommends the use of the default central inventory for a platform. |
jdk | Specifies the location of a particular JDK (jar) to use instead of the default location under the Oracle home directory. |
jre | Specifies the location of a particular JRE (Java) to use instead of the default location under the Oracle home directory. |
local | Specifies that the OPatch utility patch the local node and update the inventory of the local node. It does not propagate the patch or inventory update to other nodes. This command-line argument can be used on Oracle Real Application Clusters environments and non-clustered environments. If an entire cluster is shutdown before patching, then this argument can be used for non-rolling patches. |
oh | Specifies the Oracle home directory to use instead of the default directory. |
opatch_post_end | Marks the end of the post options. This command-line argument is used with the post command-line argument. If this argument is not used, then everything after post is passed into post . |
opatch_pre_end | Marks the end of the pre options. This command-line argument is used with the pre command-line argument. If this argument is not used, then everything after pre is passed into pre . |
ph | Specifies the valid patch directory area. The utility will use the command types found in the patch directory to identify which commands are used for the current operating system. |
post | Specifies the parameters to be passed inside the post script besides the standard parameters. |
pre | Specifies the parameters to be passed inside the pre script besides the standard parameters. |
retry | Specifies how many times the OPatch utility should try in case of an inventory lock failure. |
silent | Suppresses user interaction, and defaults any answers to 'yes.' |
verbose | Prints output to the screen as well as to the log file. |
Oracle Application Server Latest Version
I.6.2.5 version Option
Oracle Application Server Version For Windows 10
The
version
option shows the current version number of the OPatch utility. The following syntax is used for this option: