Blog Aggregator - Amardeep Sidhu

Now that we have a general understanding of some of the features that 10G Data Pump provides, let’s peel back a few of the layers and see how this utility works. In this blog, we’ll take an in-depth look at the Data Pump architecture.

One of the tasks I’ve recently been given is to collate information about our Oracle and SQLServer databases. Stuff like sizes, init.ora parameters &c. I’ve developed a script that gets a lot of the stuff we need out of Oracle.

Here it is:set echo off
set verify off
set feedback off
set linesize 132
set pagesize 60
set heading off
/* This script must be run as SYS (SYSDBA) */

Prompt “Audit

Finally got a response from Oracle, turned out they had put it with their US office who don’t start work until 13:00 our time.

The eventual response was:23-MAY-06 14:49:43 GMT

DATA COLLECTED
===============
On alert.log we can see some:
ORA-07445: exception encountered: core dump [00000001009B0B04] [SIGSEGV] [Address not mapped to obj
ect] [0×000000000] [] []

Trace file uploaded shows:
/opt/

Describing the Oracle Export and Import utilities as slow is like saying the Titanic sprung a small leak. Stories of Export and Import executions running for hours (and sometime days) are commonplace. Oracle 10G provides a new data movement utility, called Data Pump, to increase the performance of data transfers.

Now that I’ve used Data Pump, I found out that the improvements go far beyond mere performance enhancements. In part 1 of this multi-part series on the Data Pump toolsets, I’ll cover some of the new features and functionalities the utility provides. In upcoming blogs, we’ll take a look at the data pump architecture and compare the toolset to its ancestors Export and Import.

Late yesterday one of our projects passed me information abvout an ORA-07445 error they’d had earlier in the day, apparently this is stopping one of the modules in their application to stop working. Why they couldn’t have told me about it earlier I don’t know, I would have had time to raise a Service Request with Oracle during our maintenence hours (the why we don’t have 24×7 cover is a rant for

Correctly sizing online redo log files is critical if you want to achieve ‘maximus database performis’. 10G Grid Control provides a redo log file sizing advisor that provides administrators with an initial sizing recommendation. I’ll begin this blog by showing you how to use the automatic sizing advisor and continue our discussion by explaining the manual process of determining the size of your online redo logs.

Although I provided a quick demo on how to use 10G Grid Control’s SQL Access Advisor in an earlier blog, I think it may be beneficial for us to take a more in-depth look at this powerful utility. We’ll peel back the covers to find out what the SQL Access Advisor actually does when you activate it as well as the benefits it provides. I think you will find that the SQL Access Advisor is a strong analysis tool that deserves your consideration.

In a few of my previous blogs, I provided instructions on how to use 10G Grid Control to run the SQL Tuning Advisor and the SQL Access Advisor. In this next couple of blogs, we’ll peel back the layers and find out exactly what happens when these utilities are executed.

In part one of this multi-part blog on the advisors, we take a look at how the SQL Tuning Advisor uses the optimizer to generate its tuning recommendations. We’ll also cover the types of recommendations it provides and how it comes to those conclusions.