Oracle E-Business Suite Lifecycle Management

This chapter covers the following topics:

Add and Delete Nodes

Use these procedures to add or delete nodes from a provisioned environment that has load balancing configured.

Note that adding and deleting nodes can both be done while the system is online. The system does restart the administration server during these procedures but the running Oracle E-Business Suite instance should not be affected.

Prerequisites

Add a Node

The Oracle E-Business Suite Cloud Manager performs the following actions when adding a node to your application tier:

In addition, the Cloud Manager modifies the load balancer back-end set to accommodate the new application tier node.

Note that if Manually Configured Load Balancer was chosen for the Web Entry Point, you can add nodes, but LBaaS is not deployed.

  1. For an environment that has been successfully provisioned, click the environment name in the Environments page to navigate to the Environment Details page.

  2. In the Topology tab, for a chosen Zone, click the Add Node button.

  3. In the Add Node window, enter the following:

    • Shape

    • File System Type - This value is derived for you and cannot be changed.

    • Fault Domain

    • Logical Hostname

    • APPS Password

    • WLS Password - For Oracle E-Business Suite Release 12.2 only.

  4. Click Submit.

    Manual Steps after Adding a Node

    You must perform the following manual steps after adding a node. Run these steps on all existing nodes.

    Update the TNS Listener Service

    1. Source the run file system.

    2. Run AutoConfig. This step is required to register the new node with the TNS listener and to update the APPL_TOP IDs correctly.

    3. Stop and start the TNS listener service as follows:

      $ cd ADMIN_SCRIPTS_HOME    
      $ adalnctl.sh stop    
      $ adalnctl.sh start

    Stop and Start the OHS Service

    1. Source the run file system.

    2. Run the following commands to stop and start the OHS service:

      $ cd ADMIN_SCRIPTS_HOME    
      $ sh adapcctl.sh stop    
      $ sh adapcctl.sh start

Delete a Node

In deleting a node, the system will:

In deleting an application tier node, the system also modifies the back-end set to account for the loss of the node.

  1. For an environment that has been successfully provisioned, click the environment name in the Environments page to navigate to the Environment Details page.

  2. In the Topology tab, navigate to the node you want to delete and click the Delete button.

  3. Enter the APPS Password. For Oracle E-Business Suite Release 12.2, also enter the WLS Password.

  4. If the selected node is the only node in its zone, specify whether to remove LBaaS. The load balancer is removed only if it is not in use by other resources.

    Note that any custom block volume associated with the node is detached from the node when it is deleted.

  5. Click Yes to confirm the deletion.

    Manual Steps after Deleting a Node

    You must perform the following manual steps after deleting a node. Run these steps on all remaining nodes.

    Update the TNS Listener Service

    1. Source the run file system.

    2. Run AutoConfig.

    3. Stop and start the TNS listener service as follows:

      $ cd ADMIN_SCRIPTS_HOME    
      $ adalnctl.sh stop    
      $ adalnctl.sh start

    Stop and Start the OHS Service

    1. Source the run file system.

    2. Run the following commands to stop and start the OHS service:

      $ cd ADMIN_SCRIPTS_HOME    
      $ sh adapcctl.sh stop    
      $ sh adapcctl.sh start

Clone an Oracle E-Business Suite Instance

The cloning procedure leverages the native Block Volume Cloning capability in Oracle Cloud Infrastructure, and is available only for environments where the Oracle E-Business Suite database and application tiers both reside on a Compute VM.

Note these additional key attributes:

Prerequisites

Access the Clone Environment Page

  1. Click the Navigator icon and select Environments.

  2. For a successfully created environment, click the Action icon and select Clone.

  3. Alternatively, in the environment details page for a single environment, click the Action icon and select Clone.

Enter Environment Details

  1. Enter values for the clone details:

    • Environment Name: Enter a name for your environment. For example: usdev3

    • EBS Compartment: The compartment for the source environment. This cannot be updated.

    • Network Profile Name: The cloned environment will use the same network profile as the source environment.

    • Source Apps Password: Enter the password for the Oracle E-Business Suite APPS schema for the source environment.

    • Source WebLogic Server password: For an Oracle E-Business Suite Release 12.2 environment only, enter the Oracle WebLogic Server administration password.

  2. Optionally enter tagging information in the Tags region.

    • Tag Namespace: Select a predefined tag namespace or select None (add a free-form tag).

    • Tag Key: Enter the name you use to refer to the tag.

    • Value: Enter the value for the tag key.

  3. Click Next.

Enter Application Tier Information

Zone information from the source environment will appear by default.

You can change the shape for an application tier node

  1. Toggle Start Application Tier Services to indicate whether application tier services should start when the clone is complete.

  2. You must edit the zones. Click Edit for each zone.

  3. Enter the Zone name. Note that you cannot change the type of the zone.

  4. In the Web Entry Point region, choose one of the following web entry types: New Load Balancer (LBaaS), Use OCI Load Balancer to select an existing OCI load balancer, Manually Configured Load Balancer to select a manually deployed existing load balancer, or Application Tier Node to choose the primary application tier as the entry point.

  5. If you choose to use LBaaS, then you must also select a shape in the Load Balancer Shape field. The default shape is 100Mbps.

  6. Enter values for the following web entry properties.

    • Protocol: Select the protocol for access to the environment, either http or https.

    • Hostname: Enter a hostname. For example: myhost

    • Domain: Enter a domain name. For example: example.com

    • Port: Select the port. If there is no load balancer, then the port is automatically populated depending on the protocol: 8000 for http and 4443 for https. Otherwise, select the appropriate port for use with your load balancer, such as 80 for http or 443 for https. Note that to allow access to the Oracle E-Business Suite login URL, your network administrator must define an ingress rule in the load balancer security list configuring the load balancer port to be open for public access. See Create Network Resources For Deploying Oracle E-Business Suite Environments.

  7. Under Storage, the File System Type is the same as that for the source environment.

  8. Review the properties for each node in the Application Tier Nodes information.

    • Logical FQDN

    • Shape: You can change the shape for the node. When choosing a flexible shape, for example VM.Standard.E3.Flex, you will use the sliders to choose 1) the Number of OCPUs and 2) Amount of memory (GB).

    • Storage

    • Fault Domain

  9. Click Save Zone.

  10. When you are finished editing your zones, click Next.

Specify Your Extensibility Options

You can optionally extend the cloning job to meet your own requirements. By default, Oracle E-Business Suite Cloud Manager follows a standard job definition for cloning. However, Oracle E-Business Suite Cloud Manager administrators can also create extended job definitions that include additional tasks as part of the cloning job. In this case you can select the appropriate extended job definition for Oracle E-Business Suite Cloud Manager to follow when cloning your environment. If you select an extended job definition, you may need to enter values for input parameters required by the additional tasks in that job definition.

Additional Information: For more information on using the Extensibility Framework to extend job definitions, see Set Up the Extensibility Framework.

Additionally, whether you are using the standard cloning job definition or an extended job definition, you can choose to have Oracle E-Business Suite Cloud Manager pause at specified points during the cloning job. For example, if you want to perform your own validations after a particular phase before allowing Oracle E-Business Suite Cloud Manager to proceed to the next phase, you can add a pause at that point. You can then resume the cloning job when you are ready to proceed. See Monitor Job Status.

Specify Your Job Definition

  1. Optionally select an extended job definition for cloning your environment in the Job Definition field.

  2. In the Task Parameters tab, specify any parameter values required for the additional tasks in the job definition. Some parameters may include default values, which you can override as needed.

Specify Your Job Definition Details

  1. Click the Job Definition Details tab. This tab displays a list of the phases in the job definition and the tasks within each phase.

  2. To specify that Oracle E-Business Suite Cloud Manager should pause its processing before a particular phase, click the Actions icon next to that phase, and then select Add Pause.

    Note: Pauses occur before the phase at which they are defined.

  3. Click Next.

Enter SSH Keys

Optionally upload SSH keys for users.

Note: You cannot add keys after the provisioning process is completed.

  1. Click Add Key.

  2. Specify the tiers for the SSH key. Choose All Tiers, Application Tier, or Database Tier.

  3. Specify the pertinent OS User type. Choose All Users, Operating System Administrator, or Application Administrator.

  4. Upload the SSH key file. The file name will default in.

  5. The system will validate the SSH key. Click Next to continue.

Review Your Clone Environment Flow Details

  1. Review the installation details; database details; application tier details, including zones; job definition details; and SSH key information.

  2. To provision your environment, click Submit.

  3. You can check the status of the job to provision the environment in the Jobs page.

Perform Post-Cloning Tasks

After the environment is successfully cloned, perform any necessary post-cloning steps and access your environment following the instructions provided in Perform Post-Provisioning and Post-Cloning Tasks.

Back Up an Oracle E-Business Suite Instance

You can use Oracle E-Business Suite Cloud Manager to create a backup of an existing Oracle E-Business Suite environment on Oracle Cloud Infrastructure. This feature is available for environments created using Advanced Provisioning. You can either create an individual backup or schedule backups to be created automatically. Oracle E-Business Suite Cloud Manager creates backups on the Oracle Cloud Infrastructure Object Storage service.

You must have the following prerequisites to create a backup.

Prerequisites

Manage Backups

You can use Oracle E-Business Suite Cloud Manager to manage both backups created from environments on Oracle Cloud Infrastructure and backups created from on-premises Oracle E-Business Suite environments. You can provision another environment based on a backup, or delete a backup when you no longer need it.

Create a Backup of a Cloud-Based Oracle E-Business Suite Instance

Perform the following steps when creating a backup:

  1. Create a backup.

  2. Review Oracle WebLogic Server validation warnings (conditionally required).

Create a Backup

  1. Click the Navigator icon, and then select Environments. In the Environments page, click the Actions icon next to the environment you want, and then select Create Backup.

    Alternatively, click an environment name link in the Environments page to navigate to the environment details page for a single environment, and click Create Backup.

    Note that the Create Backup option is not available for environments generated using One-Click Provisioning, and is therefore grayed out for those environments.

  2. In the Create Backup window, accept the system-generated backup name or enter a new name to uniquely identify your backup. The name must be a maximum of 31 characters long and must include only alphanumeric characters and underscores. It cannot include any special characters other than underscores. Additionally, the first character of the name must be an alphabetic letter. The name cannot begin with a numeral or an underscore.

    Oracle E-Business Suite Cloud Manager adds the backup name as a prefix when creating the containers to store objects in a compartment within an Oracle Cloud Infrastructure Object Storage namespace, known as buckets. The generic bucket for the application tier and database tier Oracle home backup is named <Backup_Name>Generic. The database bucket for the database RMAN backup is named <Backup_Name>DB.

  3. Select the Oracle Cloud Infrastructure Object Storage compartment where you want to create the backup.

  4. In the Encryption Password field, specify a password to encrypt the application tier file system and database tier file system. If Transparent Data Encryption (TDE) is not enabled in the source database, then this password is also used to encrypt the database RMAN backup.

    Re-enter the encryption password in the next field to confirm it.

  5. Enter the password for the Oracle E-Business Suite APPS schema for the source environment.

  6. For an Oracle E-Business Suite Release 12.2 environment only, enter the Oracle WebLogic Server administration password for the source environment.

  7. If Transparent Data Encryption (TDE) is enabled in the source database, enter the password for the TDE wallet.

  8. You can optionally specify advanced Recovery Manager (RMAN) parameters. To do so, click Show Advanced Options. If you do not need to change the RMAN parameters, skip to step 14.

  9. As part of RMAN backup, in the copy phase database blocks will be validated implicitly, and any corruption or missing object will be reported at that time. If you want to enforce the database validation before the RMAN backup, then click the RMAN_VALIDATE_DATABASE toggle switch to turn this option on.

  10. Select the binary compression algorithm to use for RMAN backup, either Basic, Low, Medium, or High. The default value is Basic. Note that the Low, Medium, and High compression algorithms fall under Advanced Compression. You must have or acquire a license for the Advanced Compression option to use these compression algorithms. The Advanced Compression option is included in all Exadata cloud service subscriptions, and in VM DB Systems subscriptions with Enterprise Edition High Performance and Extreme Performance options.

  11. Specify the number of RMAN staging channels to allocate for creating the backup. The default value is 75% of the number of OCPUs. For example, for a VM with the shape Standard 2.4 , the default value for the RMAN Channel Count parameter is 6. The minimum value is one channel. The maximum value is 255 channels.

  12. Specify the section size for multisection backups. The default value is 64G. Valid values are 2G, 4G, 8G, 16G, 32G, 64G, 128G, or 256G.

  13. The following parameters are set automatically to default values by RMAN unless you enter specific values for them here. You should only set values for these parameters if you fully understand their effects, as inappropriate settings can reduce backup performance.

    • Specify the maximum number of data files to place in each backup set. The default value is 64. To determine the number of data files in each backup set, RMAN uses either the value you specify in this parameter or the number of files read by each channel, whichever is lower. If you allocate only one channel, then you can use this parameter to make RMAN create multiple backup sets.

    • Specify the maximum number of input files that a backup or copy can have open at a given time. The default value used by RMAN is 8.

    • Specify the rate of bytes per second that RMAN can read on this channel. Use this parameter to set an upper limit for bytes to read so that RMAN does not consume excessive disk bandwidth and degrade online performance. Specify the rate as an integer, and select the unit of measurement in which you are expressing the rate, either K, M, or G.

    • It is not recommended to use the RMAN_DATAFILE_ID_ALLOWED_MAXCORRUPT parameter for normal processing. However, if necessary, you can set this parameter to specify the maximum number of corruptions permitted in a data file during the backup job. Specify the parameter value as a list showing each data file ID and the maximum number of corruptions for that data file, in the following format: <DATA_FILE_ID_1>:<MAX_CORRUPTIONS_1>, <DATA_FILE_ID_2>:<MAX_CORRUPTIONS_2>, ...

  14. Click Create Backup.

    Note: Oracle E-Business Suite Cloud Manager automatically records the operating system time zone for the source database node as part of the backup metadata. This time zone value is used to help determine the default time zone for environments provisioned from this backup if the Server Timezone profile option is not set within the source environment. For more information, see Advanced Provisioning.

  15. You can check the status of the job to create the backup in the Jobs page. Locate the create-ossbackup job that you want to troubleshoot, and click the job name link to go to the Job Details page. See Monitor Job Status.

    The Job Details page provides links to the log files for each task performed to create the backup, including pre-validation tasks and main execution tasks. If a backup creation job does not succeed, you can review the related log files for the specific task that failed to troubleshoot the issue.

  16. After a backup is successfully created, you can review the backup details in the Backups page or in the Administration tab of the environment details page for the source environment. From these pages, to begin provisioning another environment on Oracle Cloud Infrastructure based on the backup, click the action icon and select Provision Environment. See Advanced Provisioning.

  17. If you no longer need a backup, to begin deleting it, navigate to that backup in the Backups page or the Administration tab of the environment details page for the source environment, then click the action icon, and select Delete. You can also use a command-line API to delete a failed backup. See Delete a Backup.

Review Oracle WebLogic Server Validation Warnings (Conditionally Required)

Oracle E-Business Suite Cloud Manager performs certain validations on the Oracle WebLogic Server domain and stops the backup creation job with a warning if the default threshold values are exceeded. If the job logs show one of these warning messages, then you should review the source environment to decide whether you can make changes to resolve the issue and proceed with the backup.

For more information about retrying a backup creation job, see Monitor Job Status.

Schedule Backups

You can schedule backups to be created for an environment automatically by creating a scheduling policy and then assigning it to the environment in the environment details page. See Set Up Scheduling Policies and Review Environment Details.

If you no longer want to create backups on the specified schedule, you can remove the policy assignment for the environment.

Note: A scheduled backup can be run only when no other job is being performed for that environment.

You cannot retry a missed job directly. However, you can schedule another backup or manually create another backup for the environment if necessary.

  1. Click the Navigator icon, and then select Environments. Click the environment name link for the environment you want to back up.

  2. In the environment details page, locate the Backup Policy property. If no policy is currently assigned, click the Assign link.

  3. In the Assign Backup Policy window, select the Oracle Cloud Infrastructure Object Storage compartment where you want to create the backups.

  4. Select the policy that specifies the schedule on which you want to create backups.

  5. Enter a backup name prefix to uniquely identify your backups. The name prefix must be a maximum of 18 characters long and must include only alphanumeric characters and underscores. It cannot include any special characters other than underscores. Additionally, the first character of the name must be an alphabetic letter. The name cannot begin with a numeral or an underscore.

    Oracle E-Business Suite Cloud Manager adds the backup name prefix when creating the containers to store objects in a compartment within an Oracle Cloud Infrastructure Object Storage namespace, known as buckets. The generic bucket for the application tier and database tier Oracle home backup is named <Backup_Name>Generic. The database bucket for the database RMAN backup is named <Backup_Name>DB.

  6. In the Encryption Password field, specify a password to encrypt the application tier file system and database tier file system. If Transparent Data Encryption (TDE) is not enabled in the source database, then this password is also used to encrypt the database RMAN backup.

    Re-enter the encryption password in the next field to confirm it.

  7. Enter the password for the Oracle E-Business Suite APPS schema for the source environment.

  8. For an Oracle E-Business Suite Release 12.2 environment only, enter the Oracle WebLogic Server administration password for the source environment.

  9. If Transparent Data Encryption (TDE) is enabled in the source database, enter the password for the TDE wallet.

  10. You can optionally specify advanced Recovery Manager (RMAN) parameters. To do so, click Show Advanced Options. If you do not need to change the RMAN parameters, skip to step 14.

  11. As part of RMAN backup, in the copy phase database blocks will be validated implicitly, and any corruption or missing object will be reported at that time. If you want to enforce the database validation before the RMAN backup, then click the RMAN_VALIDATE_DATABASE toggle switch to turn this option on.

  12. Select the binary compression algorithm to use for RMAN backup, either Basic, Low, Medium, or High. The default value is Basic. Note that the Low, Medium, and High compression algorithms fall under Advanced Compression. You must have or acquire a license for the Advanced Compression option to use these compression algorithms. The Advanced Compression option is included in all Exadata cloud service subscriptions, and in VM DB Systems subscriptions with Enterprise Edition High Performance and Extreme Performance options.

  13. Specify the number of RMAN staging channels to allocate for creating the backup. The default value is 75% of the number of OCPUs. For example, for a VM with the shape Standard 2.4 , the default value for the RMAN Channel Count parameter is 6. The minimum value is one channel. The maximum value is 255 channels.

  14. Specify the section size for multisection backups. The default value is 64G. Valid values are 2G, 4G, 8G, 16G, 32G, 64G, 128G, or 256G.

  15. The following parameters are set automatically to default values by RMAN unless you enter specific values for them here. You should only set values for these parameters if you fully understand their effects, as inappropriate settings can reduce backup performance.

    • Specify the maximum number of data files to place in each backup set. The default value is 64. To determine the number of data files in each backup set, RMAN uses either the value you specify in this parameter or the number of files read by each channel, whichever is lower. If you allocate only one channel, then you can use this parameter to make RMAN create multiple backup sets.

    • Specify the maximum number of input files that a backup or copy can have open at a given time. The default value used by RMAN is 8.

    • Specify the rate of bytes per second that RMAN can read on this channel. Use this parameter to set an upper limit for bytes to read so that RMAN does not consume excessive disk bandwidth and degrade online performance. Specify the rate as an integer, and select the unit of measurement in which you are expressing the rate, either K, M, or G.

    • It is not recommended to use the RMAN_DATAFILE_ID_ALLOWED_MAXCORRUPT parameter for normal processing. However, if necessary, you can set this parameter to specify the maximum number of corruptions permitted in a data file during the backup job. Specify the parameter value as a list showing each data file ID and the maximum number of corruptions for that data file, in the following format: <DATA_FILE_ID_1>:<MAX_CORRUPTIONS_1>, <DATA_FILE_ID_2>:<MAX_CORRUPTIONS_2>, ...

  16. Click Assign.

  17. For an environment that currently has a backup policy, if you no longer want to create backups on the schedule specified by that policy, click Unassign to remove the policy assignment.

Review Backups

  1. To review the backups stored on the Oracle Cloud Infrastructure Object Storage service for your deployment, click the Navigator icon, and then select Backups.

    Note: You can also review a list of the backups for a particular environment in the environment details page for that environment. See Review Environment Details.

  2. The Backups page displays the available backups within the compartment you chose in the EBS Compartment field in the Oracle E-Business Suite Cloud Manager header. The list can include both backups of on-premises environments and backups of environments on Oracle Cloud Infrastructure. You can optionally enter a full or partial value in the search field to display only backups whose properties contain that value. You can search by the following properties shown in this page:

    • Backup name

    • Oracle E-Business Suite version

    • Database version

    • Compartment name

    • Database name

    • Whether TDE is enabled for the environment

    • The size of the database after it is restored

    • Creation date and time

  3. To provision an environment from a backup, click the Actions icon next to that backup, and then select Provision Environment. See Advanced Provisioning.

  4. To delete a backup, click the Actions icon next to that network profile, and then select Delete. See Delete a Backup.

Delete a Backup

The Delete Backup operation is available for backups created using the Oracle E-Business Suite Cloud Backup Module or using Oracle E-Business Suite Cloud Manager. See: Create a Backup of an On-Premises Oracle E-Business Suite Instance on Oracle Cloud Infrastructure or Create a Backup of a Cloud-Based Oracle E-Business Suite Instance.

Delete a Successful Backup

This section covers instructions on how to delete a successful backup in Oracle E-Business Suite Cloud Manager.

Note: This action is irreversible. Use caution with this feature.

  1. Click the Navigator icon and select Backups. Alternatively navigate to the Environment Details page for the Cloud environment and select the Backups tab.

  2. Select a backup from the list of available backups on the page. You can search for the backup if you know its name or part of its name.

  3. Click Action icon for the backup and select Delete.

  4. In the confirmation window, select Yes.

  5. You can check the status of the job to delete the backup in the Jobs page. See: Monitor Job Status.

Delete a Failed Backup

This section covers instructions on how to delete a failed backup. Use these instructions if your backup process fails and you need to reuse the same bucket name in creating a new backup. The "Backup Identifier Tag" is used to create the bucket name.

  1. For the failed backup, note the path to the session ID. This ID is displayed on the console while the backup is being created when you run the Oracle E-Business Suite Cloud Backup Module. If you create a backup using Oracle E-Business Suite Cloud Manager, you can find the session ID in the job logs for the failed job. See the section Monitor Job Status for more information. The session ID should be in the format <STAGE_DIRECTORY>/session/<SESSION_ID>. An example is /u01/db1/session/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.

  2. Connect to the primary node of the application tier and the database tier, and identify if any remote clone processes related to the failed backup are running. For example, run the following command:

    $ ps -ef|grep remoteclone|grep xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 

    and terminate those processes in both the application tier and the database tier. Note that there could be other backup processes running on the source application tier or database tier. Ensure that you terminate only the processes related to the failed backup.

  3. Ensure that the OCI configuration file and PEM key file are present on the Oracle E-Business Suite Cloud Manager orchestration VM. For information on the OCI configuration file, see Create a Profile in the Oracle Cloud Infrastructure CLI Configuration File.

  4. Go to the RemoteClone directory in the current backup session, and run the command for deleting the Database and Generic buckets.

    1. Run the following command on the Oracle E-Business Suite Cloud Manager orchestration VM:

      $ cd /u01/install/APPS/apps-unlimited-ebs/RemoteClone
    2. Run the following command with the required details to delete the bucket.

      Note: You must provide the proxy details if the connection to ObjectStorage is going through a proxy server.

      $ 3pt/jre/bin/java -cp lib/cln_utils.jar:3pt/ext-jars/* 
      oracle.apps.liftNshift.commandline.client.bmcs.EBSLiftBMCSDeleteBucketClient 
      -bucketName <bucketName> [-proxyPort <proxyPort>] [-proxyProtocol
      <proxyProtocol>] -bmcsTenantName <bmcsTenantName> -compartmentID <compartmentID>
      [-proxyUsername <proxyUsername>] -bmcsConfigFilePath <bmcsConfigFilePath>
      [-proxyHost<proxyHost>] [-h]
      

      Description of parameters:

      • <bucketName> is the Bucket name.

      • <proxyPort> is the Proxy Port.

      • <proxyProtocol> is the Proxy Protocol.

      • <bmcsTenantName> is the BMCS Tenant name.

      • <compartmentID> is the BMCS Compartment ID.

      • <proxyUsername> is the Proxy Username.

      • <bmcsConfigFilePath> is the complete path to the BMCS configuration file.

      • <proxyHost> is the Proxy Host.

      • -h can be used for help with the command.

      Example commands:

      • For deleting a Generic bucket with Backup Identifier Tag 'PRODBACKUP':

        $ 3pt/jre/bin/java -cp lib/cln_utils.jar:3pt/ext-jars/* 
        oracle.apps.liftNshift.commandline.client.bmcs.EBSLiftBMCSDeleteBucketClient 
        -bucketName PRODBACKUPGeneric -compartmentID 
        ocid1.compartment.oc1..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 
        -bmcsTenantName BMCSTENANT -bmcsConfigFilePath /u01/install/APPS/userpem/user
      • For deleting a Database bucket with Backup Identifier Tag 'PRODBACKUP':

        $ 3pt/jre/bin/java -cp lib/cln_utils.jar:3pt/ext-jars/* 
        oracle.apps.liftNshift.commandline.client.bmcs.EBSLiftBMCSDeleteBucketClient 
        -bucketName PRODBACKUPDB -compartmentID 
        ocid1.compartment.oc1..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 
        -bmcsTenantName BMCSTENANT -bmcsConfigFilePath /u01/install/APPS/userpem/user

    Note: If you want to rerun the Oracle E-Business Suite Cloud Backup Module using the same bucket name, then you must first provide a new stage directory path for both the application and database tier.

Related Topics

Backing Up a Database to Object Storage Using RMAN

Oracle Database Backup and Recovery User's Guide 19c

Oracle Database Backup and Recovery User's Guide 12c Release 1 (12.1)

Oracle Database Backup and Recovery User's Guide 11g Release 2 (11.2)

Promote a Standby Environment

You may promote only standby environments that have been successfully configured.

Select the Standby Environment

  1. Navigate to the Environments page in Oracle E-Business Suite Cloud Manager.

  2. Select Promote from the Action menu for the standby environment you wish to promote.

  3. Alternatively, select the standby environment and click on Promote from its Environment Details page.

Enter Standby Environment Details

The Environment Name, EBS Compartment, and Network Profile Name are shown and cannot be changed.

  1. Enter the APPS Password.

  2. Enter the WebLogic Server Password.

  3. Optionally enter tagging information in the Tags region.

    • Tag Namespace: Select a predefined tag namespace or select None (add a free-form tag).

    • Tag Key: Enter the name you use to refer to the tag.

    • Value: Enter the value for the tag key.

  4. Click Next.

Enter Database Information

Review and enter database details and related options.

  1. Enter the following:

    • DB SID: The database SID. For example: demodb

    • Database Service Type: This field is read-only.

    • Logical Hostname: Provide the logical hostname that will be used as part of the Oracle E-Business Suite configuration. Note that this is not the physical hostname.

    • Logical Domain: Provide the logical domain that will be used as part of the Oracle E-Business Suite configuration. Note that this is not the physical domain.

    • VM Shape: This field is read-only. The shape shown is the shape selected during standby creation.

    • Enable TDE: This field is read-only and enabled by default.

    • Admin Password: The admin password for the database is used for the SYS user as well. If TDE is enabled for the environment, then this password is also used as the TDE wallet password.

  2. Enter the Active Database credentials:

    • Admin Password

    • Wallet Password

  3. Click Next.

Enter Application Tier Information

  1. Define your zones in the Zone region.

    For more information on zones, refer to My Oracle Support Knowledge Document 1375670.1, Oracle E-Business Suite Release 12.2 Configuration in a DMZ.

    Note that you can have multiple zones across subnets. You can configure your environment such that you functional redirection per zone is in accordance with functional affinity.

    Also, you can have a load balancer shared between multiple zones of the same type. This configuration allows for two separate URLs to resolve to the same IP address and the shared load balancer will target one backend set or another.

    Note too that you have flexibility in your configuration. One zone, Zone A, can have one load balancer assigned to it, while another two zones, Zone B and Zone C, can have a second load balancer assigned to them.

    Define your internal zone first.

    Enter values for the following properties:

    • Name

    • Type

  2. In the Web Entry Point region, enter values for the following properties:

    • Web Entry Type: Choose one of the following: New Load Balancer (LBaaS), Manually Configured Load Balancer to select a manually deployed existing load balancer, or Application Tier Node to choose the primary application tier as the entry point.

    • Load Balancer Shape: If you are using LBaaS, select the load balancer shape. For example: 100Mbps

    • Protocol: Select the protocol for access to the environment, either http or https.

    • Hostname: Enter the hostname for your web entry point. For example: myhost

    • Domain: Enter the domain for your web entry point. For example: example.com

    • Port: Select the port for your web entry point. If there is no load balancer, then the port is automatically populated depending on the protocol: 8000 for http and 4443 for https. Otherwise, select the appropriate port for use with your load balancer, such as 80 for http or 443 for https. Note that to allow access to the Oracle E-Business Suite login URL, your network administrator must define an ingress rule in the load balancer security list. See Create Network Resources For Deploying Oracle E-Business Suite Instances.

  3. For Storage, choose the File System Type: Non-Shared or Shared.

    If you choose Shared, then the storage is shared across all nodes in your network. You must enter a value for the Block Volume Storage field for the first node under Application Tier Nodes. This storage is then shared across all nodes, so you do not enter in storage values for your subsequent nodes. In addition, after you save your first zone with Shared storage, any subsequent zones will also be defined with Shared storage automatically.

    Important: You must ensure you specify enough storage for your nodes. Refer to Oracle E-Business Suite Installation Guide: Using Rapid Install for guidelines on space usage.

    If you choose Non-Shared, you must specify a value for the Block Volume Storage field for every node in the Application Tier Nodes field.

  4. In the Logical Host region, enter values for the following properties:

    • Logical Host Option: Choose Automatic or Manual.

    • Logical Hostname Prefix: If you chose Automatic, enter your desired hostname prefix.

      You do not need to enter this if you chose Manual for your logical host option, but you will be prompted for the Logical Hostname for your nodes in the Application Tier Nodes region.

    • Logical Domain: Enter the logical domain.

  5. In the Application Tier Nodes region, enter properties for each node.

    Note that you can define a specific shape for each application tier node.

    • Logical Hostname

    • Logical FQDN

    • Shape: You can change the shape for the node. When choosing a flexible shape, for example VM.Standard.E3.Flex, you will use the sliders to choose 1) the Number of OCPUs and 2) Amount of memory (GB).

    • Block Volume Storage

    • Fault Domain:Select the fault domain. Refer to Fault Domains for more information.

  6. Click Save Zone to save your zone definition.

  7. Define additional zones using the Add Zone button.

  8. When you have completed adding your zones, click Next.

Specify Your Extensibility Options

You can optionally extend the standby promotion job to meet your own requirements. By default, Oracle E-Business Suite Cloud Manager follows a standard job definition for promotion. However, Oracle E-Business Suite Cloud Manager administrators can also create extended job definitions that include additional tasks as part of the promotion job. In this case you can select the appropriate extended job definition for Oracle E-Business Suite Cloud Manager to follow when promoting your environment. If you select an extended job definition, you may need to enter values for input parameters required by the additional tasks in that job definition.

Additional Information: For more information on using the Extensibility Framework to extend job definitions, see Set Up the Extensibility Framework.

Additionally, whether you are using the standard promotion job definition or an extended job definition, you can choose to have Oracle E-Business Suite Cloud Manager pause at specified points during the promotion job. For example, if you want to perform your own validations after a particular phase before allowing Oracle E-Business Suite Cloud Manager to proceed to the next phase, you can add a pause at that point. You can then resume the promotion job when you are ready to proceed. See Monitor Job Status.

Specify Your Job Definition

  1. Optionally select an extended job definition for promoting your environment in the Job Definition field.

  2. In the Task Parameters tab, specify any parameter values required for the additional tasks in the job definition. Some parameters may include default values, which you can override as needed.

Specify Your Job Definition Details

  1. Click the Job Definition Details tab. This tab displays a list of the phases in the job definition and the tasks within each phase.

  2. To specify that Oracle E-Business Suite Cloud Manager should pause its processing before a particular phase, click the Actions icon next to that phase, and then select Add Pause.

    Note: Pauses occur before the phase at which they are defined.

  3. Click Next.

Enter SSH Keys

Optionally upload SSH keys for users.

Note: You cannot add keys after the promotion process is completed.

  1. Click Add Key.

  2. Specify the tiers for the SSH key. Choose All Tiers, Application Tier, or Database Tier.

  3. Specify the pertinent OS User type. Choose All Users, Operating System Administrator, or Application Administrator.

  4. Upload the SSH key file. The file name will default in.

  5. The system will validate the SSH key. Click Next to continue.

Review Your Promotion Details

  1. Review the installation details; database details; application tier details, including zones; job definition details, and SSH key information.

  2. To promote your environment, click Submit.

  3. You can check the status of the job to promote the environment in the Jobs page.

Post-Promotion Steps

  1. After the standby environment has been promoted, run the following cleanup script on the source database server to clean up the local configuration.

    $ RemoteClone/bin/db-standby-cleanup.sh --context-file <absolute path to DB context file> --standby-name <standby name> --oci-private-key-file <absolute path to key file> --ebs-username <ebs username

Delete an Oracle E-Business Suite Environment

You can delete environments that you no longer need in order to make those resources available for other uses. The Delete option is available for environments with the statuses Successful, Aborted, and Failed. It is not available for an environment for which the Last Job status is "In Progress" on the Environments page. In addition, the Delete option is not available while a backup of the environment is being taken.

The Delete option is available for environments on all Cloud Database Service options: Compute, Virtual Machine DB System, and Exadata Cloud Service.

Prerequisites

Delete a Standard Environment

Follow these instructions to delete a standard environment.

Important: Environment deletion is irreversible. Use caution with this feature.

Backups created from an environment that is subsequently deleted remain, and can still be utilized.

For environments that were not provisioned successfully, this procedure cleans up the resources of incomplete installations.

  1. From the Oracle E-Business Suite Cloud Manager Environments page, click the Action icon for an environment with its Last Job status shown as Successful, Aborted, or Failed, then select Delete. Alternatively, from the environment details page for a specific environment, click Action and select Delete.

  2. In the confirmation window, enter the environment name to confirm your choice. Then click Yes.

  3. You can check the status of the job to delete the environment in the Jobs page. See: Monitor Job Status.

    Deletion of an environment will delete the associated load balancer only if the service has only one backend set which was created by the Oracle E-Business Suite Cloud Manager.

Delete a Standby Environment

You can delete a standby environment from within Oracle Applications Manager, but not within Oracle E-Business Suite Cloud Manager. You cannot delete a standby environment that has an "In Progress" status.

  1. Navigate to the Oracle Cloud Infrastructure page within Oracle Applications Manager.

  2. Click on the name of the standby environment you wish to delete.

  3. Click Remove Standby in the Standby Environment Configuration on Oracle Cloud Infrastructure page.

  4. After the standby environment has been deleted, run the following cleanup script on the source database server to clean up the local configuration.

    $ RemoteClone/bin/db-standby-cleanup.sh --context-file <absolute path to DB context file> --standby-name <standby name> --oci-private-key-file <absolute path to key file> --ebs-username <ebs username>