SourceControl for Oracle 4.0.3 Reports Table Difference when LOB storage is included

mbruegel

SourceControl for Oracle 4.0.3 always reports a table difference between the DB and the SourceControl (SVN) repository when LOB storage is included and the table has a LOB segment.

There is no actual difference in the TABLE DDL -- in fact a commit (to subversion / SVN) returns a "Nothing to Commit" error.

Why does Source Control for Oracle identify a difference?  I even navigated to the WorkingBase and Transients for the project and they are fully up to date; showing no differences.

Update: upgraded to version 4.0.7 and am still encountering the same issue.

mbruegel

Additional clarification on this issue:

My actual column is an XML column.  The LOB reference points to a shadow column that Oracle creates for XMLType columns behind the scenes -- and not the actual column name.

See attached file, RG_ScourceControlOracle_sample_DDL_SQL.txt, for sample DDL (you will need to adjust the tablespace arguments for your environment) that illustrates this behavior.

The shadow column appears in the user_tab_cols dictionary view, but not in the user_tab_columns dictionary view.

I would expect the DDL captured by RedGate to reference the actual XML column name vs Oracle's shadow column. 

As a side note a lob_segment name (if specified) -- for any type of LOB column -- is not captured in RegGate's DDL generation.even if the LOB and tablespace options are selected.

ScourceControl differences identified -- none are visible:
(same results if using SchemaCompare)

RichardL

Hi @mbruegel

Thanks for your post. 

 

This looks like a question that one of Support engineers will need to investigate for you.

 

If you have a support contract, please send us a ticket. Provide as much information as you can - screenshots of any errors, log files etc – so we can help you as fast as possible.

If you're not covered by a Support contract at the moment, email our Sales team at sales@red-gate.com, and they'll be able to help.