Tag: IOUG

In this session, you will learn about the inner workings and features of the latest generation of Oracle RAC and how they can improve database deployments on generic systems as well as Oracle’s Engineered Systems. You will see, how those improvements can be used to provide better scalability, ensure higher availability and simplify the management…

As a DBA tasked with protecting your databases, you understand that backup and recovery success is a critical, yet often time consuming process.  But, did you know that there are tools available today to enable you not only to fine-tune your RMAN processes but also give you purview into the underlying infrastructre?   And, did…

With data growth abounding, database administrators are constantly challenged to support business-critical data protection requirements. Oracle Recovery Manager has continuously evolved over the past 15 years, with each release offering richer functionality and integration with Oracle' high-availability products to address those requirements. Attend this Oracle Recovery Manager technical session to learn about next-generation backup and…

Take a detailed look at key features of the Amazon Relational Database Service (RDS) from the team that builds it. We will provide an overview of Amazon RDS and then take a deep look at a few key features for DBAs.

For the past couple of years, Big Data along with Cloud has become the go to buzz-word in technology circles. Some of us have managed many Terabytes of data in Oracle databases with great success so you may be asking what’s the big deal with Big Data? Big Data is bringing on a fundamental shift…

Diagnosing and resolving Oracle RAC database problems has required extensive knowledge not only of database internals but networking, storage and O/S interactions. Frequently, these issues needed to be escalated to Oracle Support Services delaying their resolution. New in Oracle Database 12c / Rel. 2 is the Cluster Health Advisor that continuously analyses database ASH/AWR data…

Oracle Database 12c is designed for the cloud. With its unique Multitenant architecture you can reduce both capital and operating expenses and increase agility, and it’s easy to adopt and use. Attend this hands-on lab to experience the exciting capabilities of Oracle Multitenant for yourself.

Missed Oracle OpenWorld? then this a catch-up session for DBAs and Oracle Technologists on what are Oracle's Infrastructure as a Service offerings and how they are applicable to your job role, someone on your team,or within your company.

Do you want to migrate big database to the cloud or to a different data center with minimum downtime? That is your answer, use 12c database RMAN new features. Different OS platform? Want a version upgrade at the same time, - no problem.  Minimize downtime applying incremental backups. Use compressed backup sets or  storage split…

Success of an application depends on its performance and its cost of maintenance. Interestingly both of these factors are largely influenced by the simplicity of the algorithm and it is also important to choose the right application layer for executing this algorithm. Often accessing and processing “data” plays the pivotal role in an application’s performance.  So we can say that writing simpler data access and process algorithm we can make an application faster and scalable. Needless to say that the application should also be free from contention and locks at runtime.

Here is an architecture to apply these principals in a traditional system built with Oracle and Java.

Lets talk about accessing data – Oracle provides one of the fastest way to access data. So as a principle we will always depend on Oracle technology for accessing data. We will use simple SQL, well-designed table, pinpointed index and partition to access this data in a very fast manner.  We will not write complicated SQL which may give inefficient and complex plan which will always be slower. We will segregate data from processing so that complexity of processing doesn’t make data access complex. A complex data access is a very slow process.

Lets talk about processing data – Java (or a comparative Language) is a very fast processing engine because they entirely work in memory. It can be multi-threaded to use all cores of the server. It provides functional and object oriented paradigm to write complicated algorithm in a simple way. In-memory (soft) data structures can be built to suit the exact need of your algorithm so that finding data will be fast. This will be harder to achieve in a hard data structure like database index. So as a principle we will push execution of algorithm into Java.

Lets talk about contention and locks – Adopt immutability to protect the application from locks. Find a natural boundary/partition of data, which can be processed independently from each other. The more granular this partition is the faster your application will be. With immutable code, an in-memory process can be largely free from any contentions and locks. Whereas data access can not be as contention free because logically granular data may be sharing the same disk location and hence bottlenecked due to things like hot blocks, segment contention etc. So to build a contention free application we will prefer Java (or a comparative language) over a complicated SQL.

A real life application built on these principles yielded 10 times better performance as compared to a system built using complicated SQL.