Identifying the Running Applications in a Database for Migration from Oracle12c to Exacc

Discover how to identify all applications running in a particular database before migrating from Oracle12c to Exacc. Simplified solutions and insights inside!
---
This video is based on the question https://stackoverflow.com/q/73223616/ asked by the user 'Oze' ( https://stackoverflow.com/u/17984830/ ) and on the answer https://stackoverflow.com/a/73250030/ provided by the user 'Connor McDonald' ( https://stackoverflow.com/u/7367293/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Number of application running in a particular database

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Finding Running Applications in a Database for Migration

Migrating applications from one database environment to another can be a challenging task, especially when dealing with a legacy application on Oracle12c. Many organizations face the dilemma of identifying which applications are currently running on a given database, particularly when several applications share the same database resources. In this guide, we will explore an effective solution to identify those applications and ensure a smooth transition to Exacc.

Understanding the Challenge

When you have a common database that hosts multiple applications, it's crucial to determine which applications are relevant to your migration. This challenge becomes even more urgent when you aim to avoid migrating unnecessary applications that could complicate the transition or resource allocation in the new environment.

Solution Overview

The key to identifying running applications lies in the implementation of database auditing. Database auditing allows you to monitor and log specific actions that can provide insights into the applications connecting to your database.

Step 1: Turn on Auditing

To start, you must enable session auditing. This can be done with a simple command:

[[See Video to Reveal this Text or Code Snippet]]

By activating session auditing, you can capture significant details about the sessions interacting with your database.

Step 2: Monitor the Audit Trail

Once auditing is turned on, your database will start recording various session details in the audit trail. The information collected may include:

Schema Names: Identifies which schema (or application context) the session is associated with.

Machine Names: Provides the name of the machine that is connecting to your database.

OS User: Displays the operating system user credentials being used for the connection.

Module Information: Indicates the application module that initiated the session.

Client Info: Gives further context regarding the application requesting the connection.

Action Details: Describes the actions being performed within the session.

Step 3: Analyze the Data

With the audit trail compiled, you can analyze the logged data to deduce which applications are running on the database. Here are a few tips for this analysis:

Look for frequent schema accesses to identify applications heavily interacting with the database.

Correlate machine names and OS users to pinpoint applications on specific devices or user accounts.

Review module names to get a clearer understanding of the applications and their usage patterns.

Optional: Deeper Insight through SQL Auditing

If you require more detailed insight into the application behaviors, consider auditing every SQL statement executed:

[[See Video to Reveal this Text or Code Snippet]]

(Note: Replace <table_name> with the specific table you want to audit.)

This step will provide you with a granular level of detail, which could help identify not just which applications are using the database, but also how they are interacting with it.

Conclusion

Identifying which applications are currently running in your database prior to migration is crucial for a streamlined transition to Exacc. By enabling session auditing and analyzing the audit trail, you can gather valuable insights into the schemas and applications that are active. This knowledge will empower your migration strategy, ensuring only the relevant applications are moved while minimizing disruptions in your organization’s workflow.

Ready to find out which applications you should migrate? Start enabling your session auditing today!