Mapped Extent
When you select the Mapped Extent mode, only the persistent system and user schema database files containing classes in the relational mapping are replicated.
When a JADE database file is replicated, the entire file is replicated and not just the objects in the mapped extent.
The Mapped Extent mode does not support takeover from the RPS node.
The benefit of the Mapped Extent mode is that you can perform extract operations without impacting the operation of the production database.
When a mapped extent data store has been created, adding further classes to the RPS mapping that are mapped to database files that were not included in the current mapped extent data store, will invalidate the RPS data store. You must recreate the RPS data store from the primary database. For details, see "Creating the RPS Database" and "RPS Node Creation Example", elsewhere in this chapter.
Column-mapping methods and virtual properties executed in Mapped Extent mode raise an exception if they access any persistent objects that are not in the files included in the mapped extent.
Ad hoc indexes are not available for a mapped extent data store.
