Skip to main content

Oracle EBS Lift and Shift from On-Premises to Oracle Cloud OCI using EBS Cloud Manager-Part 2 (Advance Provisioning)

Oracle EBS Lift and Shift from On-Premises to Oracle Cloud OCI using EBS Cloud Manager-Part 2 (Advance Provisioning)

In one of the previous post I have shown how to use the EBS cloud manager to take backup from the On-Premises EBS environment.


Now with the help of EBS Cloud Manager we are going to provision the EBS Environment.

1) Lets go to backups and select appropriate compartment. We can observe that the EBS environment backup is available on Portal of EBS Cloud Manager. We will create Select Provision Environment.



2) Once the provision is selected, we are direct to a interactive page to provide required information. I have provided these values based on my environment.

Installation details:

Compartment Name
Network Profile
EBS Environment Name on Cloud
Make sure we select the Tab for Provision from Object Storage.
Provide the Backup Encryption password and the apps password from source system.
Also enter what would be new weblogic password.
Select the timezone as required.




3) Next we will need to provide the new database details and the shape of the machine.

For database we can have 3 options

1) Compute Server
2) DBCS Service
3) Exadata

The admin password will be new value as needed for the target environment.





4) Next screen we will be providing the information related to the Application Environment.

Add a zone and Loadbalancer.
Also we will be needed to add the storage option like shared or non-shared.





5) We will need to enter the required node name for application services and the system shape.






6) At extensibility option we can see the job definition being provided for VM DB System 



7) Next we will provide ssh key to connect to the server.



8) We will see. the summary of  our selections. In case we need to change any values we can go back and update the values.




9) Once click submit , as job will be triggered and start getting executed.

First it will complete the DB steps and then followed with the application steps.



10) To see the job status we can go to the jobs and see current running job and its progress.






11) Once the job is competed , now Validate the EBS environment and make sure services are running.











If you like please follow and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...
Post a Comment
Read more

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...
Post a Comment
Read more