In Addition to ORACLE Metal Support we will offer the following activities :-

1. Database Extended Support that can be divided into two parts
   1. Basic Support That includes the following activities :-
      1. 5 Days 8:00 AM – 4:00 PM Support
      2. Onsite check of the problem if required
      3. Open and follow up on Tar Requests.
      4. Install any required Batches
   2. DBA Full Support (With a limited number of Hours ) ,In addition to all the items of Basic DBA Support it includes :-
      1. 16 Hours Support from 8:00 to 12:00 7 Days every week
      2. Regular Preventive Maintenance
      3. Basic DBA Actions Support (Backup Procedures , Tuning , Storage Management , …)
2. ORACLE Applications Extended Support to be divided into two parts :-
   1. a. Basic Applications Support to includes :-
      1. 5 Days 8:00 – 4:00 Support
      2. Onsite check of the problem if required
      3. Open Tar Requests and follow up on them.
      4. Install any required Batches
   2. Applications Full Support (With a limited number of hours) that includes in addition to the Basic Applications Support the following:-
      1. 16 Hours from 8:00 AM – 12:00 PM Support 7 Days every week
      2. App’s Admin Support that includes (Add new users , change users privileges , … )
      3. Applications Consultants Telephone Support when required calculated by points
      4. One Reduced rate for any Onsite not covered consultancy Needed.
3. At a latter Stage we can start providing IAS Support , Developer Support , Case Designer Support (This will not be offered at this time ) .

Why Should Clients Go for ORACLE Support

Expert Oracle Support - Junior Oracle DBA's are the bane of Companies. ORACLE Corporation white papers suggest that more than 75% of all Oracle database outages are attributable to human error. By hiring the services of recognized Oracle DBA experts, companies avoid the potential downtime associated with human error.

 

High Availability of Oracle - With Extended DBA support you can be assured that your database is being supported by a competent professional who is thoroughly familiar with your database. With a full-time DBA, high attrition has become a major problem. Large personnel companies have noted that the average Oracle DBA can be expected to leave their current positions every four years. The most common reasons cited for leaving are boredom and the failure of the company to provide technical challenges.

 

Low Cost - With Extended DBA services, you buy only those DBA services that you require, and only at the levels you require the service. Full-time Oracle DBAs commonly cost over $50,000/year and require more than $5,000 in training per year to keep them current with the technology. Many corporations with stable Oracle databases cannot justify the costs of a full time DBA. According to Computer world Magazine, "These days, an Oracle database administrator -- any database administrator -- is worth his weight in gold".

Ensure Continuous Oracle Support - With the high attrition rate for Oracle professionals, the average time on any job is less than three years. With Extended DBA support, you are guaranteed to have a certified Oracle DBA constantly watching your databases.

No Loss of Institutional Knowledge - By using Extended DBA support, Oracle shops avoid the risk of loosing their confidential technology to competitors. Even more important, you do not need to wait for weeks while a new DBA becomes familiar with your databases.

Peace of Mind - With Extended Oracle DBA support, you can rest assured that your Oracle databases are getting the best possible care. This allows IT managers to focus on other important issues and maximize their productivity. Taken together, these are all compelling reasons to utilize professional Remote Oracle DBA support. Even the most concerned IT managers cannot guarantee that their DBA staff will always be available for an unexpected Oracle outage.

 

Remote DBA Alert Strategy

Database Server Alerts
Monitors your server with copyrighted technology to ensure that we know exactly what is happening in the Oracle database environment.

CPU Overload Alert – Monitor for high run queue values and track periods when the Oracle database server is overloaded. time when the Oracle database server experiences shortages of RAM memory.

Oracle Database Alerts
Monitor uses leading-edge technology to monitor every component of your database, and we offer the most comprehensive and sophisticated alert monitor in the world. We are proud that we detect potential problems before they cause a production outage.

Trace and Dump file Alert – We check hourly for any new Oracle trace or dump files, and e-mail the dumps directly to our support center.

Alert log message Alert - This script e-mails any important alert log messages that are found in the alert log.

Low free space in archived redo log directory Alert - If the archived redo log directory become full, our Oracle database will hang up. This alert allows the Oracle DBA to add space before the database hangs.

UNIX mount point space Alert - The script checks all datafile mount points in Oracle, including the UNIX Oracle home directory. Since most databases now use AUTOEXTEND ON, the DBA must be constantly alert for file systems that may not be able to extend. If the free space in any mount point is less than the specified threshold, an e-mail alert will be sent to the DBA.

Object cannot extend Alert - This report will alert the Oracle DBA whenever an Oracle table or index does not have room to take another extent. This alert is obsolete if you are using tablespaces with AUTOEXTEND ON, but many DBAs still keep this alert because they want to monitor the growth of the database tables and indexes.

Tablespace > 95% free Alert - This report sends an e-mail alert whenever any tablespaces contain less space than specified. Again, this alert is obsolete when using AUTOEXTEND ON, but many DBAs still want to see the available space within each tablespace.

Object > nnn extents Alert - This report is very useful for reporting tables and indexes that experience unexpected growth. Whenever a table or index exceeds the number defined, an e-mail alert will be sent to the DBA.

Hot File Reads Alert - This script reports on files whose reads are greater than (25 percent or 50 percent or 75 percent) of total reads. This code compares the individual I/O for a file from stats$filestatxs with the overall I/O for the period in stats$sysstat. When you find a hot file, you may want to place these files in the KEEP pool or stripe them across multiple disks.

Hot File Writes Alert - This script alerts you to files whose write I/Os are greater than (25 percent or 50 percent or 75 percent) of total writes. This information can help the DBA locate files that are consuming more than a normal proportion of I/O writes. You may want to place these files in the KEEP pool or stripe them across multiple disks.

Data Buffer Hit Ratio Alert - This report alerts the DBA to times when the data buffer hit ratio falls below the preset threshold. It is very useful for locating times when decision support type queries are being run, since a large number of large-table full table scans will make the data buffer hit ratio drop. This script also reports on all three data buffers, including the KEEP and RECYCLE pools, and it can be customized to report on individual pools because the KEEP pool should always have enough data blocks to cache all table rows, while the RECYCLE pool should get a very low buffer hit ratio. If the data buffer hit ratio is less than 90 percent, you may want to increase db_block_buffers, buffer_pool_keep, or buffer_pool_recycle. Also note that the Oracle8.0 version of this alert is available.

Disk Sorts Alert - If disk sorts are greater than 100/hr, you may want to increase sort_area_size or tune SQL to perform index scans. This report is very useful for monitoring the amount of activity against the TEMP tablespace, and it is also useful for ensuring that sort_area_size is set to an optimal level. As a general rule, increasing sort_area_size will reduce the number of disk sorts, but huge sorts will always need to be performed on disk in the TEMP tablespace.

I/O Wait Alert - This code interrogates to report on any files with an excessive amount of wait activity. If the number of I/O waits appears excessive, the DBA needs to investigate the cause of the waits. High I/O waits on files are commonly associated with buffer busy waits, and may be caused by tables with too few freelists.

Buffer Busy Wait Alert - Whenever you see buffer busy waits, you have a condition where a data block is in the data buffer but is unavailable. This type of contention is usually for a segment header block of a high-level index node block. Adding freelists for the object often corrects these wait conditions.

Redo Log Space Requests Alert - If redo log space requests are greater than 0, you may want to increase the log_buffer init.ora parameter. A high number of redo log space requests indicates a high level of update activity, and the Oracle log buffer is having trouble keeping up with the volume of redo log images.

Chained Row Alert - Table fetch continued rows greater than 10,000/hr you may have row chaining because of PCTFREE set too low. The table fetch continued row can also be triggered by reading data blocks with long columns that exceed the block size. This is common with rows that contain RAW, LONG RAW, NCLOB, CLOB or BLOB datatypes.

Shared Pool Contention Alert - Enqueue deadlocks can indicate contention within the shared pool and locking related problems. Enqueue deadlocks are associated with the deadly embrace condition where one task is locking resources and another task that is holding resources requests a lock on the resources of the first task. To prevent these tasks from waiting forever, Oracle aborts the tasks that requested the lock that caused the deadly embrace.

Full Table Scan Alert - Long-table full table scans are only legitimate when the query requires access to more than 40percent of ordered table rows and more than 7percent of unordered table rows. Excessive large-table full table scans may indicate poorly tuned SQL that is not using an index.

Background Wait Alert - This query interrogates Oracle to find events with high waits. When background events experience more than 100 time-outs/hr, you may have a locking problem.

System Waits Alert - This query interrogates the Oracle event structures to locate events where there are excessive waits. If you experience waits on latch free, enqueue, LGWR waits, or buffer busy waits, you need to locate the cause of the contention.

Library Cache Misses Alert - This query interrogates Oracle to look for excessive library cache miss ratios. When the library cache miss ratio is greater than .02, you may want to increase shared_pool_size.

Database Writer Contention alert - This query looks at Oracle for values in summed dirty queue length, write requests, and DBWR checkpoints. When the write request length is greater than 3 or your DBWR checkpoint waits, you need to look at tuning the database writer processes.

Data Dictionary Miss Ratio Alert - This query looks at the Oracle data dictionary to compute data dictionary gets, data dictionary cache misses, and the data dictionary hit ratio. This script alerts the DBA to times when requests for data dictionary metadata are high. This problem can sometimes be relieved by increasing the shared_pool_size init.ora parameter.

Data Dictionary Object Alert - This report looks into Oracle to find individual objects that experience a row hit ratio. This report can reveal internal contention with the Oracle data dictionary and times of high dictionary metadata requests.

 

Remote DBA Automation Strategy

We will use Sophisticated set of proprietary scripts that will completely automate Oracle reporting, capacity planning and pre-outage alerts. By addressing the conditions that cause an outage before your database crashes, the probability of a databases outage is dramatically reduced. Our monitor software falls into several areas:

Tuning Reports – We will use new Oracle monitoring techniques that are not available anywhere else to perform proactive tuning for the Oracle database. Our reports identify I/O problems at the object level and automatically perform caching operations. In addition, our DBAs are alerted to potentially serious performance problems such as missing indexes.

Trend Reports - The trend reports are used to establish the baseline signature for the database. From this signature, exception reports will identify abnormal conditions. Trend reports are created for all major areas of the Oracle database including I/O, memory usage, CPU consumption and Oracle internal metrics.

 

Exception Reports - Our exception reports are e-mailed to the in-house manager daily. These reports show all times when the database is experiencing stress. Our reports go beyond ordinary Oracle monitoring and monitor the processing environment, reporting on CPU and RAM-related problems.

Capacity Planning Reports - These reports provide the in-house manager all of the the summary information from the prior weeks activity. Weekly statistics reports show the total growth for the week and show all object activity within Oracle.

Automated Oracle Alerts - These reports trigger a page to the on-call DBA for immediate resolution. The alerts warn the on-call DBA whenever a pending problem may cripple the database.