Nobody can say that I am not current and topical with my posts. This post refers to functionality that was introduced in 9i, however I have just come across it and thought it useful enough to blog about it.
The command ALTER USER USERB GRANT CONNECT THROUGH USERA allows a proxy connection to be made using the username and password of USERA but to connect in as USERB. The purpose is so that management of a user can be done without knowing that users password or changing it. This is most commonly going to be used by support teams.
I will give an example
This was sent to me for posting by my friend and ex-colleague Vitaly Kaminsky ….
I have recently worked with the customer where standard RMAN backups of production 2-node cluster (18.104.22.168) were getting too big and taking longer than 24 hours to run.
The problem with this particular cluster was the fact that ALLOCATION of RMAN connections to the instances of the cluster was controlled by SCAN and driven by the load-balancing algorithm of SCAN.
I will start this post off stating that I know there are better and more efficient methods of doing this but this is the best method I could come up with.
I had a csv file with a number of columns, one of which was data in a timestamp with timezone format.
A few rows looked like this – note I have stripped the other columns out for ease of display.
7941 11/9/2014 12:46:49 AM +00:00
8533 11/9/2014 12:46:49 PM +00:00
3692 11/9/2014 1:10:36 PM +00:00
I received an email from a team member yesterday
Have you seen this? https://docs.oracle.com/database/121/TDPPT/tdppt_awr_warehouse.htm
Interesting idea – ever thought of implementing it?
Well of course I have implemented a AWR data repository and I thought I would catch-up on where I am with it and how it is being used.
In the (good) old days there was only one optimizer and plans were developed based on the precedence of the rules. For some reason I have always thought there were 11 rules but looking at the manual it tells me there are 15 rules
It is normal for bloggers including myself to post about the great things they have done – however in this case I am blogging about why I was surprised that adding a specific index had the substantial benefits it did have.
The table contains around 32M rows, is not partitioned and is on Linux 22.214.171.124
It is long been a concern of mine that it is relatively easy to open a standby database inadvertently and then be potentially liable to a licensing cost as usage is shown in the
In fact we logged an SR on the subject based on experiences on failing over using DataGuard Broker
A well configured OEM 12c (or any previous version of your choice) is a fantastic enterprise tool and the reporting capabilities are a major asset.
I am going to share three examples of reports we use and find valuable and if anybody has any other good ideas I am happy to hear about them.
I don’t think I wrote any of them but I almost certainly identified the requirement and instigated the creation of each report. I have masked out obvious details so the screen shots do look messy.
This post runs in parallel with a post I made 5 years ago and which is still the most read one on this blog
It will show how to reduce space taken up in the SYSAUX tablespace by because you have many more AWR snapshots being retained than you think.
Firstly lets take an example database and we can see that we are using 92Gb of space