#1 Global Leader in Data Protection & Ransomware Recovery

ORA-27515 Error During Managed Application Backup Policy Run

KB ID: 4518
Product: Veeam Backup & Replication | 12 | 12.1
Published: 2023-11-27
Last Modified: 2023-11-27
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

Running a managed backup policy with Veeam Plugin for Oracle RMAN results in job failure:

Failed to execute plug-in manager command: RMAN-03002: failure of backup command at 07/13/2023

 

Plugin logs (/tmp/veeam_plugin_logs) and database trace files reference ORA-27515 error:

$ grep ORA-27515 *.log
RMANPluginManager.log:[13.07.2023 20:01:32.234] <139829803869952> plugin_co|   ORA-27515: inadequate memlock limit or driver settings
$ oerr ora 27515
27515, 00000, "inadequate memlock limit or driver settings"
// *Cause: Inter Process Communication(IPC) queue creation failed due to
//         inadequate memlock limit or driver settings.
// *Action: Set a higher memlock limit and review the network driver
//          settings to ensure that this limit is accepted.

 

Note: Manual backup through the RMAN shell completes successfully.

Cause

In Oracle Database environments, custom maximum locked memory (memlock) values may be required for proper database and utilities operations, such as RMAN. Usually, these are configured in user limit settings (ulimit or /etc/security/limits.conf). For more information, refer to Oracle Database Administrator's Reference.

However, in the case of a managed plug-in policy, the RMAN process is spawned by the veeamtransport service. Systemd services do not follow limits configured in limits.conf, and default to 64k memlock limit. For more details, refer to the Root Cause section of https://access.redhat.com/solutions/1257953.

Thus, all processes started in the managed plug-in policy (including RMAN) inherit a default memlock value of 64k, which may not be enough and may result in ORA-27515. Meanwhile, the RMAN process started manually will be spawned by the user shell, which inherits the limits configured in limits.conf, and thus do not face this issue.

According to ORA-27515: inadequate memlock limit or driver settings in EXADATA

  • 3rd party softwares connect to database with a hard code memlock setting should have the sufficient value.

Solution

Manually adjust memlock value for veeamtransport service in systemd configuration files.

  1. Calculate the required memlock value in bytes. According to Oracle Database Administrator's Reference:
    • If HugePages are enabled, the memlock value must be at least 90% of the total RAM.
      For example, if there is 64GB of RAM, 90% will be 61847529062 bytes.
    • If HugePages are not enabled, the memlock value must be at least 3GB or 3221225472 bytes.
  2. Create a directory for veeamtransport service drop-in files, create memlock.conf file in that folder, and then populate the conf file with a new memlock limit value.

    Below is an example of these steps for the 64GB RAM example from step 1.
    Remember to modify the LimitMEMLOCK value for the environment.
mkdir /etc/systemd/system/veeamtransport.service.d
cat > /etc/systemd/system/veeamtransport.service.d/memlock.conf <<EOF
[Service]
LimitMEMLOCK=61847529062
EOF
  1. Make sure that no backups or restores are running on the Oracle server, then reload the systemd daemon configuration and restart veeamtransport service:
systemctl daemon-reload
systemctl restart veeamtransport.service
  1. Verify that the drop-in file memlock.conf is recognized:
systemctl status veeamtransport.service
# systemctl status veeamtransport.service
● veeamtransport.service - VeeamTransport
   Loaded: loaded (/etc/systemd/system/veeamtransport.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/veeamtransport.service.d
           └─memlock.conf
<...>

 

  1. Start the managed RMAN backup policy and check if the issue persists.

 

If the issue persists, contact Veeam Technical Support.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.