User`s guide

SQL Error Recognition During Oracle Database Imports
Oracle Exports Data Export User’s Guide
8-2 Version 5.0rev1
• On the NT platform only, the ORALOAD_VER variable must be
uncommented. Add the version number of Oracle SQL*Loader to the right
of the = sign. Only the first two digits are required, and they must be
enclosed in quotes. For example, the variable line for SQL*Loader version
number 7.1.4.0.0 should read ORALOAD_VER=Ò7.1Ó.
• If you want Models exports to display more than the first 32 characters of
model names, you must change the value of the SDE_OUTPUT_MODEL_LEN
variable. For Oracle, you can specify display of up to 1024 characters.
When this script executes, the Oracle environment variables are exported and
the Oracle bin area is added to the user's PATH environment variable.
SQL Error Recognition During Oracle Database
Imports
When you export to Oracle, 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:
ÒOracle 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 Oracle Tables
Data Export uses its own Oracle user ID to create and load your Oracle tables.
This user ID must be added by your database administrator. The Oracle
account must be created with a user ID of spectrum and a password of
cabletron. The following is the syntax for the create user command:
create user spectrum identified by cabletron
The spectrum user ID must own the database into which data is imported. In
addition, the spectrum user ID must have the create session and create
table system privileges.
To keep other data secure, it is recommended that your database
administrator revoke privileges to the spectrum user ID for any non-
SPECTRUM data.