| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: Copying a database from Oracle 6 on OS2 to Oracle 8 on NT
Stanleys <fstanley_at_dciexpress.com> wrote in message
news:7l6mj8$nkg$1_at_nnrp02.primenet.com...
> I have lots of experience administering MS SQL Server and Informix
> databases, but I'm just starting a project that will require me to learn
> Oracle for the first time. Can you help me get started by telling me how
I
> can copy an Oracle 6 database from an OS2 system to an Oracle 8 database
on
> NT (schema and data). If you could even just tell me the Oracle specific
> utilities that I'll have to use, I can probably take it from there.
See below
>
> Also, what is the default administrator user/password after installing
> oracle 8?
sys/change_on_install
system/manager
scott/tiger
>
use export from O6 and import into O8.
RTFM
This section describes guidelines and restrictions that apply when you import data from an Oracle Version 6 database into an Oracle8 Server. Additional information may be found in the Oracle8 Server Migration manual.
CHAR columns
Oracle Version 6 CHAR columns are automatically converted into the Oracle VARCHAR2 datatype.
If you pre-create tables from prepared scripts, the CHAR columns are created as Oracle fixed-width columns instead of the desired VARCHAR2 (variable-width) columns. However, if you set Version 6 compatibility mode before you run the creation script, variable-length columns are created instead of fixed-width columns.
LONG columns
Version 6 Export truncates LONG data when writing to the Export file. In Version 6.0.35.0 and higher, Export truncates LONG data to 64 kilobytes minus 3 bytes and issues a warning message. Earlier versions truncate data to 64 kilobytes minus 2 bytes and do not issue a warning message. Importing such long data may result in an error and cause the rest of the table to be skipped.
Syntax of Integrity Constraints
The SQL syntax for integrity constraints in Oracle Version 6 is different from the Oracle7 and Oracle8 Server syntax. Import automatically adjusts the declaration so that integrity constraints are properly imported into the Oracle8 Server, unless Version 6-compatibility mode is in effect.
Status of Integrity Constraints
Oracle Version 6 integrity constraints are imported with the status recorded in the export file. In Version 6, all constraints other than NOT NULL are disabled, and that status is recorded in the export file. NOT NULL constraints imported into Oracle are either ENABLED or DISABLED, depending on the status recorded in the export file.
Length of DEFAULT Column Values
A table with a default column value that is longer than the maximum size of that column generates the following error on import to Oracle8:
ORA-1401: inserted value too large for column
Oracle Version 6 did not check the columns in a CREATE TABLE statement to be sure they were long enough to hold their DEFAULT values so these tables could be imported into a Version 6 database. The Oracle8 Server does make this check, however. As a result, tables that could be imported into a Version 6 database may not import into Oracle8.
If the DEFAULT is a value returned by a function, the column must be large enough to hold the maximum value that can be returned by that function. Otherwise, the CREATE TABLE statement recorded in the export file produces an error on import.
Note: The maximum value of the USER function increased in the Oracle7 Server, so columns with a default of USER may not be long enough. To determine the maximum size that the USER function returns, execute the following SQL command:
DESCRIBE user_sys_privs
The length shown for the USERNAME column is the maximum length returned by the USER function. Received on Sun Jun 27 1999 - 21:56:10 CDT
 |
 |