Apply Siebel Server Patch-Set

Product	Siebel CRM
Product Version	8.1.1.11 [IP2013]
Operating System	Oracle Solaris on SPARC (64-bit)

   Patch-Set Version:- 8.1.1.11.17

1. Set Required Parameter

ORACLE_HOME=/u01/SBA_81

2. Copy Patch-Set

Patch_Location='/u01/PS/Siebel_Enterprise_Server'

3. Check Existing Version

cd /u01/SBA_81/Opatch

./opatch lsinventory -details -invPtrLoc /u01/app/oraInventory/oraInst.loc

4. Apply Patch

./opatch apply <Patch_Location> -invPtrLoc /u01/app/oraInventory/oraInst.loc

5. Remove Patch

./opatch rollback -id 8111117

Copying / Cloning a Siebel Object Manager

1.    Connect to srvrmgr command prompt

cd /u01/SBA_81/siebsrvr
. ./siebenv.sh
./srvrmgr -g Gateway -e SBA_81 -s Siebserver  -u username -p  password

2.    Copying/Deleting vanilla object manager

copy compdef from SCCObjMgr_enu to SCCObjMgrOUI_enu

delete component definition SCCObjMgrOUI_enu

3.    Activating/Deactivating new object manager

activate component definition SCCObjMgrOUI_enu

deactivate component definition SCCObjMgrOUI_enu

4.       Setting Env variable:- Exit from srvrmgr and set flag before Sync

export SIEBEL_DEBUG_FLAGS=16

5.    Syncing component

srvrmgr -g Gateway -e SBA_81 -s Siebserver  -u username -p  password
Sync comps

6.       Object Managers parameter setting:- First Restart Siebel Server and Gateway, then change required parameter of new component

change param MaxTasks=20,CFGTempDir="/u01/SBA_81/siebsrvr/temp",CFGClientRootDir="/u01/SBA_81/siebsrvr",CFGApplicationName="Siebel Universal Agent" for compdef SCCObjMgrOUI_enu

change param CFGApplicationSplashText="Siebel Call Center",CFGApplicationTitle="Siebel Call Center",FileSystem="/u01/SBA_81/Siebfs" for compdef SCCObjMgrOUI_enu

change param MaxMTServers=1,MinMTServers=1,SecAdptMode="LDAP",SecAdptName="LDAPSecAdpt",ConfigFile="uagentdboui.cfg",EnableOpenUI="True" for compdef SCCObjMgrOUI_enu

Apply BIP Patch

To check Current Applied BIP Patch
cd /u01/BIP_11g/wlserver_10.3/server/bin
./setWLSEnv.sh
cd /u01/BIP_11g/utils/bsu
./bsu.sh -prod_dir=/u01/BIP_11g/wlserver_10.3  -status=applied -verbose -view

Output Like:-
sadmin@Server_name:/u01/BIP_11g/utils/bsu$ ./bsu.sh -prod_dir=/u01/BIP_11g/wlserver_10.3  -status=applied -verbose -view
ProductName:       WebLogic Server
ProductVersion:    10.3 MP5
Components:        WebLogic Server/Core Application Server,WebLogic Server/Admi
                   nistration Console,WebLogic Server/Configuration Wizard and
                   Upgrade Framework,WebLogic Server/Web 2.0 HTTP Pub-Sub Serve
                   r,WebLogic Server/WebLogic SCA,WebLogic Server/WebLogic JDBC
                    Drivers,WebLogic Server/Third Party JDBC Drivers,WebLogic S
                   erver/WebLogic Server Clients,WebLogic Server/WebLogic Web S
                   erver Plugins,WebLogic Server/UDDI and Xquery Support,WebLog
                   ic Server/Evaluation Database,WebLogic Server/Workshop Code
                   Completion Support
BEAHome:           /u01/BIP_11g
ProductHome:       /u01/BIP_11g/wlserver_10.3
PatchSystemDir:    /u01/BIP_11g/utils/bsu
PatchDir:          /u01/BIP_11g/patch_wls1035
Profile:           Default
DownloadDir:       /u01/BIP_11g/utils/bsu/cache_dir
JavaVersion:       1.6.0_24
JavaVendor:        Sun


Patch ID:          L5TD
PatchContainer:    L5TD.jar
Checksum:          1472039350
Severity:          optional
Category:          General
CR/BUG:            16088411
Restart:           true
Description:       WLS PATCH SET UPDATE 10.3.5.0.7
WLS PATCH SET UPDATE 10.3.5.0.7

To Install/Uninstall any patch:-

Install

 ./bsu.sh -prod_dir=/u01/BIP_11g/wlserver_10.3 -patchlist=RVBS -verbose -install

Uninstall

./bsu.sh -prod_dir=/u01/BIP_11g/wlserver_10.3 -patchlist=RVBS -verbose -remove

BIP 11G Security Patching

1.   Stop BIP and webLogic server from Weblogic Console

            http://SERVER_NAME:7001/console

            To check if any service is still running use below command and kill it if available

ps –ef | grep BI or ps –ef| grep weblogic

Kill -9 <PID>

2.   Take backup of BIP File System before patching:-Make a copy of above folders “user_projects” and “wlserver_10.3”

cp –rp  /u01/BIP_11g/user_projects  /u01/BIP_11g/user_projects_`date +%d.%m.%Y`

cp –rp /u01/BIP_11g/wlserver_10.3  /u01/BIP_11g/wlserver_10.3_`date +%d.%m.%Y`

3.   Get Patch Set Files: - You can get particular/latest patch from:

a.    Download the patch 16088411 for 10.3. from My Oracle Support (MOS). For more details, please refer to Master Note: How to Locate and Download Patches for WebLogic Server Using My Oracle Support Note 1302053.1.

b.    Copy from backup Location

4.   Extract the contents from the zip file: If you are downloading it from oracle Support, you will have a jar file and patch-catalog_xxx.xml. A readme file may also be included.

5.   Copy Patch Files: - move L5TD.jar and the patch-catalog.xml from the zip file to the target machine.

To take backup,Rename cache_dir folder

mv /u01/BIP_11g/utils/bsu/cache_dir /u01/BIP_11g/utils/bsu/cache_dir_`date +%d.%m.%Y`

Copy the files to cache_dir

scp -rp sadmin@SERVER_NAME:/u01/DR_Installables/Installers/BIP_SPARC_11g/p16088411_1035_Generic /u01/BIP_11g/utils/bsu/cache_dir

6.   Check applied patches as below:- If any patch is already applied, then fist remove patch then install latest patch.

cd /u01/BIP_11g/wlserver_10.3/server/bin

./setWLSEnv.sh

cd /u01/BIP_11g/utils/bsu

./bsu.sh -prod_dir=/u01/BIP_11g/wlserver_10.3 -status=applied -verbose –view

 Output:-

As per output, SFAP is already applied. Therefore, you have to remove this patch. To remove patch use below command:-

./bsu.sh -prod_dir=/u01/BIP_11g/wlserver_10.3 -patchlist=SFAP -verbose -remove

7.   Run the command to install a new patch:

./bsu.sh -prod_dir=/u01/BIP_11g/wlserver_10.3 -patchlist=L5TD -verbose -install

8.   Run command to check if the patch is installed:

./bsu.sh -prod_dir=/u01/BIP_11g/wlserver_10.3 -status=applied -verbose -view

9.   Cache Clear: - Clear cache by taking backup of tmp and cache file:

bi_server1

mv /u01/BIP_11g/user_projects/domains/bifoundation_domain/servers/bi_server1/tmp  /u01/BIP_11g/user_projects/domains/bifoundation_domain/servers/bi_server1/tmp_`date +%d.%m.%Y`

mv /u01/BIP_11g/user_projects/domains/bifoundation_domain/servers/bi_server1/cache  /u01/BIP_11g/user_projects/domains/bifoundation_domain/servers/bi_server1/cache_`date +%d.%m.%Y`

AdminServer

mv /u01/BIP_11g/user_projects/domains/bifoundation_domain/servers/AdminServer/tmp  /u01/BIP_11g/user_projects/domains/bifoundation_domain/servers/AdminServer/tmp_`date +%d.%m.%Y`

mv /u01/BIP_11g/user_projects/domains/bifoundation_domain/servers/AdminServer/cache  /u01/BIP_11g/user_projects/domains/bifoundation_domain/servers/AdminServer/cache_`date +%d.%m.%Y`

10.   Restart WebLogic Server: - login to VNC viewer with sadmin and execute below commands in separate terminals

             To Start Weblogic Admin Console

          cd /u01/BIP_11g/user_projects/domains/bifoundation_domain/bin

 ./startWebLogic.sh   

To Start Node Manager

           cd /u01/BIP_11g/wlserver_10.3/server/bin

          ./startNodeManager.sh

11.    Start BI Publisher Server

         Login to WebLogic Console and start bi_server1

         http://SERVER_NAME:7001/console

12.    Access BIP link, it should be up and running

         http://SERVER_NAME:9704/xmlpserver

Complete Life-cycle of mounting drive in Unix

1.       Login with root user in source machine and check if drive is ready to be shared

root@localhost:/u01# share

Output: - it will show all shared drive. If there is no drive to be shared then cursor will move to next line

2.       Run below command to share drive to mount on destination machine

root@localhost:/u01# share -F nfs /u01/SBA_81

Output: - It will share drive on source machine

3.       Check if drive is available to mount

root@localhost:/u01# share

Output: - it will show shared device as below:-

u01_SBA_81      /u01/SBA_81     nfs     sec=sys,rw

4.       Login with root user in destination machine and create directory to mount

root@localhost:/u01# mkdir mount_point

Output: It will create directory in folder /u01

5.       Mount source directory on destination machine as below:-

root@localhost:/u01# mount -F nfs Source_IP:/u01/SBA_81 /u01/mount_point

Output: - it will mount required drive to destination server. Check if all folders and files are visible in mounted directory.

6.       To Un-Mount any mounted directory use below command

root@localhost:/u01# umount /u01/mount_point

Output: - It will un-mount drive and you can’t use shared directory anymore.

7.       To Remove created directory use below command

root@localhost:/u01# rmdir /u01/mount_point

Output: - It will delete previously created directory

8.       To un-share any shared directory use below command

root@localhost:/u01# unshare -F nfs /u01/SBA_81

Output: - It will un-share drive on source machine

9.       Finally crosscheck if directory is not accessible anymore

root@localhost:/u01# share

Output: - If there is no drive to be shared then cursor will move to next line

Note: Please find complete screenshot of command execution for reference 

                                                                               

 Best of Luck

RCU Schema Configuration failed with the error “The specified prefix already exists”

Process:

We all know that we need to create RCU schemas before starting OBIEE 11G (In fact, for any Fusion Middleware application) Installation. Because it is the base store for FMW.

Problem:

Recently I came across a scenario where my customer created RCU schemas with Oracle Repository Creation Utility (RCU) version 11.1.1.3.0 and Installed OBIEE 11.1.1.3.0. Now after new OBIEE 11.1.1.5.0 release he wants to upgrade his application from 11.1.1.3.0. But he is not interested at the In-place upgrade. Therefore, we uninstalled weblogic and OBIEE 11.1.1.3.0 and started RCU 11.1.1.3.0 to drop the _BIPLATFORM and _MDS schemas.

The RCU shown up with successful message and so we thought everything is cleaned up and it’s good to create schemas again. I started RCU 11.1.1.5.0 and selected Oracle Business Intelligence component and given prefix as DEV. But am not able to assign this prefix and got a message like “The specified prefix already exists”.  Though I got successful dropped schemas message, just for cross check I looked at database for the DEV_BIPLATFORM and DEV_MDS schemas. There I am not seeing any of them.

Cause:

Then I checked at dropped schemas log generated by RCU and realized that there is an entry in System.SCHEMA_VERSION_REGISTRY$ table which is stopping me to assign the same DEV prefix which we used for earlier version schemas.

Actually, the RCU should drop schemas using mdsschemamanager.pl script. This script has capability to do cascade delete and will delete entries in System.SCHEMA_VERSION_REGISTRY$ table.

To make sure this log into RCU DATABASE as sys and run the following SQL Query:

Select * from System.SCHEMA_VERSION_REGISTRY$;

If this query returns any record then it means the RCU didn’t drop the schemas properly.

Actually what happened in this case is the RCU schemas were not dropped using mdsschemamanager.pl script, it’s just dropped with normal schema delete and the resulting repository record for the schema is not clean. Keep in mind, this is just in case if you want to use same prefix. Otherwise, RCU will let you proceed to create new prefixed Schemas.

If the RCU schemas have been deleted incorrectly using the RCU drop user command, then we need to clean these entries before starting new repository schemas creation.

Solution:

To fix it, run the following SQL*Plus command as sys to complete the removal of the RCU schemas records in the repository database:

delete from System.SCHEMA_VERSION_REGISTRY$;

Once you confirmed there are no entries in System.SCHEMA_VERSION_REGISTRY$ table and start the RCU to create repository schemas with the prefix (DEV in my case). The RCU will go smooth and will not complain with any error.

Hope this helps you in your RCU issues troubleshooting.

 Thanks

OBIEE 11g Installation error : One or more entries are found in HSS_COMPONENT table

 

Oct24by Gaurav Chaudhary

Issue:
While installing OBIEE 11g in a system where OBIEE was previously installed, then uninstalled for any reasons with the same RCU schema, then we got this error. One or more entries are found in HSS_COMPONENT table
Cause:
While installing RCU, two RCU schemas are created BIPLATFORM,MDS. These schemas contain all the configuration tables. OBIEE 11g installation always inserts some data in HSS_COMPONET table. As the data is already present for the previous installation , it is showing this error.
Resolution:
There is no need to delete/uninstall RCU schemas. We can continue OBIEE 11g installation again with the same schema which we have already installed.
Step 1:
Login into SQLPLUS and connect BIPLATFORM Schema with the same credentials which we have given when we installed.
SQL> conn DEV_BIPLATFORM/password@connection_string
Step 2:
Once we connected with BIPLATFORM Schema delete the entry which is available in the HSS_COMPONENT table and commit the table.
SQL> DELETE FROM HSS_COMPONENT;
7-8 entries will deleted.
SQL> COMMIT;
Commit Complete;

Now start the installation and give the BIPLATFORM AND MDS schema details in its related steps. The error will no more exist.

N.B.: Do not forget to ‘COMMIT’ once we deleted the entry from HSS_COMPONENT table because ‘DELETE’ command will not be updated without commit.