Simple script to move AIX LVs from one VG to another

-
OS -- AIX 5.3

This is a very simple script that can be used to transfer set of AIX logical volumes (LV) from one volume group (VG) to another.

This was used to move all oracle db LVs from one VG to another.

1. List all LVs to be moved in a txt file in the format of "lsvg -l" output.
 [root@BLOGHOST:/vg_move]$lsvg -l datavg | grep -i ora > oracle_lv.txt  

 [root@BLOGHOST:/vg_move]$ cat oracle_lv.txt   
 oracle_home2_lv   jfs2    40   40   1  open/syncd  /oracle  
 oracle_home3_lv   jfs2    32   32   1  open/syncd  /cust  
 fslv02       jfs2    120   120   3  open/syncd  /orahome11g  
 fslv05       jfs2    80   80   1  open/syncd  /orahome  
 nms_temp      jfs2    8    8    1  open/syncd  /ora_temp  
 orahome10gg_2    jfs2    280   280   2  open/syncd  /orahome10_2  
 oradataictpslt_   jfs2    444   444   5  open/syncd  /oradata2  
 oradata1_lv     jfs2    400   400   9  open/syncd  /oradata1  
 oradataicp1_lv   jfs2    400   400   5  open/syncd  /ora  
 fx_orahome     jfs2    32   32   1  open/syncd  /oracle/orahome  
 orr_lv       jfs2    200   200   2  open/syncd  /oracle_home 
This txt file is the input to below script lv_move.sh, which will move the above lvs from datavg (original) to daatvg01 (new). 
 [root@BLOGHOST:/vg_move]$ cat lv_move.sh  
 while read line  
 do  
   name=$line  
   lv=`echo $name | awk '{print $1}'`   
   mp=`echo $name | awk '{print $7}'`    
   j=`echo $mp | sed 's/[/]//g'`  
 #echo "Text read from file - $name testsss $lv"  
 umount $mp > um_status_$j.txt  
 if [ -s um_status_$j.txt ]  
 then  
   echo "umount failed for $j" > umount_failed_log.txt     
 else  
   echo "umount ok for $j" > umount_ok_log.txt   
   cplv -v datavg01 $lv  
 nlv=`lsvg -l datavg01 | awk '{print $1}' | grep -i fslv | tail -1`  
 chfs -a dev=/dev/$nlv -a log=/dev/loglv01 $mp   
 fsck -p /dev/$nlv > fsck_report_$j.log  
 fi  
 done < $1  

 [root@BLOGHOST:/vg_move]$ sh lv_move.sh oracle_lv.txt
Note : This script is an example only, changes will be required for different setup.

Comments

Post a Comment

Popular posts from this blog

ORA-16433: The database or pluggable database must be opened in read/write

-
Image
ORA-16433 is an error returned when a database cannot be opened. This can be a result of multiple conditions including, The inconsistency of the database Physical corruption Loss of dependent files or access issues etc.. More often than not the solution is to recover from available backups, but there can be situations where backups are not available, specially on UAT or Test setups. Although not the ideal scenario, in this type of situation you might want to open the databases even with inconsistency.  In Comes --> _ALLOW_RESETLOGS_CORRUPTION First, if you are in a position to use _ALLOW_RESETLOGS_CORRUPTION=TRUE, that means it has to be a critical moment, and when you come across more ora- errors while you are trying to reopen the databsae, that can be annoying. Note - _ALLOW_RESETLOGS_CORRUPTION=TRUE must only be used after Oracle support confirmation as a last resort. Also make sure to take cold backup before proceeding. Basic steps to be followed to resolve ORA 16433 af...
Read more

Oracle Multitenant - Create new service for PDB using DBMS_SERVICE

-
Image
When an Oracle PDB is created it starts up a default service with the PDB name. For direct connections to    PDB this service can be used. But there are situations where new service name is required in PDB level, common example is after a PDB restoration/clone, in order to enable application connections without changes in connection string. Setting service_names parameter in PDB level is not possible hence it is not an option in multitenant setup. How to create a new PDB service on Oracle 12C Check the current services, here only the default service is running, SQL> show pdbs; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 3 NFACTORPDB READ WRITE NO SQL> select service_id, name, pdb from dba_Services; SERVICE_ID NAME PDB ---------- ---------------------------------------- ---------- 7 nfactorpdb NFACTORPDB SQL> ...
Read more

Wait for unread message on broadcast channel - Blocking Sessions

-
Image
What is Wait for unread message on broadcast channel wait event? Wait for unread message on broadcast channel is a wait event where source destination communication is involved and the database is waiting for a reply from remote party. Mostly this wait is seen related to data pump export (expdp) or import (impdp) operations. Although categorized in idle wait class "Wait for unread message on broadcast channel" can become the blocking session for some other sessions. Common causes for stuck sessions waiting on this wait event includes, Broken databases links, where remote database is not responding. Abnormally killed remote processes causing the sessions to wait. When a session is waiting on "Wait for unread message on broadcast channel" it can become a blocking session for dependent sessions. Most probably these sessions will be waiting on "library cache pin" or related concurrency wait events. The blocking_session column of (g)v$session view...
Read more