Skip to main content

ORA-15040: diskgroup is incomplete


<<Back to Oracle ASM Main Page

ORA-15040: diskgroup is incomplete

SQL> startup
ORA-00099: warning: no parameter file specified for ASM instance
ASM instance started
Total System Global Area 1140850688 bytes
Fixed Size                  8629704 bytes
Variable Size            1107055160 bytes
ASM Cache                  25165824 bytes
ORA-15110: no diskgroups mounted

Reason:

The reason of this error is simply the ASM is not able to find the some or all the disks.

Solution:
Investigate and make all the disks available to ASM to mount the disk group.
Make sure the disks has proper permissions.
If you are using AFD check following services are online
oracleacfs
oracleadvm
oracleoks 
oracleafd  

 Source of Problem: Issue started after restart of the server

 After restarting the server when I tried to start the ASM instance its started throwing error. ORA-15110: no diskgroups mounted
Investigation in my Case


Step1> ASM Logfile Scanning 

 Looked in the ASM log file and noticed following errors 

 WARNING: using default parameter settings without any parameter file
NOTE: remote asm mode is local (mode 0x301; from cluster type)
ERROR: Unable to get logical block size for spfile '+DG_TST_DATA/ASM/ASMPARAMETERFILE/registry.253.985607873'.

So it was very clear that ASM was not able to find the parameter file ( and yes that's what I expected because the parameter file reside in DG which was not mounted). So I decided to grab the parameters from last restart of ASM Instance and create the pfile and start the ASM with pfile.

Step2> Constructing of PFILE and Attempting to Start ASM with PFILE

From ASM Alert Log
Using parameter settings in server-side spfile +DG_TST_DATA/ASM/ASMPARAMETERFILE/registry.253.985607873
System parameters with non-default values:
  large_pool_size          = 12M
  remote_login_passwordfile= "EXCLUSIVE"
  asm_diskstring           = "AFD:*"
  asm_diskgroups           = "DG_TST_FRA"
  asm_diskgroups           = "DG_TST2_FRA"
  asm_diskgroups           = "DG_TST2_DATA"
  asm_diskgroups           = "DG_TEST"
  asm_power_limit          = 1

I created a pfile with highlighted parameters in bold above and tried to start the ASM instance again.

SQL> startup pfile='/u01/oragrid/12.2.0.1/grid/dbs/init+ASM.ora';
ASM instance started
Total System Global Area 1140850688 bytes
Fixed Size                  8629704 bytes
Variable Size            1107055160 bytes
ASM Cache                  25165824 bytes
ORA-15032: not all alterations performed
ORA-15017: diskgroup "DG_TST_FRA" cannot be mounted
ORA-15040: diskgroup is incomplete
ORA-15017: diskgroup "DG_TST2_FRA" cannot be mounted
ORA-15040: diskgroup is incomplete
ORA-15017: diskgroup "DG_TST2_DATA" cannot be mounted
ORA-15040: diskgroup is incomplete
ORA-15017: diskgroup "DG_TEST" cannot be mounted
ORA-15040: diskgroup is incomplete

The error is still present


AS ROOT USER

Step3>Cross Check DISK at OS Level and 

#ls -lrt /dev/xvd*
Everything was fine

Step4> Validate if the DISKS are visible to ASM AFD

Logged in as root user and cross checked the disk. Everything seems fine. Even disks are visible to ASM
# export ORACLE_HOME=/u01/oragrid/12.2.0.1/grid
# export ORACLE_SID=+ASM
# export PATH=$PATH:$HOME/.local/bin:$HOME/bin:$ORACLE_HOME/bin
# asmcmd afd_lslbl
--------------------------------------------------------------------------------
Label                     Duplicate  Path
================================================================================
DISK011                               /dev/xvdd11
DISK012                               /dev/xvdd12
DISK013                               /dev/xvdd13
DISK014                               /dev/xvdd14
DISK015                               /dev/xvdd15
DISK10                                /dev/xvdd10
DISK11                                /dev/xvdc11
DISK12                                /dev/xvdc12
DISK13                                /dev/xvdc13
DISK14                                /dev/xvdc14
DISK15                                /dev/xvdc15

Step5> Validate if the DISKS are listed under  /dev/oracleafd/disks.
#ls -lrt /dev/oracleafd/disks
Nothing returned 
Note:- There was no disks in this directory and that's the issue


Step6> Check if the ACFS related modules are loaded

#lsmod | grep acfs
Nothing returned 

 #lsmod | grep oracle
oracleafd             212992  1

That's it. Now I can see there is no acfsload  service running and that's the issue.

Step6> Start the ACFSLOAD module 

 #acfsload start 

# lsmod | grep oracle
oracleacfs           4616192  0
oracleadvm            782336  1
oracleoks             655360  2 oracleacfs,oracleadvm
oracleafd             212992  1

Login as ASM owner and start the ASM instance.
$sqlplus "/as sysasm"
SQL> shut abort
SQL> startup

ASM instance started successfully. All the disks are now visible to ASM and ASM was able to mount the diskgroups successfully

Comments

  1. UnknownAugust 1, 2020 at 4:30 PM

    I had the same issue but on RHEL8 where I could not use acfsload. I got the ACFS-9459 error which seem to indicate that 'ADVM/ACFS is not supported on this OS Version'. In my case the /dev/sda* disks were owned by root:root. I had to change ownership to oracle:dba. Once I did that the disks mounted. no issues. I'm going to find out how to keep the ownership to oracle:dba. This seems to have reverted after a reboot.

    ReplyDelete
  2. QkaModeAugust 31, 2022 at 4:26 AM

    for printer drivers: drivers for printer

    ReplyDelete

Post a Comment

Popular posts from this blog

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the serve...
Post a Comment
Read more

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco...
7 comments
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.
Post a Comment
Read more

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container
Post a Comment
Read more

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database (disabled)       ORA-16905: The member was not enabled yet. Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL>  show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 38 seconds ago)
Post a Comment
Read more

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE;   System altered.
Post a Comment
Read more

Starting RMAN and connecting to Database

  <<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P  target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that  you have proper TNS sentry...
Post a Comment
Read more

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02          ...
7 comments
Read more

ORA-46655: no valid keys in the file from which keys are to be imported

<<Back to DB Administration Main Page SQL> administer key management import encryption keys with secret "xxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxx" with backup; administer key management import encryption keys with secret "xxxxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxxxx" with backup * ERROR at line 1: ORA-46655: no valid keys in the file from which keys are to be imported Cause: Either the keys to be imported already present in the target database or correct container (PDB) is not set. Solution: In my case I got the error because I attempted to import the keys for newly plugged database PDB02 from CDB$ROOT container. To Solve the issue just switched to the correct container and re run the import. SQL> show con_name CON_NAME ------------------------------ CDB$ROOT <===Wrong Container selected  SQL> alter session set container=PDB02; Session alt...
Post a Comment
Read more