Impact of P2T on Extensions

When it comes time to test your extensions, or new versions of your extensions, you might want to use the Oracle Production-to-Test (P2T) refresh process to copy data from your Production environment (the source environment) to a Test or Development environment (the target environment). This allows you to thoroughly test your extensions without disrupting the Production environment. (You can also use the process to move data from one Test or Development environment to another Test or Development environment (T2T)).

The P2T process copies the contents of the database in the Production environment to the database in the target environment. Here’s what happens during the process:

• All extensions on the target environment are replaced by the extensions from your Production environment. If the Production environment has older versions of extensions, they are copied over and effectively replace the versions on the target environment, even if the versions on your target environment are newer.
• Similarly, all metadata related to your extensions stored in the target environment’s database is overwritten by the metadata info from the Production instance’s database.

The P2T/T2T process copies only source environment’s database content, which means that none of these are affected:

• The source for your extension, which lives in your project’s Git repo
• Your CI/CD build jobs and pipelines
• The passwords to access the Test or Development environment.

During the P2T process, you won’t be able to access VB Studio on the target TEST or DEV instance for up to two days. However, you can use the instance of VB Studio associated with a different DEV or TEST instance in your environment family, assuming your user account has been added to the project you want to work in.