We have a Database on R8.02 server:
The server crashed due to: “Couldn’t get default View id for database”
The database has a corresponding template containing numerous new views, which will replace views in the production database. One of the new views was flagged as the “default view.”
Using the template, manually ran a “Replace design” on the production db.
Although the default view was replaced in the db design by the “replace design” action, the flag to identify the default view did not “carry” to the database.
The database new design functionality was verified in production, via the Notes client. But the default view flag was not verified via the designer. And in fact, the flag for the default view was not present. No view was flagged as a default view.
That evening, the production server housing this database crashed after a scheduled agent for the database successfully completed. The error: Couldn’t get default View id for database.
-
Is there some way to avoid a crash if a default view flag is not present in a database?
-
Is there a standard code that is recommended so that if a default view is not identified in a database, an agent can continue to run, and not crash the server?
-
Shouldn’t the default view flag been maintained when the template was used to replace design of the target database?
-
Why is the notes server dependent on a default view in a database?
I remember from the R4 days that flagging the default view was critical. But I would have expected the “replace design” using the template to maintain the default view flag, set in the template.
Has anyone else experienced this? Is this an R8 bug?
Thanks.