Login to support.oracle.com
Go to Patches & updates tab
Enter Patch Number 13390677 and select Platform
Click search
Download
File 1&2 is db, 3 is grid, 4 is client, 5 is gateway, 6 is example, 7 is deinstall
Login to support.oracle.com
Go to Patches & updates tab
Enter Patch Number 13390677 and select Platform
Click search
Download
File 1&2 is db, 3 is grid, 4 is client, 5 is gateway, 6 is example, 7 is deinstall
While running the RCU, below error comes if the database is not configured to use the AL32UTF8 character set -

In order to change the character set in the database, follow the next steps.
1. Open SQLplus and login using a sysdba role
2. One by one, execute the next statements.
shutdown immediate; startup restrict; alter database character set internal_use AL32UTF8; alter database character set AL32UTF8; shutdown immediate; startup;
3. Exit SQL Plus
If getting any of the below error in log–
<Critical> <Security> <BEA-090402>
<Authentication denied: Boot identity not valid; The user name and/or
password from the boot identity file (boot.properties) is not valid.
Caused By: javax.security.auth.login.FailedLoginException:
[Security:090304]Authentication Failed: User weblogic
javax.security.auth.login.FailedLoginException: [Security:090302]Authentication
Failed: User weblogic denied
<Critical> <WebLogicServer> <BEA-000386>
<Server subsystem failed. Reason:
weblogic.security.SecurityInitializationException: Authentication denied: Boot
identity not valid; The user name and/or password from the boot identity file
(boot.properties) is not valid.
Authentication denied: Boot identity not valid
Then check the boot.properties file under security folder and data/nodemanager folder if they have been changed recently, edit boot.properties and change the password.
Boot.properties location –
/<MiddlewareHome>/user_projects/domains/bifoundation_domain/servers/AdminServer/security/boot.properties
/<MiddlewareHome>/user_projects/domains/bifoundation_domain/servers/bi_server1/security/boot.properties
Backup and remove ldap folder from -
/<MiddlewareHome>/user_projects/domains/bifoundation_domain/servers/bi_server1/data/
=========================================================================
Stop services
=========================================================================
---------------------------------Step 1 Stop OPMN Components-----------
If its a clustered environment then stop opmnctl in all nodes.
cd /<MiddlewareHome>/instances/instance1/bin
./opmnctl stopall
(wait until the prompt is back)
--------------------------------Step 2 Stop Node Manager---------------
If its a clustered environment then kill the process in all nodes.
ps -ef |grep NodeManager
kill -9 <number of process above>
--------------------------------Step 3 Stop Managed Server---------------
cd /<MiddlewareHome>/user_projects/domains/bifoundation_domain/bin/
./stopManagedWebLogic.sh <bi server name>
eg.- ./stopManagedWebLogic.sh bi_server1
If its a clustered environment -
./stopManagedWebLogic.sh bi_server1 t3://weblogic.hostServerNname:7001
./stopManagedWebLogic.sh bi_server2 t3://weblogic.hostServerName:7001
If boot.properties are not set then provide user and password in the argument -
./stopManagedWebLogic.sh bi_server1 t3://obieenode1.com:7001 weblogic password
./stopManagedWebLogic.sh bi_server2 t3://obieenode1.com:7001 weblogic password
Verify that the Managed Server has shutdown completely in both nodes with -
ps -ef | grep bi_server1
ps -ef | grep bi_server2
-------------------------Step 4 Stop Admin Server------------------
Only in node1-
cd /<MiddlewareHome>/user_projects/domains/bifoundation_domain/bin/
./stopWebLogic.sh
If boot.properties are not set then provide user and password in the argument -
./stopWebLogic.sh weblogic password t3://obieenode1.com:7001
(wait until the prompt is back)
------------------------Kill any running processes----------------------------
Check if any process is running in all nodes.
ps -ef | grep -v grep | grep -i weblogic.NodeManager
ps -ef | grep Node | grep nodemanager | grep -v grep | cut -c10-15
ps -ef | grep AdminServer
=========================================================================
Start Services
=========================================================================
-------------------------Step 1 Start Admin Server------------------
only on node1 -
cd /<MiddlewareHome>/user_projects/domains/bifoundation_domain/bin/
nohup ./startWebLogic.sh &
tail -1000f nohup.out
or - log path can be provided -
nohup ./startWebLogic.sh > /service_logs_path/startWeblogic.log 2>&1 &
tail -1000f /service_logs_path/startWeblogic.log
or - if boot.properties are not set then provide user and password in the argument -
nohup ./startWebLogic.sh -Dweblogic.management.username=weblogic -Dweblogic.management.password=password > /service_logs_path/startWeblogic.log 2>&1 &
tail -1000f /service_logs_path/startWeblogic.log
Output -
<WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
--------------------------------Step 2 StartNode Manager---------------
If its a clustered environment then run on all nodes.
cd /<MiddlewareHome>/wlserver_10.3/server/bin/
nohup ./startNodeManager.sh &
tail -1000f nohup.out
or - log path can be provided -
nohup ./startNodeManager.sh > /service_logs_path/startNodeManager.log 2>&1 &
tail -1000f /service_logs_path/startNodeManager.log
Output -
<Info> <Secure socket listener started on port ####>
-----------------------------------Step 3 Start Managed Server------------
cd /<MiddlewareHome>/user_projects/domains/bifoundation_domain/bin/
nohup ./startManagedWebLogic.sh bi_server1 &
tail -1000f nohup.out
or - log path can be provided -
nohup ./startManagedWebLogic.sh bi_server1 > /service_logs_path/startManagedWebLogic.log 2>&1 &
tail -1000f /service_logs_path/startManagedWebLogic.log
If its a clustered environment then (obieenode1 is node1_hostname) -
nohup ./startManagedWebLogic.sh bi_server1 t3://obieenode1:7001 &
nohup ./startManagedWebLogic.sh bi_server2 t3://obieenode1:7001 &
nohup -1000f nohup.out
or - if boot.properties are not set then provide user and password in the argument -
nohup ./startManagedWebLogic.sh bi_server1 t3://obieenode1:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=password > /service_logs_path/startManagedWebLogic.log 2>&1 &
nohup ./startManagedWebLogic.sh bi_server2 t3://obieenode1:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=password > /service_logs_path/startManagedWebLogic.log 2>&1 &
nohup -1000f /service_logs_path/startManagedWebLogic.log
Output-
Server started in RUNNING mode
---------------------------------Step 4 Startup OPMN Components-----------
If its a clustered environment then run on all nodes.
cd /<MiddlewareHome>/instances/instance1/bin
./opmnctl startall
Check status -
./opmnctl status
Output -
------------------------------------+-------------------------+----------+---------
ias-component | process-type | pid | status
------------------------------------+-------------------------+----------+---------
coreapplication_obisch1 | OracleBIScheduler~ | xxxx | Alive
coreapplication_obiccs1 | OracleBIClusterCo~ | xxxx | Alive
coreapplication_obips1 | OracleBIPresentat~ | xxxx | Alive
coreapplication_obijh1 | OracleBIJavaHostC~ | xxxx | Alive
coreapplication_obis1 | OracleBIServerCom~ | xxxx | Alive