What's a good checklist of things to verify in an IFS environment after performing a database refresh (e.g., copying Production data down to a lower environment), to confirm the refresh 'took' correctly and the environment is properly configured for its own purpose?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Check the following against what the target environment should actually have (not what was copied over from the source): batch queue configuration; delivery/component differences (via the Installed Components window, since environments can legitimately be on different code levels); System Parameters, the PLSQLAP_ENVIRONMENT_TAB table, and IFS Connect configurations; License Management window information; the Connect server's listener port (Setup IFS Connect window); database backup method configuration and archive log parameters; undo tablespace names; and Oracle directory object names/paths. These commonly get silently overwritten by a refresh from a different environment (like Production) and need to be reset back to values appropriate for the target environment. If you have customized tables or environment-specific custom data, those need a separate verification pass as well, since this list only covers standard IFS configuration areas.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions