Max of 15 Voting disk ?
Hi All,
Please find the below errors:
./crsctl add css votedisk +DATA
CRS-4671: This command is not supported for ASM diskgroups.
CRS-4000: Command Add failed, or completed with errors.
./crsctl add css votedisk /u01/vote.dsk
CRS-4258: Addition and deletion of voting files are not allowed because the voting files are on ASM #
What I understood is that:
1) It is not possible to put Voting disk in multiple diskgroups as it is for OCR.
2) The Voting disk copy will be created according to the redundnacy of the Diskgroup where it is in.
No I have a couple question based on this:
1) If i create a disk group with external redundnacy , does that menat that I will be having only one voting disk ?I cannot add any more ?
2) Oracle tells that it is possible tor create up to 15 voting disk.
So does that mean that I will be having one voting (total 15) disk on each disk provided that If i have a disk group with normal or high redundnacy and the disk group have 15 disk with disk in its own faliure group
May be I silly here, but if some one can advise me, please
Regards
Joe
Hi Joe,
Jomon Jacob wrote:
Hi All,
Please find the below errors:
./crsctl add css votedisk +DATA
CRS-4671: This command is not supported for ASM diskgroups.
CRS-4000: Command Add failed, or completed with errors.
./crsctl add css votedisk /u01/vote.dsk
CRS-4258: Addition and deletion of voting files are not allowed because the voting files are on ASM #When votedisk is on ASM diskgroup, no add option available. The number of votedisk is determined by the diskgroup redundancy. If more copy of votedisk is desired, one can move votedisk to a diskgroup with higher redundancy.
When votedisk is on ASM, no delete option available, one can only replace the existing votedisk group with another ASM diskgroup.
When votedisk is on ASM the option to be used is replace.
crsctl replace css votedisk +NEW_DGVOTE>
>
What I understood is that:
1) It is not possible to put Voting disk in multiple diskgroups as it is for OCR.Yes.. because Voting file is placed directly on ASMDISK not in a DISKGROUP, although it uses the configuration of a diskgroup (e.g failgroup, asmdisks, and so on).
2) The Voting disk copy will be created according to the redundnacy of the Diskgroup where it is in.When you move (replace) voting file to ASM, Oracle will take configuration of Diskgroup (i.e failgroup) and place one voting file in each ASM DISK in different failgroups.
>
>
No I have a couple question based on this:
1) If i create a disk group with external redundnacy , does that menat that I will be having only one voting disk ?I cannot add any more ?Yes.. with external redundancy you don't have the concept of failgroup because you not use mirror by ASM. So, it's like one failgroup. Then you can have only one Voting file in this Diskgroup.
2) Oracle tells that it is possible tor create up to 15 voting disk.
So does that mean that I will be having one voting (total 15) disk on each disk provided that If i have a disk group with normal or high redundnacy and the disk group have 15 disk with disk in its own faliure groupNo. 15 voting files is allowed if you not storing voting on ASM. If you are using ASM the maximum number of voting files is 5. Because Oracle will take configuration of Diskgroup.
Using high number of voting disks can be useful when you have a big cluster environment with (e.g) 5 Storage Subsystem and 20 Hosts in a single Cluster. You must set up a voting file in each storage ... but if you're using only one storage voting 3 files is enough.
Usage Note
You should have at least three voting disks, unless you have a storage device, such as a disk array, that provides external redundancy. Oracle recommends that you do not use more than 5 voting disks. The maximum number of voting disks that is supported is 15.
http://docs.oracle.com/cd/E11882_01/rac.112/e16794/crsref.htm#CHEJDHFH
See this example;
I configured 7 ASM DISK but ORACLE used only 5 ASM DISK.
SQL> CREATE DISKGROUP DG_VOTE HIGH REDUNDANCY
FAILGROUP STG1 DISK 'ORCL:DG_VOTE01'
FAILGROUP STG2 DISK 'ORCL:DG_VOTE02'
FAILGROUP STG3 DISK 'ORCL:DG_VOTE03'
FAILGROUP STG4 DISK 'ORCL:DG_VOTE04'
FAILGROUP STG5 DISK 'ORCL:DG_VOTE05'
FAILGROUP STG6 DISK 'ORCL:DG_VOTE06'
FAILGROUP STG7 DISK 'ORCL:DG_VOTE07'
ATTRIBUTE 'compatible.asm' = '11.2.0.0.0';
Diskgroup created.
SQL> ! srvctl start diskgroup -g DG_VOTE -n lnxora02,lnxora03
$ crsctl replace votedisk +DG_VOTE
CRS-4256: Updating the profile
Successful addition of voting disk 427f38b47ff24f52bf1228978354f1b2.
Successful addition of voting disk 891c4a40caed4f05bfac445b2fef2e14.
Successful addition of voting disk 5421865636524f5abf008becb19efe0e.
Successful addition of voting disk a803232576a44f1bbff65ab626f51c9e.
Successful addition of voting disk 346142ea30574f93bf870a117bea1a39.
Successful deletion of voting disk 2166953a27a14fcbbf38dae2c4049fa2.
Successfully replaced voting disk group with +DG_VOTE.
$ crsctl query css votedisk
## STATE File Universal Id File Name Disk group
1. ONLINE 427f38b47ff24f52bf1228978354f1b2 (ORCL:DG_VOTE01) [DG_VOTE]
2. ONLINE 891c4a40caed4f05bfac445b2fef2e14 (ORCL:DG_VOTE02) [DG_VOTE]
3. ONLINE 5421865636524f5abf008becb19efe0e (ORCL:DG_VOTE03) [DG_VOTE]
4. ONLINE a803232576a44f1bbff65ab626f51c9e (ORCL:DG_VOTE04) [DG_VOTE]
5. ONLINE 346142ea30574f93bf870a117bea1a39 (ORCL:DG_VOTE05) [DG_VOTE]
SQL >
SET LINESIZE 150
COL PATH FOR A30
COL NAME FOR A10
COL HEADER_STATUS FOR A20
COL FAILGROUP FOR A20
COL FAILGROUP_TYPE FOR A20
COL VOTING_FILE FOR A20
SELECT NAME,PATH,HEADER_STATUS,FAILGROUP, FAILGROUP_TYPE, VOTING_FILE
FROM V$ASM_DISK
WHERE GROUP_NUMBER = ( SELECT GROUP_NUMBER
FROM V$ASM_DISKGROUP
WHERE NAME='DG_VOTE');
NAME PATH HEADER_STATUS FAILGROUP FAILGROUP_TYPE VOTING_FILE
DG_VOTE01 ORCL:DG_VOTE01 MEMBER STG1 REGULAR Y
DG_VOTE02 ORCL:DG_VOTE02 MEMBER STG2 REGULAR Y
DG_VOTE03 ORCL:DG_VOTE03 MEMBER STG3 REGULAR Y
DG_VOTE04 ORCL:DG_VOTE04 MEMBER STG4 REGULAR Y
DG_VOTE05 ORCL:DG_VOTE05 MEMBER STG5 REGULAR Y
DG_VOTE06 ORCL:DG_VOTE06 MEMBER STG6 REGULAR N
DG_VOTE07 ORCL:DG_VOTE07 MEMBER STG7 REGULAR NRegards,
Levi Pereira
Edited by: Levi Pereira on Jan 5, 2012 6:01 PM
Similar Messages
-
OCR and voting disks on ASM, problems in case of fail-over instances
Hi everybody
in case at your site you :
- have an 11.2 fail-over cluster using Grid Infrastructure (CRS, OCR, voting disks),
where you have yourself created additional CRS resources to handle single-node db instances,
their listener, their disks and so on (which are started only on one node at a time,
can fail from that node and restart to another);
- have put OCR and voting disks into an ASM diskgroup (as strongly suggested by Oracle);
then you might have problems (as we had) because you might:
- reach max number of diskgroups handled by an ASM instance (63 only, above which you get ORA-15068);
- experiment delays (especially in case of multipath), find fake CRS resources, etc.
whenever you dismount disks from one node and mount to another;
So (if both conditions are true) you might be interested in this story,
then please keep reading on for the boring details.
One step backward (I'll try to keep it simple).
Oracle Grid Infrastructure is mainly used by RAC db instances,
which means that any db you create usually has one instance started on each node,
and all instances access read / write the same disks from each node.
So, ASM instance on each node will mount diskgroups in Shared Mode,
because the same diskgroups are mounted also by other ASM instances on the other nodes.
ASM instances have a spfile parameter CLUSTER_DATABASE=true (and this parameter implies
that every diskgroup is mounted in Shared Mode, among other things).
In this context, it is quite obvious that Oracle strongly recommends to put OCR and voting disks
inside ASM: this (usually called CRS_DATA) will become diskgroup number 1
and ASM instances will mount it before CRS starts.
Then, additional diskgroup will be added by users, for DATA, REDO, FRA etc of each RAC db,
and will be mounted later when a RAC db instance starts on the specific node.
In case of fail-over cluster, where instances are not RAC type and there is
only one instance running (on one of the nodes) at any time for each db, it is different.
All diskgroups of db instances don't need to be mounted in Shared Mode,
because they are used by one instance only at a time
(on the contrary, they should be mounted in Exclusive Mode).
Yet, if you follow Oracle advice and put OCR and voting inside ASM, then:
- at installation OUI will start ASM instance on each node with CLUSTER_DATABASE=true;
- the first diskgroup, which contains OCR and votings, will be mounted Shared Mode;
- all other diskgroups, used by each db instance, will be mounted Shared Mode, too,
even if you'll take care that they'll be mounted by one ASM instance at a time.
At our site, for our three-nodes cluster, this fact has two consequences.
One conseguence is that we hit ORA-15068 limit (max 63 diskgroups) earlier than expected:
- none ot the instances on this cluster are Production (only Test, Dev, etc);
- we planned to have usually 10 instances on each node, each of them with 3 diskgroups (DATA, REDO, FRA),
so 30 diskgroups each node, for a total of 90 diskgroups (30 instances) on the cluster;
- in case one node failed, surviving two should get resources of the failing node,
in the worst case: one node with 60 diskgroups (20 instances), the other one with 30 diskgroups (10 instances)
- in case two nodes failed, the only node survived should not be able to mount additional diskgroups
(because of limit of max 63 diskgroup mounted by an ASM instance), so all other would remain unmounted
and their db instances stopped (they are not Production instances);
But it didn't worked, since ASM has parameter CLUSTER_DATABASE=true, so you cannot mount 90 diskgroups,
you can mount 62 globally (once a diskgroup is mounted on one node, it is given a number between 2 and 63,
and other diskgroups mounted on other nodes cannot reuse that number).
So as a matter of fact we can mount only 21 diskgroups (about 7 instances) on each node.
The second conseguence is that, every time our CRS handmade scripts dismount diskgroups
from one node and mount it to another, there are delays in the range of seconds (especially with multipath).
Also we found inside CRS log that, whenever we mounted diskgroups (on one node only), then
behind the scenes were created on the fly additional fake resources
of type ora*.dg, maybe to accomodate the fact that on other nodes those diskgroups were left unmounted
(once again, instances are single-node here, and not RAC type).
That's all.
Did anyone go into similar problems?
We opened a SR to Oracle asking about what options do we have here, and we are disappointed by their answer.
Regards
OscarHi Klaas-Jan
- best practises require that also online redolog files are in a separate diskgroup, in case of ASM logical corruption (we are a little bit paranoid): in case DATA dg gets corrupted, you can restore Full backup plus Archived RedoLog plus Online Redolog (otherwise you will stop at the latest Archived).
So we have 3 diskgroups for each db instance: DATA, REDO, FRA.
- in case of fail-over cluster (active-passive), Oracle provide some templates of CRS scripts (in $CRS_HOME/crs/crs/public) that you edit and change at your will, also you might create additionale scripts in case of additional resources you might need (Oracle Agents, backups agent, file systems, monitoring tools, etc)
About our problem, the only solution is to move OCR and voting disks from ASM and change pfile af all ASM instance (parameter CLUSTER_DATABASE from true to false ).
Oracle aswers were a litlle bit odd:
- first they told us to use Grid Standalone (without CRS, OCR, voting at all), but we told them that we needed a Fail-over solution
- then they told us to use RAC Single Node, which actually has some better features, in csae of planned fail-over it might be able to migreate
client sessions without causing a reconnect (for SELECTs only, not in case of a running transaction), but we already have a few fail-over cluster, we cannot change them all
So we plan to move OCR and voting disks into block devices (we think that the other solution, which needs a Shared File System, will take longer).
Thanks Marko for pointing us to OCFS2 pros / cons.
We asked Oracle a confirmation that it supported, they said yes but it is discouraged (and also, doesn't work with OUI nor ASMCA).
Anyway that's the simplest approach, this is a non-Prod cluster, we'll start here and if everthing is fine, after a while we'll do it also on Prod ones.
- Note 605828.1, paragraph 5, Configuring non-raw multipath devices for Oracle Clusterware 11g (11.1.0, 11.2.0) on RHEL5/OL5
- Note 428681.1: OCR / Vote disk Maintenance Operations: (ADD/REMOVE/REPLACE/MOVE)
-"Grid Infrastructure Install on Linux", paragraph 3.1.6, Table 3-2
Oscar -
How to find the max data transfer rate(disk speed) supported by mobo?
I plan on replacing my current HDD with a new and bigger HDD.
For this I need to know the max data transfer rate(disk speed) that my mobo will support. However, dmidecode is not telling me that. Am I missing something?
Here's dmidecode:
# dmidecode 2.11
SMBIOS 2.5 present.
80 structures occupying 2858 bytes.
Table at 0x000F0450.
Handle 0xDA00, DMI type 218, 101 bytes
OEM-specific Type
Header and Data:
DA 65 00 DA B2 00 17 4B 0E 38 00 00 80 00 80 01
00 02 80 02 80 01 00 00 A0 00 A0 01 00 58 00 58
00 01 00 59 00 59 00 01 00 75 01 75 01 01 00 76
01 76 01 01 00 05 80 05 80 01 00 D1 01 19 00 01
00 15 02 19 00 02 00 1B 00 19 00 03 00 19 00 19
00 00 00 4A 02 4A 02 01 00 0C 80 0C 80 01 00 FF
FF 00 00 00 00
Handle 0xDA01, DMI type 218, 35 bytes
OEM-specific Type
Header and Data:
DA 23 01 DA B2 00 17 4B 0E 38 00 10 F5 10 F5 00
00 11 F5 11 F5 00 00 12 F5 12 F5 00 00 FF FF 00
00 00 00
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: A17
Release Date: 04/06/2010
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 4096 kB
Characteristics:
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
EDD is supported
Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
BIOS Revision: 17.0
Handle 0x0100, DMI type 1, 27 bytes
System Information
Manufacturer: Dell Inc.
Product Name: OptiPlex 755
Version: Not Specified
UUID: 44454C4C-5900-1050-8033-C4C04F434731
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Not Specified
Handle 0x0200, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Dell Inc.
Product Name: 0PU052
Version:
Handle 0x0300, DMI type 3, 13 bytes
Chassis Information
Manufacturer: Dell Inc.
Type: Space-saving
Lock: Not Present
Version: Not Specified
Asset Tag:
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
Handle 0x0400, DMI type 4, 40 bytes
Processor Information
Socket Designation: CPU
Type: Central Processor
Family: Xeon
Manufacturer: Intel
ID: 76 06 01 00 FF FB EB BF
Signature: Type 0, Family 6, Model 23, Stepping 6
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Not Specified
Voltage: 0.0 V
External Clock: 1333 MHz
Max Speed: 5200 MHz
Current Speed: 2666 MHz
Status: Populated, Enabled
Upgrade: Socket LGA775
L1 Cache Handle: 0x0700
L2 Cache Handle: 0x0701
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 2
Core Enabled: 2
Thread Count: 2
Characteristics:
64-bit capable
Handle 0x0700, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 32 kB
Maximum Size: 32 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: None
System Type: Data
Associativity: 8-way Set-associative
Handle 0x0701, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Varies With Memory Address
Location: Internal
Installed Size: 6144 kB
Maximum Size: 6144 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: <OUT OF SPEC>
Handle 0x0800, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: PARALLEL
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-25 female
Port Type: Parallel Port PS/2
Handle 0x0801, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: SERIAL1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x0802, DMI type 126, 9 bytes
Inactive
Handle 0x0803, DMI type 126, 9 bytes
Inactive
Handle 0x0804, DMI type 126, 9 bytes
Inactive
Handle 0x0805, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0806, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB2
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0807, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB3
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0808, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB4
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0809, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB5
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB6
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB7
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB8
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: ENET
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: RJ-45
Port Type: Network Port
Handle 0x080E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MIC
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x080F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0810, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-IN
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0811, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: HP-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0812, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MONITOR
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-15 female
Port Type: Video Port
Handle 0x090A, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT1
Type: x1 Proprietary
Current Usage: In Use
Length: Long
Characteristics:
PME signal is supported
Handle 0x0901, DMI type 126, 13 bytes
Inactive
Handle 0x0902, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT2
Type: 32-bit PCI
Current Usage: Available
Length: Long
ID: 2
Characteristics:
5.0 V is provided
3.3 V is provided
PME signal is supported
Handle 0x0903, DMI type 126, 13 bytes
Inactive
Handle 0x0904, DMI type 126, 13 bytes
Inactive
Handle 0x0905, DMI type 126, 13 bytes
Inactive
Handle 0x0906, DMI type 126, 13 bytes
Inactive
Handle 0x0907, DMI type 126, 13 bytes
Inactive
Handle 0x0908, DMI type 126, 13 bytes
Inactive
Handle 0x0A00, DMI type 10, 6 bytes
On Board Device Information
Type: Video
Status: Disabled
Description: Intel Graphics Media Accelerator 950
Handle 0x0A02, DMI type 10, 6 bytes
On Board Device Information
Type: Ethernet
Status: Enabled
Description: Intel Gigabit Ethernet Controller
Handle 0x0A03, DMI type 10, 6 bytes
On Board Device Information
Type: Sound
Status: Enabled
Description: Intel(R) High Definition Audio Controller
Handle 0x0B00, DMI type 11, 5 bytes
OEM Strings
String 1: www.dell.com
Handle 0x0D00, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
Handle 0x0F00, DMI type 15, 29 bytes
System Event Log
Area Length: 2049 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: Memory-mapped physical 32-bit address
Access Address: 0xFFF01000
Status: Valid, Not Full
Change Token: 0x00000018
Header Format: Type 1
Supported Log Type Descriptors: 3
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: System limit exceeded
Data Format 2: System management
Descriptor 3: Log area reset/cleared
Data Format 3: None
Handle 0x1000, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 8 GB
Error Information Handle: Not Provided
Number Of Devices: 4
Handle 0x1100, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_1
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Manufacturer: AD00000000000000
Handle 0x1101, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_3
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1102, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_2
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1103, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_4
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1300, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FDFFFFFF
Range Size: 4064 MB
Physical Array Handle: 0x1000
Partition Width: 1
Handle 0x1400, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1100
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1401, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1101
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1402, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1102
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1403, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1103
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1410, DMI type 126, 19 bytes
Inactive
Handle 0x1800, DMI type 24, 5 bytes
Hardware Security
Power-On Password Status: Enabled
Keyboard Password Status: Not Implemented
Administrator Password Status: Enabled
Front Panel Reset Status: Not Implemented
Handle 0x1900, DMI type 25, 9 bytes
System Power Controls
Next Scheduled Power-on: *-* 00:00:00
Handle 0x1B10, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD00
Handle 0x1B11, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD01
Handle 0x1B12, DMI type 126, 12 bytes
Inactive
Handle 0x1B13, DMI type 126, 12 bytes
Inactive
Handle 0x1B14, DMI type 126, 12 bytes
Inactive
Handle 0x2000, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected
Handle 0x8100, DMI type 129, 8 bytes
OEM-specific Type
Header and Data:
81 08 00 81 01 01 02 01
Strings:
Intel_ASF
Intel_ASF_001
Handle 0x8200, DMI type 130, 20 bytes
OEM-specific Type
Header and Data:
82 14 00 82 24 41 4D 54 01 01 00 00 01 A5 0B 02
00 00 00 00
Handle 0x8300, DMI type 131, 64 bytes
OEM-specific Type
Header and Data:
83 40 00 83 14 00 00 00 00 00 C0 29 05 00 00 00
F8 00 4E 24 00 00 00 00 0D 00 00 00 02 00 03 00
19 04 14 00 01 00 01 02 C8 00 BD 10 00 00 00 00
00 00 00 00 FF 00 00 00 00 00 00 00 00 00 00 00
Handle 0x8800, DMI type 136, 6 bytes
OEM-specific Type
Header and Data:
88 06 00 88 5A 5A
Handle 0xD000, DMI type 208, 10 bytes
OEM-specific Type
Header and Data:
D0 0A 00 D0 01 03 FE 00 11 02
Handle 0xD100, DMI type 209, 12 bytes
OEM-specific Type
Header and Data:
D1 0C 00 D1 78 03 07 03 04 0F 80 05
Handle 0xD200, DMI type 210, 12 bytes
OEM-specific Type
Header and Data:
D2 0C 00 D2 F8 03 04 03 06 80 04 05
Handle 0xD201, DMI type 126, 12 bytes
Inactive
Handle 0xD400, DMI type 212, 242 bytes
OEM-specific Type
Header and Data:
D4 F2 00 D4 70 00 71 00 00 10 2D 2E 42 00 11 FE
01 43 00 11 FE 00 0F 00 25 FC 00 10 00 25 FC 01
11 00 25 FC 02 12 00 25 FC 03 00 00 25 F3 00 00
00 25 F3 04 00 00 25 F3 08 00 00 25 F3 0C 07 00
23 8F 00 08 00 23 F3 00 09 00 23 F3 04 0A 00 23
F3 08 0B 00 23 8F 10 0C 00 23 8F 20 0E 00 23 8F
30 0D 00 23 8C 40 A6 00 23 8C 41 A7 00 23 8C 42
05 01 22 FD 02 06 01 22 FD 00 8C 00 22 FE 00 8D
00 22 FE 01 9B 00 25 3F 40 9C 00 25 3F 00 09 01
25 3F 80 A1 00 26 F3 00 A2 00 26 F3 08 A3 00 26
F3 04 9F 00 26 FD 02 A0 00 26 FD 00 9D 00 11 FB
04 9E 00 11 FB 00 54 01 23 7F 00 55 01 23 7F 80
5C 00 78 BF 40 5D 00 78 BF 00 04 80 78 F5 0A 01
A0 78 F5 00 93 00 7B 7F 80 94 00 7B 7F 00 8A 00
37 DF 20 8B 00 37 DF 00 03 C0 67 00 05 FF FF 00
00 00
Handle 0xD401, DMI type 212, 172 bytes
OEM-specific Type
Header and Data:
D4 AC 01 D4 70 00 71 00 03 40 59 6D 2D 00 59 FC
02 2E 00 59 FC 00 6E 00 59 FC 01 E0 01 59 FC 03
28 00 59 3F 00 29 00 59 3F 40 2A 00 59 3F 80 2B
00 5A 00 00 2C 00 5B 00 00 55 00 59 F3 00 6D 00
59 F3 04 8E 00 59 F3 08 8F 00 59 F3 00 00 00 55
FB 04 00 00 55 FB 00 23 00 55 7F 00 22 00 55 7F
80 F5 00 58 BF 40 F6 00 58 BF 00 EB 00 55 FE 00
EA 00 55 FE 01 40 01 54 EF 00 41 01 54 EF 10 ED
00 54 F7 00 F0 00 54 F7 08 4A 01 53 DF 00 4B 01
53 DF 20 4C 01 53 7F 00 4D 01 53 7F 80 68 01 56
BF 00 69 01 56 BF 40 FF FF 00 00 00
Handle 0xD402, DMI type 212, 152 bytes
OEM-specific Type
Header and Data:
D4 98 02 D4 70 00 71 00 00 10 2D 2E 2D 01 21 FE
01 2E 01 21 FE 00 97 00 22 FB 00 98 00 22 FB 04
90 00 11 CF 00 91 00 11 CF 20 92 00 11 CF 10 E2
00 27 7F 00 E3 00 27 7F 80 E4 00 27 BF 00 E5 00
27 BF 40 D1 00 22 7F 80 D2 00 22 7F 00 45 01 22
BF 40 44 01 22 BF 00 36 01 21 F1 06 37 01 21 F1
02 38 01 21 F1 00 39 01 21 F1 04 2B 01 11 7F 80
2C 01 11 7F 00 4E 01 65 CF 00 4F 01 65 CF 10 D4
01 65 F3 00 D5 01 65 F3 04 D2 01 65 FC 00 D3 01
65 FC 01 FF FF 00 00 00
Handle 0xD403, DMI type 212, 157 bytes
OEM-specific Type
Header and Data:
D4 9D 03 D4 70 00 71 00 03 40 59 6D 17 01 52 FE
00 18 01 52 FE 01 19 01 52 FB 00 1A 01 52 FB 04
1B 01 52 FD 00 1C 01 52 FD 02 1D 01 52 F7 00 1E
01 52 F7 08 1F 01 52 EF 00 20 01 52 EF 10 21 01
52 BF 00 22 01 52 BF 40 87 00 59 DF 20 88 00 59
DF 00 E8 01 66 FD 00 E9 01 66 FD 02 02 02 53 BF
00 03 02 53 BF 40 04 02 53 EF 00 05 02 53 EF 10
06 02 66 DF 00 07 02 66 DF 20 08 02 66 EF 00 09
02 66 EF 10 17 02 66 F7 00 18 02 66 F7 08 44 02
52 BF 40 45 02 52 BF 00 FF FF 00 00 00
Handle 0xD800, DMI type 126, 9 bytes
Inactive
Handle 0xDD00, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 00 DD 00 01 00 00 00 10 F5 00 00 00 00 00
00 00 00
Handle 0xDD01, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 01 DD 00 01 00 00 00 11 F5 00 00 00 00 00
00 00 00
Handle 0xDD02, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 02 DD 00 01 00 00 00 12 F5 00 00 00 00 00
00 00 00
Handle 0xDE00, DMI type 222, 16 bytes
OEM-specific Type
Header and Data:
DE 10 00 DE C1 0B 00 00 10 05 19 21 01 00 00 01
Handle 0x7F00, DMI type 127, 4 bytes
End Of Table
Hdparm also does not tell me the max data transfer rate (disk speed) of my current drive although this link : www.wdc.com/en/library/sata/2879-001146.pdf says that it is 3.0Gb/s
and here's hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
Model Number: WDC WD800JD-75JNC0
Firmware Revision: 06.01C06
Standards:
Supported: 6 5 4
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
CHS current addressable sectors: 16514064
LBA user addressable sectors: 156250000
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 76293 MBytes
device size with M = 1000*1000: 80000 MBytes (80 GB)
cache/buffer size = 8192 KBytes
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 8
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
SET_MAX security extension
Automatic Acoustic Management feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* SMART error logging
* SMART self-test
* Gen1 signaling speed (1.5Gb/s)
* Host-initiated interface power management
* SMART Command Transport (SCT) feature set
* SCT Long Sector Access (AC1)
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
Checksum: correct
Last edited by Inxsible (2011-03-27 04:40:49)I just checked my BIOS and my current setting is set at IDE although it also mentions that the default should be AHCI. Currently I have a dual boot of Windows 7 (need it for Tax software) and Arch
So I guess, when I get the new HDD, I will first set it to AHCI and then install the OSes on it. See if NCQ helps any, and if not I will turn it back and re-install (if I have to). I am planning to have Windows only in virtualbox in the new drive.
Anyhoo, while I was in the BIOS I found two things which I had questions about :
1) Under Onboard Devices --> Integrated NIC , my setting is currently set at "On w/PXE" and it says the default should be just "On". Would it be ok to change it back to On since its a single machine and its not booting an OS on any server. I just don't want to have to re-install anything now since I will be doing that in the new HDD.
2) How would I know whether my BIOS would support a 64 bit OS in Virtualbox? I checked some setting under Virtualization, but they weren't very clear.
I will edit this post and let you know exactly what settings were present under the Virtualization sub-section. -
At the time of recovering voting disk
os:redhat linux
rdbms:10.2.0.1
clusterware:10.2.01.
hai...
we are using three voting disks for our cluster.i have taken backup of these three voting disks indivdually.like voting_disk1_bkp,voting_disk2_bkp,voting_disk3_bkp
suddenly the drive of voting_disk_file2 file has failed.
now i have to recover the voting_disk_file2.which method do i need to follow?
1)dd if=voting_disk2_bkp of=voting_disk_name
or
2)crsctl add css votedisk <path>
and why should we take individual backup of votking disks?
is these three voting disks are not equal?
please guide me.
v.s.srinivasAlso be aware that in 10g theres a bug; Some of the the docs and books say that you can do "crsctl add css votedisk " with the "-force" option to add a voting disk with the cluster up. This can cause corruption - see Note:390880.1
Yours,
Bob -
After Patch 10.2.0.4, got "voting disk corrupted" error.
Dear all,
My setting is:
OS:RHEL4.8 U8 x86
DB:10.2.0.1
CRS:10.2.0.1
After I installed Patchset 10.2.0.4 and execute $CRS_HOME/install/root102.sh, I could't start clusterware anymore. After checking ocssd.log, I found some messages like this:
[ CSSD]2010-01-07 15:53:06.519 [3086919360] >TRACE: clssscmain: local-only set to false
[ CSSD]2010-01-07 15:53:06.562 [3086919360] >TRACE: clssnmReadNodeInfo: added node 1 (x101) to cluster
[ CSSD]2010-01-07 15:53:06.578 [3086919360] >TRACE: clssnmReadNodeInfo: added node 2 (x102) to cluster
[ CSSD]2010-01-07 15:53:06.580 [3086919360] >TRACE: clssnmInitNMInfo: Initialized with unique 1262850786
[ CSSD]2010-01-07 15:53:06.586 [3086919360] >TRACE: clssNMInitialize: Initializing with OCR id (33483723)
[ CSSD]2010-01-07 15:53:06.650 [84294560] >TRACE: clssnm_skgxninit: Compatible vendor clusterware not in use
[ CSSD]2010-01-07 15:53:06.650 [84294560] >TRACE: clssnm_skgxnmon: skgxn init failed
[ CSSD]2010-01-07 15:53:06.657 [3086919360] >TRACE: clssnmNMInitialize: misscount set to (60), impending reconfig threshold set to (56000)
[ CSSD]2010-01-07 15:53:06.659 [3086919360] >TRACE: clssnmNMInitialize: Network heartbeat thresholds are: impending reconfig 30000 ms, reconfig start (misscount) 60000 ms
[ CSSD]2010-01-07 15:53:06.669 [3086919360] >TRACE: clssnmDiskStateChange: state from 1 to 2 disk (0//ocfs/voting)
[ CSSD]2010-01-07 15:53:06.669 [84294560] >TRACE: clssnmvDPT: spawned for disk 0 (/ocfs/voting)
[ CSSD]2010-01-07 15:53:08.755 [84294560] >TRACE: clssnmDiskStateChange: state from 2 to 4 disk (0//ocfs/voting)
[ CSSD]2010-01-07 15:53:08.821 [113339296] >TRACE: clssnmvKillBlockThread: spawned for disk 0 (/ocfs/voting) initial sleep interval (1000)ms
[ CSSD]2010-01-07 15:53:08.889 [3086919360] >TRACE: clssnmFatalInit: fatal mode enabled
[ CSSD]2010-01-07 15:53:08.999 [94784416] >TRACE: clssnmClusterListener: Spawned
[ CSSD]2010-01-07 15:53:09.002 [94784416] >TRACE: clssnmClusterListener: Listening on (ADDRESS=(PROTOCOL=tcp)(HOST=x102-priv)(PORT=49895))
[ CSSD]2010-01-07 15:53:09.002 [94784416] >TRACE: clssnmconnect: connecting to node(1), con(0x81bc480), flags 0x0003
[ CSSD]2010-01-07 15:53:09.069 [3083459488] >TRACE: clssgmclientlsnr: Spawned
[ CSSD]2010-01-07 15:53:09.072 [113339296] >ERROR: clssnmvDiskKillCheck: voting disk corrupted (0x00000000,0x00000000) (0//ocfs/voting)
[ CSSD]2010-01-07 15:53:09.072 [113339296] >TRACE: clssnmDiskStateChange: state from 4 to 3 disk (0//ocfs/voting)
[ CSSD]2010-01-07 15:53:09.072 [130767776] >TRACE: clssnmDiskPMT: disk offline (0//ocfs/voting)
[ CSSD]2010-01-07 15:53:09.072 [130767776] >ERROR: clssnmDiskPMT: Aborting, 1 of 1 voting disks unavailable
[ CSSD]2010-01-07 15:53:09.072 [130767776] >ERROR: ###################################
[ CSSD]2010-01-07 15:53:09.072 [130767776] >ERROR: clssscExit: CSSD aborting
[ CSSD]2010-01-07 15:53:09.072 [130767776] >ERROR: ###################################
[ CSSD]--- DUMP GROCK STATE DB ---
I tried to recreate my voting disk like this:
$CRS_HOME/bin/crsctl add css votedisk /ocfs/voting1 -force
$CRS_HOME/bin/crsctl delete css votedisk /ocfs/voting -force
$CRS_HOME/bin/crsctl add css votedisk /ocfs/voting -force
$CRS_HOME/bin/crsctl delete css votedisk /ocfs/voting1 -force
Then run root102.sh again but still got the same error message about "voting disk corrupted".
I was totally confused and don't know how to fix it.
Please, any suggestion would be appreciated.Hello,
Did u try restore the OCR?
http://download-west.oracle.com/docs/cd/B19306_01/rac.102/b14197/votocr.htm#i1012456
The steps to apply RAC patch were followed correctly?
See a patchset roadmap at http://mufalani.blogspot.com/2009/06/applying-10204-patch-on-rac-systems.html
Best Regards,
Rodrigo Mufalani
http://www.mrdba.com.br/mufalani -
Root.sh hangs at formatting voting disk on OEL32 11gR2 RAC with ocfs2
Hi,
Am trying to bring up Oracle11gR2 RAC on Enterprise Linux x86 (32bit) version 5.6. I am using Ocfs2 1.4 as my cluster file share. Everything went fine till the root.sh and it hangs with a message "now formatting voting disk <vdsk path>
The logs are mentioned below.
Checked the alert log:
{quote}
cssd(9506)]CRS-1601:CSSD Reconfiguration complete. Active nodes are oel32rac1 .
2011-08-04 15:58:55.356
[ctssd(9552)]CRS-2407:The new Cluster Time Synchronization Service reference node is host oel32rac1.
2011-08-04 15:58:55.917
[ctssd(9552)]CRS-2401:The Cluster Time Synchronization Service started on host oel32rac1.
2011-08-04 15:58:56.213
[client(9567)]CRS-1006:The OCR location /u02/storage/ocr is inaccessible. Details in /u01/app/11.2.0/grid/log/oel32rac1/client/ocrconfig_9567.log.
2011-08-04 15:58:56.365
[client(9567)]CRS-1001:The OCR was formatted using version 3.
2011-08-04 15:58:59.977
[crsd(9579)]CRS-1012:The OCR service started on node oel32rac1.
{quote}
crsctl.log:
{quote}
2011-08-04 15:59:00.246: [ CRSCTL][3046184656]crsctl_vformat: obtain cssmode 1
2011-08-04 15:59:00.247: [ CRSCTL][3046184656]crsctl_vformat: obtain VFListSZ 0
2011-08-04 15:59:00.258: [ CRSCTL][3046184656]crsctl_vformat: Fails to obtain backuped Lease from CSSD with error code 16
2011-08-04 15:59:01.857: [ CRSCTL][3046184656]crsctl_vformat: to do clsscfg fmt with lease sz 0
2011-08-04 15:59:01.910: [ SKGFD][3046184656]NOTE: No asm libraries found in the system
2011-08-04 15:59:01.910: [ CLSF][3046184656]Allocated CLSF context
2011-08-04 15:59:01.910: [ SKGFD][3046184656]Discovery with str:/u02/storage/vdsk:
2011-08-04 15:59:01.910: [ SKGFD][3046184656]UFS discovery with :/u02/storage/vdsk:
2011-08-04 15:59:01.910: [ SKGFD][3046184656]Fetching UFS disk :/u02/storage/vdsk:
2011-08-04 15:59:01.911: [ SKGFD][3046184656]OSS discovery with :/u02/storage/vdsk:
2011-08-04 15:59:01.911: [ SKGFD][3046184656]Handle 0xa6c19f8 from lib :UFS:: for disk :/u02/storage/vdsk:
2011-08-04 17:10:37.522: [ SKGFD][3046184656]WARNING:io_getevents timed out 618 sec
2011-08-04 17:10:37.526: [ SKGFD][3046184656]WARNING:io_getevents timed out 618 sec
{quote}
ocrconfig log:
{quote}
2011-08-04 15:58:56.214: [ OCRRAW][3046991552]ibctx: Failed to read the whole bootblock. Assumes invalid format.
2011-08-04 15:58:56.214: [ OCRRAW][3046991552]proprinit:problem reading the bootblock or superbloc 22
2011-08-04 15:58:56.214: [ OCROSD][3046991552]utread:3: Problem reading buffer 8532000 buflen 4096 retval 0 phy_offset 102400 retry 0
2011-08-04 15:58:56.214: [ OCROSD][3046991552]utread:3: Problem reading buffer 8532000 buflen 4096 retval 0 phy_offset 102400 retry 1
2011-08-04 15:58:56.214: [ OCROSD][3046991552]utread:3: Problem reading buffer 8532000 buflen 4096 retval 0 phy_offset 102400 retry 2
2011-08-04 15:58:56.214: [ OCROSD][3046991552]utread:3: Problem reading buffer 8532000 buflen 4096 retval 0 phy_offset 102400 retry 3
2011-08-04 15:58:56.214: [ OCROSD][3046991552]utread:3: Problem reading buffer 8532000 buflen 4096 retval 0 phy_offset 102400 retry 4
2011-08-04 15:58:56.214: [ OCROSD][3046991552]utread:3: Problem reading buffer 8532000 buflen 4096 retval 0 phy_offset 102400 retry 5
2011-08-04 15:58:56.214: [ OCRRAW][3046991552]propriogid:1_1: Failed to read the whole bootblock. Assumes invalid format.
2011-08-04 15:58:56.365: [ OCRRAW][3046991552]iniconfig:No 92 configuration
2011-08-04 15:58:56.365: [ OCRAPI][3046991552]a_init:6a: Backend init successful
2011-08-04 15:58:56.390: [ OCRCONF][3046991552]Initialized DATABASE keys
2011-08-04 15:58:56.564: [ OCRCONF][3046991552]csetskgfrblock0: output from clsmft: [clsfmt: successfully initialized file /u02/storage/ocr
2011-08-04 15:58:56.577: [ OCRCONF][3046991552]Successfully set skgfr block 0
2011-08-04 15:58:56.578: [ OCRCONF][3046991552]Exiting [status=success]...
{quote}
ocssd.log:
{quote}
2011-08-04 15:59:00.140: [ CSSD][2963602320]clssgmFreeRPCIndex: freeing rpc 23
2011-08-04 15:59:00.228: [ CSSD][2996054928]clssgmExecuteClientRequest: CONFIG recvd from proc 6 (0xb35f7438)
2011-08-04 15:59:00.228: [ CSSD][2996054928]clssgmConfig: type(1)
2011-08-04 15:59:00.234: [ CSSD][2996054928]clssgmExecuteClientRequest: VOTEDISKQUERY recvd from proc 6 (0xb35f7438)
2011-08-04 15:59:00.247: [ CSSD][2996054928]clssgmExecuteClientRequest: CONFIG recvd from proc 6 (0xb35f7438)
2011-08-04 15:59:00.247: [ CSSD][2996054928]clssgmConfig: type(1)
2011-08-04 15:59:03.039: [ CSSD][2942622608]clssnmSendingThread: sending status msg to all nodes
2011-08-04 15:59:03.039: [ CSSD][2942622608]clssnmSendingThread: sent 4 status msgs to all nodes
2011-08-04 15:59:07.047: [ CSSD][2942622608]clssnmSendingThread: sending status msg to all nodes
2011-08-04 15:59:07.047: [ CSSD][2942622608]clssnmSendingThread: sent 4 status msgs to all nodes
2011-08-04 15:59:11.057: [ CSSD][2942622608]clssnmSendingThread: sending status msg to all nodes
2011-08-04 15:59:11.057: [ CSSD][2942622608]clssnmSendingThread: sent 4 status msgs to all nodes
2011-08-04 15:59:16.068: [ CSSD][2942622608]clssnmSendingThread: sending status msg to all nodes
2011-08-04 15:59:16.068: [ CSSD][2942622608]clssnmSendingThread: sent 5 status msgs to all nodes
2011-08-04 15:59:21.079: [ CSSD][2942622608]clssnmSendingThread: sending status msg to all nodes
2011-08-04 15:59:21.079: [ CSSD][2942622608]clssnmSendingThread: sent 5 status msgs to all nodes
{quote}
Any help here is appreciated.
Regards
Amith R
Edited by: Mithzz on Aug 4, 2011 4:58 AMDid an lsof on vdisk and it showed
>
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
crsctl.bi 9589 root 26u REG 8,17 21004288 102980 /u02/storage/vdsk
[root@oel32rac1 ~]# ps -ef |grep crsctl
root 9589 7583 0 15:58 pts/1 00:00:00 [crsctl.bin] <defunct>
>
Could this be a permission issue ?
--Amith -
Hello,
It may sound too easy to someone but I need to ask it anyway.
I am in the middle of building Oracle RAC 11.2.0.3 on Linux. I have 2 storage and I created three LUNs in each of storage so 6 LUNs in total look in both of servers. If I choose NORMAL as a redundancy level, is it right to choose my 6 disks those are created for OCR_VOTE at the grid installation? Or should I choose only 3 of them and configure mirroring at latter stage?
The reason why I am asking this is that I didn't find any place to create asm disk group for ocr and voting disks at the oracle grid infrastructure installation window. In fact, I would to like to create two disk groups in which one of groups contains three disks those were brought from storage 1 and the second one contains rest three 3 disk that come from the last storage.
I believe that you will understand the manner and help me on choosing proper way.
Thank you.Hi,
You have 2 Storage H/W.
You will need to configure a Quorum ASMDisk to store a Voting Disk.
Because if you lose 1/2 or more of all of your voting disks, then nodes get evicted from the cluster, or nodes kick themselves out of the cluster.
You must have the odd number of voting disk (i.e 1,3 or 5) one voting disk per ASM DISK, So 1 Storage will hold more voting disk than another storage.
(e.g 3 Voting Disk - 2 voting stored in stg-A and 1 voting disk store in stg-B)
If fail the storage that hold the major number of Voting disk the whole cluster (all nodes) goes down. Does not matter if you have a other storage online.
It will happen:
https://forums.oracle.com/message/9681811#9681811
You must configure your Clusterware same as RAC extended
Check this link:
http://www.oracle.com/technetwork/database/clusterware/overview/grid-infra-thirdvoteonnfs-131158.pdf
Explaining: How to store OCR, Voting disks and ASM SPFILE on ASM Diskgroup (RAC or RAC Extended) | Levi Pereira | Oracl… -
How can i backup my voting disk on windows
i can backup voting disk with dd in unix, but how can i backup it in windows,
I will replace my disk-storage in the ORACLE rac enviement, must i reistall operating system; ocr and voting disk (then restore the database); or can i resotre ocr and voting disk than restore database; have you any other idear ,You can not backup from *NIX & restore onto Windoze.
-
Voting disk external redundancy
Hey,
question:
I´ve got an database which I haven´t installed myself.
A query for the votedisk shows only one configured votedisk for my 2 node rac cluster.
So I presume, that external redundancy was setup during installation of clusterware.
A few weeks ago I hit an unpublished error, where oracle sends a message that the voting disk are corrupted - which is a false message.
But anyway, what is happening, when I hit this error in my new scenarion (apart of applying the crs bundle patch - which I cant apply...)
How can make sure, that a new voting disk is added with external redundancy as well (crsctl add css votedisk /dev/raw/raw#)
or would this give back an error, because only one voting disk is configurable ?Hi Christian,
How can make sure, that a new voting disk is added with external redundancy as well (crsctl add css votedisk /dev/raw/raw#) or would this give back an error, because only one voting disk is configurable ?I will assume you are using version 11.1 or earlier.
What determines whether your voting disk is with external redundancy or normal redudancy the amount of voting is that your environment has.
If you have only one voting disk you have external redundancy (The customers guarantees the recovery of the voting disk in case of failure. At least Oracle thinks so).
If you more than 2 (because you need to get an odd number) voting disk you are using normal redundancy. *## Edited by: Levi Pereira on Feb 7, 2011 12:09 PM*
Then you can add more voting disk in your environment without worrying about external redudancy previously configured.
External Redundancy or Normal Redundancy is nominated only by the amount from voting disk you have, there is no configuration to change External Redundancy to Normal Redundancy. As I have said is only the amount from voting that you have configured in your environment.
Make sure you have a fresh backup of your voting disk.
Warning: The voting disk backup is performed manually in the environment UNIX/Linux with the dd command.
Regards,
Levi Pereira
Edited by: Levi Pereira on Feb 7, 2011 12:09 PM -
I had a problem with my votingdisks:
First CSS would not start. CSS log said votingdisks were missing:
C:\oracle\product\10.2.0>crsctl query css votedisk
0. 0 \\.\votedsk1
1. 0
2. 0
located 3 votedisk(s).
I stopped the cluster and could add my voting disks:
Result:
C:\oracle\product\10.2.0>crsctl query css votedisk
0. 0 \\.\votedsk1
1. 0
2. 0
3. 0 \\.\votedsk3
4. 0 \\.\votedsk2
located 5 votedisk(s).
How can I get rid off the "empty" values?I ran into the samething today and figured out how to get rid of them at least on a Win 2003 SP2R2 cluster. Mine were showing 0s for the path as well so after a lot of trial and error I finally just tried:
crsctl delete css votedisk 0
And it worked... What happens is, when you have to do a -force to create extra votedisks the cluster has to be stopped on all nodes or this will happen. We were doing a totally fresh install so we played with it a little to determine this is what happened. When we stopped everything before adding votedisks using -force and cleaning up the bad ones, everything went fine. -
How to rename voting disk name in oracle clusterware 11gr2
Hi:
I need change the name of voting disk at os level, original name is /dev/rhdisk20, I need rename to /dev/asmocr_vote1 (unix AIX), the voting disk is locate in ASM diskgroup +OCR.
Initial voting disk was: /dev/rhdisk20 in diskgroup +OCR
#(root) /oracle/GRID/11203/bin->./crsctl query css votedisk
## STATE File Universal Id File Name Disk group
1. ONLINE a2e6bb7e57044fcabf0d97f40357da18 (/dev/rhdisk20) [OCR]
I createt a new alias disk name:
#mknod /dev/asmocr_vote01 c 18 10
# /dev->ls -lrt|grep "18, 10"
brw------- 1 root system 18, 10 Aug 27 13:15 hdisk20
crw-rw---- 1 oracle asmadmin 18, 10 Sep 6 16:57 rhdisk20 --> Old name
crw-rw---- 1 oracle asmadmin 18, 10 Sep 6 16:59 asmocr_vote01 ---> alias to old name, the new name.
After change votingn disk unix name, the cluster doesn't start, voting disk is not found by CRSSD.
-STEPS to start clusterware after changing the OS voting disk name are:
1- stop al nodes:
#crsctl stop crs -f (every node)
Work only in one node (node1, +ASM1 instance):
2- Change asm_diskstring in init+ASM1.ora:
asm_diskstring = /dev/asm*
3- change disk unix permiss:
# /dev->ls -lrt|grep "18, 10"
brw------- 1 root system 18, 10 Aug 27 13:15 hdisk20
crw-rw---- 1 root system 18, 10 Sep 6 16:59 asmocr_vote01
crw-rw---- 1 oracle asmadmin 18, 10 Sep 6 17:37 rhdisk20
#(root) /dev->chown oracle:asmadmin asmocr_vote01
#(root) /dev->chown root:system rhdisk20
#(root) /dev->ls -lrt|grep "18, 10"
brw------- 1 root system 18, 10 Aug 27 13:15 hdisk20
crw-rw---- 1 oracle asmadmin 18, 10 Sep 6 16:59 asmocr_vote01 --> new name only have oracle:oinstall
crw-rw---- 1 root system 18, 10 Sep 6 17:37 rhdisk20
4-start node in exclusive mode:
# (root) /oracle/GRID/11203/bin->./crsctl start crs -excl
CRS-4123: Oracle High Availability Services has been started.
CRS-2672: Attempting to start 'ora.mdnsd' on 'orarac3intg'
CRS-2676: Start of 'ora.mdnsd' on 'orarac3intg' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'orarac3intg'
CRS-2676: Start of 'ora.gpnpd' on 'orarac3intg' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'orarac3intg'
CRS-2672: Attempting to start 'ora.gipcd' on 'orarac3intg'
CRS-2676: Start of 'ora.cssdmonitor' on 'orarac3intg' succeeded
CRS-2676: Start of 'ora.gipcd' on 'orarac3intg' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'orarac3intg'
CRS-2672: Attempting to start 'ora.diskmon' on 'orarac3intg'
CRS-2676: Start of 'ora.diskmon' on 'orarac3intg' succeeded
CRS-2676: Start of 'ora.cssd' on 'orarac3intg' succeeded
CRS-2672: Attempting to start 'ora.ctssd' on 'orarac3intg'
CRS-2672: Attempting to start 'ora.drivers.acfs' on 'orarac3intg'
CRS-2679: Attempting to clean 'ora.cluster_interconnect.haip' on 'orarac3intg'
CRS-2681: Clean of 'ora.cluster_interconnect.haip' on 'orarac3intg' succeeded
CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'orarac3intg'
CRS-2676: Start of 'ora.ctssd' on 'orarac3intg' succeeded
CRS-2676: Start of 'ora.drivers.acfs' on 'orarac3intg' succeeded
CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'orarac3intg' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'orarac3intg'
CRS-2676: Start of 'ora.asm' on 'orarac3intg' succeeded
CRS-2672: Attempting to start 'ora.crsd' on 'orarac3intg'
CRS-2676: Start of 'ora.crsd' on 'orarac3intg' succeeded
5-check votedisk:
# (root) /oracle/GRID/11203/bin->./crsctl query css votedisk
Located 0 voting disk(s).
--> NO VOTING DISK found
6- mount diskgroup of voting disk (+OCR in this case) in +ASM1 instance:
SQL> ALTER DISKGROUP OCR mount;
7-add votedisk belongs diskgroup +OCR:
# (root) /oracle/GRID/11203/bin->./crsctl replace votedisk +OCR
Successful addition of voting disk 86d8b12b1c294f5ebfa66f7f482f41ec.
Successfully replaced voting disk group with +OCR.
CRS-4266: Voting file(s) successfully replaced
#(root) /oracle/GRID/11203/bin->./crsctl query css votedisk
## STATE File Universal Id File Name Disk group
1. ONLINE 86d8b12b1c294f5ebfa66f7f482f41ec (/dev/asmocr_vote01) [OCR]
Located 1 voting disk(s).
8-stop node:
#(root) /oracle/GRID/11203/bin->./crsctl stop crs –f
8-start node:
#(root) /oracle/GRID/11203/bin->./crsctl start crs
10- check:
# (root) /oracle/GRID/11203/bin->./crsctl query css votedisk
## STATE File Universal Id File Name Disk group
1. ONLINE 86d8b12b1c294f5ebfa66f7f482f41ec (/dev/asmocr_vote01) [OCR]
Vicente.
HP.
Edited by: 957649 on 07-sep-2012 13:11There is no facilty to rename a column name in Oracle 8i. This is possible from Oracle 9.2 version onwards.
For you task one example given below.
Example:-
Already existed table is ITEMS
columns in ITEMS are ITID, ITEMNAME.
But instead of ITID I want ITEMID.
Solution:-
step 1 :- create table items_dup
as select itid itemid, itemname from items;
step 2 :- drop table items;
step 3 :- rename items_dup to items;
Result:-
ITEMS table contains columns ITEMID, ITEMNAME -
Confusion with OCFS2 File system for OCR and Voting disk RHEL 5, Oracle11g,
Dear all,
I am in the process of installing Oracle 11g 3 Node RAC database
The environment on which i have to do this implementation is as follows:
Oracle 11g.
Red Hat Linux 5 x86
Oracle Clusterware
ASM
EMC Storage
250 Gb of Storage drive.
SAN
As of now i am in the process of installing Oracle Clusterware on the 3 nodes.
I have performed these tasks for the cluster installs.
1. Configure Kernel Parameters
2. Configure User Limits
3. Modify the /etc/pam.d/login file
4. Configure Operating System Users and Groups for Oracle Clusterware
5. Configure Oracle Clusterware Owner Environment
6. Install CVUQDISK rpm package
7. Configure the Hosts file
8. Verify the Network Setup
9. Configure the SSH on all Cluster Nodes (User Equivalence)
9. Enable the SSH on all Cluster Nodes (User Equivalence)
10. Install Oracle Cluster File System (OCFS2)
11.Verify the Installation of Oracle Cluster File System (OCFS2)
12. Configure the OCFS2 (/etc/ocfs2/cluster.conf)
13. Configure the O2CB Cluster Stack for OCFS2
BUT, here after i am a little bit confused on how to proceed further. The next step is to Format the disk and mount the OCFS2, Create Software Directories... so and so forth.
I asked my system admin to provide me two partitions so that i could format them with OCFS2 file system.
He wrote back to me saying.
*"Is what you want before I do it??*
*/dev/emcpowera1 is 3GB and formatted OCFS2.*
*/dev/emcpowera2 is 3GB and formatted OCFS2.*
*Are those big enough for you? If not, I can re-size and re-format them*
*before I mount them on the servers.*
*the SAN is shared storage. /dev/emcpowera is one of three LUNs on*
*the shared storage, and it's 214GB. Right now there are only two*
*partitions on it- the ones I listed below. I can repartition the LUN any*
*way you want it.*
*Where do you want these mounted at:*
*/dev/emcpowera1*
*/dev/emcpowera2*
*I was thinking if this mounting techique would work like so:*
*emcpowera1: /u01/shared_config/OCR_config*
*emcpowera2: /u01/shared_config/voting_disk*
*Let me know how you'd like them mounted."*
Please recommend me what i should convey to him so that i can ask him to the exact same thing.
My second question is, as we are using ASM, for which i am gonna configure ASM after clusterware installation, should i install Openfiler??
Pls refer the enviroment information i provided above and make recommendations.
As of now i am using Jeffery Hunters guide to install the entire setup. You think the entire install guide goes well with my enviroment??
http://www.oracle.com/technology/pub/articles/hunter_rac11gr1_iscsi.html?rssid=rss_otn_articles
Kind regards
MKThanks for ur reply Mufalani,
You have managed to solve half part of my query. But still i am stuck with what kind of mount point i should ask the system admin to create for OCR and Voting disk. Should i go with the mount point he is mentioning??
Let me put forth few more questions here.
1. Is 280 MB ok for OCR and voting disks respectively??
2. Should i ask the system admin to create 4 voting disk mount points and two for ocr??
3. As mentioned by the system admin.
*/u01/shared_config/OCR_config*
*/u01/shared_config/voting_disk*
Is this ok for creating the ocr and voting disks?
4. Can i use OCFS2 file system for formating the disk instead of using them as RAW device!!?
5. As u mentioned that Openfiler is not needed for Configuring ASM... Could you provide me the links which will guide me to create partition disks, voting disks and ocr disks!! I could not locate them on the doc or else were. I did find a couple of them, but was unable to identify a suitable one for my envoirement.
Regards
MK -
Oracle RAC 11g. 3rd Voting disk mounting automatically without fstab
Hi,
We have a 2 node Oracle 11Gr2 Extened RAC database on Redhat Linux. We have a vote disk on each node and a 3rd vote disk on a separate site. The vote disk directories are NFS mounted. We have noticed that there is no entry in the fstab (on either RAC node) for the 3rd voting disk location, yet the directory is still mounted automatically on each RAC node at startup.
Can Oracle manage mounting the disks itself without using fstab? Oracle recommends using the fstab for mounting the directories and I have found nothing on Oracle mounting the directories in any other way other than fstab.
I am completely lost here. We need to do some configuration on the 3rd voting disk location and I need to find out how the disk is being mounted on the RAC nodes. Any help on this would be greatly appreciated. Thanks.
Rgs,
RobDid you check that rc.local file? Perhaps, the mount entries are in there.
HTH -
Dear all
I uninstall clusterware. And i want to install again that but when i made partition in windows 2003 then CVU fail the stage command.
I did the following things..
1) diskpart --->select Disk 1----> clean -->exit (both the nodes)
2) diskpart -->automount enable--->exit ---> restart (both the nodes)
3) Then i make four partition in one node. And see after restart node 2 have that partition with drive letter. I remove all the drive letter.
But CVU stage command failed. And if i run clusterware then it can get partition which has not previous OCR and voting. I think previous OCR and Voting disk could not clean.
Could u pls tell me how can i get solution.
MoinulCheck Metalink for this problem area ! Raise TAR
-
OCR and Voting Disk Migration to new media
Hello,
We need to move OCR,voting disk and ASM from one storage media to another .I think ASM related files are very easy to move/re map but how OCR and Voting Disk files will be migrated to the new storage media?
Thanks,
S.MannHi,
when you said:
"Move Voting Disk : run as root.
crsctl query css votedisk
crsctl add css votedisk new_backup_san_device
crsctl query css votedisk - Make sure the new device is added
crsctl delete css votedisk current_san_device_to_be_encrypted
crsctl query css votedisk - Make sure that the old one is removed "
I supose the new_backup_san_device could be a raw device??
In my system I have a 2 nodes cluster, oracle 10gR2, RAC and ASM
the ocr and voting disk are stored in /dev/raw/raw1 and /dev/raw/raw2
thoses 2 raw devices are mapped with LUNS in the first storade media.
We are about to change it..
So what must I do at this step? What are the logical steps I must done?
add the new LUNS in the nodes and map it as raw devices?
I have this at the moment:
crw-r----- 1 root oinstall 162, 1 Feb 8 17:33 /dev/raw/raw1
crw-r----- 1 root oinstall 162, 2 Feb 8 17:33 /dev/raw/raw2
crw-r----- 1 oracle oinstall 162, 3 Feb 8 17:33 /dev/raw/raw3
in the case of migration, I must add 3 new row devices?
as this?
crw-r----- 1 root oinstall 162, 1 Feb 8 17:33 /dev/raw/raw1
crw-r----- 1 root oinstall 162, 2 Feb 8 17:33 /dev/raw/raw2
crw-r----- 1 oracle oinstall 162, 3 Feb 8 17:33 /dev/raw/raw3
crw-r----- 1 root oinstall 162, 1 Feb 8 17:33 /dev/raw/raw4
crw-r----- 1 root oinstall 162, 2 Feb 8 17:33 /dev/raw/raw5
crw-r----- 1 oracle oinstall 162, 3 Feb 8 17:33 /dev/raw/raw6
That's it?
Thanks to help
Maybe you are looking for
-
if i type in one url, it just displays that url no matter what page or tab i have moved on on. the 'back' button is also greyed out and doesn't work. i'm using windows vista. this problem started a few days ago.
-
Compare different versions of a workflow template
Hi, How can we compare workflow templates? We need to compare the different versions available in our Quality and development systems for any kind of changes - 1. new steps added 2. steps deleted 3. other changes related to binding, events etc.. What
-
Css shows in live view, not in design view
Hi all- I'm new to dreamweaver and was trying to move a site I have already coded into dreamweaver, hopefully to be able to find errors but mostly to be able to update more quickly in the future. I've noticed one pecularity (at least to me!) - I have
-
When put() does not return
We're using Coherence 3.0/315. We've experienced a couple of failures in our system and tracked it down to sort of deadlock in our code. I say "sort of" because really the threads don't seem to be interlocked in a traditional deadlock, but rather it'
-
I 'm unable to cancel my month-to-month subscription
When trying to cancel my month-to-month plan / subscription I get an error messages staying I should try it later again. However later (1 day or 1 hour) still gives the same result. Sadly the chat with an agent is not available on the pages it is lis