...
- Stop source FlexDeploy server in order to take cold backup.
- Export data from source FlexDeploy database. You will be prompted to enter password for system user.
This step will create fd_bkup.dmp file with all details from FD,FF and FD_ADMIN schemas. File should be in data pump directory, for example - C:\oraclexe\app\oracle\admin\XE\dpdump.
Code Block language bash theme RDark title Export data from source FlexDeploy database expdp system directory=DATA_PUMP_DIR dumpfile=fd_bkup.dmp schemas=FD,FF,FD_ADMIN - Copy fd_bkup.dmp file to the target FlexDeploy database server in the data pump directory. (e.g. C:\oraclexe\app\oracle\admin\XE\dpdump)
- Import data into target FlexDeploy database. You will be prompted to enter password for system user.
Make sure there are no errors in import process. If there are errors, make corrections appropriately and restart import process.
Code Block language bash theme RDark title Import data in to target FlexDeploy databaseimpdp system directory=DATA_PUMP_DIR dumpfile=fd_bkup.dmp schemas=FD,FF,FD_ADMIN
- At this point the target FlexDeploy database should be an exact copy of the source database. Often times you will not need or want any of the execution details, so let's delete execution data using following commands. Make sure to run these commands on target FlexDeploy database. Keep in mind that in this process we have not copied artifact repository as goal was to not include execution details.
If there are errors in delete process below you can run it multiple times. In case of issues, please contact us at http://support.flexagon.com.
Code Block language sql theme RDark title Delete execution data in target FlexDeploy database delete from FD.PIPELINE_STAGE_STEP_EXEC_WFRQ; delete from FD.PIPELINE_STAGE_EXEC_INFO; delete from FD.PIPELINE_STAGE_STEP_EXEC; delete from FD.PIPELINE_STAGE_GATE_EXEC; delete from FD.PIPELINE_STAGE_EXEC; delete from FD.PIPELINE_EXEC; delete from FD.REL_SNAPSHOT_VERSION_REQ; delete from FD.REL_SNAPSHOT_VERSION; delete from FD.REL_SNAPSHOT; delete from FD.REL_BUILD_MONITOR; delete from FD.TEST_DEF_QUALIFIER_VALUE; delete from FD.TEST_RESULT; delete from FD.TEST_DEFINITION_RUN; delete from FD.TEST_SET_QUALIFIER_VALUE; delete from FD.TEST_SET_RUN; delete from FD.TEST_RUN; delete from FD.PLUGIN_EXECUTION_OUTPUT_VALUE; delete from FD.PLUGIN_EXECUTION_OUTPUT; delete from FD.PLUGIN_EXECUTION_LOG; delete from FD.PACKAGE_OBJECT_EXECUTION; delete from FD.PLUGIN_EXECUTION; delete from FD.WORKFLOW_EXECUTION_DATA; delete from FD.PACKAGE_OBJ_CURRENT_STATUS; delete from FD.WORKFLOW_EXECUTION; delete from FD.WORKFLOW_REQUEST_INPUT; delete from FD.SCHEDULED_TASK; delete from FD.HUMAN_TASK; delete from FD.FOLDER_REQUEST_CURRENT_STATE; delete from FD.PROJECT_WF_CURRENT_STATUS; delete from FD.WORKFLOW_REQUEST_INST; delete from FD.WORKFLOW_REQUEST_CMS_ISSUE; delete from FD.WORKFLOW_REQUEST; delete from FD.FOLDER_REQUEST; delete from FD.FOLDER_PROJECT_VERSION; delete from FD.PROJECT_VERSION_DATA_VAL; delete from FD.PROJECT_VERSION_DATA; delete from FD.PACKAGE_OBJECT; delete from FD.PROJECT_VERSION; delete from FD.FOLDER_VERSION; delete from FD.PURGE_FOLDER_VERSION_KEY; delete from FD.PURGE_PROJ_VERSION_KEY; delete from FF.SEQUENCE_BLOCK where SEQ_NAM like 'stream-%'; delete from FD_ADMIN.PS_TXN; commit;
- We will not copy any Artifact Repository in this process, as we are purging the execution data.
- FlexDeploy can now be installed in target environment as per FlexDeploy Installation Guide, but skip database tier as it was already copied from a different environment. You could do this step before database copy as well.
- At the end of installation process, start FlexDeploy and validate that your configurations are present in various screens.
- As necessary upgrade details like Security realm, group, user configurations, Email server settings etc.
...