You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It will be convenient to obtain actual attributes of DB when its state is backup-lock.
Currently such actions as 'gfix -w sync | async' or 'gfix -h <sweep_interval>' do not reflect on gstat -h:
It is easy to check if we first do 'nbackup -L <dbname>' and then:
1) check current header:
# /opt/fb30/bin/gstat -h /home/bases/oltp30-etalone.fdb | tail
Creation date Apr 3, 2020 16:41:55
Attributes force write, backup lock
In this example "force write" attribute remains unchanged. But is *was* changed and this can be seen when querying mon$database table.
So, one need to connect and to ask monitoring to get actual value of this attribute.
The text was updated successfully, but these errors were encountered:
Submitted by: @pavel-zotov
Is duplicated by CORE6402
It will be convenient to obtain actual attributes of DB when its state is backup-lock.
Currently such actions as 'gfix -w sync | async' or 'gfix -h <sweep_interval>' do not reflect on gstat -h:
It is easy to check if we first do 'nbackup -L <dbname>' and then:
1) check current header:
# /opt/fb30/bin/gstat -h /home/bases/oltp30-etalone.fdb | tail
Creation date Apr 3, 2020 16:41:55
Attributes force write, backup lock
Variable header data:
Sweep interval: 0
*END*
Gstat completion time Wed Sep 9 10:32:54 2020
2) try to change FW (or sweep interval; or page buffers - no matter):
# /opt/fb30/bin/gfix -w async localhost:/home/bases/oltp30-etalone.fdb
# -- no output, i.e. all OK --
3) read DB header again:
# /opt/fb30/bin/gstat -h /home/bases/oltp30-etalone.fdb | tail
Creation date Apr 3, 2020 16:41:55
Attributes force write, backup lock
Variable header data:
Sweep interval: 0
*END*
Gstat completion time Wed Sep 9 10:33:17 2020
In this example "force write" attribute remains unchanged. But is *was* changed and this can be seen when querying mon$database table.
So, one need to connect and to ask monitoring to get actual value of this attribute.
The text was updated successfully, but these errors were encountered: