5
Export and Import Utilities

Running Under UNIX System Services

When running Export under USS, considerations are the same as described in the Oracle9i Database Utilities manual.  Refer to Chapter 4, " Accessing Oracle9i Under USS", for general information about running utilities in the USS environment.

Running Under TSO

The syntax for running Export under TSO is:

EXP [userid[/password[@connect-string]]

where:

The normal OS/390 EOF key sequence, /*, ends the Export utility from any prompt.  The alias of EXP is ORAEXP.

Running in Batch

Export is supported in the batch environment through the ORAEXP JCL procedure.  The following is a copy of this procedure:

//ORAEXP   PROC INDEX=oran, 

//              LIBV=orav, 

//              SYSOUT='SYSOUT=*', 

//              USERID='NAME/PASSWORD'

//ORAEXP   EXEC PGM=EXP,REGION=4M,

//              PARM='&USERID' 

//STEPLIB  DD   DSN=&INDEX..&LIBV..CMDLOAD,DISP=SHR 

//ORA$LIB  DD   DSN=&INDEX..&LIBV..MESG,DISP=SHR

//SYSOUT   DD   &SYSOUT,DCB=(LRECL=132,BLKSIZE=1320,RECFM=VB) 

//SYSERR   DD   SYSOUT=*,DCB=(LRECL=132,BLKSIZE=1320,RECFM=VB) 

//ORAPRINT DD   SYSOUT=* 

To run this JCL procedure, you must include additional DD statements that refer to other required data sets.  The following example assumes the Oracle9i database server is installed with a system identification (SID) of ORA1:

//USER1JOB JOB  ........ 

//STEP1    EXEC ORAEXP, 

// PARM='SCOTT/TIGER PARFILE=/DD/PARFILE'

//ORA@ORA1 DD   DUMMY 

//SYSIN    DD   DUMMY

//EXPTFL   DD   DSN=userid.EXPDTFL.TEST,

//              DISP=(NEW,CATLG,DELETE),

//              VOL=SER=TEMP01,UNIT=SYSDA,

//              SPACE=(TRK,(5,5),RLSE),

//              DCB=(RECFM=FB,LRECL=4096,BLKSIZE=24576)

//PARFILE  DD   *

DIRECT=N

BUFFER=10240

FILE=/DD/EXPTFL

GRANTS=Y

INDEXES=Y

ROWS=Y

CONSTRAINTS=Y

COMPRESS=N

FULL=N

TABLES=(DEPT)

/*

In this example, Oracle user SCOTT with password TIGER performs an Export of data from the database instance whose OSDI service SID ORA1.  The Export parameters reside in PARFILE instream data.  As an alternative, the Export responses can be included as SYSIN instream data.

To further illustrate, you can use Export in two ways:

• Enter the command EXP user name and password PARFILE=filename with the remaining Export parameters contained in the specified file.  This is the preferred method.  If you use this method, then PARFILE cannot be a PDS member.

• Enter the command EXP user name and password followed by various parameters that control how Export runs.  You can use this method as long as the number of parameters does not exceed the maximum length of a command line on your system.  The parameter redirection attribute ++ can be used to redirect parameters to the input file.

For more information on using Export, refer to Oracle9i Database Utilities.

Return Codes

Export issues the following return codes:

Exporting to Non-OS/390 Systems

When exporting to non-OS/390 systems, ensure the data transfer process does not result in the translation of the Export file from EBCDIC to ASCII or from one EBCDIC character set to another.  This translation, if necessary, is provided by the Import utility on the receiving system.  If an external translation is performed, then Import ends with an irrecoverable error and you receive the following error message:

Seals don't match

You must also ensure Exports to other operating system environments are done on compatible media.

Running Under UNIX System Services

When running Import under USS, considerations are the same as described in the Oracle9i Database Utilities manual.  Refer to Chapter 4, " Accessing Oracle9i Under USS", for general information about running utilities in the USS environment.

Running Under TSO

The syntax for running the Import utility under TSO is:

IMP [userid[/password[@connect-string]]

where:

Use the normal OS/390 EOF key sequence (/*) to end the Import utility from any prompt.  The IMP alias is ORAIMP.

Running in Batch

Import is supported in the batch environment through the ORAIMP JCL procedure. A copy of this procedure is:

//ORAIMP   PROC INDEX=oran, 

//              LIBV=orav, 

//              SYSOUT='SYSOUT=*',

//              USERID='NAME/PASSWORD' 

//ORAIMP   EXEC PGM=IMP,REGION=4M,

//              PARM='&USERID' 

//STEPLIB  DD   DSN=&INDEX..&LIBV..CMDLOAD,DISP=SHR 

//ORA$LIB  DD   DSN=&INDEX..&LIBV..MESG,DISP=SHR

//SYSOUT   DD   &SYSOUT,DCB=(LRECL=132,BLKSIZE=1320,RECFM=VB) 

//SYSERR   DD   SYSOUT=*,DCB=(LRECL=132,BLKSIZE=1320,RECFM=VB) 

//ORAPRINT DD   SYSOUT=*  

The following JCL illustrates the use of the previous procedure:

//USER1JOB JOB  ........ 

//STEP1    EXEC ORAIMP, 

//              USERID=,

//              PARM='PARFILE=/DD/PARFILE' 

//ORA@ORA1 DD   DUMMY 

//SYSIN    DD   DUMMY

//EXPTFL   DD   DSN=userid.EXPDTFL.TEST,DISP=SHR

//PARFILE  DD   *

USERID=SCOTT/TIGER

BUFFER=10240

FILE=/DD/EXPTFL

SHOW=N

IGNORE=N

GRANTS=Y

INDEXES=Y

ROWS=Y

FULL=Y

COMMIT=Y

/*

In this example, data is imported to the database instance whose OSDI service SID is ORA1.  The Import parameters reside in PARFILE instream data.  These responses can alternatively be specified as SYSIN instream data.

To further illustrate, you can use Import in two ways:

• Enter the command IMP user name and password PARFILE=filename with the remaining Import parameters contained in the specified file.  This is the preferred method.  If you use this method, then PARFILE cannot be a PDS member.

• Enter the command IMP user name and password followed by various parameters that control how Import runs.  You can use this method as long as the number of parameters does not exceed the maximum length of a command line on your system.  The parameter redirection attribute ++ can be used to redirect parameters to the input file.

For more information about Import, refer to Oracle9i Database Utilities.

Return Codes

Import provides one of the following return codes:

Importing from Non-OS/390 Systems

When importing from non-OS/390 systems, ensure your data transfer process does not translate the Export file from ASCII to EBCDIC.  This translation, if needed, is provided by the Import utility on the OS/390 system.  If an external translation is performed, then Import ends with an irrecoverable error and you receive the following error message:

Seals don't match 

You must also ensure Exports done for eventual Import to OS/390 environments are done on compatible media.