Which was our next guess. I did a count on user_cache to check for NULL entryIDs and NULL usernames and returned zero results in either case. I'd really like for this export and import to work so we're not down for somewhere in the neighborhood of two days but I can't figure out why those records won't import.
Do I maybe fail at exporting records? I simply ran some chunked queries (it doesn't appear to like unqualified searches on a half million records) and then exported them to .arx files via the User tool. As noted earlier, I also tried the straight transfer via a SQL Server DTS package. I hope I'm doing something wrong, but if I am, I can't figure out what it is. Thanks, Michael A. McManus, SSgt, USAF Remedy Developer HQ 754 ELSG/DOMH -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Tuesday, August 26, 2008 5:47 PM To: [email protected] Subject: Re: Problem importing records ** I'll give you a hint: Multiple NULL values will trigger the duplicate key errors as well. Rick On Tue, Aug 26, 2008 at 3:37 PM, McManus Michael A SSgt HQ 754 ELSG/DOMH <[EMAIL PROTECTED]> wrote: ** Listers, So it appears the problem with our upgrade and it's ridiculous length was the user form (and the user_cache). When the system was conceived, the original developer used the User form as a User form and a Customer form so we're looking at 555000+ records in the User form as of now. The arsql.log file shows the installer walking each individual record in the user_cache for license information. This appears to take a fairly significant amount of time (and a lot of space). Per a discussion with BMC today, it was suggested that I export all the user records to a .arx file and then delete all but one administrator account so that the installer can run. I exported all the user records, deleted all but one admin account and upgraded in about 20 minutes from 5.1.2 to 7.0.01 (a far cry from 36 hours). After the server was upgraded, I attempted to re-import all those records and I'm getting all sorts of errors. Thousands and thousands of records will not import due to a "unique index being violated on this form". It's my understanding that Request ID and username are the only unique indexes on the user form (and for posterity's sake, I verified in both the admin tool, and enterprise manager) and I ran queries to validate that there were no duplicate usernames or request ids on the user_cache table or in the user_x view. I attempted to import using the AR Import tool and it failed miserably. I also attempted via a DTS package to copy the data from a test 5.1.2 database to our freshly upgraded 7.0 test database and that also failed miserably. I've worked myself ragged on this upgrade and made absolutely no progress. Does anyone have any idea why these records won't import? Environment is Windows Server 2003, AR Server 5.1.2 (which we upgraded to 7.0 patch 8 after exporting and deleting all those records) and database is SQL Server 2003 Thanks a bunch, Michael A. McManus, SSgt, USAF Remedy Developer HQ 754 ELSG/DOMH __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
