AskTom

Hi,
today I had a problem to discover new database in Grid Control version 10.2.0.4.
When I tri to discover a database I’ve got an error:

oracle.sysman.emSDK.emd.comm.CommException: Connection refused

Solution:
Try to unsecure and secure agent on the host what you want to add in GC

./emctl unsecure agent
./emctl secure agent
./emctl upload agent

Regards,

Tom

Yesterday we lost production database due a harware error. When i tried to restore database from backup I faced same errors.

1) first error
ORA-15096: lost disk write detected
Cause: A failure either by disk hardware or disk software caused a disk write to to be lost, even though ASM received acknowledgement that the write completed. Alternatively, a clustering hardware failure or a clustering software failure resulted in an ASM instance believing that another ASM instance had crashed, when in fact it was still active.
Action: The disk group is corrupt and cannot be recovered. The disk group must be recreated, and its contents restored from backups.

Solution:
Recreate ASM disks
/etc/init.d/oracleasm createdisk DATA1 /dev/disk/by-name/dae1

you can check it by:
/etc/init.d/oracleasm listdisks
DATA1

2) Second error
- I was unable to mount diskgroup in ASM
alter diskgroup data mount;
alter diskgroup data mount
*
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup “DATA”

Solution:
from sqlplus for ASM instance

SQL>create diskgroup DATA external redundancy disk ‘ORCL:DATA1′;
SQL>alter diskgroup data mount;

This error is related to error above
ASMCMD-08001: diskgroup ‘data’ does not exist or is not mounted

DONE
Now you have ASM instance up and you can restore database.

Regards,

Tom

After migration I tried to startup ASM database but there was any error during startup

ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup “DATA”

oracle@server:~> oerr ora 15063
15063, 00000, “ASM discovered an insufficient number of disks for diskgroup \”%s\”"
// *Cause:  ASM was unable to find a sufficient number of disks belonging to the
//          diskgroup to continue the operation.
// *Action: Check that the disks in the diskgroup are present and functioning,
//          that the owner of the ORACLE binary has read/write permission to
//          the disks, and that the ASM_DISKSTRING initialization parameter
//          has been set correctly.  Verify that ASM discovers the appropriate
//          disks by querying V$ASM_DISK from the ASM instance.

1)Check that the disks in the diskgroup are present and functioning

select DG.GROUP_NUMBER “G.NO”,DG.NAME,D.DISK_NUMBER,D.MOUNT_STATUS,
D.HEADER_STATUS,DG.TYPE,D.NAME,D.PATH FROM V$ASM_DISK D,V$ASM_DISKGROUP DG
where DG.GROUP_NUMBER=D.GROUP_NUMBER;

–> in my case there now rows are selected

2) check if is averythink ok on OS level

oracle@server:/opt> /etc/init.d/oracleasm listdisks

–> nothing. It’s strange so let’s try to scan all disks

3) check ASM disks
oracle@server:/etc/init.d> /etc/init.d/oracleasm scandisks
Scanning system for ASM disks:                                       done

4) now we have all disks
oracle@server:/etc/init.d> /etc/init.d/oracleasm listdisks
DATA1
DATA2

5) now we must mount diskgroup manually from sqlplus

alter diskgroup data mount;

6) ASM is up and running

Regards,

Tom