Cloned or restored metastore will not open and Data Object Broker (DOB) fails to start.
Article ID: KB0084607
Updated On:
| Products | Versions |
|---|---|
| TIBCO Object Service Broker for z/OS | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
Attempting to clone an Object Service Broker (OSB) Table Data Store (TDS) system or database segment using DF/DSS or equivalent causes data integrity issues.
Environment:
============
* z/OS Based OSB systems.
Symptoms:
=========
After restoring a segment with DF/DSS or equivalent then when the DOB attempts to open the segment only the first dataset is opened and then immediately closed.
If the segment is a system segment, 0 or 99, then the the DOB does not start.
If the segment is a user segment then the segment does not open.
Cause:
======
The cause of this problem is the use of logical restore. If a logical restore of a VSAM ESDS is performed then all the data is pushed to the start of the datasets and empty space is left at the end. TDS segments are supposed to have gaps in the data and there are pointers in the data pages to the pages containing related data. Not restoring datasets such that each record is at EXACTLY the same position as in the original data structure will result in unusable corrupted data TDS segments.
Resolution:
===========
The real solution to this problem is to use OSB supplied backup and restore utilities, such as S6BTLBPS and S6BTLRPS, which will maintain database integrity.
Alternatively it is possible to use other backup products provided these products copy the whole tracks as a single image/entity.
Note:
1) due to the way the DOB performs checkpointing, the segment should be closed or frozen when a backup is taken, since an open database is seldom logically consistent. (In the event of a DOB failure, the DOB recovery process corrects any inconsistencies.)
2) after restoring a database, especially when using non-OSB tools, you should always run a backup and then pointer checker S6BBRPTR against the backup to ensure its integrity.
References:
===========
TIBCO® Object Service Broker for z/OS Managing Backup and Recovery
TIBCO® Object Service Broker for z/OS Utilities
IBM DFSMSdss Storage Administration
Description:
============
Attempting to clone an Object Service Broker (OSB) Table Data Store (TDS) system or database segment using DF/DSS or equivalent causes data integrity issues.
Environment:
============
* z/OS Based OSB systems.
Symptoms:
=========
After restoring a segment with DF/DSS or equivalent then when the DOB attempts to open the segment only the first dataset is opened and then immediately closed.
If the segment is a system segment, 0 or 99, then the the DOB does not start.
If the segment is a user segment then the segment does not open.
Cause:
======
The cause of this problem is the use of logical restore. If a logical restore of a VSAM ESDS is performed then all the data is pushed to the start of the datasets and empty space is left at the end. TDS segments are supposed to have gaps in the data and there are pointers in the data pages to the pages containing related data. Not restoring datasets such that each record is at EXACTLY the same position as in the original data structure will result in unusable corrupted data TDS segments.
Resolution:
===========
The real solution to this problem is to use OSB supplied backup and restore utilities, such as S6BTLBPS and S6BTLRPS, which will maintain database integrity.
Alternatively it is possible to use other backup products provided these products copy the whole tracks as a single image/entity.
Note:
1) due to the way the DOB performs checkpointing, the segment should be closed or frozen when a backup is taken, since an open database is seldom logically consistent. (In the event of a DOB failure, the DOB recovery process corrects any inconsistencies.)
2) after restoring a database, especially when using non-OSB tools, you should always run a backup and then pointer checker S6BBRPTR against the backup to ensure its integrity.
References:
===========
TIBCO® Object Service Broker for z/OS Managing Backup and Recovery
TIBCO® Object Service Broker for z/OS Utilities
IBM DFSMSdss Storage Administration
Issue/Introduction
Cloned or restored metastore will not open and Data Object Broker (DOB) fails to start.
Feedback
Yes
No
Powered by
