This is default featured slide 1 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions..

This is default featured slide 2 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions..

This is default featured slide 3 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions..

This is default featured slide 4 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions..

This is default featured slide 5 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions..

 

Friday, June 6, 2008

Sharing Memory - Automatically

It used to be a challenge to size the various memory pools that comprise the Oracle System Global Area (SGA) for optimal performance. But that was before Oracle Database 10g. First introduced in Oracle Database 10g and further enhanced in Oracle Database 10g Release 2, Automatic Shared Memory Management (ASMM) automatically sizes many of the memory pools while the database is running, allocating and de-allocating memory as needed. As the workload composition changes, Oracle Database 10g enlarges the appropriate pools and reduces the sizes of other automatically sized pools accordingly. In short, ASMM can save a lot of trouble - and improve overall performance as well.

More information : http://www.oracle.com/technology/oramag/oracle/05-sep/o55tuning.html

Understanding Shared Pool Memory Structures: Tips on How to Optimize Usage and Avoid Errors

The Oracle shared pool provides critical services for sharing of complex objects among large numbers of users. Prior to 10g R1, DBAs often spent much time learning about the shared pool memory management to configure and tune shared pool usage; with the tight time constraints and ever-changing workloads, many found this task daunting. The Automatic Shared Memory Management (ASMM) features introduced in 10gR1 solved this problem by providing the DBA a simple, automatic self-tuning mechanism for configuring shared memory components of the SGA, including the buffer cache and shared pool. The Automatic Database Diagnostic Monitor (also introduced in 10gR1) further simplified shared pool related tuning efforts by providing automatic diagnosis and recommendations for application specific issues.

More information : http://download.oracle.com/oowsf2005/003wp.pdf

Thursday, June 5, 2008

Tuning Oracle on Windows for Maximum Performance on PowerEdge Servers

Tuning is the art and science of modifying and reconfiguring your system in order to achieve better performance. Tuning and sizing are closely related, in that tuning hardware might require the addition of more hardware. Tuning is done on a live system that is in use or in test, whereas sizing is a theoretical exercise that is done without actually modifying the system. This paper covers some of the general Oracle tuning practices as well as specific tuning for the Windows platform.

More Information : http://www.dell.com/downloads/global/solutions/Oracle%20on%20Windows%20Tuning.pdf

Get More from Your Oracle Database: Best Practice Performance Management for Real Results

DBAs are constantly challenged to increase database performance while keeping costs down. This short paper discusses Resource Mapping Methodology (RMM) which defines a systematic process for performing Wait-Event analysis to optimize database performance. It includes a brief overview of Ignite for Oracle and the business benefits that Ignite users have demonstrated.

More information : http://www.confio.com/English/Downloads/Articles/GetMoreOracleDatabase_WP.pdf

An Oracle Technology Brief: The Oracle Database and Storage

Given the intimate relationship between the Oracle Database and the storage it resides on it is important to ensure the interface between the two is efficient and robust. This is why Oracle and the storage vendors have invested so much in the interface and interrelationship of database and storage. There is a stack of storage management software, programs, and practices available for the Oracle database. All of the components in the stack are highly tuned and optimized for use with the Oracle database. They are the most performant, scalable, reliable, easy to use, and inexpensive way of using storage with the Oracle database.

See more information http://www.oracle.com/technology/deploy/availability/pdf/1121_Weiss_Grancher_WP.pdf

Oracle in a Nutshell: Performance

Achieving optimal performance from the Oracle database is an art, not a science. Using the appropriate data structures, ensuring that there are adequate resources available, and leveraging the features of the Oracle database can help to avoid bottlenecks that reduce the performance of the system. This paper provides an overview of some of the tools within an Oracle database that will help one understand how Oracle optimizes performance for its operations.

More information: http://oreilly.com/catalog/oracleian/chapter/ch17.pdf

Self-Tuning Oracle9i Database: Oracle SGA

As DBAs become more sophisticated in their self-tuning endeavors, many Oracle metrics may become self-tuning. In Oracle Database 10g, more self-tuning capability will be seen than ever before. For example, the dynamic memory allocation features of Oracle Database 10g make it possible to create a self-tuning Oracle SGA. By means of demonstration, in this paper the author will explain how to examine the Oracle instance in Oracle 9i Database and adjust the memory regions for sort_area_size or pga_aggregate_target, large_pool_size, sga_max_size and db_cache_size according to the processing demands on the server and within the database. The techniques discussed are based on the use of Statspack to monitor memory regions over time and develop signatures of system resource usage.

More information on http://www.dba-oracle.com/art_otn_auto_tuning_10g.htm

Understanding Optimization

Improvements in the Oracle Database 10g Optimizer make it even more valuable for tuning.

In Oracle Database 10g, the cost-based optimizer (CBO) has two modes—the normal mode and a tuning mode that is invoked by the SQL Tuning Advisor (and many other Oracle Database 10g advisors, such as the SQL Access Advisor). The SQL Tuning Advisor is a great new tool for DBAs in Oracle Database 10g. Specifically, in previous releases of Oracle, if you weren't happy with the plan created by the optimizer, you could hint your code to influence the optimizer's decision, but figuring that out is time-consuming at best. And even if you had the time to do all the analysis necessary to figure out the best execution plan, you can't touch the SQL generated by packaged applications—or any other application for which you didn't have access to the source code.

More information : http://www.oracle.com/technology/oramag/oracle/05-jan/o15tech_tuning.html

Wednesday, May 28, 2008

Secrets for optimizing Oracle table inserts

When loading large-volumes of data, you have several choices:

1 - Tune INSERTS - Parallelized programs doing concurrent INSERT statements

2 - Tune SQL*Loader - Using sqlldr Direct Load, and adjusting parameters improves INSERT performance.

3 - Tune imports - Use Oracle Data Pump (Formally Oracle import utility) - Here are tips for hypercharging Oracle import.

Optimizing Oracle INSERT performance

When using standard SQL statements to load Oracle data tables, there are several tuning approaches:

a - Manage segment header contention for parallel inserts - Make sure to define multiple freelist (or freelist groups) to remove contention for the table header. Multiple freelists add additional segment header blocks, removing the bottleneck. You can also use Automatic Segment Space Management (bitmap freelists) to support parallel DML, but ASSM has some limitations.

Read more about secrets for optimizing Oracle table inserts here:
http://oracle-tips.c.topica.com/maalfseabGRCBcilq9pb/

Oracle Business Intelligence (BI) Software Benefits and Challenges

Oracle BI Suite EE Plus represents significant opportunities and challenges for Oracle E-Business Suite (EBS) customers. Using automated conversion tools and services, there is now a cost-effective method of migrating that minimizes downtime and maximizes the benefits your organization receives from Oracle's next generation BI platform.

Attend this Webcast to learn about successful strategies for using Oracle BI Suite EE Plus with the E-Business Suite to provide real-time access to transaction data for operational reporting. Explore specific topics, including:

* Benefits of Oracle BI Suite EE Plus.
* Challenges of integrating Oracle BI Suite EE Plus with Oracle EBS.
* Provide an instant self-service reporting environment.
* How to reduce the time, cost, and risks during migration.

Get this white paper at: http://searchoracle.bitpipe.com/data/document.do?res_id=1204913038_975

Utility Computing Made Simple: Automated Provisioning and Patching Solutions for Oracle Grid Computing

Utility computing is all about enabling system resources, including the grid, server farm, and clustering, to be acquired for different types of applications.

Many enterprises are adopting grid and utility computing technologies because of their benefits. This document discusses the growth of enterprise computing.

Oracle Enterprise Manager provides these benefits:

* Centralized control for software lifecycle, from deploying to uninstalling the software
* Out-of-the-box best practices for patching and rolling out software
* Reduction in human error because of minimal human involvement in the patching and provisioning processes
* Incorporation of all the best practices in patching and provisioning procedures from Oracle's experience in the field
* Accelerated service delivery time


Download here: Utility Computing Made Simple: Automated Provisioning and Patching Solutions for Oracle Grid Computing

Master Data Management

If Master data management (MDM) is defined as the processes and tools which centrally and persistently define non-transactional entities of an organization, then its execution requires consideration of many moving parts. There is the data itself, data governance, business rules, data storage and implementation. This white paper provides independent insight and guidance as to which approach might work best for your organization.

Download here: Master Data Managementw

Monitor Oracle Application Health and Performance with Middleware

Organizations are finding limitations in orchestrating processes across ERP, SCM and CRM applications. Business and IT leaders deploy middleware with a sharp eye on the health and performance of key business applications.

Learn how you can narrow your short list significantly with a more strategic approach to IT portfolio management and application synergies. By considering the potential business benefits and teaming middleware with familiar applications, you can move to new levels of performance and response without making huge investments.

Download here: Monitor Oracle Application Health and Performance with Middleware

Sunday, May 25, 2008

Transactional Data Management for Eliminating Database Downtime When Upgrading or Migrating from Oracle 8i or 9i to Oracle 10g

Oracle 8i and 9i database customers are facing more urgency to upgrade to Oracle 10g or higher, particularly where more business-critical applications are supported. In many cases, cross-platform migrations may also need to occur along with the database upgrade. Despite this necessary IT project, users expect uninterrupted availability and/or SLAs (service level agreements) dictate uptime requirements. Therefore any outage, even if scheduled or "planned", has a negative impact on the business.

Learn about a practical, proven solution that tackles the challenge of upgrading or migrating to Oracle database version 10g without taking database downtime. Learn how you can successfully upgrade or migrate to Oracle 10g as well as:

* Achieve rolling upgrade or migration.
* Keep transactions in synch across the databases.
* Manage partial or phased migrations or upgrades.
* Conduct data verification post-upgrade or migration.
* Implement easy and reliable failover strategy.



Get this white paper at: http://searchoracle.bitpipe.com/data/document.do?res_id=1139491378_804

Thursday, May 22, 2008

How to Create Oracle Database Manually

CREATING THE DATABASE MANUALLY

This method involves typing the create database statement within SQL*DBA.
Using this method allows for more flexibility such as specifying
the MAXDATAFILES parameter or specifying multiple SYSTEM tablespace
database files. However by doing this manually there is also a greater
possibility of syntax errors. In addition there is no logfile automatically
created to record the options which have been specified.

Steps for Method I:

1. Set unix environment (SEE SETTING UNIX EVIRONMENT SECTION ABOVE).

2. Create a new init.ora for your new database by copying the default
one provided by Oracle:

% cp $ORACLE_HOME/dbs/init.ora $ORACLE_HOME/dbs/initNEW_NAME.ora

3. Change db_name parameter in the new initNEW_NAME.ora from DEFAULT to
the new database name.

4. Startup sql*dba in line mode:

sqldba lmode=y

5. Connect to the instance, and startup in a 'NOMOUNT' state:

SQLDBA> connect internal
Connected.
SQLDBA> startup nomount
ORACLE instance started.
SQLDBA>

6. Refer to the SQL Language Reference Guide for the 'CREATE DATABASE'
statement syntax - page 4-148.

Here is a sample create database statement:

SQLDBA> create database NEW_NAME
2> logfile group 1 ('oracle_home/dbs/log1NEW_NAME.dbf') size 500K,
3> group 2 ('oracle_home/dbs/log2NEW_NAME.dbf') size 500K
4> datafile 'oracle_home/dbs/dbsNEW_NAME.dbf' size 20M
5> maxdatafiles 50;

7. Once completed run catalog.sql located in the oracle_home/rdbms/admin
directory. This script must be run under the 'SYS' user or connected
'internal'.

NOTE: catproc.sql must also be run if you have the procedural option
installed.

SQLDBA>@oracle_home/rdbms/admin/catalog.sql
SQLDBA>@oracle_home/rdbms/admin/catproc.sql

8. After the database has been created, the SYSTEM tablespace and SYSTEM
rollback segment will exist. However, a second rollback segment in the
SYSTEM tablespace must be created and activated before any other
tablespaces can be created in the database (Refer to SQL Lanuguage
Reference Manual for full syntax).

Creating the rollback segment:

SYNTAX: CREATE ROLLBACK SEGMENT system2
TABLESPACE SYSTEM
STORAGE (...);

Activating the rollback segment:

SYNTAX: ALTER ROLLBACK SEGMENT system2 ONLINE;

9. Modify the /etc/oratab file by adding the new database name. This
is used by dbstart to startup all databases with a 'Y' entry in this
file. (See page 4-17 of Oracle for Unix technical Reference Guide).


Source:http://www.fors.com/orasupp/unix/13481_1.HTM