Oracle X9M ORA-15001 ORA-15018問題處理
資料庫版本: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.log
Errors in file /u01/app/oracle/diag/rdbms/crmcdb/cdmcrm1/trace/cdbcrm1_m002_197778.trc:
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
...
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例項中沒有+DA他的磁碟組。
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-
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/28373936/viewspace-2928536/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Oracle一體機x9m ORA-00800處理Oracle
- Oracle啟動問題處理Oracle
- Oracle壞塊問題處理Oracle
- crontab對oracle操作問題處理Oracle
- oracle SP2-問題處理Oracle
- ORACLE問題處理十個指令碼Oracle指令碼
- Oracle delete 高水位線處理問題Oracledelete
- Oracle日常問題處理ORA-04031Oracle
- oracle taf unknown 問題處理過程Oracle
- ORACLE懸疑分散式事務問題處理Oracle分散式
- linux處理oracle問題常用命令LinuxOracle
- Oracle CPU使用率過高問題處理Oracle
- Oracle_dg歸檔丟失問題處理Oracle
- Oracle資料庫無效物件問題處理Oracle資料庫物件
- 處理問題的方法
- perl中文處理問題
- 漢字處理問題?
- xml處理的問題XML
- 貨品問題處理
- [git] git問題處理Git
- oracle系統表空間過大問題處理Oracle
- Oracle資料庫中的逐行處理問題NEOracle資料庫
- 近期處理的Oracle資料庫問題總結Oracle資料庫
- oracle bdump 下.trc檔案過大問題處理Oracle
- ORACLE 11G EM 配置命令及問題處理Oracle
- Oracle日常問題處理-資料庫無法啟動Oracle資料庫
- pyinstaller打包cx_Oracle庫問題處理記錄Oracle
- Oracle 記一次ORA-00001問題處理Oracle
- Oracle全部索引丟失導致的效率問題處理Oracle索引
- oracle鎖表問題處理 v$lock v$locked_objectOracleObject
- ORACLE LINUX 6 安裝telnet包問題處理OracleLinux
- 解決Oracle中Exp/Imp大量資料處理問題Oracle
- golang json處理問題GolangJSON
- 併發問題處理方式
- ASMCMD處理問題一則ASM
- mysql的處理能力問題MySql
- RMAN處理split block問題BloC
- mysql問題處理兩則MySql