Oninit
Talk to an expert →

Informix Error -16339: Break or trace name name is not unique.

Cause and resolution

Break or trace name name is not unique.

A name that you assign to a breakpoint or tracepoint in a BREAK or TRACE command cannot duplicate the name of any existing reference point (including disabled breakpoints or tracepoints). This message will also appear after a READ command that sets a named breakpoint or tracepoint if you read the same input file twice.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-16339 fires when a BREAK/TRACE command assigns a name that duplicates an existing reference point — per the official guidance, including disabled breakpoints/tracepoints.

  1. A breakpoint/tracepoint name duplicating an existing one, per the official guidance — the direct, only cause.
  2. A READ command reading the same input file twice, per the official guidance, when that file sets a named breakpoint/tracepoint.
Solutions / Resolution
  1. Choose a name that doesn't duplicate any existing reference point, per the official guidance.
  2. Avoid reading the same .4db file twice in the same session, per the official guidance, if that's the cause.
Examples
A duplicate breakpoint name
> BREAK mybrk AT mymodule.10
> BREAK mybrk AT mymodule.20
Corrected
> BREAK mybrk2 AT mymodule.20
Diagnostic Checks
  1. Check existing breakpoint/tracepoint names (including disabled ones) for a match, and check whether a .4db file was read more than once.
Related Errors / Related Topics

No closely related error codes are cross-referenced for -16339 in this set yet.

A breakpoint/tracepoint name duplicates an existing reference point — choose a unique name, or avoid re-reading the same .4db file.