Cobra Help

Fixing Duplicate Records

When Cobra detects duplicate records during login, it displays a dialog box that lists the affected file types and asks whether you want Cobra to fix the duplicates automatically.

Duplicate Record

This topic explains what happens when you select Yes or No.

Note: This topic applies only to Oracle databases. Duplicate records can occur when record names differ only by trailing spaces. For example, Oracle may store both “Project” and “Project “ (with a trailing space), but Cobra treats these values as the same name when reading the data. As a result, Cobra detects the records as duplicates and cannot continue processing until the issue is resolved.

When You Click Yes

When you click Yes, Cobra identifies and renames duplicate records in the affected file types. Cobra displays its progress for each affected record type. After correcting all records, Cobra displays the Summary dialog box. The summary lists the changes made and can be copied to the clipboard.

Summary

When you click OK, Cobra loads and displays the Cobra Explorer.

Note: Information about the affected records is written to the ClientDebugLog.xml file.

When Cobra encounters an error while renaming duplicate project records, it displays a message indicating that the error occurred and no changes were saved. Click OK to close the dialog box and exit Cobra.

How Cobra Renames Duplicate Records

When Cobra detects duplicate records, it retains one record with the original name and renames the remaining duplicates by appending a -DUP suffix and sequential number.

The affected file types can include:

  • Projects
  • Calendars
  • Codes
  • Rates
  • Resources

For example:

Original Records Corrected Records
"Shuttle Work " "Shuttle Work"
"Shuttle Work " "Shuttle Work-DUP1"
"Shuttle Work " "Shuttle Work-DUP2"

If a record name is close to Cobra's default maximum length of 22 characters, Cobra truncates the name as needed to accommodate the -DUP suffix.

When You Click No

When you click No, Cobra displays a message that it cannot run while duplicate records exist, then exits.

Note: Although no changes are made, the ClientDebugLog.xml file still records details about the affected records, which you or a Deltek Support Services analyst can use to review the issue before running Cobra again.

How to...

Log into Cobra


Learn more about...

Cobra Login Dialog Box


Parent Topic:

Advanced Topics