This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


~Holly Lopweburakoi
Apr 29, 2014, 4:41 PM
51 Posts
topic has been resolvedResolved

Unable to "upgrade" ODS format of daoscat.nsf...

  • Category: Administration
  • Platform: Windows
  • Release: 9.0.1
  • Role: Administrator
  • Tags: DAOS,Catalog
  • Replies: 5

After upgrade do Domino R9 we have upgraded almost all databases to ODS 52 (R9). However, we have problem to upgrade ODS of DAOS Catalog:

 

1) We have stopped Domino server (> quit)

2) Issued cmmand from CMD: > ncompact daoscat.nsf -c -i

3) The response is (always): Error compacting daoscat.nsf,  daoscat.nsf -c -i: Database is currently in use by you or another user
 

How can I upgrade ODS format of this database? (I know, that it will run without problems under ODS 43, however this is our custopmer's infrastructure and they want to know answer...)

~Lisa Frogerozen
Apr 30, 2014, 5:47 PM
115 Posts
Suggestions

1. Stop all services related to Domino.

2. If 1 doen't work, use Unlocker or another software to find which process is locking your file.

Jean-Pierre

~Lisa Frogerozen
Apr 30, 2014, 5:47 PM
115 Posts
Suggestions

1. Stop all services related to Domino.

2. If 1 doen't work, use Unlocker or another software to find which process is locking your file.

Jean-Pierre

~Holly Lopweburakoi
May 1, 2014, 12:18 PM
51 Posts
Thanks for tips, however the daoscat.nsf is not locked....

....by any service. I've stopped all Domino related services, checked it via Unlocker: The file could be moved/renamed in OS without any problem...

However, when I issue >ncompact daoscat.nsf -c -i, the above mentioned error (the file is used by you or another user....) is displayed. Compacting other databases is not problem (e.g. >ncompact log.nsf -c- -i will compact it...)

It's really strange - maybe the daoscat.nsf internal structure prohibits compacting (as it's not fully initialized database), do you have similar experience?

 

Added later - workaround found:

I renamed dasocat.nsf to daoscat1.nsf and issued >ncompact daoscat1.nsf -c -i

Result:

C:\Program Files (x86)\IBM\Lotus\Domino>ncompact daoscat1.nsf -c -i
Restart Analysis (0 MB): 100%
01. 05. 2014 14:42:19  Recovery Manager: Restart Recovery complete. (0/0 databases needed full/partial recovery)
01. 05. 2014 14:42:19  The DAOS catalog does not exist.: File does not exist
01. 05. 2014 14:42:19  Recovery Manager: Assigning new DBIID for C:\Program Files (x86)\IBM\Lotus\Domino\data\daoscat.nsf (need new backup for media recovery).
01. 05. 2014 14:42:21  Compacting daoscat1.nsf (DAOS Catalog),  daoscat1.nsf -c -i
01. 05. 2014 14:42:21  Recovery Manager: Assigning new DBIID for C:\Program File s (x86)\IBM\Lotus\Domino\data\daoscat1.nsf (need new backup for media recovery).
01. 05. 2014 14:42:21  Compacted  daoscat1.nsf, 0K bytes recovered (0%)
01. 05. 2014 14:42:23  Database compactor process shutdown

The daoscat1.nsf was compacted and new daoscat.nsf was created.

 

Conclusion: The compact task runs "special" on file called daoscat.nsf...

~Sven Nimgerosterflar
May 6, 2014, 1:40 PM
46 Posts
Data is not ODS'ed
The ODS in the daos catalog does not play a role as the data stored in the doas catalog is not ODS'ed.  Therefore upgrading the ODS from 43 to 51 would not really be necessary.  
If you really must (even tho there is no point in doing so) you can do the following

Option #1
1. Shut down Domino
2. Make an OS copy (not Notes copy --it wont work)) of the daoscat.nsf  (example daoscatcopy.nsf)
3. Run the compact -c to upgrade the ODS on the copy made in step 2 (example:  compact -c daoscatcopy.nsf)
4. Rename the current daoscat.nsf to daoscatbackup.nsf ( so that we have a copy in case we need to revert back)
5. Rename the database compacted in step 3 to  daoscat.nsf
6. Start the server

Option#2

1. Stop the server
2. Copy daoscat.nsf to a Notes client machine
3. Run compact -c from the Notes client against the daoscat.nsf copied in step 2
4. Rename the current daoscat.nsf on the server to daoscatbackup.nsf ( so that we have a copy in case we need to revert back)
5. Copy the daoscat.nsf compacted in step 3 back to the server
6. Start the server
~Ned Opjumiobu
Sep 11, 2014, 7:11 AM
10 Posts
Perfect solution for ODS 52 issue

Thank you Ricardo!  Although perhaps not necessary, I have still done the conversion.

I like to have ALL database on the newest ODS, because I have had performance problems in the past with old databases lingering on an old ODS.

Since I use ODS 52 (9.0.1), my usual 'ncompact -* -ods -upgrade' after each fix pack or upgrade was being foiled by the daoscat.nsf being always open.  Your method of making an OS copy let me fix that.

 

BTW the -upgrade, option is new, it upgrades databases who were created using the ns6. ns5 or ns4 extension.  Using that extension set a database ODS class which before needed to be removed by creating a new replica with an nsf extension.  Now only a rename and compact command is needed, having the bonus of keeping the original creation date.

 

Cheers!


This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal