roll forward fails with error 8019 883 11014 on first aiarchived backup sequence number

RFUTIL roll forward fails with error 8019 883 11014 on first aiarchived backup sequence number.
The first aiarchived extent with the new backup sequence number change fails to roll forward.
Restoring all ai extents with the same database backup sequence number.

ai files are named by the ai archiver daemon process
ai files are referenced in the dbname.archival.log

The switch to the new extent happens after the master block in the database has been updated with the new database backup sequence number. The first extent with the new backup sequence number is actually the last ai extent for the previous backup sequence number. This issue affects both online and offline PROBKUP.

This enhancement has not been implemented in the product.  As an alternative use the workaround below.

Roll forward the next named ai extent with the new backup sequence number.

For example:

The aiarchiver log file extract below, shows:
-> an aiarchiver daemon switch pre backup
-> an aiarchiver daemon switch resulting from a full online probkup
-> an aiarchiver daemon switch (post full online probkup)

[dbname.archival.log]
0001,\aiarc\dbname,20080728,102808,20080728,101732,4,6,\aiarc\dbname.a1,\aiarc\ais1,\aiarc\ais1\aiarc~dbname.20080728.101732.00004.00000006.dbname.a1
0032,\aiarc\dbname,20080728,102940,1,5,20080728,102939,8,1,dbnamel2.bak,BACKUP_SET_20080728_102939
0001,\aiarc\dbname,20080728,102943,20080728,101732,5,7,\aiarc\dbname.a2,\aiarc\ais1,\aiarc\ais1\aiarc~dbname.20080728.101732.00005.00000007.dbname.a2

The resulting named ai files in the ai archiver directory at the time (-aiarcdir) are:

directory~database.dateAIFMstarted.timeAIFMstarted.backup-sequence.ai-sequence.extent-name
aiarc~dbname.20080728.101732.00004.00000006.dbname.a1
aiarc~dbname.20080728.101732.00005.00000007.dbname.a2 << should be named (...)00004.00000007.dbname.a2
aiarc~dbname.20080728.101732.00005.00000008.dbname.a3

If we were to roll foward (..)00005.00000007.dbname.a2 against the online probkup restored (dbnamel2.bak), it would fail.
This ai file 'belongs' as the last ai file to the previous backup sequence '00004'.

Instead, rollfoward the aifile named with the new backup sequence +1. In the above example - this would be (...).00005.00000008.dbname.a3

As a consequence, the backup sequence number of the backup (buseq) has been removed from Archive Record in AI archive log file since OpenEdge 10.1C02.

References to Other Documentation: 

For further information on the AI Archiver utility and naming conventions please refer to:
OpenEdge Data Management: Database Administration, Chapter "After-imaging", Section: AI File Management utility.