Reading obejct_id_sequence during Oracle LogMiner replication.
Dominik Maciejewski
Hello, I have possible customer with very curious issue.
Source DB have extended object_id sequence – this customer installed special patch from Oracle that extends object_id sequence - Oracle maximum is 4254950909. And they have higer values. We need something like integer 8 bytes to cover this.
This patch provides additional 39000000 id's to standard maximum (4254950909). How to check and simulate:
update obj$ set dataobj#=4254950909 where name='_NEXT_OBJECT';
commit;
select dataobj# from obj$ where name='_NEXT_OBJECT';
And while creating new objects - Ora 600 will appear - without patch.
Question is "Can Debezium handle such a big number in object_id_sequenc while replicating using LogMiner? (over regular max)".
Possible issue is for example reading this value with LogMiner to debezium java (types mapping).
Chris Cranford
That's a great question and unfortunately it's not one which we can answer.
Debezium works with table/column names and not their object ids. The table that Debezium reads changes from does describe the object ids as NUMBER data types without any precision or scale, so the column theoretically supports up to 38 digits. However, the translation from id to name is a step that Oracle LogMiner does internally and there could exist the possibility of an overflow if the Oracle LogMiner code isn't written to support object ids beyond this 4254950909 threshold.
I would suggest reaching out to Oracle and having them confirm Oracle LogMiner is compatible with their patch or if there will be problems.
CC
--
You received this message because you are subscribed to the Google Groups "debezium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debezium+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/ac71754d-fbbf-4633-a829-be86843a6931n%40googlegroups.com.