Dieser Artikel aus der KB beschreibt zwar die Gegenrichtung, aber ich könnte mir vorstellen, dass das trotzdem auch auf Deinen Fall zutrifft:
Problem
A database created with an On Disk Structure (ODS) specific extension (for example .NS4 or .NS5) is not upgraded by the Compact task even though the extension has been renamed to .NSF.
Solution
By design when a database is created with a ODS-specific extension the database is flagged so that Compact will not alter the database. Renaming the extension of the database has no effect on this flag; once the flag is set it cannot be reset. The flag is set in the Creation-class property of the database header. Databases created with an .NSF extension have a Creation-class value of "NoteFile", and will have their ODS upgraded by Compact as necessary.
To upgrade the ODS of a database originally created with an ODS-specific extension create a new replica (select File --> Replication --> New Replica) or a new Notes copy (select File --> Database --> New Copy) of the database, and give it an NSF extension.
The fact that the Help incorrectly indicates that renaming the extension will allow Compact to update the ODS of a database, has been reported to Lotus Software Quality Engineering (SPR # RMAS5MYJHV).
Supporting Information:
The Creation-class property can be seen in the Database Information section of a database by using the NotesPeek tool. For more information about NotesPeek see the document, "NotesPeek 1.5x for R5: A Tool for Viewing Notes Databases on Notes R5 Clients Document" (#4003920).
Du siehst: Durch das reine umbenennen wird das Flag, dass es sich bei der DB um eine 5er- DB handelt, NICHT gelöscht... Andersherum kann ich mir vorstellen, dass das Flag durch einfaches umbenennen nach ns5 auch nicht gesetzt wird...
Du musst wahrscheinlich eine neue Repli erstellen, und der von vorneherein ns5 als Endung geben, dann wird das Flag wahrscheinlich auch gesetzt...
Hier übrigens noch ein KB- Artikel zu dem Thema..
HTH
Tode
An administrator is interested in preventing the On Disk Structure (ODS) from being updated when they migrate to a later release. What is the recommended procedure for doing this?
Solution
The suggested method to prevent a databases ODS from being updated is to schedule the Compact task on the sever to run with the -R switch, or to create a new replica of the database with a version-specific extension. For example, if you create a replica with a NS5 extension in a Notes 6.x environment, the database will be the R5 ODS, which will not be updated when Compact runs without the -R switch.
If a database's ODS has been updated to the later ODS then you can run Compact with the -R switch to revert the ODS.
Note: Renaming the filename extension of a database to NS4 or NS5 will not prevent Compact from upgrading the ODS; the functionality which prevents the ODS change involves more than the file name extension.
