Note : This expanded capability is only available on Solaris systems at this time.
System Requirements/Recommendations:
Memory: 16GB RAM and 24GB swap
CPUs: 8 x 2.0 GHz UltraSPARC or SPARC64 VI/VII
eHealth Environment Variable Required
NH_STAT_POLLS_PER_SECOND = 600 (default is 300)
Sizing Procedure:
1) Use SWIZ to create an LCF file for a configuration with half the desired number of elements for the desired roll-up schedule (e.g. to size for 80,000 elements, run SWIZ for 40,000).
2) Edit the LCF file and duplicate the datafiles for the following tablespaces (keeping the same size and path but changing the name of each file):
a. NH_INDEX
b. NH_DATA01
c. NH_DATA02
d. NH_REG01
e. NH_REG02
f. NH_REG_INDEX01
g. NH_REG_INDEX02
For example (original files are black; new files are red):
NH_INDEX 10659M /export/yen02/oradata/{SID}/NH_INDEX01.dbf
NH_INDEX 10659M /export/yen02/oradata/{SID}/NH_INDEX02.dbf
NH_DATA01 16101M /export/yen03/oradata/{SID}/NH_DATA01a.dbf
NH_DATA01 16101M /export/yen03/oradata/{SID}/NH_DATA01b.dbf
NH_DATA02 4226M /export/yen04/oradata/{SID}/NH_DATA02a.dbf
NH_DATA02 4226M /export/yen04/oradata/{SID}/NH_DATA02b.dbf
NH_REG01 14050M /export/yen04/oradata/{SID}/NH_REG01a.dbf
NH_REG01 14050M /export/yen04/oradata/{SID}/NH_REG01b.dbf
NH_REG02 14050M /export/yen05/oradata/{SID}/NH_REG02a.dbf
NH_REG02 14050M /export/yen05/oradata/{SID}/NH_REG02b.dbf NH_REG_INDEX01 4501M /export/yen02/oradata/{SID}/NH_REG_INDEX01a.dbf
NH_REG_INDEX01 4501M /export/yen02/oradata/{SID}/NH_REG_INDEX01b.dbf
NH_REG_INDEX02 4501M /export/yen03/oradata/{SID}/NH_REG_INDEX02a.dbf
NH_REG_INDEX02 4501M /export/yen03/oradata/{SID}/NH_REG_INDEX02b.dbf
Note : The datafile names must be unique. This is done via a unique suffix in the name of the file. These are shown in green in duplicated files.
CAUTION: The SWIZ utility performs a check to ensure that there is sufficient space on each path. When the LCF file is modified as specified above, a manual check must be performed to ensure that there is sufficient space for the new files. If there is not, alternate paths can be created and used.
3) Use the new LCF file to create the database as usual.
.