Wednesday, August 21, 2024


Editing files with vi


Lesson 1: How to Quit vi

To exit vi without saving changes, hit Escape a couple of times to ensure you are in Normal mode, and then type:
:q!

Lesson 2: Editing with vi

Start vi and press i. The cursor may change shape, and INSERT is displayed at the bottom of the screen (in most vi clones). You are now in insert mode — all your keystrokes are entered into the current buffer and are displayed to the screen.
Hit the Escape key. The cursor changes shape again, and INSERT has disappeared. You are back in Normal mode. Hitting Escape a few times will pretty much always cancel whatever you are doing and return you to Normal mode.
Command mode is also where you move around in the file. On most systems, you can use the arrow keys to move the cursor. If that fails, cursor movement can be accomplished with the hjkl keys:
h   move left one character
j   move down one character
k   move up one character
l   move right one character
vi has its own command line, which you access by typing a colon. Commands typed at the command line will not be executed until you hit Enter, just like in the shell.
Many of the commands that you will use in command mode begin with a colon. For example, the command to quit is :q, as we learned in Lesson 1 above. Actually, in Lesson 1 we added !, which tells vi to “force” the operation. If you have edited the file, typing :q will not immediately exit the program, but instead produce this error message:
E37: No write since last change (add ! to override)
To save your changes, use the :w command (“Write”). You can save and quit all in one go by typing both commands together:
:wq
Of course, if you started vi without giving a file name, you’ll need to provide one. For example, to save your working file as test.txt, you would type:
:w test.txt
Try editing some text now.
  • Start vi
  • Hit i to go to Insert mode.
  • Type some text.
  • Hit Escape to return to Normal mode.
  • Type :w test.txt to save your work
  • Type :q to quit

vi Quick Reference

Movement

hjkl
left, down, up, right
$
To the end of the line
^
To the beginning of the line
G
To the end of the file
:1
To the beginning of the file
:47
To line 47

Editing

dd
Remove a line
5dd
Removing five lines
r
Replace a character
x
Delete a character
5x
Delete 5 characters
u
Undo last action
J
Join current and next lines (Note the capital — hold the Shift key)

Saving and Quitting

:q
Quit
:q!
Quit without saving
:wq
Write and quit
:w
Write (without quitting)
:e!
Reload currently open file from disk
:w test.txt
Write buffer to file test.txt
:e test2.txt
Open file test2.txt

How To Apply/Install Patch Using BSU (bea smart update)?

This Demo Shows How To Apply/Install Patch Using BSU Utility Command 

Line


==> The purpose of applying patch to BEA_HOME OR WLS_HOME Is To Fix Bugs.

==> BSU Utility is shipped with weblogic product 

==> Oracle Releases PSU(Patch Set Update) OR CPU(Critical Patch Update) Patches Quarterly 
(January - April - July - October), As PSU patches Are Cumulative and all bug fixes are available 
hence it is highly recommended to apply psu quarterly   

Summary

  1. Download The PSU From Oracle Support
  2. Create Directory cache_dir inside $MW_HOME/utils/bsu
  3. Copy The Downloaded Patch To $MW_HOME/utils/bsu/cache_dir 
  4. Unzip The Copied Zip Patch File
  5. Set The Environment Using setWLSEnv.sh 
  6. Run The Patch Install Command Using bsu.sh
  7. Verify Whether Patch Applied To The BEA_HOME

1. Download The PSU From Oracle Support

  • Login To My Oracle Support http://support.oracle.com
  • Click on "Patches & Update" Tab
  • Click on Search ==> Click on "Recommended Patch Advisor"
  • Select Product: Oracle Weblogic Server
  • Select Release 10.3.6.0 OR Any of your prefered wls version
  • Platform Select Any
  • Click on Search
  • Result will lists latest available PSU
  • Click on "Patch Name" 20780171
  • Click on Download 

2. Create Directory cache_dir inside $MW_HOME/utils/bsu

      cd /oracle/Middleware1036/utils/bsu/
      mkdir cache_dir

3. Copy The Downloaded Patch To $MW_HOME/utils/bsu/cache_dir Using WinScp

4. Unzip The Copied Zip Patch File

     cd /oracle/Middleware1036/utils/bsu/cache_dir
   
      unzip p20780171_1036_Generic.zip

5. Set The Environment Using setWLSEnv.sh 

     cd /oracle/Middleware1036/wlserver_10.3/server/bin
   
     . ./setWLSEnv.sh

6. Run The Patch Install Command Using bsu.sh

     cd /oracle/Middleware1036/utils/bsu/

     ./bsu.sh -patch_download_dir=/oracle/Middleware1036/utils/bsu/cache_dir -patchlist=EJUW -prod_dir=/oracle/Middleware1036/wlserver_10.3 -install  -log=patch_apply.log -log_priority=trace

7. Verify Whether The Patch Applied To The BEA_HOME is Successfull

      cd /oracle/Middleware1036/utils/bsu

       ./bsu.sh -report -bea_home=/oracle/Middleware1036 -output_file=bsu_report.log

     View the file bsu_report.log. Below Snap Shot Shows That The Patch ID EJUW is applied
  

    OR
    You Can Verify by Checking Admin Server Start up log 
   


COMPLETED

Thursday, March 22, 2018


Apply Siebel Server Patch-Set

Siebel CRM
8.1.1.11 [IP2013]
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

Monday, March 12, 2018

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

            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

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







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