数据库版本：Oracle Database 19.7
操作系统：Red Hat Enterpise Linux Server release 7.9（Maipo）
问题描述：数据库日志报 ORA-15001: diskgroup "DATA" does not exist or is not mounted和 ORA-15018: diskgroup cannot be created
问题原因： RMAN配置中 SNAPSHOT CONTROLFILE NAME设置的+DATA磁盘组不存在
解决方案： 重新进行RMAN的 SNAPSHOT CONTROLFILE NAME设置
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+DATAC1/snapcf_cdbcrm.f'; 分析过程： 1、检查数据库日志alert_cdbcrm1.logErrors in file /u01/app/oracle/diag/rdbms/crmcdb/cdmcrm1/trace/cdbcrm1_m002_197778.trc:ORA-15001: diskgroup "DATA" does not exist or is not mountedORA-15018: diskgroup cannot be createdORA-15001: diskgroup "DATA" does not exist or is not mountedORA-15001: diskgroup "DATA" does not exist or is not mountedORA-15018: diskgroup cannot be createdORA-15001: diskgroup "DATA" does not exist or is not mountedORA-15001: diskgroup "DATA" does not exist or is not mountedORA-15018: diskgroup cannot be createdORA-15001: diskgroup "DATA" does not exist or is not mountedORA-15001: diskgroup "DATA" does not exist or is not mountedORA-15018: diskgroup cannot be created...DATA磁盘组不存在，磁盘组创建失败。 2、检查trace日志cdbcrm_m002-1977.trc Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Version 19.7.0.0.0 Build label: RDBMS_19.7.0.0.0DBRU_LINUX.X64_200403 ORACLE_HOME: /u01/app/oracle/product/19.7.0.0/dbhome_1 System name: Linux Node name: bj9dbadm01.sh.com Release: 4.14.35-2047.514.5.1.2.el7uek.x86_64 Version: #2 SMP Thu Jul 28 15:33:31 PDT 2022 Machine: x86_64 Storage: Exadata Instance name: crmcdb1 Redo thread mounted by this instance: 1 Oracle process number: 148 Unix process pid: 197778, image: oracle@: bj9dbadm01.sh.com (M002)... *** 2022-12-02T11:44:15.546198+08:00 *** MODULE NAME:(MMON_SLAVE) 2022-12-02T11:44:15.546228+08:00 *** ACTION NAME:(Intensive AutoTask Dispatcher) 2022-12-02T11:44:15.546232+08:00 *********** START A RUN OF [Intensive AutoTask Dispatcher] ************* *********** END A RUN ************* *** 2022-12-02T11:45:15.770130+08:00 *** MODULE NAME:(MMON_SLAVE) 2022-12-02T11:45:15.770161+08:00 *** ACTION NAME:(KDILM background CLeaNup) 2022-12-02T11:45:15.770165+08:00 *********** START A RUN OF [KDILM background CLeaNup] ************* *********** END A RUN ************* *** 2022-12-02T11:46:15.930394+08:00 *********** START A RUN OF [KDILM background CLeaNup] ************* *********** END A RUN ************* *** 2022-12-02T11:47:16.089940+08:00 *********** START A RUN OF [KDILM background CLeaNup] ************* *********** END A RUN ************* *** 2022-12-02T11:49:16.408540+08:00 *** MODULE NAME:(MMON_SLAVE) 2022-12-02T11:49:16.408571+08:00 *** ACTION NAME:(Autobackup Control File) 2022-12-02T11:49:16.408575+08:00 *********** START A RUN OF [Autobackup Control File] ************* 2022-12-02 11:49:16.530 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.530 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.531 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.532 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.532 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.532 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.533 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.533 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.533 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.534 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.534 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.534 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.534 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.535 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.535 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.535 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.536 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.536 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.536 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.537 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.537 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.538 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.538 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.538 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.539 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.539 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.539 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.539 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.540 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.540 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.540 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.541 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.541 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.541 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.542 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.542 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.542 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.543 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 2022-12-02 11:49:16.543 :kfncTraceReturn(): call failed; [kfncGroupUse] flags=0x0 ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15018: diskgroup cannot be created ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15018: diskgroup cannot be created ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15018: diskgroup cannot be created ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15018: diskgroup cannot be created ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15018: diskgroup cannot be created ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15018: diskgroup cannot be created ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mou 2022-12-02 11:49:16.543*:KRB:krbm.c@5636:krbmdabCbk(): ******************** WARNING ************************** The errors during server control file autobackup are not fatal, as it is attempted after sucessful completion of the command. However, it is recomended to take an RMAN control file backup as soon as possible because the autobackup failed with the following error: ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15018: diskgroup cannot be created ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15018: diskgroup cannot be created ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15018: diskgroup cannot be created ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" ******************** END OF WARNING ******************* <error barrier> at 0x7ffe276bc0a0 placed krbm.c@5998 ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15018: diskgroup cannot be created ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15018: diskgroup cannot be created ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15018: diskgroup cannot be created ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15018: diskgroup cannot be created ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15018: diskgroup cannot be created ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15018: diskgroup cannot be created ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA *********** END A RUN ************* *** 2022-12-02T11:51:16.793893+08:00 *** MODULE NAME:(MMON_SLAVE) 2022-12-02T11:51:16.793924+08:00 *** ACTION NAME:(KDILM background CLeaNup) 2022-12-02T11:51:16.793928+08:00 *********** START A RUN OF [KDILM background CLeaNup] ************* *********** END A RUN ************* *** 2022-12-02T11:52:16.980931+08:00 *** MODULE NAME:(MMON_SLAVE) 2022-12-02T11:52:16.980961+08:00 *** ACTION NAME:(Intensive AutoTask Dispatcher) 2022-12-02T11:52:16.980966+08:00 *********** START A RUN OF [Intensive AutoTask Dispatcher] ************* *********** END A RUN ************* *** 2022-12-02T11:53:17.242807+08:00 *** MODULE NAME:(MMON_SLAVE) 2022-12-02T11:53:17.242837+08:00 *** ACTION NAME:(Automatic Report Flush) 2022-12-02T11:53:17.242841+08:00 *********** START A RUN OF [Automatic Report Flush] ************* *********** END A RUN ************* *** 2022-12-02T11:54:17.563335+08:00 *** MODULE NAME:(MMON_SLAVE) 2022-12-02T11:54:17.563362+08:00 *** ACTION NAME:(Intensive AutoTask Dispatcher) 2022-12-02T11:54:17.563366+08:00 *********** START A RUN OF [Intensive AutoTask Dispatcher] ************* *********** END A RUN ************* *********** START A RUN OF [KDILM background CLeaNup] ************* *** 2022-12-02T11:55:17.754230+08:00 *** MODULE NAME:(MMON_SLAVE) 2022-12-02T11:55:17.754246+08:00 *** ACTION NAME:(KDILM background CLeaNup) 2022-12-02T11:55:17.754250+08:00 *********** END A RUN ************* *** 2022-12-02T11:56:17.913948+08:00 *** MODULE NAME:(MMON_SLAVE) 2022-12-02T11:56:17.913978+08:00 *** ACTION NAME:(KDILM background EXEcution) 2022-12-02T11:56:17.913983+08:00...从trace可以看到，数据库控制文件自动备份时kfncTraceReturn(): call failed，ORA-15001，ORA-15018。 3、检查ASM实例参数+ASM1.__asm_max_connected_clients=8+ASM2.__asm_max_connected_clients=8+ASM1.__oracle_base='/u01/app/grid'#ORACLE_BASE set from in memory value+ASM2.__oracle_base='/u01/app/grid'#ORACLE_BASE set from in memory value*.asm_diskgroups='RECOC1'#Manual Mount*.asm_diskstring='o/*/DATAC1_*','o/*/RECOC1_*','/dev/exadata_quorum/*'*.asm_power_limit=4*.audit_sys_operations=TRUE*.audit_syslog_level='LOCAL0.INFO'+ASM1.cluster_interconnects='192.168.30.1:192.168.30.2'+ASM2.cluster_interconnects='192.168.30.3:192.168.30.4'*.large_pool_size=12M*.memory_target=0*.pga_aggregate_target=419430400*.processes=1024*.remote_login_passwordfile='EXCLUSIVE'*.sga_target=3221225472*.use_large_pages='TRUE' ASM实例中没有+DATA的磁盘组。 4、检查RMAN配置 RMAN> show all; using target database control file instead of recovery catalog RMAN configuration parameters for database with db_unique_name CRMCDB are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP ON; # default CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+DATA/snapcf_crmcdb.f'; SNAPSHOT CONTROLFILE NAME设置在+DATA磁盘组下，该磁盘组不存在。 小结：rman配置SNAPSHOT CONTROLFILE NAME时设置的ASM磁盘组不存在，控制文件自动配置时找不到该磁盘组，数据库日志报ORA-15001 ORA-15018。生产环境设置任何参数和进行所以配置时，都应该要仔细核对和复核，变更前要在测试环境进行严格测试，准备详细的变更方案。 -the end-
