This post is more than 5 years old
11 Posts
0
5798
DR test not showing anything (Windows) - what's been missed?
Hi,
Is there any document detailing the steps to bring ASM up on a replicated DR site?
We have our production server block replicating to another site. On the DR side we took a snapshot & presented this snapshot to a server (prod is still replicating blocks to DR, it's just not visible to the snapshot).
I brought the disks online but ASMCMD didn't show anything. I then ran md_restore to retrieve the folder structure.
lsdg/v$asm_disk show disks there but they say the disks are almost completely free. I asked & was told the snapshot hadn't accidentally been emptied (so the 100% free info remains a mystery). Navigating asmcmd shows no files.
The disks are showing as being stamped though.
dba_hba
63 Posts
0
November 4th, 2014 07:00
Get your snapshot refreshed and do not use md_restore. Then repeat the steps I outlined.
Also check out MyOS: Disks shown in asmtool but not in v$asm_disk view on Windows (Doc ID 1069456.1)
Allan
ichakrab
27 Posts
0
October 31st, 2014 07:00
Hi,
Did you create and mount the disk groups ? When you start the ASM instance what is the error message you are getting ? Pls. let us know. If you are getting additional error messages , pls. let us know.
For reference, you may consult the Oracle documentation on ASM here.
Regards,
Indranil
Dird
11 Posts
0
October 31st, 2014 10:00
Hi,
I restored the disk groups from production using md_restore.
The ASM instance has no error message, it lists the disks (by their labels) in v$asm_disk.
However, it says the diskgroups are empty and when you go through ASMCMD the folders (e.g. \datafile) are empty
ichakrab
27 Posts
0
October 31st, 2014 15:00
Hi,
Pls. provide the output of the following sql queries/commands
1) SQL> select path,total_mb,free_mb,name,label,mode_status,state,mount_status from v$asm_disk where rownum < 6;
2) /etc/init.d/oracleasm listdisks
3) md_backup & md_restore (along with the parameter file associated with md_backup)
4) SQL> select * from v$asm_diskgroup;
Regards,
Indranil
Dird
11 Posts
0
November 3rd, 2014 00:00
Hi,
1) is identical to prod except it says like 99% free space.
2) It's Windows
3) md_backup was taken from prod & restored to DR
4) They're the same except different GROUP_NUMBERs and the FREE_MB again (68mb used vs 600gb)
Mike
ichakrab
27 Posts
0
November 3rd, 2014 01:00
Hi,
I was trying to see the file that got generated during md_backup and was used during md_restore.
Can you please try RMAN Level 0 backup and restore in DR. Does it work ?
Regards,
Indranil
dba_hba
63 Posts
0
November 3rd, 2014 01:00
Mike
You do not say which version of Oracle you are using or if it is single instance? There could be a number of thing that are not correctly configured.
Firstly,
The following My Oracle Support: Documents may be of help
Disks shown in asmtool but not in v$asm_disk view on Windows (Doc ID 1069456.1)
Oracle Restart on Windows: How to Reinstall GI + RDBMS Software keeping the ASM disk groups in a 11.2 Grid Infrastructure Standalone Environment (Doc ID 1471405.1)
Lastly
md_backup generates SQL/DDL to recreate an ASM DiskGroup and structure (metadata). md_restore recreates a NEW EMPTY disk group from the SQL - so is behaving as expected.
Allan
dba_hba
63 Posts
1
November 3rd, 2014 02:00
What about in ASMCA? are the disk groups recognised?
Dird
11 Posts
0
November 3rd, 2014 02:00
Hi Allan,
ASM is 11.2.0.3 (11.2.0.0.0 compatibility).
asmtool is showing them labelled as expected. The disks are stamped correctly, the group number's are just different.
asm_diskstring is null, the same as production. amdu doesn't seem to do anything...possibly due to the asm_disktring?
It creates a new disk group? I was under the impression it just creates the folder structure (asmcmd). Otherwise wouldn't you lose the datafiles (making the restore worthless)?
All 5 disks are listed as MOUNTED & AVAILABLE in ASM.
Mike
Dird
11 Posts
0
November 3rd, 2014 03:00
ASCMA looks different compared to prod. It asks for passwords: pasteall.org/pic/show.php?id=79281 (URL, avoiding moderation wait)
I'm a bit confused by it since the ASM instance is already there & I can query the views.
dba_hba
63 Posts
1
November 3rd, 2014 05:00
Where is your original spfile and password file for the ASM instance? They
Sounds like ASMCA is not seeing the ASM instance
Have you set your ORACLE_SID,ORACLE_HOME and PATH before running ASMCA?
Dird
11 Posts
0
November 3rd, 2014 06:00
Also I should note that only the diskgroups are being replicated, none of the Oracle Home content is currently being replicated.
Dird
11 Posts
0
November 3rd, 2014 06:00
Well for DR the password file is in "D:\app\oracle\product\11.2.0.3\grid\database" but the spfile is not and the spfile parameter isn't specified within ASM (it is on prod).
On prod the spfile is in "D:\app\oracle\product\11.2.0\grid\database" but the password file is not.
SID & HOME were set as I can asmcmd / sqlplus. PATH is set as ORA_HOME;GI_HOME;the_rest. This is the same as prod.
I cd'd to GI_HOME/bin and ran the asmca.bat & had the same view as in the screenshot.
dba_hba
63 Posts
0
November 3rd, 2014 07:00
Reply try something like
set ORACLE_SID=+ASM
set ORACLE_HOME=GRID_HOME
sqlplus / as sysasm
-- show asm parameters - asm_diskgroups and asm_diskstring
show parameter asm
-- check for any DG
select name, state from v$asm_diskgroup;
-- assign snapped ASM DG to the ASM instance
alter system set asm_diskgroups =' ',' ',....., ' ' scope = both;
-- mount snapped ASM DG
alter diskgroup ' ' mount;
alter diskgroup ' ' mount;
...
alter diskgroup ' ' mount;
-- check the DG have mounted
select name, state from v$asm_diskgroup;
PS: you might want a fresh snap and don't use md_restore
Let me know how you go and if you have problems I will offer a couple of alternatives but you may want to open a case with support.
Dird
11 Posts
0
November 3rd, 2014 07:00
SQL> show parameter asm
NAME TYPE VALUE
------------------------------------ ----------- ----------------
asm_diskgroups string DATA, LOG, RECO
asm_diskstring string
asm_power_limit integer 1
asm_preferred_read_failure_groups string
This is the same as on prod except asm_diskgroups is in a different order.
v$asm_diskgroup says all 3 groups are MOUNTED.
I assume I don't need to do the rest due to them being "there" & mounted? What does snapped mean?