Rebuilding operational schema

So, I've decided not to upgrade eDir on the NW60 servers, install the
NW65SP8 servers with 8.7.3.10 and then upgrade all of the NW65 servers
to eDir 8.8.x once all of the NW60 servers have been decommissioned.

Is there any concern about having these notices in the DSREPAIR logs for
the NW60 servers? Should I try to get rid of these notices or can I just
not worry about them and let them disappear as the NW60 servers get
decommissioned? There are no actual errors, only these notices...

Geoff K. wrote:
> Thanks for the response. Here is why I asked this question. I am getting
> ready for a migration to Linux, so first I need to get all of the
> servers -- presently running NW60SP5 -- up to NW65SP8 with eDir 8.8.
> When I have run database repairs I get the following notices:
>
> * * * * * * *
>
> Schema Attribute Definition, Object ID: 00000188, RDN: App Blurb
> NOTICE: Invalid OID for : App Blurb, You need to run DSRepair on the
> [Root] replica.
>
> Schema Attribute Definition, Object ID: 00000189, RDN: App Contacts
> NOTICE: Invalid OID for : App Contacts, You need to run DSRepair on the
> [Root] replica.
>
> Schema Attribute Definition, Object ID: 0000018A, RDN: App Drive Mappings
> NOTICE: Invalid OID for : App Drive Mappings, You need to run DSRepair
> on the [Root] replica.
>
> Schema Attribute Definition, Object ID: 0000018B, RDN: App Flags
> NOTICE: Invalid OID for : App Flags, You need to run DSRepair on the
> [Root] replica.
>
> Schema Attribute Definition, Object ID: 0000018C, RDN: App Icon
> NOTICE: Invalid OID for : App Icon, You need to run DSRepair on the
> [Root] replica.
>
> Schema Attribute Definition, Object ID: 0000018D, RDN: App Parameters
> NOTICE: Invalid OID for : App Parameters, You need to run DSRepair on
> the [Root] replica.
>
> Schema Attribute Definition, Object ID: 0000018E, RDN: App Path
> NOTICE: Invalid OID for : App Path, You need to run DSRepair on the
> [Root] replica.
>
> Schema Attribute Definition, Object ID: 0000018F, RDN: App Printer Ports
> NOTICE: Invalid OID for : App Printer Ports, You need to run DSRepair on
> the [Root] replica.
>
> Schema Attribute Definition, Object ID: 00000190, RDN: App Shutdown Script
> NOTICE: Invalid OID for : App Shutdown Script, You need to run DSRepair
> on the [Root] replica.
>
> Schema Attribute Definition, Object ID: 00000191, RDN: App Startup Script
> NOTICE: Invalid OID for : App Startup Script, You need to run DSRepair
> on the [Root] replica.
>
> Schema Attribute Definition, Object ID: 00000192, RDN: App Working
> Directory
> NOTICE: Invalid OID for : App Working Directory, You need to run
> DSRepair on the [Root] replica.
>
> Schema Attribute Definition, Object ID: 00000193, RDN: Desktop
> NOTICE: Invalid OID for : Desktop, You need to run DSRepair on the
> [Root] replica.
>
> Schema Attribute Definition, Object ID: 00000194, RDN: Auto Start
> NOTICE: Invalid OID for : Auto Start, You need to run DSRepair on the
> [Root] replica.
>
> Schema Attribute Definition, Object ID: 00000195, RDN: Launcher Config
> NOTICE: Invalid OID for : Launcher Config, You need to run DSRepair on
> the [Root] replica.
>
> Schema Class Definition, Object ID: 000004B0, RDN: Application (DOS)
> NOTICE: Invalid OID for : Application (DOS), You need to run DSRepair on
> the [Root] replica.
>
> Schema Class Definition, Object ID: 000004B1, RDN: Application (Windows
> 3\.x)
> NOTICE: Invalid OID for : Application (Windows 3\.x), You need to run
> DSRepair on the [Root] replica.
>
> Schema Class Definition, Object ID: 000004B2, RDN: Application (Windows 95)
> NOTICE: Invalid OID for : Application (Windows 95), You need to run
> DSRepair on the [Root] replica.
>
> Schema Class Definition, Object ID: 000004B3, RDN: Application (Windows NT)
> NOTICE: Invalid OID for : Application (Windows NT), You need to run
> DSRepair on the [Root] replica.
>
> * * * * * * *
>
> They all appear to be old ZFD4-related objects (no Zen version in use
> any longer)...
>
> I want to get these to go away, and I was thinking about rebuilding the
> operational schema on Root, but it makes me nervous I might corrupt the
> Root replica. The master of Root is still a NW60SP5 server. Should the
> server holding the root replica be a NW65 server?
>
> Any thoughts on how to clear these up, or if they're nothing to worry
> about for the migration would be greatly appreciated.
>
> Thanks,
>
> -- Geoff