Data Pump delivers several new features in Oracle Database 11g,including major new apabilities such as dump file encryption anddata compression. This paper describes these and other new featuresof Data Pump.
Enhanced Compression
The ability to compress the metadata associated with a Data Pump job is provided in Oracle Database 10g Release 2.
In Oracle Database 11g, this compression capabilityhas been extended so that you can now compress table data on export.
Data Pumpcompression is an inline operation, so the reduced dump file size means a ignificant savings in disk space. Unlike operating system or file system compression utilities,Data Pump compression is fully inline on the import side as well, so there is no needto uncompress a dump file before importing it.
In the following compression example from the Oracle sample database, the oe andsh schemas were exported while simultaneously compressing all data and metadata.
The dump file size was reduced by 74.67%.Three versions of the gzip (GNU zip) utility and one UNIX compress utility wereused to compress the 6.0 MB dump file set. The reduction in dump file size wascomparable to Data Pump compression.
Note that your reduction in dump file sizewill vary based on data types and other factors.
Compression Method Dump File Size Reduction %
Expdp schemas=oe,sh 6.0 MB N/A
Compression=none
Expdp schemas=oe,sh 1.5 MB 74.67%
Compression=all
gzip –cv1 oesh.dmp 1.1 MB 82.7%
gzip –cv6 oesh.cmp 835 KB 86.2%
gzip –cv9 oesh.dmp 818 KB 86.5%
UNIX compress 1.6 MB 74.24%
Oesh.dmp
You get full Data Pump functionality using a compressed file. Any command that you would use on a regular file will also work on a compressed file.
New Encryption Options
In Oracle Database 11g, Data Pump supplies more encryption options for more flexible and robust security.
The most important new encryption feature for Data Pump is the ability to encrypt dump file sets. You can select encryption for the data, the metadata, or the entire dump file as your needs require.
You can also specify the type of security to use during an export. If Transparent Data Encryption is installed, then transparent encryption employing the Oracle Wallet can be used. If you are moving sensitive data to a system that does not share wallet information with the source database, then password-based encryption might be a better choice. Or, if you want to use both password-based encryption and transparent data encryption, then dual mode is available. All of these encryption modes can be used in combination with dump file compression if you desire.
Encryption is part of the Advanced Security Option and requires Oracle Enterprise Edition.
Data Transforms
This feature allows you to remap data during export or import. There may be a need to obscure data as it is being moved from a production system to a test system so that unauthorized users do not see the data, but the essential processing characteristics of the data are preserved.
For example, you may have a column of customer credit card numbers that needs to remain secure, but for test purposes would still need to retain a particular format and range of values. During export, you can replace the actual data from the source database with numbers generated by a user-defined remap function. The data retains its essential characteristics without exposing the credit card numbers to unauthorized users.
The remap feature can also be used to remap data as it is being inserted into a new database during import. This can be useful to avoid collision of unique values such as sequences when merging data from multiple sources.
Single Partition Transportable Tablespace
You can now export one or more partitions of a table without having to move the entire table. On import, you can choose to load partitions as is, merge them into a single table, or promote each into a separate table.
Dynamic Restart of Workers
If a worker process hits a fatal error, such as a process being manually shut down,
then the worker will be restarted a number of times in an attempt to continue processing.
Re-use Dump Files
You would normally get a fatal error during a Data Pump export if you specify dump files that already exist. This feature allows you to overwrite existing dump files during an export operation.
May 23, 2009
Data Pump features in Oracle11g
Labels: Oracle11g
December 03, 2008
ASM New Features in Oracle11g
The new features in Automatic Storage Management (ASM) extend the storagemanagement automation, improve scalability, and further simplify management forOracle Database files.
■ ASM Fast Mirror Resync A new SQL statement, ALTER DISKGROUP ... DISK ONLINE, can be executedafter a failed disk has been repaired. The command first brings the disk online forwrites so that no new writes are missed. Subsequently, it initiates a copy of all extentsmarked as stale on a disk from their redundant copies.This feature significantly reduces the time it takes to repair a failed diskgroup,potentially from hours to minutes. The repair time is proportional to the number ofextents that have been written to or modified since the failure.
■ ASM Manageability Enhancements The new storage administration features for ASM manageability include the following:
■ New attributes for disk group compatibilityTo enable some of the new ASM features, you can
use two new disk groupcompatibility attributes, compatible.rdbms and compatible.asm. Theseattributes specify the minimum software version that is required to use diskgroups for the database and for ASM, respectively. This feature enablesheterogeneous environments with disk groups from both Oracle Database 10g andOracle Database 11g. By default, both attributes are set to 10.1. You must advancethese attributes to take advantage of the new features.
■ New ASM command-line utility (ASMCMD) commands and options ASMCMD allows ASM disk identification, disk bad block repair, and backup andrestore operations in your ASM environment for faster recovery.
■ ASM fast rebalance Rebalance operations that occur while a disk group is in RESTRICTED modeeliminate the lock and unlock extent map messaging between ASM instances inOracle RAC environments, thus improving overall rebalance throughput.This collection of ASM management features simplifies and automates storagemanagement for Oracle databases.
■ ASM Preferred Mirror Read When ASM failure groups are defined, ASM can now read from the extent that isclosest to it, rather than always reading the primary copy. A new initializationparameter, ASM_PREFERRED_READ_FAILURE_GROUPS, lets the ASM administratorspecify a list of failure group names that contain the preferred read disks for each nodein a cluster. In an extended cluster configuration, reading from a local copy provides a greatperformance advantage. Every node can read from its local diskgroup (failure group),resulting in higher efficiency and performance and reduced network traffic.
■ ASM Rolling Upgrade Rolling upgrade is the ability of clustered software to function when one or more ofthe nodes in the cluster are at different software versions. The various versions of thesoftware can still communicate with each other and provide a single system image.The rolling upgrade capability will be available when upgrading from OracleDatabase 11g Release 1 (11.1). This feature allows independent nodes of an ASM cluster to be migrated or patchedwithout affecting the availability of the database. Rolling upgrade provides higheruptime and graceful migration to new releases.
■ ASM Scalability and Performance Enhancements This feature increases the maximum data file size that Oracle can support to 128 TB.ASM supports file sizes greater than 128 TB in any redundancy mode. This providesnear unlimited capacity for future growth. The ASM file size limits are:
■ External redundancy - 140 PB
■ Normal redundancy - 42 PB
■ High redundancy - 15 PB Customers can also increase the allocation unit size for a disk group in powers of 2 upto 64 MB.
■ Convert Single-Instance ASM to Clustered ASM This feature provides support within Enterprise Manager to convert a non-clusteredASM database to a clustered ASM database by implicitly configuring ASM on allnodes. It also extends the single-instance to Oracle RAC conversion utility to supportstandby databases. Simplifying the conversion makes it easier for customers to migrate their databasesand achieve the benefits of scalability and high availability provided by Oracle RAC.
■ New SYSASM Privilege for ASM Administration This feature introduces the new SYSASM privilege to allow for separation of databasemanagement and storage management responsibilities.The SYSASM privilege allows an administrator to manage the disk groups that can beshared by multiple databases. The SYSASM privilege provides a clear separation ofduties from the SYSDBA privilege. For complete list of 11g ASM New Feature, You can refer the following
Note: Metalink Id: 551205.1 11g ASM New Features Technical White
Paperhttp://www.oracle.com/technology/pub/articles/oracle-database-11g-top-features/11g-asm.html
Labels: Oracle11g
Backup & Recovery New Features in Oracle11g
* Enhanced configuration of archive deletion policies Archive can be deleted , if it is notneed DG , Streams Flashback etc When you CONFIGURE an archived log deletion policyapplies to all archiving destinations, including the flash recovery area. BACKUP ... DELETEINPUT and DELETE... ARCHIVELOG use this configuration, as does the flash recovery area.When we back up the recovery area, RMAN can fail over to other archived redo logdestinations if the flash recovery area is inaccessible.
* Configuring backup compression: In 11g can use CONFIGURE command to choose between the BZIP2 and ZLIB compressionalgorithms for RMAN backups.
* Active Database Duplication: Now DUPLICATE command is network aware i.e.we can create a duplicate or standbydatabase over the network without taking backup or using old backup.
* Parallel backup and restore for very large files: RMAN Backups of large data files now use multiple parallel server processes to efficientlydistribute theworkload for each file. This features improves the performance of backups.
* Improved block media recovery performance: RECOVER command can recover individual data blocks.RMAN take older, uncorrupted blocks from flashback and the RMAN can use these blocks,thereby speeding up block media recovery.
* Fast incremental backups on physical standby database: 11g has included new feature of enable block change tracking on a physical standbydatabase (ALTER DATABASE ENABLE/DISABLE BLOCK CHANGE TRACKING SQL statement).
This new 11g feature enables faster incremental backups on a physical standby databasethan in previous releases.because RMAN identifywe the changed blocks sincethe lastincremental backup.
Labels: Oracle11g
SQL and PL-SQL New Features in Oracle11g
> Fine Grained Dependency Tracking: In 11g we track dependencies at the level of element within unit. so that these changes haveno consequence
• Transparent performance improvement
• Unnecessary recompilation certainly consumes CPU
create table t(a number)
create view v as select a from t
alter table t add(Unheard_Of number)
select status from User_Objectswhere Object_Name = 'V'- -----VALID
No recompilation of dependent objects when Columns added to tables OR Proceduresadded to packages
> Named and Mixed Notation from SQL:
select fun(P4=>10) from DUAL; In 10g not possible to call function in select statment by passing 4th parameter, but in 11g it is possible
> PL/SQL "continue" keyword - It is same as we read in c/c++ loop
> Support for “super”: It is same "super" in Java.
> Powerfull Regular Expression:
Now we can access data between TAGS like data between tags ......... The new built-in REGEXP_COUNT returns the number of times the pattern is matched in theinput string.
> New table Data Type "simple_integer"
> SQL Performance Analyzer(SPA) :
It is same as Database replay except it not capture all transaction.The SQL PerformanceAnalyzer (SPA) leverages existing Oracle Database 10g SQL tuning components. The SPAprovides the ability to capture a specific SQL workload in a SQL Tuning Set, take aperformance baseline before a major database or system change, make the desired changeto the system, and then replay the SQL workload against the modified database orconfiguration. The before and after performance of the SQL workload can then be comparedwith just a few clicks of the mouse. The DBA only needs to isolate any SQL statements thatare now performing poorly and tune them via the SQL Tuning Advisor
> Caching The Results with /*+ result_cache */ :
select /*+ result_cache */ * from my_table, New for Oracle 11g, the result_cache hint cachesthe result set of a select statement. This is similar to alter table table_name cache,but as youcan adding predicates makes /*+ result_cache */ considerably more powerful by caching asubset of larger tables and common queries.
select /*+ result_cache */ col1, col2, col3 from my_table where colA = :B1
> The compound trigger : A compound trigger lets you implement actions for each of the table DML timing points in asingle trigger
> PL/SQL unit source can exceeds 32k characters
> Easier to execute table DDL operations online: Option to wait for active DML operations instead of aborting
> Fast add column with default value: Does not need to updateall rows to default value.
Labels: Oracle11g
December 02, 2008
Oracle Database 11g New Features
1) Automatic Diagnostic Repository [ADR]
2) Database Replay
3) Automatic Memory Tuning
4) Case sensitive password
5) Virtual columns and indexes
6) Interval Partition and System Partition
7) The Result Cache
8) ADDM RAC Enhancements
9) SQL Plan Management and SQL Plan Baselines
10) SQL Access Advisor & Partition Advisor
11) SQL Query Repair Advisor
12) SQL Performance Analyzer (SPA) New
13) DBMS_STATS Enhancements
14) The Result Cache
15) Total Recall (Flashback Data Archive)
Note: The above are only top new features, there are other features as well introduced in 11g which will be included subsequently
Oracle 11g Database DBA New Features with brief explanation ==========================================
# Database Capture/replay database workloads :
This allows the total database workload to be captured, transferred to a test database create from a backup or standby database, then replayed to test the affects of an upgrade orsystem change. Currently, these are working to a capture performance overhead of 5%, so this will capture real production workloads
# Automatic Memory Tuning:
Automatic PGA tuning was introduced in Oracle 9i. Automatic SGA tuning was alreadyintroduced in Oracle 10g. But In 11g, all memory can be tuned automatically by setting oneparameter. We can literally tell Oracle how much memory it has and it determines how much to use for PGA, SGA and OS Processes. Maximum and minimum thresholds can be set.
# Interval partitioning for tables :
Interval partitions are extensions to range partitioning. These provide automation for equi-sized range partitions. Partitions are created as metadata and only the start partition ismade persistent. The additional segments are allocated as the data arrives. The additionalpartitions and local indexes are automatically created.
# Feature Based Patching:
All one-off patches will be classified as to which feature they affect. This allows you to easilyidentify which patches are necessary for the features you are using. EM will allow you tosubscribe to a feature based patching service, so EM automatically scans for availablepatches for the features you are using
# RMAN UNDO bypass :
Rman backup can bypass undo. Undo tablespaces are getting huge, but contain lots ofuseless information. Now rman can bypass those types of tablespace. Great for exporting a tablespace from backup.
# Virtual columns/indexes :
User can create Virtual index on table. This Virtual index is not visible to optimizer, so it willnot affect performance, Developer can user HINT and see is Index is useful or not.InvisibleIndexesprevent premature use of newly created indexes
# New default audit settings :
Oracle database where general database auditing was "off" by default, logging is intendedto be enabled by default with the Oracle Database 11g beta secure configuration. Notableperformance improvements are planned to be introduced to reduce the performancedegradation typically associated with auditing.
# Case sensitive password :
Passwords are expected to also become case sensitive This and other changes should resultin better protection against password guessing scenarios. Forexample, in addition to limiting the number of failed login attempts to 10 (defaultconfiguration in 10gR2), Oracle 11g beta’s planned default settings should expirepasswords every 180 days, and limit to seven the number of times a user can login with anexpired password before disabling access.
# Faster DML triggers :
Create a disabled trigger; specify trigger firing order
# Fine grained access control for Utl_TCP:
in 10g all port are available, now it is controlled.
# Data Guard supports "Flashback Standby"
# New Trigger features
# Partitioning by logical object and automated partition creation.
# LOB's - New high-performance LOB features.
# New Oracle11g Advisors
# Enhanced Read only tables
# Table trigger firing order
# Enhanced Index rebuild online : - Online index build with NO pause to DML.
# No recompilation of dependent objects:- When
A) Columns added to tables
B) Procedures added to packages
# Improved optimizer statistics collection speed
# Online index build with NO pause to DML
# Read only table :-
alter table t read only
alter table t read write
For Complete list of 11g New Features, You can refer to the following link
http://www.oracle.com/technology/pub/articles/oracle-database-11g-top-features/index.html
Labels: Oracle11g