Oracle Database 1. New Features. The following sections describe Availability features for Oracle Database 1. Release 2. 1. 2. 1 Fast- Start Failover to Standby Database. In Oracle Database 1.
In Oracle 10g R2 the SGA size can be increased to approximately 2.7 GB using the smp kernel and to approximately 3.42 GB using the hugemem kernel. 1.1.2 Globalization and Unicode Improvements. Globalization and Unicode support have been enhanced in Oracle Database 10 g Release 2. Consistent linguistic ordering. Oracle Reports is a tool for developing reports against data stored in an Oracle database. Oracle Reports consists of Oracle Reports Developer (a component of the. Oracle offers a comprehensive and fully integrated stack of cloud applications and platform services. The butt of his friends, the chartered oracle of the barrooms, even in whose wretched vanity there was always the haunting suspicion that he was despised and scorned. Oracle Forms is a software product for creating screens that interact with an Oracle database. It has an IDE including an object navigator, property sheet and code.
Release 2, Oracle Data Guard offers a compelling set of capabilities that provide unparalleled levels of data availability, data protection, and data recovery. For example, on an outage of the primary server, site, or network, the new Fast- Start Failover feature allows Data Guard to rapidly and automatically fail over to the standby database, without requiring manual intervention.
This significantly improves the degree of high availability as well as the disaster resilience for the system infrastructure. This capability makes Data Guard particularly attractive as a high availability/disaster recovery solution for 2. Fast- Start Failover. On a failure or outage of the primary server or site, or of the network, Data Guard can now rapidly and automatically fail over to a previously chosen standby database, without requiring manual intervention. The benefit of fast- start failover is that it increases the degree of high availability, as well the robustness of disaster recovery, for the system infrastructure. It also reduces manual operations, thereby reducing management costs. This makes Data Guard particularly attractive as a high availability/disaster recovery solution for 2.
Preparing to pass Oracle certification exams will expand your knowledge and skill set. View Agile, Hyperion, PeopleSoft exams and more. Oracle Database 11g Express Edition Free to develop, deploy, and distribute. Oracle Database 11g Express Edition (Oracle Database XE) is an entry-level, small.
Automatic Conversion of the Primary Database to a Standby Database Upon Failover. After a failover, this feature allows the old primary database to be automatically reinstated as a standby database, without requiring re- creation of the primary, or manually performing the Flashback Database operation. This feature is supported only for synchronous redo transports that enabled zero data loss (that is, Maximum Protection and Maximum Availability modes). It also requires Flashback Database to be enabled on both the primary and target standby databases. It is also possible to do this conversion using a single command or a simple push- button interface through Enterprise Manager. The benefit of this feature is that it enables the Data Guard configuration to easily restore disaster protection in the configuration, without complex manual steps, improving the robustness of the disaster recovery features of Data Guard, as well as improving Data Guard manageability.
Oracle SQL 10g Fundamental I 1. Oracle Database 10g: SQL Fundamentals I Volume I • Student GuideD17108GC11Edition 1.1August 2004D39766 ® 2.
Optimized Asynchronous Redo Transmission. Asynchronous redo transmission using the log writer process is no longer limited by the size of the network buffer.
The log writer process is no longer blocked on network time outs during asynchronous redo transmission. This allows a greater number of archiver processes to archive redo logs remotely. The benefit of this feature is that it reduces any effect on the primary database during asynchronous redo transmission.
It allows faster redo transmission to standby databases for bulk batch updates on the primary database. Faster Redo Apply Failover. This feature allows the user to activate a physical standby database (that is, fail over to a primary database) that has never been opened read- only, without doing a database restart.
The benefit of faster Redo Apply failover is that it enables customers to recover from a failure or outage much faster, increasing the degree of high availability of the system. Faster SQL Apply Failover. Failover to a logical standby database can now be completed much faster. It is no longer necessary to restart SQL Apply as part of the failover operation.
The benefit of faster SQL Apply failover is that it enables recovery from a failure or outage much faster, increasing the degree of high availability of the system. Support for Database Transport Across Same Endian Platforms. Oracle Database 1. Release 2 introduces database transport across the same Endian platforms which provides a fast and easy way to transport the whole database across platforms with the same Endian format. This feature uses RMAN to quickly convert the datafiles and create the new database. The newly created database is a copy of the source database but on a different operating system/hardware platform; for example, fast Windows to Linux or Solaris to HP- UX migration. Database Transport Across Same Endian Platforms.
This transport feature provides a fast method to move a database from one platform to another. The ability to migrate databases from one platform to another has become more important for Oracle customers. Oracle Data Pump can export the entire database, but it may be time consuming because it uses the SQL layer to process data. Database transport across the same Endian platforms provides a faster and easier way to move Oracle databases from one platform to another. High Availability Improvements. Oracle Database 1. Release 2 continues to enhance the built- in database features for recovery and testing operations to be expeditious, simple, and automatic.
Employing Recovery Manager (RMAN) and Flashback Database further reduces the DBA's time spent on the important task of database backup and recovery and creation of test databases. In this release, Data Guard has also optimized the network transmission of redo data, enabling standby databases to be synchronized with the primary database at a faster rate than in previous releases, with minimal effect on the primary database. Similarly, Data Guard has considerably improved its manageability and ease- of- use compared to previous releases, allowing administrators to monitor the state and performance of the disaster recovery configuration at a higher granular level. Add and Create a Transportable Tablespace to a Database. This feature allows a DBA to: Generate a tablespace set from the source database and plug it into the target database, essentially automating movement of tablespaces between the databases. Generate a tablespace set which can be used to transfer a tablespace to any compatible database. Plug- in the tablespace set (provided by the user) into the target database and perform an import operation.
Using this tool, database administrators can automate the process of transporting tablespaces across databases. Tablespaces can be transported between databases running on different platforms using different supported versions. This user- friendly tool performs checks and validations, which are needed to ensure valid and compatible tablespace sets for plugging into the target databases.
Additional Data Type Support in Log. Miner and SQL Apply.
SQL Apply, Log. Miner, and Streams now support IOTs with overflow segments and LOBs. This feature allows Data Guard SQL Apply and Log. Miner to be used for protection of a broader range of data types.
Similarly, Streams can be used for replication of a broader range of data types. Automatic Deletion of Applied Archive Logs. Archived logs, once they are applied on the logical standby database, will be automatically deleted by SQL Apply. This feature reduces storage consumption on the logical standby database and improves Data Guard manageability.
Data Guard: Improved Manageability for Redo Transport, Log Apply, and Broker. This feature deprecates unnecessary initialization parameters and attributes for Oracle Database 1.
Release 2. This feature simplifies the usage of initialization parameters and attributes, as well as certain SQL statements. Dynamic RMAN Channel Allocation for Backing Up and Recovering RAC Database. By configuring parallelism when backing up or recovering a RAC database, RMAN channels are dynamically allocated across all RAC instances. This is similar to dynamic RMAN channel allocation for a single instance. Channel failover allows a failed operation on one node to be continued on another node.
This feature eliminates manual allocation of RMAN channels for each RAC node. It also provides better tolerance of media failures (that is, when one node fails, another node can continue backup work). RMAN Backup Encryption. RMAN now creates encrypted backups that cannot be restored by unauthorized people. There are 3 modes of backup encryption: Transparent encryption. Password encryption. Dual- mode encryption using either transparent or password encryption.
Backup encryption is a regulatory requirement for many customers. The presence of this capability in Oracle obviates the need to purchase it elsewhere. Easy Conversion of a Physical Standby Database to a Reporting Database.
A physical standby database may be activated to be a primary database, opened read/write for reporting purposes, then flashed back in the past to be easily converted back to a physical standby, upon which Data Guard will automatically synchronize the standby database with the primary database. This mechanism also allows a physical standby database to be used as part of a clone, test, or development solution.
Note that while this database is open for reporting, it will not be able to receive any redo data from the primary database. Therefore, such a configuration may be more suitable for customers with less demanding disaster recovery requirements. This feature allows the physical standby database to be utilized for reporting, read/write, and cloning activities, enabling customers to extract more value out of their Data Guard investment. Eliminate Control File Re- Creation. With the control file enhancements, there is no longer a requirement to re- create the control file when changes in the configuration parameters are made.
These include the MAXLOGFILE, MAXLOGMEMBERS, MAXLOGHISTORY, MAXDATAFILES, and MAXINSTANCES parameters. This feature eliminates database downtime when a configuration parameter change is made in the control file. Enhanced Memory Corruption Checking. A new value of MAX has been added to the database parameter, DB_BLOCK_CHECKSUM, to compute checksums on the reading, updating, and deleting of a block. This feature enhances the ability to validate the block when it is in memory and not just on disk. Enhanced RMAN Backup Job Views.
The new RMAN views correlate and simplify the metadata of an RMAN backup job.