[rt-users] Dealing with old CustomFields after upgrade from 3.6.10 to 4.2.4

[LABANJ2]

I am a newbie (but not an alcoholic... {:-)}):
I just installed a new 4.2.4 and even the update to the Oracle Schema went 
fine (I looked at the schema in the ../etc and looked at the schema in the 
Toad and they were fine.). However, I have a lot of custom stuff in the 
old installation and several Custom Fields and Custom Templates, and the 
ClearTrust on top of it, and so on... When I use the menu the PullDown 
Menu (that  is between [New Ticket In] [ThePullDownMenu] [Search Field] I 
will be fine on some items and on the Custom Ones I will get

: An internal RT error has occurred. Your administrator can find more 
details in RT's log files. 
When I go to logs, I will see lots of stack traces, like
[5416] [Tue May 27 19:52:36 2014] [error]: could not find component for 
path 'EditCustomFieldNWIE_UID_Callup_Lookup'

Stack:
  [/u01/app/RT-4.2.4-443/share/html/Elements/EditCustomField:111]
  [/u01/app/RT-4.2.4-443/share/html/Elements/EditCustomFields:65]
 
[/u01/app/RT-4.2.4-443/share/html/Elements/EditCustomFieldCustomGroupings:56]
  [/u01/app/RT-4.2.4-443/share/html/Widgets/TitleBox:56]
 
[/u01/app/RT-4.2.4-443/share/html/Elements/EditCustomFieldCustomGroupings:57]
  [/u01/app/RT-4.2.4-443/share/html/Ticket/Create.html:119]
  [/u01/app/RT-4.2.4-443/share/html/Ticket/autohandler:66]
  [/u01/app/RT-4.2.4-443/sbin/../lib/RT/Interface/Web.pm:682]
  [/u01/app/RT-4.2.4-443/sbin/../lib/RT/Interface/Web.pm:370]
  [/u01/app/RT-4.2.4-443/share/html/autohandler:53] 
(/u01/app/RT-4.2.4-443/sbin/../lib/RT/Interface/Web/Handler.pm:210)
How should I approach the problem? Just brutal copy of old stuff from  
RT-3.6.19.../local/ did not work and asked me to download mod_perl and the 
likes (I work under FCGI under IHS 8.0).

Any good write-ups on the approach of upgrading the custom fields, custom 
templates, ClearTrust (I know perl well, but I do not know RT...)?

Jan Labanowski
laba...@nationwide.com
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

[rt-users] Column order in tables after upgrade from 3.6.10 to 4.2.4

[LABANJ2]

Distinguished RT-Users,

After running upgrade_database (I am upgrading from 3.6.10 to 4.2.4) I 
have some problems (e.g., [Search Tickets] times out in the browser, but I 
admit that I did not do a whole lot of testing yet). What I found is that 
some columns in the schema.Oracle script in the 4.2.4 distribution, and 
the columns in the tables in the database after conversion from 3.6.10 to 
4.2.4, are in a different order.
For example, in the schema.Oracle for 4.2.4:
CREATE TABLE Queues (
id  NUMBER(11,0)
CONSTRAINT Queues_Key PRIMARY KEY,
NameVARCHAR2(200) CONSTRAINT 
Queues_Name_Unique UNIQUE NOT NULL,
Description VARCHAR2(255),
CorrespondAddress   VARCHAR2(120),
CommentAddress  VARCHAR2(120),
Lifecycle   VARCHAR2(32),
SubjectTag  VARCHAR2(120),
InitialPriority NUMBER(11,0) DEFAULT 0 NOT NULL,
FinalPriority   NUMBER(11,0) DEFAULT 0 NOT NULL,
DefaultDueInNUMBER(11,0) DEFAULT 0 NOT NULL,
Creator NUMBER(11,0) DEFAULT 0 NOT NULL,
Created DATE,
LastUpdatedBy   NUMBER(11,0) DEFAULT 0 NOT NULL,
LastUpdated DATE,
DisabledNUMBER(11,0) DEFAULT 0 NOT NULL
);

In the actual table after conversion to 4.2.4:
Column Name:
ID
NAME
DESCRIPTION
CORRESPONDADDRESS
COMMENTADDRESS
INITIALPRIORITY
FINALPRIORITY
DEFAULTDUEIN
CREATOR
CREATED
LASTUPDATEDBY
LASTUPDATED
DISABLED
SUBJECTTAG
LIFECYCLE
Of course, if data are always retrieved as hashrefs for rows it should 
have no impact, but if they are retrieved occasionally as arrays, it may 
be a problem ...

Should I worry or look elsewhere?
Jan Labanowski
laba...@nationwide.com-- 
RT Training - Dallas May 20-21
http://bestpractical.com/training