...
Restore routinely selected database content from the full backup to the shore production transfer schema. - DBA
Info |
---|
Nota bene. The expectation is that the data staged will contain the new expedition, QAQC, and 999 (operational test expedition). In some cases, data is included from a prior expedition.
Presently a common edge case with poor automation. Tread lightly. Check your work. |
Once staged extract, transfer, and load scripts may be run.
...
The data is first imported into a test database instance in the transfer schema. After the data has been remediated to support moratorium concerns, a snapshot of this data may be exported for re-use. The export will be re-imported into the production databasefor re-use. The export will be re-imported into the production database.
Code Block |
---|
sql my_dba@instance
dp export -directory dmpdir -dumpfile ###-transfer.dmpdp -schemas transfer -filesize 15gb |
After completing the above export from the selected test instance, complete these commands at the production instance (LIMSHQ).
Code Block |
---|
sql my_dba@instance_dba@limshq call transfer.util_cleanout_transfer_new_tables(); dp exportimport -directory dmpdir -dumpfile ###-transfer.dmpdp -logfileschemas 400-transfer-export.log -schemas transfer -filesize 15gb -nameexpr table="like 'NEW__%'" -includemetadata false -includerows true |
chk_tablespace_free.ksh
Review the space available in LABWARE, LABWAREIDX.
...