We are back to REPVFY, (Repository Verification Utility) this week, (first post can be found here…) And I’m onto the next file of substance since looking at the advisor log, (performance data). The next files are the two “details” files. One is a query used to produce the output and the second is the actual output
Want peace in the Middle East? It is actually pretty simple, but the best solution requires the Palestinians to unilaterally do something BOLDLY PEACEFUL. I promise you this will work: Get your folks together. Talk them into disarming and being the model of civility beyond any requirements of Israel for commerce, border crossing, WHATEVER. Invite their security forces in, all the way to your borders to protect you from external issues. Challenge your people to be easy to protect and civil and challenge Israel to protect you. Israel will relish the extra territorial distance from attack and the cost of providing security will pale compared to its value. Then make a long declaration of tolerance. Absurdly long. Let’s say 49 years. Challenge your people to suspend any and all aggressive acts for 49 years and to just play ball.
It’s always the combinations that catch you out.
Bigfile tablespaces have their uses – especially in big systems
Materialized views have their users – especially in big systems
There’s absolutely no reason why the two technologies should interfere with each other … until you find a bug !
Running an example, stripped to the bare minimum, and doing a couple of things that I personally don’t like doing, on 11.2.0.4:
I’ve been having a play with Oracle Linux 7 beta over the weekend. Not surprisingly my first thoughts were to install the Oracle database on it.
As expected, the installations were almost identical or Fedora 19.
In the first part of this article you could read how to add an additional network resource, additional VIPs and SCAN to an 12.1.0.1.2 cluster. In this part I hope to show you the next steps such as adding the SCAN listeners and other resources.
New SCAN listener
With the second SCAN added it is time to add the next set of SCAN listeners. This is really simple, and here is the code to add them:
[oracle@ron12cprinode1 ~]# srvctl add scan_listener -netnum 2 -listener dgscanlsnr
After starting the SCAN listeners on network 2, I can see they are indeed working correctly:
In the first part of this article you could read how to add an additional network resource, additional VIPs and SCAN to an 12.1.0.1.2 cluster. In this part I hope to show you the next steps such as adding the SCAN listeners and other resources.
New SCAN listener
With the second SCAN added it is time to add the next set of SCAN listeners. This is really simple, and here is the code to add them:
[oracle@ron12cprinode1 ~]# srvctl add scan_listener -netnum 2 -listener dgscanlsnr
After starting the SCAN listeners on network 2, I can see they are indeed working correctly:
Some time back, I investigated the options to do profiling of processes in Linux. One of the things I investigated was systemtap. After careful investigation I came to the conclusion that systemtap was not really useful for my investigations, because it only worked in kernelspace, only very limited in userspace. The limitation of working in userspace was that you had to define your own markers in the source code of the program you wanted to profile with systemtap and compile that. Since my investigations are mostly around Oracle products, which are closed source, this doesn’t help me at all.
In the previous post, I pontificated about triggers that "lock you in" to having them fire, which can create dramas when it comes to doing data patching.
Maybe you can design your application around this, but if you cant, the last thing you want to be doing is having to take an outage so that you can disable the trigger whilst you do your data maintenance. Ideally you want the trigger to fire as per normal, except in your session.
And that’s actually pretty easy to do. A simple example is below
When working with Top Activity, we’re accustomed to viewing to wait class in the top, graphed area and below left, the top SQL by SQL_ID and below right is our Top Session information. ASH Analytics was designed so you would enter into a view that looked very similar to Top Activity, but was enhanced so the user could update it to view the data in multiple ways.
Recent comments
3 years 5 weeks ago
3 years 17 weeks ago
3 years 21 weeks ago
3 years 22 weeks ago
3 years 27 weeks ago
3 years 48 weeks ago
4 years 16 weeks ago
4 years 46 weeks ago
5 years 30 weeks ago
5 years 30 weeks ago