X

Recent Posts

Database Appliance

Oracle Database Appliance X8 More Powerful, Higher Capacity, Improved Connectivity

ODA has experienced broad adoption around the world in all industries across a wide range of customers, from SMBs to Fortune 100 corporations. As a result, we continue to invest in Oracle Database Appliance by offering the latest generation hardware along with on-going software enhancements for all supported models.  We are committed to maintaining Oracle Database Appliance as the database platform of choice for customers looking to realize the benefits of: Simple, Optimized, Affordable Database System with Built-in Automation Integrated full-stack patching Pay As You Grow, Capacity-On-Demand Oracle Database Licensing  Cost-effective Consolidation Platform for Databases and Applications On-premises Database Platform Offering a Path to the Cloud    We are excited to announce Oracle Database Appliance X8!   Key Enhancements: More Powerful New Intel Xeon Gold 5218, 16-core, 2.3GHz processors with fixes for Spectre and Meltdown vulnerabilities, provide CPU performance improvements.  Higher Storage Capacity ODA X8-2M supports up to 76.8TB NVMe storage, 50% more than X7 ODA X8-2-HA base configuration includes 46TB SSD storage (240% more than X7), expandable to 369TB SSD (250%+ more than X7) or 596TB SSD+HDD (175%+ more than X7) Improved Network Connectivity Support for up to 3 network cards per server: 25GbE SFP28 (Fiber) or 10GBase-T (copper) options Flexibility to separate customer database client network traffic from backup, management, or other traffic. Oracle Database 19c Support Run Oracle Database 19c Enterprise Edition and Standard Edition 2, the latest long-term support releases, in addition to 18c, 12g, and 11g.   Recent ODA Software Enhancement for All Supported Models: Simplified backup and restore The Brower User Interface enables backup and restore for both on-premise and Oracle cloud. Supports backup to local storage, NFS storage, or Object Store in Oracle Cloud. Enhanced system availability for ODA Standard Edition users We are introducing integrated HASE (High Availability Standard Edition) that provides active-passive failover to enhance system availability for Standard Edition users on ODA Built-in automation configures HASE for SE failover--no additional software licenses required. Backup and restore system configuration ODABR - A new backup and restore utility is available for administrators to create a local disk snapshot for ODA bare metal systems. Patching enhancements to improve security and availability Out of Cycle Database and OS Patching uncouples Critical Database Patches from the ODA Bundle Patch so that critical database updates and kernel RPMs can be installed independently of the current bundle patch. This allows users to implement the most current critical patches to meet security and compliance requirements as soon as they become available. Rolling patching has been enhanced to include shared storage and eliminate the need for planned outages for storage updates. Individual drives are patched without disruption, allowing the system to continue to run during firmware updates. Monitoring enhancements to improve operability The ODA Brower User Interface (BUI) allows users to display per node metrics for data collection, detailed diskgroup storage utilization, feature usage and high-water marks, and software bill of materials tracking for richer system management. Please refer to the ODA X8 product pages for more details on each configuration. For more information on ordering options and pricing, contact your Oracle sales representative.    

ODA has experienced broad adoption around the world in all industries across a wide range of customers, from SMBs to Fortune 100 corporations. As a result, we continue to invest in Oracle Database...

Database Appliance

Storage Expansion Guide for ODA X7 and X6 Systems

Revised November 2019 Oracle Database Appliance X7 and X6 both offer some flexibility on the storage capacity of the systems.  It’s recommended that you initially configure the system with enough storage capacity to accommodate future data growth.  However, if you experience more data growth than you expected and purchased an ODA with a partially populated storage configuration, you can add storage for additional capacity. customers should always be on the latest release when adding storage. Note: We recommend you upgrade to the latest ODA software release before adding storage to ensure you have the latest firmware. Single Node Models   ODA X7-2 Single Node Models The Oracle Database Appliance X7-2S/M base system was shipped with two 6.4TB NVMe Drives, providing 12.8TB raw storage. The ODA X7-2M offers the option to expand up to 51.2TB of raw storage by adding up to six additional 6.4TB NVMe Drives. (When you expand storage, you must add three NVMe Drives at a time, adding just one or two NVMe Drives is NOT supported.) The storage for the ODA X7-2S can’t be expanded to more than 12.8TB raw storage (two 6.4TB NVMe Drives).   CONFIGURATION ODA X7-2S ODA X7-2M BASE CONFIGURATION Two 6.4TB NVMe Drives populated in Slots 0 & 1 Two 6.4TB NVMe Drives populated in Slots 0 & 1 EXPANSION OPTIONS None Three 6.4TB NVMe Drives populated in Slots 2 - 4 (Order Qty 1 - 7117431 and upgrade to 12.2.1.4 or later) or Six 6.4TB NVMe Drives populated in Slots 2 - 7 (Order Qty 2 - 7117431 and upgrade to 12.2.1.4 or later)   ODA Release 12.2.1.4 and later supports expansion after initial deployment.  The initial ODA X7-2S/M release only supported the first generation of 6.4TB NVMe Drives.  Beginning with ODA release 18.5, the second generation of 6.4TB NVMe Drives referred to as v2 are also supported for storage expansion. Refer to the Oracle Database Appliance documentation for more information on the steps to add ODA X7-2S/M NVMe Drives.   X6-2 Single Node Models The Oracle Database Appliance X6-2S/M base system was shipped with two 3.2TB NVMe Drives, providing 6.4TB raw storage. Two additional 3.2TB NVMe Drives can be added to expand the capacity to 12.8TB raw storage. The ODA X6-2L base system came with 19.2TB NVMe raw storage (six 3.2TB NVMe Drives), expandable to 28.8TB raw storage by adding three additional 3.2TB NVMe Drives. The 3.2TB NVMe Drives are no longer available, however, starting with ODA release 12.2.1.4 the first generation of 6.4TB NVMe Drives are supported to expand the storage. And beginning with ODA release 18.5, the second generation of 6.4TB NVMe Drives referred to as v2 are also supported for storage expansion.   The table below shows how 6.4TB NVMe Drives can be used in the X6-2S/M/L.   CONFIGURATION SCENARIO OPERATION RESULT X6-2S/M Base Configuration Storage Expansion 3.2TB NVMe Drives populated in Slots 0 & 1 Add 6.4TB NVMe Drives to Slots 2 & 3 (Order Qty 2 - 7120558 and upgrade to 18.5 or later) 6.4TB NVMe Drives partitioned to 3.2TB X6-2L Base Configuration Storage Expansion 3.2TB NVMe Drives populated in Slots 0,1,3,4,6,7 Add 6.4TB NVMe Drives to Slots 2,5,8 (Order Qty 3 - 7120558 and upgrade to 18.5 or later) 6.4TB NVMe Drives partitioned to 3.2TB   If all the 3.2TB NVMe Drives are replaced with 6.4TB NVMe Drives, the system can be redeployed to utilize the full capacity.  Refer to the Oracle Database Appliance documentation for more information on the steps to add ODA X6-2S/M/L NVMe Drives.   High Availability Models   ODA X7-2-HA Model The Oracle Database Appliance X7-2-HA base system ships with five 3.2TB SSDs providing 16TB SSD of raw storage for DATA and 3.2TB SSD raw storage for REDO. The system provides two storage expansion configuration options, all SSDs for high performance or SSDs in the base system plus HDDs for high capacity. ODA Release 12.2.1.4 and later supports expansion after initial deployment.  High-Performance SSD Option The high-performance ODA X7-2-HA configuration provides up to 64TB raw SSD storage per storage shelf Add up to three 5-packs of 3.2TB SSDs to the base system starting with slot 5 up to slot 19 Double the storage by adding a fully populated SSD expansion shelf for an additional 64TB SSD raw storage for DATA and 3.2TB SSD raw storage for REDO The base storage shelf must be fully populated before you can add the expansion shelf The expansion shelf must be the same as the base shelf High Capacity HDD Option The high capacity ODA X7-2-HA configuration provides 150TB of HDD raw storage.  You can purchase the 15-pack of 10TB HDDs after the initial base system deployment, but you will need to move the SSDs in the base system to Slots 15-19 and re-deploy the system You can add a fully populated HDD expansion shelf for an additional 150TB HDD raw storage for DATA, 3.2TB SSD for REDO, and 16TB SSD for FLASH The base storage shelf must be fully populated before you can add the expansion shelf The expansion shelf must be the same as the base shelf   CONFIGURATION ODA X7-2-HA Base Configuration Four 800GB SSDs populated in Slots 20 – 23 Five 3.2TB SSDs populated in Slots 0 - 4 Expansion Options ODA X7-2-HA ALL SSDs for HIGH-PERFORMANCE ODA X7-2-HA SSD AND HDD for HIGH-CAPACITY Base Shelf Expansion   Up to three 5-packs of 3.2TB SSDs populated in Slots 5 - 19 (Order Qty 1, 2, or 3: 7117369: Five 3.2TB SSD drive-pack and upgrade to 12.2.1.4 or later) Five 3.2TB SSDs moved to Slots 15 – 19 Fifteen 10TB HDDs populated in Slots 0 – 14 (Order Qty 1: 7117704: Fifteen 10TB HDD drive-pack and upgrade to 12.2.1.4 or later) Expansion Self Expansion Shelf with Four 800GB SSDs and Twenty 3.2TB SSDs (Order Qty 1 - 7119675 - Twenty 3.2 TB SSDs and four 800 GB SSDs and upgrade to 18.5 or later) Expansion Shelf with Four 800GB SSDs, Five 3.2TB SSDs and Fifteen 10TB HDDs (Order Qty 1 - 7119676 - Fifteen 10 TB HDDs, Five 3.2 TB SSDs, and Four 800 GB SSDs and upgrade to 18.5 or later)   Refer to the Oracle Database Appliance documentation for more information on the steps to add ODA X7-2-HA drives.   ODA X6-2-HA Model The Oracle Database Appliance X6-2-HA only support SSDs.  The 200GB SSDs are dedicated for database REDO while 1.6TB SDDs are used for DATA. The storage shelf can be half-populated with 1.6TB SSDs to provide 12TB of raw storage. The storage shelf can be expanded to be fully populated for a total of 24TB of raw storage. An expansion shelf can also be added to provide an additional 24TB of raw storage. Since the 1.6TB SSDs are no longer available, the ODA X6-2-HA storage can be expanded using 3.2TB SSDs as long as the system is running ODA Release 12.2.1.4 or later. The table below shows how 3.2TB SSDs can be used in the X6-2-HA.   CONFIGURATION SCENARIO OPERATION RESULT X6-2-HA Base Configuration Base Shelf Expansion Ten 1.6TB SSDs in slots 0 - 9 and four 200GB SSD in slots 20 - 23 Add Ten 3.2TB SSD in slots 10 - 19 (Order Qty 2 -7117369 - Five 3.2TB SSD drive pack and upgrade to 12.2.1.4 or later) 3.2TB SSDs partitioned to 1.2TB X6-2-HA with Fully Populated Shelf Expansion Shelf Twenty 1.6TB/3.2TB SSDs in slots 0 - 19 and four 200GB SSD in slots 20 - 23 Add X7-2 fully populated expansion shelf with four 800GB and twenty 3.2TB SSDs (Order Qty 1 - 7119675 - Twenty 3.2 TB SSDs and four 800 GB SSDs and upgrade to 18.5 or later) 800GB SSDs partitioned to 200GB and 3.2TB SSDs partitioned to 1.2TB   If all the 1.6TB SSDs are replaced with 3.2TB SDDs, the system can be redeployed to utilize the full capacity. REDO can be expanded by replacing all the 200GB SSDs with 800GB SSDs and redeploying the system to utilize the full capacity. Refer to the Oracle Database Appliance documentation for more information on the steps to add ODA X6-2-HA SSDs.    

Revised November 2019 Oracle Database Appliance X7 and X6 both offer some flexibility on the storage capacity of the systems.  It’s recommended that you initially configure the system with enough...

Database Appliance

Oracle Database Appliance (ODA) Appliance Manager Continued Support and Persistiveness Scripts

Oracle Database Appliance launched its first model, V1, in Oct 2011.  Since then, additional hardware models have been released with the ability to run the same version of the Database Appliance Manager software across all Database Appliance hardware models. Oracle Database Appliance Manager software has a support life of five years. The following models have reached the five-year expiration date for Appliance Manager software certification: Oracle Database Appliance Manager software certification (e.g. odacli and oakcli) for ODA X3-2 ended with the 18.5 release.  Oracle Database Appliance Manager software certification (e.g. oakcli) for ODA V1 ended with the 12.2.1.4 release.  The table below should be used for planning and discussion purposes only.  ODA Hardware Model First Ship Date Last Order Date Appliance Manager Software Support ODA V1 Oct 2011 March 2013 July 2018 - Last supported Appliance Manager release:  12.2.1.4 ODA X3-2 March 2013 Dec 2013 Mar 2019 - Last supported Appliance Manager release:  18.5 ODA X4-2 Dec 2013 Apr 2015 Apr  2020 - Last supported Appliance Manager release:  18.8 ODA X5-2 Feb 2015 Nov 2017 Nov 2022 ODA X6-2 (all models) June 2016 Nov 2017 Nov 2022 ODA X7-2 (all models) Oct 2017         FAQs:   Q:  Can I continue to use my Database Appliance beyond the Appliance Manager last support date? A:  Yes -You will need a valid Oracle hardware support contract and a valid Database software support contract in place.   Q: How can I update my databases after the Appliance Manager software last support date? A: ODA bare-metal customers who want to update their databases, must run the ODA-Persistiveness script to convert their ODA into a generic x86 system.  Customers do not need to re-image or re-deploy their databases. After the ODA-Persistiveness script is run, customers can use standard x86 administrative methods to update firmware, the Linux Operation System (OS), and databases.   Customers running ODA virtualized systems who want to update their databases after the Application Manager last support date, must first back up their databases, and install the Oracle VM Server software, and re-deploy their databases with Oracle VM (OVM).  (Please see the Oracle Virtualization documentation for more information at https://docs.oracle.com/en/virtualization/).   Note: Standard OVM virtual machines do not have PCI pass-through like ODA_Base, so virtual machines may see a degradation in I/O performance.    Q: Where can I find the correct ODA-Persistiveness scripts? A: The ODA-Persistiveness script for V1 can be downloaded here:  oda_persistiveness_V1​.pl      The ODA-Persistiveness script for X3-2 can be downloaded here: oda_persistiveness_X3-2.pl   Q: How do I use the ODA-Persistiveness scripts? A: Run the script from the 1st node (Node 0). After the script has successfully finished running on the 1st node (Node 0) , run the script on the 2nd node (Node 1). Manually restart the crs/clusterware for both nodes if crs/clusterware is down.   NOTE: If the script had previously successfully completed on the 1st node (Node 0) and rebooted, it is only necessary to run the script on the 2nd node (Node 1). This will stop the clusterware on both nodes, and you will need to manually start clusterware for the 1st node after rebooting the 2nd node.   Q: Where can I find more information about Oracle x86 hardware and database support? A: Oracle hardware and database software will continue to be supported as long as the support contract is in effect. Please see the details below: https://www.oracle.com/support/lifetime-support/index.html http://www.oracle.com/us/support/library/057419.pdf   Q: What if I need a security patch that becomes available after the Appliance Manager last support date?  A:  The best practice is to keep your system and software up-to-date.  It is recommended that you run the ODA-Persistiveness script and maintain the hardware as a generic x86 system.    Q:  Can I apply future Database Appliance patches after the last support date? A:  Yes -  However, understand we do not test new versions of the Database Appliance Manager software on models that are beyond the last support date listed.  If you would like to continue to use the hardware platform, it is recommended to run the ODA-Persistiveness script and maintain it as a generic x86 system.   Q:  Could I just apply the GRID and Database PSU/BP/RU to the ODA after the Appliance Manager last support date?     A:  Only after the ODA-Persistiveness script has been run on your Database Appliance.  Oracle Grid Infrastructure and Database software schedule and support information are maintained independently of the Database Appliance Patch releases.    Q:  If I run the ODA-Persistiveness script, is the hardware supported beyond the Appliance Manager last support date? A:  Yes - As long as your hardware support contract is in effect, hardware replacements are supported. Please consult Oracle Support to understand any hardware specific issues.  

Oracle Database Appliance launched its first model, V1, in Oct 2011.  Since then, additional hardware models have been released with the ability to run the same version of the Database Appliance...

Database Appliance

Introducing: ODABR - A Backup/Restore Utility for ODA System Nodes

When applying maintenance to Oracle Database Appliance, it's best practice to back up the ODA system environment (local system boot disk). DBAs have procedures to backup and recover the database but it is also important that you are able to backup and recover the environment that runs the database. ODA administrators should have a regular backup plan for their ODA operating system environment and there are many tools available for backing up and restoring. This is a best practice for any Linux server and we are emphasizing this best practice for the ODA. This is especially useful if you encounter an issue during patching; you can quickly restore the system disk back to the pre-patch state. In response to our user's requests, we are providing a new backup and restore option, an optional utility downloadable from My Oracle Support, (ODABR a System Backup/Restore Utility Doc ID 2466177.1). Significant changes happen on ODAs most often during the application of new ODA patch bundles. ODABR's ability to backup and restore the ODA system environment gives users a rapid recovery path to the last known working state of their production system and helps avoid a complete rebuild of the underlying environment in the event of a failed attempt at updating or patching the system.   ODABR provides users with the ability to perform a consistent point-in-time backup of the ODA System Node with a single command.   ODABR utilizes the Linux LVM (Logical Volume Manager) Snapshot feature.  An LVM snapshot is an exact space-efficient copy of an LV (Logical Volume) at a point in time with all the data from the original LV. After taking a snapshot, you have two copies of the same LV, one containing the state of the system at the time of the snapshot and another that reflects the ongoing state of the system   The two obvious advantages of Snapshots are: Snapshot creation is instantaneous; no need to stop your production environment. A Snapshot only uses the space needed to accommodate the difference between the two LVs and this is accomplished by tracking changes between the LV and the LV's snapshot version.   An ODA System Node Backup Creates image Copies for the Following: – Root file system (/) – Boot partition (/boot) – opt file system: OAK/DCS,TFA, OWG, ASR (/opt) – u01 file system: Grid Infrastructure, RDBMS binaries – Grid Infrastructure OCR file   ODABR Provides an ODA System Node Backup and Restore Using a Single Command ODABR backup has two forms of backup:             "-snap" (typical form) - Creates a local point-in-time backup             "-destination" - Creates a remote backup that is updated incrementally   Using "-snap" option, odabr will create an LVM snapshot for: /dev/VolGroupSys/LogVolU01 /dev/VolGroupSys/LogVolOpt /dev/VolGroupSys/LogVolRoot "-snap" also performs: An image copy of boot partition, storing the "/boot" partition image as "/opt/odabr/out/hbi/boot.img” The Grid Infrastructure ocr backup as /opt/odabr/out/hbi/ocrbackup_<pid>.bck These snapshots can be used to restore the host back to the state captured by the snapshot using the command "odabr restore -snap" For the majority of customers, it's recommended that you follow the simple steps below to create a backup in preparation before applying your patches or changes. Suggested Workflow for Backup and Restore: It's best to take a backup on BOTH nodes in an ODA HA before you start the upgrade on any of the nodes. It's also a good idea to check the disposition of your backup after it's created and before it's used to restore to be certain it is not marked inactive.   It is recommended you use the LVM only option for patching operations and you should delete the LVM snapshots when patching successfully completes and you’re comfortable that everything is working. We also suggest that when you create an LVM snapshot backup for patching that you try and patch during off-peak hours. If you want to keep a long-term backup you should create a remote copy using the -destination ssh://backup@remotehost:/backup option.     odabr backup -snap   (Takes a snapshot of LVs) odabr infosnap   (Let's you verify the Snapshot is successful) Apply patches or updates, preferably during off-peak hours. if patches or updates have a problem and after all attempts to repair have been unsuccessful, you can restore the System Node snapshot following the remaining steps.  odabr infosnap   (Make sure the backup is not marked inactive and if not continue with the restore)  odabr restore -snap -boot  (Restore from snapshot, this operation will automatically restore the boot partition as well.  To restore only the boot partition without touching any other files, issue "odabr restore -boot"). If patching or updating is successful you can delete the snapshot after rebooting. Reboot the node(s)   ODABR Backup to Create a Snapshot and a Remote File Copy By default ODABR creates LVM snapshots with the following standard factory LVM sizes: root LVM snapshot 30Gb  opt LVM snapshot 60Gb u01 LVM snapshot 100Gb If you have modified the sizes of our logical volumes from factory defaults, you may have less then 190 Gb of total available free space.  You can override these sizes using the command options for root, opt or uo1 to specify a specific size: -rsize -osize -usize As your LVs will likely be larger than your snapshot volumes, there may be insufficient space to track all changes.  In that case, you should save the backup to a remote destination prior to patching the system. (NOTE: You must make certain there is always enough free space to keep all blocks changes or your backup will be marked inactive for restore, in this case, you must save the backup to a remote destination prior to patching the system. See the next section).   Using "-destination", ODABR will create a LVM snapshot for "/u01", "/opt" and/or "root" (based on the selection) and: Using "rsync" ODABR will create a physical copy of files, not a Snapshot, to the destination specified in "-destination" and the destination can be local, remote ssh host (ssh://USER@HOST:PATH), or remote rsync daemon (rsync://USER@HOST/PATH) The "-destination" option gives you the ability to copy the entire contents of the files specified to another location for an added layer of recovery and it also allows customers to store multiple copies of their backups and retain them indefinitely.   (Note: in order to use "ssh/rsync" as a destination, appropriate ssh and/or rsync daemon must be configured on destination) LVM snapshots are taken prior to copying the data to provide a consistent point-in-time backup.  If you have insufficient free space in the volume group to support the default snapshot sizes, use the -osize, -rsize, and -usize parameters to specify smaller snapshot sizes.  If using the "-destination" option to copy the backup prior to starting the patching operation, very little snapshot space is required.  Once the copy (rsync) is executed, the underlying LVM snapshots are automatically removed but if you want to keep the LVM snapshots after the rsync execution, the "-snap" option must be used along with the "-destination" option.  Unless you know your snapshot volumes will have insufficient space to track all the changes expected through the patching process, it is a good idea to retain the snapshot as it may be available to more quickly and easily recover in the event of an issue. Example:  odabr backup -snap -destination ssh://backup@remotehost:/backup This combination provides you with the dual functionality of having both Snapshots and copied files residing in different locations for multiple restore options.   ODBR Has Some Limitations to Consider:  Using ODABR "restore" requires that files are not in use by running processes.  For this reason, you must boot the system with a Linux recovery disk to restore the system from a remote destination.  Contact support for assistance with any restoration from a remote copy. It's important to understand that ODABR is NOT for backing up or restoring the Oracle Database itself and you can't use ODABR to back up ASM (Automatic Storage Management) content. ODABR works on ODA BM (Bare Metal) only but will work with both the OAK and DCS stacks. When restoring an LVM snapshot and the previous Grid Infrastructure binaries, it may be necessary to restore the OCR/Voting file as well. ODABR saves the current OCR under "/opt/odabr/out/hdi/ocrbackup_<pid>.bck". (the documentation explains how to restore the OCR and Voting file). ODABR should not be used as a tool to perform a Grid Infrastructure downgrade.     Acknowledgment: Thanks to Sanjay Singhn and the RACPAC team, and especially to Ruggero Citton, the creator of ODABR.      

When applying maintenance to Oracle Database Appliance, it's best practice to back up the ODA system environment (local system boot disk). DBAs have procedures to backup and recover the database but...

ODA Plug-In for Enterprise Manager Cloud Control Now Available!

Enterprise Manager Cloud Control provides unattended monitoring of your IT environment and key components such as applications, application servers, databases, and your Oracle Database Appliance!   The updated ODA-EM Plug-In not only supports all of the ODA hardware models from V1 through X7-2 but also offers:  Centralized console to monitor a single ODA or multiple ODA Simple, intuitive tag-based model to create ODA groups Actionable component level analytics across an ODA group Hierarchical viewer to show component relationships Full support for both bare-metal and virtualized ODAs Version 13.2.2.1 of the ODA Plug-In supports Enterprise Manager Cloud Control versions 13.3 and 13.2 and can be updated in your Enterprise Manager Cloud Control environment through the Enterprise Manager Store or by importing the ODA opar file into the OMS.  You can find more details on the ODA Plug-In features in the Oracle Database Appliance Plug-In documentation or take a look at this presentation. Want to Deploy Enterprise Manager Cloud Control on ODA? If you are looking for a platform to deploy your Enterprise Manager Cloud Control, the Oracle Database Appliance white papers present a solution for high availability and single instance architectures. Solution-in-A-Box: Deploying Highly Available Monitoring Infrastructure using Oracle Enterprise Manager Cloud Control 13cR2 and Oracle Database Appliance Solution-in-a-Box: Deploying Cost-effective IT Manageability Infrastructure Using Oracle Enterprise Manager and Oracle Database Appliance (Oracle Enterprise Manager 13c Release 2 Deployment on Oracle Database Appliance X7-2S / X7-2M For more information Enterprise Manager Cloud Control Plug-In Documentation Oracle Database Appliance Plug-In Documentation Download the Oracle Database Appliance OPAR file  

Enterprise Manager Cloud Control provides unattended monitoring of your IT environment and key components such as applications, application servers, databases, and your Oracle Database Appliance!   The...

Product News

Get Ready for the ODACLI stack on your ODA!

In a past blog, I talked about the two ODA software stacks  – oakcli and odacli/odaadmcli.  The oakcli stack is the original Database Appliance software that provides automated deployment, patching, database provisioning, and monitoring.  Starting with the ODA X6-2S/M/L hardware, we introduced a new software stack called ODACLI/DCS.  The ODACLI/DCS stack was designed to work with the Oracle Cloud (OCI) services as well as on premise with the ODA.  Over the past two years a lot of work has gone into adding more automated functionality as well as a new UI interface that we call the Web Console. The ODA mantra is to use the same Database Appliance stack on all versions of the ODA hardware.  And now that is going to happen on the bare metal deployments with the release of the 18.3 ODA Patch.  What does that mean to you? If you are running on the ODA with the virtualized platform deployed, then nothing changes with the 18.3 patch.  The OAKCLI command line structure will remain until a future release.  Stay tuned for updates on KVM on ODA. If you are running on ODA X7-2-HA bare metal, X7-2S/M or X6-2S/M/L, then there is very little impact but to patch your ODA to the 18.3. release. If you are running on bare metal ODA X6-2-HA, X5-2, X4-2 or X3-2, the 18.3 patch release will migrate your ODA to the ODACLI/DCS software stack.  Your only difference will be the commands that you use to manage the ODA. Let’s compare a few of the ODA commands. Task ODACLI/DCS OAKCLI View the ODA State   validate Plumb the ODA network configure-firstnet configure firstnet Provision ODA create-appliance deploy View ODA details describe-appliance list details Configure ASR configure-asr configure asr Enable additional cores update-cpucore update-cpucore View database homes list-dbhomes show dbhomes View databases list-databases show databases Create new database create-database create database   For more information on the ODACLI/DCS commands, take a look at the latest ODA Documentation here:  ODACLI/DCS commands

In a past blog, I talked about the two ODA software stacks  – oakcli and odacli/odaadmcli.  The oakcli stack is the original Database Appliance software that provides automated deployment, patching,...

Product News

Implementing CIS with a Single Command on ODA

It is good to get your name in the news, right?  Well, the good news anyway, but not so much when associated with data security breaches -- especially when it is personal information that can be detrimental to your customers.  Data breaches can be quite costly to the business in terms of money spent to fix breaches and to your reputation. The Oracle Database Appliance is engineered with security built-in.  For this blog, let’s focus on CIS.  CIS® (Center for Internet Security, Inc.) is a non-profit entity that harnesses the power of a global IT community to safeguard private and public organizations against cyber threats. Their Controls and Benchmarks are a global standard and are recognized for best practices in securing IT systems and data against the most pervasive attacks. Starting with Database Appliance 12.2.1.3 release, the ODA CIS script is shipped as part of the software stack.  It can be found in the  /opt/oracle/oak/bin directory.  The ODA CIS script is written specifically for ODA and helps you meet your CIS compliance goals. To run the ODA CIS script, cd to the directory /opt/oracle/oak/bin and type: ./cis.py –h  This will display the options to view and correct CIS based standards. Each time you run the cis.py script, a report is created to show any CIS violations.  The CIS report output can be found in the /opt/oracle/oak/log/<ODA system name>/cis directory. For more information: CIS : https://www.cisecurity.org Oracle Database Security: http://www.oracle.com/technetwork/database/security/index.html ODA PM Webcast: Faster adoption of regulations and compliance with Oracle Database Appliance Built-In Security https://event.on24.com/wcc/r/1636506/53D8CE58784D79BBD28EA16D93CF8E31

It is good to get your name in the news, right?  Well, the good news anyway, but not so much when associated with data security breaches -- especially when it is personal information that can be...

Product News

ODA 12.2.1.3 - New feature Web Console to Backup to the Cloud!

Oracle Database Appliance has released version 12.2.1.3.   One of the new features is the Web Console UI to backup to the Oracle Cloud.  If you are looking to dip your toe into the Oracle Cloud, the ODA integrated backup simplifies and automates your database backup to Oracle OCI.  All you need is an OCI account and an Object Store for the database and archive log backups.  Log into your ODA’s Web Console and provide your Object Store Credentials and create the backup policy. After the backup policy is created, attach it to your database and the backup schedule is automatically generated.  Once your backup is in the Oracle Cloud, then you can use it to create a test/dev database, clone the database to another ODA on premise, and of course you can use it to recover your database! What's are some of the other new features? Enforce strong password rules for the Database Administrator Password for new databases and the System Password for all operating system users (root, grid, and oracle). Provide a new password upon first log in for the Web Console Ability to break the bond of the public network interface to support two separate physical network interfaces in your data center Patching pre-checks for the ODACLI stack including checks for server update, Oracle Grid Infrastructure, and Oracle Database NEW CIS script and updated STIG scripts are now shipped on the Database Appliance and can be found in /opt/oracle/oak/bin directory Database Updates: Oracle Database 12.2.0.1.180116 Release Update (RU) Oracle Database 12.1.0.2.180116 Bundle Patch (BP) Oracle Database 11.2.0.4.180116 Patch Set Update (PSU) Please refer to the Oracle Database Appliance Release Notes Documentation for a complete listing of What’s New and patch numbers. For more information on Oracle Database Appliance software stacks, please take a look at this blog: The Two Software Stacks of Oracle Database Appliance

Oracle Database Appliance has released version 12.2.1.3.   One of the new features is the Web Console UI to backup to the Oracle Cloud.  If you are looking to dip your toe into the Oracle Cloud, the...

Product News

Oracle Database 18c (18.2) Now Available on Oracle Database Appliance

I am happy to announce the availability of Oracle Database 18c on Oracle Database Appliance.   This Database Appliance release marks a new and exciting time, giving you the opportunity to start testing and using the new Oracle Database 18c functionality and improvements with your applications. For Oracle Database Appliance customers, the Hybrid Columnar Compression (HCC) functionality will be made available starting with the Database 18c release.  The HCC feature will provide the ability to recognize storage savings achieved from compression.  For more information on HCC, please take a look at the Oracle Documentation. For more information on Oracle Database 18c features, Read the announcement blog. Read the white paper: Introducing Oracle Database 18c. Read the documentation. How can you download and use the Oracle Database 18c release on ODA? The Oracle Database Appliance 18.2 release is a special parallel release that you can use to try Oracle Database 18.2. ODA 18.2 is not part of the ODA patch cycle.  If you are looking to run database versions of 12.1.0.2 or 12.1.0.1 or 11.2.0.4, then this release is not for you.  Please refer to this ODA Blog Post on the ODA software stack on planned patch updates.   https://blogs.oracle.com/oda/the-two-software-stacks-of-oracle-database-appliance Oracle Database Appliance 18.2 supports Oracle Database Appliance models X7-2-HA (bare metal), X7-2S/M, X6-2-HA (bare metal), X6-2S/X6-2M/X6-2L and X5-2. You must re-image your ODA and deploy the ODA 18.2 patches to access the Oracle Database Appliance 18c software. The 18.2 release only supports provisioning 18.2 databases.  For more information, please take a look the Oracle Database Appliance 18.2 documentation at Oracle Database Appliance 18.2  The 18.2 release is available in MOS to download.  

I am happy to announce the availability of Oracle Database 18c on Oracle Database Appliance.   This Database Appliance release marks a new and exciting time, giving you the opportunity to start...

Product News

The Two Software Stacks of Oracle Database Appliance

We designed Oracle Database Appliance to provide simplicity, reliability, and the affordability to deploy a 2-Node RAC cluster in a matter of minutes.  In October 2011, Database Appliance accomplished this with Appliance Manager.  Appliance Manager is the software that contains the intelligence of the Database Appliance to automate deployment and management of the entire stack from hardware through the infrastructure.  The first version of Appliance Manager is referred to as OAKCLI, which stands for Oracle Appliance Kit CLI.  Appliance Manager grew over the past few years to automate database provisioning, patching, virtualization management, and monitoring. The next generation of Appliance Manger was released with the ODA X6 model family, called ODACLI.  Since there were some opportunities to make some changes, we thought it was the perfect time to change it to Oracle Database Appliance CLI. Beginning with ODA X6-2, we started creating hardware-specific books. Each book has a chapter for its command line interface.  To access the latest Database Appliance documentation, please go to:  http://www.oracle.com/goto/oda/docs Over the next few months, we will continue to enhance ODACLI and all of the Database Appliance Hardware stacks will use ODACLI. Below is a table to help you to identify the hardware and software models along with the plan to merge the stacks.   Release / Stack 12.2.1.2 Released Jan 2018 12.2.1.3 12.2.1.4 18.3.1.0 odacli bare metal and KVM support ODA X7-2S, X7-2M, X7-2-HA ODA X6-2S, X6-2M, X6-2L ODA X7-2S, X7-2M, X7-2-HA ODA X6-2S, X6-2M, X6-2L ODA X7-2S, X7-2M, X7-2-HA ODA X6-2S, X6-2M, X6-2L ODA X7-2S, X7-2M, X7-2-HA ODA X6-2S, X6-2M, X6-2L ODA X5-2, X4-2, X3-2 oakcli bare metal ODA X6-2-HA ODA X5-2, X4-2, X3-2, V1 ODA X6-2-HA ODA X5-2, X4-2, X3-2, V1 ODA X6-2-HA ODA X5-2, X4-2, X3-2 Migrate to ODACLI oakcli virtualization ODA X7-2-HA ODA X6-2-HA ODA X5-2, X4-2, X3-2, V1 ODA X7-2-HA ODA X6-2-HA ODA X5-2, X4-2, X3-2, V1 ODA X7-2-HA ODA X6-2-HA ODA X5-2, X4-2, X3-2 ODA X7-2-HA ODA X6-2-HA ODA X5-2, X4-2, X3-2   Stay tuned for more information on the software merge of the Database Appliance stacks.

We designed Oracle Database Appliance to provide simplicity, reliability, and the affordability to deploy a 2-Node RAC cluster in a matter of minutes.  In October 2011, Database Appliance accomplished...

KVM

KVM Import an OVA Template

Article Table of Contents ​KVM on ODA Overview Enabling KVM on ODA Creating Guest VM storage for KVM KVM Networking on ODA Deploy a KVM guest on ODA Importing an OVA Template into KVM on ODA KVM Troubleshooting An OVA (open virtual appliance/archive) is a tar archive, containing an .ovf and .vmdk files, respectively the VM configuration and disks. A direct OVA template import into KVM is not supported, the steps to convert are the following (below example will show how to use 'OVM_OL7U2_x86_64_PVHVM.ova'): The Manual Steps 1. extract the files from the OVA template:  tar xvf OVM_OL7U2_x86_64_PVHVM.ova 2. convert the vdisk "System.vmdk" to qcow2 (qcow2 supports snapshots).   qemu-img convert -O qcow2 System.vmdk /<kvm_Guest_repo>/OL7U2.qcow2 3. Create a new Guest VM with virt-manager using the qcow2 disk above import existing disk image browse to the qcow2 disk above choose required memory and CPUs Customize and setup the network base on your requirement Note: you must change Disk Bus to "IDE" You can now start the imported guest VM The "OVA4KVM" tool Scope of ov4kvm tool is permit the Guest VM OVA format template import into KVM within "1-click" without any manual conversion. Check it out from My Oracle Support: KVM: Import an OVA Guest VM format template into KVM (2284806.1)  

Article Table of Contents ​KVM on ODA Overview Enabling KVM on ODA Creating Guest VM storage for KVM KVM Networking on ODA Deploy a KVM guest on ODA Importing an OVA Template into KVM on ODA KVM...

KVM

KVM Deploying Guest VMs with ISO

Article Table of Contents ​KVM on ODA Overview Enabling KVM on ODA Creating Guest VM storage for KVM KVM Networking on ODA Deploy a KVM guest on ODA Importing an OVA Template into KVM on ODA KVM Troubleshooting There are at least three methods of creating a guest on ODA KVM machine: the virt-install tool, the virt-manager tool, and the virsh tool (in conjunction with XML files). Deploy a KVM guest using virt-install (command line) You can create a KVM guest with the virt-install command-line tool. This topic provides information about creating KVM guests, and specific example for Oracle Linux 7. Example: Deploy a KVM Guest VM with Oracle Linux 7 The following command code example creates a KVM guest running Oracle Linux 7. Assumptions : You have a running storage pool repository (/kvm_repos/kvm_repo1/) MACVTap network bridge over public NIC btbond1 will be used The OL6 ISO is available on ODA The basic Command: virt-install --name=OL-1 \                --ram=16384 \                --vcpus=4 \                --os-type=linux \                --os-variant=rhel7 \                --accelerate \                --disk /kvm_repos/kvm_repo1/OL-1_boot.img,device=disk,size=40,sparse=yes,cache=none,format=qcow2,bus=virtio \                --network type=direct,source=btbond1,model=virtio \                --vnc \                --noautoconsole \                --cdrom=/iso/OracleLinux-R7-U3-Server-x86_64-dvd.iso Parameters Details --name Name of the guest instance --ram Memory to allocate for guest instance in megabytes --vcpus Number of vcpus to configure for your guest --os-type The OS type being installed --os-variant The OS variant being installed guests --accelerate KVM kernel acceleration capabilities are used --disk you define the path, then comma delimited options, device is the type of storage, bus is the interface ide, scsi, usb, virtio – virtio is the fastest --network The network configuration, in this case we are connecting to a MACVTap bridge over "btbond1", and using the virtio drivers which perform much better --vnc configures the graphics card to use VNC allowing you to use virt-viewer or virt-manager to see the desktop as if you were at the a monitor of a physical machine --noautoconsole configures the installer to NOT automatically try to open virt-viewer (if installed) to view the console to complete the installation – this is helpful if you are working on a remote system through SSH without graphical environment --cdrom this option specifies the iso image with which to boot off Note: instead to use '--cdrom', the OS installation source can be on http, nfs, ftp using     --location=(eg, nfs:host:/path, http://host/path, ftp://host/path)   Deploy a KVM guest using virt-manager (GUI) virt-manager, also known as Virtual Machine Manager, is a graphical tool for creating and managing guest virtual machines. 1. Lunch virt-manager 2. Create a new virtual machine Click the Create a new virtual machine button to open the new vm wizard 3. Specify the installation type "Local install media (ISO image or CDROM)" 4. Locate the ISO image, Configure OS Type and Version 5. Configure CPU and memory 6. Configure the virtual storage Note: "Manage" will give you the possibility to create a volume under a KVM "pool" (It should be an ACFS volume created previously) 7. Final Configuration Verify the settings of the virtual machine and click "Begin Installation" 

Article Table of Contents ​KVM on ODA Overview Enabling KVM on ODA Creating Guest VM storage for KVM KVM Networking on ODA Deploy a KVM guest on ODA Importing an OVA Template into KVM on ODA KVM...

KVM

KVM Networking on ODA (Oracle Database Appliance)

Article Table of Contents ​KVM on ODA Overview Enabling KVM on ODA Creating Guest VM storage for KVM KVM Networking on ODA Deploy a KVM guest on ODA Importing an OVA Template into KVM on ODA KVM Troubleshooting KVM Networking A virtual machine typically needs to be connected to a network to be useful. Because a virtual machine runs as an application inside the host computer, connecting it to the outside world needs support from the host operating system. There are a number of options for networking a virtual machine, both on the Link Layer and the Network layer. This page provides an introduction to the common networking configurations used by KVM. Two common setups are "virtual network" or "shared physical device". NAT forwarding (aka "virtual networks") Standard deployment of on ODA provides NAT based connectivity to virtual machines out of the box. This is the  'default virtual network'. You verify that NAT is available by issuing the following command:   # virsh net-list --all Name                 State      Autostart     Persistent -------------------------------------------------- default              active     yes           yes With the libvirt default network active, this will provide an isolated bridge device (virbr0):   # brctl show bridge name    bridge id        STP enabled    interfaces virbr0        8000.525400cd635d    yes        virbr0-nic The default virtual network configuration can be displayed issuing the following command: # virsh net-info default Name            default UUID            ed67f5c0-65f8-45b8-9bd3-f613b1789e48 Active:         yes Persistent:     yes Autostart:      yes Bridge:         virbr0 and # virsh net-dumpxml default <network>   <name>default</name>   <uuid>ed67f5c0-65f8-45b8-9bd3-f613b1789e48</uuid>   <forward mode='nat'/>   <bridge name='virbr0' stp='on' delay='0' />   <mac address='52:54:00:CD:63:5D'/>   <ip address='192.168.122.1' netmask='255.255.255.0'>     <dhcp>       <range start='192.168.122.2' end='192.168.122.254' />     </dhcp>   </ip> </network>   Create a new NAT network (using the command line) To define a new NAT bridge, complete the following steps. 1. Create a new libvirt network configuration like the following: # cat ~/new-kvm-net.xml <network>     <name>nat_01</name>     <forward mode='nat'>         <nat>             <port start='1024' end='65535'/>         </nat>     </forward>     <bridge name='virbr%d' stp='on' delay='0'/>     <ip address='192.168.150.1' netmask='255.255.255.0'>         <dhcp>             <range start='192.168.150.2' end='192.168.150.254'/>         </dhcp>     </ip> </network> Note: bridge name='virbr%d' will use the first bridge name available (vribr1, virbbr2, ...) 2. Add the new network definition XML file to libvirt: # virsh net-define ~/new-kvm-net.xml 3. To set the new network to automatically startup each time ODA host is rebooted, do this: # virsh net-autostart <net name from xml> 4. Start the new network # virsh net-start <net name from xml>   Create a new NAT network (using the virt-manager GUI) It's possible create a new libvirt network configuration using "virt-manager" 1. Click on QEMU/KVM "Details", Virtual Network 2. Add a new entry '+' set your preferences: Note: You can not edit the above configuration using thr GUI, you need to recreate the virtual network. Applying modifications to the network The most common scenario for this is adding new static MAC+IP mappings for the network's DHCP server. If you edit the network with "virsh net-edit", any changes you make won't take effect until the network is re-started, which unfortunately will cause a all guests to lose network connectivity with the host until their network interfaces are explicitly re-attached. It's possible to edit the network definition above and apply the changes on the fly using  "virsh net-update" instead. virsh net-update Several changes to the network configuration can be done with "virsh net-update" command, which can be used to enact the changes immediately. In the following example, we want to add a new DHCP static rule to the "default" network mapping MAC address "52:54:00:b2:19:fb" to IP address 192.168.122.50 and hostname "ol68": # virsh net-update default add ip-dhcp-host \       "<host mac='52:54:00:b2:19:fb' \        name='ol68' ip='192.168.122.50' />" \        --live --config After the above command the new "default" network configuration will be as following: # virsh net-dumpxml default <network>   <name>default</name>   <uuid>ed67f5c0-65f8-45b8-9bd3-f613b1789e48</uuid>   <forward mode='nat'/>   <bridge name='virbr0' stp='on' delay='0' />   <mac address='52:54:00:CD:63:5D'/>   <ip address='192.168.122.1' netmask='255.255.255.0'>     <dhcp>       <range start='192.168.122.2' end='192.168.122.254' />       <host mac='52:54:00:b2:19:fb' name='ol68' ip='192.168.122.50' />     </dhcp>   </ip> </network> The config entries in a network that can be changed with virsh net-update are: ip-dhcp-host ip-dhcp-range (add/delete only, no modify) forward-interface (add/delete only) portgroup dns-host dns-txt dns-sr Guest Configuration A guest can be connected to the virtual network based on the network name. Example to connect a guest to the "default" virtual network, you need to edit the configuration file for such guest: # virsh edit <guest VM name> Add the following XML to the configuration file: <interface type='network'> <source network='default'/> <mac address='52:54:00:b2:19:fb'/> </interface> Note: the MAC address is optional and will be automatically generated if omitted.   Host Configuration Libvirt will add iptables rules to allow traffic to/from guests attached to the virbr0 device, but by default, on Oracle Database Appliance "net.ipv4.ip_forward" is set to "0". With such setting the guests that are connected via a virtual network with <forward mode='nat'/> can make outgoing network connection only to the ODA host (in this example "192.168.122.1") and from/to other guests connected to the same libvirt network. If you need your guest able to go outside you need to change "net.ipv4.ip_forward" to "1" in the "/etc/sysctl.conf" file. To enable the changes you will need to run the command: # sysctl -p /etc/sysctl.conf   Bridged networking (aka "shared physical device") The NAT based connectivity is useful for quick & easy deployments, or on machines with dynamic/sporadic networking connectivity. More advanced users will want to use full bridging (also known as physical device sharing), where the guest is connected directly to the LAN. Command line steps 1. Create a Bridge Execute the following command: # brctl addbr pubbr0 2. Edit "/etc/sysconfig/network-scripts/ifcfg-pubbr0" adding the ODA host public IP (based on the public ODA interface you want to use btbond1, btbond2, sfpbond1), in example: # cat ifcfg-pubbr0 DEVICE=pubbr0 TYPE=Bridge BOOTPROTO=static ONBOOT=yes IPADDR=10.214.105.34 NETMASK=255.255.248.0 GATEWAY=10.214.104.1 DELAY=0 3. Edit /etc/sysconfig/network-scripts/ifcfg-btbond1 removing the public IP (added to the pubbr0 conf file) and setting the bridge to "pubbr0", in example: # cat ifcfg-btbond1 DEVICE=btbond1 ONBOOT=yes BOOTPROTO=none USERCTL=no BONDING_OPTS="mode=active-backup miimon=100 primary=em1" TYPE=BOND BRIDGE=pubbr0 IPV6INIT=no 4. Edit /etc/sysconfig/network, changing the "GATEWAYDEV" to your bridge # cat /etc/sysconfig/network NETWORKING=yes NETWORKING_IPV6=no HOSTNAME=rwsodal001 NOZEROCONF=yes GATEWAYDEV=pubbr0 GATEWAY=10.214.104.1 5. Restart the network service network restart 6. Attach the new NIC device to the guest virsh attach-interface --domain <guest name> --type bridge --source pubbr0 --model virtio --config --live   GUI steps The same setup can be done using the virt-manager GUI 1. Click on QEMU/KVM "Details", Virtual Network 2. Add a new bridge '+'   Manually edit /etc/sysconfig/network, changing the "GATEWAYDEV" to your bridge Virtualized bridged networking with MacVTap Another alternative to using a bridge to enable a KVM guest to communicate externally is to use the Linux MacVTap driver. Macvtap is essentially a combination of the MacVLAN driver and a Tap device. Each virtual NIC has its own MAC address different from the physical interface's MAC address. Frames from or to the virtual interface are mapped to the physical interface called lower interface. MacVLAN allows you to have multiple Ethernet MAC addresses on one NIC. If you enable bridge mode, all virtual NICs attached to the same host can see each other. Note: The guests can talk to each other. But the host cannot talk with the guests. A MacVTap interface to be used within KVM can be created as following making a resource xml file (macvtap0-def.xml): <network>   <name>macvtap0</name>   <forward mode="bridge">     <interface dev="btbond1"/>   </forward> </network> Then you can set it up issuing: virsh net-define macvtap0-def.xml virsh net-autostart macvtap0 virsh net-start macvtap0 Attach the new NIC device to the guest virsh attach-interface --domain <guest name> --type network --source macvtap0 --model virtio --config --live The same cna be achievable using the virt-manager GUI on defining the network for the Guest VM:

Article Table of Contents ​KVM on ODA Overview Enabling KVM on ODA Creating Guest VM storage for KVM KVM Networking on ODA Deploy a KVM guest on ODA Importing an OVA Template into KVM on ODA KVM...

KVM

KVM Guest VM storage devices on ODA

Article Table of Contents ​KVM on ODA Overview Enabling KVM on ODA Creating Guest VM storage for KVM KVM Networking on ODA Deploy a KVM guest on ODA Importing an OVA Template into KVM on ODA KVM Troubleshooting Storage Pool -- The Overview A storage pool is a file, directory, or storage device managed by libvirt  for the purpose of providing storage to guest virtual machines. Although the storage pool is a virtual container it is limited by two factors: maximum size allowed by qemu-kvm and the size of the disk on the host physical machine. libvirt uses a directory-based storage pool, the /var/lib/libvirt/images/ directory, as the default storage pool. This default storage pool can be changed.  In the case of ODA, the following is recommended. For example, here are 4 different storage pools (aka Guest VM repositories) using the virsh pool-list command. # virsh pool-list Name                 State      Autostart ----------------------------------------- kvm_repo1            active     yes       kvm_repo2            active     yes       kvm_repo3            active     yes       kvm_repo4            active     yes     We can obtain storage pool information details by using the virsh pool-info <storage-pool> command. # virsh pool-info kvm_repo1 Name:           kvm_repo1 UUID:           d2e44017-7137-efa2-1da9-db63cdd754fa State:          running Persistent:     yes Autostart:      yes Capacity:       200.00 GiB Allocation:     5.08 GiB Available:      194.92 GiB Volumes Storage pools are divided into storage volumes. Storage volumes are an abstraction of physical partitions, LVM logical volumes, file-based disk images and other storage types handled by libvirt. Storage volumes are presented to guest virtual machines as local storage devices regardless of the underlying hardware. For example, here are the details of the storage pool "kvm_repo1" content. In this case 3 storage volumes are belong the same guest virtual machine (OL-6U8) as local storage devices # virsh vol-list --pool kvm_repo1 Name                            Path                                    ------------------------------- ---------     OL-6U8.qcow2           /kvm_repos/kvm_repo1/OL-6U8.qcow2 OL-6U8_storage0.qcow2  /kvm_repos/kvm_repo1/OL-6U8_storage0.qcow2 OL-6U8_storage1.qcow2  /kvm_repos/kvm_repo1/OL-6U8_storage1.qcow2 We can view the storage volume information details issuing: # virsh vol-info --pool kvm_repo1 OL-DB_6U8.qcow2 Name:           OL-DB_6U8.qcow2 Type:           file Capacity:       512.00 GiB Allocation:     7.10 GiB How to Create a KVM Storage Pool on ODA - Detailed Steps On ODA we will create KVM storage pools using the shared storage on the ODA X6-2S/X6-2M/X6-2L.  By default the shared storage disk group DATA is designed to store Databases. To use this shared storage with KVM, we will define new ACFS (Oracle Automatic Storage Management Cluster File System) file system to store guest VM volumes (disk image files). The Steps 1. Create your ACFS volume (as grid user) asmca -silent -createVolume -volumeName <ASM volume name> -volumeDiskGroup <ASM disk group name for the volume> -volumeSizeGB <ASM volume size in GB> -sysAsmPassword <sys asm password> example: [grid@odaL ~]$ asmca -silent -createVolume -volumeName kvm_repo5 -volumeDiskGroup DATA -volumeSizeGB 100 -sysAsmPassword welcome1 Volumes fetched successfully. Check /u01/app/grid/cfgtoollogs/asmca/asmca-170526AM012426.log for details. 2. Verify your volume creation (as grid user) asmcmd volinfo -G <diskgroup> <ASM volume name> | grep -oE '/dev/asm/.*' example: [grid@odaL ~]$ asmcmd volinfo -G DATA kvm_repo5 | grep -oE '/dev/asm/.*' /dev/asm/kvm_repo5-208 3. Create the ACFS filesystem (as grid user) asmca -silent -createACFS -acfsVolumeDevice <volume_device> -acfsMountPoint <mount point> example (note as the acfsVolumeDevice is the output of previous command '/dev/asm/kvm_repo5-208') : [grid@odaL ~]$ asmca -silent -createACFS -acfsVolumeDevice /dev/asm/kvm_repo5-208 -acfsMountPoint /kvm_repos/kvm_repo5 ASM Cluster File System created on /dev/asm/kvm_repo5-208 successfully. Run the generated ACFS registration script /u01/app/grid/cfgtoollogs/asmca/scripts/acfs_script.sh as privileged user to register the ACFS with Grid Infrastructure and to mount the ACFS. The ACFS registration script needs to be run only on this node: odaL. 4. Run the generated ACFS registration script as privileged user /u01/app/grid/cfgtoollogs/asmca/scripts/acfs_script.sh example: [root@odaL ~]# /u01/app/grid/cfgtoollogs/asmca/scripts/acfs_script.sh ACFS file system /kvm_repos/kvm_repo5 is mounted on node odaL 5. Create the KVM pool (as root user) virsh pool-define-as <poolname> --type dir --target <path> example: [root@odaL ~]# virsh pool-define-as kvm_repo5 --type dir --target /kvm_repos/kvm_repo5 Pool kvm_repo5 defined 6. Start the pool (as root user) virsh pool-start <poolname> example: [root@odaL ~] # virsh pool-start kvm_repo5 Pool kvm_repo5 started 7. Setup the autostart (as root user) virsh pool-autostart <poolname> example: [root@odaL ~]# virsh pool-autostart kvm_repo5 Pool kvm_repo5 marked as autostarted

Article Table of Contents ​KVM on ODA Overview Enabling KVM on ODA Creating Guest VM storage for KVM KVM Networking on ODA Deploy a KVM guest on ODA Importing an OVA Template into KVM on ODA KVM...

KVM

KVM on ODA X7-2S/X7-2M/X7-2HA, X6-2S/X6-2M/X6-2L

Q: Does Oracle Linux include support for KVM? A: Yes it does! KVM is a feature of Oracle Linux today. Please refer to My Oracle Support Doc ID 417770.1.  And more importantly, Oracle Linux Premier Support is included with Oracle Premier Support for Systems and Engineering Systems, such as ODA hardware support. Oracle Database Appliance models X7-2S/X7-2M/X7-2HA, X6-2S/X6-2M/X6-2L are including the KVM libraries in the software stack that is deployed on ODA starting with release 12.1.2.11. Available today on My Oracle Support. In this initial role out of KVM on ODA, you will easily be able to startup the KVM service to create guest VMs to deploy applications. By deploying applications in a guest VM, you can run both databases and applications with isolation capabilities; essentially creating a Solution-in-a-Box with ODA platform.  With the ODA 12.1.2.11 release, there are just a few limitations. Guest VM OS can only be Linux.  Other OS support will be provided in later releases. Guest VMs do not support Oracle databases to be deployed in them.  We are in the process of certifying databases in a KVM guest VM. KVM on Oracle Linux does not support hard partitioning.  This means that all enabled cores/sockets on the ODA will be licensed for databases and applications running on the ODA using the appropriate licensing metric for the database edition and application.  Capacity on demand for the ODA still remains in effect. For more information on capacity on demand, please review the ODA Licensing documentation here:  http://docs.oracle.com/cd/E86648_01/doc.121/e85590/toc.htm With the support of KVM, this will add virtualization functionality to the ODA X7-2S/X7-2M/X7-2HA, X6-2S/X6-2M/X6-2L models.  This provides the ability to patch the ODA and the application separately without impact to either stack.  But most importantly, this provides the ability to deploy both the database and application on the same system to create a Solution-in-a-Box. For other Solution-in-a-Box white papers, please take a look at the ODA OTN Learn More tab here: http://www.oracle.com/technetwork/database/database-appliance/learnmore/index.html The ODA team looks forward to creating new white papers to deploy Oracle applications in KVM and working with ISVs and customers to implement your solution on ODA. Please take a look at the following entries on how to setup KVM on ODA. Article Table of Contents KVM on ODA Overview Enabling KVM on ODA Creating Guest VM storage for KVM KVM Networking on ODA Deploy a KVM guest on ODA Importing an OVA Template into KVM on ODA KVM Troubleshooting  

Q: Does Oracle Linux include support for KVM? A: Yes it does! KVM is a feature of Oracle Linux today. Please refer to My Oracle Support Doc ID 417770.1.  And more importantly, Oracle Linux Premier...

Product News

Deploying Enterprise Manager 13c on ODA

Looking for a simple to use, fast to deploy, engineered platform to deploy your Enterprise Manager infrastructure?  Oracle Database Appliance is for you!   Oracle Database Appliance X6 models offer a high availablity platform called ODA X6-2-HA to deploy the OVM stack and rapidly deploy an Enterprise Manager template to start managing your enterprise in hours. For the latest white paper on the deployments, please take a look here. Solution-in-A-Box: Deploying Highly Available Monitoring Infrastructure using Oracle Enterprise Manager Cloud Control 13cR2 and Oracle Database Appliance Since you are deploying a virtualized stack, you could utilize the ODA X6-2-HA resources to deploy other databases such as the RMAN repository database or other application VMs that are used to manage your business landscape. Oracle Database Appliance X6 models also offer three single node platforms called ODA X6-2S, ODA X6-2M, and ODA X6-2L. These platforms are bare metal and provide high-performance database characteristics. For more information on how to deploy Enterprise Manager on the single node platforms, please take a look here: Solution-in-A-Box: Deploying Oracle Enterprise Manager Cloud Control 13c on Oracle Database Appliance X6-2S / X6-2M If this is the first time you are deploying the Oracle Database Appliance, take a look at this video on how easy it is to deploy the ODA X6-2M.  

Looking for a simple to use, fast to deploy, engineered platform to deploy your Enterprise Manager infrastructure?  Oracle Database Appliance is for you!   Oracle Database Appliance X6 models offer a...

Events

Oracle Database Appliance X6-2S / X6-2M Support Oracle Database Standard Edition and Oracle Database Standard Edition One

Thenext Oracle Database Appliance software update (12.1.2.8) will add support forOracle Database 11g Standard Edition and Standard Edition One (release11.2.0.4) running on Oracle Database Appliance X6-2S /X6-2M.  You will beable to deploy and run Oracle Database Standard Edition (release 11.2.0.4) onODA X6-2S/X6-2M and utilize Oracle Database Standard Edition, Oracle DatabaseStandard Edition One, or Oracle Database Standard Edition 2 licenses. Refer to the table below for specific details. Database Version Platform License Required Standard Edition/Standard Edition One (11.2.0.4) ODA X6-2S 1 x DB SE, or 1 x DB SE1, or 1 x DB SE2 Standard Edition/Standard Edition One (11.2.0.4) ODA X6-2M 2 x DB SE, or 2 x DB SE1, or 2 x DB SE2 Enterprise Edition (11.2.0.4 or 12.1.0.2) ODA X6-2S, or ODA X6-2M, or ODA X5-2-HA  (number of cores enabled/2) x DB EE (plus options) Standard Edition 2 (12.1.0.2) ODA X6-2S 1 x DB SE2 Standard Edition 2 (12.1.0.2) ODA X6-2M 2 x DB SE2 FrequentlyAsked Questions: Q: If I have an SE or SE1 license, can I runOracle Database 12c Standard Edition?  You mustmigrate your license to SE2, and then you can run Oracle Database 12cStandard Edition 2. Q:Can I run Oracle Database 11g Standard Edition on an ODA X6-2 S/X6-2M using anSE One license?  Yes.   SE isvalid on servers with up to a four sockets, and SE1 is valid servers with up totwo sockets.  ODA X6-2S/X6-2M thus meets the criteria for either SE or SE1licenses. Q:Can I purchase a new license to run Oracle Database 11g Standard Edition? Yes, but you must purchase an Oracle Database Standard Edition 2 license, whichwill entitle you to run Oracle Database 11g Standard Edition as well as OracleDatabase 12g Standard Edition 2. Q:Can I run Oracle Database Standard Edition on ODA X5-2?  No,only ODA X6-2S/X6-2M are eligible to run Standard Edition. Q:When will 11g Standard Edition be supported on ODA? Effectivewith the 12.1.2.8 update, currently targeted for release on August 29. Q:Can I use Capacity on Demand licensing with Standard Edition (SE/SE1/SE2)? No,you cannot disable an entire socket in any X86 server.  Q:Can I run Oracle Standard Edition Real Application Clusters (SE RAC) on ODA?No, SE RAC requires an HA configuration like the ODA X5-2, and that platformis not eligible to run Standard Edition.

The next Oracle Database Appliance software update (12.1.2.8) will add support for Oracle Database 11g Standard Edition and Standard Edition One (release11.2.0.4) running on Oracle Database Appliance...

Product News

Why ODA is a perfect solution for Disaster Recovery

While disasters do occur every now and then, many production deployments lack a disaster recovery (DR) system. Oracle Database Appliance makes a great solution for deploying a disaster recovery system (especially for production ODA deployments) for the following reasons. 1. Easy to setup (setup entire DR site in a matter of hours)2. Matches production platform exactly for your ODA production environment3. Low total cost of solution4. Large additional CPU, Memory, and Storage capacity available for additional use5. Leverage low CPU initial configuration on DR side and scale dynamically only when needed6. Consistent performance between production and standby environments7. Easy to maintain DR solution (sort of one-button maintenance)8. Achieve higher availability during both planned and unplanned downtimes9. Use DR environment for additional purposes (use extra capacity for deploying DBs and VMs)10. Test and validate patches using standby first patching11. Distribute workload and CPU allocation between production and DR using Active Data Guard12. Keep DR environment up-to-date at the touch of a button (easy to synchronize production and DR environments)13. Use ODA as DR solution for both ODA and non-ODA production environments14. Easy to migrate from your non-ODA infrastructure to ODA infrastructureRefer to Oracle White Paper Deploying Oracle Data Guard with Oracle Database Appliance (http://www.oracle.com/technetwork/database/database-appliance/documentation/deploying-odg-with-oda-1615029.pdf). 

While disasters do occur every now and then, many production deployments lack a disaster recovery (DR) system. Oracle Database Appliance makes a great solution for deploying a disaster recovery system...

Product News

Using the new ‘-local’ parameter to roll the 12.1.2.6 Patch

As part of the ApplianceManager 12.1.2.6, a new parameter has been introduced to control the rolling ofODA patching from one node to another. This is the first release to provide this functionality to allow you tocontrol when the second node is patched. After you have uploaded the patch (Patch 22328442) to both nodes of your ODA, unpackedit, and passed the pre-check script, you are ready to patch your ODA. Please remember that it is expected for INFRA and GI to be patchedtogether. Oracle database homes areflexible when they can be patched.  Determine which node you want to patch first.  DO NOT patch both nodes at the same time. Database Services  As a best practice, you want to stop database services for RAC so that new connections will connect to the node that is not being actively patched, or relocate RAC ONE database to the other node. First, view the databases running on ODA oakcli show databases -detail Name Type Storage HomeName HomeLocation Version HostName ----- ------ -------- -------------- ----------------- ----------- -------------- mydb RAC ACFS OraDb12102_home2 /u01/app/oracle/product/12.1.0.2/dbhome_2 12.1.0.2.5(21359755,21359758)       myoda1,myoda2                           fred RACOneNode ACFS OraDb12102_home3 /u01/app/oracle/product/12.1.0.2/dbhome_3 12.1.0.2.5(21359755,21359758)       myoda1 I am going to patch myoda1, therefore I want to stop mydb service for myoda1 and relocate fred to myoda2 Connecting as the 'oracle' user, srvctl status service -db mydb Service acservice is running on instance(s) mydb1,mydb2  srvctl status service -db fred Service fred_racone is running on instance(s) fred_1  Now I am going to stop the RAC service srvctl stop instance -i mydb1 -db mydb -force srvctl status service -db mydb Service acservice is running on instance(s) mydb2 Relocate the RAC One instance to the other node  srvctl relocate database -d fred -n myoda2 You are now ready to patch myoda1 node  oakcli update –patch 12.1.2.6.0 –infra –local --local will execute the INFRA patch on only that node. Once the patching has completed, a re-boot of the node will occur andnode 0 is running OL6.7 and node 1 is running OL5.11 At this point you can then patch the GI on the same node. oakcli update –patch 12.1.2.6.0 –gi –local After GI has been patched, you have a choice to patch the databases ornot. Now, patch the second node: oakcli update –patch 12.1.2.6.0 –infra –local oakcli update –patch 12.1.2.6.0 –gi –local And now, optionally, the database can be patched. We do not encourage you to run the nodes with mixed versions for more than 24 hours. At this point you can relocate your RAC One database back over to the other node and start the RAC service backup to patch the other node. Please refer to chapter 1 of Oracle® Database Appliance Administration and Reference Guide Release 12.1.2.6.0 for more detailed examples of updating your ODA.

As part of the Appliance Manager 12.1.2.6, a new parameter has been introduced to control the rolling of ODA patching from one node to another. This is the first release to provide this functionality...

Events

Prepare for the Oracle Database Appliance 12.1.2.6 Patch

The next ODA Patch 12.1.2.6is going to provide in-place upgrade of the operating system from OL5.11 toOL6.7.  As many of you may know, it wasnot an easy upgrade to OL6 as it required your systems to be re-imaged. Our ODA team did not feel this was a goodthing to require a re-image of your ODA, so we have engineered the upgrade tobe in-place and rolling. However, before you jumpinto the air and yell hurrah, this patch requires the ODA to first have the12.1.2.5 patch applied successfully. Sofor those of you that have not upgraded your ODA’s in a while or are on aversion less than 12.1.2.2.0, please review the README (https://updates.oracle.com/Orion/Services/download?type=readme&aru=19485583)of the 12.1.2.5 patch set as you may need to apply an interim patch beforemoving to 12.1.2.5. The 12.1.2.6 patch does not apply updates to the ILOM, BIOS, Controller, Expander, or disk firmware.  So, before you patch your ODA to 12.1.2.6, run the  oakcli command with the 12.1.2.5 version/patch oakcli show version -detail All of the components, except the databases, should show Up-To-Date.  The installed versions vary from ODA HW versions...it is the UP-TO-DATE that you are looking for. Component Name   Installed Version Proposed Patch Version  Controller_INT 4.230.40-3739   Up-to-date   Controller_EXT 06.00.02.00 Up-to-date   Expander 0018   Up-to-date   SSD_SHARED A29A Up-to-date   HDD_LOCAL A729  Up-to-date   ILOM 3.2.4.52 r101649 Up-to-date   BIOS 30050100 Up-to-date  Up-to-date   IPMI 1.8.12.4 Up-to-date   HMP 2.3.4.0.1 Up-to-date   OAK 12.1.2.5.0 Up-to-date   After your ODA is patched up-to-date with 12.1.2.5, continue to prepare for the 12.1.2.6patch using the pre-check tool. It will verify if you have enough free spacein /u01, verify RPMs that have been added, and verify RPMs that are expected. This means that if you have3rd party agents running on ODA and had to install RPMs from OL5,you will have to re-install the OL6 RPMs to support those agents after theupgrade. For the pre-check tool, download the ZIP file from here.  Upload it to both of your ODA nodes to a directory, /tmp works just fine.  Unzip the file and run the command ./validateOl6PreChecks --pre You can checkthe currently installed RPMs using "rpm -qa" command or you may wantto use “rpm –qa –last” to see the latest RPMs that were updated since the lastupgrade. In addition, here are somebest practices for patching on ODA .  Check ALL disks / diskgroups and make sure that they are allonline and healthy.  For a  good disk level check for ASM, OS andmultipath:    oakcli stordiag [e#_]pd_##   · Make sure the ODA patch level matches on both nodes. Check CRS and connectivity before patching. Make sure CRS, ASM and OAK are running on both nodes. Check OS based storage. Clean up as needed including older installations if you have upgraded previously. -  10GB of free space min. on each node (/u01 and / ) Run an oracheck report Review 888888.1 for known issues o Fix or replace any disks before considering upgrading o If your ODA version is 2.10 or lower for your source makesure you check compatibility with the new disk - See ODA + HGST based notes) showversion -detail oakclivalidate -d on each node oakcliorachk

The next ODA Patch 12.1.2.6 is going to provide in-place upgrade of the operating system from OL5.11 to OL6.7.  As many of you may know, it wasnot an easy upgrade to OL6 as it required your systems to...

Events

A RACI Chart for Oracle Database Appliance

A responsibility assignment matrix, also known as RACI matrixdescribes the participation by various roles in completing tasks ordeliverables for a project or business process. It is especially useful in clarifyingroles and responsibilities in cross-functional/departmental projects andprocesses. RACI is an acronym derived from the four key responsibilities mosttypically used: Responsible, Accountable, Consulted, and Informed. Oracle Engineered Systems such as Oracle DatabaseAppliance and Oracle Exadata are integrated systems that greatly simplify andredefine how systems’ deployments have traditionally been planned, executed andmanaged. Different organizations use different approaches to assignresponsibilities in this new world of system management. Customers and project managers sometimes ask for or wantto build a RACI chart for Oracle Engineered Systems. Someone recently asked forone for Oracle Database Appliance. Each environment is different and assignmentof roles and responsibilities is often a contentious topic. On one extreme, asingle DBA or System Administrator can deploy and manage the entire system;while on the other traditional teams take their own well defined roles and responsibilities.A sample RACI chart for Oracle Database Appliance may look as follows. However,it is certainly up to you to define the roles and responsibilities as per yourrequirements in your environment. Build your own RACI chart for your environment and share your thoughts! Activity Project Sponsor System / Database Architect DB Admin System Admin Network Admin Storage Admin Appln Admin Apps Owner Data Center Ops Platform Product Selection I R C C C C C C C System Sizing and Requirement Analysis I C R C C C I I I Oracle Database Appliance Procurement I C I I I I I R I Oracle Database Appliance Sizing I R C C C C C C I Oracle Database Appliance Initial Deployment (BM and VM) I C R C C C I I I Oracle Database Deployments on Oracle Database Appliance I I R C C C I I I Virtual Machine Management on Oracle Database Appliance I C C R C C I I I Oracle Database Appliance Operations and Monitoring I I R C C C C I C Oracle Database Appliance Management Patching I I R C I I I C I Oracle Database Appliance Management Problem Resolution (HW) I I C I I I I I R Oracle Database Appliance Management Problem Resolution (SW) I I R C C C I C I Oracle Database Appliance Management Problem Resolution (NW) I I C C R I I I C

A responsibility assignment matrix, also known as RACI matrix describes the participation by various roles in completing tasks ordeliverables for a project or business process. It is especially useful...

Events

Checking health of your Oracle Database Appliance using ORAChk

ORAChk (formerly ODAChk) is a handyscript tool included on Oracle Database Appliance to facilitate quick checkingand validation of configuration, best practices, and patches on the system.ORAChk is integrated with OAKCLI, the Oracle Database Appliance command-lineinterface, and should be run as the root user. ORAChk is a handy configurationvalidation tool. Over time, users may knowingly or unknowingly make changes toOracle Database Appliance configuration or the environment growth may have led tointentional or unintentional changes. ORAChk is typically used to validateOracle Database Appliance configuration periodically (say after each upgrade orpatching event, or every 3 or 6 months, etc.) and to quickly identify anydeviations. The ORAChk script tool can beaccessed as “oakcli orachk” from either Oracle Database Appliance server node.The tool can be run against any of the available database environmentscurrently running on the servers and the output is displayed on the screen aswell as captured in an HTML file (and zip file) located within the/opt/oracle/oak/orachk directory for easier viewing (and upload to OracleSupport, if needed). Among other things, such asverifying that Oracle Database Appliance adheres to the best practices and thatany customizations have not have resulted in a configuration deviation fromthose best practices, ORAChk also checks and validates the operation of theOracle software stack on both servers in the Oracle Database Appliance cluster. Some of the checks that are carriedout by ORAChk are as follows: Checks against Oracle Database Appliance Best Practices reference setASM Disk Group attributes and ASM initialization parametersDatabase standard and undocumented parameters’ settingsKernel parameters and shared memory configurationOS packages installed and patches for Grid Infrastructure and for RDBMS home The ORAChk output highlightsactionable items and upon reviewing ORAChk output, action may be planned foraddressing any anomalies to re-align the Oracle Database Applianceconfiguration as originally intended.

ORAChk (formerly ODAChk) is a handy script tool included on Oracle Database Appliance to facilitate quick checking and validation of configuration, best practices, and patches on the system.ORAChk is...

Events

Agile Development and Oracle Database Appliance

Agile software development is a group ofsoftware development methods in which requirements and solutions evolve as selforganizing, cross functional teams collaborate to build the product orsolution. Oracle Database Appliance provides an ideal platform for AgileDevelopment. The following are some of the Oracle Database Appliance featuresand functionalities that enable the desired flexibility and adaptability, thatmay be key to all Agile development environments. 1. Pay-as-you-grow licensing method Oracle Database Appliance allows for dynamicenabling of CPU cores and software licensing. Thus, you have the ability toidentify and measure your requirements before making investments, and then growthe platform capacity at the touch of a button. 2. Oracle Database Appliance VirtualizedPlatform Implementation Oracle Database Appliance can be deployed as aVirtualized Platform wherein you can deploy not only databases but also themiddle-tiers and web-tiers, all on the same hardware system. Additional, components(virtual machines/ virtual servers) can also be dynamically deployed dependingon your requirements while minimizing costs (the database systems operates fromonly one, specialized VM on each server) and maximizing flexibility andavailable capacity.   3. Dynamic and transparent extensibility ofstorage system In the default configuration, Oracle DatabaseAppliance has one storage shelf. However, an additional storage shelf can beordered and dynamically and transparently added to the system without affectingthe operational system, thus doubling the storage capacity of the system ondemand. 4. Rapid provisioning and cleanup Oracle Database Appliance allows for trulyrapid provisioning of database environments. Using a command-line interface(“oakcli create database”) command, you can provision a stable, pre-tuned,database environment in a matter of minutes. The removal of database is alsosimilarly rapid and easily accomplished. It is also easy to clean up the entireenvironment and reset it to factory state should you need to redeploy for anyreason, reset/restart a project workstream, or move systems among data centers,etc. 5. Multiple software stack versions on oneplatform Oracle Database Appliance allows you toconfigure multiple versions of the Oracle Database on the same hardwareplatform without having to worry about inter-operability and platform patching.This makes it easy to transition back and forth between multiple versions ofthe software stack, if needed. 6. Ability to restructure platform and rapidlyredeploy Oracle Database Appliance gives you multipleoptions for initial deployment. For example, you can choose the RDBMS versionsto deploy, the level of disk mirroring, the location of backups, databasecharacter sets, database block sizes, and so forth. Although in many cases,these requirements do not change half way through the product, in some casesthey do. In a traditional environment it may be very difficult to adapt to suchchanges, but on Oracle Database Appliance, many such changes can be more easilyincorporated.

Agile software development is a group of software development methods in which requirements and solutions evolve as self organizing, cross functional teams collaborate to build the product orsolution....

Events

Oracle Database Appliance Plug-In for Enterprise Manager

With the OracleDatabase Appliance plug-in, you can monitor Oracle Database Appliance targetsusing Oracle Enterprise Manager Cloud Control 12c. The plug-in providesconfiguration and monitoring information about any Oracle Database Appliancetarget running Appliance Manager 12.1.2.2 or higher. Features include: Monitoring of theOracle Database Appliance as an Enterprise Manager target Monitoring a dynamicgroup of Oracle Database Appliance systems using tags Oracle Database Appliance components (DB,ILOM, HOST, Virtual Machines, Hypervisor, ASM, and Oracle Appliance Manager)are grouped and can be monitored under a target The Oracle Database Appliance (ODA) Plug-In for EnterpriseManager is now available. It can beupdated via the Self Update feature of Enterprise Manager, which updatescomponents whenever new or updated features become available. The ODA Plug-Inis now available via the Enterprise Manager Store, an external site that isperiodically checked by Enterprise Manager Cloud Control to obtain informationabout updates ready for download. The documentation can be found in the Oracle Enterprise Manager CloudControl Documentation 12c Release 4 Plug-Ins library. Update your Enterprise Manager today and check out the ODA Plug-In!

With the Oracle Database Appliance plug-in, you can monitor Oracle Database Appliance targets using Oracle Enterprise Manager Cloud Control 12c. The plug-in providesconfiguration and monitoring...

Events

Oracle Database Appliance 12.1.2 release new features to support a Test/Dev environment in minutes!

Oracle Database Appliance release 12.1.2 supports databaseand VM snapshots to create storage-efficient and fast instances of the databaseand guest VMs.  This capability is nowenabled with each Oracle Database Appliance running with the latest ApplianceManager 12.1.2 update. Each new Oracle Database version 12.1.0.2 or 11.2.0.4 willbe created in Oracle’s clustered file system, ACFS. ACFS is a highly performant and highlyavailable cluster file system that is built on top of Oracle ASM.  It is fully integrated with the GridInfrastructure and is database-IO aware.  With a new single command, a database snapshot is created inminutes ready to be used for testing. oakcli create snapshotdb –db <snap-shot-db-sid> -from<existing-db-sid> Oracle Database 12.1.2 release also includes the support of: Database version: 12.1.0.2, 11.2.0.4, 11.2.0.3,11.2.0.2 Choice of CDB and non-CDB database for new12.1.0.2 databases VM Snapshots VDisk Support The ODA OTN Page has updated FAQ, Data Sheet, and whitepaper. The Oracle Database Appliance Documentation has a new book - Administrations and Reference Guide and updated GettingStarted Guide. Downloadthe latest Oracle Database Appliance 12.1.2 patch release from My OracleSupport (MOS)!

Oracle Database Appliance release 12.1.2 supports database and VM snapshots to create storage-efficient and fast instances of the database and guest VMs.  This capability is nowenabled with each...

Product News

Deploy Oracle Enterprise Manager Cloud Control 12c Solution-in-a-Box on Oracle Database Appliance

The new Oracle White Paper title Solution-in-a-box: Deploying Highly Available Monitoring Infrastructure using Oracle Enterprise Manager Cloud Control 12c and Oracle Database Appliance is now available. This white paper outlines the process of setting up the complete stack of Oracle Enterprise Manager Cloud Control 12c on Oracle Database Appliance Virtualized Platform. Now you can deploy a highly available Enterprise Manager Cloud Control 12c configuration including Oracle Management Repository (OMR) database servers and Oracle Management Service (OMS) servers almost instantaneously. The setup uses virtual machines all in a single Oracle Database Appliance environment. If you are considering "trying out" or evaluating Oracle Database Appliance, Enterprise Manager Cloud Control may be an great choice for your first system to build on Oracle Database Appliance and in the process learn all about it and see it prove its value.Oracle Database Appliance already provides standard, pre-tuned templates to setup fully optimized OMR databases quickly. A new pre-built, ready to deploy VM Template is provided to facilitate rapid deployment of Oracle Enterprise Manager Cloud Control 12c.The white paper can be accessed through My Oracle Support Note 1673246.1 or through Oracle Tehnnology Network using the following link:http://www.oracle.com/technetwork/database/database-appliance/documentation/oda-oemcloudcontrol-2209378.pdf 

The new Oracle White Paper title Solution-in-a-box: Deploying Highly Available Monitoring Infrastructure using Oracle Enterprise Manager Cloud Control 12c and Oracle Database Appliance is now...

Events

Try the Oracle Database Appliance Manager Configurator - For Fun!

If you wouldlike to get a first hand glimpse of how easy it is to configure an ODA, even ifyou don’t have access to one, it’s possible to download the ApplianceManager Configurator from the OracleTechnology Network, and run it standalone on your PC or Linux/Unix workstation. The configuratoris packaged in a zip file that contains the complete Java environment to runstandalone. Once the package is downloaded and unzipped it’s simply amatter of launching it using the config command or shell depending onyour runtime environment. Oracle Appliance Manager Configurator is a Java-basedtool that enables you to input your deployment plan and validate your networksettings before an actual deployment, or you can just preview and experiment with it. Simplydownload and run the configurator on a local client system which can be aWindows, Linux, or UNIX system. (For Windows launch the batch file config.batfor Linux/Unix environments, run  ./ config.sh). Youwill be presented with the very same dialogs and options used to configure a production ODA but on your workstation. At the end of a configurator session, you may save yourdeployment plan in a configuration file. If you were actually ready to deploy, you could copythis configuration file to a real ODA where the online OracleAppliance Manager Configurator would use the contents to deploy your plan in production. Youmay also print the file’s content and use the printout as a checklist forsetting up your production external network configuration. Be sure to use theactual production network addresses you intend to use it as this will only workcorrectly if your client system is connected to same network that will be usedfor the ODA. (This step is not necessary if you are justpreviewing the Configurator). This is a great way to get an introductory look atthe simple and intuitive Database Appliance configuration interface and the stepsto configure a system.

If you would like to get a first hand glimpse of how easy it is to configure an ODA, even if you don’t have access to one, it’s possible to download the Appliance Manager Configurator from the OracleT...

Events

Expanding the Storage Capabilities of the Oracle Database Appliance

The Oracle Database Appliance X4-2 comes with a total of 18TBs of raw shared storage and depending on availability requirements can beconfigured in a mirrored configuration yielding 9 TBs of usable storage orconfigured in a tripled-mirrored maximum availability configuration for a totalof 6 TBs of usable storage. In most cases this is a sufficient amount ofstorage but if users require additional storage, there are two options for storageexpansion depending on their requirements. Storage Expansion Shelf The first option is to add the Storage Expansion Shelf thateffectively doubles the raw storage and usable storage. The additional storage shelf isdirectly cabled to the storage controllers and zero-admin is required for thestorage to be added to the Oracle Database Appliance.  After you havecabled and turned it on, The Appliance Manager software configures andre-balances the data across both storage shelves which effectively scales in alinear fashion providing approximately twice the I/O throughput as all spindlesare used for the data re-balance. This is a great option when additional high performancelocally attached shared storage is needed, especially for virtual environmentswhere user defined virtual machines need storage space. Networked Attached Storage Customers canuse Oracle compatible NFS-attached storage with Oracle Database Appliance. An excellentoption is to use Oracle’s ZFS StorageAppliance. There are several features of the Oracle Sun ZFS StorageAppliance that make it the ideal choice for expanding the storage capabilitiesof the Oracle Database Appliance. These features include intuitive managementtools, real-time performance analysis, data compression, multiprotocolintegration, de-duplication, cloning and HybridColumnar Compression, (HCC). NFS storage isalso a great option to create external database disk backups. Network attachedstorage for database backups allows isolation of backups from the internalstorage, and opens a range of possibilities for management of the backupsincluding replication to a remote site, snapshots for additional copies ofbackups, compression of backups by the ZFS Appliance, and sharing of thebackups with another database server. For a good discussion of network storagebackups, (See - Backupand Recovery Strategies for the Oracle Database Appliance).

The Oracle Database Appliance X4-2 comes with a total of 18 TBs of raw shared storage and depending on availability requirements can beconfigured in a mirrored configuration yielding 9 TBs of...

Events

Why Does ODA Use Enterprise Edition?

All of Oracle’s Engineered Systems, including ODA, engineer their solutions for optimal Availability, Performance, Security and Scalability. When we compare Enterprise Edition with Standard Edition we see some significant features in Enterprise Edition that provide maximum Availability, Performance, Security and Scalability to provide ODA with an optimal Enterprise Database Solution. AVILIBILITY: In the area of Availability, Enterprise Edition has many unique features that enhance availability not found in Standard Edition including: RAC One Node Data Guard—Redo Apply Data Guard—SQL Apply Data Guard—Snapshot Standby Active Data Guard Rolling Upgrades—Patch Set, Database, and Operating System Online index rebuild Online index-organized table organization Online table redefinition Duplexed backup sets Block change tracking for fast incremental backup Unused block compression in backups Block-level media recovery Lost Write Protection Automatic Block Repair Parallel backup and recovery Tablespace point-in-time recovery Trial recovery Fast-start fault recovery Flashback Table Flashback Database Flashback Transaction Flashback Transaction Query Flashback Data Archive (Total Recall) PERFORMANCE:When we look at Performance, Enterprise Edition has the Parallel Query feature not found in Standard Edition. In benchmarking on ODA, with real customer workloads, we have seen better performance when compared to Standard Edition. For many workloads this means a requirement for fewer cores to execute the same workloads while maintaining the same service levels. When we couple this performance advantage with ‘on-demand’ software licensing, (an exclusive ODA feature), it can result in a significant reduction in the overall cost of Enterprise Edition licensed cores. SECURITY: Security is an imperative for all enterprise customers and especially important to financial, public sector, healthcare and retail customers. ODA using Enterprise Edition is able to offer security features not supported in the Standard Edition: Oracle Advanced Security Oracle Label Security Virtual Private Database Fine-grained auditing Oracle Database Vault Enterprise User Security SCALABILITY: To protect our customer’s investment in the ODA Engineered System, and extend its useful life, Enterprise Edition offers features that extend system Scalability that do not exist in Standard Edition including: Quality of Service Management Performance                                        Client Side Query Cache                 Query Results Cache      PL/SQL Function Result Cache In-Memory Database Cache       Database Smart Flash Cache

All of Oracle’s Engineered Systems, including ODA, engineer their solutions for optimal Availability, Performance, Security andScalability. When we compare Enterprise Edition with Standard Edition we...

Events

ODA Makes Service Easier, Before You Need it and When You Need It!

One of the many features that helps make ODA systems administration much easier for customers is a feature called Auto Service Request, (ASR). There are times when ODA Administrators spend time detecting and diagnosing hardware problems, and resolving them. Managing these problems can be time consuming and a distraction from other more important activities. ODA’s ASR is a secure, optional customer-installable support feature that provides automatic service generation and priority service request handling for certain hardware faults that might occur in the ODA. Let’s take a closer look at how ODA’s ASR works. When a hardware fault is detected, ASR opens an Oracle Support Service Request, (SR), and automatically transmits detailed electronic fault diagnostic information to Oracle Support to help them expedite the diagnostic and problem resolution process. (It can also be configured to notify the local administrator or anyone else on the customer end). If parts are necessary to correct the problem they will be dispatched upon receipt of the SR, and in many cases, Oracle engineers will begin working to resolve the problem before others are even aware it exists! ODA’s ASR only requires an outbound, secure Internet connection to Oracle (based on SSL and https). Customers configure ASR options using the ODA Configurator and may configure ODA ASR during a Custom deployment. They may also configure ASR after deployment (either Typical or Custom) using the oakcli configure asr command.The command prompts for inputs and after all of the required information is supplied, it completes the ASR configuration and is very simple and easy to use. An ASR configuration requires an administrator to enter their My Oracle Support account user name and password. If you’re using a proxy server for Internet access to Oracle, then the proxy servers name will need to be supplied. A complete description of all the steps and options for ASR configuration are outlined in the Oracle Database Appliance Getting Started Guide, page 5-2, Configuring Oracle Auto Service Request. ODA doesn’t require a dedicated ASR server like other Oracle products and this makes ASR simpler to install and use. However, if you are using an ASR server for other Oracle hardware then ODA is flexible enough to allow you to connect to and use the existing ASR dedicated server optionally. If your ODA system is covered under an Oracle Premier Support for Systems plan or is under product warranty, you can take advantage of ODA’s ASR at no additional cost. ODA’s ASR feature can help improve your system availability and reduce the time to resolve issues.  Make sure you take advantage of this excellent support feature to simplify service requests and compress the time to repair.

One of the many features that helps make ODA systems administration much easier for customers is a feature called Auto Service Request, (ASR). There are times when ODA Administrators spend...

Product News

Why Virtualized Platform is the best deployment option for Oracle Database Appliance

Recently a user asked, what are the considerations for usingthe Virtualized Platform configuration or the Bare Metals configuration onOracle Database Appliance? Certainly, the Virtualized Platform configurationseems to provide everything that the Bare Metals configuration does plus more. Listed below are some of the considerations for why you maywant to prefer to use the Oracle Database Appliance Virtualized Platformoption. 1. A single hardware environment for deploying both database andapplications 2. Database runs in a Virtual Machine (ODA_BASE) with direct access tostorage (for native performance) 3. Control licensed CPUs by configuring ODA_BASE domain withthe required number of CPU cores (and memory) 4. CPU cores (and memory) not assigned to the ODA_BASEdomain are not wasted and are available for use by other, non-database Virtual Machiness 5. Oracle provided pre-configured VM application templatesenable rapid deployment for both the database and applications 7. Use VLAN to provide separate networks to different Virtual Machines 8. Use shared repository to grow storage for VM repository 9. No VM expertise needed; Oracle Appliance Manager (oakcli)makes it easy to setup and manage the virtualized environment

Recently a user asked, what are the considerations for using the Virtualized Platform configuration or the Bare Metals configuration onOracle Database Appliance? Certainly, the Virtualized...

Product News

BI Solution-in-a-Box -- Enterprise Class BI for the Mid Market

Attend the Webinar on January 23rd @ 12 noon ET, 9:00 am PT  Tammy Bednar, WillHutchinson, Rob Klaassens, and Mike Mrazek,  Oracle Corp. Since the Oracle Database Appliance (ODA) started supportingOracle Virtual Machine (OVM) twelve months ago, we have seen several groupsdevelop purpose built offerings on top of it, called “Solutions in a Box,”where they combine an application or middleware on top of the robust, costeffective ODA platform. The newestmember of this family combines enterprise class business intelligence, dataintegration and Oracle’s enterprise class database at a price mid market organizationscan afford. In our prior post, wedescribed the need IT industry analysts see for mid market organizationsadopting business intelligence. In thispost, we will talk about how Oracle addresses this need. To address this need, Oracle has developed the BISolution-in-a-Box. It contains theOracle database with partitioning, diagnostics, and tuning, BI FoundationSuite, and Oracle Database Integrator, all running in two virtual machines onthe Oracle Database Appliance. It ispackaged to let customers license only the cores they need, expand as theygrow, and be easy to buy and support, all supported by a single vendor. Because it is based on standardOracle products, one can add other hardware, database or BI products ifdesired, like more storage, RAC, Advanced Analytics or an Oracle BIApplication. By providing enterprise class BI in a pre integratedpackage, Oracle has brought enterprise class functionality to the midmarket. Enterprise class organizations,no matter what size, recognize that they stay enterprise class by adoptingsolutions that minimize their total cost of ownership. By pre integrating the hardware, firmware,operating system, virtualization, database, ETL, and BI, Oracle has provided apackage that minimizes the total cost of ownership by eliminating integrationchallenges and minimizing the effort needed to stand up a business intelligencesystem. In addition, the toolsthemselves are regarded as having industry leading total costs ofownership. All these advantages helpmidsize organizations increase their agility while minimizing their laborcosts. Labor costs, according toGartner, are at least 75% of the total cost of ownership of a businessintelligence system. In addition, to make this solution easier to buy, Oracle haspre arranged financing through Oracle Finance Division to make the purchaseeither a loan or a lease depending on whether customers would prefer to treatthe expenditure as a capital expense or an operating expense. Oracle will be introducing and discussing the Oracle DatabaseAppliance and BI Solution in a Box on a Webinar on January 23rd. For more information and to register for theevent, please register to attend the event: http://www.oracle.com/us/dm/245722-nafs13054094mpp037-se-2052054.html

Attend the Webinar on January 23rd @ 12 noon ET, 9:00 am PT  Tammy Bednar, Will Hutchinson, Rob Klaassens, and Mike Mrazek,  Oracle Corp. Since the Oracle Database Appliance (ODA) started supportingOracl...

Product News

BI for the Mid Market

Tammy Bednar, WillHutchinson, Rob Klaassens, and Mike Mrazek, Oracle Corp. Oracle and industry analysts have seen a rapid expansion ofbusiness intelligence and data warehouse solutions into midsize and smallerorganizations.  The need to understandhow they are serving their customers, how their suppliers are serving them andthe opportunity to drive growth and cost reductions requires insights into data. ERP,Performance Management systems and CRM/CX systems are great way to collect databut do not provide and easy and flexible way to combine data from multiplesources for in depth analysis. Traditionally, midsize and smaller organizations have reliedon spreadsheets or downloads of data to a personal database to meet theseneeds. However these solutions do notscale and suffer from problems of inconsistent data, errors, manual work andnon-repeatable processes for gathering and analyzing data, leading to theinability to respond quickly. In thepast, these organizations have not invested in business intelligence because theperception was that a Business Intelligence or Data Warehouse Strategy was tooexpensive to install and maintain. Onewould have to buy and configure hardware, a database, BI and ETL tools, andother middleware. The time, effort andcost to support these types of solutions would typically overwhelm most midsizeIT staffs. Also, deploying these systemscan cost several hundred thousand dollars over five years, after taking intoaccount both out of pocket costs and the time the staff spends on BI, timewhich if it were available could effectively be spent elsewhere. Register today to attend and learn how you can replace thoseExcel spreadsheets and Access databases with the type of analytics big companieshave, analytics you thought you could never afford. http://www.oracle.com/us/dm/245722-nafs13054094mpp037-se-2052054.html

Tammy Bednar, Will Hutchinson, Rob Klaassens, and Mike Mrazek, Oracle Corp. Oracle and industry analysts have seen a rapid expansion ofbusiness intelligence and data warehouse solutions into midsize...

Product News

Some nice new features in Oracle Appliance Manager 2.8 (OAK 2.8)

Oracle Appliance Manager 2.8 (aka, OAK 2.8) has a number ofnew, useful, and important features that further enhance ODA product capabilityand flexibility. In a nutshell, the following are the key new enhancements inOAK 2.8.  You can find details of each ofthese new features in the Oracle DatabaseAppliance Getting Started Guide. Support for a sharedrepository for virtual machines and templates – If you are an ODAVirtualized Platform user, then this may be a big enhancement for you. In theearlier versions of Oracle Appliance Manager, the VM repository was stored onlyon local disks on each ODA server node. That restricted the amount of storageavailable for the storing and sizing VMs to the free space available on thelocal 600GB disks, which was 250GB on V1 ODA hardware and 350GB on the X3-2 ODAhardware. However, the newly available shared repository implementation allowsfor the creation of the VM repository on the shared storage, thereby significantlyincreasing the storage available for the VM repository. You can create a shared repository using the “oakcli create repo<repository-name> -dg <disk-group-name> -size <size in GB>”command. You can place the repository in the DATA or the RECO ASM disk group. Placingthe repository on the shared storage not only increases the capacity of therepository, it also makes the repository accessible on both server nodes,thereby facilitating VM failover capabilities. Support for VLANs -With the 10GB network interfaces available on ODA, there is plenty of networkbandwidth on the servers. VLAN (Virtual Local Area Network) provides a means tosecure network traffic and isolate networks using logical identifiers.Broadcast propagated in one VLAN is thus not transmitted to the other VLANs.This also improves security as by placing devices in different broadcastdomains, it is possible to limit access through the use of address filters andaccess lists. For communication across VLANs the traffic must pass through alayer-3 routing device, which can be configured to control and monitor accessamong different devices. You can create and manage VLANs using OAKCLI commands. Forexample, use the "oakcli create vlan <vlan name> -vlanid <vlantag id> -if <interface name> -node <0|1>" command to createa VLAN on ODA. Similarly, "oakcli show vlan", "oakcli delete vlan"commands are available to see VLAN configuration, delete a VLAN configuration,etc. Database setup is nowoptional at the time of initial deployment – In the earlier versions ofOracle Appliance Manager, during the initial deployment, you had to create aninitial database as part of the deployment. Sometimes, at the time of initialdeployment users were not quite ready to create the database and needed to planfor its size, naming, and other configuration settings etc. With OAK 2.8, younow have the option to forgo the creation of this initial database. Instead, you may choose to create the database after the initialdeployment using the “oakcli create database …” command. Note that you may usethe default parameter file (/opt/oracle/oak/install/dbconf/default.dbconf) thatspecifies the block size, database language, characterset, etc. or create a newdb configuration parameter file using the “oakcli create db_config_params …)command before issuing the “oakcli create database…” command. Hardware monitoringusing OAKCLI – OAKCLI becomes even more powerful. From OAK 2.8 onwards, youcan now monitor all hardware components (except storage, currently) of ODAusing the OAKCLI command-line interface. This includes monitoring of servers,processors, memory, network interfaces, cooling units, and power units, etc. To monitor a component, simply issue the “oakcli show<component-name>” command. Where component name may be “server”, “processor”,“memory”, “power”, “cooling”, or “network”. Flexibility to have additionalcustomizations – In the earlier version of Oracle Appliance Manager, standardUID/GID and usernames were used for Oracle and Grid users. If you need toadhere to certain local standards for usernames and ID numbers that you mayhave in place within your organization, then using the advanced deploymentoption of Appliance Manager you can now specify non-default UID/GID andusernames for Oracle and Grid owner users. The advanced deployment option is invoked simply by issuingthe “oakcli deploy –advance” command.

Oracle Appliance Manager 2.8 (aka, OAK 2.8) has a number of new, useful, and important features that further enhance ODA product capabilityand flexibility. In a nutshell, the following are the key...

Events

Managing Oracle Database Appliance

There are three key tools that you can use to manage theOracle Database Appliance. Together, these tools are adequate to completelymanage, maintain, and operate Oracle Database Appliance including the hardwareplatform, the operating system, and the databases running on the system. Oracle IntegratedLights Out Manager (a.k.a., Oracle ILOM) Oracle ILOM provides a “just like being there” experienceand allows you to completely manage your system remotely (including powering itup and shutting it down) over a dedicated network interface. You can start the Remote Console over a web interface to connect to an Oracle DatabaseAppliance server node, check status of hardware components, manage faults (ifany), monitor system temperature and ambience, re-image server, and so forth.Point your web browser to the IP address you have configured for theserver’s ILOM network interface, and there you are. You typically configureOracle ILOM interface on Oracle Database Appliance server nodes at the time ofinitial deployment using the Configurator (when you issue the "oakcli deploy" command). Alternatively, youcan configure ILOM before the deployment using the server’s BIOS utility (pressing the F2 key duringsystem boot), or using the “ipmitool” utility from the server operating systemcommand line. You can also configure Oracle ILOM on Oracle Database Appliance afterthe initial deployment of the system using any of the latter two methods (BIOS or ipmitool). Oracle EnterpriseManager Database Control (OEM) Oracle Enterprise Manager Database Control is a no-cost toolto manage Oracle databases and it can be automatically configured at the timeof initial deployment of Oracle Database Appliance. Database Control provides aweb user interface to manage, maintain, and operate the Oracle database. Thisincludes administering users, data structures, database and instances, usersessions, backup and recovery, analyzing performance, tuning SQL, instance, anddatabase, and so forth. Alternatively, if you use Oracle Enterprise ManagerGrid Control or Oracle Enterprise Manager Cloud Control in your organization, you can use it tomanage databases running on Oracle Database Appliance. An Oracle DatabaseAppliance plug-in may also become available for Oracle Enterprise Manager CloudControl in the future. Oracle ApplianceManager (oakcli) Oracle Appliance Manager command-line interface (oakcli)provides unique abilities to manage, maintain, and operate the Oracle DatabaseAppliance platform. This includes setup and deployment of the system, runningdiagnostics on servers and storage, patching server, storage, and network, andcreating multiple Oracle homes and database environments, and so forth. Starting with Oracle Appliance Manager 2.8, youcan also monitor the hardware (servers, CPUs, power, cooling, and so forth) usingoakcli. You can invoke Oracle Appliance Manager command-line interface usingthe /opt/oracle/oak/bin/oakcli command from an Oracle Database Appliance servernode.

There are three key tools that you can use to manage the Oracle Database Appliance. Together, these tools are adequate to completelymanage, maintain, and operate Oracle Database Appliance...

Product News

Comparing Oracle Database Appliance (ODA) with manually built and assembled systems

I thought I ought to have this note to outline the differences between typical old-style system building approach and the engineered system approach used for Oracle Database Appliance. Oracle Database Appliance is a unique, modern product thatis revolutionary and disruptive. It is an Oracle engineered system that servesas a highly available database and application server. Its benefits are unique andunparalleled. However, as with any new, disruptive product, users may notreadily recognize all the benefits. Often new customers ask for the benefits ofchoosing Oracle Database Appliance versus building your own system. The matrixbelow tries to summarize the benefits. Oracle Database Appliance Manually assembled systems Single vendor – Customer only needs to contact Oracle for any and all problems with the system. Oracle is able to rapidly diagnose the problem, match it with a fingerprint of the issue, and provide immediate solution. Multiple vendors – Servers, storage, networking gear, and software components may be sourced from different vendors, that causes finger pointing and makes it hard to obtain support quickly and effectively No integration required – Oracle Database Appliance is a pre-integrated, pre-tested, pre-tuned configuration. It requires no integration, other than simply plugging in some cables. Extensive integration required – The components sourced from multiple vendors must be compatible and interoperate successfully. Instant deployment – Deployment of Oracle Database Appliance in a customer environment is as easy as plugging in the cables, powering on the system and issuing a command. Long drawn error prone deployment process – Deployment of a manually built system requires setting up and validating each component, going through multiple steps to configure operating system, networking, storage, database, and so forth. A missed-step can be costly. Best practices are included – Oracle Database Appliance is built from the grounds up with Oracle’s best practices in mind. These best practices cover operating system, networking, storage, database, and performance and availability best practices. Best practices implementation requires considerable extra effort - Best practices must be identified and implemented for each component. This may not be an easy task by any measure. Patching is quick and predictable – With a known hardware and software configuration, Oracle is able to provide pre-tested, complete patch bundles that cover the entire firmware and software stack. Further, Oracle is able to structure and tune the patching process so that it executed flawlessly in an optimal amount of time with predictable results. Patching is time consuming, risky and unpredictable – Customers often patch one component at a time, thereby increasing the frequency of patching. Patching process is unpredictable and therefore risky. Vendors have no way of testing the exact configuration that a customer may be using. Problem diagnostics are immediate – Oracle knows exactly which information and logs are required for instant diagnosis of problems as well as how to collect it. Oracle makes it trivial for customers to collect the information. Quick diagnosis results in rapid problem resolution. Problem diagnostics is complex and long drawn – Multiple experts may be needed to diagnose problems. Often it may not be readily apparent what information is relevant and required for a corresponding problem. Longer diagnosis results in delayed problem resolution. Performance is predictable – An engineered system makes deploying workloads a science not an art. The system capacity and capability can be quantified exactly and workloads can be deployed using simple mathematics. Performance may not always be predictable – Making workloads perform on manually assembled systems remains an art. Due to the various components and stack layers from different vendors, typically configured using an imprecise math, it is usually not possible to define capacity and capability correctly. Service requests can be opened automatically – In case of a problem, such as hardware failure, a service request can be opened automatically by the system using Oracle Auto Service Request. A solution may be available even before the customer recognizes the problem. Service request initiation and management is complex – In case of a problem first the correct vendor needs to be identified. The service request needs to be manually managed and diagnostics data needs to be identified, manually collected, and sent to the vendor. Manual analysis of diagnostics further delays solution that may need to be tested before it is deployed. Storage is integrated and managed as a whole – Storage is pre-integrated with the servers and the system is managed end-to-end as a whole, including monitoring, management, diagnostics, and repair of storage. Storage is separate and managed separately – Storage is managed, monitored, diagnosed and repaired separately, typically provided by a different vendor and managed by storage administrators Pay-as-you-go licensing saves costs substantially – Significant CPU power available but only CPUs used need to be licensed while the remaining CPU power is available for instant deployment if and when needed Must pay for all CPUs on the system upfront – All CPUs present in the servers must be licensed upfront whether fully used or not. Additional CPU addition typically requires costly hardware upgrades Versatile system with support for both native and virtualized environments – The same system and software supports both native and virtualized implementations, switching from one to the other is easy Typically vendor specialized hardware sold for native or virtualized implementations – Implementation of native and virtualized environments could be fundamentally different. Host both application and database in a single system (system in a box) – Supports hosting of entire application stack in a single system; virtualized platform makes it possible to segregate different tiers of application stack into different virtual machines that are easy to size and tune Application is typically hosted on separate hardware (one system many boxes) – Application, web, and database tiers are typically hosted on separate hardware and storage; it is not easy to resize these environments unless hardware is replaced It is amazing!

I thought I ought to have this note to outline the differences between typical old-style system building approach and the engineered system approach used for Oracle Database Appliance. Oracle Database...

Product News

Implementing Oracle Maximum Availability Architecture (MAA) using Oracle Database Appliance (ODA)

Oracle Database Maximum Availability Architecture (MAA) isOracle’s blueprint for maximizing database uptime and availability forimportant business system and mission critical architecture. Oracle RealApplication Clusters (RAC) and Oracle Data Guard and Oracle Database BestPractices are some of the key components of this architecture.  Oracle RAC provides high availability in theevent of intra-site failures (failures that occur within the primary databaseenvironment, such as node failures, network failure, etc.) while Oracle DataGuard provides high availability in the event of site level failures, storagesub-system failures, and planned downtime. Within Oracle MAA, Oracle’s DatabaseBest Practices ensure a consistent and optimal implementation of a databaseenvironment. Traditionally, implementing Oracle Database MAA has been acomplex and time consuming initiative, sometimes requiring weeks to months ofefforts to fully implement. However, youcan readily deploy Oracle Database Maximum Availability Architecture usingOracle Database Appliance (ODA). Oracle Database Appliance can provide thepre-built Oracle RAC highly available environment for each site and includesdatabase best practices embedded in the pre-configured system. Check out the white paper titled “DeployingOracle Data Guard with Oracle Database Appliance” as it provides areference sample implementation of Oracle Data Guard across Oracle DatabaseAppliance environments.

Oracle Database Maximum Availability Architecture (MAA) is Oracle’s blueprint for maximizing database uptime and availability forimportant business system and mission critical architecture....

Product News

Leverage the Oracle Database Appliance Virtualized Platform

In my opinion, one of the best things to happen to Oracle Database Appliance recently was the availability of virtualization on the system. The virtualized Oracle Database Appliance (or "Oracle Database Appliance Virtualized Platorm" as it is officially called) allows you to run multiple virtual machines, hosting different tiers of your system architecture all within a single Oracle Database Appliance. And users love it! This is a major development for those looking for drastic cost reductions in managing their traditional multi-tier systems or even consolidating many systems into one, etc. Now you can have one single platform, that is already extremely easy to setup, operate, and manage, and host many virtual servers, deploying everything from your database to application logic tier to the web-tier and other supporting systems such as a load balancer, security server, etc. all in a single environment. Some ISVs are already looking for building and selling ready-to-go complete systems for their customers with everything inside one Oracle Database Appliance.  The Oracle Database Appliance Virtualized Platform can be used with Oracle Appliance Manager (OAK) 2.5 and above for V1 hardware and with OAK 2.5.5 and above with Oracle Database Appliance X3-2 hardware. If you are on the non-virtualized deployment of your Oracle Database Appliance (and all new systems are currently  shipped from the factory with the non-virtualized ISO image), then you must re-image the server with the Oracle Database Appliance Virtualized Platform ISO image. Once you have re-imaged the servers with the virtualized platform ISO image, Oracle Appliance Manager lets you deploy a special virtual machine or domain called (ODA_BASE domain) to host all your databases. You allocate CPU and memory to this ODA_BASE domain as per your need (and available database licenses). Dedicated access to shared storage is provided to this domain by design (bypassing any negative performance impact of virtualization that it would otherwise incur) using the PCI pass through technique. The rest of the server capacity is available for deploying additional virtual machines for your application and web tiers and for other purposes. You can check out the Oracle Database Appliance Getting Started Guide for more information. Also, the updated Oracle Database Appliance Setup Poster provides the details on setting up the Virtualized Platform on the Oracle Database Appliance X3-2 system. Virtualization for real!

In my opinion, one of the best things to happen to Oracle Database Appliance recently was the availability of virtualization on the system. The virtualized Oracle Database Appliance (or "Oracle...

Events

Oracle Database Appliance X3-2 Generally Available Now

Good news! The second generation Oracle Database Appliance to be known as "Oracle Database Appliance X3-2" was released on March 5th,2013. Oracle Database Appliance X3-2 is built using the Sun Server X3-2 servers(the same servers that are used as compute nodes in Exadata environments) and is a substantiallymore powerful system with a small price differential from the earlier model. Storage Shelf consists of a 2 rack-u unit and an identical expansion storage shelf is also available. You now have 18TB of raw storage which is expandable to 36TB of raw storage(all ASM managed) within a single Database Appliance architecture and configuration. The maximum CPU power increases from 24 cores before to 36cores, while the new system now has 512 GB of memory (2x256 GB), a quantum jumpfrom the 192 GB (2x96GB) before. The local available disk storage capacityincreases from 500GB to 600GB. Oracle Database Appliance X3-2 when used as a Virtualized Platform(support for virtualization on Oracle Database Appliance was announced inFebruary 2013) can be an extremely powerful system with very substantialfurther improvement in the already compelling value proposition of OracleDatabase Appliance. On Oracle Database Appliance X3-2 you can consolidatemultiple database environments. With the Virtualized Platform deployment, youcan consolidate entire multi-tier environments within a single Oracle DatabseAppliance X3-2 system. The older model continues to be available until May31st, 2013. You can find more details on the newly announced Oracle Database Appliance X3-2 athttp://www.oracle.com/us/products/database/database-appliance/overview/index.html

Good news! The second generation Oracle Database Appliance to be known as "Oracle Database Appliance X3-2" was released on March 5th,2013. Oracle Database Appliance X3-2 is built using the Sun...

Events

Oracle Database Appliance Performance White Paper Released

A new white paper titled "Evaluating and Comparing Oracle Database Appliance Performance" was recently released. This white paper outlines a quick and simple process to evaluate the performance of Oracle Database Appliance for both OLTP and DSS workloads and compare it to the same workloads when run in your local environment. The testing for this paper was conducted using Swingbench's Order Entry (OLTP) and Sales History (DSS) workloads. Users can review already the documented results and conduct a reverse-POC (proof-of-concept) in their legacy environment by running Swingbench and then simply compare relative performance.  For the testing conducted during the course of writing this white paper, Oracle Database Appliance was able to support up to 10,000 Swingbench users for the OLTP workload (while maintaining sub-second response times) and provided throughput of more than 2400 MB/Second for the DSS workload. Both are significant numbers. The white paper provides the results of various core configurations tests (related to the pay-as-you-grow feature) in a matrix form.The paper also covers some minor tweaks to the standard configuration that can enable even greater workload performance. I invite you to take a look at http://www.oracle.com/technetwork/server-storage/engineered-systems/database-appliance/documentation/oda-eval-comparing-performance-1895230.pdf

A new white paper titled "Evaluating and Comparing Oracle Database Appliance Performance" was recently released. This white paper outlines a quick and simple process to evaluate the performance of...

Product News

ASM Normal Redundancy versus High Redundancy on Oracle Database Appliance

The availability of normal redundancy configuration optionfor Automatic Storage Management (ASM) on Oracle Database Appliance starting with OAK version 2.4 allows foradditional usable space on Oracle Database Appliance (about 6 TB with NormalRedundancy versus about 4 TB with High Redundancy). This is great news for manycustomers. Some environments, such as test and development systems, maybenefit significantly as a result of this new option. However, the availabilityof Normal Redundancy option obviously should not be taken to mean that choosingNormal Redundancy may the best approach for all database environments. High redundancy would still provide a better andmore resilient option (and may be a preferred choice) for mission criticalproduction systems. It is therefore an option and not the default configurationchoice. Many customers may choose to use Normal Redundancy for test, development, and other non-critical environments and High Redundancy for production and other important systems. In general, ASM supports three types of redundancy (mirroring*)options. High Redundancy -In this configuration, for each primary extent, there are two mirrored extents.For Oracle Database Appliance this means, during normal operations there wouldbe three extents (one primary and two secondary) containing the same data, thusproviding “high” level of protection. Since ASM distributes the partneringextents in a way that prevents all extents to be unable due to a componentfailure in the IO path, this configuration can sustain at least twosimultaneous disk failures on Oracle Database Appliance (which should be rare but is possible). Normal Redundancy- In this configuration, for each primary extent, there is one mirrored (secondary)extent. This configuration protects against at least one disk failure. Notethat in the event a disk fails in this configuration, although there istypically no outage or data loss, the system operates in a vulnerable state,should a second disk fail while the old failed disk replacement has notcompleted. Many Oracle Database Appliance customers thus prefer the High Redundancy configuration tomitigate the lack of additional protection during this time. External Redundancy- In this configuration there are only primary extents and no mirrored extents.This option is typically used in traditional non-appliance environments whenthe storage sub-system may have existing redundancy such as hardware mirroringor other types of third-party mirroring in place. Oracle Database Appliancedoes not support External Redundancy. *ASM redundancy is different from traditional disk mirroringin that ASM mirroring is a logical-physical approach than a pure physicalapproach. ASM does not mirror entire disks. It mirrors logical storage entitiescalled ‘extents’ that are allocated on physical disks. Thus, all “mirrored”extents of a set of primary extents on a given disk do not need to be on asingle mirrored disk but they could be distributed across multiple disks. Thisapproach to mirroring provides significant benefits and flexibility. ASM usesintelligent, Oracle Database Appliance architecture aware, extent placementalgorithms to maximize system availability in the event of disk failure(s).

The availability of normal redundancy configuration option for Automatic Storage Management (ASM) on Oracle Database Appliance starting with OAK version 2.4 allows foradditional usable space on Oracle...

Events

Normal Redundancy (Double Mirroring) Option Available

The Oracle Database Appliance 2.4 Patch was released lastweek and provides you an option of ASM normal redundancy (double mirroring) duringthe initial deployment of the Database Appliance. The default deployment of the Oracle DatabaseAppliance is high redundancy for the +DATA and +RECO disk groups. While there is 12TB of raw shared storageavailable, the Database Backup Location and Disk Group Redundancy govern howmuch usable storage is presented after the initial deployment is completed. The Database Backup Location options are Local orExternal. When the Local Backup Optionis selected, this means that 60% of the available shared storage will beallocated for the Fast Recovery Area that contains database backups and archivelogs. The External Backup Option willallocate 20% of the available shared storage to the Fast Recovery Area. So, let’s look at an example of High Redundancy and ExternalBackups. Disk Group Redundancy – High --> Triple Mirroring to provide ~4TB of available storage Database Backup Location – External --> 20%of available shared storage allocated to +RECO +DATA = 3.2TB of usable storage, +RECO = 0.8TBof usable storage What about Normal Redundancy with External Backups? Disk Group Redundancy – Normal --> Double Mirroring to provide ~6TB ofavailable storage Database Backup Location – External --> 20%of available shared storage allocated to +RECO +DATA = 4.8TB of usable storage, +RECO = 1.2TBof usable storage As a best practice, we would recommend using NormalRedundancy for your test and/or development Oracle Database Appliances and HighRedundancy for production.

The Oracle Database Appliance 2.4 Patch was released last week and provides you an option of ASM normal redundancy (double mirroring) duringthe initial deployment of the Database Appliance. The...

Events

Is Oracle Database Appliance (ODA) A Best Kept Secret?

There is something about Oracle Database Appliance that underscores the tremendous value customers see in the product. Repeat purchases. When you buy “one” of something and come back to buy another, it confirms that the product met your expectations, you found good value in it, and perhaps you will continue to use it. But when you buy “one” and come back to buy many more on your very next purchase, it tells something else. It tells that you truly believe that you have found the best value out there. That you are convinced! That you are sold on the great idea and have discovered a product that far exceeds your expectations and delivers tremendous value! Many Oracle Database Appliance customers are such larger-volume-repeat-buyers. It is no surprise, that the product has a deeper penetration in many accounts where a customer made an initial purchase. The value proposition of Oracle Database Appliance is undeniably strong and extremely compelling. This is especially true for customers who are simply upgrading or “refreshing” their hardware (and reusing software licenses). For them, the ability to acquire world class, highly available database hardware along with leading edge management software and all of the automation is absolutely a steal. One customer DBA recently said, “Oracle Database Appliance is the best investment our company has ever made”. Such extreme statements do not come out of thin air. You have to experience it to believe it.Oracle Database Appliance is a low cost product. Not many sales managers may be knocking on your doors to sell it. But the great value it delivers to small and mid-size businesses and database implementations should not be underestimated. 

There is something about Oracle Database Appliance that underscores the tremendous value customers see in the product. Repeat purchases. When you buy “one” of something and come back to buy another,...

Events

Oracle Database Appliance Value Proposition for Small and Mid-size Businesses

Today most customers want their databases and systems to be always available (always on!). No one, whether it is a customer, an employee, a partner, or anyone else, wants to deal with a down system. The “seven second rule” that summarizes customers’ patience threshold is all well known in the internet driven world. In today’s fast paced world with a plethora of information and product sources available at one’s fingertips, the general level of consumer patience is greatly reduced. High availability and good performance is ever more important. But many a times, customers leave their HA and performance needs unfulfilled. Why? Because they think,1. For middle sized businesses reliable HA hardware is expensive2. There are significant upfront costs in setting up HA systems3. HA systems are just hard to implement4. There is substantial on-going management cost associated with HA systems, etc. If a small or medium sized business used the “traditional approach” to assembling and building HA systems, then it may indeed be true that it is simply out of reach for many of these customers to deploy real HA systems.The Oracle Database Appliance addresses this problem for these small and medium sized businesses. Not only is the Oracle Database Appliance hardware more cost effective, it is extremely easy to deploy (the deployment process takes about 1 hour total). The pay as you grow licensing model for software really directly addresses the high up-front cost issue. You can buy the highly available, robust Oracle Database Appliance at a fraction of the cost you would incur if you put a system of such capabilities together yourself. Not only that, you only pay for what you need in terms of software licensing. And you still enjoy the capability to scale WHEN you need more capacity, without the need to dump old hardware and migrate to a new hardware! I think, there cannot be a greater value proposition than this.The other major challenge that customers have in deploying HA systems is that they may not currently have the skills within their staff to implement high availability solutions. Again, Oracle Database Appliance addresses this problem directly. With the Database Appliance the need for local HA expertise is significantly diminished. The processes associated with the entire life cycle of the product from deployment to patching to diagnostics data collection and maintenance are all streamlined and substantially automated. Customers can deploy, operate, and manage their Database Appliance environments without deep technical skills. Further, dealing with mundane things is not necessary either and the staff can focus on more important, strategic work!What is more is that due to a standard configuration and pre-tested software and hardware, the processes associated with the deployment, management, maintenance, and diagnostics are extremely reliable and predictable. This virtually eliminates the risks typically associated with building HA systems. Now SMBs can deploy HA systems to compete in today’s world, do so at a fraction of the normal cost, and be confident that their investment can generate immediate returns. 

Today most customers want their databases and systems to be always available (always on!). No one, whether it is a customer, an employee, a partner, or anyone else, wants to deal with a down system....

Product News

Oracle Database Appliance Unplugged @ Northern California Oracle Users Group

The Oracle Database Appliance is Simple, Reliable, & Affordable.  Still skeptical about the 'reliability'? Join Sohan DeMel, Vice President, Product Strategy and Business Development, at the Northern California Oracle Users Group to demonstrate the fault-tolerance of the Oracle Database Appliance.  A recent addition to Oracle’s Engineered System category, the Oracle Database Appliance offers customers a fully integrated system of software, servers, storage and networking in a single box that delivers high availability database services for a wide range of applications. Oracle Database Appliance has fault-tolerance built-in: The hardware is fully redundant. Oracle RAC protects against server failure and database instance failure. Oracle ASM triple mirroring maintains data redundancy. Storage multi-pathing and network bonding are built-in. In this demo-based presentation, members of the audience will be invited on-stage to literally unplug the Oracle Database Appliance – pull-out power cords, pull-out network cords, pull-out server trays, and pull out disks, all while the database is processing SwingBench transactions on the big screen. When: May 31, 2012 Where: The NoCOUG Spring Conference Go to the NoCoug.org web site for more information and to RSVP to this very exciting presentation and conference!

The Oracle Database Appliance is Simple, Reliable, & Affordable.  Still skeptical about the 'reliability'? Join Sohan DeMel, Vice President, Product Strategy and Business Development, at the Northern...

Product News

Oracle Database Appliance Best Practices Webcast - May 23, 2012 10 a.m. PT / 1 p.m. ET

Simplify Database Management with Oracle Database Appliance Deployment ScenariosBusiness users increasingly demand 24x7 availability of their data while IT departments face the challenge of ensuring maximum availability while operating with limited budgets.By deploying Oracle Database Appliance organizations can benefit from a reliable system that significantly reduces the time spent on routine system administration and maintenance, lowering operational costs, and allowing IT personnel to focus on higher value activities. Using proven deployment best practices, midsize customers and enterprise departments alike can quickly integrate Oracle Database Appliance into their backup, test, development, and production environments. And since Oracle Database Appliance is based on Intel® Xeon® processors, organizations can ensure a high level of performance and scalability. Join Oracle Database Appliance experts Tammy Bednar, David Swanger, and Intel expert Fabrizio Giamello for this live Webcast and learn how to: Achieve a high quality of service at the lowest cost Reduce up-front investment in hardware and software Implement best practices across a multitude of deployment scenarios Register today and get answers to your questions live from the experts.

Simplify Database Management with Oracle Database Appliance Deployment Scenarios Business users increasingly demand 24x7 availability of their data while ITdepartments face the challenge of ensuring...

Events

What is Oracle Database Appliance?

Oracle Database Appliance is an “always on” database system. It does not have to go down if a component fails. Component failures are accounted for and the configuration is built with redundancy and single point of failures in mind. Further, it is a very simple system to deploy and operate. If you are familiar with Oracle technologies, then technically, the best way to look at the Oracle Database Appliance may be to think of it as a two node Oracle Linux RAC cluster in a single box with shared storage and networking all included in the box. It is built and configured with redundancy to achieve continuous availability in the event of component failures. It addresses all single points of failures within the system. ü Pre-built ü Pre-configured ü Pre-tested ü Pre-validated ü Pre-tuned The current software stack (as of April, 2012) consists of Oracle Linux 5.8 (with the UEK kernel), Oracle Grid Infrastructure 11.2.0.3, and Oracle Database 11.2.0.3. On your Oracle Database Appliance, you can run Oracle RAC databases, Oracle Single Instance databases, or Oracle RAC One (active – passive) databases, or a combination of these. Oracle Database Appliance is extremely simple to deploy. When you receive your appliance unit, you simply put the appliance in a computer rack, (or you can place it on a table, or in a closet), then you plug in the power and network connections to the Database Appliance and power on the Oracle Database Appliance. You then input the information for your configuration (system names, database names, database size, etc.) and for all practical purposes you just issue a single command to complete the deployment of your Oracle Database Appliance. That command is “oakcli deploy” that you issue from Linux system prompt. More on that will be covered later. The command initiates the entire process of setting up the OS, installing Oracle software, creating the initial database, and optionally setting up a cloud file system volume (a shared file system), configuring Oracle Auto Service Request, etc. as you watch the progress on your screen. The multiple weeks’ worth of effort previously required in configuring an HA database is no longer necessary! The actual deployment process in fact takes less than one hour. And at the end of that one hour you have a fully functional cluster and a fully usable database available for your application to use. Customers typically complete their deployments on the day they open the box and put the appliance in the rack. What is really interesting is the side benefit of this ease of use which results in lower chances of errors in configuration. The risks and uncertainties involved in setting up the HA system have virtually disappeared. And that means a lot for users. Now they can go ahead and buy an Oracle Database Appliance knowing that they can have a fully functional highly available database system on the day that it arrives!

Oracle Database Appliance is an “always on” database system. It does not have to go down if a component fails. Component failures are accounted for and the configuration is built with redundancy and...

Events

Oracle Database Appliance, an Introduction

Even a couple of years ago, if you were building and deploying an Oracle RAC database system, which is basically a highly available database environment, you would start with careful planning and then  assemble all the components - the servers, the storage, the networking components from various vendors, and you would connect them together. Then you would look into what you needed for the software, whether there were any compatibility and interoperability issues in your chosen stack, whether you needed firmware, operating system, clusterware, or database patches and so forth.  And after all this work, you would look into the best practices for your configuration from these different vendors to make sure that your planned configuration was going to be compliant with those best practices. All of this resulted in weeks, if not months, worth of work and cost significant money and resources. And unfortunately, there was still no real assurance that you may not have missed something. Right? The Oracle Database Appliance completely solves that problem! It attacks the complexity issue head on. It creates a huge value proposition for customers. HA is no longer complex! In the past customer shied away from HA because it was complex. It was harder to deploy HA systems. They were costly and it took a long time to fully deploy a true HA configuration. Customers did not have the expertise to deploy HA systems. Complex = Harder + Costlier + Longer At the same time the need for HA systems continued to increase rather dramatically. In today’s fast paced world, your customers do not wait for a down system to be repaired and brought up. They move on the next vendor whose system is up. High availability is not a luxury but a necessity today.Downtime = Lost Revenue + Lost ProductivityIn addition, if your systems are down frequently and you start losing customers because of this, consider the loss based on the customer lifetime value! That can be really significant.With the Oracle Database Appliance, you buy a highly available system and not try to build one. You deploy the entire system easily in 1 day instead of three months. You use it instead of constantly try to keep it up. You manage it effortlessly … and you focus on your business.

Even a couple of years ago, if you were building and deploying an Oracle RAC database system, which is basically a highly available database environment, you would start with careful planning and then...