Hello,
We are testing multi-tenancy on OE 11.3.3 (SP3) on AIX 7.1 64bit, I noticed the repot produced by tabanalys after D&L data from Default tenant into Regular tenant the scatter factor is huge!!
Before...
RECORD BLOCK SUMMARY FOR TENANT Default: 0...
I have found out that we need to do a D&L to move the data where it needs be (or you can do ABL move); no other alternatives so that is fine. Just wanted to answer my own thread in case anyone else stumbles down this path.
I can definitely see a reason for a D&L if we are moving data areas; but in our case when I enable a table for MT I set the allocation policy to delayed so that I can choose non tenant default index/blob/data areas that are defined during regular tenant creation.
This allows us to keep the...
I just find it strange that we can't enable a table for MT and have the data owned by someone other than Default from the get-go; instead of assigning the data to Default tenant giving us the option to assign to a Regular tenant to avoid a D&L to move the data as this is time consuming; but then...
Thanks Cringer, I have that one printed sitting by my desk at work :) It did answer a lot of unknowns; I guess I just didn't want to believe I have to D&L to initially move data from Default to Regular tenant.
Hello,
Working on enabling multi-tenancy in our environment, we are running OE 11.3.3.
We have a few databases and for content ill add structure file here to support my question..
Database name: is db1
b /usr4/bi_test/db1.b1
d "Schema Area":6,64;1 /usr4/testdbs/db1.d1
a /usr4/ai_test/db1.a1...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.