This document provides an architectural diagram of a multitenant database. It shows that a multitenant container database (CDB) contains multiple pluggable databases (PDBs). Common objects like users and roles are defined at the CDB level while each PDB contains local users, roles, and database objects like tables. System resources like memory and processes are shared between the CDB and PDBs.
This document discusses Oracle Multitenant 19c and pluggable databases. It begins with an introduction to the speaker and overview of pluggable databases. It then describes the traditional Oracle database architecture and the multitenant architecture in Oracle 19c. It discusses the different components of a container database including the root, seed PDB, and application containers. It also covers how to create pluggable databases from scratch, through cloning locally and remotely, relocating PDBs, and plugging in unplugged PDBs.
MySQL 8 High Availability with InnoDB ClustersMiguel Araújo
MySQL’s InnoDB cluster provides a high-level, easy-to-use solution for MySQL high availability. Combining MySQL Group Replication with MySQL Router and the MySQL Shell into an integrated solution, InnoDB clusters offer easy setup and management of MySQL instances into a fault-tolerant database service. In this session learn how to set up a basic InnoDB cluster, integrate it with applications, and recognize and react to common failure scenarios that would otherwise lead to a database outage.
- Workshop presentation
This document provides an overview of Oracle 12c Pluggable Databases (PDBs). Key points include:
- PDBs allow multiple databases to be consolidated within a single container database (CDB), providing benefits like faster provisioning and upgrades by doing them once per CDB.
- Each PDB acts as an independent database with its own data dictionary but shares resources like redo logs at the CDB level. PDBs can be unplugged from one CDB and plugged into another.
- Hands-on labs demonstrate how to create, open, clone, and migrate PDBs between CDBs. The document also compares characteristics of CDBs and PDBs and shows how a non-C
This document provides an overview of upgrading to Oracle Database 19c and the release and patching strategy. It discusses:
- Why customers should upgrade their outdated Oracle 7 databases to take advantage of modern features and extended support.
- Oracle's lifetime support policy and how different release types have different support windows.
- The differences between patching and upgrading an Oracle database.
- Details on Oracle's release numbering and how patches are applied as Release Updates and Release Update Revisions over time.
- Recommendations on testing patches before applying them to avoid issues and ensure a smooth upgrade and patching process.
The document discusses MySQL Shell and how it can help database administrators (DBAs) with common tasks like deploying architectures, preparing upgrades, dumping and loading data, and managing users. MySQL Shell provides tools like the Admin API for configuring MySQL clusters and replicasets, an upgrade checker utility to validate upgrades to MySQL 8.0, and parallel dump and load functionality to backup, migrate, and reset data.
This document provides an architectural diagram of a multitenant database. It shows that a multitenant container database (CDB) contains multiple pluggable databases (PDBs). Common objects like users and roles are defined at the CDB level while each PDB contains local users, roles, and database objects like tables. System resources like memory and processes are shared between the CDB and PDBs.
This document discusses Oracle Multitenant 19c and pluggable databases. It begins with an introduction to the speaker and overview of pluggable databases. It then describes the traditional Oracle database architecture and the multitenant architecture in Oracle 19c. It discusses the different components of a container database including the root, seed PDB, and application containers. It also covers how to create pluggable databases from scratch, through cloning locally and remotely, relocating PDBs, and plugging in unplugged PDBs.
MySQL 8 High Availability with InnoDB ClustersMiguel Araújo
MySQL’s InnoDB cluster provides a high-level, easy-to-use solution for MySQL high availability. Combining MySQL Group Replication with MySQL Router and the MySQL Shell into an integrated solution, InnoDB clusters offer easy setup and management of MySQL instances into a fault-tolerant database service. In this session learn how to set up a basic InnoDB cluster, integrate it with applications, and recognize and react to common failure scenarios that would otherwise lead to a database outage.
- Workshop presentation
This document provides an overview of Oracle 12c Pluggable Databases (PDBs). Key points include:
- PDBs allow multiple databases to be consolidated within a single container database (CDB), providing benefits like faster provisioning and upgrades by doing them once per CDB.
- Each PDB acts as an independent database with its own data dictionary but shares resources like redo logs at the CDB level. PDBs can be unplugged from one CDB and plugged into another.
- Hands-on labs demonstrate how to create, open, clone, and migrate PDBs between CDBs. The document also compares characteristics of CDBs and PDBs and shows how a non-C
This document provides an overview of upgrading to Oracle Database 19c and the release and patching strategy. It discusses:
- Why customers should upgrade their outdated Oracle 7 databases to take advantage of modern features and extended support.
- Oracle's lifetime support policy and how different release types have different support windows.
- The differences between patching and upgrading an Oracle database.
- Details on Oracle's release numbering and how patches are applied as Release Updates and Release Update Revisions over time.
- Recommendations on testing patches before applying them to avoid issues and ensure a smooth upgrade and patching process.
The document discusses MySQL Shell and how it can help database administrators (DBAs) with common tasks like deploying architectures, preparing upgrades, dumping and loading data, and managing users. MySQL Shell provides tools like the Admin API for configuring MySQL clusters and replicasets, an upgrade checker utility to validate upgrades to MySQL 8.0, and parallel dump and load functionality to backup, migrate, and reset data.
Oracle Real Application Clusters 19c- Best Practices and Internals- EMEA Tour...Sandesh Rao
In this session, I will cover under-the-hood features that power Oracle Real Application Clusters (Oracle RAC) 19c specifically around Cache Fusion and Service management. Improvements in Oracle RAC helps in integration with features such as Multitenant and Data Guard. In fact, these features benefit immensely when used with Oracle RAC. Finally we will talk about changes to the broader Oracle RAC Family of Products stack and the algorithmic changes that helps quickly detect sick/dead nodes/instances and the reconfiguration improvements to ensure that the Oracle RAC Databases continue to function without any disruption
This document provides an overview and summary of Oracle Data Guard. It discusses the key benefits of Data Guard including disaster recovery, data protection, and high availability. It describes the different types of Data Guard configurations including physical and logical standbys. The document outlines the basic architecture and processes involved in implementing Data Guard including redo transport, apply services, and role transitions. It also summarizes some of the features and protection modes available in different Oracle database versions.
New Features for Multitenant in Oracle Database 21cMarkus Flechtner
Oracle Database 21c introduces several new features for multitenant databases:
- PDBs can now be upgraded automatically when plugged into a 21c CDB or opened, replaying the upgrade process.
- Resource management is improved with options like mandatory user profiles, per-PDB database resident connection pooling, and Oracle DB Nest for isolating PDBs using Linux namespaces and cgroups.
- Multitenant enhancements for high availability include PDBs being managed as cluster resources and improved PDB-level recovery when using Active Data Guard.
This document provides an introduction to Oracle Database 18c's multitenant architecture. It explains that a multitenant database functions as a container database (CDB) that can include zero, one, or many pluggable databases (PDBs). Each PDB acts as an isolated database environment with its own schemas, objects, and users. The maximum number of PDBs allowed in a CDB depends on licensing but can be up to 4098 or 5254. Benefits of the multitenant architecture include reduced costs, easier data movement and management, isolation of PDBs, and easier performance tuning, patching and upgrades.
This document discusses Oracle database performance tuning. It covers identifying common Oracle performance issues such as CPU bottlenecks, memory issues, and inefficient SQL statements. It also outlines the Oracle performance tuning method and tools like the Automatic Database Diagnostic Monitor (ADDM) and performance page in Oracle Enterprise Manager. These tools help administrators monitor performance, identify bottlenecks, implement ADDM recommendations, and tune SQL statements reactively when issues arise.
Oracle is planning to release Oracle Database 12c in calendar year 2013. The new release will include a multitenant architecture that allows for multiple pluggable databases to be consolidated and managed within a single container database. This new architecture enables fast provisioning of new databases, efficient cloning of pluggable databases, simplified patching and upgrades applied commonly to all pluggable databases, and other benefits that improve database consolidation on cloud platforms.
Starting with 12c Release 1, Oracle introduced a completely new architecture concept for its database - the Container Database.
With this new architecture, new challenges came up but with the same breath a wide branch of new opportunities.
The presentation will address the capabilities to create fast and easy new (test) databases or clones for a running production database. Five different ways will be discussed.
- Using Local and Remote Cloning
- Using an Unplugged PDB (predefined master)
- Using Refreshable PDBs as a master for new (test) databases
- Snapshot Carousel
Another point of the agenda is the usage of the Snapshot features of ACFS and Direct NFS to speed up the creation process.
In this tutorial, we cover the different deployment possibilities of the MySQL architecture depending on the business requirements for the data. We also deploy some architecture and see how to evolve to the next one.
The tutorial covers the new MySQL Solutions like InnoDB ReplicaSet, InnoDB Cluster, and InnoDB ClusterSet.
This document provides an overview of Oracle 12c and its pluggable database feature from a presentation by Gustavo René Antúnez, an Oracle DBA at Pythian. It discusses the benefits of pluggable databases such as greater scalability and consolidation. It also covers key aspects of the multitenant architecture like common users, local users, and views that span the container and pluggable databases. The presentation concludes with a demonstration of RMAN backups in a multitenant environment.
Database Consolidation using the Oracle Multitenant ArchitecturePini Dibask
The document discusses Oracle's Multitenant architecture, which allows multiple pluggable databases (PDBs) to consolidate within a single multitenant container database (CDB). It describes how Multitenant provides advantages like simplified upgrades, cloning, and migration of PDBs. The document also covers ensuring quality of service for PDBs using resource management, and how RAC supports high availability and scalability in a Multitenant environment. It concludes with a discussion of performance monitoring of workloads across PDBs.
When does InnoDB lock a row? Multiple rows? Why would it lock a gap? How do transactions affect these scenarios? Locking is one of the more opaque features of MySQL, but it’s very important for both developers and DBA’s to understand if they want their applications to work with high performance and concurrency. This is a creative presentation to illustrate the scenarios for locking in InnoDB and make these scenarios easier to visualize. I'll cover: key locks, table locks, gap locks, shared locks, exclusive locks, intention locks, insert locks, auto-inc locks, and also conditions for deadlocks.
24시간 365일 서비스를 위한 MySQL DB 이중화.
MySQL 이중화 방안들에 대해 알아보고 운영하면서 겪은 고민들을 이야기해 봅니다.
목차
1. DB 이중화 필요성
2. 이중화 방안
- HW 이중화
- MySQL Replication 이중화
3. 이중화 운영 장애
4. DNS와 VIP
5. MySQL 이중화 솔루션 비교
대상
- MySQL을 서비스하고 있는 인프라 담당자
- MySQL 이중화에 관심 있는 개발자
MySQL Database Architectures - MySQL InnoDB ClusterSet 2021-11Kenny Gryp
Oracle's MySQL solutions make it easy to setup various database architectures and achieve high availability with the introduction MySQL InnoDB Cluster and MySQL InnoDB ReplicaSet meeting various high availability requirements. MySQL InnoDB ClusterSet provides a popular disaster recovery solution.
Completely built in-house and supported by Oracle, many enterprises large and small have adopted these solutions into business critical applications.
In this presentation the various database architecture solutions for high availability and disaster recovery will be covered and help you choose the right solutions based on your business requirements.
MySQL Database Architectures - InnoDB ReplicaSet & ClusterKenny Gryp
This document provides an overview and comparison of MySQL InnoDB Cluster and MySQL InnoDB ReplicaSet. It discusses the components, goals, and features of each solution. MySQL InnoDB Cluster uses Group Replication to provide high availability, automatic failover, and data consistency. MySQL InnoDB ReplicaSet uses asynchronous replication and provides availability and read scaling through manual primary/secondary configuration and failover. Both solutions integrate MySQL Shell, Router, and automatic member provisioning for easy management.
This document provides an overview of use cases for the ProxySQL database proxy. It discusses how ProxySQL can be used to:
1. Improve scalability through features like connection pooling, read/write splitting, and sharding.
2. Enhance high availability with seamless failover, load balancing, and cluster awareness.
3. Enable advanced query capabilities such as caching, rewriting, blocking, and routing.
4. Provide manageability tools for authentication, runtime configuration, and monitoring.
The document describes several specific scenarios where ProxySQL can optimize operations, help solve performance issues, and empower database administrators. It also outlines how ProxySQL has been tested at large scale supporting millions of
This document discusses techniques for optimizing SQL performance in Oracle databases. It covers topics like optimizing the optimizer itself through configuration changes and statistics collection, detecting poorly performing SQL, and methods for improving plans such as indexing, partitioning, hints and baselines. The goal is to maximize the optimizer's accuracy and ability to handle edge cases, while also knowing how to intervene when needed to capture fugitive SQL and ensure acceptable performance.
Infinispan, a distributed in-memory key/value data grid and cacheSebastian Andrasoni
This document provides an introduction to distributed in-memory data grids and caches, including Infinispan. It discusses hash tables, distributed hash tables, consistent hashing, and the Chord lookup protocol. It then describes data grids and Infinispan's architecture, which uses consistent hashing to distribute data across clusters and allows for high availability even when nodes fail or partitions occur. The document also briefly discusses Infinispan's features like transactions, querying, map-reduce, and more.
This document discusses database security solutions from Oracle, including Oracle Audit Vault and Database Firewall. It provides an overview of the Oracle Database Security solutions for activity monitoring, database firewalling, auditing and reporting, and encryption. It then focuses on describing the features and benefits of Oracle Audit Vault and Database Firewall, including how they provide database activity auditing and monitoring, extensive reporting, powerful alerting, and strengthened data security.
Oracle Real Application Clusters 19c- Best Practices and Internals- EMEA Tour...Sandesh Rao
In this session, I will cover under-the-hood features that power Oracle Real Application Clusters (Oracle RAC) 19c specifically around Cache Fusion and Service management. Improvements in Oracle RAC helps in integration with features such as Multitenant and Data Guard. In fact, these features benefit immensely when used with Oracle RAC. Finally we will talk about changes to the broader Oracle RAC Family of Products stack and the algorithmic changes that helps quickly detect sick/dead nodes/instances and the reconfiguration improvements to ensure that the Oracle RAC Databases continue to function without any disruption
This document provides an overview and summary of Oracle Data Guard. It discusses the key benefits of Data Guard including disaster recovery, data protection, and high availability. It describes the different types of Data Guard configurations including physical and logical standbys. The document outlines the basic architecture and processes involved in implementing Data Guard including redo transport, apply services, and role transitions. It also summarizes some of the features and protection modes available in different Oracle database versions.
New Features for Multitenant in Oracle Database 21cMarkus Flechtner
Oracle Database 21c introduces several new features for multitenant databases:
- PDBs can now be upgraded automatically when plugged into a 21c CDB or opened, replaying the upgrade process.
- Resource management is improved with options like mandatory user profiles, per-PDB database resident connection pooling, and Oracle DB Nest for isolating PDBs using Linux namespaces and cgroups.
- Multitenant enhancements for high availability include PDBs being managed as cluster resources and improved PDB-level recovery when using Active Data Guard.
This document provides an introduction to Oracle Database 18c's multitenant architecture. It explains that a multitenant database functions as a container database (CDB) that can include zero, one, or many pluggable databases (PDBs). Each PDB acts as an isolated database environment with its own schemas, objects, and users. The maximum number of PDBs allowed in a CDB depends on licensing but can be up to 4098 or 5254. Benefits of the multitenant architecture include reduced costs, easier data movement and management, isolation of PDBs, and easier performance tuning, patching and upgrades.
This document discusses Oracle database performance tuning. It covers identifying common Oracle performance issues such as CPU bottlenecks, memory issues, and inefficient SQL statements. It also outlines the Oracle performance tuning method and tools like the Automatic Database Diagnostic Monitor (ADDM) and performance page in Oracle Enterprise Manager. These tools help administrators monitor performance, identify bottlenecks, implement ADDM recommendations, and tune SQL statements reactively when issues arise.
Oracle is planning to release Oracle Database 12c in calendar year 2013. The new release will include a multitenant architecture that allows for multiple pluggable databases to be consolidated and managed within a single container database. This new architecture enables fast provisioning of new databases, efficient cloning of pluggable databases, simplified patching and upgrades applied commonly to all pluggable databases, and other benefits that improve database consolidation on cloud platforms.
Starting with 12c Release 1, Oracle introduced a completely new architecture concept for its database - the Container Database.
With this new architecture, new challenges came up but with the same breath a wide branch of new opportunities.
The presentation will address the capabilities to create fast and easy new (test) databases or clones for a running production database. Five different ways will be discussed.
- Using Local and Remote Cloning
- Using an Unplugged PDB (predefined master)
- Using Refreshable PDBs as a master for new (test) databases
- Snapshot Carousel
Another point of the agenda is the usage of the Snapshot features of ACFS and Direct NFS to speed up the creation process.
In this tutorial, we cover the different deployment possibilities of the MySQL architecture depending on the business requirements for the data. We also deploy some architecture and see how to evolve to the next one.
The tutorial covers the new MySQL Solutions like InnoDB ReplicaSet, InnoDB Cluster, and InnoDB ClusterSet.
This document provides an overview of Oracle 12c and its pluggable database feature from a presentation by Gustavo René Antúnez, an Oracle DBA at Pythian. It discusses the benefits of pluggable databases such as greater scalability and consolidation. It also covers key aspects of the multitenant architecture like common users, local users, and views that span the container and pluggable databases. The presentation concludes with a demonstration of RMAN backups in a multitenant environment.
Database Consolidation using the Oracle Multitenant ArchitecturePini Dibask
The document discusses Oracle's Multitenant architecture, which allows multiple pluggable databases (PDBs) to consolidate within a single multitenant container database (CDB). It describes how Multitenant provides advantages like simplified upgrades, cloning, and migration of PDBs. The document also covers ensuring quality of service for PDBs using resource management, and how RAC supports high availability and scalability in a Multitenant environment. It concludes with a discussion of performance monitoring of workloads across PDBs.
When does InnoDB lock a row? Multiple rows? Why would it lock a gap? How do transactions affect these scenarios? Locking is one of the more opaque features of MySQL, but it’s very important for both developers and DBA’s to understand if they want their applications to work with high performance and concurrency. This is a creative presentation to illustrate the scenarios for locking in InnoDB and make these scenarios easier to visualize. I'll cover: key locks, table locks, gap locks, shared locks, exclusive locks, intention locks, insert locks, auto-inc locks, and also conditions for deadlocks.
24시간 365일 서비스를 위한 MySQL DB 이중화.
MySQL 이중화 방안들에 대해 알아보고 운영하면서 겪은 고민들을 이야기해 봅니다.
목차
1. DB 이중화 필요성
2. 이중화 방안
- HW 이중화
- MySQL Replication 이중화
3. 이중화 운영 장애
4. DNS와 VIP
5. MySQL 이중화 솔루션 비교
대상
- MySQL을 서비스하고 있는 인프라 담당자
- MySQL 이중화에 관심 있는 개발자
MySQL Database Architectures - MySQL InnoDB ClusterSet 2021-11Kenny Gryp
Oracle's MySQL solutions make it easy to setup various database architectures and achieve high availability with the introduction MySQL InnoDB Cluster and MySQL InnoDB ReplicaSet meeting various high availability requirements. MySQL InnoDB ClusterSet provides a popular disaster recovery solution.
Completely built in-house and supported by Oracle, many enterprises large and small have adopted these solutions into business critical applications.
In this presentation the various database architecture solutions for high availability and disaster recovery will be covered and help you choose the right solutions based on your business requirements.
MySQL Database Architectures - InnoDB ReplicaSet & ClusterKenny Gryp
This document provides an overview and comparison of MySQL InnoDB Cluster and MySQL InnoDB ReplicaSet. It discusses the components, goals, and features of each solution. MySQL InnoDB Cluster uses Group Replication to provide high availability, automatic failover, and data consistency. MySQL InnoDB ReplicaSet uses asynchronous replication and provides availability and read scaling through manual primary/secondary configuration and failover. Both solutions integrate MySQL Shell, Router, and automatic member provisioning for easy management.
This document provides an overview of use cases for the ProxySQL database proxy. It discusses how ProxySQL can be used to:
1. Improve scalability through features like connection pooling, read/write splitting, and sharding.
2. Enhance high availability with seamless failover, load balancing, and cluster awareness.
3. Enable advanced query capabilities such as caching, rewriting, blocking, and routing.
4. Provide manageability tools for authentication, runtime configuration, and monitoring.
The document describes several specific scenarios where ProxySQL can optimize operations, help solve performance issues, and empower database administrators. It also outlines how ProxySQL has been tested at large scale supporting millions of
This document discusses techniques for optimizing SQL performance in Oracle databases. It covers topics like optimizing the optimizer itself through configuration changes and statistics collection, detecting poorly performing SQL, and methods for improving plans such as indexing, partitioning, hints and baselines. The goal is to maximize the optimizer's accuracy and ability to handle edge cases, while also knowing how to intervene when needed to capture fugitive SQL and ensure acceptable performance.
Infinispan, a distributed in-memory key/value data grid and cacheSebastian Andrasoni
This document provides an introduction to distributed in-memory data grids and caches, including Infinispan. It discusses hash tables, distributed hash tables, consistent hashing, and the Chord lookup protocol. It then describes data grids and Infinispan's architecture, which uses consistent hashing to distribute data across clusters and allows for high availability even when nodes fail or partitions occur. The document also briefly discusses Infinispan's features like transactions, querying, map-reduce, and more.
This document discusses database security solutions from Oracle, including Oracle Audit Vault and Database Firewall. It provides an overview of the Oracle Database Security solutions for activity monitoring, database firewalling, auditing and reporting, and encryption. It then focuses on describing the features and benefits of Oracle Audit Vault and Database Firewall, including how they provide database activity auditing and monitoring, extensive reporting, powerful alerting, and strengthened data security.
공유 스토리지를 이용한 H/A Cluster 뿐만 아니라
Replication을 이용한 Shared Nothing H/A Cluster 제공
내장된 Application 인지형의 고가용성 기능 제공
DB에 대하여 이중으로 Check 하는 Depth 모니터링 기능
30개의 주요한 Applications 지원
넥슨 글로벌 플랫폼 구축 이야기 : DB Migration case study (임현수 플랫폼인프라실 Technical Manager, 넥...Amazon Web Services Korea
넥슨 글로벌 플랫폼 구축 이야기 : DB Migration case study
이 세션에서는 넥슨의 Case study를 통하여 글로벌플랫폼 구축을 위해 기존 플랫폼을 AWS로 Migration하는 과정 및 발생가능한 이슈를 공유합니다. 넥슨이 DB서버를 이전하는 과정 속에서 마주한 기술적 고민과 이슈를 통하여 AWS 활용 시 고려해야 할 부분들에 대해 소개하고 함께 이야기 나누고자 합니다.
네이버클라우드플랫폼에서 제공하는 클라우드 데이터베이스 서비스를 소개하고, 네이버클라우드 플랫폼의 클라우드 데이터베이스 관리 노하우에 대해 소개합니다 | Introduce cloud database services provided by Naver Cloud Platform and know-how of managing cloud databases on Naver Cloud Platform
클라우드에서 인프라 구축 시 고려해야 할 사항들을 살펴보고, 네이버 클라우드 플랫폼을 활용하여 고가용성을 유지하는 방안에 대해 소개합니다. | Explore the considerations of building infrastructure in the cloud and introduce ways to maintain high availability by leveraging the Naver cloud platform.
엔터프라이즈 클라우드 마이그레이션 준비와 실행. 그리고, 클라우드 운영 모범 사례 공유-최지웅, 오픈소스컨설팅 CTO / 장진환, 스마일샤...Amazon Web Services Korea
클라우드 마이레이션은 단순한 업무의 환경 이전 차원을 넘어 미래를 준비하는 긴 여정의 출발점이기도 합니다. 또한, 클라우드 마이그레이션의 전략,기술 준비사항은 기존의 IT 운영 환경에 비례하여 매우 다양하며 복잡 합니다. 이번 세션에서는 AWS MSP 파트너사인 오픈소스 컨설팅, 스마일 샤크의 다양한 클라우드 마이그레이션 사례 및 운영 환경 최적화 사례를 기반으로 여러분들의 클라우드 여정에 도움을 드리고자 합니다.
이번 웨비나에서는 여러분에게 MySQL 성능 튜닝에 대한 깊이 있는 소개를 통해 많은 경험과 전문지식을 배울 수 있는 기회를 제공할 것입니다. 모범 사례를 검토하고 가장 중요한 설정, 초기 MySQL 설정파일, 모니터링 및 그 밖의 것을 다룰 것입니다.
MySQL Workbench, MySQL Enterprise Monitor, 또는 sys schema에서 제공하는 성능 리포트를 이용하여 최적화가 필요한 쿼리를 어떻게 찾는지 배워봅시다.
OCI DBCS, Autonomous Database, Exadata Cloud Service를 위한 DB Tools 설정 방법
https://docs.oracle.com/en-us/iaas/Content/Database-Tools/dbtools_topic-overview.htm
3. Database Management Overview
• Basic Management : 무료
• 14 basic monitoring metrics such as CpuUtilization, StorageAllocated, and UserCalls.
These metrics are displayed in the Oracle Cloud Infrastructure Monitoring service and on the Database Details
page of the database after Database Management is enabled.
• ASH Analytics and SQL Monitoring features in Performance Hub for CDBs.
Note that these features are currently not available for PDBs.
• Full Management : $0.04 OCPU Per Hour (월 환산시 1 OCPU당 $29.76)
• Features available as part of Basic Management.
• Monitoring and management capabilities for your fleet of databases.
Note that these capabilities are currently not available for PDBs.
• SKU features, which include advanced Performance Hub features such as Automatic Database Diagnostic
Monitor (ADDM) and Blocking Sessions and other features such as SQL Jobs and Tablespace monitoring.
• For the Oracle Database Standard Edition, it does not include Performance Hub features.
• Manamgent Agent : External Database 경우 설치 필요하고 DBCS는 필요치 않음
5. 단계 1) DBCS에 모니터링 계정 활성화
• DBCS CDB로 접속하여 ‘dbsnmp’ 계정 활성화
SQL > alter user dbsnmp account unlock;
# 패스워드는 FIPS 정책에 따라 14자리 이상, 대/소문자/숫자/특수문자 혼용
SQL > alter user dbsnmp identified by <password>;
# Performance Hub와 AWR Explorer 를 위해 권한 부여
SQL > GRANT CREATE PROCEDURE to dbsnmp;
SQL > GRANT SELECT ANY DICTIONARY, SELECT_CATALOG_ROLE to dbsnmp;
SQL > GRANT ALTER SYSTEM to dbsnmp;
SQL > GRANT ADVISOR to dbsnmp;
SQL > GRANT EXECUTE ON DBMS_WORKLOAD_REPOSITORY to dbsnmp;
6. 단계 2) DB패스워드에 대해 Vault Secret 생성
* DB User 패스워드 보안을 위해 Secret Key를 이용
7. 단계 3) Private Endpoint 생성
• Database Tools의 Private Endpoint와는 별개임
• Public Subnet으로 선택하여도 Public IP를 받지 못 하므로, DB와 동일한 Subnet으로 생성하는 것을 권장
• https://docs.oracle.com/en-us/iaas/database-management/doc/perform-database-management-prerequisite-tasks.html
8. 단계 3) Private Endpoint 생성
• RAC DB 경우는 RAC 옵션을 체크해야 함
• 촤측은 DB와 동일한 Subnet을 설정한 사례임
• Private Endpoint에 Private IP가 할당됨
9. 단계 4) 방화벽 오픈
• Private Endpoint → DB 로 접근이 가능하도록 방화벽 오픈
10. 단계 5) DB Management를 위한 Policy 등록
# DB Mng가 Vault Secret를 읽기 위한 권한
Allow service dpd to read secret-family
in compartment <Vault Location>
where target.vault.id = ‘<Vault OCID>’
32. Policy 등록
# DB내 Agent의 Dynamic Group 생성
ALL {resource.type=‘managementagent’, resource.compartment.id=‘{DBCS Compartment OCID}’}
# Bucket 읽기 권한
Allow dynamic-group Management-Agents-Group to read buckets in compartment ABC
where request.principal.type = 'managementagent'
# Object 생성 및 확인 권한
Allow dynamic-group Management-Agents-Group to manage objects in compartment ABC
where all {request.principal.type = 'managementagent',
any {request.permission='OBJECT_CREATE', request.permission='OBJECT_INSPECT'}}
# DB Managment의 scheduled job의 결과를 Object Storage에 저장하기 위한 권한
Allow service dpd to manage objects in compartment ABC
https://docs.oracle.com/en-us/iaas/database-management/doc/permissions-required-database-management.html
* scheduled job의 결과를 Object Storage에 저장하기 위해 필요한 권한