USING SAP NETWEAVER WITH ORACLE DATABASE 12C ON ORACLE EXADATA Installation of OPatch and MOPatch Utilities 105 Installation of the SAP Bundle Patch for Oracle. Getting ready for a Exadata interview Make sure to refresh your knowledge by reviewing this list of Exadata Interview Questions. Read more for a quick review of the. Legrand 037 53 User Manual. Community homepage for SAP on Oracle. Find the latest user blogs, questions and answers, and resources along with featured content. Join the conversation with us. Title ServerHardware Partitioning Author Oracle Corporation Subject The purpose of this policy document is to define which of these partitioning technologies is. Exadata Vm TemplateSUN LDOMS aka oracle VM for SPARC is a complete virtual machines that runs an independent operating systems and contains its own virtual CPUs,Storage,Memory. R2 rac installation on 64 bit Linux step by step Nafey March 11, 2010 at 1203 pm. Very nice post. I was able to complete the 11gR2 Rac. Toad for Oracle is the de facto Oracle developer and database administration software tool for SQL development and tasks. The most popular Oracle DBA tool. This appendix describes the new features included in Oracle Exadata Database Machine and Oracle Exadata System Software. Whats New in Oracle Exadata Database Machine. Exam. Within 3. 0 minutes of completing your Oracle Certification exam, you will receive an email from Oracle notifying you that your exam results are available in Cert. View. If you have previously authenticated your Cert. View account, simply login and select the option to See My New Exam Result Now. If you have not authenticated your Cert. View account yet at this point, you will need to proceed with your account authentication. Authentication requires an Oracle Single Sign On username and password and the following information from your Pearson VUE profile email address and Oracle Testing ID. You will be taken to Cert. View to log in once your account has been authenticated. Managing Processes and Memory Consumption on Oracle Exadata database machines. This post is equally applicable to Rac databases deployed, both on oracle database machines as well as traditional serverstorage architectures, running RHEL5 or OEL5 OEL6 has a new feature called transparent hugepages. The Best practices for database consolidation on exadata database machine, White Paper outlines a lot of good guidelines. However the best practices seems to be getting occasionally overlooked, in some cases resulting in Node evictionsrestarts in the cluster. High amounts of memory and cpu consumption can result in some real bad things happening Like for eg Node evictions. So it is important to configure the operating system and the databases you deploy on the machine optimally, to use the available CPU and memory resources. E80920_01/DBMIN/img/GUID-D06D2443-1F79-455F-8F5D-661D57D8E8AC-default.png' alt='Exadata Vm' title='Exadata Vm' />Let us first review what those available memory and cpu resources are on an Oracle Exadata Database Machine, on each database node. Anytime a workload is deployed on a database server, that exceeds the, operating systems ability to efficiently use the above mentioned, available cpu and memory resources, bad things can happen. I know i am over simplifying in the prior comment, but you get the idea. Managing Memory Resources. Setting up Huge. Pages. First we need to make sure that Huge. Pages on each node, is setup correctly, for the databases you have deployed on the node. Tanel Poder has explained the reasons for setting up Huge. Pages on Exadata systems. When the database machines are installed, the Huge. Pages is configured to accomodate the one database that is pre installed. So if you change the SGA setting for that database or deploy more databases you should now adjust the Huge. Pages setting accordingly. It goes without saying that if you have already configured the hugepages to accomodate all the databases you have, and then you removed some databases from the node, or resized the SGAs to be smaller, you should again resize your hugepages to free up the excess hugepages. Once all the database instances are configured and started up you can run the script, hugepagessettings. Mos Note 4. 01. 74. I usually recommend adding 1. With 1. 1. 2. 0. 2 and 1. USELARGEPAGES, preferably to ONLY, following the instructions in Mos Note 1. You can then follow the instructions in MOS note 3. Kernel version 2. You need to restart the databases so the SGA gets allocated with the hugepages. You should also follow instructions from MOS note 1. Managing Memory Usage. Ideally for critical implementations, your SGAPGAIndividual server processes, memory allocations should not exceed 7. The Exadata consolidation white paper above suggests that. For critical Hardware Pools, we recommend an even more conservative approach by not exceeding 7. OLTP applications SUM of databases SGATARGET PGAAGGREGATETARGET 4 MB Maximum PROCESSES lt Physical Memory per Database Node. DWBI applications SUM of databases SGATARGET 3 PGAAGGREGATETARGET lt Physical Memory per Database Node. You can monitor the pga usage a few different ways. SELECT s. instid, s. FROM gvsession s JOIN gvprocess p ON p. AND p. instid s. WHERE s. BACKGROUND and s. P and p. pgausedmem lt APPLICATIONMEMORYTHRESHOLD order by s. The value you use for APPLICATIONMEMORYTHRESHOLD is dependent on your application and howmuch pga it needs to efficiently run your queries Performing the sorts in memory using the space for PGA is usually faster than using the TEMP tablespace. However the white paper suggests using 1. Gb for OLTP applications and 1. Gb for DSS applications. You can monitor the sysmetric Total PGA Allocated from dbahistsysmetricsummary, to see how much PGA is being allocated. You can use the PGA Memory Advisory and SGA Target Advisory sections of the awr report, to guage, the impacts of increasing or decreasing the SGA and PGA Allocations. You can monitor the memory usage at the os level using the top Mem free,free or vmstat bo page out,bi page in commands. Managing OS Processes And as a consequence CPU usage. It is important to control the number of processes that are actively executing on each node. Each of these processes consume cpu and memory resources. The following guidelines are important to follow. Use Application connection pooling to appropriately limit the number of sessions connected to the oracle database. This is important for two reasons. Right Size the resource consumption on each database node. Minimize the impact of connection storms. Configure the parallel query servers appropriately. For all the databases deployed on a node the total setting for PARALLELMAXSERVERS should be less than or equal to the following. X2 2 or X3 2, lt 2. X2 8 or X3 8, lt 1. I often see implimentations where parallelmaxservers 2. I have occassionaly seen systems where there is sustained 1. Use Instance Caging and Database Resource Manager to manage cpu allocation on the server. It would be a good idea to always review the Best practices for database consolidation on exadata database machine, White Paper and follow the guidelines, to have a well performing and  stable database environment. It would be a good idea to review the performance management screens from Enterprise Manager 1.