|
I can't answer your first question. The comments I would make about
putting all of [ALLIN1...] on an ESE20 are:-
There are some directories that are hardly ever touched such as those
defined by OA$BUILD, OA$DO, OA$SCP, OA$BLP and possibly the CBI
directories. It would seem reasonable not to put these on the ESE20.
Within the directories that are touched it is only a minority of files
that will be accessed - you will have seen this from the VPA hotfiles.
I don't know whether it is possible to separate these out from their
directories.
There are some system files that are recommended to go on an ESE20 -
SYSUAF.DAT, RIGHTSLIST.DAT and JBCSYSQUE.DAT.
I would guess that when the ESE20 is up and running there are some
possible tuning actions to take account of the faster I/Os - for
example reduce the number of global buffers on profile and pending
files, reduce the system block count for sequential files to 4 - the
principal file of interest here is OAFORM.FLB.
Mark
|
| Hi,
I have a long list of system type files that I am going to move.
With the ALL-IN-1 files, I felt it was better to move directories
rather than individual files just for maintenance reasons. That was
what I was thinking about when I ask about moving all of ALL-IN-1
over. So one does not ahve to worry about where things are during
upgrades, or changes.
Jerry
|