Hi folks,

We've got a workbench that's been working fine in FME for Oracle 2006 (20051216 build 2182) and have recently moved to a new processing server with FME for Oracle 2006 GB (20060620 build 2651).

The workbench runs fine for a short period and then exits with no error messages.  It exits before features are read from the database.  We get a warning/info message just prior to the tremination of processing:

Connected to ORACLE database `osmmt01'.
Using MultiWriter $Revision: 17.0 $ ( $Date: 2005/10/28 21:05:10 $ ) with keyword `MULTI_WRITER' to output data (ID_ATTRIBUTE is `TILE')
Writer output will be ordered by input dataset ordering.
Module `LogCount_func' API version matches current core version (3.1 20031010).
ORACLE_DEF line only defines partial search envelope; using global search envelope (from ORACLE_SEARCH_ENVELOPE directive).
Column `GEOLOC' of table `LIVE.CARTO_SYMBOL' has been chosen to hold the geometry.


On the 'old' processing machine this area of the log looks like:

Connected to ORACLE database `osmmt01'.
Using MultiWriter $Revision: 16.0 $ ( $Date: 2005/04/14 19:27:47 $ ) with keyword `MULTI_WRITER' to output data (ID_ATTRIBUTE is `TILE')
Writer output will be ordered by input dataset ordering.
Column `GEOLOC' of table `LIVE.CARTO_SYMBOL' has been chosen to hold the geometry.
The OGC definition of the FME coordinate system 'NonEarth_Meter' is 'PROJCS["British National...
Processing continues normally from here...

The only other difference between the two machines is the Oracle client versions - 10g Client on the new machine versus 9i CLient on the old one.

We're going to try reverting to the 9i client to see if that solves the problem but any clues to the cause of the problem would be appreciated.

Cheers,

Iain
__._,_.___

 



Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe

__,_._,___

Reply via email to