Don't worry. It's just me.

Andy's Blog

Problem with Compact -C in 8.0.2 sure puts crimp in moving to ODS 48

Andrew M Pedisich  December 3 2008 12:54:51 PM

Looks like IBM Technote 1329103 (http://www-01.ibm.com/support/docview.wss?uid=swg21329103) makes it pretty problematic to move to the ODS 48.  Compact with the -C option is broken, and that's exactly the option you need to move your databases to the new ODS.

Normally, I don't use the -C option for anything but an extreme measure to try and repair a database, so the fact that it is broken is bad, but not a show stopper.

However, if you've placed the CREATE_R8_DATABASES=1 paramter in you 8.0.2 server's NOTES.INI with the expectation of actually going to the new ODS, I'd remove the parameter and back off.  Keep your -B and leave it all on the old ODS for now.

You don't need grief like that when upgrading.  And since the parameter is required, you can definitely separate the ODS change from the upgrade.

- Andy


Comments

1Jon Champlin  12/3/2008 1:07:46 PM  Problem with Compact -C in 8.0.2 sure puts crimp in moving to ODS 48

Its not the -C option that is broken, but when using -i the database can get into an unreliable state. There shouldn't be a reason to use -i, just run fixup on the database before compacting if you think it has a problem.

2Andy Pedisich  12/3/2008 1:11:27 PM  Problem with Compact -C in 8.0.2 sure puts crimp in moving to ODS 48

Actually, the technote says that -C...

"Stops with error 02:0A and does not commence compacting until a certain size of the TMP file is reached."

That's not the sort of thing to use in production.

- Andy

3Andy Pedisich  12/3/2008 1:21:04 PM  Problem with Compact -C in 8.0.2 sure puts crimp in moving to ODS 48

Plus, that part about "until a certain size of the TMP file is reached" is way too ambiguous.

If there's ANY kind of an issue I sure as heck don't want to be the one that proves it with a favorite client. That's just plain risky, and I don't do risk.

- Andy

4Chad Scott  12/3/2008 2:02:12 PM  Problem with Compact -C in 8.0.2 sure puts crimp in moving to ODS 48

You should not get the errors if you uncheck the "Optimize document table map" option in database properties.

5andy pedisich  12/3/2008 4:28:52 PM  Problem with Compact -C in 8.0.2 sure puts crimp in moving to ODS 48

6andy pedisich  12/3/2008 4:30:43 PM  Problem with Compact -C in 8.0.2 sure puts crimp in moving to ODS 48

Is there another technote that indicates why unchecking that is necessary?

- Andy

7Chad Scott  12/3/2008 4:39:18 PM  Problem with Compact -C in 8.0.2 sure puts crimp in moving to ODS 48

I have updated the TN with that information. Here's some more info:

{ http://bleedyellow.com/blogs/chadscott/entry/another_problem_with_the_document_table_map_property9 }

8Andy Pedisich  12/3/2008 9:16:27 PM  Problem with Compact -C in 8.0.2 sure puts crimp in moving to ODS 48

What a proverbial can of worms.

I only wish it was bass season.

Thanks for the info, Chad, and also to Jon.

In my experience, each system has its own idiosyncracies to be sure.

However, in my humble opinion, I don't think that normal administrator people should have to deal with this kind of detail when all they want to do is bring their databases up to ODS48.

I would prefer to see issues like this to be better socialized, and more to the point with solution proposals. Administrators who experience these things shouldn't have to dig to determine that they are not the only ones who have the issues. There is too much duplication of effort in problem solving of this type.

But again, I appreciate both the candor and the willingness to share potential solutions. Thanks, guys.

- Andy