OraEasy

Introduction Oracle APEX is a low-code development platform that helps you build scalable, secure enterprise apps. Accessing the APEX administration interface requires the ADMIN account, and losing or forgetting that password locks you out of workspace management, user provisioning, and instance-level settings. This guide walks through changing the APEX Admin password using the built-in apxchpwd.sql script. Prerequisites Oracle APEX should already be installed. Environment Used in This Guide Hostname: apex IP: 192.168.101.10 ORACLE_SID : APEXDB PDB: APEXPDB APEX: 24.1 ORDS: 24.2 Step 1: Recognize an Incorrect ADMIN Password If you're here because login is failing, this is the error you'll typically see when the ADMIN password is wrong: Step 2: Stop the Running ORDS Service Before changing the password, stop ORDS by killing its process. This isn't strictly required for the password change itself to work, but it avoids any confusion from cached sessio...

Introduction In Oracle, the timezone file is the data file the database uses to store and manage time zone information, including the rules for daylight saving time and standard time across different regions. Governments periodically change daylight saving rules for various countries, so Oracle periodically releases updated timezone file versions to keep up. Running on an outdated version can cause incorrect time calculations for regions whose DST rules changed after your current file was released. This guide walks through upgrading the timezone file, step by step. Time Zone File Locations Oracle stores time zone files in the $ORACLE_HOME/oracore/zoneinfo/ directory. Files are named timezlrg_XX.dat (the large time zone file) and timezone_XX.dat (the small time zone file), where XX is the version number. Prerequisites Plan for roughly 45 minutes of database downtime, since the upgrade process restarts the database multiple times. Environment Used in This Guide Hostn...

Introduction DBNEWID ( nid ) is an Oracle utility that changes the internal database identifier (DBID) and the database name (DBNAME) of an operational database. This is useful when cloning or duplicating a database that needs to coexist with the original, since two databases with the same DBID and name can cause conflicts in areas like RMAN cataloging and Data Guard. This guide walks through using DBNEWID to change a database name, step by step. Ramifications of Changing the DBID and DBNAME Before changing the DBID and DBNAME of a database with DBNEWID, review Oracle's official guidelines . Once you change the DBID or DBNAME, existing backups and archived logs taken before the change can no longer be used to recover the database, since they were created under the old identity. Plan for a fresh backup immediately afterward. Syntax To change both DBID and DBNAME: nid TARGET=sys/password@orcl DBNAME=orcl2 To change only the DBNAME: nid TARGET=sys/password@orcl DBNAME=orcl2...

Introduction A switchover is a planned role transition between the primary and standby databases in a Data Guard environment, done for maintenance, testing, or periodic load balancing, without any data loss. We covered performing a switchover manually with SQL*Plus in an earlier post. This guide covers the same operation done through Data Guard Broker instead, using a single DGMGRL command rather than a sequence of manual SQL statements on each side. Broker handles most of the coordination automatically, though there's one connectivity quirk worth knowing about in advance, covered in Step 3. Prerequisites Plan for roughly 30 minutes of database downtime during the switchover window. Confirm application and database connectivity are ready at the standby site. Primary and standby databases must be fully in sync before starting. Data Guard Broker must already be configured between the primary and standby. See our Data Guard Broker configuration guide if you haven't set t...

Introduction Data Guard Broker is a management tool for Oracle Data Guard that simplifies the configuration, monitoring, and administration of Data Guard environments. Instead of manually tracking parameters and switchover steps across each database individually, Broker gives you a centralized, automated interface, and it can also monitor apply lag and health status continuously rather than requiring manual checks. It can be managed using DGMGRL (the Data Guard Broker command-line interface) or Oracle Enterprise Manager Cloud Control. This guide walks through setting up Data Guard Broker on an existing primary and standby pair, step by step. Prerequisites Oracle Database Enterprise Edition. Standard Edition does not support Data Guard. The same database version and patch level on both primary and standby. A working Data Guard configuration already in place on both systems, with the primary and standby in sync. Environment Used in This Guide This continues from our earlier ...