OraEasy

Introduction Oracle Database Auditing is a crucial tool that helps database administrators monitor and record activities occurring within the database environment. By tracking actions such as data modifications, user access, and system changes, auditing provides a detailed record of who did what and when. This is the first post in a series on Oracle auditing, and it covers Standard Auditing: what it is, how it compares to the other auditing types, and how to configure it step by step. Types of Auditing in Oracle Oracle supports four distinct approaches to auditing, each suited to different needs. Mandatory Auditing Certain critical actions and users, such as SYSDBA, are audited by default with no configuration required, ensuring that the most sensitive operations are always tracked. This includes: Logons by privileged users connecting with SYSDBA, SYSOPER, or similar administrative roles. Startup and shutdown operations of the Oracle instance. DDL and DML statements affecti...

Introduction Oracle Enterprise Manager (OEM) is Oracle's unified management platform for overseeing the full Oracle technology stack. It enables administrators to monitor, configure, and optimize Oracle Databases, Oracle Middleware, Oracle Applications, and Oracle Engineered Systems from a single console. OEM streamlines critical operations such as patching, configuration management, performance diagnostics, and lifecycle automation, keeping Oracle workloads secure, reliable, and high-performing. This article walks through configuring OEM on a Linux environment step by step. Prerequisites Below are the minimum requirements for a Linux environment: CPU: 2 cores RAM: 10GB Disk space: 45GB (/u01) and 50GB (/oem) OEM binary, downloadable here . Root user or sudo access. Firewall disabled. Environment Used in This Guide Hostname oem.oraeasy.com / 192.168.1.33 OS OL 7.3 OEM Version 13c Release 5 (13.5) OMS Home ...

Introduction Automatically starting and stopping database services during server reboots or shutdowns avoids manual intervention and keeps operations running smoothly. Oracle provides built-in scripts, dbstart and dbshut, for exactly this purpose. By wiring these into a Linux service through systemd or init.d, the database and listener come up automatically when the server boots and shut down cleanly when it powers off. This article walks through setting that up step by step. Prerequisites Root user or sudo access. Environment Used in This Guide Hostname orcl.oraeasy.com OS OL9 Database Name ORCLDC Database Version 19.27.0 Oracle Home /u01/app/oracle/product/19.0.0/dbhome_1 Approach: We'll use Oracle's own scripts for auto startup (dbstart) and shutdown (dbshut), which live in $ORACLE_HOME/bin , wrapped in a small init script that systemd can manage. Step 1: Enable Auto Start in /...

Introduction This is the third post in our four-part series on upgrading Oracle Database from 12c to 19c. We've already covered the GUI-driven Upgrade Using DBUA and the Upgrade Using Manual Method . This time we'll use autoupgrade.jar , Oracle's own command-line tool that drives the same underlying upgrade through a single config file, which makes it a natural fit for scripting and batch upgrades of multiple databases. Methods of Upgrade As a reminder, Oracle supports four approaches for this upgrade: Using DBUA (Database Upgrade Assistant) Using the manual method Using autoupgrade.jar Using RMAN and catctl.pl Unlike DBUA, autoupgrade.jar needs no GUI or X11 forwarding, and unlike the manual method, it doesn't require running each catalog step by hand. It reads a config file describing the source and target homes, then works through prechecks, fixups, and the catalog upgrade itself, with a console you can query for live status. Prerequisites 12c bi...