Ignite-UX (IUX) Frequently Asked Questions (July 2013)

'/dev/async' device file (which will be used in the examples below).
You do have several options:
1. Change your per-system post recovery instructions to remind you to
look at the setting of '/dev/async' (the minor number) to ensure
it is as it should be for this system.
2. Write a startup script that looks at '/dev/async' and verifies
that it has the minor number you would expect. If it is not the
expected value, recreate it in the startup script.
It is important to note that anyone can run the 'insf -e' command
that would create this device file, not just Ignite-UX during a
recovery.
Note: If the '/dev/async' device file needs to be customized, make
the change before the database starts.
=============================================================================
==
4.13
Q: How do I recover a system which has Cluster-wide Device Special File
(cDSF)
configured?
A: Starting from Version 7.16.x Ignite-UX supports cDSF. No additional steps
are required to recover a system on which cDSF have been configured. The
consistency of cDSF is not checked across the systems sharing the storage
during recovery and the cDSF are not synchronized. The user is responsible
for ensuring the same.
=============================================================================
==
----------------------------------------
5. General Installation
----------------------------------------
5.1
Q: How does Ignite-UX estimate needed file system sizes? Does it do
anything other than add up the impacts statements?
A: Ignite-UX adds in minfree (normally 10%) to the amount required by
the software impact.
You may have software bundles that have overlapping contents:
filesets and/or files. The make_config command makes sw_impact
statements for each bundle without doing anything special to guard
against over-counting when the bundles overlap.
For example, the Ignite-UX-11-XX bundles all overlap so when you
install all of them using Ignite-UX it estimates too much space.
You should be able to add the sw_impact of all the sw_sels that you
are installing and to calculate the required file system size.