Dear IFS Experts, We are currently upgrading two IFS customers: one from IFS 9 to IFS Cloud and the other from IFS 10 to IFS Cloud. Both customers are already hosted in the IFS Managed Cloud, and they will continue to be hosted there after upgrading to IFS Cloud. This means we cannot upgrade directly on the IFS use place production environment in the Managed Cloud. Instead, we have to use an interim database outside of the Managed Cloud to run the upgrade scripts. This approach requires us to: Export (Data Pump) the current database (based on IFS 9 or IFS 10). Upload the dump file to Azure Storage. Download the dump file from Azure Storage to the interim environment to prepare for the upgrade. Import the dump file to the interim database. Perform the upgrade. Complete all validations. Create an Oracle PDB Archive file as per the IFS Managed Cloud procedure. Upload the PDB Archive file to Azure Storage. Download the PDB Archive file from Azure Storage to the IFS live production environment. Plug the PDB Archive file into the production database, following the IFS Cloud Team’s process. Make the upgraded environment available for the customer to complete all necessary post-upgrade tasks before allowing end-users to start working with IFS Cloud. Considering the size of the databases (one around 700 GB and the other around 1.7 TB) and the nature of the customers' business, the technical steps alone take several days, especially because the upgrade has to be performed in an interim environment. We are seeking your experiences and any tips to reduce downtime, particularly around database export/import. Note: For your information, IFS Managed Cloud applied an Oracle patch to the existing live databases of these customers, which significantly improved the Data Pump export time. However, we haven't found an effective solution to reduce import time, despite increasing server resources and parallelism. Some heavy indexes take a long time to create during the import. Additionally, after the upgrade, creating the PDB Archive file takes time due to compression, and as per our DBA, this process works on a single thread. The IFS Managed Cloud team also needs several hours to plug the PDB Archive file into the production environment. We would highly appreciate it if anyone has tested and proven methods to further reduce the total downtime for the customer. Thanks in advance!

Upgrade IFS from earlier version to IFS cloud || Reduce Time for Technical Upgrade

Dear IFS Experts,

We are currently upgrading two IFS customers: one from IFS 9 to IFS Cloud and the other from IFS 10 to IFS Cloud. Both customers are already hosted in the IFS Managed Cloud, and they will continue to be hosted there after upgrading to IFS Cloud. This means we cannot upgrade directly on the IFS use place production environment in the Managed Cloud. Instead, we have to use an interim database outside of the Managed Cloud to run the upgrade scripts.

This approach requires us to:

Export (Data Pump) the current database (based on IFS 9 or IFS 10).
Upload the dump file to Azure Storage.
Download the dump file from Azure Storage to the interim environment to prepare for the upgrade.
Import the dump file to the interim database.
Perform the upgrade.
Complete all validations.
Create an Oracle PDB Archive file as per the IFS Managed Cloud procedure.
Upload the PDB Archive file to Azure Storage.
Download the PDB Archive file from Azure Storage to the IFS live production environment.
Plug the PDB Archive file into the production database, following the IFS Cloud Team’s process.
Make the upgraded environment available for the customer to complete all necessary post-upgrade tasks before allowing end-users to start working with IFS Cloud.

Considering the size of the databases (one around 700 GB and the other around 1.7 TB) and the nature of the customers' business, the technical steps alone take several days, especially because the upgrade has to be performed in an interim environment.

We are seeking your experiences and any tips to reduce downtime, particularly around database export/import.

Note: For your information, IFS Managed Cloud applied an Oracle patch to the existing live databases of these customers, which significantly improved the Data Pump export time. However, we haven't found an effective solution to reduce import time, despite increasing server resources and parallelism. Some heavy indexes take a long time to create during the import. Additionally, after the upgrade, creating the PDB Archive file takes time due to compression, and as per our DBA, this process works on a single thread. The IFS Managed Cloud team also needs several hours to plug the PDB Archive file into the production environment.

We would highly appreciate it if anyone has tested and proven methods to further reduce the total downtime for the customer.

Thanks in advance!

Be the first to reply!

Reply

Did you find what you're looking for? If not:

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded