MHR Ownership Production data issue at BCA #18098
Comments
|
@lbergero819 @mstanton1 assets ticket 18043 now in PROD addresses future owngroup table grpseqno values with a tenants in common scenario. I have applied a data fix to the 101 registration for MHR 107962 owngroup table second group grpseqno, changing it from 1 to 2: In the above BCA data, the second number is the document registration number. 00483496 and 00483494 are registrations created in the legacy system, so I am ignoring those. For the owner records created in MHR with document registration number 00550062: Comparing the owner record from an existing tenants in common registration, the values in the owner record are correct. I think the extract owner record is using the owngroup.grpseqno which is now fixed. |
|
DB2 PROD 107962 101 registration owner record info: Example of existing 101 tenants in common owner information: The owngrpid, ownerid, and ownseqno values match. |
|
Thank you Doug,
I have follow-up questions
1. You mention below that you are ignoring registrations (00483494 & 00483496) in error with document registration number 00483496 and 00483494, as they were created in the legacy system, do we know why they are rejected at BCA?
2. For registration 00550062 it has been fixed by using the owngroup.grpseqno in the extract owner record, but do we need to go back and convert other records from previous registrations that could have the same issue?
3. For the issue fixed from ticket 18043, owngroup table, can we check if other registrations with TC done previously have the same issue, and if so, can we fix them.
Thanks
Louise
From: Doug Lovett ***@***.***>
Sent: Thursday, October 5, 2023 12:41 PM
To: bcgov/entity ***@***.***>
Cc: Bergeron, Louise CITZ:EX ***@***.***>; Mention ***@***.***>
Subject: Re: [bcgov/entity] MHR Ownership Production data issue at BCA (Issue #18098)
[EXTERNAL] This email came from an external source. Only open attachments or links that you are expecting from a known sender.
@lbergero819<https://github.com/lbergero819> @mstanton1<https://github.com/mstanton1> assets ticket 18043 now in PROD addresses future owngroup table grpseqno values with a tenants in common scenario. I have applied a data fix to the 101 registration for MHR 107962 owngroup table second group grpseqno, changing it from 1 to 2:
update amhrpdb.owngroup
set grpseqno = 2
where manhomid = 550091
and regdocid = '63502788'
and owngrpid = 2
;
which fixes:
107962 00550062 C 001 000 E TC UNDIVIDED 1/2 <-- rejected
In the above BCA data, the second number is the document registration number. 00483496 and 00483494 are registrations created in the legacy system, so I am ignoring those.
For the owner records created in MHR with document registration number 00550062:
107962 00550062 C 001 001 F B 2506742396 V0E 1N2 SILVER DEW HARDWOODS LTD. PETER IAN PELTON 420 RICHIE RD CLEARWATER BC CA <-- inserted
107962 00550062 C 001 001 F B 2506747076 V0E 1N1 KIJA HOLDINGS LTD. TODD PHILLIPS 444 RICHIE RD CLEARWATER BC CLEARWATER BC CA <-- rejected
Comparing the owner record from an existing tenants in common registration, the values in the owner record are correct. I think the extract owner record is using the owngroup.grpseqno which is now fixed.
—
Reply to this email directly, view it on GitHub<#18098 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AT3A4LZ2KY3MVUAZX7EBKMLX54EOHAVCNFSM6AAAAAA5UV6YCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZGUZTKMZWHE>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
|
@lbergero819
|
|
Thank you Doug
From: Doug Lovett ***@***.***>
Sent: Thursday, October 5, 2023 3:06 PM
To: bcgov/entity ***@***.***>
Cc: Bergeron, Louise CITZ:EX ***@***.***>; Mention ***@***.***>
Subject: Re: [bcgov/entity] MHR Ownership Production data issue at BCA (Issue #18098)
[EXTERNAL] This email came from an external source. Only open attachments or links that you are expecting from a known sender.
@lbergero819<https://github.com/lbergero819>
To answer your questions.
1. I don't know but it may be a cascading issue. The original registration owner group/owner record load failed, so subsequent change registration loads failed. I have no insight into the BCA load process.
2,3 I am not sure what the difference is between these questions. There has only been 1 tenants in common registration in the modernized system for MHR 107962, so no further data fixes are needed.
—
Reply to this email directly, view it on GitHub<#18098 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AT3A4L3WXUVP2OL3SM7DIHTX54VNTAVCNFSM6AAAAAA5UV6YCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZG4YTSNBSGE>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
|
@lbergero819 can this be closed? Have you reached out to BCA to confirm all is well on their side. For future ops issues can you please log those tickets on the ops board: https://app.zenhub.com/workspaces/ops-60f8556e05d25b0011468870/board? |
|
Yes I will use OPS board, and I am in a middle of writing the email to BCA
From: mstanton1 ***@***.***>
Sent: Friday, October 6, 2023 9:42 AM
To: bcgov/entity ***@***.***>
Cc: Bergeron, Louise CITZ:EX ***@***.***>; Mention ***@***.***>
Subject: Re: [bcgov/entity] MHR Ownership Production data issue at BCA (Issue #18098)
[EXTERNAL] This email came from an external source. Only open attachments or links that you are expecting from a known sender.
@lbergero819<https://github.com/lbergero819> can this be closed? Have you reached out to BCA to confirm all is well on their side.
For future ops issues can you please log those tickets on the ops board: https://app.zenhub.com/workspaces/ops-60f8556e05d25b0011468870/board<https://app.zenhub.com/workspaces/ops-60f8556e05d25b0011468870/board>?
—
Reply to this email directly, view it on GitHub<#18098 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AT3A4L44QGB5IDOPLD3AQDDX6AYEJAVCNFSM6AAAAAA5UV6YCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGA4DSNJYHE>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
|
On October 6, BCA has been advised that we have made a fix to prevent further similar issues, and since then they did not report any other case, so this can be closed. |
This morning BCA referred ownership data issues, there seems to be 2 different issues, first with the owner-sequence number being duplicated and second issue is the owner group number also being duplicated (is that related to ticket 18043?)
below is what has been reported by BCA:
In addition to the usual owner records with incorrect OWNER_SEQUENCE_NO (where the 2nd owner SHOULD have a different OWNER_SEQUENCE_NO):
107962 00483494 C 001 001 F B 2506742396 V0E 1N2 SILVER DEW HARDWOODS LTD. PETER IAN PELTON 420 RICHIE RD CLEARWATER BC CA <-- inserted
107962 00483494 C 001 001 F B 2506747076 V0E 1N1 KIJA HOLDINGS LTD. TODD PHILLIPS 444 RICHIE RD CLEARWATER BC CLEARWATER BC CA <-- rejected
107962 00483496 P 001 001 H B 2506742396 V0E 1N2 SILVER DEW HARDWOODS LTD. PETER IAN PELTON 420 RICHIE RD CLEARWATER BC CA <-- inserted
107962 00483496 P 001 001 H B 2506747076 V0E 1N1 KIJA HOLDINGS LTD. TODD PHILLIPS 444 RICHIE RD CLEARWATER BC CLEARWATER BC CA <-- rejected
107962 00550062 C 001 001 F B 2506742396 V0E 1N2 SILVER DEW HARDWOODS LTD. PETER IAN PELTON 420 RICHIE RD CLEARWATER BC CA <-- inserted
107962 00550062 C 001 001 F B 2506747076 V0E 1N1 KIJA HOLDINGS LTD. TODD PHILLIPS 444 RICHIE RD CLEARWATER BC CLEARWATER BC CA <-- rejected
there's are now also duplicate records for owner groups. See below:
107962 00483494 C 001 000 E TC UNDIVIDED 1/2 <-- inserted
107962 00483494 C 001 000 E TC UNDIVIDED 1/2 <-- rejected
107962 00483496 P 001 000 G TC UNDIVIDED 1/2 <-- inserted
107962 00483496 P 001 000 G TC UNDIVIDED 1/2 <-- rejected
107962 00550062 C 001 000 E TC UNDIVIDED 1/2 <-- inserted
107962 00550062 C 001 000 E TC UNDIVIDED 1/2 <-- rejected
The text was updated successfully, but these errors were encountered: