Time to show you what is the big advantage of multitenant. Then we have consolidated several datamarts into same tablespaces. I had to when we had some block corruption on the SAN (you know, because of issue 1 we did lot of online reorg of the filesystems, and SAN software had a bug) This is where I made my alternative to DBA_EXTENTS. Let me give you an example I create the same table in two schemas (DEMO1 and DEMO2) of same database.
10 years ago I worked on a database that had 3000 schemas. You can think of them as specialized datamarts: same code, same data model, but different data, used by application services provided to different customers. When I think about it, the multitenant database we can have today (12c) would not have been an easy solution. I’m in multitenant here because of the second test I’ll do, but it’s the same pluggable database PDB1.
I remember a telco billing software I’ve installed 15 years ago. It had nothing to do with the software name or the vendor name. Per application backend point-in-time recovery is prohibitively difficult I don’t see the point.
Currently multitenant do not give us more options because pluggable database point in time recovery, nor flashback pluggable database, is currently possible in-place. You can already read about it at Of course, when using schema-based consolidation you should used different tablespaces and you have TSPITR.
The Fargo alum, meanwhile, simply tweeted a diamond ring emoji.
After moving to Los Angeles, Peretti made appearances on programs such as Louie, The Sarah Silverman Program, Tru TV Presents: World's Dumbest..., and Tosh.0.
We can see that because there is not an additional ‘reason’ in V$SQL_SHARED_CURSOR.Then it follows the child list in order to see if a child can be shared. We didn’t have ‘perf flame graphs’ at that time, or we would have seen a large flame over .But semantic verification sees that it’s not the same ‘DEMO’ table and it had to hard parse. Looking at thousand of child cursors in the hope to find one that can be shared is very expensive.The V$SQLAREA is also misleading because VERSION_COUNT aggregates the versions across containers.
But the real behavior is visible in V$SQL_SHARED_CURSOR above and if you run that with a lot of child cursor you will see the difference in CPU time, latching activity, etc. Pluggable database do not need the multitenant option as you can plug/unplug database in single-tenant.Hello experts, I have a scenario where there are 3 - 4 BW systems, disparate, in seperate regions and I am looking to put together a consolidation scenario where we have just one/two BW systems. Can you please share some documents/links to knowledge papers of such consolidation scenarions?