Backup jobs fail with error: Failed to get status code information (2505)

Problem

All the backup jobs fail with error 2505

Failed to get status code information (2505)

Error Message

Job details in Activity Monitor:

Error bpbrm (pid=1480) db_FLISTsend failed: Unable to connect to the database (2505)
12/05/2013 15:39:45 - job 63389 was restarted as job 63390
Failed to get status code information (2505)

bpdbm log:

15:31:14.460 [1480] <16> DbmOdbcConnect::initialize_odbc: Odbc connection failed ErrMsg [Sybase][ODBC Driver][SQL Anywhere]Connection error: An error occurred during the SharedMemory connection attempt, ErrCode -1, Sqlstate 08001, ConnStr PROWS=1000;PBUF=8m;CS=utf8;UID=DBM_MAIN;PWD=******;LINKS=shmem,tcpip{PORT=13785};ENG=NB_server;DBN=NBDB;CON=DBM_1480_1
15:31:14.461 [1480] <16> DbmOdbcConnect::spawnOdbcView: (-1) Not connected
15:31:14.461 [1480] <16> getMasterServerKey: Cannot create database connection
15:31:14.461 [1480] <16> DbmSLP::get_Master_Server_Key: could not get master server key: retial (2505)
15:31:14.461 [1480] <16> DbmSLP::get_DBM_SLP_ALL_WITH_ALL_VERSIONS: could not get master server key: Success (0)

Cause

This error can be caused by a lack of semaphore tuning within the kernel. This error cannot be resolved by NetBackup.

The following command will show your current semaphore values. This example shows the value at 128:

# sysctl -a | grep kernel.sem
kernel.sem = 250 32000 32 128

Solution

The semaphores can be adjusted using the following command:

# sysctl -w kernel.sem="300 32000 32 1024"

The following command will show your updated semaphore values. This example shows the value at 1024

# sysctl -a | grep kernel.sem
kernel.sem = 300 32000 32 1024

The Related Article (100023842) below discusses the minimum recommended kernel tuning requirements for NetBackup on a Linux or Unix platform.