Hi David,
I don't think the fact that your database creation script probably doesn't match the original layout of the source database is causing this error. You should be able to load any dump into a database that is the same size as the source regardless of layout (assuming same page size, character set, sort order, etc). Matching the layout does make things "prettier" (log fragments end up on devices named "log...", etc, but the load should succeed and the database be functional regardless.
I agree with Jeff that the "with compression" option should be used in preference to the older "compress::" syntax. The "with compression" feature is more flexible as the dump header and trailer can be read, the dump can be made to a remote backupserver, etc.
There is a known bug on 16.0 that results in this 692 error, which is CR 764402. The error is specific to the use the "for load" option. I recommend that you drop the database and create it without using "for load"; the process will take longer as it initializes every page, but it will avoid the bug. A fix for the bug is expected in the 16.0 SP00 PL04 release (I don't have an expected date for it, but should be fairly near future).
Cheers,
-bret