Sponsored Content
Operating Systems AIX Oracle ASM accidentally messed with my hdisk Post 302524966 by zaxxon on Wednesday 25th of May 2011 08:07:06 AM
Old 05-25-2011
Changes to LVM are written to the ODM and onto the disks. They are permanent and can't be resolved by a reboot. After a reboot your box will not come up again, since you destroyed it's rootvg. It is currently only working, because the programs are in memory.
If there is a mirror set up between hdisk0 and 1, the copy will most probably be destroyed as well.

I guess you have to reinstall or restore a backup of your rootvg.
You simply have to take care with what you do.

Last edited by zaxxon; 05-25-2011 at 09:14 AM.. Reason: removed assumption about raw LVs
 

8 More Discussions You Might Find Interesting

1. Solaris

asm vs disksuite for oracle

I'm running solaris, with solstice disksuite. With other systems, i run veritas volume manager. My dba want to implement ASM with oracle 10g. Is it possible to create volumes with disksuite for ASM. Oracle want a volume name ex: vol1 My question is, what is the best STANDARD solution. ... (5 Replies)
Discussion started by: simquest
5 Replies

2. Red Hat

ORACLE RAC ASM disk question

Perhaps someone here has some experience with this. machine os RHE 4 6 oracle 10g RAC disk is SAN attached clariion. I have presented new disks to the host, so the machine sees all needed LUNS. powermt shows them, they are labeled and i have fdisk'd them. They are visible across all RAC... (5 Replies)
Discussion started by: Eronysis
5 Replies

3. Solaris

Command to format Oracle ASM raw disk

Hi, Can any one please provide the command to format an Oracle Raw Disk in Solaris 10. I have been used the following commands: dd if=/dev/zero of=<raw disk path> Thanks ---------- Post updated at 12:20 PM ---------- Previous update was at 10:11 AM ---------- Well this didn't give... (0 Replies)
Discussion started by: Mack1982
0 Replies

4. Programming

Help on a perl script to connect to oracle ASM as sysdba

I am novice to perl. Can someone guide me on the below query. We have an existing perl script which connects to database to check the disk group status which i wanted to retieve directly from ASM rather than database. This is because, a cluster has more than 4 databases running and a check on... (0 Replies)
Discussion started by: sai_rsk
0 Replies

5. Shell Programming and Scripting

Use perl to connect to Oracle ASM as sysdba

I am novice to perl. Can someone guide me on the below query. We have an existing perl script which connects to database to check the disk group status which i wanted to retieve directly from ASM rather than database. This is because, a cluster has more than 4 databases running and a check on... (1 Reply)
Discussion started by: sai_rsk
1 Replies

6. Solaris

Can we add Oracle ASM in sun cluster3.3 or 4.0 in failover mode

Hi I am new to this forum & oracle DBA also, I would like to know that can we add Oracle ASM in failover mode in sun cluster 3.3 or 4.0 means that if suppose oracle is running along with ASM on node1 & this node went down due to hardware issue then both oracle along with ASM must move to... (1 Reply)
Discussion started by: hb00
1 Replies

7. UNIX for Advanced & Expert Users

Script to automate add/resize datafile in Oracle ASM Storage

Hi all, Could anyone please share ideas or logic on how to automate add/resize datafile in Oracle ASM Storage for Oracle RAC/Single Node databases when any tablespace space alert is trigerred by OEM? Thanks for your help and time on it! Thanks&regards, a1_win Please DON'T use CODE tags... (0 Replies)
Discussion started by: a1_win
0 Replies

8. Solaris

Oracle ASM on Solaris 11.3

Hi Folks, I've just built a Solaris 11.3 server with a number of LDOM's, all good and well and not any serious issues so far. On our older Solaris 10 systems we ran Oracle 11g using ASM disks, these disks were the raw device meta disks and came in very nicely as "/dev/md/rdsk/dnn" all worked... (4 Replies)
Discussion started by: gull04
4 Replies
vxconfigrestore(1M)													       vxconfigrestore(1M)

NAME
vxconfigrestore - restore disk group configuration SYNOPSIS
/etc/vx/bin/vxconfigrestore [-c | -d | -n | -p] [-l directory] {dgname | dgid} DESCRIPTION
The vxconfigrestore utility is used to restore a disk group's configuration information if this has been lost or become corrupted. The disk group whose configuration is to be restore is specified either by name or by ID. Any disks whose private region headers have become corrupted are reinstalled when the disk group configuration is restored. If you choose not to reinstall the VxVM headers for these disks, it may not be possible to restore the disk group. The disk group configuration backup files may have been automatically created by the vxconfigbackupd daemon, or manually by running the vxconfigbackup command. Restoration of a disk group configuration has two stages: precommit and commit. The precommit stage allows you to temporarily load the con- figuration that is to be restored, and examine it using the vxprint utility. At this stage, the disk group configuration is read-only. No permanent changes are written to disk until you choose to commit them. If desired, you can abandon the restore operation at the precommit stage. OPTIONS
-c (Commit) Permanently commits changes to the disks. The restoration must be at the precommit stage for this command to succeed. Volumes are synchronized in the background. For large volume configurations, it may take some time to perform the synchroniza- tion. You can use the vxtask -l list command to monitor the progress of this operation. -d (Decommit) Abandons the restore operation at the precommit stage. -n (Precommit: no installation of VxVM disk header) Loads the disk group configuration at the precommit stage. This option speci- fies that disks whose private region headers have become corrupted are not to be reinstalled. -l directory Specifies a directory other than the default (/etc/vx/cbr/bk) where the backup configuration files are located. -p (Precommit: load) Loads the disk group configuration at the precommit stage. This option specifies that disks whose private region headers have become corrupted are to be reinstalled. The vxprint command can be used to examine the disk group configura- tion. Note: The volumes have not yet been synchronized at this stage. This is the default operation if no option is specified. EXAMPLES
Load the configuration of the mydg disk group from the default directory, and reinstall disks that have corrupted VxVM disk headers: vxconfigrestore -p mydg Load the configuration of the mydg1 disk group from the backup files in the directory /dgbackup/mydg1 without reinstalling any disks that have corrupted private region disk headers: vxconfigrestore -n -l /dgbackup/mydg1 mydg1 Abandon the restoration of the mydg2 disk group at the precommit stage: vxconfigrestore -d -l /dgbackup/mydg2 mydg2 Commit the restoration of the configuration of the mydg disk group from the backup files in the directory /dgbackup/mydg: vxconfigrestore -c -l /dgbackup/mydg mydg FILES
/etc/vx/cbr/bk/dgname.dgid/dgid.dginfo Default location of backup file for disk group information. /etc/vx/cbr/bk/dgname.dgid/dgid.diskinfo Default location of backup file for disk attributes. /etc/vx/cbr/bk/dgname.dgid/dgid.binconfig Default location of backup file for binary configuration copy. /etc/vx/cbr/bk/dgname.dgid/dgid.cfgrec Default location of backup file for configuration records in vxprint -m format. NOTES
A disk group must be restored on the same physical disks as are defined in the configuration backup files. The disk group configuration backup and restore utilities do not save any data in the public region. This includes file system or other application data that is configured within VxVM objects. A shared disk group in a cluster is restored as a private disk group. After the commit phase has completed, you can deport the private disk group and re-import it as a shared disk group. SEE ALSO
vxconfigbackup(1M), vxconfigbackupd(1M) VxVM 5.0.31.1 24 Mar 2008 vxconfigrestore(1M)
All times are GMT -4. The time now is 10:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy