Collection copy-on-write functionality is disabled for the Oplog collection because LocalOplogInfo holds onto a oplog collection pointer that would become unsafe. However, if such copy-on-write operations are not allowed against the oplog collection, then we wouldn't need to keep logic around to modify the existing Collection instances, in addition to the new Collection copy-on-write logic.