Troubleshooting issues related to Oracle Copilot with universal shares — NetBackup 10.3 | Cohesity Documentation

Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist

Troubleshooting issues related to Oracle Copilot with universal shares — NetBackup 10.3 | Cohesity Documentation

NetBackup™ for Oracle Administrator's Guide

Troubleshooting issues related to Oracle Copilot with universal shares

The following table describes the issues that are related to Oracle Copilot with universal shares:

Table: Troubleshoot issues

Job state	Error message	Issue	Action
Partial success	ORA-19504: failed to create file "XXXXXXXXXXXX" ORA-27040: file create error, unable to create file	Shares that failed from nodes.	Verify that the shares on all nodes have correct permissions associated. Remount the share, run crosscheck manually, and then run the job again.
Partial success	ORA-19625: error identifying file"XXXXXXXXXXXX" ORA-27037: unable to obtain file status	Datafile on the share may be corrupted or missing	If the file is missing, verify that the shares are mounted on all nodes. Try to remount the share, run crosscheck manually, and then run the job again. If the file exists, use Oracle tools to verify the file and ensure that the file is not corrupted. If the file is corrupted, keep all the logs and call technical support. Move the corrupted file from a shared drive to a local drive, run crosscheck, and then run the job again.
Partial success	Snapshot failed	Snapshot rotation limitation exceeded.	Check if a previous backup from snapshot job failed. Increase the maximum snapshot number and run crosscheck manually. Modify datafile copy tag in the Oracle tab of policy, and run a new full backup. If the error persists, call technical support.
Partial success	RMAN Catalog failed	Shares that failed from nodes.	Verify that the shares on all nodes have correct permissions associated. Remount the failed share, find the backup set on share, and try to manually catalog it.
Success	Backup job takes more time than expected.	Performance issue	Verify the operating system resource and ensure that there is no performance issue from Oracle. Run the job again with the force rescan option.
Fail	SLP job keeps failing.	The ushare is created on a different backup target storage.	Verify and change the SLP backup snapshot storage target. Run the job again.

Feedback

Was this page helpful?

Feedback

Was this page helpful?