10.3.6.0.7 PSU Patch Application Process while Upgrading 12.2.0 to 12.2.4

10.3.6.0.7 PSU Patch Application Process:

My current weblogic version is 10.3.6 .Which is come by while Installing 12.2.0 Oracle applications.
In my way of upgrading to 12.2.4 I ahve to apply the latest patches to my current weblogic version.

Using the smart update utility is easy to apply the patches on weblogic.

Go to the FMW_HOME/utils/bsu location you will be find bsu.sh file.

Run sh bsu.sh file on vnc server.

Before this step please down load the patch and unzip the patch 17572726 on FMW_FOME/utils/bsu/cache_dir.

1. Remove following patches, they are included in 10.3.6.0.7 
VFS8,D33T,ll4G 

All patches has been removed.Now we are going to apply the main PSU patch.

2. Complete following steps for patch YIJF 

c. Apply patch 13729611 for 10.3.6.0.7 (You must download the 10.3.6.0.7 version for YIJF:13729611) 

Downloaded the latest patch 13729611 and kept in cache_dir folder.

When using the bsu.sh script to install an Oracle WebLogic Server patch, you may receive an out of memory error for either "GC overhead limit" or "Java heap space". In such a case, run the commands shown below (the examples are for UNIX).For any overlay patches we have to change bsu.sh file as below.

MEM_ARGS="-Xms256m -Xmx512m

to

                        MEM_ARGS="-Xms512m -Xmx1024m -XX:+UseParallelGC"


Now Re launch the ./bsu.sh It will prompt the patches information as below.

 Click and Apply BLTG patch which is repalced YIJF .

Now the PSu patch hasbeen applied succesfully.

How to Install EM 12c Agent in Silent Mode using a Response File

Installation Steps:

1. Get the agent image:

login to the OMS_HOME/bin 

Run emcli login to establish a session.

[gridagt@xxxxxx bin]$ ./emcli login -username=sysman -password=welcome123

Login successful

[gridagt@xxxxx bin]$ ./emcli sync

Synchronized successfully

[gridagt@xxxxx bin]$ ./emcli get_supported_platforms

-----------------------------------------------

Version = 12.1.0.4.0

 Platform = Linux x86-64

-----------------------------------------------

Platforms list displayed successfully.

[gridagt@xxxxxx bin]$ ./emcli get_agentimage -destination=/apps/gridagt/agentimage -platform="Linux x86-64" -version=12.1.0.4.0

=== Partition Detail ===

Space free : 22 GB

Space required : 1 GB

Check the logs at /apps/gridagt/OEM12c/12.1.0/gc_inst/em/EMGC_OMS1/sysman/emcli/setup/.emcli/get_agentimage_2015-05-11_10-33-17-AM.log

Downloading /apps/gridagt/agentimage/12.1.0.4.0_AgentCore_226.zip

File saved as /apps/gridagt/agentimage/12.1.0.4.0_AgentCore_226.zip

Downloading /apps/gridagt/agentimage/12.1.0.4.0_PluginsOneoffs_226.zip

File saved as /apps/gridagt/agentimage/12.1.0.4.0_PluginsOneoffs_226.zip

Downloading /apps/gridagt/agentimage/unzip

File saved as /apps/gridagt/agentimage/unzip

Agent Image Download completed successfully.

EM 12c: How to Install EM 12c Agent in Silent Mode using a Response File (Doc ID 1360083.1)

2. Steps to deploy the agent:

• Transfer the downloaded ZIP file to a temporary directory (/tmp) on the destination host where you want to install the Management Agent.

Stop the WF emails after clone.

1) Update the notifications you do not want sent, in the WF_NOTIFICATIONS table.  Check the WF_NOTIFICATIONS table. Records where status = 'OPEN' and mail_status = 'MAIL' are notifications that will have an e-mail notification sent.

SQL> select notification_id, status, mail_status, begin_date from WF_NOTIFICATIONSwhere status = 'OPEN' and mail_status = 'MAIL';   Above script willshow which notifications are waiting to be e-mailed.  
 
To update a notification so that it will not get e-mailed. Set the MAIL_STATUS = 'SENT'. The
mailer will think the e-mail has already been sent and it will not send it again.. (Users can 
still reply to the notification from the worklist page in the applications). 
Example:
update WF_NOTIFICATIONS set mail_status = 'SENT' where mail_status = 'MAIL'; 
OR
update wf_notifications
set mail_status = 'SENT'
where end_date is not null
and status = 'CLOSED'
and MAIL_STATUS = 'MAIL';
 
 
This will update all notifications waiting to be sent by the mailer. 
2. Then run the script wfntfqup.sql to purge the WF_NOTIFICATION_OUT queue and rebuild it with data currently in the WF_NOTIFICATIONS table. This is what purges all notifications waiting in the queue to be sent.  It will then populate the queue with the current data in the wf_notifications table. 
Since you have changed the mail_status = 'SENT" it will not enqueue these messages again.. Only the ones where mail_status = 'MAIL' and status = 'OPEN' will be placed in the WF_NOTIFICATION_OUT queue and sent by the mailer. 


sqlplus apps/apps @$FND_TOP/patch/115/sql/wfntfqup.sql 

SQL*Plus: Release 10.1.0.5.0 - Production on Mon Jun 22 16:10:37 2015

Copyright (c) 1982, 2005, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> @@wfntfqup.sql

PL/SQL procedure successfully completed.

Elapsed: 00:00:03.01

Commit complete.

Elapsed: 00:00:00.00
**** TEMPORARY TABLES / AQs created ****

PL/SQL procedure successfully completed.

Elapsed: 00:00:00.12
**** Messages backed up ****

Commit complete.

Elapsed: 00:00:00.00
**** wfaqback.sql completed,  executing SQLs from wfntfqup

PL/SQL procedure successfully completed.

Elapsed: 00:02:10.21
***  invoking wfaqrenq.sql ******
*** Re-enqueing messages

PL/SQL procedure successfully completed.

Elapsed: 00:00:00.12

Commit complete.

Elapsed: 00:00:00.01
***** Re-enqueue OF Alerts completed *****
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

847889.1 - Stop Workflow Notification Emails During Clone
828812.1 - How To Stop Old Outbound Workflow Notification Email Messages During Clone Activity

562551.1 - Workflow Java Mailer FAQ

Which Table Stores the NEW Test Address 'set override address'?


SQL> select fscpv.parameter_value
from fnd_svc_comp_params_tl fscpt
,fnd_svc_comp_param_vals fscpv
where fscpt.display_name = 'Test Address'
and fscpt.parameter_id = fscpv.parameter_id;

3. Now start the mailer. 

Running the Repository Creation Utility for OPSS

Contents

To create the necessary schemas for your application, you must run the Repository Creation Utility (RCU). You must have a supported OPSS schema before installing Oracle Primavera Prime. See the Tested Configurations document for supported OPSS servers.

To run the RCU:

1. Go to the location where RCU was installed after you ran the fmw_infra_.jar. For example, C:\oracle\Middleware\Oracle_Home\oracle_common\bin.
   • For Windows installations, run rcu.bat
   • For Linux installations, run ./rcu
2. On the Welcome screen, click Next.
   Note: Click Next on each screen to advance to the next step.
3. On the Create Repository screen, choose Create Repository and System Load and Product Load.
4. On the Database Connection Details screen, enter the following details for the OPSS Schema:
   • Database Type: Select the Oracle Database.
   • Host Name: The host name or the server IP address of the database server.
   • Port: A unique port number for the database schema.
   • Service Name: The global database name. For example, orcl.us.oracle.com.
   • Username: The username for a user with DBA privileges who can install a schema.
   • Password: The password for the username provided above.
   • Role: Role of the user who will be creating the OPSS schema. Select any of the following:
     SYSDBA: A user role with database administration privileges.
     Normal: A database user with no database administration privileges
5. On the Select Components screen:
   1. Choose whether to use an existing or new prefix. Make a note of the prefix you choose.
   2. In the Components section, select Metadata Services and Oracle Platform Security Services.
6. On the Schema Passwords screen, choose a method for handling your passwords. Make note of the password you use.
7. On the Map Tablespaces screen, keep the defaults or choose different tablespace names. Make notes of your selections.
8. On the Summary screen, review your selected installation options and click Create.
9. When the wizard is finished, click Close.

Weblogic 12c (12.1.3.0.0) Admin and Nodemanager Issues

Installed weblogic12c(12.1.3.0.0) succesfully.

After installation I got many erros like not starting the Admin Server Then after NodeManger etc.
Here am giving the solutions for Admin Server issues:
installed weblogic on non SSL mode.
Check The config.xml file as always when the Admin server is not coming up.
I changed the couple of parameters in config.xml
cd $DOMAIN_HOME/config
configCache  config.lok  config.xml  config.xml_back  deployments  diagnostics  jdbc  nodemanager  security  startup
 10.1.11.104 ,update from hostname to IP Address as I Installed this on VM.
After this cahnge am able to start my Admin server.
After launch teh Admin server my cpnsole page take huge time to open like after 45 min my login page appeared .For this issue we  added JAVA_OPTIONS in domain.env file as below.
JAVA_OPTIONS="${JAVA_OPTIONS} -Djava.security.egd=file:/dev/./urandom"
export JAVA_OPTIONS
 in setDomainEnv.sh file.
Then after bounce the Admin server it works as expected.
2)Node Manager  startup issue.
The same way nodemanger will coming for after 20 min when I executed the start command.
JAVA_OPTIONS="${JAVA_OPTIONS} -Djava.security.egd=file:/dev/./urandom"
export JAVA_OPTIONS
Added in startNodeManager.sh
Issue has been resolved.
3)Domain Servers are not coming up through command prompat or console.
This is struggled a lot,Many ways I tried to resolved ,but lastly I amnged to startup from both the ways adding below parameters.
-Dweblogic.management.discover=false -Dweblogic.management.server=${ADMIN_URL} First I added above parameter in startManagedWebLogic.sh which will start domain servers. I am succed on this .Then after the same parameters passed specifically in created Manged servers through console.
 login to console:
go to Enviornments>servers> WLS_1
go to server start tab and add in Argument column abvoe parameters.
And try to start the  services through console.It will come up with out any issue.
Please contact me if any .

ASM views

View	Description
V$ASM_ALIAS	In an ASM instance, contains one row for every alias present in every disk group mounted by the ASM instance. In a DB instance, contains no rows.
V$ASM_ATTRIBUTE	Displays one row for each attribute defined. In addition to attributes specified by CREATEDISKGROUP and ALTERDISKGROUPstatements, the view may show other attributes that are created automatically. Note that attributes are only displayed for disk groups where COMPATIBLE.ASM is set to 11.1 or higher.
V$ASM_CLIENT	In an ASM instance, identifies databases using disk groups managed by the ASM instance. In a DB instance, contains information about the ASM instance if the database has any open ASM files.
V$ASM_DISK	In an ASM instance, contains one row for every disk discovered by the ASM instance, including disks that are not part of any disk group. In a DB instance, contains rows only for disks in the disk groups in use by that DB instance. This view performs disk discovery every time it is queried.
V$ASM_DISK_IOSTAT	Displays information about disk I/O statistics for each ASM client. In a DB instance, only the rows for that instance are shown.
V$ASM_DISK_STAT	In an ASM instance, contains the same columns as V$ASM_DISK, but to reduce overhead, does not perform a discovery when it is queried. It does not return information about any disks that are new to the storage system. For the most accurate data, useV$ASM_DISK instead.
V$ASM_DISKGROUP	In an ASM instance, describes a disk group (number, name, size related info, state, and redundancy type). In a DB instance, contains one row for every ASM disk group mounted by the local ASM instance. This view performs disk discovery every time it is queried.
V$ASM_DISKGROUP_STAT	In an ASM instance, contains the same columns asV$ASM_DISKGROUP, but to reduce overhead, does not perform a discovery when it is queried. It does not return information about any disks that are new to the storage system. For the most accurate data, use V$ASM_DISKGROUP instead.
V$ASM_FILE	In an ASM instance, contains one row for every ASM file in every disk group mounted by the ASM instance. In a DB instance, contains no rows.
V$ASM_OPERATION	In an ASM instance, contains one row for every active ASM long running operation executing in the ASM instance. In a DB instance, contains no rows.
V$ASM_TEMPLATE	In an ASM or DB instance, contains one row for every template present in every disk group mounted by the ASM instance.

Online Patching on 11gR2

In 11g R2 new feature is added Online patching.

OPatch - How are Online Patches Installed?

OPatch is the recommended (Oracle-supplied) tool that customers are supposed to use in order to apply or rollback patches. It maintains an inventory of patches, and ensures that two conflicting patches are not simultaneously installed. OPatch was recently modified to support online patches, which means that it can apply/rollback online patches, as well as detect conflicts between any two kinds of patches. As such, it is not necessary for customers to execute the "oradebug patch" commands; OPatch does this.

All OPatch versions after 11.1.0.6 are Online Patch aware.

The syntax to install an Online Patch is:

opatch apply online -connectString :::

example:

$ opatch apply online -connectString db11202:sys:oracle -invPtrLoc /u01/app/oracle/product/11.2.0/dbhome_1/oraInst.loc
Invoking OPatch 11.2.0.1.4

Oracle Interim Patch Installer version 11.2.0.1.4
Copyright (c) 2010, Oracle Corporation. All rights reserved.


Oracle Home : /u01/app/oracle/product/11.2.0/dbhome_1
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/11.2.0/dbhome_1/oraInst.loc
OPatch version : 11.2.0.1.4
OUI version : 11.2.0.2.0
OUI location : /u01/app/oracle/product/11.2.0/dbhome_1/oui
Log file location : /u01/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/opatch2011-01-27_16-14-21PM.log

Patch history file: /u01/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/opatch_history.txt


The patch should be applied/rolled back in '-all_nodes' mode only.
Converting the RAC mode to '-all_nodes' mode.
ApplySession applying interim patch '10188727' to OH '/u01/app/oracle/product/11.2.0/dbhome_1'

Running prerequisite checks...
Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit http://www.oracle.com/support/policies.html for details.
Email address/User Name:

You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: y

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.

Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '10188727' for restore. This might take a while...
Backing up files affected by the patch '10188727' for rollback. This might take a while...

Patching component oracle.rdbms, 11.2.0.2.0...
The patch will be installed on active database instances.
Installing and enabling the online patch 'bug10188727.pch', on database 'db11202'.

ApplySession adding interim patch '10188727' to inventory

Verifying the update...
Inventory check OK: Patch ID 10188727 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 10188727 are present in Oracle Home.

OPatch succeeded.

For RAC you can list all of the instances:

opatch apply online -connectString :::,:::,...

The USERNAME and PASSWORD are those of a user that has SYSDBA privileges.
The USERNAME and PASSWORD can be left blank if the OS user applying the patch has the SYSDBA privilege.
To apply a patch only to local in the RAC environment, it is necessary to use '-loca

How are Online Patches rollback'ed?

Using "opatch" you can rollback the patch

opatch rollback -id -connectString :::,:::, ...

The USERNAME and PASSWORD are those of a user that has SYSDBA privileges. The USERNAME and PASSWORD can be left blank if the OS user applying the patch has the SYSDBA privilege. Also the NODE is optional if the patch is being applied locally.
Using opatch does not remove the patch, it simply disables it (rolls it back) and removes the patch entry from the inventory. This behavior may change in the future.

Example:

$ opatch rollback -id 10188727 -connectString db11202:sys:oracle -invPtrLoc /u01/app/oracle/product/11.2.0/dbhome_1/oraInst.loc
Invoking OPatch 11.2.0.1.4

Oracle Interim Patch Installer version 11.2.0.1.4
Copyright (c) 2010, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/app/oracle/product/11.2.0/dbhome_1
Central Inventory : /u01/app/oraInventory
   from           : /u01/app/oracle/product/11.2.0/dbhome_1/oraInst.loc
OPatch version    : 11.2.0.1.4
OUI version       : 11.2.0.2.0
OUI location      : /u01/app/oracle/product/11.2.0/dbhome_1/oui
Log file location : /u01/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/opatch2011-01-27_16-21-59PM.log

Patch history file: /u01/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/opatch_history.txt

RollbackSession rolling back interim patch '10188727' from OH '/u01/app/oracle/product/11.2.0/dbhome_1'

The patch should be applied/rolled back in '-all_nodes' mode only.
Converting the RAC mode to '-all_nodes' mode.

Running prerequisite checks...

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.

Backing up files affected by the patch '10188727' for restore. This might take a while...

Patching component oracle.rdbms, 11.2.0.2.0...
The patch will be removed from active database instances.
Disabling and removing online patch 'bug10188727.pch', on database 'db11202'

RollbackSession removing interim patch '10188727' from inventory

OPatch succeeded.