We identify five stages in the journey to the cloud. Most customers today are still mostly siloed, or in the process of standardizing their environment. Standardization is actually very important, and many of the benefits of moving to the cloud come from this phase. We want to encourage customers to standardize as much as possible, and particularly standardize on Oracle. We provide a single architecture that can help a customer move through the cloud stages with simple configuration changes and minimal disruption. Each phase delivers value of the customer, and needs to be messaged according to the customer value it delivers. Each phase also provides an opportunity to upsell new products. In the consolidation phase the key focus is on cost savings, and reducing floorspace. It is possible to consolidate using EE, but in this phase we want to encourage standardizing on RAC or even better our engineered systems, We also have an opportunity to uspell security and management options. In the service delivery phase we shift the focus to agility, rapid provisioning and the ability to rapidly respond to changes in business requirements. Things like self-service provisioning, metering and chargeback also become important. In the final cloud delivery phase, the focus shifts to enabling location independence and integrating the private cloud with other clouds. Here we have an opportunity to upsell products and services for integration.
Let me explain more what I mean by “engineered to work together”. Again each of these layers—and all the products within the layers—have been designed and engineered using open standards. Oracle tests everything within a stack layer and across stack layers, from applications all the way down to the servers and storage. Oracle then certifies all these different combinations so that customers know which particular versions of software are designed to work together and we manage and support them all together. But it’s more than just certification. Because this is one development organization – they are actually developing these components in concert with one another. (examples: Every night when a software team drops their code, there is integration and regression testing with the hardware systems. If the database team is working on a new patch, it’s also going through regression testing with the OS, the virtualization and the servers and storage. And then with the core infrastructure (the HW, OS and Virtualization) and with our Engineered Systems, we’re actually taking this even further. This when we don’t just certify across layers of the stack, but it’s actually pre-integrated and productized as a single system which is deployed, upgraded and supported as a single system. (We’ll cover more on ES later) Oracle makes it easier to deploy them together, and they are designed to be easily upgraded together. And, the entire stack can be managed together, and supported together. -------- When we say that Oracle hardware and software is engineered to work together, this refers to our unique ability to offer customers a complete hardware and software stack, from applications through middleware and databases, and all the way down into servers and storage. Each of these layers—and all the products within the layers—have been designed and engineered to work together according to open standards. Oracle tests everything within a stack layer together– for example, between different applications, between different middleware suites, between various database products, and so on. Oracle also tests everything across stack layers, from applications all the way down to the servers and storage. So, applications are tested with middleware, middleware is tested with the database, the database is tested with the hardware … every layer is tested with every other layer. Oracle certifies the complete stack so that customers know which particular versions of software are designed to work together. For example, every major application that Oracle delivers, including Oracle E-Business Suite, PeopleSoft Enterprise, JD Edwards and Siebel CRM is certified with Oracle Fusion Middleware 11g . Database 11g Release 2 has been tested and certified with all of Oracle’s major applications, including Oracle Fusion Applications. Oracle packages our different technologies into standardized solutions, which customers can then deploy together. These complete solutions are designed to be upgraded effectively and efficiently together. And, the entire stack can be managed together, supported together and so on.
In 126.96.36.199 -&gt; only Exadata target -&gt; 1389592.1 - Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backups Minimize read-only impact with multiple incremental backups Successive incrementals converted & applied to restored data files Final incremental while tablespace in read-only mode, with separate Data Pump metadata export and import To create the backup set containing data that must be transported to the destination database, use the BACKUP command on the source database. To indicate that you are creating a cross-platform backup, the BACKUP command must contain either the FOR TRANSPORT or TO PLATFORM clause. When you use FOR TRANSPORT, the backup set that is created can be transported to any destination database. If the destination database uses an endian format that is different from that of the source database, the endian format conversion is performed on the destination database. When you use TO PLATFORM, the endian format conversion is performed on the source database. If you specify a target platform by using TO PLATFORM, the platform must be a supported platform. In the source database, use the DATAPUMP clause of the BACKUP command to create the metadata required to plug tablespaces into the target database. The metadata is stored in a Data Pump export dump file as a separate backup set. This backup set can be used in conjunction with the tablespace backup set to plug the transported tablespaces into the target database.