Hello Hairless Ones,
I'd add that the key often in these situations is to look carefully at
the log. It should indicate the kind of query that Oracle was being
asked to do, and if I didn't know better, I'd wonder if somehow the
key fields weren't properly matched up originally. The original log
would indicate exactly how the query was being made.
There is also an internal debug option for the Joiner that could come
into play if we wanted to investigate it further if the problem
becomes reproducable -- but right now to use it we'd have to make the
workspace into a mapping file <mock shudder--sorry Peter L> and add it
in.
Dale
On 9/26/06, mark2atsafe <[EMAIL PROTECTED]> wrote:
>
> Hi Richard,
> Welcome to the land of the hairless - the natural state of those who
> work with spatial data.
>
> Do you have the original log file? It might give us a clue as to what
> was happening - whether it was a system failure of an fme related
issue.
>
> Mark
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/fme/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/fme/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
