request synchronization error in the GBAK utility (restore) [CORE5579] #5846
Assignees
Comments
Modified by: Oleg Matveyev (o_matveev)Attachment: gbak_test_rest.7z [ 13160 ] Attachment: r.bat [ 13161 ] Attachment: r.sql [ 13162 ] |
Modified by: Oleg Matveyev (o_matveev)Attachment: r.bat [ 13163 ] |
|
Commented by: Oleg Matveyev (o_matveev) Total rows, with -O -N -I options ============ Rows with -O options ============ |
Modified by: Sean Leyne (seanleyne)Attachment: r.bat [ 13161 ] => |
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Alpha 1 [ 10731 ] Fix Version: 2.5.8 [ 10809 ] Fix Version: 3.0.3 [ 10810 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Done successfully |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: Oleg Matveyev (o_matveev)
Attachments:
gbak_test_rest.7z
r.sql
r.bat
We have database in which there are 14 rows with has violation of NOT NULL constraint.
We create backup copy with gbak utility.
But in the restore progress disappear not 14, but 1981 rows.
Errors are displayed
Gbak: ERROR: request synchronization error
If you restore DB with the -n -i option, you can see all the rows.
Question: why was not restore 1967 rows?
Commits: 100b539 661df1b 81dea30
The text was updated successfully, but these errors were encountered: