Databases@Powered by Passion
The post details a troubleshooting experience while patching an Oracle Database Appliance from version 19.26 to 19.30. Despite following official procedures, the update failed on the second node due to a mismatch between running instances and registered Oracle Home. It is resolved by manually stopping and starting the instance, then completing the datapatch process.
This article discusses the automation of schema refreshing in Oracle databases using Bash scripts with the Data Pump utility. It outlines how the script accepts a schema name, locates the latest export directory, checks schema existence, terminates sessions, drops the schema if it exists, imports data, and gathers statistics. Additionally, it sends email notifications regarding the operation’s success or failure. The solution is designed to be straightforward and maintainable, primarily for development or test environments.
Oracle Data Pump is utilized for database migrations and backups. To automate daily exports, I have two Bash scripts: one for managing directories and notifications, and another for executing the Data Pump export with custom parameters. Features include automated directory creation, log management, and email alerts for failures.
This article provides a step-by-step guide to changing the DB_UNIQUE_NAME parameter in Oracle Database after cloning, migration, or environment refreshes. It explains how to relocate database files, including datafiles, tempfiles, redo logs, control files, SPFILE, and password files, to a new directory structure in ASM or filesystem storage, while also covering for pdb$seed and Oracle Clusterware configuration.
The RMAN backup error originated after upgrading an Oracle Database from version 19.26 to 19.32 while using Veritas NetBackup. The issue was identified as a version incompatibility between the RMAN recovery catalog (19.6) and the database environment. Testing showed that the backup worked without the recovery catalog, indicating that the catalog was the stumbling block. Upgrading the catalog resolved the issue, allowing successful backup operations to resume.
The post discusses an error encountered during a Data Pump export from an Oracle Database 19c, upgraded from 12c, specifically ORA-31642 and ORA-01031. Initially attributed to insufficient privileges, the problem was traced to lacking necessary rights. After granting required privileges and tablespace quotas, the export completed successfully.
