Export Options for Constraints, Synonyms, Sequences, Views, and Grants 
Procedure
a |
- Incl. owners SYS,SYSTEM |
d |
- Working directory |
s |
- Start |
q |
- Return |
See
SAPDBA: Export MenuPreliminary Result
SAPDBA generates a restart file restart.exg and a log <timestamp>.exg. If an error occurs, you must repeat the structure export. You can later start an import of the objects using the scripts stored in restart.exg. If an error occurs, you can repeat the import process with the restart function (see
Restarting the Export/Import).If the objects have to be created in the database, use the SAPDBA function Import structures. You can also start the script individually (using the SAPDBA function Additional functions
® Execute SQL script). Objects that exist in the database are not overwritten by the import (see Data Consistency and Structure Import).Script Categories
During an export of the objects listed above, the following scripts are used (when required) or created for a later import or restart:

Constraint import command: Constraints are imported using commands with the form ALTER TABLE <owner>.<table name> ADD (<table constraint A>, <table constraint B>, ...
Sequence counter: Sequences are exported with their counters, the last number used in every sequence. Therefore, you should only export and import sequences along with the data that they refer to.
Views: The complete specifications of all views are included in an export. The export includes view columns, comments, grants, and inspection options (constraints with category V).
See
Restart File for Export/Import and SAPDBA Scripts and Files.