DBA Data[Home] [Help]

APPS.MIGRATE_BATCH dependencies on GME_TEMP_EXCEPTIONS

Line 36: -- Messages are logged to gme_temp_exceptions.

32: -- migration. This is for purposes of validation, so that the user can find all data
33: -- conditions that exist without changing data. Call migrate_batch.run(p_commit => TRUE)
34: -- and this will migrate data with a commit at each phase of migration.
35: --
36: -- Messages are logged to gme_temp_exceptions.
37: -- Message types are: 'P' for progress, 'I' for information, 'E' for error, and 'D' for
38: -- unexpected error. 'D' will come from WHEN OTHERS exception block and there can only be
39: -- one 'D' because WHEN OTHERS do a RAISE and will not continue processing further. This
40: -- will typically occur because of unexpected SQL errors.

Line 116: INSERT INTO gme_temp_exceptions

112: ELSIF p_procedure_name = 'reset_GME_validated' THEN
113: reset_GME_validated;
114: END IF;
115: ELSE
116: INSERT INTO gme_temp_exceptions
117: (table_name,
118: procedure_name,
119: parameters,
120: message,