Add disk in ASM
Hi,
on 11g R2 , UNIX, RAC
our ASM is in RAC, 4 instances.
I want to add a disk. My questions are :
-should I issu :
alter diskgroup data add disk 'D:\asmdisk\disk3';
on each instance ? Then four times ?
-should I restart :
startup mount
each instance (then four times) ?
Thank you.
before adding disk in asm,the status of disk(HEADER_STATUS) should be candidate.
means CANDIDATE - Disk is not part of a disk group and may be added to a disk group with the ALTER DISKGROUP statement.
and once its added then you can check the freespace in diskgroup as it should be increased by adding the disk and header_status changed to MEMBER;
Please close the thread if you feel you have the answer and keep the Oracle forum clean.
https://forums.oracle.com/forums/ann.jspa?annID=885
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 -
Hi folks,
I have one query why asm startwith with + sign? what happen add datafile file in table space,or add disk in disk group without using + sign ,please explain with error no.hello,
+ sign is to indicate the diskgroup you intended to place datafile. this apply to all database files.
without + sign,will be place in ORACLE_HOME/dbs directory. there will be NO error.
see example here: without using +
SQL> create tablespace test45 datafile 'temdg' size 10m;
Tablespace created.
SQL> select name from v$datafile;
NAME
/u01/app/oracle/product/11.2.0/dbhome_1/dbs/temdg
7 rows selected.
second example: with using + sign to specify diskgroup
SQL> create tablespace test55 datafile '+temdg' size 10m;
Tablespace created.
SQL> select name from v$datafile;
NAME
/u01/app/oracle/product/11.2.0/dbhome_1/dbs/temdg
+TEMDG/orcl/datafile/test55.261.844200359
8 rows selected.
HTH
Tobi
Tobi's Oracle DBA & UNIX Blog -
Dropping a Disk from ASM disk group
Hi Team,
I was dropping 10 disks from ASM , due to storage migration.
9 Disks I was dropped successfully, but 1 disk (/dev/oracleasm/disks/ST_OCR_VOTE02 ) was not able to recognize , it is part of which group..!!
That is not part of any group but still showing as member..!!! Please help . Not sure this is part of which group.
SQL> select GROUP_NUMBER,DISK_NUMBER,NAME,path,header_status,FAILGROUP from v$asm_disk where path='/dev/oracleasm/disks/ST_OCR_VOTE02';
GROUP_NUMBER DISK_NUMBER NAME PATH HEADER_STATU FAILGROUP
0 0 /dev/oracleasm/disks/ST_OCR_VOTE02 MEMBER
SQL>
0 17 NORMAL FORMER /dev/oracleasm/disks/STASM3_02 0 0
0 9 NORMAL FORMER /dev/oracleasm/disks/STASM1_01 0 0
0 10 NORMAL FORMER /dev/oracleasm/disks/STASM5_01 0 0
0 11 NORMAL FORMER /dev/oracleasm/disks/STASM4_01 0 0
0 12 NORMAL FORMER /dev/oracleasm/disks/STASM3_01 0 0
0 13 NORMAL FORMER /dev/oracleasm/disks/STASM2_01 0 0
0 14 NORMAL FORMER /dev/oracleasm/disks/STASM1_02 0 0
0 15 NORMAL FORMER /dev/oracleasm/disks/STASM2_02 0 0
0 16 NORMAL FORMER /dev/oracleasm/disks/STASM4_02 0 0
0 0 NORMAL MEMBER /dev/oracleasm/disks/ST_OCR_VOTE02 0 0
Thanks ManoharHi ,
As group_number of that disk is 0 ,it is not part of any mounted diskgroup in your system .
So,you cannot drop that disk .
May be sometime back due to some issue that disk was evicted ,but was not dropped properly ,so disk header still holds old diskgroup information.
kfed read <device_name>|egrep "kfbh.type|kfdhdb.hdrsts|kfdhdb.grpname"
above command will tell you the cause of MEMBER
To reuse that disk,
-- Validate same disk having similar status on all nodes of this cluster
-- if So,then to overwrite that disk header ,use FORCE option to create/add it into any existing diskgroup.
Regards,
Aritra -
Hello folks ?
I need to add a new disc in a RAC with ASM instance, there is a specific procedure?
Can i connect in any ASM instance with SQL-PLUS and execute the command ALTER DISKGROUP DADOS ADD DISK '/devices/disk*3', '/devices/disk*4';
SpaulonciASM instances in a RAC environment don't act independently, a diskgroup serving a RAC database is maintained by all participating ASM instances. So you don't add a disk to a particular instance. There's no need to shutdown ASM to add a disk, that's one of the ASM advantages.
Werner -
Hi,
on 10g R2 ,Unix HP and ASM 10.2
a new filesystem would be added by system (Unix administrator) what should I do as DBA to :
-see it in ASM ?
-be able to create datafiles on it ?
Thank you.Hi,
First you will have to find the new disk with fdisk -l
then you will have to create a partition, if not already done
fdisk /dev/<your_disk>Use oracleasm to create a disk and scan for the disk on the other nodes
oracleasm createdisk <DISKNAME> /dev/<your_disk>
oracleasm scandisksto make sure the disk exist you can use
oracleasm listdisksLog into ASM with sqlplus and run
alter diskgroup <your_diskgroup_name> ADD DISK '/dev/<your_disk>';you can look at "http://download.oracle.com/docs/cd/B28359_01/server.111/b31107/asmdiskgrps.htm#CHDBIFGA" for more info on how to admin ASM diskgroups.
Regards. -
How to add disk to disk group File System in oracle windows
Hi all
Please any body can help ... I need to know how can I add disk to disk group
I have Oralce 11g Database RAC Setup with 2 nodes node1 and node2 , ASM not enabled , Windows OS 2003 , I have shared storage (G, H and O ) My system administrator add additional SAN Storage (R) to my setup, how can I add the new disk to disk group.
Please helpI have Oralce 11g Database RAC Setup with 2 nodes node1 and node2 , ASM not enabled , Windows OS 2003 , I have shared storage (G, H and O ) My system administrator add additional SAN Storage (R) to my setup, how can I add the new disk to disk group.If ASM is not enabled that mean, Database is running on normal file system?
Hi thanks for you help.,,, But my system admnistrator already did thies steps,... I think my question was not clear enough
I mean after I add the disk group from O.S side what shall I do from Oracle Side? Since From windows explorer I can see the new drive.If the volumes are ready, you can use ASMCA to configure diskgroups. -
Hyper -V Win 8 Pro, media option -add disk is not available on some created VM
Hi,
installed Hyper-V on Windows Pro
1.I created VM generation 2 with win2012 server eval.
2.using sysprep to create clone
3. created 3 copy of the file
4.installed 3 machine from file (DC,node1,node2)
4.on DC created domain
5.joined node1 and node2 to domain
6.created cluster
When I was going to install SQL server from ISO to node1 and node2 I noticed that in media action option to attach disk is not available (it show no disk to display) on node1 and node2
However on DC machine I can attach ISO disk!
Why option to attach disk is not available on other machine and how make it available?
Currently I access disk from node1 and2 from domain using \\DC\D\setup.exe
P.S
few days ago I created 3 VM with Win2008R2 server (join then on domain and created cluster),add disk optiion availbale on all win2008R2 machines
Thank you
AlexHi AlexMtl,
Based on my knowledge , physical DVD only can be mapped to IDE controller in VM .
"you can only assign the physical CD/DVD drive to one VM at the same time (running VM)."
Similar thread :
http://social.technet.microsoft.com/Forums/windowsserver/en-US/b4e68fe6-3a7e-46f0-b15d-c90790ff3f71/unable-to-access-cddvd-on-second-vm?forum=winserverhyperv
Gen2 VM can add DVD device attach to SCSI controller and insert .ISO file (this file should be used by multiple VMs ).
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Hi,
Can anybody let me know how to add datafile using ASM
DB- ORACLE 10.2
OS-RHELSQL> select name from v$asm_diskgroup;
NAME
DATA1
DATA
Above we are having two asm diskgorup
SQL> alter tablespace users add datafile ‘+data1′ size 5M;
Tablespace altered.
SQL> select name from v$datafile;
NAME
+DATA1/nonasmtoasm/datafile/system.259.721108803
+DATA1/nonasmtoasm/datafile/undotbs1.261.721108865
+DATA1/nonasmtoasm/datafile/sysaux.260.721108841
+DATA1/nonasmtoasm/datafile/users.262.721108873
+DATA1/nonasmtoasm/datafile/users.269.721187971 -
Hi! I have recently dropped a disk in asm
DISK_NUMBER HEADER_STATU STATE TOTAL_MB/1024 NAME FAILGROUP LABEL PATH
3 MEMBER DROPPING 16,7998047 PITSM0_DG_NODATOS_0003 FG_JC2 /dev/rdisk/disk613
But the operation generates an error. My asm instance and database are generating logfiles and I dont know how to stop the operation or fix it.
SQL> select * from v$asm_operation;
GROUP_NUMBER OPERA STAT POWER ACTUAL SOFAR EST_WORK EST_RATE EST_MINUTES ERROR_CODE
2 REBAL ERRS 1 ORA-15041
The asm traces don't show nothing concrete
$ cat +ASM1_ora_17509.trm
@2|2|czasf4QM1"17509|+ASM1|
M/czasf4QM1~O1O2
@2|2|44csf4QM1"17509|+ASM1|
6/Dybsf4QM1~09Z
3?t7~01
SQL> select NAME, FREE_MB, TOTAL_MB from v$asm_disk where NAME like 'PITSM0_DG_NODATOS_0003' ;
NAME FREE_MB TOTAL_MB
PITSM0_DG_NODATOS_0003 4714 17203
SQL> select NAME, GROUP_NUMBER, STATE, TOTAL_MB, FREE_MB, (FREE_MB /TOTAL_MB)*100 AS PORCENTAJEFREE from v$asm_diskgroup ;
NAME GROUP_NUMBER STATE TOTAL_MB FREE_MB PORCENTAJEFREE
PITSM0_DG_RECO 3 MOUNTED 185640 153200 82,5253178
PITSM0_DG_CLUSTER 1 MOUNTED 86015 84989 98,8071848
PITSM0_DG_DATOS 4 MOUNTED 3619980 2802044 77,404958
PITSM0_DG_NODATOS 2 MOUNTED 51609 26629 51,5975896
SQL> select NAME, FREE_MB, TOTAL_MB from v$asm_disk where NAME like 'PITSM0_DG_NODATOS_%';
NAME FREE_MB TOTAL_MB
PITSM0_DG_NODATOS_0000 10959 17203
PITSM0_DG_NODATOS_0006 10956 17203
PITSM0_DG_NODATOS_0003 4714 17203Hi! thanks for answering
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit
I dont see nothing in alerts since yesterday
RDBMS:
Additional information: 1
Writing to the above trSun Jan 15 22:08:38 2012
SUCCESS: disk PITSM0_DG_NODATOS_0001 (1.4042269599) dropped from diskgroup PITSM0_DG_NODATOS
SUCCESS: disk PITSM0_DG_NODATOS_0002 (2.4042269597) dropped from diskgroup PITSM0_DG_NODATOS
SUCCESS: disk PITSM0_DG_NODATOS_0004 (4.4042269595) dropped from diskgroup PITSM0_DG_NODATOS
SUCCESS: disk PITSM0_DG_NODATOS_0005 (5.4042269596) dropped from diskgroup PITSM0_DG_NODATOS
SUCCESS: disk PITSM0_DG_NODATOS_0007 (7.4042269598) dropped from diskgroup PITSM0_DG_NODATOS
SUCCESS: disk PITSM0_DG_NODATOS_0008 (8.4042269600) dropped from diskgroup PITSM0_DG_NODATOS
SUCCESS: disk PITSM0_DG_NODATOS_0009 (9.4042269594) dropped from diskgroup PITSM0_DG_NODATOS
Mon Jan 16 01:00:00 2012
Clearing Resource Manager plan via parameter
ASM:
Tue Jan 10 22:04:25 2012
Non critical error ORA-00001 caught while writing to trace file "/aplicaciones/oracle/trc_asm01/diag/asm/+asm/+ASM1/trace/+ASM1_ora_2795.trc"
Error message: HPUX-ia64 Error: 28: No space left on device
Additional information: 1
Writing to the above trace file is disabled for now on...
Tue Jan 10 22:08:25 2012
Non critical error DIA-00001 caught while writing to trace file "/aplicaciones/oracle/
My FS was full due to traces
ASM trace files have no sense except this one, with more information:
cat +ASM1_ora_28435.trc
Trace file /aplicaciones/oracle/trc_asm01/diag/asm/+asm/+ASM1/trace/+ASM1_ora_28435.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Real Application Clusters and Automatic Storage Management options
ORACLE_HOME = /productos/oracle/asm1120/11.2.0
System name: HP-UX
Node name: tghch01a
Release: B.11.31
Version: U
Machine: ia64
Instance name: +ASM1
Redo thread mounted by this instance: 0 <none>
Oracle process number: 0
Unix process pid: 28435, image: oracle@tghch01a
*** 2012-01-16 14:23:23.998
Ioctl ASYNC_CONFIG error, errno = 1
Ioctl ASYNC_CONFIG error, errno = 1 -
Backup and Restore OCR,Voting Disk and ASM Disks in new SAN-10g RAC
Dear Friends,
I am using 10g R2 RAC serup on Linux
My OCR,Voting Disk and ASM Disk for DBF Files are on a SAN box
Now i am reorganising SAN by scrapping the entire SAN and cretaing new LUN's (It's a must)
so pleae let me know
1) how do i take backup of OCR and Voting Disk from existing SAN and how do i restore it in new LUN's after SAN reorganisation
2) how do i take backup of existing Database's from existing SAN and how do i restore it in new LUN's after SAN reorganisation.
I will be doing it in Planned downtime only
Regards,
DBFor step 1 you should following metalink doc.
For step 2 here is simple backup command script.
I have done this in windows for you.
D:\app\ranjit\product\11.2.0\dbhome_1\BIN>rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Feb 8 21:48:47 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1299593730)
RMAN> run
+{+
allocate channel c1 device type disk format 'D:\app\ranjit\rman\%U';
allocate channel c2 device type disk format 'D:\app\ranjit\rman\%U';
backup database;
backup current controlfile format 'D:\app\ranjit\rman\%U';
+}+
Regards -
Advantage of having OCR and Voting disk on ASM
What are advantages of putting OCR and Voting disk on ASM from 11g
well, other than the sharing thing, you dont have to go RAIDing an additional shared disk either. If you have properly configured ASM, redundancy should be built in as well, either soft or hard.
not sure what other advantages you may need. Theres the IO thing with ASM, buit thats not really an advantage persay with ocr and vote. I may be contradicted by others but Ive never seen performance hit of any kind attributed to ocr and vote on non-ASM disk. -
After add (in a wrong way) a new disk in ASM, cluster don´t start
Hi,
Environment:
Oracle RAC 10gR2
2 nodes windows 2003 advanced server (node1 called "database1" and node2 called "database2").
ASM
san storage
Case:
My client has tried to add a new disk (in a environment san) in ASM with the next steps:
1. database1 and database2 are up.
2. instance ASM1 from database is up and instance ASM2 from database2 is down (I don´t know why¿¿¿¿¿¿¿??????????).
3. add a new disc from san storage to instance ASM1. At the end, a lot of errors show in screen due to instance ASM2 was down.
4. client tried to up +ASM2 and then , all the cluster crashed.
5. reboot boths nodes database1 and database2 , and Windows 2003 Server don´t start well (hung up, due to services from oracle cluster are "automatically start"-
6. disable oracle services in "not automatically start" and windows 2003 server start well.
7. now oracle rac don´t start, ASM don start, instances don´t start ....
what can I do? any idea?
Regards.
LauraDid you try to bring the U1 and it's associated ASM instance up while the other node is shutdown? Are you using Oracle clusterware?
-
Please Help - When I try to add ASM Disk to ASM Diskgroup it crashes Server
We are using a Pillar SAN and have LUNS Created and are using the following multipath device: (I'm a DBA more then anything else... but I am rather familiar with linux .... SAN Hardware not so much)
Device Size Mount Point
/dev/dpda1 11G /u01
The Above device is working fine... Below are the ASM Disks being Created
Device Size Oracle ASM Disk Name
/dev/dpdb1 198G ORCL1
/dev/dpdc1 21G SIRE1
/dev/dpdd1 21G CART1
/dev/dpde1 21G SRTS1
/dev/dpdf1 21G CRTT1
I try to create to the first ASM Disk
/etc/init.d/oracleasm createdisk ORCL1 /dev/dpdb1
Marking disk "ORCL1" as an ASM disk: [FAILED]
So I check the oracleasm log:
#cat /var/log/oracleasm
Device "/dev/dpdb1" is not a partition
I did some research and found that this is a common problem with multipath devices and to work around it you have to use asmtool
# /usr/sbin/asmtool -C -l /dev/oracleasm -n ORCL1 -s /dev/dpdb1 -a force=yes
asmtool: Device "/dev/dpdb1" is not a partition
asmtool: Continuing anyway
now I scan and list the disks
# /etc/init.d/oracleasm scandisks
Scanning the system for Oracle ASMLib disks: [ OK ]
# /etc/init.d/oracleasm listdisks
ORCL1
Here is whats going on in /var/log/messages when I run the oracleasm scandisks command
# date
Fri Aug 14 13:51:58 MST 2009
# /etc/init.d/oracleasm scandisks
Scanning the system for Oracle ASMLib disks: [ OK ]
cat /var/log/messages | grep "Aug 14 13:5"
Aug 14 13:52:06 seer kernel: dpdb: dpdb1
Aug 14 13:52:06 seer kernel: dpdc: dpdc1
Aug 14 13:52:06 seer kernel: dpdd: dpdd1
Aug 14 13:52:06 seer kernel: dpde: dpde1
Aug 14 13:52:06 seer kernel: dpdf: dpdf1
Aug 14 13:52:06 seer kernel: dpdg: dpdg1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: printk: 30 messages suppressed.
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: sda : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sda : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sda: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sda: asking for cache data failed
Aug 14 13:52:06 seer kernel: sda: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sda:end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: Dev sda: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdb: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdb: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdb: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdb: sdb1
Aug 14 13:52:06 seer kernel: SCSI device sdc: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sdc: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdc: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdc: sdc1
Aug 14 13:52:06 seer kernel: SCSI device sdd: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdd: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdd: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdd: sdd1
Aug 14 13:52:06 seer kernel: SCSI device sde: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sde: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sde: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sde: sde1
Aug 14 13:52:06 seer kernel: SCSI device sdf: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdf: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdf: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdf: sdf1
Aug 14 13:52:06 seer kernel: SCSI device sdg: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdg: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdg: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdg: sdg1
Aug 14 13:52:06 seer kernel: SCSI device sdh: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdh: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdh: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdh: sdh1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sdi, logical block 0
Aug 14 13:52:06 seer kernel: sdi : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sdi : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sdi: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sdi: asking for cache data failed
Aug 14 13:52:06 seer kernel: sdi: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sdi:end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer last message repeated 4 times
Aug 14 13:52:06 seer kernel: Dev sdi: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdj: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdj: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdj: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdj: sdj1
Aug 14 13:52:06 seer kernel: SCSI device sdk: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sdk: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdk: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdk: sdk1
Aug 14 13:52:06 seer kernel: SCSI device sdl: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdl: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdl: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdl: sdl1
Aug 14 13:52:06 seer kernel: SCSI device sdm: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdm: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdm: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdm: sdm1
Aug 14 13:52:06 seer kernel: SCSI device sdn: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdn: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdn: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdn: sdn1
Aug 14 13:52:06 seer kernel: SCSI device sdo: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdo: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdo: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdo: sdo1
Aug 14 13:52:06 seer kernel: SCSI device sdp: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdp: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdp: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdp: sdp1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: sdq : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sdq : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sdq: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sdq: asking for cache data failed
Aug 14 13:52:06 seer kernel: sdq: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sdq:end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer last message repeated 5 times
Aug 14 13:52:06 seer kernel: Dev sdq: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdr: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdr: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdr: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdr: sdr1
Aug 14 13:52:06 seer kernel: SCSI device sds: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sds: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sds: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sds: sds1
Aug 14 13:52:06 seer kernel: SCSI device sdt: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdt: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdt: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdt: sdt1
Aug 14 13:52:06 seer kernel: SCSI device sdu: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdu: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdu: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdu: sdu1
Aug 14 13:52:06 seer kernel: SCSI device sdv: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdv: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdv: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdv: sdv1
Aug 14 13:52:06 seer kernel: SCSI device sdw: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdw: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdw: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdw: sdw1
Aug 14 13:52:06 seer kernel: SCSI device sdx: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdx: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdx: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdx: sdx1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: sdy : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sdy : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sdy: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sdy: asking for cache data failed
Aug 14 13:52:06 seer kernel: sdy: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sdy:end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer last message repeated 5 times
Aug 14 13:52:06 seer kernel: Dev sdy: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdz: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdz: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdz: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdz: sdz1
Aug 14 13:52:06 seer kernel: SCSI device sdaa: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sdaa: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdaa: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdaa: sdaa1
Aug 14 13:52:06 seer kernel: SCSI device sdab: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdab: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdab: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdab: sdab1
Aug 14 13:52:06 seer kernel: SCSI device sdac: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdac: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdac: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdac: sdac1
Aug 14 13:52:06 seer kernel: SCSI device sdad: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdad: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdad: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdad: sdad1
Aug 14 13:52:06 seer kernel: SCSI device sdae: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdae: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdae: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdae: sdae1
Aug 14 13:52:06 seer kernel: SCSI device sdaf: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdaf: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdaf: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdaf: sdaf1
Aug 14 13:52:06 seer kernel: scsi_wr_disk: unknown partition table
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sdy, sector 0
Here's some extra info:
# /sbin/blkid | grep asm
/dev/sdc1: LABEL="ORCL1" TYPE="oracleasm"
/dev/sdk1: LABEL="ORCL1" TYPE="oracleasm"
/dev/sds1: LABEL="ORCL1" TYPE="oracleasm"
/dev/sdaa1: LABEL="ORCL1" TYPE="oracleasm"
/dev/dpdb1: LABEL="ORCL1" TYPE="oracleasm"
I have learned that by excluding devices in the oracleasm configuration file I eliminate those I/O errors in /var/log/messages
# cat /etc/sysconfig/oracleasm
# This is a configuration file for automatic loading of the Oracle
# Automatic Storage Management library kernel driver. It is generated
# By running /etc/init.d/oracleasm configure. Please use that method
# to modify this file
# ORACLEASM_ENABELED: 'true' means to load the driver on boot.
ORACLEASM_ENABLED=true
# ORACLEASM_UID: Default user owning the /dev/oracleasm mount point.
ORACLEASM_UID=oracle
# ORACLEASM_GID: Default group owning the /dev/oracleasm mount point.
ORACLEASM_GID=oinstall
# ORACLEASM_SCANBOOT: 'true' means scan for ASM disks on boot.
ORACLEASM_SCANBOOT=true
# ORACLEASM_SCANORDER: Matching patterns to order disk scanning
ORACLEASM_SCANORDER="dp sd"
# ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan
ORACLEASM_SCANEXCLUDE="sdc sdk sds sdaa sda"
# ls -la /dev/oracleasm/disks/
total 0
drwxr-xr-x 1 root root 0 Aug 14 10:47 .
drwxr-xr-x 4 root root 0 Aug 13 15:32 ..
brw-rw---- 1 oracle oinstall 251, 33 Aug 14 13:46 ORCL1
Now I can go into dbca to create the ASM instance, which starts up fine... create a new diskgroup, I see ORCL1 as a provision ASM disk I select it ... Click OK
CRASH!!! Box hangs have to reboot it....
I have gotten myself to exactly the same point right before clicking OK and here is what is in the ASM alertlog so far
Fri Aug 14 14:42:02 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/oracle/product/11.1.0/db_1/dbs/arch
Autotune of undo retention is turned on.
IMODE=BR
ILAT =0
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.6.0.
Using parameter settings in server-side spfile /u01/app/oracle/product/11.1.0/db_1/dbs/spfile+ASM.ora
System parameters with non-default values:
large_pool_size = 12M
instance_type = "asm"
diagnostic_dest = "/u01/app/oracle"
Fri Aug 14 14:42:04 2009
PMON started with pid=2, OS id=3300
Fri Aug 14 14:42:04 2009
VKTM started with pid=3, OS id=3302 at elevated priority
VKTM running at (20)ms precision
Fri Aug 14 14:42:04 2009
DIAG started with pid=4, OS id=3306
Fri Aug 14 14:42:04 2009
PSP0 started with pid=5, OS id=3308
Fri Aug 14 14:42:04 2009
DSKM started with pid=6, OS id=3310
Fri Aug 14 14:42:04 2009
DIA0 started with pid=7, OS id=3312
Fri Aug 14 14:42:04 2009
MMAN started with pid=8, OS id=3314
Fri Aug 14 14:42:04 2009
DBW0 started with pid=9, OS id=3316
Fri Aug 14 14:42:04 2009
LGWR started with pid=6, OS id=3318
Fri Aug 14 14:42:04 2009
CKPT started with pid=10, OS id=3320
Fri Aug 14 14:42:04 2009
SMON started with pid=11, OS id=3322
Fri Aug 14 14:42:04 2009
RBAL started with pid=12, OS id=3324
Fri Aug 14 14:42:04 2009
GMON started with pid=13, OS id=3326
ORACLE_BASE from environment = /u01/app/oracle
Fri Aug 14 14:42:04 2009
SQL> ALTER DISKGROUP ALL MOUNT
Fri Aug 14 14:42:41 2009
At this point I don't want to click the OK until I am sure someone is in the office to reboot the machine manually if I do hang it again.... I hung it twice yesterday, however I did not have the devices excluded in the oracleasm configuration file as i do now
Edited by: user10193377 on Aug 14, 2009 3:23 PM
Well Clicking OK hun it again and I am waiting to get back into it, to see what new information might be gleened
Does anyone have any ideas on what to check or where to look????? Will update more once I can log back inHi Mark,
It looks like something is not correct with your raw device partition based on the error messages:
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sda: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sda: asking for cache data failed
Aug 14 13:52:06 seer kernel: sda: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sda:end_request: I/O error, dev sda, sector 0
It could be a number of things. I would check with your vendor and Oracle support to see if the multipath software drive is supported and if there is a potential workaround for ASM. Sorry this is not quite the solution, but its what jumps to mind based on issues with multipath software and storage vendors for ASM with Linux and Oracle. Have you checked the validation matrix available on Metalink?
Cheers,
Ben -
Add LUN into asm in rac (Solaris)
I have a 2 node oracle rac with asm . I have to add new LUN to asm to increase space in asm disk group I have done the following on node1
Ran format
Created the partition on slice4 on the new device file corresponding to the LUN
Created the block and character device file like RAC_ORACLE_data_05 under /dev/dsk/oracle and /dev/rdsk/oracle (where the other device files used by ASM also reside) using the major and minor number of the new LUN
Changed the permissions to oracle:dba
The new LUN is now visible through the ASM on node 1 as RAC_ORACLE_data_05
My question is what steps I need to carry out on node 2 of the cluster
The disk is visible on node 2 as well
The disk is already showing up with the partitions as created through node 1
Do I have to create the device file under /dev/dsk/oracle with the major minor numbers as shown on node 2 for the LUN
TIA
RavinderAlmost never use Solaris (last Oracle db I managed on Solaris was 10 years ago). And as this is not a Solaris o/s forum space, you should not expect quick answers to your Solaris o/s questions (which has little to do with ASM).
A comment though on what needs to be done at o/s level to satisfy RAC/ASM requirements.
ASM does not care for device names. Device names do not need to be persistent before and after reboots. Device names do not need to be persistent across RAC nodes in a cluster.
ASM simply needs to
a) be able to discover the device
b) be able to open the device
This means that the device name needs to match the ASM disk discovery string (or vice versa) across all RAC nodes/ASM instances. And that the device permissions need to allow access read/write access to ASM.
ASM enumerates devices it can I/O using its discovery string. For each device, ASM opens the device. It then reads the ASM disk label of the disk. If there is a valid label, ASM knows the disk name, status, and failgroup and diskgroup this disk belongs to. If no label, ASM treats it as a candidate disk.
So from an o/s perspective - a cluster LUN/disk needs to be visible on all nodes, in order to use that disk for RAC/grid storage. Actual device name is not important.
So whatever you did on node 1 to make that new LUN available to ASM, you need to do on node 2 and others.
I have 2 bash scripts I feel are essential to managing a RAC. The 1st script enables me to execute a command on all RAC nodes. The 2nd script enables me to copy/distribute a local file to all other RAC nodes.
So using these scripts and dealing with Linux as o/s, I would determine whether the new disk/LUN is seen by all RAC nodes, and whether the permissions are correct for ASM usage.
If not, I will use the 2nd script to distribute the config file(s) needed to configure the other RAC nodes with the same changes (on Linux this typically would be /etc/multipath.conf). And then use the 1st script to enable those changes on all RAC nodes (e.g. by restarting multipathd).
Maybe you are looking for
-
In Oracle SQL, cannot use column in select statement and order by
Hi, Is there a work around for this. Thanks in advance Pablo.
-
Using ACE RHI to inject a default route
I think I posted this onto the wrong Forum. Anyone able to advise here? SteveK. Posted by: stevek1 - Network Administrator, Dept Natural Resources and Mines Apr 18, 2008, 12:04am PST Hi Folks, I need to provide internal devices with active-active acc
-
Hi, I've been trying to pinpoint why our LMS 3.2 Ciscoworks server shuts down all LMS processes on occasion. The following is displayed repeatedly within the daemonsbackup.log 08/Nov/2009 03:17:16:265 ERROR ? ? - URN_NOT_FOUND : urn "ogs_server_urn"
-
Instantiating MXML class in AS3
I have a simple MXML component: -- code -- 'MyClass' <mx:Canvas ... creationPolicy="none" ... > <mx:HBox id="innerPanel" > <mx:Canvas ... /> </mx:HBox> </mx:Canvas> -- /code -- I'm trying to instantiate this in AS3 as so: -- code -- var myCla
-
Trend-Micro Smart Surfing for Mac
I know that malware is not a big concern for Mac users, yet. However, I am interested in trying new products as they come out. I use Trend-Micro products for Windows at work on a daily basis and they are a fantastic company when it comes to malware p