- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for Oracle RMAN Agent Overview
- Enabling the Oracle RMAN Agent
- Review Oracle data protection and replication requirements
- Protecting a stand-alone Oracle server
- Protecting Oracle RAC environments
- Install and configure the Oracle RMAN agent
- Install the Oracle RMAN agent
- Integration with PowerProtect Data Manager software
- Install the PowerProtect Data Manager agent
- Uninstall the Oracle RMAN agent
- Uninstall the PowerProtect agent service
- Update the Oracle RMAN agent
- Update the PowerProtect agent
- Recommission the Oracle RMAN agent
- How the Oracle RMAN agent communicates with PowerProtect Data Manager
- Verify the connectivity from ddbmcon
- Discover the storage units
- Manage the Oracle application agent
- Supporting existing Oracle RMAN agent backups with PowerProtect Data Manager
- Enable multi-stream backups for Oracle protection policy
- Enabling app-optimization for storage unit created by Oracle protection policy
- Managing Storage, Assets, and Protection
- Add protection storage
- Storage unit considerations
- Enable an asset source
- Delete an asset source
- Discover an Oracle application host
- Add and remove the credentials for Oracle assets
- Add a protection policy for Oracle database protection
- Cancel an application agent protection job
- Add a service-level agreement
- Extended retention
- Edit the retention period for backup copies
- Delete backup copies
- Enable the Oracle RMAN agent after hostname change
- Manage the PowerProtect agent service
- Manage the cloud tier operations with PowerProtect Data Manager
- Performing Self-Service Backups and Restores of Oracle Databases
- Oracle RMAN Best Practices and Troubleshooting
- Troubleshooting storage units
- Troubleshooting backup failures when credentials include a backslash character (\)
- Troubleshooting PowerProtect Data Manager UI display of localhost.localdomain hostname
- Troubleshooting agent registration
- Troubleshooting PowerProtect agent service operations
- Troubleshooting self-service backup error related to top-level pathname
- Troubleshooting self-service operations with data-in-flight encryption
- Troubleshooting Oracle self-service jobs that run indefinitely
- Troubleshooting an incorrect self-service backup report for different backup types in same session
- Troubleshooting an incorrect asset display after asset source deletion
- Troubleshooting an issue with AIX RAC cluster failover
- Troubleshooting RAC cluster failure due to active node issue
- Troubleshooting a missing duration value for centralized backup
- Troubleshooting an issue with onboarded backup copies
- Troubleshooting missing Oracle version with added protection rules
- Troubleshooting restore failure due to FORMAT specification
PowerProtect Data Manager 19.10 Oracle RMAN User Guide
Troubleshooting self-service backup error related to top-level pathname
If a self-service backup fails with the following type of error, you must complete the required top-level directory changes:
Reason for failure: orcl failed due to error message: The backup operation failed for the instance 'orcl' with dbid '1585115093' due to the following error: RMAN-03009: failure of Control File and SPFILE Autobackup command on CH0 channel at 12/09/2020 13:16:52 ORA-19502: write error on file "c-1585115093-20201209-06", block number 1 (block size=16384) ORA-27030: skgfwrt: sbtwrite2 returned error ORA-19511: non RMAN, but media manager or vendor specific failure, error text: sbtwrite2:The top-level pathname must be specified in backup piece format for assets configured with PowerProtect Data Manager. Recovery Manager complete.
To resolve this type of error for a self-service backup, complete the procedure in Performing self-service backups of Oracle databases.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\