SAP Note 18743 - SAPDBA: export/import/reorg. with extra tapes

Symptom:

Export to tape with extra tapes

Solution
Subsequent tape management during an export to tape and import from tape is NOT currently supported by SAPDBA!

However, it is not explicitly prevented, either - instead, the properties of ORACLE exp and imp determine whether the export to or import from several tapes is possible.
If you select the option "Export on tape" in the SAPDBA export or reorg. menu, the program prompts you to specify the tape size, which SAPDBA passes directly on to ORACLE exp. It requires the tape size in order to hold the backup before the physical end of the tape is reached and request a new tape.

If you specify a too large tape size, exp runs to the end of the tape and terminates with an error.
If you specify the tape size correctly (or, for safety's sake, somewhat smaller), then SAPDBA checks whether the data for backup (the total of all the extent sizes) fits in the specified tape size.
If the data fits, the export is performed immediately. If the check shows that the total of all extents for export is larger than the tape size, SAPDBA issues a warning message and asks whether the export should be attempted anyway.

It is possible, for example, that several of the extents belonging to the table are empty or not completely full, which means that the export would still fit on a single tape. It is also possible, however, that an additional tape is required.

What ORACLE exp/imp then does with this tape/these tapes, and how the tapes are managed, are irrelevant for SAPDBA. SAPDBA merely passes control on to exp/imp, waits until exp/imp is finished, and then checks the return code AND the exp/imp log(!) to make sure no errors occurred.

When serious errors occur, SAPDBA will terminate unconditionally; other warnings and minor errors during the exp/imp are reported by SAPDBA, the user must either terminate SAPDBA or confirm that the program should continue.

Therefore, the use of extra tapes is entirely possible, provided that this is supported by ORACLE exp/imp. You must, however, make sure that the tapes are managed properly and in the correct order. SAPDBA considers all the tapes as a single unit, and does not write any header information of its own.