Let us let you in on one of the open secrets of calendar migration: It's not a wise investment to put a lot of code into pulling data OUT of a legacy system. Better to use one of the utilities the legacy system uses for purposes of upgrading servers or moving users between servers. Less prone to error, it uses the legacy's capability against itself, and it allows a migrator to put their effort into getting the data INTO the target system.
Sometimes though this gets more difficult when there's bugs in the legacy system.
One of our clients (shout out to Matt in North Carolina!), discovered some data missing from the UNICPOUTU export in their Solaris environment.
Quel horreur!
It's been mentioned a little on the OCS boards, but nobody is making a big deal about it and it is unlikely Oracle is going to fix it to make breaking your OCS habit any easier.
Thus far we've seen this ONLY with OCS 10.x on Solaris (all the 9.0.4 migration systems look absolutely peachy and we've been doing 10.x for years with no issues). We suspect it's with the very latest and is more prone to happen when the export is constrained by date (so export everything and let us segment it in our tools).
So as always, keep an eye out.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment