Aaron,
Thank you for your suggestion! I had the technical team run RT-Validator with links-only. This fixed the links in the “Refers to” category, but did not fix the tickets in the “Referred to by:” category. We next ran RT Validator with –check—resolve—force and it did not resolve the “Referred to by:” category.
Looking at the output from the RT-Validator run, we received a lot of errors.
23159 reports of “Record #123456 in Transactions. Value of NewValue column most probably is an incorrect link”
176 reports of “Record #1234567 in Transactions. Value of OldValue column most probably is an incorrect link”
20275 reports of “Record #12345 in Links. Value of Target column most probably is an incorrect link”
20323 reports of “Record #12345 in Links. Value of Base column most probably is an incorrect link”
A little bit of this:
Warning: Use of “localtime” without parentheses is ambiguous at /public/server/apps/rt-4.2.11/sbin/…/lib/RT/Interface/Email.pm line 526.
[7344] [Thu Oct 22 21:59:40 2015] [warning]: Nonexistant status refferred in action in default lifecycle at /public/server/apps/rt-4.2.11/sbin/…/lib/RT/Lifecycle.pm line 744. (/public/server/apps/rt-4.2.11/sbin/…/lib/RT/Lifecycle.pm:744)
A little bit of that:
[7344] [Thu Oct 22 22:00:15 2015] [warning]: DBD::Oracle::st execute failed: ORA-00001: unique constraint (RT3EMTS.LINKS1) violated (DBD ERROR: OCIStmtExecute) [for Statement “UPDATE Links SET Base = CONCAT(?, SUBSTR(Base, ?)) WHERE Base LIKE ?” with ParamValues: :p1=‘fsck.com-rt://abc.com’, :p2=26, :p3=“fsck.com-rt://example.com/%”] at ./rt-validator line 1316. (./rt-validator:1316)
[7344] [Thu Oct 22 22:00:15 2015] [critical]: couldn’t execute UPDATE Links SET Base = CONCAT(?, SUBSTR(Base, ?)) WHERE Base LIKE ?
Error: ORA-00001: unique constraint (RT3EMTS.LINKS1) violated (DBD ERROR: OCIStmtExecute) at ./rt-validator line 1316. (/public/server/apps/rt-4.2.11/sbin/…/lib/RT.pm:389)
couldn’t execute UPDATE Links SET Base = CONCAT(?, SUBSTR(Base, ?)) WHERE Base LIKE ?
Error: ORA-00001: unique constraint (RT3EMTS.LINKS1) violated (DBD ERROR: OCIStmtExecute) at ./rt-validator line 1316.
Warning: Use of “localtime” without parentheses is ambiguous at /public/server/apps/rt-4.2.11/sbin/…/lib/RT/Interface/Email.pm line 526.
[15012] [Fri Oct 23 02:23:07 2015] [warning]: Nonexistant status refferred in action in default lifecycle at /public/server/apps/rt-4.2.11/sbin/…/lib/RT/Lifecycle.pm line 744. (/public/server/apps/rt-4.2.11/sbin/…/lib/RT/Lifecycle.pm:744)
Record #3665 in Principals references a nonexistent record in Users
id => ‘3665’ => id
Record #3356 in GroupMembers references a nonexistent record in Principals
MemberId => ‘3665’ => id
Record #1356849 in CachedGroupMembers references a nonexistent record in GroupMembers
GroupId => ‘5’ => GroupId
MemberId => ‘3665’ => MemberId
Record #328577 in Transactions references a nonexistent record in Groups
ObjectId => ‘64505’ => id
Transaction #328577 → object RT::Group #64505
Record #3042 in ObjectCustomFieldValues references a nonexistent record in Articles
ObjectId => ‘8’ => id
The entire output is around 2580 pages.
Prior to the upgrade (with all the links working), I printed off the System Configuration webpage. I just double checked and our Organization was ‘abc.com’ . In our system configuration after the upgrade(with broken links), the organization is ‘abc.com’.
Would having the app down effect the RT-Validator? My technical team did not take Request Tracker down during the process and they were wondering if this could make a difference. Is there anything else we can do or check?
Thank you for your time and support.
Sincerely,
GregFrom: Aaron Guise [mailto:aaron@guise.net.nz]
Sent: Thursday, October 22, 2015 5:43 AM
To: Hummer, Greg
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Ticket Links missing post upgrade/conversion to Oracle 4.2.11.
Hi Greg,
This certainly sounds like a mismatch as Maik suggested. This happens when I refresh my test/dev instance of RT from production also.
I then run the rt-validator over the database and this corrects all the mismatched links. This is needed as I use the server hostname as the Organization and this does differ between environments.
I simply import the database and then execute /opt/rt4/sbin/rt-validator --check --resolve --force
Once that is completed all ticket links are working again.
Regards,
Aaron Guise
[http://www.guise.net.nz/images/signatures/ph.jpg] 07 850 3231
[http://www.guise.net.nz/images/signatures/mob.gif]027 704 5306
[http://www.guise.net.nz/images/signatures/email.gif]aaron@guise.net.nzmailto:aaron@guise.net.nz
[http://www.guise.net.nz/images/signatures/itil_logo.gif] [http://www.guise.net.nz/images/signatures/officiallogo-nd-25.jpg] [http://www.guise.net.nz/images/signatures/ubuntu.png] [http://www.linkedin.com/img/webpromo/btn_profile_greytxt_80x15.png] http://nz.linkedin.com/pub/aaron-guise/35/953/b86