How to Check Fusion Middleware and WebLogic Component Versions
Fusion Middleware components including WebLogic Server, RCU, and components such as SOA, Identity Management, Portal-Forms-Reports-Discover, and JDeveloper must have concordant versions. This affects configuration, but not installation, and can cause a variety of failures, including ClassDefNotFound exceptions when trying to configure a new domain or managed server.
1.To determine the WebLogic Server version. There are several ways to confirm the version:
Enter this command with the weblogic environment enabled:
$ java weblogic.version
Look in the file Middleware Home/registry.xml, and note the component tag
The exact WLS version can be checked using the following commands:
On Unix:
cat $MW_HOME/wlserver_10.3/.product.properties | grep WLS_PRODUCT_VERSION
On Windows:
type %MW_HOME%\wlserver_10.3\.product.properties | findstr WLS_PRODUCT_VERSION
Use SmartUpdate to check the Product Version:
On Unix:
$MW_HOME/utils/bsu/bsu.sh -view -status=applied -prod_dir=$MW_HOME/wlserver_10.3 | grep ProductVersion
On Windows:
%MW_HOME%\utils\bsu\bsu.sh -view -status=applied -prod_dir=$MW_HOME\wlserver_10.3 | findstr ProductVersion
You should see a result such as this:
ProductVersion: 10.3 MP5
2. For JDeveloper, look in the Middleware Home/registry.xml file for the following:
3. For Fusion Middleware products, use the command Oracle Home/Opatch/opatch lsinventory and note the output:
Installed Top-level Products (2):
Application Server 11g SOA Patchset 11.1.1.3.0
Oracle SOA Suite 11g 11.1.1.2.0
There are 2 products installed in this Oracle Home.
4. For the MDS version, look in the file RCU Home/rcu/log/logdir./mds.log:
REPOS_VERSION CONSTANT VARCHAR2(32) := '11.1.1.56.27' (this is for 11.1.1.3)
To get the schema version from the database, login to the database as sysdba and enter the command as shown (example here for 11.1.1.3):
SQL> select comp_id, comp_name, version from schema_version_registry;
COMP_ID
-----------------------
COMP_NAME
-----------------------
VERSION
-----------------------
IAU
Audit Service
11.1.1.3.0
MDS
Metadata Services
11.1.1.2.0
OID
Oracle Internet Directory
11.1.1.3.0
OIF
Oracle Identity Federation Database Schema
11.1.1.2.0
ORAESS
Enterprise Scheduler Service
11.1.1.2.0
ORASDPLS
SIP Infrastructure Location Service
11.1.1.2.0
ORASDPSDS
SIP Infrastructure Subscriber Data Service
11.1.1.2.0
ORASDPXDMS
Presence
11.1.1.2.0
8 rows selected.
You can also get the schema prefix from the database using the following command:
SQL> select username, created from dba_users order by 2;
USERNAME CREATED
----------------
OE 12-MAY-10
SH 12-MAY-10
BI 12-MAY-10
PM 12-MAY-10
TEST01_MDS 21-JAN-11
TEST01_IAU 21-JAN-11
TEST01_IAU_APPEND 21-JAN-11
TEST01_IAU_VIEWER 21-JAN-11
TEST01_ORAESS 21-JAN-11
ODS 21-JAN-11
ODSSM 21-JAN-11
USERNAME CREATED
----------------------
TEST01_OIF 21-JAN-11
TEST01_ORASDPXDMS 21-JAN-11
TEST01_ORASDPLS 21-JAN-11
TEST01_ORASDPSDS 21-JAN-11
The prefix given in the Repository Creation Utility (RCU) dialog is TEST01.
Fusion Middleware components including WebLogic Server, RCU, and components such as SOA, Identity Management, Portal-Forms-Reports-Discover, and JDeveloper must have concordant versions. This affects configuration, but not installation, and can cause a variety of failures, including ClassDefNotFound exceptions when trying to configure a new domain or managed server.
1.To determine the WebLogic Server version. There are several ways to confirm the version:
Enter this command with the weblogic environment enabled:
$ java weblogic.version
Look in the file Middleware Home/registry.xml, and note the component tag
The exact WLS version can be checked using the following commands:
On Unix:
cat $MW_HOME/wlserver_10.3/.product.properties | grep WLS_PRODUCT_VERSION
On Windows:
type %MW_HOME%\wlserver_10.3\.product.properties | findstr WLS_PRODUCT_VERSION
Use SmartUpdate to check the Product Version:
On Unix:
$MW_HOME/utils/bsu/bsu.sh -view -status=applied -prod_dir=$MW_HOME/wlserver_10.3 | grep ProductVersion
On Windows:
%MW_HOME%\utils\bsu\bsu.sh -view -status=applied -prod_dir=$MW_HOME\wlserver_10.3 | findstr ProductVersion
You should see a result such as this:
ProductVersion: 10.3 MP5
2. For JDeveloper, look in the Middleware Home/registry.xml file for the following:
3. For Fusion Middleware products, use the command Oracle Home/Opatch/opatch lsinventory and note the output:
Installed Top-level Products (2):
Application Server 11g SOA Patchset 11.1.1.3.0
Oracle SOA Suite 11g 11.1.1.2.0
There are 2 products installed in this Oracle Home.
4. For the MDS version, look in the file RCU Home/rcu/log/logdir./mds.log:
REPOS_VERSION CONSTANT VARCHAR2(32) := '11.1.1.56.27' (this is for 11.1.1.3)
To get the schema version from the database, login to the database as sysdba and enter the command as shown (example here for 11.1.1.3):
SQL> select comp_id, comp_name, version from schema_version_registry;
COMP_ID
-----------------------
COMP_NAME
-----------------------
VERSION
-----------------------
IAU
Audit Service
11.1.1.3.0
MDS
Metadata Services
11.1.1.2.0
OID
Oracle Internet Directory
11.1.1.3.0
OIF
Oracle Identity Federation Database Schema
11.1.1.2.0
ORAESS
Enterprise Scheduler Service
11.1.1.2.0
ORASDPLS
SIP Infrastructure Location Service
11.1.1.2.0
ORASDPSDS
SIP Infrastructure Subscriber Data Service
11.1.1.2.0
ORASDPXDMS
Presence
11.1.1.2.0
8 rows selected.
You can also get the schema prefix from the database using the following command:
SQL> select username, created from dba_users order by 2;
USERNAME CREATED
----------------
OE 12-MAY-10
SH 12-MAY-10
BI 12-MAY-10
PM 12-MAY-10
TEST01_MDS 21-JAN-11
TEST01_IAU 21-JAN-11
TEST01_IAU_APPEND 21-JAN-11
TEST01_IAU_VIEWER 21-JAN-11
TEST01_ORAESS 21-JAN-11
ODS 21-JAN-11
ODSSM 21-JAN-11
USERNAME CREATED
----------------------
TEST01_OIF 21-JAN-11
TEST01_ORASDPXDMS 21-JAN-11
TEST01_ORASDPLS 21-JAN-11
TEST01_ORASDPSDS 21-JAN-11
The prefix given in the Repository Creation Utility (RCU) dialog is TEST01.
No comments:
Post a Comment