User Tools

Site Tools


console_output_for_export

Console Output For Export (and Extract)

During Export all changes to the source files are logged to the console. In Dry-Run mode Lure indicates the changes that need to be made to the files without actually doing so. Lure uses a concise four letter event code to indicate what changes were (or have to be) made to the source files. The following is a typical output:

TEST1/data/mviews/MVIEW_1.mv
 CU- MATERIALIZED_VIEW MVIEW_1
TEST1/nav/grants/TEST1.opr
 KA- OBJECT_PRIVILEGE TEST1.MVIEW_1
TEST2/nav/grants/TEST1.opr
E  A OBJECT_PRIVILEGE TEST1.MVIEW_1

For every file that is altered in any way Lure prints the relative path to this file on a single line, followed by one or more lines indicating which DDL statements within this file were updated, one line per DDL statement. The lines that represent the updated DDL statement consist of three parts:

  1. The first part is a four character event code describing the change that ocurred during the export (highlighted in yellow above).
  2. The second element indicates the type of object that was exported.
  3. The third element is the name of object that was exported.

The four character event code has the following meaning:

Column 1: Indicates the status of the object that was exported

<space> valid object or no status associated with DDL
E exported object has an invalid status in the database

Column 2: Shows information about incoming changes (changes in the source file).

<space> No incoming changes (changes in the source file) detected for the object.
K An incoming change (a change in the source file) was detected but not reverted. No outgoing change (change in the database) 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 source file.
O The incoming change was reverted and the outgoing change (if any) was applied to the source file. (Export Over)

Column 3: Shows the required change to the DDL statement in the file. The required change is only shown in this column if Lure was not able to make the change to the source file.

<space> Update succeeded.
A Statement for this object needs to be added to the source file but wasn't due to an incoming change.
D Statement for this object needs to be removed from the source file but wasn't due to an incoming change.
U Statement for this object needs to be updated in the source file but wasn't due to an incoming change.

Column 4: Actual change to DDL statement in file

- No change to the statement in the file.
A The DDL statement for this object was added to the source file (or needs to be in the case of Dry-Run).
D The DDL statement for this object was deleted from the source file (or needs to be in the case of Dry-Run).
U The DDL statement for this object was updated in the source file (or needs to be in the case of Dry-Run).
P A patch file was created. This file needs to be reviewed/edited by the user.
F A file error ocurred. This could be a parsing or other file level error which prevents Lure from processing this file.
Examples
Four letter event code Description of event
   A Statement for object was successfully added to the source file.
   U Statement for object was successfully updated in the source file.
 KD- An incoming change (change in the source file) for the object was detected but kept (not reverted). Therefore the statement was not deleted from the source file.
 O D In incoming change for the object was detected in the source file but this change was reverted by deleting the statement from the source file. (Export Over)
E  U Statement for object was successfully updated in the source file. The corresponding object was invalid in the database.
   P A patch file was created for the object/source file and needs to be reviewed/edited by the user.
   F A file level error occurred and the corresponding file or patch file could not be created/updated.
console_output_for_export.txt · Last modified: 2013/07/29 19:44 by admin

Page Tools