load database has the following limitations when used with an archive database:
The database dump for an archive database
is required to be a disk dump on a file system mounted on the local
machine. This can be local storage or NFS storage. load
database ... at <remote server> syntax is not
supported, nor are database dumps on tape.
Cross-architecture loads are not supported. The database dump and the load database command must be performed on the same architecture with respect to byte ordering.
The database that was dumped must have the same page size as that used by the server that is hosting the archive database.
The major version of the server on which the dump was taken must be earlier than or equal to the major version of the server hosting the archive database.
The character set and sort order on the server on which the database dump was taken must be the same as the character set and sort order of the server hosting the archive database.
The maximum size of any stripe in the database dump cannot exceed 32GB.
If the stripes are bigger than 32GB, specify additional
stripes when you issue a dump database command.
That way, the size of each stripe is reduced such that it may fall
within the maximum size.
