I had the pleasure of rebuilding an Exadata rack for a customer a while back, and it provided a pretty good refresher in backup and recovery for me. As DBAs, we back up databases all the time, but the restores are performed much less frequently. In the case of this rack, there were several databases across multiple ASM diskgroups. One of the goals of the rebuild was to consolidate all of the databases into a (more...)
Announcing the release of Exachk Version 18.104.22.168.4_20150702. Exachk is a tool that is used to quickly determine the health of the entire Exadata infrastructure. Some of the key components that are checked include the database, cell servers and the network. This tool further reviews the configuration of the system and compares with the best practices. […]
The post Latest Release of Oracle Exadata Exachk and HealthCheck appeared first on VitalSoftTech.
Some time ago Oracle announced that RDBMS 22.214.171.124 has built-in support for JSON processing. A little later it was also mentioned that you have support for JSON in the Exadata storage servers for offloading. This is probably a lot more exciting to users of JSON than it is to me as I’m not a developer. However, whenever an announcement such as the one I’m referring to is made I would like to (more...)
This will be simple and short post on an issue I had recently. I got the following error while running the first step of onecommand – Validate Configuration File:
2015-07-01 12:31:03,712 [INFO ][ main][ ValidationUtils:761] SUCCESS: NTP servers on machine exa01db02.local.net verified successfully 2015-07-01 12:31:03,713 [INFO ][ main][ ValidationUtils:761] SUCCESS: NTP servers on machine exa01db01.local.net verified successfully 2015-07-01 12:31:03,714 [INFO ][ main][ ValidationUtils:778] Following errors were found... 2015-07-01 12:31:03,714 [INFO ][ (more...)
If you’ve run an exachk report, y0u may have seen the following message with regard to your databases:
|FAIL||Database Check||Database parameter CLUSTER_INTERCONNECTS is NOT set to the recommended value||db01:dbm011, db02:dbm012||View|
This check is commonly seen when a database is created on Exadata without using the custom “Exadata” templates included with the database creation assistant. These customized templates include a multitude of recommended parameter settings found in (more...)
While deploying an X5 Full Rack recently it happened that the Grid Infrastructure Management Repository was not created by onecommand. The GIMR database was optional in 126.96.36.199 and became mandatory in 188.8.131.52 and should be automatically installed with Oracle Grid Infrastructure 12c release 1 (184.108.40.206). For unknown reason to me that didn’t happen and I had to create it manually. I’ve checked all the log files (more...)
I’ve done several Exadata deployments in the past two months and had to upgrade the Exadata storage software on half of them. Reason for that was because units shipped before May had their Exadata storage software version of 220.127.116.11.0.
The upgrade process of the database nodes ran fine but when I ran dbnodeupdate.sh -c for completing post upgrade steps I got an error that the system wasn’t on the expected (more...)
This is just a quick post to highlight a problem I had recently on another Exadata deployment.
For the most customers the management network on Exadata is routable and the DNS servers are accessible. However in a recent deployment for a financial organization this wasn’t the case and the storage servers were NOT able to reach the DNS servers. The customer provided a different set of DNS servers within the management network which were still (more...)
I’ve done several Exadata deployments recently and I have to say of all the components PDUs were hardest to configure. Important to notice that unlike earlier generations of Exadata the PDUs in X5 are Ehnanced PDUs and not Standard.
Reading the public documentation (Configuring the Power Distribution Units) it says that on PDUs with three power input leads you need to connect the middle power lead to the power source. Well I’ve done (more...)
Another interesting topic that goes over and above the CDB Resource Manager Plans I described earlier this week is the implementation of IORM Plans for Pluggable Databases. Pluggable Databases are an interesting object for studies, and I like to research things. When 12c came out there was no support for offloading initially, it is required that you are on cell software 12.1.x.x.x for full 12c support on Exadata. One aspect I was particularly (more...)
Inspired by Sue Lee’s presentation at Enkitec’s E4 conference I decided to re-run my test suite to work out how you can use Database and I/O Resource Manager in Oracle 18.104.22.168.2 to help consolidating databases in the new Multi-Tenant architecture. I should point out briefly that the use of Multi-Tenant as demonstrated in this article requires you to have a license. Tuning tools shown will also require you to be appropriately (more...)
With the release of Exadata X5 Oracle introduced elastic configurations and changed the process on how the initial configuration is performed. Back before you had to run applyconfig.sh which would go across the nodes and change all the settings according to your config. This script has now evolved and it’s called applyElasticConfig.sh which is part of OEDA (onecommand). During one of the recent deployments I ran into the below problem:
[root@node8 linux-x64]# ./applyElasticConfig. (more...)
During a recent X5 installation I had to configure Link Aggregation Control Protocol (LACP) on the client network of the compute nodes. Although the ports were running at 10Gbits and default configuration of Active/Passive works perfectly fine the customer wanted even distribution of traffic and workload across their core switches.
Link Aggregation Control Protocol (LACP), also known as 802.3ad is a methods of combining multiple physical network connections into one logical connection to increase (more...)
Before discussing the Exadata-specific feature, let’s review what the database engine can do independently of whether Exadata is used. To execute queries containing the
max functions efficiently, two specific operations are available with B-tree indexes defined on the column referenced in the
max function. The first,
INDEX FULL SCAN (MIN/MAX), is used when a query doesn’t specify a range condition. In spite of its name, however, it performs no full (more...)