Importing the replica packet

When you import a replica-creation packet, you import raw data into existing vendor databases. Replica-creation packets do not contain databases; they contain the metadata and record data that form a database.

About this task

These steps take place in San Francisco, which has no replicas in the clan.
  1. If you used store-and-forward, verify the packet’s arrival by entering the lspacket command on the synchronization server.
    multiutil lspacket –short
  2. Create empty vendor databases for the new schema repository and user databases.
  3. Enter the import form of the replica-creation command.

    In the mkreplica –import command, you must specify the path name of the incoming packet as listed by the lspacket command. For example:

    multiutil mkreplica –import –site sanfran_hub –repository ORC1 –vendor
    ORACLE –dbologin orcadmin password –connectopts
    –database ORC1 –vendor ORACLE ORC1 –dbologin orcuser password
    –comments “Importing the initial replicas of the PRODA database and its
    schema repository for the San Francisco site in the telecommunication clan�?
  4. Confirm that import was successful, and then delete the replica-creation packet. (Update packets are deleted automatically.)
  5. Begin development.

    Users in San Francisco can access the new replica in the same way they access an unreplicated database.