Fixing 262 Warnings?

[Former Member]

Hello all,

MDM Server version 5.5 SP5 (5.5.42.83) on Solaris with an Oracle 10g database.

I ran a Verify / Check on a master repository yesterday and was told there were 262 warnings. Viewing the report showed that all 262 were: "Warning (1385): The table xyzzy has not been analyzed recently." where xyzzy is an MDM table name.

How do I analyze my tables? When I right-click my repository in the Console, I don't see that choice in the submenu.

Any help would be appreciated.

-Bruce

[Former Member · Accepted solution]

After check in Console, right click on repository and do Verify--> Repair repository. then again check do you get any fatal error or warning message.

BR,

Alok

[Former Member · Accepted solution]

Thank you for replying.

I cannot do the repair at this time because the repository is in a production environment and I cannot unload it until late Saturday night (during specified maintenance window).

I will let you know the result after I do it.

-Bruce

[Former Member]

Hi Bruce,

I ran a Verify / Check on a master repository yesterday and was told there were 262 warnings. Viewing the report showed that all 262 were: "Warning (1385): The table xyzzy has not been analyzed recently." where xyzzy is an MDM table name.

1. Now, as Alok mentioned, please use the Verify->Repair commmand. Since you only have Warnings in the Repository, it is very likely that it removes all the Warnings.

2. Also, since the warning also tellls you about analzing a table recently. It can be any structural change. Hence when you will be unloading the repository for Repairing, then please use - Load with Updated indices. it is generally useful in the case of the structural changes done in Console.

And you are also viewing the Log report. It will also help you.

Hope it helps.

Thanks and Regards

Nitin Jain

[Former Member]

During our maintenance window, I ran the Verify/Repair and then Load/Update Indices. The 262

warnings were fixed. I wonder if I have to do this every few weeks in order to keep the tables "analyzed".

I created a new slave repository because I am not sure if the Update Indices confuses the synchronizer.

Also, to respond to one of the other replies - it is unlikely that the catalog structure has changed recently. The last time the Master repository was loaded was back on Feb 10.

Edited by: Bruce Berkowicz on Apr 7, 2008 2:20 PM

[former_member201266]

Hi,

I think the repository sturctured had been changed; for example if you have a loop up field in main table reference to a sub table field; that field in the sub table might be deleted or might be that sub table itself is deleted, this is just an example, they might be some other such change which happened, kindly recheck with last few update that you made on the repository, that will give you the solution for your question.

Cheers,

Cherry.