AIX使用LV创建ASM磁盘组-mysql教程-PHP中文網

首頁

資料庫

mysql教程

AIX使用LV创建ASM磁盘组

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

Jun 07, 2016 pm 03:56 PM

aiasmcreate使用創建磁碟

CREATE ASM ON AIX LV DEVICE
OS:AIX 6100-03
ASM版本 10205
# lspv
hdisk0 000d295a6d68902b rootvg active
hdisk1 000d2e62ac906f43 rootvg active
hdisk2 000d2e629b38c89d datavg active
hdisk3 none None
hdisk4 none None

# lsvg
rootvg
datavg

# chdev -l hdisk3 -a pv=yes --创建PV
hdisk3 changed
hdisk3已识别PVID
# lspv
hdisk0 000d295a6d68902b rootvg active
hdisk1 000d2e62ac906f43 rootvg active
hdisk2 000d2e629b38c89d datavg active
hdisk3 000d2e621c735061 None
hdisk4 none None

创建VG:
# mkvg -y asmvg hdisk3
asmvg

# lsvg -o
asmvg
datavg
rootvg

创建LV
mklv -y lv_asm1 asmvg 8
mklv -y lv_asm2 asmvg 8
mklv -y lv_asm3 asmvg 8
mklv -y lv_asm4 asmvg 8

# mklv -y lv_asm4 asmvg 8
lv_asm1
# mklv -y lv_asm2 asmvg 8
lv_asm2
# mklv -y lv_asm3 asmvg 8
lv_asm3
# mklv -y lv_asm4 asmvg 8
lv_asm4
修改权限
chown oracle.dba /dev/rlv_asm1 chown oracle.dba/dev/rlv_asm2 chown oracle.dba/dev/rlv_asm3 chown oracle.dba/dev/rlv_asm4
查看ASM设备
$ kfod status=TRUE asm_diskstring='/dev/rlv*' disk=all
--------------------------------------------------------------------------------
Disk Size Header Path
================================================================================
1: 256 Mb CANDIDATE /dev/rlv_asm1
2: 256 Mb CANDIDATE /dev/rlv_asm2
3: 256 Mb CANDIDATE /dev/rlv_asm3
4: 256 Mb CANDIDATE /dev/rlv_asm4
--------------------------------------------------------------------------------
ORACLE_SID ORACLE_HOME
================================================================================
+ASM /oracle/product/10.2.0/+ASM

创建磁盘组：
create diskgroup data external redundancy disk '/dev/rlv_asm1','/dev/rlv_asm2','/dev/rlv_asm3','/dev/rlv_asm4';

SQL> create diskgroup data external redundancy disk '/dev/rlv_asm1','/dev/rlv_asm2','/dev/rlv_asm3','/dev/rlv_asm4';
create diskgroup data external redundancy disk '/dev/rlv_asm1','/dev/rlv_asm2','/dev/rlv_asm3','/dev/rlv_asm4'
*
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15031: disk specification '/dev/rlv_asm4' matches no disks
ORA-15014: location '/dev/rlv_asm4' is not in the discovery set
ORA-15031: disk specification '/dev/rlv_asm3' matches no disks
ORA-15014: location '/dev/rlv_asm3' is not in the discovery set
ORA-15031: disk specification '/dev/rlv_asm2' matches no disks
ORA-15014: location '/dev/rlv_asm2' is not in the discovery set
ORA-15031: disk specification '/dev/rlv_asm1' matches no disks
ORA-15014: location '/dev/rlv_asm1' is not in the discovery set

create diskgroup data external redundancy disk '/dev/rlv_asm*';

SQL> create diskgroup data external redundancy disk '/dev/rlv_asm*';
create diskgroup data external redundancy disk '/dev/rlv_asm*'
*
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15031: disk specification '/dev/rlv_asm*' matches no disks
ORA-15014: location '/dev/rlv_asm4' is not in the discovery set
ORA-15014: location '/dev/rlv_asm3' is not in the discovery set
ORA-15014: location '/dev/rlv_asm2' is not in the discovery set
ORA-15014: location '/dev/rlv_asm1' is not in the discovery set

SQL> alter system set asm_diskstring='/dev/rlv_asm*';

System altered.

SQL> create diskgroup data external redundancy disk '/dev/rlv_asm*';

Diskgroup created.

查看alter日志：
Wed May 21 10:08:57 GMT+08:00 2014SQL> create diskgroup data external redundancy disk '/dev/rlv_asm1','/dev/rlv_asm2','/dev/rlv_asm3','/dev/rlv_asm4'
Wed May 21 10:08:57 GMT+08:00 2014ERROR: diskgroup DATA was not created
Wed May 21 10:11:46 GMT+08:00 2014SQL> create diskgroup data external redundancy disk '/dev/rlv_asm*'
Wed May 21 10:11:46 GMT+08:00 2014ERROR: diskgroup DATA was not created
Wed May 21 10:15:40 GMT+08:00 2014SQL> create diskgroup data external redundancy disk '/dev/rlv_asm*'
Wed May 21 10:15:40 GMT+08:00 2014ERROR: diskgroup DATA was not created
Wed May 21 10:16:20 GMT+08:00 2014ALTER SYSTEM SET asm_diskstring='/dev/rlv_asm*' SCOPE=BOTH;
Wed May 21 10:16:30 GMT+08:00 2014SQL> create diskgroup data external redundancy disk '/dev/rlv_asm*'
Wed May 21 10:16:30 GMT+08:00 2014NOTE: initializing header on grp 1 disk DATA_0000
NOTE: initializing header on grp 1 disk DATA_0001
NOTE: initializing header on grp 1 disk DATA_0002
NOTE: initializing header on grp 1 disk DATA_0003
NOTE: PST update: grp = 1
Wed May 21 10:16:30 GMT+08:00 2014NOTE: group DATA: initial PST locations: disk 0000 (PST copy 0)
Wed May 21 10:16:30 GMT+08:00 2014NOTE: cache registered group DATA number=1 incarn=0x1649be7b
NOTE: cache opening disk 0 of grp 1: DATA_0000 path:/dev/rlv_asm1
NOTE: cache opening disk 1 of grp 1: DATA_0001 path:/dev/rlv_asm2
NOTE: cache opening disk 2 of grp 1: DATA_0002 path:/dev/rlv_asm3
NOTE: cache opening disk 3 of grp 1: DATA_0003 path:/dev/rlv_asm4
NOTE: cache creating group 1/0x1649BE7B (DATA)
NOTE: cache mounting group 1/0x1649BE7B (DATA) succeeded
NOTE: allocating F1X0 on grp 1 disk DATA_0000
NOTE: diskgroup must now be re-mounted prior to first use
NOTE: cache dismounting group 1/0x1649BE7B (DATA)
SUCCESS: diskgroup DATA was created
NOTE: cache registered group DATA number=1 incarn=0x2769be7e
Wed May 21 10:16:33 GMT+08:00 2014NOTE: Hbeat: instance first (grp 1)
Wed May 21 10:16:37 GMT+08:00 2014NOTE: start heartbeating (grp 1)
NOTE: cache opening disk 0 of grp 1: DATA_0000 path:/dev/rlv_asm1
Wed May 21 10:16:37 GMT+08:00 2014NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache opening disk 1 of grp 1: DATA_0001 path:/dev/rlv_asm2
NOTE: cache opening disk 2 of grp 1: DATA_0002 path:/dev/rlv_asm3
NOTE: cache opening disk 3 of grp 1: DATA_0003 path:/dev/rlv_asm4
NOTE: cache mounting (first) group 1/0x2769BE7E (DATA)
NOTE: cache recovered group 1 to fcn 0.0
Wed May 21 10:16:37 GMT+08:00 2014NOTE: LGWR attempting to mount thread 1 for disk group 1
NOTE: LGWR mounted thread 1 for disk group 1
NOTE: opening chunk 1 at fcn 0.0 ABA
NOTE: seq=2 blk=0
Wed May 21 10:16:37 GMT+08:00 2014NOTE: cache mounting group 1/0x2769BE7E (DATA) succeeded
SUCCESS: diskgroup DATA was mounted
Wed May 21 10:16:39 GMT+08:00 2014NOTE: recovering COD for group 1/0x2769be7e (DATA)
SUCCESS: completed COD recovery for group 1/0x2769be7e (DATA)

查看ASM状态：
SQL> select name,state from v$asm_diskgroup;

NAME
--------------------------------------------------------------------------------
STATE
---------------------------------
DATA
MOUNTED

SQL> col name for a30
SQL> col path for a30
SQL> select name,path from v$asm_disk;

NAME PATH
------------------------------ ------------------------------
DATA_0000 /dev/rlv_asm1
DATA_0001 /dev/rlv_asm2
DATA_0002 /dev/rlv_asm3
DATA_0003 /dev/rlv_asm4

select path_kfdsk,state_kfdsk,asmname_kfdsk from x$kfdsk;
PATH_KFDSK STATE_KFDSK ASMNAME_KFDSK
-------------- ----------- ----------------
/dev/rlv_asm1 2 DATA_0000
/dev/rlv_asm2 2 DATA_0001
/dev/rlv_asm3 2 DATA_0002
/dev/rlv_asm4 2 DATA_0003

ASMCMD> lsdg
State Type Rebal Unbal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Name
MOUNTED EXTERN N N 512 4096 4194304 1024 928 0 928 0 DATA/

1* select INDX,inst_id,group_kffil,number_kffil,filsiz_kffil,ftype_kffil from x$kffil
SQL> /

INDX INST_ID GROUP_KFFIL NUMBER_KFFIL FILSIZ_KFFIL FTYPE_KFFIL
---------- ---------- ----------- ------------ ------------ -----------
0 1 1 1 4194304 15
1 1 1 2 1048576 15
2 1 1 3 46137344 15
3 1 1 4 1392640 15
4 1 1 5 1048576 15
5 1 1 6 1048576 15

6 rows selected.
至此AIX使用LV创建ASM磁盘组操作完成。

陳述

本文內容由網友自願投稿，版權歸原作者所有。本站不承擔相應的法律責任。如發現涉嫌抄襲或侵權的內容，請聯絡admin@php.cn

MySQL與Sqlite有何不同？Apr 24, 2025 am 12:12 AM

MySQL和SQLite的主要區別在於設計理念和使用場景：1.MySQL適用於大型應用和企業級解決方案，支持高性能和高並發；2.SQLite適合移動應用和桌面軟件，輕量級且易於嵌入。

MySQL中的索引是什麼？它們如何提高性能？Apr 24, 2025 am 12:09 AM

MySQL中的索引是數據庫表中一列或多列的有序結構，用於加速數據檢索。 1）索引通過減少掃描數據量提升查詢速度。 2）B-Tree索引利用平衡樹結構，適合範圍查詢和排序。 3）創建索引使用CREATEINDEX語句，如CREATEINDEXidx_customer_idONorders(customer_id)。 4）複合索引可優化多列查詢，如CREATEINDEXidx_customer_orderONorders(customer_id,order_date)。 5）使用EXPLAIN分析查詢計劃，避

說明如何使用MySQL中的交易來確保數據一致性。Apr 24, 2025 am 12:09 AM

在MySQL中使用事務可以確保數據一致性。 1)通過STARTTRANSACTION開始事務，執行SQL操作後用COMMIT提交或ROLLBACK回滾。 2)使用SAVEPOINT可以設置保存點，允許部分回滾。 3)性能優化建議包括縮短事務時間、避免大規模查詢和合理使用隔離級別。

在哪些情況下，您可以選擇PostgreSQL而不是MySQL？Apr 24, 2025 am 12:07 AM

選擇PostgreSQL而非MySQL的場景包括：1)需要復雜查詢和高級SQL功能，2)要求嚴格的數據完整性和ACID遵從性，3)需要高級空間功能，4)處理大數據集時需要高性能。 PostgreSQL在這些方面表現出色，適合需要復雜數據處理和高數據完整性的項目。

如何保護MySQL數據庫？Apr 24, 2025 am 12:04 AM

MySQL數據庫的安全可以通過以下措施實現：1.用戶權限管理：通過CREATEUSER和GRANT命令嚴格控制訪問權限。 2.加密傳輸：配置SSL/TLS確保數據傳輸安全。 3.數據庫備份和恢復：使用mysqldump或mysqlpump定期備份數據。 4.高級安全策略：使用防火牆限制訪問，並啟用審計日誌記錄操作。 5.性能優化與最佳實踐：通過索引和查詢優化以及定期維護兼顧安全和性能。

您可以使用哪些工具來監視MySQL性能？Apr 23, 2025 am 12:21 AM

如何有效監控MySQL性能？使用mysqladmin、SHOWGLOBALSTATUS、PerconaMonitoringandManagement(PMM)和MySQLEnterpriseMonitor等工具。 1.使用mysqladmin查看連接數。 2.用SHOWGLOBALSTATUS查看查詢數。 3.PMM提供詳細性能數據和圖形化界面。 4.MySQLEnterpriseMonitor提供豐富的監控功能和報警機制。

MySQL與SQL Server有何不同？Apr 23, 2025 am 12:20 AM

MySQL和SQLServer的区别在于：1)MySQL是开源的，适用于Web和嵌入式系统，2)SQLServer是微软的商业产品，适用于企业级应用。两者在存储引擎、性能优化和应用场景上有显著差异，选择时需考虑项目规模和未来扩展性。

在哪些情況下，您可以選擇SQL Server而不是MySQL？Apr 23, 2025 am 12:20 AM

在需要高可用性、高級安全性和良好集成性的企業級應用場景下，應選擇SQLServer而不是MySQL。 1)SQLServer提供企業級功能，如高可用性和高級安全性。 2)它與微軟生態系統如VisualStudio和PowerBI緊密集成。 3)SQLServer在性能優化方面表現出色，支持內存優化表和列存儲索引。

See all articles