Specifications

Data Export
Known Data Export Anomalies in SPECTRUM 6.0.2
SPECTRUM Software Release Notes Page 65
Windows NT as the client the export completes but you are unable to view
the table even though the table exists in the database. Since the Oracle
server is on UNIX and the client is on NT, this becomes a heterogeneous
environment when a homogenous environment is needed. You receive an
error message that says:
ÒError checking path homogeneity
ORA-02352: Direct path connection must be homogeneousÓ
Solution: Oracle exports in a heterogeneous environment (i.e., across NT
and UNIX platforms) are not supported. Both the Oracle client and Server
must be the same platform (i.e., NT to NT or UNIX to UNIX). (An NT client
export to a UNIX server will work in Oracle 8 but not in Oracle 7.) If
the client and server are not of the same platform, you must use a
conventional path load... “Use conventional path load.” This is discussed
in Chapter 9, “Direct Path Loads” of the Oracle 7 Server Utility User’s Guide.
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