Specifications

Corrected and Known Anomalies
Data Export
Software Release Notes Page 83
Problem 4: Exports to Sybase on the Windows NT platform fail because
the 10.0 /10.0.3 versions of Sybase Open Client do not correctly handle
the syntax, ! !, on Windows NT.
Solution: Aprisma recommends that you upgrade to Sybase Open Client,
Release 11.
Problem 5: When trying to export to SAS, it fails with error messages. A
syntax error in the SAS autoexec.sas file, config.sas, can cause these
messages. Examples of the messages are:
Mar 21 16:02:19 Description: Export Definition Description
SpectroSERVERS: svaa0026 0x2f80000
Mar 21 16:02:19 Begin Models export to model
Solution: Do not change the autoexec.sas file for data export as
inconsistent results may occur. This problem will be addressed in a future
release of SPECTRUM.
Problem 6: When SDE exports Models to an existing table, the existing
table is truncated rather than dropped, leaving intact the table column
characteristics. If you have increased the default model name length (via
the SDE_OUTPUT_MODEL_LEN variable in the dtxscript) and the ensuing
export contains models with names longer than the previous default, the
export will likely fail with an Oracle error indicating that the insert value
was too large for the column.
Solution: Manually drop the existing table and then perform the export.
This will establish the column width to the value specified in the dtxscript.
Problem 7: Statistical exports fail to SQL databases because of an
incorrect echo statement in the scripts that when run perform database
insertions.
Solution: In the echo_no_cr() function, there is a case statement with
the following line:
AIX|SunOS|ULTRIX) # berkeley; use -n option
The above statement should be changed to: