|
> > > > Yep, after you do the install, do something to touch all of > the files on the > > system - a RCLSTG, a DSPOBJD *ALL/*ALL, anything really > just touch every > > file on the system - we found heaps of unconverted files on > our production > > system - it's a known problem where the files don't get > converted during the > > upgrade but nobody knows why. > > "Converted"? From what to what? I'm not aware of any specific > V5R1 conversion for database objects except for the system > cross-reference info. > All IBM told me at the time was the new V5R1 database format. Conversion is supposed to take place during the upgrade. Ours didn't (on two out of two upgrades that we've done so far) and when access attempts were attempted on production files, things went belly up. I can't remember the full details, it was a while ago, but a targetted "touching" of the files fixed the problems. Regards, Dwayne Lindner Team Leader - Data Centre Wesfarmers Rural Information Technology 184 Railway Parade, Bassendean WA 6054 Ph: (08) 9273 5365 Mob: 0407 386 693 Email: dwayne.lindner@writ.wesfarmers.com.au
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.