Oracle Applications DBA

Zero Downtime Migration (ZDM)

2025-05-20T14:36:00.000+05:30

Zero Downtime Migration (ZDM) supports cross-platform migration of Oracle databases. Specifically, ZDM 21.2 introduced the ability to migrate source Oracle databases running on Oracle Solaris or IBM AIX to Oracle Autonomous Database or Co-managed Oracle Database on Oracle Linux. ZDM also supports cross-platform migrations using the Logical Offline workflow, and has expanded to include source databases on AWS RDS.

ZDM offers different migration workflows, including:

· Logical Offline Migration:

This method uses Data Pump export and import for migrations, allowing for cross-platform and cross-version migrations.

· Physical Offline Migration:

This workflow utilizes RMAN backup and restore, supporting migrations between the same database versions and platforms.

· Physical Online Migration:

This method leverages Oracle Data Guard for online migrations, and supports migrations between different platforms and versions.

· Logical Online Migration:

This approach utilizes Oracle GoldenGate to keep the source and target databases in sync during the migration, enabling minimal downtime.

Supported Sources:

· Oracle Databases on Linux, Solaris, and AIX.

· Oracle Databases on AWS RDS.

· On-premises Oracle Databases.

· Oracle Databases on Oracle Cloud Infrastructure.

Supported Targets:

Oracle Autonomous Database, Co-managed Oracle Databases, Oracle Database on Oracle Cloud Infrastructure, and Oracle Database@Azure.

Install, configure, and migrate an Oracle database using Zero Downtime Migration (ZDM)

2025-05-20T14:34:00.007+05:30

To install, configure, and migrate an Oracle database using Zero Downtime Migration (ZDM), you'll need to follow these steps:

1. Install ZDM:

· Download the ZDM software from the Oracle website.

· Create necessary directories (e.g., grid, base) on the ZDM service host.

· Use the zdminstall.sh script to install ZDM, specifying the Oracle Home and Oracle Base locations.

2. Configure ZDM:

· Prepare the Source and Target Hosts:

· Ensure SSH connectivity and SQL*Net connectivity between the source and target database hosts.

· Configure the ZDM service host to have necessary hostnames and IP addresses.

· Ensure the source database is running in archive log mode.

· Create a Response File:

· Use the template file provided with ZDM ($ZDMHOME/rhp/zdm/template/zdm_template.rsp).

· Customize the response file with details about the source and target databases, including credentials, network information, and object storage details.

· Verify the Configuration:

· Use ZDM's configuration verification tools to ensure all parameters are correctly set.

· Create a Wallet on the Source Database:

· If you're using Transparent Data Encryption (TDE), create a wallet and save the public key. This is needed for encrypting the backup.

3. Migrate the Database:

· Initiate the Migration:

· Use the migrate_database command in the ZDM CLI.

· Provide the response file as an argument to the command.

· ZDM will then:

· Connect to the source and target databases.

· Prepare the source and target environments.

· Validate the configuration.

· Perform discovery and copy files to the object storage.

· Restore the database on the target.

· Complete the Migration:

· ZDM will notify you when the migration is complete.

· You can then switch over to the new database.

ZDM - Pause after ZDM_CONFIGURE_DG_SRC

2025-05-20T14:33:00.005+05:30

Oracle ZDM (Zero Downtime Migration) allows pausing the migration process, including before the final switchover to the target database. This pause allows you to verify the target database, perform application tests, or prepare for the switchover at a time convenient for your application and business needs.

Key features and considerations for pausing ZDM before switchover:

· Pause after ZDM_CONFIGURE_DG_SRC:

This is the recommended stage to pause before the actual switchover. At this point, the standby database is created, and synchronization between the source and target databases is established.

· Manual switchover:

After pausing, you can manually switchover your application to the standby database.

· Validating the target database:

You can verify that the target database is working as expected and perform application tests before switching over.

· Resuming the ZDM job:

Once you are ready, you can resume the ZDM job, which will then perform the final switchover and other necessary post-migration tasks.

· Hybrid disaster recovery:

Pausing before switchover allows you to create a hybrid disaster recovery setup where the on-premises database remains in place as a standby for disaster recovery.

Example:

You can pause the ZDM job with the -pauseafter flag when running the zdmcli migrate database command.

Code

$ $ZDMHOME/bin/zdmcli migrate database \ -rsp /home/zdmuser/physical_online/physical_online.rsp \ -sourcesid oradb \ -pauseafter ZDM_CONFIGURE_DG_SRC

Oracle ZDM – Zero Downtime Migration

2025-05-20T14:32:00.001+05:30

1. Introduction to ZDM

Oracle Zero Downtime Migration (ZDM) is an automated utility for migrating Oracle databases to Oracle Cloud Infrastructure (OCI) with minimal or zero downtime. It supports both physical and logical migrations using proven Oracle MAA (Maximum Availability Architecture) technologies.

2. Architecture Overview

ZDM works by coordinating backup, restore, and synchronization activities between the source and target databases. The source can be on-prem or in a different cloud, while the target is usually in OCI. A dedicated ZDM server orchestrates the migration steps.

3. Pre-requisites

• ZDM server on Oracle Linux 7/8 • Required RPMs: glibc-devel, expect, libaio, unzip • SSH access between ZDM and source/target DBs • SQL*Net connectivity (port 1521) • Object Storage/Recovery Appliance access

4. ZDM Installation

• Extract ZDM zip file and run zdminstall.sh • Define ZDM_BASE and ZDM_HOME • Add ZDM_HOME/bin to PATH • Start services using zdmservice • Validate using zdmcli version/status

5. Response File Parameters

The response file defines the source, target, backup location, method, and advanced behavior like fallback, shutdown source, or convert to PDB. Important keys include: • MIGRATION_METHOD=ONLINE_PHYSICAL • BACKUP_PATH • TGT_RETAIN_DB_UNIQUE_NAME • NON_CDBTOPDB_CONVERSION • SHUTDOWN_SRC

6. Migration Execution Flow

1. Validate job config with -eval 2. Execute migration using zdmcli 3. Use -pauseafter ZDM_CONFIGURE_DG_SRC to allow testing 4. Resume ZDM to perform switchover 5. Monitor logs and validate completion

7. Pause After DG Configuration

Using -pauseafter ZDM_CONFIGURE_DG_SRC, DBAs can stop the migration before final switchover. Benefits: • Validate the target standby DB • Conduct application testing or UAT • Retain source as a hybrid DR system

8. Monitoring & Logs

ZDM logs are vital for tracking job progress and diagnosing issues. • ZDM Server Logs: $ZDM_BASE/crsdata/<node>/rhp/rhpserver.log • Migration Logs: $ORACLE_BASE/zdm/zdm_<DB>_<JOBID>/zdm/log • Command: zdmcli query job -jobid JOB1

9. Troubleshooting

Common issues include: • SSH permission denied • TNS alias resolution failure • Incorrect RMAN backup paths • Version mismatch or missing redo logs Always validate with zdmcli query job and inspect logs.

10. Best Practices & Tips

• Always use -eval to pre-validate the job • Pause before switchover to reduce risk • Use snapshot standby for UAT • Keep ZDM node isolated from DBs • Automate cleanup and fallback testing

An Oracle Database Performance Crisis/Scenario : A Comprehensive Analysis and Strategic Recommendations

2024-04-29T17:31:00.009+05:30

We had a Performance Issue sometime back. Here's a concise summary of the situation and our resolution approach.

Situation:

1. Apps reports are running significantly longer compared to yesterday/week before, with some running for more than 4 hours as compared to 10-15 min in the last run..

2. SQL*Plus login from the apps node to DB is taking an extended time.

3. CPU on DB Node is used up, with a high load average of above 120 on a 16-core CPU.

4. A long-running process or session is not releasing CPU or memory, causing High Wait times for other sessions.

5. Many concurrent requests, more than 250, are in pending status.

Findings:

1. Gather Statistics was last run about 3 months back for most CUSTOM tables though regular GSS request was already scheduled.

2. optimizer_adaptive_features is set to TRUE, which is not recommended.

3. filesystemio_options is set to NONE.

4. High I/O on TABLES "GL.GL_*******". Main cause is SQL_ID: "xxxxxxxxxxxxxxxx".

5. Indexes "GL"."GL_*******_N1" were not analyzed.

6. Builtin Scheduler Jobs/AUTOTASK CLIENT JOBS are enabled.

7. Scheduled Full DB Backup was running.

Recommendations:

Firstly, Stop the Full DB backup or kill the backup session and process. Run it once issue gets resolved and schedule it when this report is not running .

1. Run Gather Statistics and schedule it to run at regular intervals across the weekdays at non-peak hours of business.

2. Set optimizer_adaptive_features to FALSE.

3. Set filesystemio_options to SETALL.

4. Disable auto space advisor job, as it is causing a performance impact.

5. Consider disabling SQL Tuning Advisor job as ACCEPT_SQL_PROFILES is set to FALSE.

6. Gather statistics for the "GL"."GL_*********_N1" indexes.

7. Optimize the SQL query causing high I/O on "GL.GL_*******". Run SQL Tuning Advisor and Accept the profiles given.

8. Cancel long-running requests –ID’s: xxxxxxxx and xxxxxxxx after confirmation from Functional teams.

9. Run and schedule maintenance programs for GL to optimize the Posting program performance.

10. Move the GL tables mentioned above to gain performance on IOPS.Db file sequential/scattered reads were high and SEGMENT ADVISOR recommended to move tables and reclaim space.

Meanwhile we increased the Concurrent Manager processes and Added 2 more OPP processes.

The other pending requests started processing slowly and completed within an hour or so.

Issue was fixed finally. DB was performing better than before the issue.

---

TOP 10 COMMON CAUSES FOR A DATABASE CRASH AND THEIR POSSIBLE FIXES

2024-04-29T14:41:00.001+05:30

1. Insufficient Memory:

- Reason: If the Oracle instance does not have enough memory allocated, it can lead to crashes.

- Fix: Increase the memory allocated to the Oracle instance.

- Use the following command to increase the SGA (System Global Area) size:

```

ALTER SYSTEM SET SGA_TARGET=4G SCOPE=SPFILE;

```

- Restart the Oracle instance for the changes to take effect:

```

SHUTDOWN IMMEDIATE;

STARTUP;

```

2. Corrupted Data Files:

- Reason: If the Oracle data files get corrupted, it can cause the database to crash.

- Fix: Perform a data file recovery.

- Identify the corrupted data file:

```

SELECT FILE_NAME FROM DBA_DATA_FILES WHERE TABLESPACE_NAME='TABLESPACE_NAME';

```

- Take the tablespace offline:

```

ALTER TABLESPACE TABLESPACE_NAME OFFLINE;

```

- Perform recovery:

```

RECOVER DATAFILE 'FULL_PATH_TO_DATAFILE' ;

```

- Bring the tablespace online:

```

ALTER TABLESPACE TABLESPACE_NAME ONLINE;

```

3. Resource Contention:

- Reason: If there is contention for resources like CPU or I/O, it can lead to database crashes.

- Fix: Identify and resolve the contention issues.

- Check for resource-intensive queries:

```

SELECT SQL_ID, SQL_TEXT FROM V$SQL WHERE PARSING_SCHEMA_NAME='SCHEMA_NAME';

```

- Tune the queries or restrict their resource usage.

4. Listener Issues:

- Reason: If the listener service is not running or misconfigured, it can cause database connectivity issues and crashes.

- Fix: Restart the listener service.

- Stop the listener:

```

lsnrctl stop;

```

- Start the listener:

```

lsnrctl start;

```

5. Database Locks:

- Reason: If there are long-held locks on critical resources, it can lead to database hangs or crashes.

- Fix: Identify and release the locks.

- Check for locks:

```

SELECT * FROM V$LOCK WHERE BLOCK=1;

```

- Release locks:

```

ALTER SYSTEM KILL SESSION 'SID,SERIAL#' IMMEDIATE;

```

6. Hardware Failure:

- Reason: Hardware failures such as disk failures or memory issues can cause the database to crash.

- Fix: Replace the faulty hardware component.

- Check hardware health using vendor-specific tools.

- Replace faulty hardware components.

7. Software Bugs:

- Reason: Bugs or issues in the Oracle Database software can lead to crashes.

- Fix: Apply patches and updates.

- Check for available patches and updates on the Oracle support website.

- Apply the patches using Oracle OPatch utility.

8. Configuration Issues:

- Reason: Incorrect or misconfigured database parameters can cause instability and crashes.

- Fix: Review and adjust database configuration.

- Check the current database parameters:

```

SHOW PARAMETER NAME;

```

- Adjust parameters as needed:

```

ALTER SYSTEM SET PARAMETER_NAME=VALUE SCOPE=SPFILE;

```

9. Network Problems:

- Reason: Network issues such as packet loss or network latency can cause database connectivity problems and crashes.

- Fix: Troubleshoot and resolve network issues.

- Check network connectivity between client and server.

- Investigate and resolve any network hardware or configuration issues.

10. Excessive Redo Log Generation:

- Reason: Excessive redo log generation due to high DML activity can lead to crashes.

- Fix: Manage redo log generation.

- Increase the size of redo logs:

```

ALTER DATABASE ADD LOGFILE ('/path/to/new/logfile1.log', '/path/to/new/logfile2.log') SIZE 100M;

```

- Monitor and optimize DML operations to reduce redo log generation.

It's essential to regularly monitor your Oracle Database for performance issues and address them promptly to prevent crashes.

THE FLOW OF A SELECT OR DML INSIDE ORACLE DATABASE

2024-04-27T20:21:00.002+05:30

THE FLOW OF A SELECT OR DML INSIDE ORACLE DATABASE

1. Client Connection:

- The user's client application establishes a connection to the Oracle database server.

2. Server Authentication:

- The database server authenticates the user's credentials.

3. Session Initialization:

- Upon successful authentication, the database server initializes a session for the user, allocating memory in the PGA and setting up session-specific parameters.

4. Process Creation:

- A dedicated server process or a shared server process is created on the database server to handle the user's session.

5. SGA Initialization:

- The SGA is initialized, including components such as the buffer cache, shared pool, and redo log buffer.

6. SQL Parsing (for DML or SELECT):

- When the user executes a DML or SELECT statement, the server parses the SQL query, checking syntax and semantics. If the statement is valid, an execution plan is generated and stored in the shared pool.

7. Transaction Initialization (for DML):

- For DML statements, the database initializes the transaction context, starting a new transaction ID or using an existing one.

8. Execution Plan Execution:

- The database server executes the execution plan, which may involve data retrieval (for SELECT) or modification (for DML). Data blocks are cached in the buffer cache if needed.

9. Redo Logging (for DML):

- For DML statements, changes are recorded in the redo log buffer for recovery purposes.

10. Data Modification (for DML):

- The actual data modification (insert, update, delete) is performed on the database files. Indexes are updated as necessary.

11. Transaction Commit or Rollback (for DML):

- Depending on the outcome of the transaction, a commit or rollback is issued. A commit makes the changes permanent, while a rollback undoes the changes.

12. Data Retrieval (for SELECT):

- For SELECT statements, the requested data is retrieved from the buffer cache and sent back to the client.

13. Session Termination:

- When the user disconnects or the session is terminated, the session is cleaned up, and the server process is released.

During this entire process, the SGA and PGA are used for memory management, caching, and storing session-specific and shared data structures. The server process manages the communication between the client application and the database, executing SQL statements, managing locks, and ensuring data consistency and integrity.

ECPUC

2024-02-03T14:00:00.000+05:30

ECPUC.sql

E-Business Suite Critical Patch Update Checker (ECPUC)

ECPUC is avaialble with Patch 35583866

When run, ECPUC.sql generates the ECPUC_YYYY-MM-DD_HH24-MI.lst report for your environment which includes a list of required patches and security fixes available as of the latest quarterly Oracle E-Business Suite (EBS) Critical Patch Update (CPU)

Connect to the database as the APPS user.

     For example:  $ sqlplus APPS

 
Run ECPUC.sql while connected as APPS to the database.

     For example:  SQL> @ECPUC.sql

Vulnerability Scanning Service

2024-01-09T19:57:00.002+05:30

Title: Strengthening Cloud Security with Oracle's Vulnerability Scanning Service

Introduction:

In today's dynamic digital landscape, ensuring the security of your cloud infrastructure is paramount. Oracle Cloud Infrastructure's Vulnerability Scanning Service emerges as a powerful tool to fortify your defenses against potential threats. This service is specifically designed to assess and monitor the security of your cloud hosts, providing a robust solution to identify and eliminate vulnerabilities and open ports on various supported operating systems, including Oracle Linux, CentOS, Ubuntu, and Windows Server.

Getting Started:

To kickstart your journey towards a more secure cloud environment, you can create a Scan Recipe tailored to your specific requirements. This will enable you to seamlessly integrate the Vulnerability Scanning Service into your workflow, allowing for continuous monitoring and assessment of your hosts.

Benefits and Features:

The heart of this service lies in its agent plugin, which meticulously inspects the host's operating system. It goes beyond the surface by comparing installed components with several open-source vulnerability databases, ensuring a thorough analysis. Additionally, the plugin identifies open ports on the host and validates against industry-standard benchmarks defined by the Center for Internet Security (CIS), focusing on Linux authentication and access benchmarks. The service also scans public IP addresses to identify open ports, a critical step in fortifying the most vulnerable points of your infrastructure. All scan results are conveniently stored in the same region, allowing you to review them through detailed reports.

Requirements:

Before diving into host scanning, ensure that your administrator creates policies that grant the Vulnerability Scanning Service access to your host resources. These policies should also empower your administration group to effectively manage the scanning resources. Examples of such policies include permissions to manage instances, read compartments, and access VNICS and VNIC attachments.

Example Service Policy:

- Allow the service vulnerability-scanning-service to manage instances in tenancy.

- Allow the service vulnerability-scanning-service to read compartments in tenancy.

- Allow the service vulnerability-scanning-service to read VNICS in tenancy.

- Allow the service vulnerability-scanning-service to read VNIC attachments in tenancy.

Example User Group Policy:

- Allow the group SecurityAdmins to manage VSS-family in tenancy.

Pricing:

The best part? The Vulnerability Scanning Service is absolutely free for all paying customers. Oracle encourages users to leverage this service alongside other cloud security products to maximize their overall security posture.

A typical list of hosts that have been scanned:

Detail Host scan results with the vulnerabilities listed:

Federating Microsoft Active Directory on Oracle Cloud Infrastructure

2024-01-09T19:21:00.004+05:30

**Title: A Guide to Federating with Microsoft Active Directory on Oracle Cloud Infrastructure**

Federating with Microsoft Active Directory (AD) through Microsoft Active Federation Services (AD FS) is a crucial step in integrating your organization's identity management with Oracle Cloud Infrastructure. This guide outlines the steps to achieve seamless federation.

### About Federating with Microsoft Active Directory

Your organization may have multiple Active Directory accounts, each possibly representing a division. While it's possible to federate multiple Active Directory accounts with Oracle Cloud Infrastructure, each federation trust should be established for a single Active Directory account.

To initiate federation with Active Directory, a trust needs to be set up between Active Directory and Oracle Cloud Infrastructure. This involves steps in both the Oracle Cloud Infrastructure Console and Active Directory Federation Services.

#### Step 1: Obtain Required Information from Active Directory Federation Services

**Summary:** Retrieve the SAML metadata document and the names of Active Directory groups for mapping to Oracle Cloud Infrastructure Identity and Access Management (IAM) groups.

1. Locate the SAML metadata document for your AD FS federation server:

- Default URL: `https://<yourservername>/FederationMetadata/2007-06/FederationMetadata.xml`

- Download and save this document for the next step.

2. Note all Active Directory groups intended for mapping to Oracle Cloud Infrastructure IAM groups.

#### Step 2: Add Active Directory as an Identity Provider in Oracle Cloud Infrastructure

**Summary:** Add the identity provider to your tenancy. Optionally, set up group mappings.

1. Sign in to the Oracle Cloud Infrastructure Console.

2. Navigate to Identity & Security > Federation.

3. Click "Add identity provider" and provide the required information:

- Display Name: A unique name for the federation trust.

- Description: A friendly description.

- Type: Select Microsoft Active Directory Federation Services (ADFS) or SAML 2.0 compliant identity provider.

- XML: Upload the FederationMetadata.xml file downloaded earlier.

Click "Show Advanced Options" for additional settings like assertion encryption and force authentication.

4. Click "Continue" and set up mappings between Active Directory groups and IAM groups.

- Enter the Active Directory group name under Identity Provider Group.

- Choose the corresponding IAM group from the list under OCI Group.

Click "Create" to finish.

#### Step 3: Copy the URL for the Oracle Cloud Infrastructure Federation Metadata Document

**Summary:** Obtain the URL for the Oracle Cloud Infrastructure Federation Metadata document.

1. On the Federation page, click "Download this document."

2. Copy the URL provided, which looks similar to:

- `https://auth.r2.oracleiaas.com/v1/saml/ocid1.tenancy.oc1..aaaaaaaaqdt2tvdmhsa3jmvc5dzulgs3pcv6imfwfgdya4aq/metadata.xml`

#### Step 4: In Active Directory Federation Services, Add Oracle Cloud Infrastructure as a Trusted Relying Party

1. Open the AD FS Management Console and sign in.

2. Add Oracle Cloud Infrastructure as a trusted relying party:

- Right-click AD FS > Add Relying Party Trust.

- Import data about the relying party using the Oracle Cloud Infrastructure Federation Metadata URL copied in Step 3.

Follow the wizard to complete the setup.

#### Step 5: Add Claim Rules for the Oracle Cloud Infrastructure Relying Party

**Summary:** Add claim rules to include required elements in the SAML authentication response.

1. Add the Name ID rule:

- Incoming claim type: Windows account name.

- Outgoing claim type: Name ID with Persistent Identifier format.

- Pass through all claim values.

Click "Finish" and add the groups rule.

#### Step 6: Set up IAM Policies for the Groups

If not done earlier, configure IAM policies to control federated user access to Oracle Cloud Infrastructure resources. Refer to [Getting Started with Policies](#) for guidance.

#### Step 7: Share Tenant Information with Federated Users

Provide federated users with the Oracle Cloud Infrastructure Console URL (`https://cloud.oracle.com`) and your tenant's name. Users will need to input the tenant name when signing in.

---

Cloud Guard

2024-01-09T16:55:00.003+05:30

Automatically identify and remediate security problems.

Cloud Guard is a centralized infrastructure security console that enables IT security and risk management teams to monitor the aggregated security posture for applications, workloads and databases running on Oracle cloud.

Features

Detects misconfigured resources and identifies risky activities.

Delivers out-of-the-box recipes that apply security best practices with a few clicks.

Provides automated responders to trigger corrective actions.

Gives a global view of customer's overall security posture of their OCI tenancy, including security and risk scores and activity maps.

Targets

Targets set the scope of resources to be examined. For OCI, compartments and their descendent structures are used.

Detectors

Detectors are Cloud Guard components that identify issues with resources or user actions and alert when an issue is found.

Problems

Problems are notifications that a configuration or activity is a potential security issue.

Responders

Responders provide notifications and corrective actions to for security problems.

Cloud Guard is not available for free Oracle Cloud Infrastructure tenancies. Before you attempt to enable Cloud Guard, ensure that:

You have a paid tenancy.

Your tenancy account type is one of these:

default_dbaas

enterprise_dbaas

enterprise

Oracle Database@Azure

2024-01-08T17:01:00.001+05:30

# Simplifying Oracle Database@Azure Integration: A Comprehensive Guide

In the dynamic landscape of cloud computing, the collaboration between Oracle and Microsoft has paved the way for streamlined database management through Oracle Database@Azure. This innovative solution combines the power of Oracle Cloud Infrastructure (OCI) with Microsoft Azure, providing users with a seamless and efficient experience. In this article, we'll delve into the key features and step-by-step processes to implement Oracle Database@Azure, covering identity federation, provisioning an Exadata VM cluster, database creation, and Infrastructure as Code (IAC).

### Identity Federation:

- **Purpose:** Federating identities between Entra ID and OCI to reduce management overhead and allow users to access OCI accounts with Azure logins.

- **Benefits:** Enforces consistent identity structure across both cloud providers.

- **Prerequisites for Azure User:** Requires specific Entra ID privileges - External identity provider administrator, Groups administrator, User administrator.

### Groups and Roles:

- **Azure Groups:** Includes infra-admins, VM cluster admins, etc., for administering Exadata database resources and VM clusters in Azure.

- **Replication in OCI:** Groups with attached policies are replicated in OCI during federation.

- **Azure Roles:** Include database owner, infra-admin, VM cluster admin, subscription manager, and database reader with standard permissions.

- **OCI Groups and Policies:** Created to manage database actions.

### Provisioning:

- **Streamlined Process:** Provisioning Oracle Database@Azure resources involves a few simple steps in each portal (Azure and Oracle Cloud Console).

- **Steps in Azure Portal:** Creating infrastructure, VM clusters, etc., involves specifying subscription, resource group, naming, region, availability zone, configuration customization, maintenance setup, consent, tagging, and final review/validation.

- **Resource Deployment:** Resources can be deployed directly from the Azure portal by selecting Oracle Database@Azure from the Azure services.

- **User Prerequisites:** Users must be part of the Exadata infrastructure administrators group in Azure and have sufficient limits assigned to the region.

- **Infrastructure Creation Flow:** Involves steps like Basics (subscription, resource group, naming), Configuration (customization of servers and storage), Maintenance (setting maintenance details), Consent (agreeing to terms), Tags (naming infrastructure resource), and final Review and Create.

## Provisioning an Exadata VM Cluster:

### Prerequisites:

- Grant appropriate permissions for VM cluster admins and Oracle Database@Azure.

- Create a virtual network (vNet) with two delegated subnets for Oracle Database@Azure.

### Required Permissions:

- Microsoft.Network/virtualNetworks/*

- Microsoft.Network/virtualNetworks/subnets/*

### Creation Process:

1. On the Oracle Exadata VM Clusters tab, click the Create link.

2. Follow the multistep process, including Basics, Configuration, Networking, Diagnostics collection, Consent, Tags, and Review and create.

## Database Creation and Management:

Database creation, deletion, and management are facilitated in the Oracle Cloud Console, accessible through single sign-on in the Azure portal. Before proceeding, set up Identity Federation with trust between Azure Entra ID and OCI identity domains. Azure groups must be created and replicated in OCI.

### Creating a Database:

1. Access the Oracle Cloud Console through the Azure portal.

2. Use Console or Database APIs to create database homes, container databases, and pluggable databases.

3. Provide necessary information such as name, database service version (e.g., 19c), admin credentials, backup configuration, etc.

4. Complete the process, and your new database progresses from "Provisioning" to "Available."

## Infrastructure as Code (IAC):

Oracle Database@Azure supports both GUI and CLI operations through PowerShell in Azure and Terraform in OCI. PowerShell is applicable for resources within Azure, while Terraform can be used natively in OCI Resource Manager or as a standalone application for operations in both Azure and OCI.

## Management Responsibilities:

The management responsibilities for Oracle Database@Azure are shared between Oracle, Microsoft, and the customer.

Oracle takes care of Exadata hardware, host infrastructure, and the Oracle Database@Azure API endpoint, while Azure handles the physical network, SDN, and application infrastructure. Data residency and support are shared responsibilities, and customers play a role in certain service components as outlined in the Azure portal and Oracle Cloud Console.

Implementing Oracle Database@Azure empowers organizations with a powerful, collaborative solution that harnesses the strengths of both Oracle and Microsoft. By following these comprehensive steps, users can seamlessly integrate and manage their databases, fostering efficiency and innovation in their cloud journey.

Oracle Database Security Assessment Tool (DBSAT) 3.0

2024-01-08T16:07:00.000+05:30

**Oracle DBSAT 3.0 Unveiled: Strengthening Your Database Security Posture**

**1. Oracle Best Practice Findings:**

- DBSAT 3.0 brings a more nuanced approach to security by clearly identifying findings aligned with Oracle best practices (OBP). This distinction ensures that users not only adhere to conventional security frameworks but also follow recommended configurations specific to Oracle databases.

**2. Expanded Security Checks:**

- The release incorporates a range of new security checks, including support for Oracle Database 23c SQL Firewall. Addressing auditing-related issues, transparent sensitive data protection, and numerous other checks, DBSAT 3.0 provides a more exhaustive examination of database security.

**3. Updated DISA STIG Support:**

- In alignment with the latest US Department of Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG) version V2R8, DBSAT 3.0 ensures that users have the latest guidance and best practices for securing their Oracle databases.

**4. Desupport Notices for Proactive Measures:**

- DBSAT 3.0 assists organizations in proactive risk management by listing desupport notices. This feature helps identify database features and parameters that are approaching or have reached end-of-life, enabling users to take timely measures.

**5. Enhanced Remarks and Recommendations:**

- To facilitate more effective risk mitigation, the remarks and recommendations provided by DBSAT have been updated in version 3.0. These updates aim to make the information clearer and more actionable, aiding users in addressing security issues promptly.

**6. DBSAT Discoverer Enhancements:**

- Reflecting a commitment to global standards, DBSAT Discoverer now includes support for India permanent account number (PAN) and the unique identification (Aadhaar) number, ensuring that users can align their security practices with regional regulatory requirements.

**7. Integration with Oracle Solutions:**

- DBSAT remains a pivotal component in Oracle's security ecosystem, powering various solutions, including Oracle Data Safe Security Assessment, Oracle Audit Vault and Database Firewall, and more. This integration underscores the tool's versatility and centrality in ensuring comprehensive database security.

In essence, Oracle DBSAT 3.0 is not merely an update but a strategic move towards fortifying Oracle database security. Its incorporation of best practices, extended security checks, and support for global standards make it a valuable tool for organizations aiming to enhance their database security posture. Embrace the latest features and stay one step ahead in the ever-evolving landscape of database security.

Oracle Database Security Assessment Tool (DBSAT) (Doc ID 2138254.1)

Oracle Data Safe - Cloud service

2024-01-08T15:33:00.001+05:30

Oracle Data Safe is a comprehensive database security control center designed to protect sensitive and regulated data in Oracle databases. The key features of Oracle Data Safe include:

1. **Security Assessment:**

- Analyzes database configurations, user accounts, and security controls.

- Provides findings and recommendations for remediation activities based on best practices, Security Technical Implementation Guides (STIG), and Center for Internet Security (CIS) Configurations.

2. **User Assessment:**

- Identifies highly privileged accounts that may pose a threat if misused or compromised.

- Reviews user information in the data dictionary, calculating a potential risk score for each user.

- Evaluates user types, authentication methods, password policies, and password change intervals.

- Provides links to audit records related to each user.

3. **Data Discovery:**

- Helps find sensitive data within databases.

- Allows customization for searching specific types of sensitive data.

- Scans actual data in the database and its data dictionary, providing a list of sensitive columns.

- Default searches include identification, biographic, IT, financial, healthcare, employment, and academic information.

4. **Data Masking:**

- Enables the masking of sensitive data for non-production purposes.

- Useful for creating copies of production data for development and testing without exposing sensitive information.

- Replaces sensitive data with realistic but fictitious data.

5. **Activity Auditing:**

- Monitors and audits user activity on databases.

- Helps organizations track and review database usage.

6. **Alerts:**

- Informs users of unusual database activities in real-time.

- Enables proactive response to potential security incidents.

7. **SQL Firewall:**

- Protects against risks such as SQL injection attacks and compromised accounts.

- Built into the Oracle Database 23c kernel.

- Allows centralized management and monitoring of SQL Firewall policies for target databases.

- Collects authorized SQL activities, generates and enables policies with allowlists of approved SQL statements and database connection paths.

- Provides a comprehensive view of SQL Firewall violations across the fleet of target databases.

These features collectively offer a robust and centralized solution for managing the security of Oracle databases, helping organizations comply with regulations and secure sensitive information effectively.

EBS_SYSTEM Schema, AD-TXK DELTA13 and 12.2.11

2021-11-15T16:18:00.010+05:30

Oracle E-Business Suite Release 12.2 System Schema Migration (Doc ID 2755875.1)

Requirements:

AD Delta 13 (or later) and TXK Delta 13 (or later)

EBS 12.2.11 RUP, or EBS Release 12.2.3-12.2.10 and EBS System Schema Migration Consolidated Patch

DB Switchover to Standby - DGMGRL

2021-02-24T10:27:00.002+05:30

prod-ebs-db10

dgmgrl

edit database 'PROD' set state = 'TRANSPORT-OFF';

edit database 'PRODS' set state = 'APPLY-OFF';

On standby database:

CREATE RESTORE POINT DG1 GUARANTEE FLASHBACK DATABASE;

On primary database:

CREATE RESTORE POINT DG1 GUARANTEE FLASHBACK DATABASE;

dgmgrl

edit database 'PROD' set state = 'TRANSPORT-ON';

edit database 'PRODS' set state = 'APPLY-ON';

DB Switchover Steps to DR - STDBY

PROD:oracle@prod-ebs-db10:~>

srvctl stop database -d PROD

PROD:oracle@stdby-ebs-db01:~>

srvctl stop database -d PRODS

Switchover the database

PROD:oracle@prod-ebs-db10:~> srvctl start instance -d PROD -i PROD1

PROD:oracle@prod-ebs-db10:~> srvctl status database -d PROD

PROD:oracle@stdby-ebs-db01:~> srvctl start instance -d PRODS -i PROD1

PROD:oracle@stdby-ebs-db01:~> srvctl status database -d PRODS

PROD:oracle@stdby-ebs-db01:~>dgmgrl /

DGMGRL> show configuration

PROD:oracle@prod-ebs-db10:~>dgmgrl /

PROD:oracle@prod-ebs-db10:~>DGMGRL> show configuration

PROD:oracle@prod-ebs-db10:~>DGMGRL> validate database 'PROD';

PROD:oracle@stdby-ebs-db01:->DGMGRL> validate database 'PRODS'

PROD:oracle@prod-ebs-db10:~>DGMGRL> connect sys@PROD

PROD:oracle@prod-ebs-db10:~>DGMGRL> validate database 'PROD'

PROD:oracle@prod-ebs-db10:~>DGMGRL> switchover to 'PRODS'

PROD:oracle@prod-ebs-db10:~> srvctl status database -d PROD

PROD:oracle@prod-ebs-db10:~>sqlplus / as sysdba

set pages 1000

SELECT

name,

db_unique_name,

open_mode,

database_role,

switchover#

FROM

v$database;

PROD:oracle@prod-ebs-db10:~>

srvctl config database -d PROD

PROD:oracle@stdby-ebs-db01:~>

srvctl config database -d PRODS

PILLAR1:oracle@stdby-ebs-db01:~>

srvctl status service -d PRODS

stdby-ebs-db01

srvctl add service -d PRODS -s APPS_SRVC -r PROD1 -a PROD2 -e SELECT -m BASIC -q TRUE -w 5 -z 180 -P BASIC

srvctl add service -d PRODS -s PROD_SRVC -r PROD1 -a PROD2 -e SELECT -m BASIC -q TRUE -w 5 -z 180 -P BASIC

Configure DB and Apps after Switchover

UTL_FILE_DIR issue in 19c

2021-02-22T21:02:00.001+05:30

Concurrent requests/reports fails with below error after DB is upgraded to 19c.

Cause: FDPSTP failed due to ORA-20100: ORA-20100: Temporary file creation for FND_FILE failed.

Directory &FILE_DIR is invalid, contact your system administrator.

Action: Check that the directory is a valid directory with wri

Fix:

======

Create the first directory that was existing in utl_file_dir parameter in 12c before the DB upgrade.

1) Connect to the PDB.

alter session set container=TST;

2) Create the directory

CREATE OR REPLACE DIRECTORY APPLPTMP AS '/u01/TEST/applptmp';

3) Run autoconfig on DB and APPS:

cd $ORACLE_HOME/appsutil/bin/

0/dbhome_1/appsutil/TEST_xxxx-365-db02.xml \LE_HOME/appsutil/bin/txkCfgUtlfileDir.pl -contextfile=/u01/app/oracle/product/19.3.0.

> -oraclehome=/u01/app/oracle/product/12.1.0 -outdir=/u01/app/oracle/product/19.3.0.0/dbhome_1/appsutil/log \

> -upgradedhome=/u01/app/oracle/product/19.3.0.0/dbhome_1 -mode=getUtlFileDir -servicetype=onpremise

Enter the APPS Password:

Script Name : txkCfgUtlfileDir.pl

Script Version : 120.0.12020000.11

Started : xxxxxx xxxx xxxx xxxxx

Log File : /u01/app/oracle/product/19.3.0.0/dbhome_1/appsutil/log/TXK_UTIL_DIR_Tue_xx_xx_xx_xx_1/txkCfgUtlfileDir.log

Context file: /u01/app/oracle/product/19.3.0.0/dbhome_1/appsutil/TEST_xxxx-365-db02.xml exists.

==============================================================================

Successfully generated the below file with UTL_FILE_DIR content:

/u01/app/oracle/product/19.3.0.0/dbhome_1/dbs/TEST_utlfiledir.txt

==============================================================================

Completed : Tue JXXX xx xx:00

Successfully Completed the script

ERRORCODE = 0 ERRORCODE_END

[TEST|orateb1@xxx-365-db02 bin]$ vi /u01/app/oracle/product/19.3.0.0/dbhome_1/dbs/TST_utlfiledir.txt

OCI - Mobile APP

2021-02-22T13:41:00.002+05:30

OCI Mobile APP

Using the mobile APP for OCI, below tasks can be performed.

Check for the resources by each compartment.
Monitor resource health, properties,metrics.
Check CPU, Memory and I/O usage.
View Alarms, Billing Information.
Check Service limits , Quotas, Usage.

ADOP - File System Synchronization Options - 12.2.10

2021-02-18T19:06:00.003+05:30

ADOP - File System Synchronization Options

On R12.AD.C.Delta.12 and R12.TXK.C.Delta.12, or on EBS 12.2.10,

We have below options for Prepare and Fs_clone respectively.

prepare_sync_mode — Valid for prepare phase.

Can have a value of either or delta or patch. The default is patch.

Specifying delta uses the file system synchronization command specified in the $APPL_TOP_NE/ad/admin/delta_sync_drv.txt file.

Specifying patch reapplies all the patches that were applied to the run file system.

fs_clone_sync_mode — Valid for prepare and fs_clone phases.

Can have a value of either cp or delta. The default is cp.

Specifying cp creates the complete patch file system from the run file system.

Specifying delta uses the file system synchronization command specified in the $APPL_TOP_NE/ad/admin/delta_sync_drv.txt file.

Install, Configure and Integrate OID 12c and OAM 12c with EBS 12.2

2021-01-13T18:31:00.007+05:30

Install, Configure and Integrate OID 12c and OAM 12c with EBS 12.2

References:

Integrating Oracle E-Business Suite Release 12.2 with Oracle Internet Directory 12c (12.2.1.3.0) (Doc ID 2339362.1)
Integrating Oracle E-Business Suite Release 12.2 with Oracle Access Manager 12c (12.2.1.3.0)
using Oracle E-Business Suite AccessGate (Doc ID 2339348.1)
Overview of Single Sign-On Integration Options for Oracle E-Business Suite (MOS Note 1388152.1)
Example to Install and Configure Oracle Directory Integration Platform (DIP) 12.2.1.3 Separate From Oracle Internet Directory (OID) 12.2.1.3 (Doc ID 2306423.1)

Install OID

Install FMW Infrastructure for OID

[debssso@dev-ebs-sso01 ~]$ cd /stage/soft/
$ /devsso/jdk/bin/java -jar fmw_12.2.1.3.0_infrastructure.jar

Install OID 12c Software

[debssso@dev-ebs-sso01 soft]$ ./fmw_12.2.1.3.0_oid_linux64.bin

Apply patch for RCU Error:

[debssso@dev-ebs-sso01 ~]$ cd /stage/soft/29691671
[debssso@dev-ebs-sso01 29691671]$ export ORACLE_HOME=/devsso/app/oracle/oim
[debssso@dev-ebs-sso01 29691671]$ export PATH=$ORACLE_HOME/OPatch:$PATH
[debssso@dev-ebs-sso01 29691671]$ opatch apply

Run RCU for OID

[debssso@dev-ebs-sso01 soft]$ cd /devsso/app/oracle/oim/oracle_common/bin/
[debssso@dev-ebs-sso01 bin]$ ./rcu

Run config.sh for OID

[debssso@dev-ebs-sso01 bin]$ cd ../common/bin/
[debssso@dev-ebs-sso01 bin]$ ./config.sh

Choose OID (Collocated) and DIP
Listen Address: dev-ebs-sso01.us.corp.example2qa.com

Install OAM

Install FMW Infrastructure for OAM

[debssso@dev-ebs-sso01 bin]$ cd /stage/soft/
[debssso@dev-ebs-sso01 soft]$ /devsso/jdk1.8.0_251/bin/java -jar fmw_12.2.1.3.0_infrastructure.jar

Install OAM 12c Software

[debssso@dev-ebs-sso01 soft]$ /devsso/jdk1.8.0_251/bin/java -jar fmw_12.2.1.3.0_idm.jar

Run RCU for OAM

[debssso@dev-ebs-sso01 soft]$ cd /devsso/app/oracle/oam/oracle_common/bin/
[debssso@dev-ebs-sso01 bin]$ ./rcu

Run config.sh for OAM

cd /devsso/app/oracle/oam/oracle_common/common/bin
./config.sh

On EBSQ1 Instance, Install Webgate

txkrun.pl -script=SetOAMReg -installWebgate=yes -webgatestagedir=/finapp/EBSQ1/OAM_Webgate

Apply OAM Webgate Bundle Patch 29309637

[EBSQ1@qa-ebs-app01 ~]$ which curl
/usr/bin/curl
[EBSQ1@qa-ebs-app01 ~]$ ls -trl /usr/bin/curl
-rwxr-xr-x. 1 root root 156672 Apr 2 19:02 /usr/bin/curl
[EBSQ1@qa-ebs-app01 ~]$ ldd /usr/bin/curl
[EBSQ1@qa-ebs-app01 ~]$ ls -ltr /usr/lib64/libcurl.so.4*
-rwxr-xr-x. 1 root root 439344 Apr 2 19:02 /usr/lib64/libcurl.so.4.3.0
lrwxrwxrwx. 1 root root 16 May 11 07:34 /usr/lib64/libcurl.so.4 -> libcurl.so.4.3.0
[root@qa-ebs-app01 ~]# cd /usr/lib64
[root@qa-ebs-app01 lib64]# ln -s /usr/lib64/libcurl.so.4.3.0 libcurl.so
[root@qa-ebs-app01 lib64]# ls -trl /usr/lib64/libcurl.so
lrwxrwxrwx. 1 root root 27 Jul 13 08:54 libcurl.so -> /usr/lib64/libcurl.so.4.3.0

[EBSQ1@qa-ebs-app01 ContentsXML]$ cd $FMW_HOME/
[EBSQ1@qa-ebs-app01 FMW_Home]$ export ORACLE_HOME=/finapp/EBSQ1/fs1/FMW_Home/Oracle_OAMWebGate1
[EBSQ1@qa-ebs-app01 FMW_Home]$ export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH
[EBSQ1@qa-ebs-app01 FMW_Home]$ cd /finapp/EBSQ1/OAM_Webgate/
[EBSQ1@qa-ebs-app01 OAM_Webgate]$ cd 29309637/
[EBSQ1@qa-ebs-app01 29309637]$ opatch apply -jdk $COMMON_TOP/util/jdk64

On EBSQ1 Instance, Deploy Access Gate

[EBSQ1@qa-ebs-app01 ~]$ perl $AD_TOP/patch/115/bin/adProvisionEBS.pl ebs-create-oaea_resources -contextfile=$CONTEXT_FILE -deployApps=accessgate -SSOServerURL=http://dev-ebs-sso01.us.corp.example2qa.com:7021 -managedsrvname=oaea_server1 -managedsrvport=6801 -logfile=OAEA_Server_deploy.log
Enter the APPS Schema password:
Enter the WebLogic AdminServer password:

Add MS to Config files

$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl \
-contextfile=$CONTEXT_FILE \
-configoption=addMS \
-accessgate=qa-ebs-app01.us.corp.example2qa.com:6801

Register OID with EBS

[EBSQ1@qa-ebs-app01 ~]$ $FND_TOP/bin/txkrun.pl -script=SetSSOReg -registeroid=yes -ldaphost=dev-ebs-sso01.us.corp.example2qa.com -ldapport=9055 -oidadminuser=cn=orcladmin -oidadminuserpass=devsso2020 -appspass=fvcey3xnab -instpass=fvcey3xnab -appname=EBSQ1 -svcname=EBSQ1 -provisiontype=4 -dbldapauthlevel=0

Update Profiles

SQL> set serveroutput on
DECLARE
stat BOOLEAN;
BEGIN
stat := FND_PROFILE.SAVE('APPS_SSO_OID_IDENTITY','Y','SITE');
IF stat THEN
dbms_output.put_line( 'Profile APPS_SSO_OID_IDENTITY updated with Enabled ' );
commit;
ELSE
dbms_output.put_line( 'Profile APPS_SSO_OID_IDENTITY could NOT be updated with Enabled' );
rollback;
END IF;
END;
/

SQL> set serveroutput on
DECLARE
stat BOOLEAN;
BEGIN
stat := FND_PROFILE.SAVE('APPS_SSO_LINK_SAME_NAMES','Y','SITE');
IF stat THEN
dbms_output.put_line( 'Profile APPS_SSO_LINK_SAME_NAMES updated with Enabled' );
commit;
ELSE
dbms_output.put_line( 'Profile APPS_SSO_LINK_SAME_NAMES could NOT be updated with Enabled' );
rollback;
END IF;
END;
/

SQL> set serveroutput on
DECLARE
stat BOOLEAN;
begin
stat := FND_PROFILE.SAVE('APPS_SSO', 'SSWA_SSO', 'SITE');
IF stat THEN
dbms_output.put_line( 'Profile APPS_SSO updated with SSWA_SSO' );
commit;
ELSE
dbms_output.put_line( 'Profile APPS_SSO could NOT be updated with SSWA_SSO' );
rollback;
END IF;
end;
/

Run autoconfig

Bring down Services

adstpall.sh
adautocfg.sh

Enable TLS

Generate CSR for certs

[debssso@dev-ebs-sso01 devwallet]$ export JAVA_HOME=/devsso/jdk1.8.0_251
[debssso@dev-ebs-sso01 devwallet]$ /devsso/app/oracle/oim/bin/orapki wallet create -wallet . -pwd devsso2020
[debssso@dev-ebs-sso01 devwallet]$ /devsso/app/oracle/oim/bin/orapki wallet add -wallet . -dn "CN=dev-ebs-sso01.us.corp.example2qa.com,OU=IT,O=Example,L=Cambridge,S=MA,C=US,emailAddress=db-admins@example.com" -keysize 2048
Enter wallet password:

[debssso@dev-ebs-sso01 devwallet]$ /devsso/app/oracle/oim/bin/orapki wallet export -wallet . -dn "CN=dev-ebs-sso01.us.corp.example2qa.com,OU=IT,O=Example,L=Cambridge,S=MA,C=US,emailAddress=db-admins@example.com" -request ./dev-ebs-sso01.csr
Enter wallet password:

Add certs to wallet

[debssso@dev-ebs-sso01 devwallet]$ /devsso/app/oracle/oim/bin/orapki wallet add -wallet /devsso/devwallet/. -trusted_cert -cert /devsso/devwallet/root.cer -pwd devsso2020

[debssso@dev-ebs-sso01 devwallet]$ pwd
/devsso/devwallet
[debssso@dev-ebs-sso01 devwallet]$ /devsso/app/oracle/oim/bin/orapki wallet add -wallet /devsso/devwallet/. -trusted_cert -cert /devsso/devwallet/intermediary.cer -pwd devsso2020

[debssso@dev-ebs-sso01 devwallet]$ /devsso/app/oracle/oim/bin/orapki wallet add -wallet /devsso/devwallet/. -user_cert -cert /devsso/devwallet/dev-ebs-sso01.cer -pwd devsso2020

[debssso@dev-ebs-sso01 devwallet]$
[debssso@dev-ebs-sso01 devwallet]$ /devsso/app/oracle/oim/bin/orapki wallet display -wallet .

Prepare Java Keystores

[debssso@dev-ebs-sso01 ~]$ /devsso/app/oracle/oim/bin/orapki wallet pkcs12_to_jks -wallet /devsso/devwallet -pwd devsso2020 -jksKeyStoreLoc /devsso/devwallet/devssoK.jks -jksKeyStorepwd devsso2020 -jksTrustStoreLoc /devsso/devwallet/devssoT.jks -jksTrustStorepwd devsso2020
Oracle PKI Tool : Version 12.1.0.2
Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved.

[debssso@dev-ebs-sso01 ~]$ cd /devsso/devwallet/

[debssso@dev-ebs-sso01 devwallet]$
keytool -import -trustcacerts -alias cert1 -file /devsso/devwallet/adcert1.txt -keystore /devsso/devwallet/devssoDIP.jks
keytool -import -trustcacerts -alias cert2 -file /devsso/devwallet/adcert2.txt -keystore /devsso/devwallet/devssoDIP.jks

On OIM_Domain Weblogic Console, Perform Below Steps:

a)Update Keystore Location and password for OIM Adminserver

b)Update Hostname verification to “None”

c)Verify and Update the Listen Address, Listen Port and SSL Listen port for Admin Server

d)Update Keytstore location and password for WLS_ODS1

e)Update HostName Verification to “None”

f)Verify and Update Listen Address,Port and SSL Listen Port for WLS_ODS1 Managed Server

g)Copy boot.properties

[debssso@dev-ebs-sso01 ~]$ cd /devsso/app/oracle/oim/user_projects/domains/OIM_domain/servers/wls_ods1
[debssso@dev-ebs-sso01 wls_ods1]$ mkdir security
[debssso@dev-ebs-sso01 wls_ods1]$ cd security/
[debssso@dev-ebs-sso01 security]$ ls
[debssso@dev-ebs-sso01 security]$ cp /devsso/app/oracle/oim/user_projects/domains/OIM_domain/servers/AdminServer/security/boot.properties /devsso/app/oracle/oim/user_projects/domains/OIM_domain/servers/wls_ods1/security
[debssso@dev-ebs-sso01 security]$ ls -trl
total 4
-rw-r-----. 1 debssso dba 186 Jul 15 15:23 boot.properties
[debssso@dev-ebs-sso01 security]$

Update SSL Mode for DIP Server

[debssso@dev-ebs-sso01 ~]$ export JAVA_HOME=/devsso/jdk1.8.0_251
[debssso@dev-ebs-sso01 ~]$
$ORACLE_HOME/bin/manageDIPServerConfig set -attribute sslmode -val 1 -h dev-ebs-sso01.us.corp.example2qa.com -p 9009 -D "weblogic"
[Weblogic user password]
Connection parameters initialized.
Connecting at dev-ebs-sso01.us.corp.example2qa.com:9009, with userid "weblogic"..
Connected successfully.
The attribute sslmode is successfully changed to value 1.
[debssso@dev-ebs-sso01 ~]$

Add Cipher Suites Configured for OID into DIP

http://dev-ebs-sso01.us.corp.example2qa.com:9001/em/
Weblogic -> OIM_Domain -> wls_ods1 -> Weblogic Server -> System MBean Browser -> com.bea -> Server -> wls_ods1 -> SSL -> wls_ods -> CipherSuites

Add

TLS_DH_anon_WITH_AES_128_GCM_SHA256
SSL_DH_anon_WITH_3DES_EDE_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_AES_256_GCM_SHA384
TLS_RSA_WITH_AES_128_GCM_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA
TLS_RSA_WITH_AES_128_CBC_SHA
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA

Update /devssp/jdk/jre/lib/security/java.security file

jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, DH keySize < 1024, \
EC keySize < 224, DES40_CBC, RC4_40, 3DES_EDE_CBC

- Apply weblogic patch

- Upgrade OPatch to 13.9.4
java -jar /stage/soft/WLS_Patch/6880880/opatch_generic.jar -silent oracle_home=/devsso/app/oracle/oim

- Apply OUI patch

export ORACLE_HOME=/devsso/app/oracle/oim
export PATH=$ORACLE_HOME/OPatch:$PATH
cd /stage/soft/WLS_Patch/29909359
opatch apply -silent -jre /devsso/jdk/jre

- Apply latest WL PSU patch

export ORACLE_HOME=/devsso/app/oracle/oim
export PATH=$ORACLE_HOME/OPatch:$PATH
cd /stage/soft/WLS_Patch/31535411
opatch apply -silent
cd /stage/soft/WLS_Patch/31544340
opatch apply -silent

- Apply OID mandatory patches

cd /stage/soft/OID_Patch/31404516
opatch apply -silent
cd /devsso/soft/OID_Patch/26649795
opatch apply -silent
vi db.properties
DRIVER_NAME:oracle.jdbc.OracleDriver
DRIVER_TYPE:thin
DB_HOST:debssso-db.example.com
DB_PORT:1631
DB_SERVICENAME:DEBSSSO_SRV
[debssso@dev-ebs-sso01 oracle]$ pwd
/devsso/app/oracle

Setup OID

sh $ORACLE_HOME/oracle_common/common/bin/wlst.sh
connect('weblogic','weblogic1','t3://dev-ebs-sso01.us.corp.example2qa.com:9001')
wls:/OIM_domain/serverConfig/> oid_setup(orcladminPassword = 'devsso2020', odsPassword = 'example123', realmDN ='dc=corp,dc=example2qa,dc=com', port=9055, sslPort=9057)

Store User Config for OID

[debssso@dev-ebs-sso01 logs]$ cd $ORACLE_HOME
[debssso@dev-ebs-sso01 oim]$ cd user_projects/domains/OIM_domain/
[debssso@dev-ebs-sso01 OIM_domain]$ cd bin
[debssso@dev-ebs-sso01 bin]$ sh startComponent.sh oid1 storeUserConfig

Configure DIP with OID

[debssso@dev-ebs-sso01 oracle]$ export ORACLE_HOME=/devsso/app/oracle/oim
[debssso@dev-ebs-sso01 oracle]$ export WL_HOME=/devsso/app/oracle/oim/wlserver
[debssso@dev-ebs-sso01 oracle]$ export JAVA_HOME=/devsso/jdk1.8.0_251
[debssso@dev-ebs-sso01 oracle]$ $ORACLE_HOME/bin/dipConfigurator setup -wlshost dev-ebs-sso01.us.corp.example2qa.com -wlsport 9001 -wlsuser weblogic -ldaphost dev-ebs-sso01.us.corp.example2qa.com -ldapport 9057 -ldapuser "cn=orcladmin" -isldapssl true -dbconfigfile db.properties
Enter password to contact WebLogic Server :
Enter password to contact LDAP Server :

Modify OID startNodeManager.sh

cd /devsso/app/oracle/oim/user_projects/domains/OIM_domain/bin
cp startNodeManager.sh startNodeManager.sh_v1

Add

JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.nodemanager.sslHostNameVerificationEnabled=false -Dweblogic.security.SSL.minimumProtocolVersion=TLSv1.2 "
export JAVA_OPTIONS

cd /devsso/app/oracle/oim/user_projects/domains/OIM_domain/nodemanager
cp nodemanager.properties nodemanager.properties_v1

vi nodemanager.properties
KeyStores=CustomIdentityAndCustomTrust
CustomIdentityAlias=oraKey
CustomIdentityKeyStoreFileName=/devsso/devwallet/devssoK.jks
CustomIdentityKeyStorePassPhrase=devsso2020
CustomIdentityKeyStoreType=JKS
CustomIdentityPrivateKeyPassPhrase=devsso2020

Update cacerts in JDK

cd /devsso/jdk/jre/lib/security
cp cacerts cacerts_v1
keytool -import -trustcacerts -file /devsso/devwallet/root.cer -alias exampleroot -keystore /devsso/jdk/jre/lib/security/cacerts
keytool -import -trustcacerts -file /devsso/devwallet/intermediary.cer -alias exampleint -keystore /devsso/jdk/jre/lib/security/cacerts

Update Java options in SetDomainEnv.sh

cd /devsso/app/oracle/oim/user_projects/domains/OIM_domain/bin
cp setDomainEnv.sh setDomainEnv.sh_v1
JAVA_OPTIONS=" -Dweblogic.security.SSL.enableJSSE=true -Dweblogic.ssl.JSSEEnabled=true -Dweblogic.security.SSL.protocolVersion=TLSv1.2 -Dweblogic.security.SSL.minimumProtocolVersion=TLSv1.2 ${JAVA_OPTIONS} "
export JAVA_OPTIONS
EXTRA_JAVA_PROPERTIES="-Djava.io.tmpdir=/devsso/temp ${EXTRA_JAVA_PROPERTIES}"
export EXTRA_JAVA_PROPERTIES

Update keystorelocation for DIP Server

[debssso@dev-ebs-sso01 bin]$ ./manageDIPServerConfig get -h dev-ebs-sso01.us.corp.example2qa.com -p 9009 -D weblogic -attr keystorelocation
[Weblogic user password]
The attribute keystorelocation has value JKS_KEYSTORE_LOCATION.
[debssso@dev-ebs-sso01 bin]$ ./manageDIPServerConfig set -h dev-ebs-sso01.us.corp.example2qa.com -p 9009 -D weblogic -attr keystorelocation -val /devsso/devwallet/devssoDIP.jks
[Weblogic user password]
The attribute keystorelocation is successfully changed to value /devsso/devwallet/devssoDIP.jks.

Set the JKS Password

debssso@dev-ebs-sso01 bin]$ sh $ORACLE_HOME/oracle_common/common/bin/wlst.sh
wls:/offline> connect('weblogic','weblogic1' ,'t3://dev-ebs-sso01.us.corp.example2qa.com:9001')
wls:/OIM_domain/serverConfig/> createCred(map="dip", key="jksKey", user="jksuser", password="devsso2020")
Apply TXK patches for OAM Registration
[hostq1@qa-ebs-app01 OAM]$ adop phase=apply patches=31142470,26401178,26879682,29460647 patchtop=/stage/soft/OAM apply_mode=downtime

Register OAM

[hostq1@qa-ebs-app01 config]$ txkrun.pl -script=SetOAMReg -registeroam=yes \
-oamHost=http://dev-ebs-sso01.us.corp.example2qa.com:9021 \
-oamUserName=weblogic \
-ldapUrl=ldap://dev-ebs-sso01.us.corp.example2qa.com:9055 \
-oidUserName=cn=orcladmin \
-skipConfirm=yes \
-ldapSearchBase=dc=corp,dc=example2qa,dc=com \
-ldapGroupSearchBase=dc=corp,dc=example2qa,dc=com

Create Synchronization Profiles

Profile name : AD_TO_OID
Host : corp.example2qa.com
Port : 636
User : svc_oraclesync@corp.example2qa.com
Pwd : _xxxxxxx
Edit Mapping Rules

Synchronize Bootstrap Profile

export WL_HOME=/devsso/app/oracle/oim/wlserver
export ORACLE_HOME=/devsso/app/oracle/oim

cd $ORACLE_HOME/bin
./syncProfileBootstrap -h dev-ebs-sso01.us.corp.example2qa.com -port 9009 -D weblogic -profile ad_to_oid -lp 50

Run Multiple times till Entries Failed is 0
The bootstrap operation completed, the operation results are:
entries read in bootstrap operation: 24964
entries filtered in bootstrap operation: 0
entries ignored in bootstrap operation: 0
entries processed in bootstrap operation: 3172
entries failed in bootstrap operation: 21792

High-Level EBS Upgrade Steps 12.1.3 to 12.2.9

2021-01-13T14:11:00.001+05:30

OCI-CLI Buckets and Objects

2020-03-11T22:22:00.001+05:30

BUCKETS
=======

LIST ---

oci os bucket list -ns kaless --compartment-id ocid1.compartment.oc1..xxxxxxxxxxxxxxxxccccccccccccdddddddddddddd

CREATE ---

oci os bucket create -ns kaless --name CLIbucket --compartment-id ocid1.compartment.oc1..xxxxxxxxxxxxxxxxccccccccccccdddddddddddddd

GET, UPDATE, DELETE ---

oci os bucket get -ns kaless --name CLIarchbucket

oci os bucket update -ns kaless --name CLIarchbucket --compartment-id ocid1.tenancy.oc1..bbbbbbbbbbbbbbbffffffffffffjjjjjjjjjjjjjjjjj

oci os bucket delete -ns kaless --name CLIbucket

OBJECTS
=========

oci os object put -ns kaless -bn hello --file://C:\Pictures --name MyLogo.jpg

oci os object put -ns kaless -bn hello --file://C:\Pictures --name BigPic.jpg --part-size
--parallel-upload-count

oci os bucket create -ns kaless --name hello --compartment-id ocid1.compartment.oc1..aaaaaaaaddp3cccccccccccccccccccbbbbbbbbvv
--metadata file://C:\temp\testfile.json

Load data to ADW/ATP using DBMS_CLOUD

2019-12-13T21:42:00.002+05:30

Create Credentials

begin
DBMS_CLOUD.create_credential(
credential_name => 'OBJ_STORE_CRED',
username => 'ale@xxxx.com',
password => 'Auth_Token'
);
end;
/

Check default Bucket:

select property_value from database_properties where property_name='DEFAULT_BUCKET';

Set Default Bucket:

alter database property set default_bucket='https://swiftobjectstorage.region.oraclecloud.com/v1/object_storage_namespace';

List Objects from Bucket:

select * from table(dbms_cloud.list_objects(credential_name => 'DEF_CRED_NAME',location_uri => 'https://objectstorage.region.oraclecloud.com/n/object_storage_namespace/b/bucket/o/'));

Drop Credentials not needed:

BEGIN

DBMS_CLOUD.DROP_CREDENTIAL (

credential_name => 'DEF_CRED_NAME');

END;

Load Data from Object Storage to a Table.

BEGIN
DBMS_CLOUD.COPY_DATA(
table_name =>'EMPLOYEES',
credential_name =>'OBJ_STORE_CRED',
file_uri_list =>'https://swiftobjectstorage..oraclecloud.com/v1///',
format => json_object('delimiter' value ',')
);
END;
/

Log and Status of data Load:

As ADMIN user,

SELECT table_name, owner_name, type, status, start_time, update_time, logfile_table, badfile_table FROM user_load_operations WHERE type = 'COPY' order by start_time desc;

Built-in SQL Developer Web - ADW

2019-12-13T20:41:00.001+05:30

Autonomous Data Warehouse
======================

SQL Developer Web is a browser-based interface of Oracle SQL Developer and
provides a subset of the features of the desktop version.

• Run SQL statements and scripts in the worksheet
• Export data

Oracle SQL Developer Web runs in Oracle REST Data Services and access is
provided through schema-based authentication.

Apex and SQL Developer can be launched from ADW Service Console

Run Queries or Scripts to view Outputs

View data Models and Work on them

APIs, Keys and OCIDs

2019-11-16T19:10:00.000+05:30

EBSCloudBackup.pl is a script which uses APIs and asks for below details for taking a backup of an On-prem Instance to Oracle Cloud Object Storage.

Every resource on OCI has a randomly generated OCID assigned to it.

Oracle Cloud User Name : xxxxx@yyyyy.com
Oracle Cloud User Auth Token : ********************

Oracle Cloud Infrastructure Details:

Oracle Storage Cloud Service Endpoint : https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/tenancyName
Oracle Cloud User Name : xxxxxxxx@yyyyyyyyyy.com
Oracle Cloud User OCID : ocid1.user.oc1..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Oracle Cloud Fingerprint : f0:05:f4:dd:15:03:7a:4a:e1:fc:f7:1d:b3:c2:ef:70
Oracle Cloud User Private Key Path : /stage/EbsBackup/oci_api_key.pem
Oracle Cloud Tenancy OCID : ocid1.tenancy.oc1..aaaaaaaaymxxxxxxxxxxxxxxxxxxxxpppppppppppppp
Oracle Cloud Region : us-ashburn-1
Oracle Cloud Tenant Name : TenancyName
Oracle Cloud Compartment OCID : ocid1.compartment.oc1..bbbbbbbbbbbbbbbbbbbbbxxxxxxxxxxxxxxpppppppppp
Target Database Type : Compute

Where do we find the details on OCI?

Tenancy OCID:

User OCID:

Generate Token for user - User Auth Token

Generate a Public Key -- and Upload the key to OCI so that you will get a Fingerprint needed above.

Download and Install Git Bash

Generate the private key and Public key as below using gitbash.

$ mkdir ~/.oci

$ openssl genrsa -out ~/.oci/oci_api_key.pem -aes128 -passout stdin 2048

$ chmod go-rwx ~/.oci/oci_api_key.pem

$ openssl rsa -pubout -in ~/.oci/oci_api_key.pem -out ~/.oci/oci_api_key_public.pem -passin stdin

Copy the public key to upload to OCI.

cat ~/.oci/oci_api_key_public.pem

-----BEGIN PUBLIC KEY-----

---------------------------------------xxxxxxxxxxxxx

xxxxxxxxxxxxxxxxxxxxxxxyyyyyyyyyyyyyyyyy

hhhhhhhhhhhhhhhhhhhhhhhhhhhyyyyyyyyyyyy

kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk

sssssssssssssssssssssssssssssssssssssssssssssss

................................................

-----------------------------------------------------

-----END PUBLIC KEY-----

Upload the Public Key to OCI.

Note the Finger Print:

Fingerprint: xx:yy:11:33:44:yy:77:pp:dd:tt:

Oracle Applications DBA

Zero Downtime Migration (ZDM)

Install, configure, and migrate an Oracle database using Zero Downtime Migration (ZDM)

ZDM - Pause after ZDM_CONFIGURE_DG_SRC

Oracle ZDM – Zero Downtime Migration

1. Introduction to ZDM

2. Architecture Overview

3. Pre-requisites

4. ZDM Installation

5. Response File Parameters

6. Migration Execution Flow

7. Pause After DG Configuration

8. Monitoring & Logs

9. Troubleshooting

10. Best Practices & Tips

An Oracle Database Performance Crisis/Scenario : A Comprehensive Analysis and Strategic Recommendations

TOP 10 COMMON CAUSES FOR A DATABASE CRASH AND THEIR POSSIBLE FIXES

THE FLOW OF A SELECT OR DML INSIDE ORACLE DATABASE

ECPUC

ECPUC.sql

Vulnerability Scanning Service

Federating Microsoft Active Directory on Oracle Cloud Infrastructure

Cloud Guard

Oracle Database@Azure

Oracle Database Security Assessment Tool (DBSAT) 3.0

Oracle Data Safe - Cloud service

EBS_SYSTEM Schema, AD-TXK DELTA13 and 12.2.11

DB Switchover to Standby - DGMGRL

UTL_FILE_DIR issue in 19c

OCI - Mobile APP

OCI Mobile APP

Using the mobile APP for OCI, below tasks can be performed.Check for the resources by each compartment. Monitor resource health, properties,metrics.Check CPU, Memory and I/O usage.View Alarms, Billing Information.Check Service limits , Quotas, Usage.

ADOP - File System Synchronization Options - 12.2.10

Install, Configure and Integrate OID 12c and OAM 12c with EBS 12.2

Install, Configure and Integrate OID 12c and OAM 12c with EBS 12.2

Install OID

Install FMW Infrastructure for OID

Install OID 12c Software

Apply patch for RCU Error:

Run RCU for OID

Run config.sh for OID

Install OAM

Install FMW Infrastructure for OAM

Install OAM 12c Software

Run RCU for OAM

Run config.sh for OAM

On EBSQ1 Instance, Install Webgate

Apply OAM Webgate Bundle Patch 29309637

On EBSQ1 Instance, Deploy Access Gate

Add MS to Config files

Register OID with EBS

Update Profiles

Enable TLS

Generate CSR for certs

Add certs to wallet

Prepare Java Keystores

On OIM_Domain Weblogic Console, Perform Below Steps:

Update SSL Mode for DIP Server

Add Cipher Suites Configured for OID into DIP

Update /devssp/jdk/jre/lib/security/java.security file

- Apply weblogic patch

- Apply OUI patch

- Apply latest WL PSU patch

- Apply OID mandatory patches

Setup OID

Store User Config for OID

Configure DIP with OID

Modify OID startNodeManager.sh

Add

Update cacerts in JDK

Update Java options in SetDomainEnv.sh

Update keystorelocation for DIP Server

Set the JKS Password

Register OAM

Create Synchronization Profiles

Synchronize Bootstrap Profile

High-Level EBS Upgrade Steps 12.1.3 to 12.2.9

OCI-CLI Buckets and Objects

Load data to ADW/ATP using DBMS_CLOUD

Built-in SQL Developer Web - ADW

Using the mobile APP for OCI, below tasks can be performed.

Check for the resources by each compartment.
Monitor resource health, properties,metrics.
Check CPU, Memory and I/O usage.
View Alarms, Billing Information.
Check Service limits , Quotas, Usage.