Troubleshooting guide

Chapter 4, Status Codes and Messages 83
Status Codes
System requirements vary; thus, no absolute recommendations can be made. One
customer running both NetBackup and ORACLE on their Solaris server made the
following changes to their /etc/system file and then rebooted the system (boot
-r); the changes were found to be adequate:
set semsys:seminfo_semmni=300
set semsys:seminfo_semmns=300
set semsys:seminfo_semmsl=300
set semsys:seminfo_semmnu=600
Set these attributes to a value great enough to provide resources to all applications on
your system.
5. Check for a shared memory problem. This error can occur if the system cannot
allocate enough shared memory. This usually occurs when you use multiplexing,
which increases the shared memory requirements. A symptom is an entry similar to
the following in a NetBackup log (or report).
could not allocate enough shared memory
If you see this type of message, refer to the vendor documentation for your platform
for instructions on increasing the amount of shared memory on your system.
Because system requirements vary, no absolute recommendations can be made, other
than to use values great enough to provide resources to all applications. In at least one
instance, however, the following was found to be adequate on a Sun platform:
set shmsys:shminfo_shmmax=8388608
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmnu=600
set semsys:seminfo_semmns=300
After making the changes to the /etc/system file on the Sun platform and
rebooting with boot -r, the problem was resolved. Note that in the above,
shminfo_shmmin must be less than or equal to 100 for NetBackup processes to run.
6. Examine other activity logs or the progress log on the client.
7. If a backup on a Windows NT/2000 NetBackup client fails with status code 11 and the
client is using Open Transaction Manager (OTM) for open file management, it is
possible that the error was caused by the OTM cache file being full. If this is the case
and bpbkar activity logs are turned on, a message similar to the following should
appear at the end of the backup:
04/28/99 11:27:56 AM: [216]: ERR - OTM Error:0xe0001005
04/28/99 11:27:59 AM: [216]: INF - OTM Terminate - disabled for all
processes