WebLogic Server Patching 10.3.6 - SU Patch [FMJJ] 26519424

# Weblogic Environment

export MW_HOME=/u01/app/oracle/product/fmw11g

export WLS_HOME=$MW_HOME/wlserver_10.3

export WL_HOME=$WLS_HOME

export JAVA_HOME=/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.41.x86_64

export PATH=$JAVA_HOME/bin:$PATH

Applying Patch Set Updates (PSUs)The patch set updates (PSUs) come with a "README.txt" file that explains how to apply the patches. You should always follow the patch note, but the basic format is typically as follows.Unzip the patch into the correct location.

[oracle@XXXXXXX tmp]$  unzip p26519424_1036_Generic.zip -d $MW_HOME/utils/bsu/cache_dir

Archive:  p26519424_1036_Generic.zip

 extracting: /u01/app/oracle/product/fmw11g/utils/bsu/cache_dir/FMJJ.jar

  inflating: /u01/app/oracle/product/fmw11g/utils/bsu/cache_dir/patch-catalog_25504.xml

  inflating: /u01/app/oracle/product/fmw11g/utils/bsu/cache_dir/README.txt

[oracle@xxxx ]$ ls -l $MW_HOME/utils/bsu/cache_dir

total 165800

-rw-r--r--. 1 oracle oinstall 90860993 Sep 12 15:15 FMJJ.jar

-rw-r--r--. 1 oracle oinstall 78902955 Sep  5 02:08 patch-catalog_25504.xml

-rw-rw-r--. 1 oracle oinstall     8741 Oct 12 04:39 README.txt

[oracle@XXXXXXX cache_dir]$Apply the patch.

$ cd $MW_HOME/utils/bsu

$ [oracle@XXXXXXX bsu]$ ./bsu.sh -install -patch_download_dir=$MW_HOME/utils/bsu/cache_dir -patchlist=FMJJ -prod_dir=$WLS_HOME -log=/tmp/weblogic_patching.log

Exception in thread "Main Thread" java.lang.OutOfMemoryError

Solution : Edit the bsu.cmd and increase the JVM to something like below.

-Xms1024m –Xmx2048m

[oracle@XXXXXXX bsu]$ ./bsu.sh -install -patch_download_dir=$MW_HOME/utils/bsu/cache_dir -patchlist=FMJJ -prod_dir=$WLS_HOME -log=/tmp/weblogic_patching.log

Checking for conflicts...

No conflict(s) detected

Installing Patch ID: FMJJ

..

Result: Success

If you get conflicts, you may have to remove previous patches, before attempting to apply the patch again.

[oracle@xxxxxxxxx bsu]$ ./bsu.sh -install -patch_download_dir=$MW_HOME/utils/bsu/cache_dir -patchlist=FMJJ -prod_dir=$WLS_HOME -log=/tmp/weblogic_patching.log

Checking for conflicts........

Conflict(s) detected - resolve conflict condition and execute patch installation again

Conflict condition details follow:

Patch FMJJ is mutually exclusive and cannot coexist with patch(es): B25A

[oracle@FCISCOSTBAPP1 bsu]$

[oracle@xxxxxxxx bsu]# ./bsu.sh -remove -patchlist=B25A -prod_dir=$WLS_HOME -log=/tmp/weblogic_patching.log
Checking for conflicts......
No conflict(s) detected

Removing Patch ID: B25A.
Result: Success


[oracle@xxxxxxxxx bsu]# ./bsu.sh -install -patch_download_dir=/u01/app/oracle/Middleware/utils/bsu/cache_dir -patchlist=FMJJ -prod_dir=/u01/app/oracle/Middleware/wlserver_10.3/ -log=/tmp/weblogic_patching.log
Checking for conflicts......
No conflict(s) detected

Installing Patch ID: FMJJ..
Result: Success

After the patch is successfully applied, restart all WebLogic servers.

Check the version.

[oracle@xxxxxx bsu]$ . $WLS_HOME/server/bin/setWLSEnv.sh

CLASSPATH=/u01/app/oracle/product/fmw11g/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u01/app/oracle/product/fmw11g/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u01/app/oracle/jdk1.8.0_45/lib/tools.jar:/u01/app/oracle/product/fmw11g/wlserver_10.3/server/lib/weblogic_sp.jar:/u01/app/oracle/product/fmw11g/wlserver_10.3/server/lib/weblogic.jar:/u01/app/oracle/product/fmw11g/modules/features/weblogic.server.modules_10.3.6.0.jar:/u01/app/oracle/product/fmw11g/wlserver_10.3/server/lib/webservices.jar:/u01/app/oracle/product/fmw11g/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/u01/app/oracle/product/fmw11g/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:

PATH=/u01/app/oracle/product/fmw11g/wlserver_10.3/server/bin:/u01/app/oracle/product/fmw11g/modules/org.apache.ant_1.7.1/bin:/u01/app/oracle/jdk1.8.0_45/jre/bin:/u01/app/oracle/jdk1.8.0_45/bin:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.41.x86_64/bin:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.41.x86_64/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin

Your environment has been set.

[oracle@xxxxx bsu]$ java weblogic.version

WebLogic Server 10.3.6.0.171017 PSU Patch for BUG26519424 TUE SEP 12 18:34:42 IST 2017

WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050

Use 'weblogic.version -verbose' to get subsystem information

Use 'weblogic.utils.Versions' to get version information for all modules

[oracle@xxxxxx bsu]$

Step by Step - How to Create And Configure RMAN Recovery Catalog Database

Purpose of the Recovery Catalog

A recovery catalog is a database schema used by RMAN to store metadata about one or more Oracle databases. Typically, you store the catalog in a dedicated database. A recovery catalog provides the following benefits:

• A recovery catalog creates redundancy for the RMAN repository stored in the control file of each target database. The recovery catalog serves as a secondary metadata repository. If the target control file and all backups are lost, then the RMAN metadata still exists in the recovery catalog.
• A recovery catalog centralizes metadata for all your target databases. Storing the metadata in a single place makes reporting and administration tasks easier to perform.
• A recovery catalog can store metadata history much longer than the control file. This capability is useful if you must do a recovery that goes further back in time than the history in the control file. The added complexity of managing a recovery catalog database can be offset by the convenience of having the extended backup history available.

Some RMAN features function only when you use a recovery catalog. For example, you can store RMAN scripts in a recovery catalog. The chief advantage of a stored script is that it is available to any RMAN client that can connect to the target database and recovery catalog. Command files are only available if the RMAN client has access to the file system on which they are stored.
A recovery catalog is required when you use RMAN in a Data Guard environment. By storing backup metadata for all primary and standby databases, the catalog enables you to offload backup tasks to one standby database while enabling you to restore backups on other databases in the environment.

Basic Concepts for the Recovery Catalog

The recovery catalog contains metadata about RMAN operations for each registered target database. When RMAN is connected to a recovery catalog, RMAN obtains its metadata exclusively from the catalog. The catalog includes the following types of metadata:

• Datafile and archived redo log backup sets and backup pieces
• Datafile copies
• Archived redo logs and their copies
• Database structure (tablespaces and datafiles)
• Stored scripts, which are named user-created sequences of RMAN commands
• Persistent RMAN configuration settings

Database Registration

The process of enrolling of a database in a recovery catalog for RMAN use is called registration. The recommended practice is to register every target database in your environment in a single recovery catalog. For example, you can register databases prod1, prod2, and prod3 in a single catalog owned by catowner in the database RMANCAT.

Creating a Recovery Catalog

Configuring the Recovery Catalog Database

When you use a recovery catalog, RMAN requires that you maintain a recovery catalog schema. The recovery catalog is stored in the default tablespace of the schema. The SYS user cannot be the owner of the recovery catalog.
Decide which database you will use to install the recovery catalog schema, and also how you will back up this database. Also, decide whether to operate the catalog database in ARCHIVELOG mode, which is recommended.

Steps to Create a RMAN Catalog User

1. Suppose you have create a oracle database or you already have a database created. We are considering RMANCAT as our Recovery Catalog Database. Connect to database RMANCAT as show below. 

• export ORACLE_SID=RMANCAT
  [oracle@ ~]$sys
  
  SQL*Plus: Release 12.2.0.1.0 Production on Tue Oct 31 17:14:17 2017
  
  Copyright (c) 1982, 2016, Oracle.  All rights reserved.
  
  
  Connected to:
  Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
  
  SQL> select name from v$database;
  
  NAME
  ---------
  RMANCAT
   
  

2. Create a tablespace and schema for the recovery catalog.

•  
  SQL> CREATE TABLESPACE RMAN
  DATAFILE '/u02/oradata/RMANCAT/rman01.dbf' SIZE 6208K REUSE
  AUTOEXTEND ON NEXT 64K MAXSIZE 32767M
  EXTENT MANAGEMENT LOCAL
  SEGMENT SPACE MANAGEMENT AUTO;  2    3    4    5
  
  Tablespace created.
  
  SQL> CREATE USER rman IDENTIFIED BY rman
  TEMPORARY TABLESPACE temp
  DEFAULT TABLESPACE rman
  QUOTA UNLIMITED ON rman;  2    3    4
  
  User created.
  
  SQL> GRANT connect, resource, recovery_catalog_owner TO rman;
  
  Grant succeeded.
  
  SQL>
    
  

3. Grant the RECOVERY_CATALOG_OWNER role to the schema owner. This role provides the user with all privileges required to maintain and query the recovery catalog.

•  SQL> grant RECOVERY_CATALOG_OWNER TO rman;  
  

4.  After creating the catalog owner, create the catalog tables with the RMAN CREATE CATALOG command. The command creates the catalog in the default tablespace of the catalog owner.

• [oracle@ ~]$rman catalog=rman/rman@RMANCAT
  
  Recovery Manager: Release 12.2.0.1.0 - Production on Tue Oct 31 18:03:06 2017
  
  Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.
  
  connected to recovery catalog database
  
  RMAN> CREATE CATALOG TABLESPACE "RMAN";
  
  recovery catalog created
  
  RMAN> exit
  
  
  Recovery Manager complete.
  
  

5. You can now connect to the catalog user from sqlplus to check the tables and view names created by the above command.

• 
  [oracle@fcias-oem-01 ~]$sys
  
  SQL*Plus: Release 12.2.0.1.0 Production on Tue Oct 31 18:32:38 2017
  
  Copyright (c) 1982, 2016, Oracle.  All rights reserved.
  
  
  Connected to:
  Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
  
  SQL> conn rman/rman
  Connected.
  SQL>  select * from tab;
  
  

Registering a Database with the REGISTER DATABASE Command

1. The first step in using a recovery catalog with a target database is registering the target database in the recovery catalog. 
2. Start RMAN and connect to a target database and recovery catalog. The recovery catalog database must be open. 

• [oracle@~]$rman target=/ catalog=rman/rman@RMANCAT
  
  Recovery Manager: Release 12.2.0.1.0 - Production on Tue Oct 31 18:30:12 2017
  
  Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.
  
  connected to target database: RMANCAT (DBID=4044589590)
  connected to recovery catalog database
  
  RMAN> 
  

3. Register the target database in the connected recovery catalog. RMAN creates rows in the catalog tables to contain information about the target database, then copies all pertinent data about the target database from the control file into the catalog, synchronizing the catalog with the control file.

• RMAN> REGISTER DATABASE;
  
  database registered in recovery catalog
  starting full resync of recovery catalog
  full resync complete
  
  RMAN>

4. Verify that the registration was successful by running REPORT SCHEMA

•  RMAN> report schema
  2> ;
  
  starting full resync of recovery catalog
  full resync complete
  Report of database schema for database with db_unique_name RMANCAT
  
  List of Permanent Datafiles
  ===========================
  File Size(MB) Tablespace           RB segs Datafile Name
  ---- -------- -------------------- ------- ------------------------
  1    810      SYSTEM               YES     /u02/oradata/RMANCAT/system01.dbf
  3    480      SYSAUX               NO      /u02/oradata/RMANCAT/sysaux01.dbf
  4    230      UNDOTBS1             YES     /u02/oradata/RMANCAT/undotbs01.dbf
  5    8        RMAN                 NO      /u02/oradata/RMANCAT/rman01.dbf
  7    5        USERS                NO      /u02/oradata/RMANCAT/users01.dbf
  
  List of Temporary Files
  =======================
  File Size(MB) Tablespace           Maxsize(MB) Tempfile Name
  ---- -------- -------------------- ----------- --------------------
  1    32       TEMP                 32767       /u02/oradata/RMANCAT/temp01.dbf
  
  RMAN>
  

• 
  

Useful emcli commands in EM Cloud Control 12c

 you to realize useful operation in EM Cloud Control 12c using emcli tool rather than GUI.

You can use emcli when you need to implement batch scripts on your Oracle Management Server (OMS).

• Login to EM

$ emcli login -username=sysman
Enter password :
Login successful

OR

$ emcli login -username=sysman -password=XXXXXX
Login successful

• Synchronize emcli with the OMS

$ emcli sync
Synchronized successfully

• Logout EM

$ emcli logout
Logout successful

• List all the targets already promoted

$ emcli get_targets
Status  Status           Target Type           Target Name
 ID
-9      n/a              group                 OFM
1       Up               host                  xxxdb-prod3.mydomain.com
1       Up               host                  xxxdb-prod2.mydomain.com
1       Up               host                  xxxlgc-prod2.mydomain.com
1       Up               host                  xxxdb-prod1.mydomain.com
1       Up               j2ee_application      /EMGC_GCDomain/GCDomain/EMGC_OMS1/e
                                               mgc
1       Up               j2ee_application      /EMGC_GCDomain/GCDomain/EMGC_OMS1/O
                                               CMRepeater
1       Up               j2ee_application      /EMGC_GCDomain/GCDomain/EMGC_OMS1/e
                                               mpbs
-9      n/a              metadata_repository   /EMGC_GCDomain/GCDomain/EMGC_ADMINS
                                               ERVER/mds-sysman_mds
-9      n/a              metadata_repository   /EMGC_GCDomain/GCDomain/EMGC_ADMINS
                                               ERVER/mds-owsm
1       Up               oracle_apache         /EMGC_GCDomain/instance1/ohs1
1       Up               oracle_apm            /EMGC_GCDomain/GCDomain/EMGC_OMS1/o
                                               racle.security.apm(11.1.1.3.0)
1       Up               oracle_beacon         EM Management Beacon
1       Up               oracle_em_service     EM Console Service
1       Up               oracle_em_service     EM Jobs Service
1       Up               oracle_emd            xxxdb-prod1.mydomain.com:1830
1       Up               oracle_emd            xxxdb-prod3.mydomain.com:1830
1       Up               oracle_emd            xxxlgc-prod2.mydomain.com:3872
1       Up               oracle_emd            xxxdb-prod2.mydomain.com:1830
1       Up               oracle_emrep          Management Services and Repository
-9      n/a              oracle_home           agent12g1_9_xxxlgc-prod2
-9      n/a              oracle_home           WebLogicServer10_3_5_0_0_xxxlgc-pro
                                               d2
-9      n/a              oracle_home           oms12g1_3_xxxlgc-prod2
-9      n/a              oracle_home           webtier12g1_20_xxxlgc-prod2
-9      n/a              oracle_ias_farm       EMGC_GCDomain
1       Up               oracle_oms            xxxlgc-prod2.mydomain.com:4889_Managem
                                               ent_Service
1       Up               oracle_oms_console    xxxlgc-prod2.mydomain.com:4889_Managem
                                               ent_Service_CONSOLE
1       Up               oracle_oms_pbs        xxxlgc-prod2.mydomain.com:4889_Managem
                                               ent_Service_PBS
-9      n/a              weblogic_domain       /EMGC_GCDomain/GCDomain
1       Up               weblogic_j2eeserver   /EMGC_GCDomain/GCDomain/EMGC_OMS1
1       Up               weblogic_j2eeserver   /EMGC_GCDomain/GCDomain/EMGC_ADMINSERVER

• Delete a specific target

$ emcli delete_target -name="/wlstest_wlstest/wlstest/myServer_jvm" -type="java_virtual_machine"

• Delete an agent and its targets

$ emcli delete_target -name="xxxlgc-prod2.mydomain.com:3872" -type="oracle_emd" -delete_monitored_targets

• Follow a plugin deployment (on the OMS / on an agent)

-- Oracle Database plugin
$ emcli get_plugin_deployment_status -plugin_id=oracle.sysman.db
-- Oracle Fusion Middleware plugin
$ emcli get_plugin_deployment_status -plugin_id=oracle.sysman.emas
-- My Oracle Support plugin
$ emcli get_plugin_deployment_status -plugin_id=oracle.sysman.mos

• Import an update (for example: a plugin update) into the software library.

$ emcli import_update -file="p14018177_112000_Generic.zip" -omslocal

• Deploy a plugin on the OMS

$ emcli deploy_plugin_on_server -plugin=oracle.sysman.db -sys_password=XXXXX

• Deploy a plugin on EM agent(s)

$ emcli deploy_plugin_on_agent -plugin="oracle.sysman.db"  -agent_names="xxxdb-prod1.mydomain.com:3872;xxxdb-prod2.mydomain.com:3872"

• List available agents in the library

$ emcli get_supported_platforms
Getting list of platforms ...
Check the logs at /home/oracle/agent.log
About to access self-update code path to retrieve the platforms list..
Getting Platforms list ...
-----------------------------------------------
Version = 12.1.0.1.0
 Platform = Linux x86-64
-----------------------------------------------
Version = 12.1.0.1.0
 Platform = Linux x86
-----------------------------------------------
Version = 12.1.0.1.0
 Platform = IBM AIX on POWER Systems (64-bit)
-----------------------------------------------
Version = 12.1.0.1.0
 Platform = Microsoft Windows (32-bit)
-----------------------------------------------
Version = 12.1.0.1.0
 Platform = Microsoft Windows (64-bit)
-----------------------------------------------
Platforms list displayed successfully

• Download an agent from the library (used for agentDeploy.sh script method)

$ emcli get_agentimage -destination=/home/oracle -platform="Microsoft Windows x64 (64-bit)" -version="12.1.0.1.0"
Platform:Microsoft Windows x64 (64-bit)
Destination:/home/oracle
 === Partition Detail ===
Space free : 11 GB
Space required : 1 GB
Check the logs at /home/oracle/get_agentimage_2012-06-11_15-18-09-PM.log
Setting property ORACLE_HOME to:/u02/Middleware/oms
calling pulloneoffs with arguments:/u02/Middleware/oms/u02/softLibrary/32/C0C9BF40C6A36668E0439D33010AE58512.1.0.1.0windows_x64
Check this logs for more information: /u02/Middleware/oms/sysman/prov/agentpush/logs

• Set monitoring credentials for a specific target (example given for an Oracle database instance)

$ emcli set_credential -target_type=oracle_database -target_name="prod1" -credential_set=DBCredsMonitoring -user=sysman -column="Role:SYSDBA;UserName:sys;password:XXXXX" -monitoring

Advertisements