N(O_VALIDITY) do not restore database validity conditions

MO(DE) 'read_only' or 'read_write' access I(NACTIVE) deactivate indexes during restore FIX_FSS_M(ETADATA) fix malformed UNICODE_FSS metadata FIX_FSS_D(ATA) fix malformed UNICODE_FSS data T(RANSPORTABLE) transportable backup - data in XDR format OL(D_DESCRIPTIONS) save old style metadata descriptions NOD(BTRIGGERS) do not run database triggers G(ARBAGE_COLLECT) inhibit garbage collection CO(NVERT) backup external files as tables REP(LACE_DATABASE) replace database from backup file (restore) R(ECREATE_DATABASE) create (or replace if OVERWRITE used) C(REATE_DATABASE) create database from backup file (restore) B(ACKUP_DATABASE) backup database to file

Y redirect/suppress status message output USE_ do not reserve space for record versions

T transportable backup - data in XDR format N do not restore database validity conditions G[ARBAGE_COLLECT) inhibit garbage collection This need not be supplied if ISC_USER environment variable exists and has a correct value for the username. U Īllows the username of the SYSDBA or database owner user to be specified if the database is to be backed up, or, in the case of a restore (with the -c switch specified), any valid username can be specified. Not of much practical use and is not normally used in practice. RO Īllows the specification of the role to be used by the connecting user. This need not be supplied if ISC_PASSWORD environment variable exists and has the correct value. Supplies the password for the username specified above. This switch can be used when creating database clones which are required to contain only the tables, indices etc but none of the data. When used in a restore, any data in the dump file will not be restored. In a backup, only the database meta data are backed up. This switch causes your data to be ignored and not backed up or restored. Backup & Restore With & Without Shadow Files. Create a Database Clone Without a Dump File.

Sql bak file viewer