StartNewDatabaseGeneration and summary records

Panorama X
1

My procedure crashed because of some programming errors, after I had used StartNewDatabaseGeneration and created some summary records. This left the database locked and waiting for me to UploadNewDatabaseGeneration. However, when I try to upload the new generation, I receive the error “RemoveSummaries statement failed because database is read only,” and when I try to manually or programmatically remove the summaries I can’t because the database is locked as it waits for having the new database generation uploaded.

So I’m stuck. What should I do?

UPDATE: I tried the “Revert to last generation on server” button but it told me it couldn’t download components of the database from the server. So I Aborted the new generation and am now in single user mode. I know a complicated procedure to get back running now. Is there something better I should have done?

UPDATE 2: Now it seems like there is no way to reattach the database (or any copy thereof) to the server. It remains locked.

2

I’m not 100% sure I understand the sequence of events you are describing. I think maybe you are saying:

  1. You used the StartNewDatabaseGeneration statement to start a critical update.
  2. You ran a procedure that caused Panorama to crash. (You say “my procedure crashed” - does that mean the procedure stopped or Panorama quit and you had to relaunch it.)
  3. I’m going to assume that you had to relaunch Panorama, and re-open the database. Though that doesn’t really make sense to me because then there would be no summary records. But I can’t think of any other scenario where the database would be locked and read-only.

UPDATE 2: Now it seems like there is no way to reattach the database (or any copy thereof) to the server. It remains locked.

It seems to me that the only way to move forward would be to delete the database from the server, then re-upload it. Then all of the other users will have to download the database again.