Database cannot be unlocked (nbackup) if located on a raw device [CORE5264] #5543
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
|
Commented by: @ibaseru well, since DE corrected me, I had a blind eye, mixed -U and -N, corrected my comment, so, only one thing left: -D off - it is used only for -B n. It is nonsense for lock/unlock options. |
|
Commented by: @dyemanov Dmitry, -N = uNlock, -U = User ;-) |
|
Commented by: @AlexPeshkoff To be precise - we should allow that switch only for -B, yes? |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0.1 [ 10730 ] Fix Version: 4.0 Alpha 1 [ 10731 ] |
Modified by: @AlexPeshkoffVersion: 4.0 Initial [ 10621 ] |
Modified by: @dyemanovsummary: To unlock a raw device DB is not working. => Database cannot be unlocked (nbackup) if located on a raw device |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Cannot be tested |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Sascha Michel (datiscum1)
Alias for my db in databases.conf
KMR-DB = /dev/DS1/DB-KM
/dev/DS1/DB-KM is a ZFS block device
I have a delta file set with:
alter database add difference file '/tmp/KMR-DB.delta'
Then I set the lock with:
/opt/firebird/bin/nbackup -S -T -D off -U sysdba -P 'master' -L KMR-DB
1061504
The File i set is used.
Now I want to release the lock with:
/opt/firebird/bin/nbackup -U sysdba -P 'master' -T -N KMR-DB
No error is reported even in firebird.log File.
If I want to put a lock again, there is an error message.
/opt/firebird/bin/nbackup -S -T -D off -U sysdba -P 'master' -L KMR-DB
[
PROBLEM ON "begin backup".
unsuccessful metadata update
-ALTER DATABASE failed
-Database is already in the physical backup mode
SQLCODE:-607
]
The delta File is in use.
Since the N switch is not working, there is no way to apply the changes to the DB.
With a database file it works as it should.
Commits: 1a4b7eb bbe640a 8709dab 97afe43
The text was updated successfully, but these errors were encountered: