I have not perform an upgrade with these versions but it is not uncommon for arx files to fail because some records already exist and the import mapping is configured to reject duplicate records. This is done so your data is not overwritten. It is hard to tell if this is an issue without knowing what arx files failed.
Regarding def files, that does sound like an issue. I would think they would be set to overwrite any existing objects unlike arx files. Can you provide the sections of the logs that list the failed arx/defs? I have not experienced what Abhinav describes but makes sense that resource exhaustion (disk or memory) would also cause imports to fail. Again the logs should show some indication as to what the problem is. Jason On Tue, Jan 18, 2011 at 7:30 AM, SriSamSri Appecherla < [email protected]> wrote: > Hi, > I performed an upgrade from ITSM 7.5.01 to 7.6.03. The upgrade went > on for a full 43 hours and failed to import def files ans arx files in > change and service desk. > > Has anyone faced such issues with upgrading from 7.5.01 to 7.6.03? > platform: solaris, db: oracle 10g > > -- > Sent from my mobile device > > Regards, > SriSamSri Appecherla > Mobile# +91 991 610 6008 > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
