IFS documentation notes that Oracle has its own built-in scheduled job for gathering table statistics (GATHER_STATS_JOB), and IFS also has its own equivalent scheduled job — using both at the same time isn't recommended. How do you find which one is active, and how can statistics be checked or gathered manually for a specific object while diagnosing a performance issue?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Only one of the two mechanisms should be left enabled at a time — if keeping IFS's own statistics-gathering job, disable Oracle's built-in job (for example via DBMS_SCHEDULER.STOP_JOB('GATHER_STATS_JOB');) so both aren't running redundantly against the same tables. For manually inspecting or triggering statistics gathering on an individual database object — useful when diagnosing a specific performance issue and wanting to check whether that object's statistics are stale — use IFS's own 'Oracle Objects' screen, which lets you view and gather statistics for a specific selected object rather than only being able to run a schema-wide job.

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