Erasing a Work Repository

Erasing a work repository is a permanent and irreversible operation. When you erase a work repository from the database, all information related to that repository—including models, projects, and run-time data (such as scenarios, schedules, and logs)—will be permanently deleted.

Steps to Erase a Work Repository:

  1. Access the Topology Navigator:
    • Open the Topology Navigator tool, which is typically part of a system for managing repositories.
  2. Expand the Repositories Panel:
    • In the Topology Navigator, locate the Repositories panel on the side.
    • Expand the Repositories section to see a list of repositories.
  3. Expand the Work Repositories Node:
    • Within the Repositories panel, you’ll find the Work Repositories node.
    • Expand this node to reveal all the work repositories in the system.
  4. Right-click the Work Repository:
    • Find the work repository you wish to erase.
    • Right-click on the repository name to bring up a context menu.
  5. Select "Erase from Database":
    • In the context menu, select the option Erase from Database. This will initiate the process of deleting the repository from the system.
  6. Confirm the Erasure:
    • A Confirmation dialog will appear asking you to confirm that you want to erase the work repository.
    • Click Yes to proceed. This action will permanently delete the work repository.
  7. Completion:
    • After confirmation, the work repository will be deleted from the database and will no longer appear in the Repositories panel of the Topology Navigator.

Important Notes:

  • Irreversibility: Once the work repository is erased, the action cannot be undone. All data within the repository will be permanently deleted.
  • Data Loss: This includes the deletion of all associated metadata, models, projects, logs, scenarios, and schedules tied to the work repository.

Warning:

Make sure that you no longer need the repository or any of its data before proceeding with the erasure, as this process cannot be reversed.

 

 

No comments:

Post a Comment