Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
DAVID GROVE — — source: IIUG Forums & Mailing Lists
IDS 12.10.FC12
Solaris 10 1/13
Consider an instance in which the logical and physical logs are retained in
the rootdbs.
Do you think there would be any benefit in moving the logs to their own
dbspaces, IF those spaces were still on the SAME SPINDLE as the rootdbs?
DG
Hello.
There are no performance benefits on your case.
But, as a best practice, is always recommended, easing administration (you can
even use an auto-extendable dbspace for your logs and their chunks).
It might be painful to grow your root dbspace, let it simple.
My opinion? Keep rootdbs as small as possible, and separate physical log in
one dbspace, and logical logs in other(s).
HTH
Best regards
Alexandre Marini
I almost forgot one important thing: security!
If you, for any reason, be with one offline chunk on your logical log dbspace,
for example, your engine might not crash!
A good point, right?
HTH
Best regards
Alexandre Marini
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.