Top 4 Reasons for Node Reboot or Node Eviction in Real Application


Remote DBA usually face Node Reboots or Node Evictions in Real Application Cluster Environment. Node Reboot is performed by CRS to maintain consistency in Cluster environment by removing node which is facing some critical issue.

A critical problem could be a node not responding via a network heartbeat, a node not responding via a disk heartbeat, a hung. or a hung ocssd.bin process etc. There could be many more reasons for node Eviction but Some of them are common and repetitive.Here, I am listing:-

Top 4 Reasons for Node Reboot or Node Eviction in Real Application Cluster (RAC) Environment:

Whenever, Database Administrator face Node Reboot issue, First thing to look at should be /var/log/message and OS Watcher logs of the Database Node which was rebooted.

var/log/messages will give you an actual picture of reboot:- Exact time of restart, status of resource like swap and RAM etc.

1. High Load on Database Server: Out of 100 Issues, I have seen 70 to 80 time High load on the system was reason for Node Evictions. One common scenario is due to high load RAM and SWAP space of DB node got exhaust and system stops working and finally reboot.

So, Every time you see a node eviction start investigation with /var/log/messages and Analyze OS Watcher logs. Below is a situation when a Database Node was reboot due to high load.

/var/log/messages output from a Database Node just before Node eviction:

From above message, we can see that this system has only 4kB free swap out of 24G swap space. This means system neither has RAM not SWAP for processing, which case a reboot. This picture is also clear from OS Watcher of system.

How to avoid Node Reboot due to High Load.

The simple and best way to avoid this is use Oracle Database Resource Manager (DBRM). DBRM help to resolve this by allowing the database to have more control over how hardware resources and their allocation. DBA should setup Resource consumer group and Resource plan and should use them as per requirements. In Exadata system Exadata DBA can use IORM to setup resource allocation among multiple database instances.

2. Voting Disk not Reachable: One of the another reason for Node Reboot is clusterware is not able to access a minimum number of the voting files .When the node aborts for this reason, the node alert log will show CRS-1606 error.

Here is a scenario for voting disk not reachable:
There could be two reasons for this issue:

A. Connection to the voting disk is interrupted.
B. if only one voting disk is in use and version is less than, hitting known bug 13869978.

How to Solve Voting Disk Outage.

There could be many reasons for voting disk is not reachable, Here are few general approach for DBA to follow.

1. Use command ” crsctl query css votedisk ” on a node where clusterware is up to get a list of all the voting files.

2. Check that each node can access the devices underlying each voting file.

3. Check for permissions to each voting file/disk have not been changed.

4. Check OS, SAN, and storage logs for any errors from the time of the incident.

5. Apply fix for 13869978 if only one voting disk is in use. This is fixed in patch set and above, and and above

If any voting files or underlying devices are not currently accessible from any node, work with storage administrator and/or system administrator to resolve it at storage and/or OS level.

3. Missed Network Connection between Nodes: In technical term this is called as Missed Network Heartbeat (NHB). Whenever there is communication gap or no communication between nodes on private network (interconnect) due to network outage or some other reason. A node abort itself to avoid “split brain ” situation. The most common (but not exclusive) cause of missed NHB is network problems communicating over the private interconnect.

Suggestion to troubleshoot Missed Network Heartbeat.

1. Check OS statistics from the evicted node from the time of the eviction. DBA can use OS Watcher to look at OS Stats at time of issue, check oswnetstat and oswprvtnet for network related issues.

2. Validate the interconnect network setup with the Help of Network administrator.

3. Check communication over the private network.

4. Check that the OS network settings are correct by running the RACcheck tool.

4. Database Or ASM Instance Hang: Sometimes Database or ASM instance hang can cause Node reboot. In these case Database instance is hang and is terminated afterwards. which cause either reboot cluster or Node eviction. DBA should check alert log of Database and ASM instance for any hang situation which might cause this issue.

Database Alert log file entry for Database Hang Situation:

At the same time resources at Cluster level start failing and node was evicted by itself. Real Application Cluster Log files

So, I believe this could be due to some bug in database.

In few of the cases, bugs could be the reason for node reboot. bug may be at Database level, ASM level or at Real Application Cluster level. Here, after initial investigation from Database Administrator side, DBA should open an SR with Oracle Support.

Please share if you know any other Common reason for Node eviction in RAC environment in comment section of the post.

Pitkins college #energy, #oil #and #gas, #boone #pickens, #t. #boone #pickens, #philanthropist,


Boone Pickens

Join the Pickens Plan Army.

The other day, my team uncovered some videos of the news interviews I had done back in the 1980s. Those were heady times. It was the start of the corporate takeover and shareholder rights era, and I was not just in the thick of it, I was driving it. And communicating clearly and effectively was critical to our success.

Strong communication has always been my core asset. I’ve always believed you can trace every problem to a lack of communication or lack of clarity in communication.

These days, I sometimes find myself literally at a loss for words. Over the Christmas holiday, I had several strokes. But with a little determination and some aggressive speech therapy, I regained 90 percent of my speech.

However, last week, I had a Texas-sized fall — one that required hospitalization. I am still mentally strong, and I comprehend and process information like I did before the incident. It’s just a little hard to find the words I m looking for to speak clearly. Speech therapy will fix that, I’m confident.

Just as I exercise my body daily I will exercise my brain and continue with rigorous speech therapy to regain what I can. I am always up for a good challenge.

Nine years ago today, we launched the Pickens Plan. We knew we had a great idea, and people across the country agreed. We d held focus groups and found that Americans knew about the problem, but saw that the country lacked an energy plan. They were hungry for something that would work, a specific energy plan that included a little bit of everything solar, wind, and natural gas.

For the final podcast on the history of the Pickens Plan, I talk with Peter McCollum and Jason Huntsberry. Although they referred to themselves as little cogs in a big machine, they were a major part of the tight-knit team that makes the Pickens Plan tick.

Last month I turned 89 years old, mindful of the fact I’m now 24 years beyond traditional retirement age. My post-65 era has included the most productive years of my life. I was 68 when I left Mesa Petroleum. I turned out the lights at 6 p.m. my last day in the office, as I Continue reading The Old Man Makes a Comeback

Washington, D.C. is as divided as it has ever been, and it has become difficult to set politics aside and get things done. But fortunately the Pickens Plan benefited from a bipartisan team that came together to promote a plan that has our nation’s best interests in mind.

For the latest episode of the Pickens Podcast, I sat down with Rich Galen, a columnist and former press secretary for U.S. Senators Dan Quayle (R-IN) and Kay Bailey Hutchinson (R-TX), and Amy Weiss, former White House Deputy Press Secretary to President Bill Clinton and press secretary and campaign manager for U.S. Rep Mike Synar (D-OK). These two have reached across the aisle to help make the Pickens Plan work. It just goes to show how successful you can be when you can look past personal politics to focus on a mission.

Without question, America is a nation committed to environmental leadership. All you have to do is look at how much cleaner our country has gotten over the last 10 years through the expanded use of natural gas. But the Paris Climate Accord is another bad deal negotiated by the Obama Administration, and America should applaud Continue reading T. Boone Pickens Statement on President Trump s Paris Climate Accord Decision

WFAA s Pete Delkus visited my office this morning for a fun conversation to celebrate my 89th birthday. CNBC s Becky Quick made a surprise appearance via phone, my wife Toni stopped by, and I appreciate all the well wishes left by commenters during the Facebook Live event. I also gave viewers a tour of my office Continue reading My 89th birthday celebration via Facebook Live

Oracle Database Monitoring Software #oracle #monitoring, #oracle #monitors, #oracle #monitoring #services, #oracle


Oracle Monitoring Software

BC consultants have written Oracle monitoring for some of the worlds most complex databases. Don’t entrust your Oracle monitoring to a novice, just call. Our staff has unprecedented opportunity to see real-world Oracle database in-action and we only recommend Oracle monitoring software that we have tested and approved.

Monitoring Tools for Oracle

It’s not necessary to spend thousands of dollars on Oracle monitoring software and BC offers solutions ranging for do-it-yourself Oracle monitoring scripts to full installation and management of customized Oracle monitoring solutions.

Recommended by Burleson Consulting

Ion is an incredible Oracle time-series monitoring tool that analyzes the Oracle AWR and ASH data.

BC consultants are noted experts in Oracle database monitoring. For Oracle database monitoring scripts, check-out our Oracle script depot, or the book Oracle Tuning: The Definitive Reference . The online monitoring scripts are available immediately.

Oracle Monitoring Products

Donald Burleson has developed several world-class Oracle monitoring products that provide complete Oracle monitoring solutions:

ServerPack – Monitoring UNIX servers is a critical IT management task. This is a complete software tool that captures UNIX server statistics into Oracle tables. ServerPack software can quickly produce valuable time-based UNIX server CPU and RAM trend reports. Click here for details.

TablePack for Oracle – Capacity planning is a critical IT management role, and TablePack can help. TablePack software captures Oracle tables and index information to produce time-based Oracle growth reports. Oracle capacity planning reports, and individual details on the growth of all Oracle tables and indexes. Click here for details.

AuditPack for Oracle – Auditing Oracle user activity, auditing database changes and auditing production database errors are critical IT management tasks. AuditPack software utilizes system-level triggers to provide a complete Oracle monitoring solution for Oracle user auditing, servererror logging, and DDL audit reports. Click here for details.

Your Oracle shop can possess complete Oracle monitoring software, completely installed and tested at your site for just a few thousand dollars. Burleson Consulting has developed a suite of standard Oracle monitoring software that can be quickly installed to monitor your Oracle databases and alert you before you have an Oracle crash.

Burleson Consulting is committed to providing world-class Oracle monitor software and services that are customized according to the needs of your company. Don has installed Oracle monitoring software on some of the world’s most sophisticated Oracle databases. Our revolutionary Oracle Monitors allow us to quickly install a complete monitoring solution and provide customized e-mail alerts for management and DBA staff.

We Guarantee your Success

In just a few days, you can own a complete and comprehensive Oracle monitoring software solution. Donald Burleson offers this complete monitoring for a fixed price and guarantees satisfaction. Click here to see a detailed list of Oracle monitor events.

These monitors often pay for themselves by reducing unplanned downtime and freeing-up you DBA for other important work.

Increase DBA availability by automating Oracle database monitoring.

Provide management reports that predict future hardware shortages.

Quickly identify transient causes of Oracle performance problems.

Develop a comprehensive Oracle database monitoring solution.

Perform Oracle monitoring tuning the smart way by analyzing historical trends.

Oracle Java SE Support Roadmap #motels #in #lancaster #pa

#end of life


Oracle Java SE Support Roadmap

(Updated May 14, 2015)

Oracle provides this updated roadmap for Javac SE and Oracle Java SE products (Oracle Java SE Support. Oracle Java SE Advanced, Oracle Java SE Advanced Desktop and Oracle Java SE Suite ) to help customers better understand the maintenance and support options available. Java SE major releases are publicly maintained for a minimum of 3 years from general availability date (GA date), or later, as described in the next section. Java SE releases are updated for the public with bug fixes, security fixes, and minor updates for a period of at least 3 years before the release reaches end-of-public-updates (EoPU). Oracle Java SE product releases – starting with Java SE 7 – are supported for no less than eleven (11) years from initial release date, enabling IT managers and ISVs to plan their upgrades according to their individual business practices. The following provides a more detailed review of the Java SE products support roadmap, along with examples specific to available major releases. All customers should refer to their specific service contract to determine their support entitlement. See the Oracle Lifetime Support Policies for complete details.

Auto-update Notice and End of Public Updates for Oracle JDK 7

As outlined in the Oracle JDK Support Roadmap. after April 2015, Oracle will not post further updates of Java SE 7 to its public download sites. Customers who need continued access to critical bug fixes and security fixes as well as general maintenance for Java SE 7 or older versions can get long term support through Oracle Java SE Support. The process of migrating users from Java 7 to Java 8 through the auto update feature is expected to take place after the January 2015 CPU release .

Java Platform, Standard Edition (Java SE) Major Releases

Major releases of the Java Platform, Standard Edition (Java SE), are identified as 5.0, 6, 7 and 8. As of the publishing of this article, the Java technology end of public updates policy has been clarified to confirm public availability of Java SE major releases for at least:

  • Three years after the general availability date (GA) of a major release
  • One year after the GA of a subsequent major release
  • Six months after a subsequent major release has been established as the default Java Runtime Environment (JRE) for end-user desktops on

Consistent with previous policies and documentation, Oracle will post an end of public updates notice for each major release well in advance, indicating that the release has entered its transition period. Once the release has completed its transition period, no new downloads of that release will be made publicly available on the public Oracle web sites, and will only be available through the My Oracle Support web site. Previously available older releases will continue to be available for support and debugging through the Java Archive but are not recommended for production use.

Java SE 7 End of Public Updates Notice

After April 2015, Oracle will no longer post updates of Java SE 7 to its public download sites. Existing Java SE 7 downloads already posted as of April 2015 will remain accessible in the Java Archive on Oracle Technology Network. Developers and end-users are encouraged to update to more recent Java SE versions that remain available for public download.

Long Term Support

Customers who need continued access to critical bug fixes and security fixes as well as general maintenance for Java SE 7 or older versions can get long term support through Oracle Java SE Support .

* or later, depending on factors described above.

Java SE Minor Release Lines

Java SE minor release lines represent a cumulative set of implementation enhancements to a major release, such as the Java SE 1.4.1, and 1.4.2 minor release lines to the Java SE 1.4 major release. Java SE minor releases do not have separate EOL periods from their corresponding major release. Once a new Java SE minor release is made available, the previous Java SE minor release line for a release will be considered superseded. Download links for the previous minor release line will be moved to the Product Archive page for historical purposes and to allow developers to resolve issues with those products that have completed their EOL process. Please note that releases from this page may contain bugs and security problems that have been fixed in a later release and for that reason downloads of superseded versions is not recommended.

Oracle Java SE Product Releases

Customers seeking longer standard support and maintenance periods for each major release are encouraged to migrate to the Oracle Java SE product offerings (Oracle Java SE Support. Oracle Java SE Advanced, Oracle Java SE Advanced Desktop and Oracle Java SE Suite ). Oracle Java SE product releases will follow the Oracle standard EOL policy for licensable products. During a release s eight (8) year transition period, customers will be eligible to receive Oracle Premier Support for that entire period, in accordance with their support contract with Oracle. Past those 8 years, support customers will receive critical bug and security fixes as well as general maintenance releases as per the Oracle Extended Support terms. Oracle Java SE Support puts you in control of your upgrade strategy so you can enjoy continued peace of mind, knowing that no matter which product release you’re running, Oracle can support your business.

Examples of some key product dates for Oracle Java SE product offerings include:

Oracle Java SE Support Roadmap *

* Oracle Java SE product EOL dates are provided here as examples to illustrate the Oracle Java SE Support, Oracle Java SE Advanced, Oracle Java SE Advanced Desktop and Oracle Java SE Suite EOL Policy. Customers should refer to Oracle Lifetime Support Policy for the most up-to-date information.

** These support timelines apply to client and server deployments of Java, with the exception of the web deployment technology. See Support of Deployment Technology section below for details.

Support of Deployment Technology

The web deployment technology, consisting of the Java Plugin and Web Start technologies, has a shorter support lifecycle. For all major releases of Java SE starting with Java SE 7, Oracle provides five (5) years of Premier Support for these technologies. Extended Support is not available for the deployment stack. See the Oracle Lifetime Support Policy for details.

Deployment Technology for Java SE 6 will be available until Jun 2017.

Extended Support Life for Java SE 6

In April 2014 Oracle extended the support lifetime for Java SE 6. Before this extension the end of Premier Support was Dec 2013 and the end of Extended Support was scheduled for Jun 2017. The new support dates are: End of Premier Support on Dec 2015, and End of Extended Support on Dec 2018.

The extension of Support Life for Java SE 6 does not include the Java SE 6 Deployment Technology. Java SE 6 Deployment Technology will only be available until Jun 2017. Update releases of Java SE 6 released after Jun 2017 will not include deployment technology.

Update Releases Revisions

As a new implementation of an existing release, an update or revision itself does not have a separate EOL period. Once a new update or revision is posted, the previous, displaced download will be moved to the Java Product Archive page.

Relevant Links

Oracle Solaris Download – Softpedia Linux #oracle #solaris, #download #oracle #solaris, #oracle


Oracle Solaris (formerly SunOS) is a commercial product that provides users with an integrated and full featured server-oriented platform that combines the powerful OpenStack open source cloud computing software with a stable and reliable enterprise-class operating system.

Availability, supported platforms, boot options, and a little bit of history

First of all, we want to remind the reader that this is not a Linux distribution! Solaris OS is a UNIX operating system initially developed by Sun Microsystems, and now maintained by Oracle Corporation under the name of Oracle Solaris.

It is available for download as installable and live ISO images that can be burned onto blank CD discs using any CD/DVD burning software, as well as USB images that allows users to write the operating system to portable USB flash drives.

Supported architectures include x86 (32-bit) and SPARC (Scalable Processor Architecture). Recommended system requirements include at least 2GB or RAM (system memory) and at least 15GB of free hard disk space.

The Live CD ISO/USB images provide users with a modern boot prompt powered by GRUB2, from where users can start the live environment with default settings, using the VESA framebuffer, with SSH enabled, with screen reader, with magnifier, or in text mode. It is also possible to boot an existing operating system installed on the first disk.

State-of-the-art UNIX technologies for both server and desktop platforms

Before entering the live environment, users will need to select a keyboard layout and the language they want to use. The graphical session is powered by the traditional GNOME desktop environment, which comprises of two panels, a top one for accessing the main menu and launching apps, and a bottom one for interacting with running apps and switching between virtual workspaces.

Using the highly acclaimed ZFS filesystem, it includes powerful applications like the Mozilla Firefox web browser, Mozilla Thunderbird email and news client, Glade interface designer, Pidgin instant messenger, Rhythmbox music player, Totem video player, Orca screen reader and magnifier, and GParted partition editor.

Bottom line

All in all, Oracle Solaris is a decent server operating system that has been redesigned from the ground up and engineered for cloud computing. It supports the x86 and SPARC architectures, and features the award winning OpenStack software.

New in Oracle Solaris 11.2:

  • Now available, Oracle Solaris 11.2 is engineered to deliver an efficient, secure, compliant, open and affordable path to enterprise cloud computing for organizations seeking to simplify and modernize their data centers.
  • Oracle Solaris 11.2 is a complete, integrated and open cloud platform engineered for large-scale enterprise cloud environments. It combines OpenStack, application-driven SDN technology, clustering, and zero-overhead virtualization with a proven enterprise-class OS.
  • With its application compatibility guarantee program, Oracle Solaris is designed to make IT’s transformation to enterprise-grade cloud simple, fast, and affordable.
  • Customers can get a cloud up and running in as few as 10 minutes using Oracle Solaris 11.2’s Unified Archive template and OpenStack distribution.

Read the full changelog

SAP vs #oracle #and #sap #are #the #biggest #erp #vendors


SAP vs. Oracle: Which ERP implementation is right for you?

Many CIOs looking to implement new ERP software will, no doubt, end up considering the industry’s two biggest behemoths: SAP and Oracle. While both vendors are clear market share leaders and have very well-established product lines, the strengths, weaknesses, risks and product roadmaps of these two vendors couldn’t be more different.

According to Panorama Consulting’s most recent Clash of the Titans report — which summarizes quantitative results from hundreds of ERP implementations across the globe — implementing the SAP ERP system. as compared with implementing the Oracle ERP system. produces very different results for companies. For example, while the average Oracle customer spends less money on their implementation, the average SAP customer is able to deliver an implementation timeline that is closer to what was expected. This is just one of many examples we found when analyzing the results of the study.

Given that there are so many tradeoffs and variables to consider, we thought it would be helpful to narrow the differences between the two products to five key areas: ERP implementation risk, implementation cost and duration, scalability. software functionality and customization, and cloud adoption. These areas underscore some of the biggest differences between the two products and their future directions.

ERP implementation risk

Every executive is concerned about the risk of their ERP implementation, which is why they are constantly craving methods and tools to help mitigate the risk of ERP failure. Data from the Clash of the Titans report confirmed that these are, indeed, rational concerns, with more SAP customers claiming their implementations were failures than Oracle’s customers. Further, more SAP customers experienced some sort of material operational disruption at the time of go-live, such as not being able to ship products or close the books.

While the research suggests that implementing SAP ERP carries a higher risk implementation profile than implementing Oracle ERP, every ERP customer experiences an elevated degree of risk. This is why these two vendors have done a particularly good job of developing risk management mechanisms to address these concerns. For example, SAP’s All-in-One product features best practices and preconfigurations for a number of different industry verticals, with the intent of reducing risk and accelerating implementations. Speaking of acceleration, Oracle has developed similar tools, with its line of implementation accelerators and its User Productivity Kit, both of which were designed to make testing, training and other key implementation processes more efficient and effective.

Implementation cost and duration

When considered as a percentage of a company’s annual revenue (or budget, for public sector organizations), SAP is the higher cost option. The average SAP customer spends 4% of its annual revenue on its total cost of ownership, while the average Oracle customer spends 1.7%. This could be attributed to the breadth of functionality — and, therefore, higher cost — associated with SAP’s software. It could also be an indication of large organizations botching their product implementations (think: Waste Management, The Hershey Company, Marin County and other high-profile failures of recent years).

However, cost is just part of the ERP implementation equation; CIOs and project teams are also concerned with implementation duration, which is where SAP excels. While the average Oracle customer takes 22.5 months to implement the ERP software, the average SAP customer is able to do so in 4 months less. Again, this is where SAP’s preconfigurations and Oracle’s accelerators come in handy; in addition to mitigating risk, as discussed above, they also help accelerate the implementation time frame.

ERP system scalability

Most midmarket and larger organizations are concerned about the scalability of their ERP systems. After all, they are typically looking to their enterprise software to provide the operational backbone to help grow and scale their companies, often after years of fragmented and inconsistent business processes and systems.

When it comes to ERP system scalability for SAP vs. Oracle, the two are fairly even, albeit for different reasons. In other words, it is safe to say that the world’s largest organizations are able to scale their companies with either product, simply because most Fortune 500 organizations are already using products from either or both.

However, the degree of scalability for your particular organization depends on your needs. While Oracle has largely created more of a best-of-breed option with its various products — such as E-Business Suite, Fusion, JD Edwards, Siebel and Hyperion — SAP has largely developed its products from the ground up, creating more of a consistent and single system feel.

Organizations looking for scalability through consistency and standardization may find SAP more scalable, while those operating from a more decentralized model based on flexibility may be better suited for Oracle’s suite of products.

Software functionality and customization

At the end of the day, the technological backbone of your chosen ERP system — whether SAP or Oracle — doesn’t really matter. Instead of a specific technology, enterprise buyers are investing in functionality and improvements to their business operations.

When comparing SAP and Oracle software through this lens, it is clear that both vendors are committed to enhancing functionality. According to the Clash of the Titans report. SAP customers generally realize more of their expected functionality and business benefits than Oracle’s customers. On the flip side, Oracle’s customers realize a faster payback than SAP users.

Similarly, the dreaded C word of ERP — customization — is on every CIO’s mind. As much as they may not want to think about it, ease of customization is a real need for organizations wanting to ensure a good fit between their ERP system and their operational needs. In the case of SAP and Oracle, customers of both vendors customize their software products quite a bit, which isn’t, in and of itself, a bad thing. As mentioned above, Oracle’s best-of-breed solutions provide options for project teams not wanting to customize their software, while SAP also offers customization and integration tools to make its software more flexible for its enterprise customers.

Cloud adoption

For many, gone are the days of big, robust, internal IT infrastructures hosting ERP software and other enterprise software applications. Instead, a growing number of organizations are migrating their products to the cloud — whether that be through pure software as a service, or through traditional, single instance landscapes hosted by a third-party provider.

When comparing SAP and Oracle in this area, Oracle has the slight upper hand, with more of its customers leveraging cloud options. and more of its cloud-based customers realizing more measurable business benefits than SAP’s. SAP’s Business One, once considered its most viable cloud-based offering for smaller businesses, is rumored to be on the chopping block, which may cause the company to lose further ground in this area.

While both vendors have adopted cloud delivery models, data suggests Oracle has been more successful in this area.

In-memory technology: SAP HANA vs. Oracle

Over the past year, we have seen SAP and Oracle boast about how their in-memory technology systems are going to change the future of ERP. SAP is making great headway with their in-memory database. as SAP HANA is differentiating itself as a highly functional, all-in-memory system. While having a single platform can be a great advantage, it also has its drawbacks, such as the cost of deployment and compatibility limitations.

In response to SAP’s success with SAP HANA. Oracle has also made great strides with their new database in-memory system by differentiating their system as being functional and easy to integrate with existing compatible databases and applications. While this is a cost advantage — especially to those already running compatible databases — this system may not provide the convenience and breadth of a centralized system.

Putting the vast technical differences between these two systems aside, the business end result for the customer is nearly the same. In-memory technology will allow customers to run essential ERP applications and analytics faster, ultimately providing for greater productivity and insight.

Which ERP system should you choose — SAP vs. Oracle?

While the above points of differentiation may not suggest that either vendor has a clear, across-the-board advantage over the other, it hopefully suggests some factors that potential ERP buyers can use to evaluate their software options. Every organization is different, with different priorities and evaluation criteria. but one or more of the above areas may provide the context for you to compare these two products.

Either product can likely get the job done, so the question becomes: Which will help get the job done best for your organization?

About the author:
Prior to founding Panorama Consulting, an ERP-targeted consulting group, Eric Kimberling banked 15 years of ERP consulting experience at firms such as Price Waterhouse. Eric is an expert on ERP implementation project management, as well as ERP software selection and ERP organizational change.

Next Steps

Just how helpful is an SAP proof of concept anyways?

Oracle SQL temporary tables #oracle #global #temp #table


Speed Oracle SQL with Temporary Tables

For certain types of SQL operations, the creation of intermediate result tables can result in stunning performance improvements. We will discuss how you can use the global temporary tables (GTT) syntax to improve the speed of queries that perform complex summarization activities, and how to speed up two-stage queries that perform both summarization and comparison activities.

Please read these important notes on SQL tuning with temporary tables:

For the full details of the huge benefits of temporary table query tuning. see my book Oracle Tuning: The Definitive Reference .

Let’s begin by looking at how the creation of temporary tables can speed non-correlated subqueries against the Oracle data dictionary.

Using temporary tables with Dictionary Views

The prudent use of temporary tables can dramatically improve Oracle SQL performance. To illustrate the concept, consider the following example from the DBA world. In the query that follows, we want to identify all users who exist within Oracle who have not been granted a role. We could formulate the query as an anti-join with a noncorrelated subquery (against a complex view) as shown here:

select username from dba_users where username NOT IN (select grantee from dba_role_privs);

This query runs in 18 seconds. As you may remember from Chapter 12, these anti-joins can often be replaced with an outer join. However, we have another option by using CTAS. Now, we rewrite the same query to utilize temporary tables by selecting the distinct values from each table.

create table temp1 as select username from dba_users; create table temp2 as select distinct grantee from dba_role_privs; select username from temp1 where username not in (select grantee from temp2);

With the addition of temporary tables to hold the intermediate results, this query runs in less than three seconds, a 6� performance increase. Again, it is not easy to quantify the reason for this speed increase, since the DBA views do not map directly to Oracle tables, but it is clear that temporary table show promise for improving the execution speed of certain types of Oracle SQL queries.

Using Temporary Tables

If the amount of data to be processed or utilized from your PL/SQL procedure is too large to fit comfortably in a PL/SQL table, use a GLOBAL TEMPORARY table rather than a normal table. A GLOBAL TEMPORARY table has a persistent definition but data is not persistent and the global temporary table generates no redo or rollback information. For example if you are processing a large number of rows, the results of which are not needed when the current session has ended, you should create the table as a temporary table instead:

The “on commit preserve rows” clause tells the SQL engine that when a transaction is committed the table should not be cleared.

The global temporary table will be created in the users temporary tablespace when the procedure populates it with data and the DIRECT_IO_COUNT will be used to govern the IO throughput (this usually defaults to 64 blocks).

Get the Complete
Oracle SQL Tuning Information

The landmark book Advanced Oracle SQL Tuning The Definitive Reference is filled with valuable information on Oracle SQL Tuning. This book includes scripts and tools to hypercharge Oracle 11g performance and you can buy it for 30% off directly from the publisher.

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals. Feel free to ask questions on our Oracle forum .

Verifyexperience!Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications .

Errata? Oracle technology is changing and we strive to update our BC Oracle support information. If you find an error or have a suggestion for improving our content, we would appreciate your feedback. Just e-mail: and include the URL for the page.

The Oracle of Database Support

Copyright 1996 – 2016

All rights reserved by Burleson

Oracle is the registered trademark of Oracle Corporation.