FAQs
This article provides answers to frequently asked questions regarding Migration Vault. If you don’t find the answer to your question here, contact Veeva Product Support.
What is the Repair process?
The Repair process occurs during the Validate and Stage phase and creates objects that are required, but not found in the source data. The Repair process also ensures that the data sent to CDMS is complete.
The system repairs the following objects:
- Events
- Forms
- Items
- Item Groups
Why is the object record in CDMS not what I expected?
There are several reasons why the object record in CDMS may not appear as expected:
- The record was not properly registered by mapping
- The record was orphaned, skipped, or manually deleted
- An error occurred during a Run or Post-Run operation
Learn more about troubleshooting Object Records.
Why is there a DNO (Did Not Occur) event where my non-DNO event should be?
If you have a non-DNO event where your DNO event should be, this could be because the event was created by Repair and not registered by mapping, or it was registered by mapping but missing a visit date.
DNO and non-DNO events are often found in the same CSV file. Typically, the CSV file is targeted by two YAML files: one that creates DNO events and one that creates non-DNO events. Events registered without a visit date are considered to be DNO events.
Why might a Validate & Stage operation appear stalled?
Validate & Stage operations have a finite number of Workers. If you start a Validate, Stage, or Validate & Stage operation and it appears stalled, the Workers may be busy processing other loads.
The following Worker pools are used to process loads:
- Message Processors: This pool is used to identify clinical Load status.
- Jobs: This pool is used to identify Attribute Status and Query Status.
Message Processors
To check the Message Processors queue, navigate to Business Admin > Connections > Spark Queues > validator_inbound_queue__v.
The Messages in Queue field tells you the size of the queue. Each message contains a work request for processing one YAML file. If the queue size is larger than the number of YAML files in your Load, it is likely that the queue is behind another Validate & Stage in progress.
The Workers that process the messages also process messages in other queues. Vault Management Console (VMC) access is required to obtain more insight into the details associated with this process.
If your Load is stalled and the_ Messages in Queue number is equal to the number of YAML files in your _Load, it’s likely that other types of messages are occupying the Workers.
Understanding Queues: In the case of two Studies, if the first Study consists of 150+ YAML files, the second Study is queued while the first one is being processed. This is true even though the status of the second one reads as In Progress. Queues are less common for Studies with fewer YAML files.
Jobs
To check the status of the Jobs Worker pool, navigate to Business Admin > Operations > Job Status.
On the Job Status page, if the Attribute processing job or Query processing job has a status of Scheduled, then operations may be delayed, but will start soon. If they have a status of Running, this indicates that the Attribute Status records or Query Status records are being created and the processing associated with each record has been queued.
If you clicked Validate & Stage or Validate, your jobs should, at minimum, have a status of Scheduled.
A Job Status of Success indicates that the Attribute Status records or Query Status records were created, the work has been queued, and processing will begin within a few minutes.