Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
markparsons Frequent Contributor.
Frequent Contributor.
961 views

Data Protector Release 9 - Bad catalog access

Hi,

I am getting the following errors when running an Internal Database backup:

[Major] From: BSM@uklodrupdpbap01.ey.net "DP_Internal_DB_Consistency_Check_7yrs" Time: 2/1/2018 4:46:53 PM

Bad catalog access for message #20016 in set 61

 

[Major] From: OB2BAR_POSTGRES_BAR@uklodrupdpbap01.ey.net "DPIDB" Time: 2/1/2018 4:46:53 PM

      Received ABORT request from BSM (ERR: Error starting backup/restore (BMA cannot be started or similar).)

The last successful backup was 9th December 2017. Could this be because its now 2018?

Here are the details of the release of data protector we are running and patches (the hpux release is B.11.31 U ia64 4251680688):

HP Data Protector A.09.00: OMNIB, internal build 88, built on Tue May 12 06:31:1

1 2015

 

# omnicheck -patches

Patch level         Patch description

===========================================

DPUX_20000/DPLNX_20000 (A.09.08) Core Component

DPUX_20000/DPLNX_20000 (A.09.08) Core of Integrations component

DPUX_20001/DPLNX_20001 (A.09.08) Cell Manager Component

DPUX_20002/DPLNX_20002 (A.09.08) Disk Agent

DPUX_20003/DPLNX_20003 (A.09.08) General Media Agent

DPUX_20003/DPLNX_20003 (A.09.08) NDMP Media Agent

DPUX_20004/DPLNX_20004 (A.09.08) User Interface

DPUX_20010/DPLNX_20010 (A.09.08) HPE P6000 / HPE 3PAR SMI-S Agent

DPUX_20016/DPLNX_20016 (A.09.08) HPE StorageWorks disk array XP Agent

DPUX_20011/DPLNX_20011 (A.09.08) DB2 Integration

DPUX_20023/DPLNX_20023 (A.09.08) Oracle Integration

DPUX_20022/DPLNX_20022 (A.09.08) SAP MaxDB Integration

DPUX_20021/DPLNX_20021 (A.09.08) Sybase Integration

DPUX_20005/DPLNX_20005 (A.09.08) English Documentation (Guides, Help)

DPUX_20000/DPLNX_20000 (A.09.08) Pegasus Libraries

DPUX_20000/DPLNX_20000 (A.09.08) Core Technology Stack

DPUX_20001/DPLNX_20001 (A.09.08) Cell Server Technology Stack

DPUX_20001/DPLNX_20001 (A.09.08) Application Server Technology Stack

DPUX_20001/DPLNX_20001 (A.09.08) Web Services

DPUX_20001/DPLNX_20001 (A.09.08) Java Runtime Environment Technology Stack

DPUX_20001/DPLNX_20001 (A.09.08) Job Control Engine Service Dispatcher

DPUX_20001/DPLNX_20001 (A.09.08) Job Control Engine Service Registry

Number of patches found: 22.

Generated at: 2018-02-02 13:04:50

Any assistance gratefully received.

Kind Regards - Mark Parsons

 

 

 

 

0 Likes
12 Replies
Highlighted
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Data Protector Release 9 - Bad catalog access

Hi Mark,

I'm wondering why omnib reports build 88 instead of the proper one for A.09.08 which should be 112. So please make sure to run "Update client" on the Cell Manager since inconsistencies in the packages can cause "Bad catalog access for message #N in set M" errors..

If the consistency check fails I would recommend running omnidbcheck -extended for possible obvious errors. Please also check if you see errors in the current log file in /var/opt/omni/server/db80/pg/pg_log and the check_*.log files created in /var/opt/omni/server/log.

Please share the full session report with us so we can have a look.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
markparsons Frequent Contributor.
Frequent Contributor.

Re: Data Protector Release 9 - Bad catalog access

Hi,

This is the output from omnidbcheck -extended;

# omnidbcheck -extended

Check Level             Mode                   Status

===========================================================

Database connection     -connection             OK

Schema consistency     -schema_consistency     OK

Datafiles consistency   -verify_db_files       OK

Database consistency   -database_consistency   OK

Media consistency       -media_consistency     OK

SIBF(readability)       -sibf                   OK

DCBF(presence and size) -bf                     OK

OMNIDC(consistency)     -dc                     Failed: 37 minor errors detected

DONE!

There is nothing relevant in the logs.

However I am wondering if anything to do with the tape drive / library might also cause the bad catalog access.

This happens whilst the backup is running:

 

[Critical] From: UMA@uklonrmpmedal2.uk.eurw.ey.net "MSL6060" Time: 3/26/2018 4:54:17 PM

[90:59]    uklonrmpmedal2.uk.eurw.ey.net : scsi8:0:0:0

      Cannot open exchanger control device ([1117] The request could not be performed because of an I/O device error. )

 

And the backup we are doing is a DP Internal DB Consistency Check.

 

 

 

0 Likes
markparsons Frequent Contributor.
Frequent Contributor.

Re: Data Protector Release 9 - Bad catalog access

Forgot to say that I have also "updated client".

Here is the full session report:

[Normal] From: BSM@uklodrupdpbap01.ey.net "DP_Internal_DB_Consistency_Check_7yrs" Time: 3/26/2018 4:49:21 PM

      Backup session 2018/03/26-2 started.

 

[Normal] From: BSM@uklodrupdpbap01.ey.net "DP_Internal_DB_Consistency_Check_7yrs" Time: 3/26/2018 4:49:21 PM

      OB2BAR application on "uklodrupdpbap01.ey.net" successfully started.

 

[Normal] From: OB2BAR_POSTGRES_BAR@uklodrupdpbap01.ey.net "DPIDB" Time: 3/26/2018 4:49:22 PM

      Checking the Internal Database consistency

 

[Normal] From: OB2BAR_POSTGRES_BAR@uklodrupdpbap01.ey.net "DPIDB" Time: 3/26/2018 4:49:42 PM

      Check of the Internal Database consistency succeeded

 

[Normal] From: OB2BAR_POSTGRES_BAR@uklodrupdpbap01.ey.net "DPIDB" Time: 3/26/2018 4:49:42 PM

      Putting the Internal database into the backup mode finished

 

[Normal] From: BMA@uklonrmpmedal2.uk.eurw.ey.net "MEDAL2_Drive2" Time: 3/26/2018 4:49:48 PM

      STARTING Media Agent "MEDAL2_Drive2"

 

[Critical] From: UMA@uklonrmpmedal2.uk.eurw.ey.net "MSL6060" Time: 3/26/2018 4:54:17 PM

[90:59]    uklonrmpmedal2.uk.eurw.ey.net : scsi8:0:0:0

      Cannot open exchanger control device ([1117] The request could not be performed because of an I/O device error. )

 

[Normal] From: BMA@uklonrmpmedal2.uk.eurw.ey.net "MEDAL2_Drive2" Time: 3/26/2018 4:54:17 PM

      ABORTED Media Agent "MEDAL2_Drive2"

 

[Major] From: BSM@uklodrupdpbap01.ey.net "DP_Internal_DB_Consistency_Check_7yrs" Time: 3/26/2018 4:54:21 PM

Bad catalog access for message #20016 in set 61

[Major] From: BSM@uklodrupdpbap01.ey.net "DP_Internal_DB_Consistency_Check_7yrs" Time: 3/26/2018 4:54:21 PM

Bad catalog access for message #20016 in set 61

[Major] From: BSM@uklodrupdpbap01.ey.net "DP_Internal_DB_Consistency_Check_7yrs" Time: 3/26/2018 4:54:21 PM

Bad catalog access for message #20016 in set 61

[Major] From: BSM@uklodrupdpbap01.ey.net "DP_Internal_DB_Consistency_Check_7yrs" Time: 3/26/2018 4:54:21 PM

Bad catalog access for message #20016 in set 61

[Major] From: OB2BAR_POSTGRES_BAR@uklodrupdpbap01.ey.net "DPIDB" Time: 3/26/2018 4:54:21 PM

      Received ABORT request from BSM (ERR: Error starting backup/restore (BMA cannot be started or similar).)

 

[Major] From: OB2BAR_POSTGRES_BAR@uklodrupdpbap01.ey.net "DPIDB" Time: 3/26/2018 4:54:21 PM

      Received ABORT request from BSM (ERR: Error starting backup/restore (BMA cannot be started or similar).)

 

[Major] From: OB2BAR_POSTGRES_BAR@uklodrupdpbap01.ey.net "DPIDB" Time: 3/26/2018 4:54:21 PM

      Received ABORT request from BSM (ERR: Error starting backup/restore (BMA cannot be started or similar).)

 

[Major] From: OB2BAR_POSTGRES_BAR@uklodrupdpbap01.ey.net "DPIDB" Time: 3/26/2018 4:54:21 PM

      Received ABORT request from BSM (ERR: Error starting backup/restore (BMA cannot be started or similar).)

 

[Normal] From: OB2BAR_POSTGRES_BAR@uklodrupdpbap01.ey.net "DPIDB" Time: 3/26/2018 4:54:22 PM

      Putting the Internal database out of the backup mode finished

 

[Critical] From: OB2BAR_POSTGRES_BAR@uklodrupdpbap01.ey.net "DPIDB" Time: 03/26/18 16:54:22

      Received ABORT request. Terminating agent.

 

[Normal] From: BSM@uklodrupdpbap01.ey.net "DP_Internal_DB_Consistency_Check_7yrs" Time: 3/26/2018 4:54:23 PM

      OB2BAR application on "uklodrupdpbap01.ey.net" disconnected.

 

[Critical] From: BSM@uklodrupdpbap01.ey.net "DP_Internal_DB_Consistency_Check_7yrs" Time: 3/26/2018 4:54:23 PM

      None of the Disk Agents completed successfully.

      Session has failed.

 

[Normal] From: BSM@uklodrupdpbap01.ey.net "DP_Internal_DB_Consistency_Check_7yrs" Time: 3/26/2018 4:54:23 PM

 

      Backup Statistics:

        

            Session Queuing Time (hours)         0.00      

            -------------------------------------------    

            Completed Disk Agents ........         0        

            Failed Disk Agents ...........         4        

            Aborted Disk Agents ..........         0        

            -------------------------------------------    

            Disk Agents Total ...........         4        

            ===========================================    

            Completed Media Agents .......         0        

            Failed Media Agents ..........         1        

            Aborted Media Agents .........         0        

            -------------------------------------------    

            Media Agents Total ..........         1        

            ===========================================    

            Mbytes Total .................       0 MB      

            Used Media Total .............         0        

            Disk Agent Errors Total ......         0  

 

 

============================================================================

                     Session failed!

============================================================================

 

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Data Protector Release 9 - Bad catalog access

Hi Mark,

to fix the backup you need to check why the device path to MEDAL2_Drive2 on uklonrmpmedal2.uk.eurw.ey.net is no longer valid. Update the path in Devices & Media context of the Data Protector GUI or use a different device for this backup.

I'm still not sure about the "Bad catalog access for message #20016 in set 61" warnings. They are coming from BSM on uklodrupdpbap01.ey.net. What does /opt/omni/lbin/bsm -version report? Has the output of omnicheck -patches changed on the Cell Manager after the "Client upgrade"?

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Data Protector Release 9 - Bad catalog access

Hello,

The error "Bad catalog access for message #20016 in set 61" could be due to a lot of things.

First recommended fix - update to the latest DP patches.

And then fix any IDB error (check omnidbcheck -extended").

If same problem still exists after the above, you may want to log a SUPPORT case so that the next available DP support can investigate this one further.

Hope this helps

Rgds,

Sherman

DP Support

0 Likes
markparsons Frequent Contributor.
Frequent Contributor.

Re: Data Protector Release 9 - Bad catalog access

Here are the results:

# /opt/omni/lbin/bsm -version

HPE Data Protector A.09.08: BSM, internal build 112, built on Tue Oct 11 23:01:4

8 2016

# omnicheck -patches

Patch level         Patch description

===========================================

DPUX_20000/DPLNX_20000 (A.09.08) Core Component

DPUX_20000/DPLNX_20000 (A.09.08) Core of Integrations component

DPUX_20001/DPLNX_20001 (A.09.08) Cell Manager Component

DPUX_20002/DPLNX_20002 (A.09.08) Disk Agent

DPUX_20003/DPLNX_20003 (A.09.08) General Media Agent

DPUX_20003/DPLNX_20003 (A.09.08) NDMP Media Agent

DPUX_20004/DPLNX_20004 (A.09.08) User Interface

DPUX_20010/DPLNX_20010 (A.09.08) HPE P6000 / HPE 3PAR SMI-S Agent

DPUX_20016/DPLNX_20016 (A.09.08) HPE StorageWorks disk array XP Agent

DPUX_20011/DPLNX_20011 (A.09.08) DB2 Integration

DPUX_20023/DPLNX_20023 (A.09.08) Oracle Integration

DPUX_20022/DPLNX_20022 (A.09.08) SAP MaxDB Integration

DPUX_20021/DPLNX_20021 (A.09.08) Sybase Integration

DPUX_20005/DPLNX_20005 (A.09.08) English Documentation (Guides, Help)

DPUX_20000/DPLNX_20000 (A.09.08) Pegasus Libraries

DPUX_20000/DPLNX_20000 (A.09.08) Core Technology Stack

DPUX_20001/DPLNX_20001 (A.09.08) Cell Server Technology Stack

DPUX_20001/DPLNX_20001 (A.09.08) Application Server Technology Stack

DPUX_20001/DPLNX_20001 (A.09.08) Web Services

DPUX_20001/DPLNX_20001 (A.09.08) Java Runtime Environment Technology Stack

DPUX_20001/DPLNX_20001 (A.09.08) Job Control Engine Service Dispatcher

DPUX_20001/DPLNX_20001 (A.09.08) Job Control Engine Service Registry

Number of patches found: 22.

Generated at: 2018-03-27 16:55:24

 

Where do I find DP patches these days - they are not on the HP Patch Management site.

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Data Protector Release 9 - Bad catalog access

Hi Mark,

Messages are loaded from omni.cat for Unix and omnienu.dll for Windows and it's updated through the Core Patch.

The message that you are getting is not related to an IDB issue, it's a cosmetic message:

./omnigetmsg 61 20016
Backup device unavailable. Trying to promote any pending mirror to original.

 

- We have to check first the Catalog, can you run /opt/omni/lbin/omnigetmsg 61 20016, did you get the message above?

- If yes then it means bsm is loading the wrong catalog so we have to check debugs.

- If you don't get any message from omnigetmsg 61 20016 then you can check on the omni.cat files located in:

/opt/omni/lib/nls/C/omni.cat
/var/opt/omni/repackage/CORE_Patch/opt/omni/lib/nls/C/omni.cat

I would recommend to install the latest Core patch, all the patches can be found here:

https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result?doctype=patches?keyword=

Best Regards

0 Likes
markparsons Frequent Contributor.
Frequent Contributor.

Re: Data Protector Release 9 - Bad catalog access

Message is indeed:


# /opt/omni/lbin/omnigetmsg 61 20016
        Backup device unavailable. Trying to promote any pending mirror to origi
nal.
#

0 Likes
markparsons Frequent Contributor.
Frequent Contributor.

Re: Data Protector Release 9 - Bad catalog access

Should I be using the following patch bundle:

Data Protector 9 – GR Patches 9.08 (Build 113)    

 

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Data Protector Release 9 - Bad catalog access

Hi Mark,

You should go for A.09.09 patch bundle + 115 GR patches + 116 GR patches. Please refer to https://www.data-protector.org/wordpress/category/patches/dp-a-09-00/ for details.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
markparsons Frequent Contributor.
Frequent Contributor.

Re: Data Protector Release 9 - Bad catalog access

If it is Build 113 then the links either dont work or they send me to a webpage that doesnt even mention Data Protector:

We found 6 results
this document provides an overview of all project and portfolio management 9.3x patches. click the patch version (the release column) for the release notes, and click the patch bundle name for the patch details and download link.
project and portfolio management 9.30 9.31 ;
patches
customer
published
Created: 2015-01-22
Modified: 2017-12-18
servicecenter 6.2.4 installation cd contains a flawed km_file_handling.unl unload file and should not be loaded into the newly upgraded servicecenter system.
servicecenter ;
patches
customer
published
Created: 2008-02-04
Modified: 2015-05-13
product alert for comtrade spi for siebel
smart plug-in for siebel ;
patches
public
published
Created: 2008-01-08
Modified: 2011-03-30
product alert for comtrade smart plug-in for documentum
smart plug-in for documentum ;
patches
public
published
Created: 2008-01-08
Modified: 2011-03-30
product alert for comtrade smart plug-in for citrix
smart plug-in for citrix ;
patches
public
published
Created: 2008-01-08
Modified: 2011-03-30
product: performance insight (pi)..version: 5.31
performance insight 5.31;
patches
public
published
Created: 2008-03-28
Modified: 2008-03-28
FirstPrev1NextLast

 

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Data Protector Release 9 - Bad catalog access

Hi Mark,

You can go to the main page https://softwaresupport.softwaregrp.com/ and from Dashboards find the patches.

After installing the patches and update the Cell Manager from the Client context, let us know if you still get the Bad Catalog. If so, then I would suggest to open a support case to determine why BSM is not loading the catalog.

If omnigetmsg loads the catalog but BSM not then debugs are needed to be analyzed.

Regards

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.