Oracle Database 10g R2 ASM：全面指南与技术实践

oracle

需积分: 9 46 浏览量更新于2024-07-25 收藏 251KB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

Oracle Database 10g Release 2 是一个重要的里程碑，它在数据库管理和存储管理方面引入了一系列创新功能，旨在提升性能、可靠性和易用性。此版本的自动存储管理（Automatic Storage Management, ASM）是核心亮点，提供了自动化、高效和可扩展的存储解决方案。 1. **ASM 新特性**：Oracle 10g Release 2 强化了ASM，包括新的空间相关列，如空间效率提升和动态空间分配，使得磁盘空间管理更加智能。同时，引入了Cluster Synchronization Services (CSS) 来优化数据一致性。 2. **安装与配置**：ASMinstallation部分详细介绍了如何部署和配置ASM实例，包括设置系统全局区（SGA）和参数优化，确保系统的稳定运行。 3. **权限与管理**：ASM和privileges章节强调了用户在ASM环境中的权限管理，确保数据安全和操作合规。 4. **存储设备和多路径**：对磁盘和磁盘组进行了优化，包括支持多路径技术，提高磁盘冗余和故障恢复能力。 5. **磁盘组与数据库**：磁盘组与数据库的整合更为紧密，确保数据的高效访问和冗余保护。数据库的迁移和部署最佳实践也得到了强调。 6. **多版本支持**：Database Multi-Version Support允许更有效地利用存储空间，减少了数据的冗余。 7. **数据库进程支持**：特定于ASM的数据库进程和初始化参数被设计得更为兼容，以优化数据库与存储的交互。 8. **依赖性和维护**：讨论了数据库启动、关闭与ASM的关系，以及数据库部署的最佳实践，确保在维护期间的无缝协作。 9. **存储管理和分配**：StorageManagement and Allocation部分着重于如何合理分配和管理存储资源，实现资源的最大利用率。 10. **重新平衡和再分布**：Rebalance and Redistribution功能允许动态调整存储分配，应对工作负载的变化。 11. **文件和别名**：Files and Aliases章节涉及文件结构和命名规则，方便管理和操作。 12. **增强的管理工具**：Enhanced management for ASM 提供了更强大的命令行界面（ASMCMD）和DBMS_FILE_TRANSFER Utility 的增强功能，便于管理员进行高级操作。 13. **XML ASM虚拟文件夹**：XML ASM Virtual Folder技术支持通过FTP等协议访问虚拟文件夹，增加了存储资源的灵活性。 14. **模板和简化迁移**：Templates 和 Simplified ASM migration using EM 提供了快速部署和迁移的便捷方案。 15. **ASM管理与结论**：最后，Oracle Database 10g Release 2 的ASM管理部分总结了整个系统的管理和优化策略，展望了未来的发展方向。 Oracle Database 10g Release 2 的Automatic Storage Management 是一个关键组件，它不仅提升了存储管理的自动化程度，还通过一系列技术改进和工具增强，为数据库环境的高效运行和维护提供了坚实的基础。

资源详情

资源推荐

ASM and privileges

Access to the ASM instance is comparable to a standard instance; i.e., SYSDBA and SYSOPER. Note

however, since there is no data dictionary, authentication is done from an Operating System level and/or an

Oracle password file. Typically, the SYSDBA privilege is granted through the use of an operating system

group. On Unix, this is typically the dba group. By default, members of the dba group have SYSDBA

privileges on all instances on the node, including the ASM instance

. Users who connect to the ASM

instance with the SYSDBA privilege have complete administrative access to all disk groups in the system.

The SYSOPER privilege is supported in ASM instances and limits the set of allowable SQL commands to

the minimum required for basic operation of an already-configured system. The following commands are

available to SYSOPER users:

•STARTUP/SHUTDOWN

•ALTER DISKGROUP MOUNT/DISMOUNT

•ALTER DISKGROUP ONLINE/OFFLINE DISK

•ALTER DISKGROUP REBALANCE

•ALTER DISKGROUP CHECK

•Access to all V$ASM_* views

All other commands, such as CREATE DISKGROUP, ADD/DROP/RESIZE DISK, and so on, require the

SYSDBA privilege and are not allowed with the SYSOPER privilege.

ASMLIB

Oracle has developed a storage management interface called the ASMLIB API. ASMLIB is not required to

run ASM; it is simply an add-on module that simplifies the management and discovery of ASM disks. The

ASMLIB provides an alternative, to the standard operating system interface, for ASM to identify and

access block devices. The ASMLIB API provides storage and operating system vendors the opportunity to

supply extended storage-related features and exploit the capabilities and strengths of vendors’ storage

array.

The ASMLIB API provides two major feature enhancements over standard interfaces:

• Disk discovery – Providing more information about the storage attributes to the Database and

the DBA

• I/O processing – To enable more efficient I/O

Oracle is providing an ASMLIB, called the Oracle ASMLIB, for the Linux platform (current version as of

this writing is 2.0). This implementation of ASMLIB makes it easier to provision storage for a clustered

pool of storage. Providing a kernel level driver access to disk means that permissions and device mapping

are more stable upon the reboot of a server.

ASMLIB also makes the discovery process simpler to manage and removes the challenge of having disks

added to one node and not be known to other nodes in the cluster.

The Oracle ASMLIB for Linux is available and can be down loaded from OTN. See the following URL

for more information on ASMLib configuration and support matrix.

http://www.oracle.com/technology/tech/linux/asmlib/index.html

On Windows systems, the sqlnet.ora must specify NTS.

Disks

The first task in building the ASM infrastructure is to discover and associate (adding) disks under ASM

management. This step is best done with the coordination of Storage and Systems administrators. The

Storage administrator will identify a set of disks and create the appropriate LUNs from the storage array

and finally present them to the host. The term disk may be used in loose terms. A disk can be partition of a

physical spindle, the entire spindle or a LUN in a RAID group set (defined in the storage array), this

depends on how the storage array presents the logical unit number (LUN) to the Operating System (OS). In

this document we will refer generically to LUNs or disks presented to the OS as simply, disks.

There are some restrictions on disk sizes that can be added to an ASM diskgroup. The maximum disk size

that can be included as an ASM disk is 2^32 MB and the minimum disk size is 4Mb

On Solaris systems, disks will generally have the following SCSI name format: CwTxDySz. Where the C is

controller number, T is the target, D is the LUN/disk number, and S is the partition. Note that each OS will

have its unique representation of SCSI disk naming.

For example, it is a best practice on a Solaris system, to create a partition on the disk; such as slice 4 or 6,

which skips the first 1Mb into the disk. Creating partition serves several purposes. A partition creates a

placeholder to identify that the disk is being used. An un-partitioned disk could be accidentally misused or

overwritten. Skipping 1Mb into the disk is done to skip the OS label/VTOC, as well as to preserve

alignment between ASM stripping and storage array internal stripping.

Keep in mind that you’ll never get perfect alignment between ASM and the underlying storage LUN

layout. Anything other than perfect 1 MB alignment will not achieve that goal. However this is not an

issue if you are not using a storage array that stripes a LUN across multiple disks with stripes that are a

power of 2. In any case, if your fdisk tool does not allow you to do this easily, then don't worry.

Different Operating Systems will have varying requirements for the OS label; i.e., some may require an OS

label before it is used while others will not. The same principles apply for different Operating systems

although the procedures may be different.

In SAN environments, it assumed that the disks are identified and configured correctly; i.e., they are

appropriately zoned or LUN masked within the SAN fabric and can be seen by the OS. Once the disks are

identified, they will need to be discovered by ASM. This requires that the disk devices (Unix filenames)

have their ownership changed from root to oracle

Throughout this document a running example consisting of diskgroup DATA will be used to procedurally

outline the steps for creating a diskgroup and other ASM objects.

In our example, disks c3t19d5s4, c3t19d16s4, c3t19d17s4, c3t19d18s4 are identified, and their ownership

set to the correct “oracle:dba” ownership.

Now, these disks can be defined and discovered via the init.ora parameter, asm_diskstring. In our example,

we will use the following wildcard setting:

*.asm_diskstring='/dev/rdsk/c3t19d*s4'.

ASM will only scan for disks that match that ASM search string. There are two forms of ASM disk

discovery; shallow and deep. Shallow discovery is simply ASM scanning (essentially an ‘ls-l’ listing) of

all the devices that are eligible to opened; i.e; these disk devices have the appropriate permissions. Deep

discovery is physical open of those eligible disk devices.

Although logical volumes can be presented to ASM as disks, it is generally not a good practice, since an

extra layer is added to IO code path, and thus some level of overhead.

剩余40页未读，继续阅读

子晤疋笺

粉丝: 0
资源: 2

Oracle Database 10g R2 ASM：全面指南与技术实践

Oracle 9i Client （Oracle 9i 客户端） 简化版 (不安装Oracle客户端,也可以使用PLSQL Developer)

oracle10G和oracle11G的OCI.dll

oracle.jdbc.driver.oracledriver Oracle JDBC驱动包 ojdbc6

oracle spatial 和oracle

Navicat for Oracle 连接oracle

oracle.jdbc.driver.OracleDriver和oracle.jdbc.OracleDriver这两个驱动的区别

oracle和oracle如何连

Oracle Linux下Oracle 19C

python 连接 Oracle 19C 是用oracledb 还是 cx_Oracle

oracle.jdbc.OracleDriver

oracle官网下载oracle教程

oracle 单机升级oracle rac

oracle md030,Oracle AIM

用oracle用户把oracle_profile复制到/oracle目录里

oracle10.2 使用 oracle_fdw

oracle 下载 地址,Oracle各版本下载地址

oracle11g导入oracle19c

在连接 Oracle 数据库之前，需要使用 cx_Oracle.init_oracle_client() 方法指定 Oracle 客户端库的路径

oracle10g导入oracle19c

Oracle Linux 安装Oracle11g

最新资源

Oracle 9i Client （Oracle 9i 客户端）简化版 (不安装Oracle客户端,也可以使用PLSQL Developer)

oracle 下载地址,Oracle各版本下载地址