USEHDROBIDS

Use the USEHDROBIDS option to indicate if the OBIDs in the header is valid or not.

When you specify OBIDXLAT (OBIDXLAT-specification) with INCOPY FULL SNAPSHOT TOCOPY syntax and do not specify OBIDs, BMC AMI Recover looks at the OBIDs in the header page to determine if the OBIDs for the source and target are the same. If the OBIDs are the same, BMC AMI Recover does not use a MERGE phase to update the OBIDs. Skipping the MERGE phase makes migration faster because it eliminates a read and write of every page of the space. (BMC AMI Recover might still do an 'optimized merge' phase to just update the header page.)

Related topic

OPTIONS-option-descriptions

Sometimes the OBIDs in the header page are not correct. An example of when this situation might occur is when the space is copied from another object and the OBIDs in the header page are not translated correctly. If the OBIDs in the header page are not correct, BMC AMI Recover might skip the MERGE phase when they should not, or the MERGE phase might fail because BMC AMI Recover detects that the OBIDs in the header page do not match the OBIDs in the rest of the data. Under circumstances like these, you can use USEHDROBIDS to tell BMC AMI Recover if the OBIDs in the header are valid or not.

If you do not code USEHDROBIDS on the OPTION command statement, the default is the value of the USEHDROBIDS installation option (USEHDROBIDS-YES), which defaults to YES.

Value

Description

USEHDROBIDS YES

When you specify USEHDROBIDS YES, BMC AMI Recover uses the OBIDs in the header page and skips the MERGE phase if possible. If BMC AMI Recover does perform the MERGE phase and detects that the OBIDs are not correct, BMC AMI Recover ends with an error message.

USEHDROBIDS NO

When you specify USEHDROBIDS NO, BMC AMI Recover always does a MERGE phase and ignores the OBIDs in the header page.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*