User`s guide

SQL Error Recognition During Sybase Database Imports
Sybase Exports Data Export User’s Guide
7-2 Version 5.0rev1
SQL Error Recognition During Sybase Database
Imports
When you export to Sybase, initially an export to ASCII is performed. Next, a
series of SQL commands is generated to create tables, copy data and add
indices. The commands are executed and a log of the execution is stored in
<deffile>_import.log (where <deffile> is the name of the definition
file). This log file is searched for errors. If any errors are found, they are placed
in the <deffile>.log file and the following message is displayed:
ÒSybase completed with possible errors detected. Examine
<deffile>_import.log file for actual errors.Ó
See Checking Export Output on Page 4-7 for more information.
Loading and Accessing Sybase Tables
Data Export uses its own Sybase user ID to create and load your Sybase
tables. This user ID must be added (via sp_addlogin) by your database
administrator. The Sybase account must be created with a user ID of
spectrum and a password of cabletron. The spectrum user ID must own
the database into which data is imported or have create table permission. The
following is the syntax for the sp_addlogin command:
sp_addlogin spectrum, cabletron, <db_name>, null, ÒSpectrum Data ExportÓ
To keep other data secure, it is recommended that your database
administrator revoke privileges to the spectrum user ID for any non-
SPECTRUM data.
After you run Data Export, the spectrum user ID owns the newly created
tables. Your database administrator should use the Sybase grant command to
allow access to the tables.
Data Export uses the Sybase bcp utility to load database tables. To use the
bcp utility, the Sybase option select into/bulkcopy must be set on. See your
database administrator to make sure database options are set correctly. See
your Sybase documentation for other restrictions and recommendations about
the bcp utility.
You should be aware of any restrictions imposed by the Sybase Database
Management System, such as reserved words and naming conventions. See
the appropriate Sybase manuals for information.