On Tuesday, May 4, 2021 at 5:08:19 AM UTC-4, Jens wrote:
Sid schrieb am Dienstag, 4. Mai 2021 um 08:37:26 UTC+2:
What's the easiest way to fix this kind of Integrity error: %GTM-E-DBMRKFREE, Nature: #DANGER***
BADA3:0 FF Block incorrectly marked free
%GTM-E-DBMRKFREE, Nature: #DANGER***
BB664:0 FF Block incorrectly marked free
%GTM-E-DBMRKFREE, Nature: #DANGER***
BB7D5:0 FF Block incorrectly marked free
%GTM-E-DBMRKFREE, Nature: #DANGER***
BB9C0:0 FF Block incorrectly marked free
%GTM-E-DBMRKFREE, Nature: #DANGER***
BB9E5:0 FF Block incorrectly marked free
What's the name of the Utility for fixing integrity errors in GT.M
Does anybody know of a Tutorial or guide?
Thanks
dse ist the Tool to handle Database errors. See https://docs.yottadb.com/AdminOpsGuide/integrity.html#m1-bitmap-errors
Better Approach is to get back to last Backup and use the journal to replay all transactions since Backup.
But this depends on your Backup-Strategy
HTH
Jens
Sid, errors like these are most likely to occur when a database is not shutdown cleanly. If you're not using before-image journaling (which the default setup from sourcing the ydb_env_set file sets up), you'll have to manually fix the errors following
the instructions in the Administration and Operations Guide linked to by Jens. If you're using before-image journaling the MUPIP JOURNAL RECOVER BACKWARD command (
https://docs.yottadb.com/AdminOpsGuide/ydbjournal.html#journal) can be used to
automatically recover the database (which sourcing ydb_env_set does under the covers).
Regards
– Bhaskar
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)