...
| Info |
|---|
This process should only be followed to perform configuration setup for brand new installation of FlexDeploy from another installation of FlexDeploy. Purpose of this document is to only copy configuration details and not execution data. If you run this against active Production FlexDeploy, you will lose all execution details. This process is only applied for 4.0, 4.0.x version of FlexDeploy. Also, source and target version of FlexDeploy must be same. |
- 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 | ||||
|---|---|---|---|---|
| ||||
expdp system directory=DATA_PUMP_DIR dumpfile=fd_bkup.dmp schemas=FD,FF,FD_ADMIN |
- Copy fd_bkup.dmp file on to target FlexDeploy database server in to data pump directory, for example - C:\oraclexe\app\oracle\admin\XE\dpdump.
- Import data in to 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 | ||||
|---|---|---|---|---|
| ||||
impdp system directory=DATA_PUMP_DIR dumpfile=fd_bkup.dmp schemas=FD,FF,FD_ADMIN |
- At this point target FlexDeploy database should be copy of source database. But in this scenario, we do not need any execution details, so let's delete execution data using following commands.
- We will not copy any Artifact Repository in this process, as we are not copying any 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.