Category: Backup

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.

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.

The RMAN database registration process encountered an error, specifically ORA-01403 (no data found), during its initial synchronization due to an existing restore point. Despite entering commands correctly, the registration failed because RMAN could not process the restore point metadata across the CDB. Upon identifying this issue through trace analysis, the restore point was deleted, allowing successful completion of the database registration process, highlighting the importance of internal procedures in troubleshooting.

This post explains how a Data Pump export in an Oracle RAC environment failed with misleading errors, including ORA-48128, related to symbolic links and file access. The actual cause was an NFS-mounted Data Pump directory that was accessible from only one RAC node. Adding CLUSTER=N resolved the issue by keeping all Data Pump workers on the local instance. Alternatively, mounting the NFS filesystem on all RAC nodes also resolves the problem.