PROBKUP on the standby database with -norecover fails 1119 1553

PROBKUP on the standby database with -norecover fails 1119 1553
PROBKUP -norecover sometimes succeeds when the bi file on the hotspare is truncated
After truncating the bi file on the standby database, the -norecover backup succeeds but subsequent roll forwards can fail as outlined in Article 000021068   
Error 1119 appears every time a PROBKUP -norecover is executed after ai's have been roll forwarded.

stack trace from _dbutil
 

User account performing backup has rw on all database files
Hardware and tape device examined for faults
System logs clean

Multiple bi extents
-biblocksize is not the default (8KB) blocksize
-biclustersize is not the default (524KB) clustersize
 

During an offline PROBKUP operation with the -norecover option, bi files are backed up as well as the database files.

It is during the read operation of the bi file that the process goes awry according to the stack trace listed above. The 1119 message indicates the database manager tried to verify the block that was requested was the block that was read and the verification failed.

This could either indicate that there is corruption in the dbkey or block on disk or that the wrong block was read into the buffer. As this message specifically relates to the bi files, if there were indeed bi corruption, then one wouldn't be able to subsequently truncate the bi file without the -F option. In this case however, it is possible so we can safely assume that there is no bi corruption.

When the bi blocksize is changed, a misconfiguration of the bi blocks results which the backup utility is (erroneously) detecting as corruption. For further detail, refer to Article, 000020102   

This behavior has been Enhanced in the following OpenEdge versions:

• OpenEdge 10.1B or later where by default, only the active bi clusters (aka initialized bi blocks) are backed up with the offline probkup -norecover option
• Upgrade to OpenEdge 11.3.0 or later where by default, only the active bi clusters (aka initialized bi blocks) are backed up during online backups. OpenEdge 11.5 or later is recommended when active bi clusters exceed 2GB. Refer to Article:
   What happens during an online backup of the database?     

a. End AI on production DB

b. Re-structure the BI files:

Remove the current bi files from the database structure
Configure the BI block size and cluster size as required:
c. Re-enable AI on production and re-create the hotspare standby database

• Probkup production DB
• Start AI on production DB
• Prorest to standby DB 
• Roll-forward AI files

d. Test probkup -norecover

Progress Articles:

 Explaining why 1119 error during ONLINE PROBKUP or PROBKUP -norecover   
 Why you should NOT truncate the bi of the target database when using an ai disaster recovery plan ?