<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 17-11-2015 20:04, Hummer, Greg
wrote:<br>
</div>
<blockquote
cite="mid:CB66DFBFF9CAE1488E6F41C5592EDA5B255333F5@SRAexMBX03.sra.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<style id="owaParaStyle" type="text/css">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
P {margin-top:0;margin-bottom:0;}</style>
<div style="direction: ltr;font-family: Tahoma;color:
#000000;font-size: 10pt;"><br>
<div style="font-family: Times New Roman; color: #000000;
font-size: 16px">
<div style="direction: ltr;" id="divRpF626018"><br>
</div>
<div>Good afternoon,<br>
<br>
I can confirm it is most likely due to an organization. The
organization in our System Configuration prior to the
Conversion/Upgrade matches the setting after. This was
confirmed though googles “Inspect Element” feature.
<br>
<br>
<b>On the bad links I get the following:</b><br>
<i><input type=“checkbox” class=“checkbox”
id=“DeleteLink-fsck.com-rt://<b>example.com</b>/ticket/101611-RefersTo”
name = “DeleteLink-fsck.com-rt://<b>example.com</b>/ticket/101611-RefersTo-:
value=”1”></i><br>
<br>
<b>On recently created- good links, I get this:</b><br>
<i><input type=“checkbox” class=“checkbox”
id=“DeleteLink-fsck.com-rt://<b>abc.com</b>/ticket/101611-RefersTo”
name = “DeleteLink-fsck.com-rt://<b>abc.com/</b>ticket/101611-RefersTo-:
value=”1”></i><br>
<br>
<br>
When we pulled two lines out of the Link table, we get the
following:<br>
<i>15367 fsck.com-rt://<b>example.com</b>/ticket/100005
fsck.com-rt://abc.com/ticket/99902 MergedInto 99902 99902
184988 4/29/2014 4:10:48 PM 184988 4/29/2014 4:10:48 PM
</i><br>
<br>
In the sage account (which has all good links) this same ID
shows up like this:<br>
<i>15367 fsck.com-rt://<b>abc.com</b>/ticket/100005
fsck.com-rt://abc.com/ticket/99902 MergedInto 99902 99902
184988 4/29/2014 4:10:48 PM 184988 4/29/2014 4:10:48 PM</i><br>
<br>
So then we went about trying to fix it. We used RT-Validator
with force, RT-Validator with links, and finally the MySQL
below. Each time, with each of the previous three items, we
got the following error:<br>
<i><br>
ORA-00001: unique constraint (RT3EMTS.LINKS1) violated</i><br>
<br>
Here is the MySQL we tried to use:<br>
UPDATE links SET BASE =
REPLACE(BASE,'example.com','abc.com') WHERE BASE LIKE
'%example.com%';<br>
<br>
Does anyone have any suggestions how to get around this
Oracle error when trying to adjust the domain in the links?<br>
<br>
</div>
</div>
</div>
</blockquote>
Your update (replacing example.com with abc.com) creates a row in
the LINKS table which violates the LINKS1 constraint. Look at the
definition of the LINKS to to find what is being violated. This
means that you already have a row with abc.com and trying to create
a second one from an old example.com.<br>
Questions is which one to keep, or where/why is there already a
abc.com row.<br>
<br>
I have done I think exactly the same update and didn't have any
problems BUT I didn't move from MySQL to Oracle. I'm going to have
a wild guess: did you check the Oracle sequences after rt-importer?
They should all be @max(id)+1 before inserting new tickets/links
etc.<br>
<br>
Joop<br>
<br>
</body>
</html>