'sdetable -o create_view' should only really be used with SDEBINARY/SDELOB storage layers.
SQL is a much more powerful tool for view creation than what 'sdetable' provides.
For ArcGIS to operate correctly, 1:M joins need to return the same USER-set rowid value for the
same row with each query (no fast/loose games with ROWNUM). It's not well-enforced, but the
column is required to map to SE_INT32_TYPE (long integer). Use 'sdetable -o describe' on the
view to make sure the type mapping is correct.
The segmentation violations are disconcerting, as is the use of DBLINK, which will often perform,
shall we say, "poorly" (make sure you tune the query so that selection is occurring on the correct
side of the link).
That join where clause isn't at all pretty -- you might want to evaluate using a UNION ALL join
within the view (just make sure the returned rowids are unique).
- V