/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Backup Protect

Oracle Backup Failure - file create error

SUMMARY

Oracle Backup fails with file create error

ISSUE

ORA-19504: failed to create file "/usr/bp/mnt/natest/unitrends-full-NATESTxx-20150609-220-1-881946839"
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 22: Invalid argument

This is caused by the option FILESYSTEMIO_OPTIONS viewable by “show parameter filesystemio_options”
https://docs.oracle.com/cd/B28359_01/server.111/b28320/initparams083.htm#REFRN10061

If this option is set to “directIO” or “setall” configuration, the Oracle system will refuse to write data to the NFS (default protocol) or CIFS share on the Unitrends system, indicating that it is unable to create the file (manual testing of individual script items indicate that the filesystem is read only, when it is tested and confirmed manually not to be).
Due to the way we perform our RMAN backups, these configuration options are invalid for use with the Unitrends system. The valid options are “asynch” and “none”.

Additional Reading:
https://community.oracle.com/thread/2475652
http://oracle-base.com/articles/misc/direct-and-asynchronous-io.php

Tested and confirmed on RHEL Oracle 11.2.02

For more detailed information on backup failures and performance issues see Unitrends KB 5062 - Backup Failures and Performance Issues