Hi,
I’m using rt2-to-rt3-1.23 to upgrade from RT-2.0.13 to RT-3.0.11, using
Perl 5.8.4 on Debian. I’ve had a look back in the list archives, but I
can’t see any other reports of the problem I’m having.
I’m seeing tens of thousands of extra rows in the Groups and
GroupMembers tables, and the same in the new Principals table; I’m
wondering if this is normal.
Here’s the database info for RT2 (via PHPMyAdmin):
Table Records Size Overhead
ACL 261 62.5 KB 11,112 Bytes
Attachments 14,320 46.2 MB -
GroupMembers 25 3.3 KB 26 Bytes
Groups 12 3.6 KB -
KeywordSelects 3 5.1 KB -
Keywords 188 17.8 KB -
Links 178 70.3 KB -
ObjectKeywords 180 20.9 KB -
Queues 8 5.7 KB -
ScripActions 10 3.1 KB -
ScripConditions 7 2.7 KB -
Scrips 16 3.7 KB -
Templates 10 5.8 KB -
Tickets 5,269 1.0 MB -
Transactions 20,052 1.6 MB -
Users 800 254.4 KB -
Watchers 5,390 569.9 KB -
17 table(s) Sum 46,729 49.8 MB 10.9 KB
And here’s the same thing for RT3 after dumping and importing:
Table Records Size Overhead
ACL 256 29.6 KB -
Attachments 14,318 46.7 MB -
CachedGroupMembers 47,296 4.2 MB -
CustomFieldValues 9 3.4 KB -
CustomFields 3 3.2 KB -
GroupMembers 13,087 436.1 KB -
Groups 21,933 3.1 MB -
Links 54 24.0 KB -
Principals 22,744 837.2 KB -
Queues 9 4.8 KB -
ScripActions 15 3.7 KB -
ScripConditions 9 2.9 KB -
Scrips 27 8.6 KB -
Templates 12 5.8 KB -
TicketCustomFieldValues 178 22.7 KB -
Tickets 5,267 1.2 MB -
Transactions 20,048 1.6 MB -
Users 810 310.4 KB -
sessions 0 1.0 KB -
19 table(s) Sum 146,075 58.4 MB 0 Bytes
Is this expected behaviour, or is something going wrong during export or
import? Should I try importing into RT3.2 instead? Is there some step
I’ve forgotten, or a configuration option to tweak?
Any advice gratefully received.
Tim.
Tim Bell – bhat@trinity.unimelb.edu.au – System Administrator
Trinity College, Royal Parade, Parkville, Victoria, 3052, Australia