INF0008: A Command Line Job Fails to Load the Library on UNIX Clients
Issue
A backup or restore command line job fails to load the library with the following error.
bash-3.2$ onbar -b -L 0
onbar is starting ..........
Galaxy Instance: Instance003
Loading Library:/opt/Commvault/Base32/libCvIbsad.so from dir /opt/Commvault/Base32
LoadLibrary failed when loading libCvIbsad.so, error = ld.so.1: onbar_d: fatal: /opt/Commvault/Base/libCvLib.so: wrong ELF class: ELFCLASS64onbar is starting ..........
Galaxy Instance: Instance003
Loading Library: /opt/Commvault/Base32/libCvIbsad.so from dir /opt/commvault/Base32
GetProcAddress failed, geterror=ld.so.1: onbar_d: fatal: invalid handle: 0x0onbar is starting ..........
Galaxy Instance: Instance003
Loading Library:/opt/Commvault/Base32/libCvIbsad.so from dir /opt/Commvault/Base32
GetProcAddress failed, geterror=ld.so.1: onbar_d: fatal: invalid handle: 0x0
Resolution
INF0009: A Reinstalled Client Can Cause the Restore to Go to the Pending State
Issue
If you reinstall a client to a different location, or manually install the client to a different location, the restore can go to the pending state. The log displays the following:
UNIX
This is the bar_act.log file.
2015-12-10 11:43:02 15601 15595 onbar_d -r
2015-12-10 11:43:02 15601 15595 (-43231) An unexpected error occurred: /opt/simpana/Base/ibsad001.so: cannot open shared object file: No such file or directory .
2015-12-10 11:43:02 15601 15595 (-43259) Could not open XBSA library /opt/simpana/Base/ibsad001.so, so trying default path.
Windows
This is the Bar_act.log file.
2016-03-07 15:36:13 11040 11040 E:\IFXSER~1\12.10\bin\onbar_d -r
2016-03-07 15:36:16 11040 11040 (-43075) Unable to open file C:\PROGRA~1\COMMVA~1\Simpana\Base\IFXXBSA.dll .
2016-03-07 15:36:16 11040 11040 Windows Error 127: The specified procedure could not be found.
Cause
The software cannot find the Informix library. This is the ibsad001.so library on UNIX and the IFXXBSA.dll library on Windows.
Resolution
UNIX Configuration
-
You must run the ifx_install.sh script to update the symlink path. For more information on this procedure, see Relink the Informix instance.
-
Update the BAR_BSALIB_PATH entry in the onconfig file.
Windows Configuration
-
Update the BAR_BSALIB_PATH entry in the onconfig file.
-
If you run INFORMIX 11.50 or 11.70, restart the Informix server.
INF0010: Restores fail when a salvage log backup is initiated during a restore
Symptom
The following additional setting applies to Informix version 12.10 FC 6 or later.
If you initiate a salvage log backup during a restore, the restore may fail.
Resolution
Set the sSKIPSINGLEJOBID to Y to have the software not merge the multiple Informix streams into a single job.
-
On the client computer, add the sSKIPSINGLEJOBID additional setting and configure the following values:
Property
Value
Name
sSKIPSINGLEJOBID
Category
InformixAgent
Type
String
Value
Y
For instructions on how to add additional settings from the CommCell Console, see Add or Modify an Additional Setting.
INF0011: Restore Failures
Cross machine restore may fail when destination client is installed as a restore only client
Issue
Informix server in a destination client may have full logical logs. As a result, you may need to back up these logical logs prior to a restore job. Since the destination client is a restore only client, it fails to perform this backup job. As a result, the restore job displays the status as pending.
Resolution
Perform a physical restore job first and then the logical restore. This will ensure a successful restore job for a restore only client.
Restore fails if there are multiple server name entries in the ixbar file
Issue
Ixbar file is referred as 'emeregency boot file' and contains the backed up information of dbspaces and logical logs. Each time a database object is backed up, this file will be updated. The information stored in this file is also kept in the sysutils database. The name of the ixbar file is in the format of ixbar.SERVERNUM.
Ixbar contains the following objects:
-
server name
-
object name (The dbspace name or 'L' for logical log),
-
object type (Either 'L' for Logical log, 'ND' for Non Critical Dbspace, 'R' for rootdbs or 'CD' for critical dbspace)
-
Whole System Backup flag,
-
Action id (Informix unique identifier that is associated with the onbar backup command)
-
Backup Level (full or incremental)
-
Copyid_hi and Copyid_lo (unique identifier of object that is stored in the storage manager)
-
TimeStamp of the backup
-
Onbar Version (comes from the sysutils:bar_version table. It is the value in the column bar_version).
During a restore, Onbar scans the ixbar server file and finds the backups it needs to restore from the storage manager. Restore fails if there are multiple server name entries in the ixbar file.
For example:
The ixbar file contains the entries for backups performed with servername = server1.
You then change the servername to server2. You have performed the backups after changing the servername to server2. The ixbar file will now contain server2 entries along with the entries of server1. When you perform a restore operation for server2, the restore may fail. The IFXXBSA.log will display the following error:
7392 1 06/06 15:10:15 48910 IfxBackupRestoreBase::GetBackupInfo() - Job[48910] thread[7392]: getArchFileByName completed, for restore: retCode=[1] appId=[0] afileNumber=[0] agroupNumber=[4286608497] streamNum=[-9223367638816624640] appType=[0].
7392 1 06/06 15:10:15 48910 IfxBackupRestoreBase::OpenArchive() - Job[48910] thread[7392]: GetBackupInfo() failed.
7392 1 06/06 15:10:15 48910 CreateIfxObject: Error, exiting after br->Initialize2
7392 1 06/06 15:10:15 48910 : CreateIfxObject: Job[48910] thread[7392]: GetBackupInfo() failed.
7392 1 06/06 15:10:15 48910 : BSAGetObject: Job[48910] thread[7392]: GetBackupInfo() failed.
This failure occurs because the onbar process tries to find the information about the servername = server1 entry from the storage manager.
Resolution
Perform the following steps:
-
Save a copy of the ixbar file.
-
Edit the original ixbar file and remove all the server1 entries from the ixbar file.
-
Perform restore operations for server2.
Restore fails when you reinstall the Commvault software to a new location on the client
Issue
On a Windows platform, when you reinstall the Commvault package using a different install location, the restores from previous backups may fail with the following error:
bar_act.log
2013-10-04 17:54:04 2784 2784 D:\\IBM\11.50\bin\onbar_d -r
2013-10-04 17:54:04 2784 2784 (-43075) Unable to open file C:\PROGRA~1\COMMVA~1\Commvault\Base\IFXXBSA.dll .
2013-10-04 17:54:04 2784 2784 D:\\IBM\11.50\bin\onbar_d complete, returning 142 (0x8e)
The BAR_BSALIB_PATH to IFXXBSA.dll remains the same in ONCONFIG file even after you reinstall the Commvault package. Hence, the restores may fail.
Resolution
As a workaround, perform the following steps:
-
Edit the BAR_BSALIB_PATH parameter in ONCONFIG file. Update the IFXXBSA.dll path to <new Commvault install location>\Base\IFXXBSA.dll.
-
Restart the Informix services after updating the ONCONFIG file.
INF0012: A Restore Might Fail If the Primary MediaAgent is Offline
Issue
An Informix restore might fail if the primary MediaAgent is offline because the restore initiates a salvage log backup. The backup always uses the primary MediaAgent so the backup fails which causes the restore to fail.
Resolution
Run a partial restore. For more information, see Performing a Partial Restore from Physical and Logical Data.
A cross machine restore fails in allocating shared memory with ENOSPC error
Issue
A cross machine restore fails to allocate the shared memory with ENOSPC error. You will see the below log information in the Informix online.log file:
Shared memory segment will use huge pages.
shmget: [ENOSPC][28]: key 52564803: The server could not allocate shared memory because an operating system limit was reached
Performance Advisory: Unable to allocate memory for bufferpool 2K
Action: Please notify IBM Informix Technical Support.
Resolution
Based on the operating system configuration of the destination client, modify NETTYPE, SHMVIRTSIZE and BUFFERPOOL values in the destination instance onconfig file. Contact the IBM technical support team.
A point-in-time restore performs reserved pages read from the latest backup for Informix 12.10 version
Issue
For Informix version 12.10, a point-in-time restore operation performs reserved pages read from the latest backup, instead of reading from the backup based on the time passed.
The Informix bar_act.log file displays the following information:
2021-10-06 18:00:55 127094 127087 onbar_d -r -p -t 2021-09-29 16:04:08
2021-10-06 18:00:55 127094 127087 Working with cvsm as generic storage manager.
2021-10-06 18:00:55 127094 127087 Successfully connected to Storage Manager.
2021-10-06 18:00:57 127094 127087 Begin reserved pages read (level 0 of rootdbs, Storage Manager copy ID: 124396 1633521206).
2021-10-06 18:00:57 127094 127087 Completed reserved pages read (level 0 of rootdbs).
2021-10-06 18:00:59 127094 127087 bar_build_timeline: target time 1632911648
Cause
This is the expected behavior for Informix version 12.10 only.
Resolution
-
Edit the Ixbar file. Retain the specific backup cycle that you want to restore and remove all the other entries.
-
Run the point-in-time restore operation.
Note
Save a copy of the Ixbar file before editing it. After running the restore operation, copy back the Ixbar file to its original location.
