If your export file tries to exceed the OS maximum size, it will fail. People on platforms that typically run into this (Unix) will split the export file into multiple pieces (using a named pipe and split/gzip/etc) or have multiple export files and limiting the size of the export file.
Originally posted by marist89 or have multiple export files and limiting the size of the export file.
Do you mean have multiple export routines which exports the DB schema by schema or table by table. Please confirm.
No, I mean using exp with files=a1.dmp, a2.dmp, a3.dmp filesize=2000M ...
Export: Release 126.96.36.199.0 - Production on Fri Jun 21 11:27:57 2002
(c) Copyright 2000 Oracle Corporation. All rights reserved.
You can let Export prompt you for parameters by entering the EXP
command followed by your username/password:
Example: EXP SCOTT/TIGER
Or, you can control how Export runs by entering the EXP command followed
by various arguments. To specify parameters, you use keywords:
Format: EXP KEYWORD=value or KEYWORD=(value1,value2,...,valueN)
Example: EXP SCOTT/TIGER GRANTS=Y TABLES=(EMP,DEPT,MGR)
or TABLES=(T1:P1,T1:P2), if T1 is partitioned table
USERID must be the first parameter on the command line.
Keyword Description (Default) Keyword Description (Default)
USERID username/password FULL export entire file (N)
BUFFER size of data buffer OWNER list of owner usernames
FILE output files (EXPDAT.DMP) TABLES list of table names
COMPRESS import into one extent (Y) RECORDLENGTH length of IO record
GRANTS export grants (Y) INCTYPE incremental export type
INDEXES export indexes (Y) RECORD track incr. export (Y)
ROWS export data rows (Y) PARFILE parameter filename
CONSTRAINTS export constraints (Y) CONSISTENT cross-table consistency
LOG log file of screen output STATISTICS analyze objects (ESTIMATE)
DIRECT direct path (N) TRIGGERS export triggers (Y)
FEEDBACK display progress every x rows (0)
FILESIZE maximum size of each dump file
QUERY select clause used to export a subset of a table
The following keywords only apply to transportable tablespaces
TRANSPORT_TABLESPACE export transportable tablespace metadata (N)
TABLESPACES list of tablespaces to transport
Export terminated successfully without warnings.
Originally posted by marist89
Exporting a VLDB is futile. [/B]
Thanks a lot jeff [/B][/QUOTE]
Why would you want to spend 24 hours exporting a DB? The data will be so inconsistent that it will be wothless.
Another alternative I use (on Unix and some other systems, haven't done it on NT, but it should work) is to export to a tape device. It creates an unlabeled ANSI tape whose size is limited to the tape capacity. (In AIX, most times, use 'file=/dev/rmt0' or something like that.) In theory, that can be 80-100GB or more (depending on the drive.)
Joseph R.P. Maloney, CSP,CDP,CCP
'The answer is 42'