by Porus Homi Havewala Ever since Enterprise Manager 12c Release 5, released in June 2015, Oracle Enterprise Manager 12c (and now 13c, released in December 2015) allows an on-premise Enterprise Manager OMS (Oracle Management Service) to install Hybrid Cloud Agents on your Oracle Cloud Database servers. In this article series, we are looking at the steps for setting up and using the Hybrid Cloud via Enterprise Manager. In the previous part of this article series, we have gone through the pre-steps and then installed a Hybrid Cloud Agent. We discovered the databases and started to monitor the hybrid cloud. We then looked at configuration comparisons and configuration management for the Hybrid Cloud, as well as compliance standards enforcement. We started to discuss the cloning of PDBs back and forth from the cloud, and said that the PSU patch may need to be applied on the cloud database. However, please read the following note “Preserving the Agent Home when patching the Cloud Database” before you start the patching process on the cloud database. Note: Preserving the Agent Home when patching the Cloud Database: If you have installed the Enterprise Manager agent under /u01/app/oracle (the Oracle Base directory), and if you then use the cloud database patching menu to apply a later PSU to the database, then the Agent home will be moved to /u01/app.ORG/oracle as part of the database patching process. You can either move the agent subdirectory back manually after the patching is completed, or use the following workaround before you start the patching process: Login to the cloud database server as the oracle unix user, and create the file “/var/opt/oracle/patch/files_to_save.ora”. In this file, add the agent directory (full path) to preserve. Then, login to the cloud database server as the opc unix user. Issue the following commands: sudo -s cd /var/opt/oracle/patch vi dbpatchm.cfg In this root-owned file, locate these lines: # create /var/opt/oracle/patch/files_to_save.ora with full path of directory or # files to preserve any special files you may have in your /u01/app directory. # set this to yes, if you have files_to_save.ora special_files="no" Change the line special_files="no" to special_files="yes". Save the file. After you follow these steps, the next time you do any patching from the cloud database patching menu, the agent directory will be preserved in the original location and you will not need to move it back after the patching has completed. The Actual Cloning Log in as SYSMAN to the Enterprise Manager console. You can currently see both on-premise databases (ahuprod) and cloud databases (OPCTST) in a single pane of glass, as can be seen below in Targets.. Databases. Right-click on the on-premise PDB “SALES”, which is in the ahuprod CDB. Now for the actual cloning, which has been in-built into the menu. Select Oracle Database.. Cloning .. Clone to Oracle Cloud. The Source and Destination screen appears. Fill in the Credentials for the on-premise side, as well as the Cloud side. For the Cloud “Database Host credential”, be sure to use the “NC_OPC_DBCS” credential which has been pre-created with the local (OMS) server private and public keys. For the Cloud Database “SYSDBA Container Database credential”, create a new Named Credential using the sys password that you specified when you previously created the Cloud database. Enter the name of the new PDB on the cloud side as “SALESDEV”, since this will be a development pluggable database. Enter a more descriptive Display Name if you wish. Also select a user name and password for the PDB administrator of the new PDB. At this point, you can click on “Clone” to start the procedure. Instead of that, click on the “Advanced” button. This switches to Advanced mode, and a multiple page workflow appears. Click on Next. The “Clone to Oracle Cloud Configuration” page appears. As per Cloud database standards - that are based on the popular Oracle Flexible Architecture (OFA) standards, the PDB data files will reside on /u02, in the /u02/app/oracle/oradata/ directory. You can also enter storage limits if you wish. Click on Next. This page shows the importance of the Advanced mode, since it is possible to select a Masking Definition if it has been created for the source database. Masking is seamlessly integrated with Enterprise Manager. This makes sure that confidential data is masked when being cloned from an on-premise production database to a cloud development database. In the Schedule screen, you can select a future date or run immediately. The Review screen then appears. Click on Clone. The procedure starts to execute. The clone completes successfully in under 14 minutes (depending on the PDB size and the internet connectivity) as can be seen below. You can examine each step and its output if you wish. Note that the “rsync” unix command is being used by the procedure to fast-copy files to the cloud. When you move to Targets.. Databases, you can now see the new SALES Development PDB under the cloud OPCTST CDB. Drill down to the Sales Development PDB Home page. The Oracle Cloud icon is visible on the top of the page. Note that database performance details are not seen – since in this case, when the cloud database OPCTST was initially created, the plain Enterprise Edition database was selected instead of Extreme or High performance. The plain EE database in the cloud does not have the Diagnostics or Tuning pack licenses that are required for these features. Clone from Oracle Cloud Now, you can try the opposite. Go to the Cloud PDB, right-click, and select Clone from Oracle Cloud. You are now bringing the PDB back to on-premise. Select the correct credentials. Select “Advanced” mode once again. Go through the next few screens as before. Call the new on-premise database “SALESSTG”. It will be used as a staging database. The cloning of the PDB from the cloud now starts. The cloning from the cloud completes successfully in about 9 minutes (depending on factors such as the PDB size and internet connectivity). After the cloning completes, you can see the new SALE Staging PDB under the on-premise ahuprod CDB. In the next and final part VII of this article series, we will see how we can also unplug from on-premise, and plug into the Oracle Cloud database.
↧