An Architect's vision

From 11gR2 onward Oracle added Cross platform Data Guard creation feature. In that case, we can set up Cross Platform Data Guard with Solaris as Source and Linux as Target. Later we can bring up Target DB and decommission Source DB.

1. If the DB is small but very busy (that's why lots of transaction logs will be created) , we can create the standby DB itself instead of applying all pending archivelogs. 2. If DB is big, use RMAN increamental backup option.

1. If the DB is small but very busy (that's why lots of transaction logs will be created) , we can create the standby DB itself instead of applying all pending archivelogs. 2. If DB is big, use RMAN increamental backup option.

1. If the DB is small but very busy (that's why lots of transaction logs will be created) , we can create the standby DB itself instead of applying all pending archivelogs. 2. If DB is big, use RMAN increamental backup option.

1. If the DB is small but very busy (that's why lots of transaction logs will be created) , we can create the standby DB itself instead of applying all pending archivelogs. 2. If DB is big, use RMAN increamental backup option.

A standby database automatically applies redo logs when they arrive from the primary database.  But in some cases, we want to create a time lag between the archiving of a redo log at the primary site, and the application of the log at the standby site. Modify the LOG_ARCHIVE_DEST_n initialization parameter on the primary database to set a delay for the standby database. The following is an example of how to add a 1-hour delay: SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=stdby_srvc DELAY=60'; The DELAY attribute is expressed in minutes. The archived redo logs are still automatically copied from the primary site to the standby site, but the logs are not immediately applied to the standby database. The logs are applied when the specified time interval expires. 

SQL> SELECT * FROM ( 2 SELECT sequence#, archived, applied, 3 TO_CHAR(completion_time, 'RRRR/MM/DD HH24:MI') AS completed 4 FROM sys.v$archived_log 5 ORDER BY sequence# DESC) 6 WHERE ROWNUM <= 10 7 / SEQUENCE# ARCHIVED APPLIED COMPLETED ---------- -------- ------- ---------------- 11211 YES NO 2004/09/16 09:30 11210 YES YES 2004/09/16 09:00 11209 YES YES 2004/09/16 08:30 11208 YES YES 2004/09/16 08:00 11207 YES YES 2004/09/16 07:30 11206 YES YES 2004/09/16 07:00 11205 YES YES 2004/09/16 06:30 11204 YES YES 2004/09/16 06:30 11203 YES YES 2004/09/16 06:30 11202 YES YES 2004/09/16 06:00 10 rows selected.

Standby databases can remain open while doing recovery Heterogeneous platform support (standby can be on a different platform). For example, production on Linux and standby on Windows . 

Maximum Availability Maximum Performance Maximum Protection AFFIRM NOAFFIRM AFFIRM SYNC ASYNC SYNC DB_UNIQUE_NAME DB_UNIQUE_NAME DB_UNIQUE_NAME

There are three different types of data guards 1. Maximum Availability 2. Maximum Performance 3. Maximum Protection Maximum Availability This protection mode provides the highest level of data protection that is possible without compromising the availability of a primary database.  Transactions do not commit until all redo data needed to recover those transactions has been written to the online redo log   (not all - that's the catch) and to at least one synchronized standby database.   If the primary database cannot write its redo stream to at least one synchronized standby database, it operates as if it were in maximum performance mode to preserve primary database availability until it is again able to write its redo stream to a synchronized standby database. This mode ensures that no data loss will occur if the primary database fails , but only if a second fault does not prevent a complete set of redo data from being sent from the primary databa

 YES RMAN and Oracle Net in Real Application Clusters In any RMAN connection made through a net service name, each net service name must specify one and only one instance. This rule applies to all RMAN connections whether they are made from the command line or through the CONNECT clause in ALLOCATE CHANNEL or CONFIGURE CHANNEL commands. Therefore, you cannot specify a net service name that uses Oracle Net features to distribute RMAN connections to more than one instance. Channel Connections to Cluster Instances When making backups in a Real Application Clusters configuration, each allocated channel can connect to a different instance in the cluster, and each channel connection must resolve to one and only one instance. For example, configure automatic channels as follows: CONFIGURE DEFAULT DEVICE TYPE TO sbt; CONFIGURE DEVICE TYPE sbt PARALLELISM 3; CONFIGURE CHANNEL 1 DEVICE TYPE sbt CONNECT = 'SYS/oracle@node1'; CONFIGURE CHANNEL 2 DEVICE TYPE sbt

Wait Information  is NULL because “CPU time” is actually not really a wait event. It's actually the time spent on CPU to do the actual work. Explanation: Let say Times = 1000 Total CPU = 4 Total CPU Time = 4 x 60 x 60 = 14400 Percentage of Total CPU Time = (1000/14400) x 100 = 6.94% Analysis Hence it is well within limit

With a large majority of expenses going to manage the existing IT applications, The transparency of the current inventory of applications and resource consumption is a primary goal of Application Portfolio Management. This enables firms to: 1) Identify and eliminate partially and wholly redundant applications, 2) Quantify the condition of applications in terms of stability, quality, and maintainability, 3) Quantify the business value / impact of applications and the relative importance of each application to the business, 4) Allocate resources according to the applications' condition and importance in the context of business priorities.

Wikipedia definition IT Application Portfolio Management ( APM ) is a practice that has emerged in mid to large size Information Technology (IT) organizations since the mid-1990s. Application Portfolio Management attempts to use the lessons of financial portfolio management to justify and measure the financial benefits of each application in comparison to the costs of the application's maintenance and operations. Extracted from Tech Target post Application portfolio management (APM) is a framework for managing enterprise IT software applications and software-based services. APM provides managers with an inventory of the company's software applications and metrics to illustrate the business benefits of each application . "[APM] is really about implementing a repeatable process to assess what we have, and, if an application is not performing or does not meet our architectural requirements, eliminating it and replacing it with a better perfor

Once you configure CloudFront to deliver your content, here's what happens when users request your objects: A user accesses your website or application and requests one or more objects, such as an image file and an HTML file. CloudFront determines which edge location can best serve the user's request, typically the nearest CloudFront edge location in terms of latency, and routes the request to that edge location. In the edge location, CloudFront checks its cache for the requested files. If the files are in the cache, CloudFront returns them to the user. If the files are  not  in the cache, it does the following: CloudFront compares the request with the specifications in your distribution and forwards the request for the files to the applicable origin server for the corresponding file type—for example, to your Amazon S3 bucket for image files and to your HTTP server for the HTML files. The origin servers send the files back to the CloudFront edge location.

We can follow these simple steps Take a snapshot of the root device volume Create a new volume from the snapshot Then Switch the volumes It accomplishes the desired goal. 

The Snapshot Amazon gives you of an EBS volume just stores it in 'S3' not your own s3 bucket,  so you do not have to concern yourself about this, AWS take care of that, they store the snapshots in S3. 

New  Amazon CloudWatch  metrics to provide you with more insight into the state of your back-end instances and applications.   ·    Backend Connection Errors:   the number of errors encountered by the load balancer while attempting to connect to your application. ·    Surge Queue Length:   the number of requests queued by the load balancer, awaiting a back-end instance to accept connections and process the request. ·    Spillovers:   the number of rejected requests due to a full surge queue.