Which three actions are mandatory post database upgrade?

Question

Options

• AUpdating client scripts with the new Oracle home.
• BResetting passwords to enforce case-sensitivity.
• CRun OPatch commands from the new Oracle home.
• DSetting threshold values for tablespace alerts.
• EMigration to unified auditing.
• FUpgrading user tables that depend on Oracle-maintained abstract data types.

• A
  69% (27)
• B
  5% (2)
• D
  8% (3)
• E
  18% (7)

Explanation

After a database upgrade, three actions are mandatory because they directly affect the functional integrity of the new environment. A is required because client scripts referencing the old Oracle home path will break - the new Oracle home must be reflected in all scripts that invoke Oracle binaries or utilities. C is required because OPatch is home-specific; patching operations must always be run from the new Oracle home to apply patches to the correct installation. F is required because Oracle-maintained abstract data types (e.g., SDO_GEOMETRY, XMLType) may have changed between versions - any user tables built on these types must be upgraded to stay compatible with the new database internals.

The distractors are wrong for these reasons: B (password reset) is a security recommendation, not a mandatory upgrade step; D (tablespace alert thresholds) is routine DBA housekeeping unrelated to the upgrade process; and E (unified auditing migration) is optional - mixed-mode auditing remains supported post-upgrade, so the migration is not forced.

Memory tip: Think of the acronym "ACF - Always Check the Foundation" - update scripts pointing to the new Address (home), run Commands from the new home, and Fix tables tied to Oracle's own types. If the action could be done on any normal Tuesday without an upgrade, it's probably not mandatory.

No community discussion yet for this question.