A very common request for every DBA is to clone databases between environments. In the following post we will address the steps required to clone a pluggable database (PDB) very easily. This post would be very useful in diverse scenarios, such as creating new development or QA scenarios. Cloning environments quickly is one of the foundation ideas of any given DBaaS (database-as-a-service) project
Viewing entries tagged
DBA
The purpose of this blog is to show how different performance strategies can be implemented using the Oracle Database Resource Manager. Some practical examples are looked at to illustrate the point.
Resource Manager is designed to maximize throughput, so the resource plan directive given is no hard limit. In a CPU constrained system, we can allocate more CPU resources to OLTP users than to batch-jobs. With Resource Manager, the DBA can plan for a more proactive and predictable performance perspective – meeting service level agreements.
Transaction Recovery is a feature of Oracle database that allows DBAs to recover from transactions which have undesirable effects. Sometimes it happens that a transaction performs an undesirable effect, and we determine later that this transaction should not have been committed. In this case, we do not want to perform database point-in-time recovery as the rest of database is working fine. We only have a problem with one transaction. Oracle allows us to provide approximate times of the problematic transaction and search the archived and online redo log files for transactions performed during said time. Then we can identify the transaction and roll it back. Transaction recovery is very easy to use from Oracle Enterprise Manager, but it requires some setup to perform before we can use it.
SQL Access Advisor allows DBAs and developers to analyze individual SQL statements, SQL tuning sets or the entire system and recommend materialize views, partitioning and indexes on tables. There are two interfaces of SQL Access Advisor: Oracle Enterprise Manager and DBMS_ADVISOR package. The Oracle Enterprise Manager interface is easy and user-friendly, but DBMS_ADVISOR package provides the same recommendations from SQL*Plus, which is useful in environments that do not have OEM installed. SQL Access Advisor is a part of the Oracle Tuning Pack, which also requires the Diagnostic Pack.
This package enables the collection of data for performance improvement or for determining code coverage for PL/SQL applications. Application developers can use code coverage data to focus their incremental testing efforts. This blog provides DBAs, developers, support analysts, and consultants with PL/SQL tuning hints and tips using profiling.