Reference Guide

7. Once the Start date has changed, re-launch DRM to make any changes to Automatic Search.

If I export a bundle using Export to light weight

deployment scripts, am I going to re-download the DUPs

which are already in my system?

Whenever a DUP is downloaded, it is stored locally in a file system [%localappdata%\RepositoryManager

\FileStore] location. It is not stored using the DUP file name in that location, hence it is not traceable with

the exact DUP names. For further use of the DUPs, DRM fetches them from this location and will NOT re-

download.

How to edit the ‘.sh’ file in Linux deployment script

bundle? Is there any recommended tool to edit this file?

Notepad++ is the best editor for editing files especially which are Linux based ones on a Windows OS. If it

is on a Linux OS, vi editor is recommended.

Why am I seeing Error parsing inventory data from file

error message while creating the new repository for CMC

Inventory?

There can be three different scenarios, where user encounters with this error message:

1. If the user does not have the proper administrative rights, DRM does not fetches the files from the

CMC folder. The error message is displayed. This error blocks the new repository creation process.

2. If the inventory file is stored in any of the network share, and if DRM is not able to connect to that

particular network share this error is displayed.

3. If the inventory file is in read-only format, DRM fails to fetch those files and the error message is

displayed, the repository creation process fails.

While using OME, why is the component getting updated

when it is removed from a particular bundle?

OME uses all the components that are within a Repository, it does not organize the updates by

Bundles. To insure that the Repository used by OME does not contain the update be sure to select the

Remove from Repository option when deleting an update. In case, if you are using the catalog created

by DRM with OME, OME does not recognize the bundles separately, it just recognizes the entire catalog

as one single file. This is how OME works. At any time, if you remove a component from the OME bundle

but not from the Repository then OME contemplates that the components is still there and compares it

against the available updates.

The database is corrupted or invalid. How do I fix this?

To fix the database:

1. Remove the corrupted database before you recreate a new database. Navigate to %localappdata%

\RepositoryManager\Database\RepositoryManager.sdf to delete the database.