Question 520
A postincident review documents: An Oracle modernization project targets a PostgreSQL engine without an inventory of PL/SQL packages and stored procedures. Which ongoing check targets the underlying failure?
Explanation
Correct Answer
Assess engine-specific code and dependencies at migration discovery. The original failure arose from: The project evaluates table storage but ignores nonportable SQL and application logic. The control reduces that failure mode.
Incorrect Answers
The proposed check would maintain a function and expression compatibility catalog for database rewrites, helping with cases where an application ported from MySQL to PostgreSQL fails because string concatenation and date expressions have different syntax. The recurring exposure described here is that the project evaluates table storage but ignores nonportable SQL and application logic.
For the situation in which a migration team bases its schedule on a 10-GB sample although the real database contains several terabytes, it makes sense to size migrations using sampled throughput applied to verified production-scale footprints. Here, the project evaluates table storage but ignores nonportable SQL and application logic, so the safeguard misses the recurring fault.
The proposed check would include collation, encoding and sorting tests in heterogeneous migration acceptance, helping with cases where an old billing database uses a locale-specific case-insensitive collation that is not identical on the new engine. The recurring exposure described here is that the project evaluates table storage but ignores nonportable SQL and application logic.