User Tools

Site Tools


console_output_for_import

Console Output for Import

During Import all changes to the database will be logged to the console. (In Dry-Run mode Lure will log to the console the required changes to the database without actually implementing those changes on the database.) The following is a typical output:

TEST1/data/mviews/MVIEW_1.mv
  UD MATERIALIZED_VIEW MVIEW_1
   A MATERIALIZED_VIEW MVIEW_1
TEST1/data/mviews/MVIEW_2.mv
  UD MATERIALIZED_VIEW MVIEW_2
   A MATERIALIZED_VIEW MVIEW_2
TEST1/nav/grants/TEST1.opr
   A OBJECT_PRIVILEGE TEST1.MVIEW_1
>CA- OBJECT_PRIVILEGE TEST1.MVIEW_2

For every file from which an object was imported Lure prints the relative path to this file on a single line, followed by one or more lines indicating the DDL statements within this file that were imported to the database, one or more lines per DDL statement. Each of these lines consists of four parts:

  1. In the first character column Lure indicates with a ”>” character whenever the final outcome of an object does not match the statement in the source file, in other words when importing of the object failed.
  2. The second part is a three character event code indicating the kind of change that occurred during the import.
  3. The third part indicates the type of object that was imported.
  4. The fourth part is the name of object that was imported.

The three character event code has the following meaning:

Column 1: Indicates whether outgoing changes (changes made directly in the database) are kept or reverted:

<space> No outgoing changes (changes in the database) detected for the object.
K An outgoing change (a change in the database) was detected but not reverted. No incoming change (change in the source file) was detected
C A conflict was detected, i.e. both an incoming change (change in the source file) and an outgoing change (change in the database) for the same object was detected. No change was applied to the database.
O The outgoing change was reverted and the incoming change (if any) was applied to the database. (Import Over)

Column 2: This column indicates the required change to the object. The required change information is only shown when it is different from the actual change as indicated in column 3. This column also indicates when a dependent change occurred:

<space> No action
A The statement/object from the source file needed to be added/installed to the database.
D The statement/object needed to be removed/dropped from the database.
U The statement/object from the source file needed to be updated in the database.
P A statement from a patch file needed to be executed in the database.
L A change to an object occurred because of a change in a dependent object.

Column 3: This column indicates the actual change that occurred:

- No change
A The statement/object was added to the database.
D The statement/object was removed/dropped from the database.
U The statement/object was updated in the database.
P A statement from a patch file was executed.
E An error occurred while importing the object from the source file.
F A file level error occurred and the file will not be processed any further.
Examples
Event Code Description of event
  A An object from the source file was successfully added/installed in the database.
KA- An outgoing change (change in the database) was detected for this object but kept. No incoming change (change in the source file) was detected or imported.
 UD The object needs to be updated. Lure dropped the object so that it can be installed again.
 CD- AThe object needed to be dropped but a conflict was detected, i.e. both incoming and outgoing changes were detected for the object . The object was not dropped.
 DE An object needed to be dropped but an error occurred.
 LD An object was dropped/removed from the database because a dependent object changed. (For example Oracle automatically drops a constraint on a column if the columns is dropped from a table.)
  P A statement in a patch file was successfully executed.
 PE An error occurred when trying to execute a statement from a patch file.
  F A file level error occurred and the file will not be processed any further.
O D In outgoing change for the object was detected in the database but this change was reverted by dropping the object from the database.(Import Over).
console_output_for_import.txt · Last modified: 2013/07/29 19:51 by admin

Page Tools