Oracle Instance Vs Oracle Database


Oracle Instance Vs Oracle Database

Today we will see the basic terms regarding the oracle database i.e. Oracle Instance, Oracle Database and Oracle Server. Many peoples are always having confusion between Oracle Instance, Oracle Database and Oracle Server. Below is the simple description for all these three terms.

1. Oracle Instance:-

Oracle instance is combination of memory structures and background processes.
When Oracle instance is started, System Global Area(SGA) is allocated and background processes are started.
Instance can open and use only one database at a time.
We can not access data from database without starting up oracle instance.


2. Oracle Database:-

Oracle database consist operating system files known as database files which provides actual storage information. Oracle database has physical and logical structure. An oracle database consist of three types of files

Data Files: These files contains actual data in the database.
Redo Files: These files contains changes made to the data in the database. This information requires for database recovery in case of instance failure.
Control Files: These files contains information which is necessary to maintain and integrity of database.


3. Oracle Server:-

Oracle server is combination of Oracle Instance and Oracle Database.

WHY TO UPGRADE ON ORACLE DATABASE 12C


As you know Oracle Database 12c is by far the most important Oracle release in the last 10 years due to various new freatures. Its advanced capabilities promote better performance, increased scalability, and easier data management. For the enterprise, this translates into significant cost savings, reduced risk, and increased flexibility.

Find the top five features which i like and prefer for make upgrading worthwhile. While there are many good reasons to move to Oracle Database 12c, depending on your business goals and strategies, these are the most broadly applicable to both large and small organizations.

1. Consolidate your data infrastructure with pluggable databases

One of the main challenges in database management is achieving the cost benefits associated with running multiple databases on the same server or cluster without sacrificing access, growth, and optimization of each database.

Prior to Oracle Database 12c, companies had three choices for Oracle database consolidation: schema-level, database-level, and virtual server-level. Schema-level consolidation offers the best use of resources, particularly heavily-contended-for memory, by eliminating redundant shared pool areas and by sharing a common buffer cache. But many applications cannot co-exist with applications in other schemas. Database and server-level consolidation permit some hardware savings, but sharing fewer resources means fewer benefits.

Oracle Database 12c pluggable database feature allows you to reduce costs by consolidating multiple databases and isolating applications while still sharing the same memory structures. You can also move the databases that you consolidated between servers easily. If one of those databases grows more than expected, performance doesn’t need to suffer on all databases—just move the “problem” one. You never know how your customers will grow, and pluggable databases deliver the benefits of virtualization, like increased flexibility and scalability, without the overhead. Pluggable databases also make it much easier to upgrade to Oracle Database 12c and with less risk.

2. Simplify information lifecycle management with data tiering

The value of data changes over time. A purchase completed today, for example, may need to be easily accessed in near real-time, because it impacts other parts of the business. A purchase made in 2008, however, is more interesting from a statistical perspective and can be part of batch reporting.
Oracle Database 12c offers a data-tiering feature, which moves data to different types of storage based on its usage. These rules can be applied as you define your database. Data that doesn’t need to be accessed frequently, for example, can be compressed and then moved to slower storage. The ability to dynamically classify and move data simplifies information management, saves money on storage, and improves performance.

3. Increase performance across globally distributed databases with

Before Oracle Database 12c, global load balancing was delivered through external hardware or software products, which was highly inefficient because of the lack of integration. The result was slow query times because of high demand or network latency from some databases, whereas other database resources would be underutilized.

With Oracle Database 12c, dynamic, global load balancing is now integrated, so that client connections and workload requests are automatically equalized across resources. You can run load balancing across clusters and geographies, which allows traffic to be distributed between facilities in real time. The result is significantly increased performance, higher availability, and improved resource utilization. Oracle Database 12c GDS is an exceptional workload management solution for large environments that have multiple locations with active replication, and large, distributed reader farms



4. Improve productivity with application continuity

Oracle has put a lot of effort into high availability for Oracle RAC, but until now, one nagging issue has remained: if a database server goes down, what do you do about in-flight data changes? How can an application even know a commit was successful?
Prior to Oracle Database 12c, DBAs could be spend hours making changes to a database and would have to choose between committing these changes too early and possibly losing their work. With Oracle Database 12c application continuity feature, they don’t have to make that choice. Java-based applications can seamlessly fail over in case of a server failure—even when there are outstanding data changes. It does this by keeping a record of uncommitted changes and seamlessly replaying them in case of a failure—all of which is completely transparent to the application. The net effect is higher availability, improved productivity, and cost savings because applications can now handle server failures without complicated and expensive coding projects.

5. Reduce costs and improve manageability

Centralized enterprise storage can significantly reduce performance and become very expensive—easily costing millions of dollars in some cases. For start-ups and small companies, this option is usually cost-prohibitive.
Oracle Database 12c’s Flex ASM improves availability by removing the requirement for a single, fixed ASM instance per cluster node. So that, even if an ASM instance fails, cluster nodes can transparently reconnect to another ASM instance in the cluster without downtime. ASM instances can be brought down for maintenance in a rolling fashion, while all the database instances remain up and functioning. And for large clusters, Flex ASM reduces maintenance effort and overhead by only running ASM on a subset of cluster nodes.

Comments

Popular posts from this blog

Step by Step: How to troubleshoot a slow running query in Oracle

Register Archive log file manually in standby Database

How to check UNDO tablespace usage and who is using more undo