Rules for Removing Objects

Oracle Life Sciences Data Hub enforces the following rules for object removal.

• You cannot remove an object if other objects are dependent on it. For example, you cannot remove an object definition if there are one or more instances of it. (You can set the object definition's status to Retired, however, and then no additional instances of it can be created.)
• You cannot remove Table instances with a validation status of Production. This is to protect production data.
• In some cases the removed object is still displayed in the user interface. The system then renames the object by prepending a tilde (~) to its name.

  Using a tilde to rename the object signifies that the object has been removed and allows you to create a new object of the same type in the same container with the same name.

  Examples:

  • If an executable object has been executed and then removed, it appears in the Job Details page for the job preceded by a tilde (~).
  • You can remove a component object (such as a Parameter) from the object that contains it (such as a Program) or an executable object (such as a Program) from either a Report Set or a Workflow. In these cases Oracle LSH continues to display the removed object in the Version History screen for its container but renames the removed object by prepending one or more tildes (~) to its name in previous versions of the container object. You can then create a new object of the same type with the same name in the latest version of the same container. The old versions of the container continue to function as before.