AIX 0506-324 and 0516-1736


Transporting servers from one site to another site is always a painful job. There are a lot of precautions that must be addressed, such as backup, for data and OS partition

A couple of days a go, we moved a server from production data center to our DR site. The process went smoothly, we were able to dismount, pack, unpack and set the machine into its’ new rack without a hitch. The problem starts when the machine was booted up. A couple of logical volumes are not present, one of them host the server’s oracle binaries.

Mounting the file system via smit fs gave out this:

mount: 0506-324 Cannot mount /dev/oraclebase on /oraclebase: A file or directory in the path name does not exist

The LV /dev/oraclebase resides in a vg called appvg, and by the look of it, it’s currently not detected on the server. So I went to /dev to make sure. It didn’t:

wildbeat# cd /dev
wildbeat# ls -la | grep ora
-rw-r--r--    1 oracle   oinstall   10485760 May 22 2014  ora_orc
crw-rw----    1 root     system       24,  3 Feb 23 09:42 roraclebase

But, special file /dev/roraclebase did exist. The output of lsvg -l:

wildbeat# lsvg -l appvg
appvg:
LV NAME             TYPE       LPs     PPs     PVs  LV STATE      MOUNT POINT
loglv00             jfs2log    1       2       2    open/syncd    N/A
fslv00              jfs2       40      80      2    open/syncd    /source
oraclebase          jfs2       80      80      1    closed/syncd  /oraclebase
fslv03              jfs2       400     400     1    closed/syncd  /racbase

Next, to see if the VG is varied on. It did:

wildbeat# lsvg -o
appvg
rootvg

I tried to vary on the vg again, with the following result:

bash-3.00# varyonvg appvg
PV Status:      hdisk2  00cfd4533960ce20        PVACTIVE
                hdisk3  00cfd4533962114a        PVACTIVE
0516-1736 varyonvg: Unable to determine if the volume group contains an active paging space

So something happened, perhaps during shutdown process that caused ODM data to become out of sync with the VGDA, VGSA, and LVCB. To do  that, do:

synclvodm -vP appvg

If it works, output should be similar to this:

wildbeat# synclvodm -vP appvg
synclvodm: Physical volume data updated.
synclvodm: Logical volume loglv00 updated.
synclvodm: Logical volume fslv00 updated.
synclvodm: Logical volume oraclebase updated.
synclvodm: Logical volume fslv03 updated.

Varyon the vg again:

bash-3.00# varyonvg appvg
bash-3.00#

It should not report any error, and try to mount the LV again:

mount /dev/oraclebase /oraclebase
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s