In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

What Debezium connector do you use and what version?

Oracle 2.3.1

What is the connector configuration?

name=enquesta-connector
connector.class=io.debezium.connector.oracle.OracleConnector
tasks.max=1
database.server.name=redacted
database.hostname=redacted
        database.port=1521
        database.user=redacted
        database.password=redacted
database.dbname=redacted
table.include.list=DBZUSER.DEBEZIUM_SIGNAL,ENQUESTACIS.CI911DISTRICT,ENQUESTACIS.CIACCOUNTACTIVECODE,ENQUESTACIS.CIACCOUNTMETERSTATUS,ENQUESTACIS.CIACCOUNTSTATUS,ENQUESTACIS.CIAGE,ENQUESTACIS.CIAMITYPE,ENQUESTACIS.CIAPPLICATION,ENQUESTACIS.CIAPPTAXDISTRICT,ENQUESTACIS.CIASSETTAXDISTRICT,ENQUESTACIS.CIBALANCEBREAKDOWN,ENQUESTACIS.CIBILLINGCYCLE,ENQUESTACIS.CICLASSTYPE,ENQUESTACIS.CICONSTRUCTIONTYPE,ENQUESTACIS.CICOUNTYCODE,ENQUESTACIS.CIDEVICECONFIG,ENQUESTACIS.CIDEVICELOCATION,ENQUESTACIS.CIDEVICEMODEL,ENQUESTACIS.CIDEVICEPARAMETER,ENQUESTACIS.CIDEVICESIZE,ENQUESTACIS.CIDEVICETYPE,ENQUESTACIS.CIDISCOUNTCODE,ENQUESTACIS.CIEMAIL,ENQUESTACIS.CIITEMCODE,ENQUESTACIS.CIMASTERREPORTCODE,ENQUESTACIS.CINAMEPREFIX,ENQUESTACIS.CINEIGHBORHOODCODE,ENQUESTACIS.CIPHONE,ENQUESTACIS.CIPOLICEDISTRICT,ENQUESTACIS.CIPROPERTYCLASS,ENQUESTACIS.CIREPORTCODEDESC,ENQUESTACIS.CISECONDARYPARTY,ENQUESTACIS.CISERVICETYPE,ENQUESTACIS.CISTATE,ENQUESTACIS.CISUBDIVISION,ENQUESTACIS.CITAXCODE,ENQUESTACIS.CITAXTYPE,ENQUESTACIS.CITOWN,CIS.FCIADDR,CIS.FCIAPREM,CIS.FCIBAL,CIS.FCICIS,CIS.FCICMTR,CIS.FCIDEVICE,CIS.FCIINSTAL,CIS.FCIITEM,CIS.FCIPREM,CIS.FCIREGISTER,CIS.FCISERVI,CIS.FDGCMAS,CIS.FRFCMAS,CIS.FRTCMAS,CIS.FSWCMAS,CIS.FTXCMAS,CIS.FUTCMAS,CIS.FWACMAS
database.history.kafka.bootstrap.servers=redacted:9092
database.history.kafka.topic=schema-changes.inventory
schema.history.internal.kafka.topic=schema-history
schema.history.internal.kafka.bootstrap.servers=redacted:9092
topic.prefix=sds_
database.history.store.only.captured.tables.ddl=true
internal.log.mining.query.logs.for.snapshot.offset=true
signal.data.collection=REDACTED.DBZUSER.DEBEZIUM_SIGNAL
value.converter.schemas.enable=false
key.converter.schemas.enable=false

What is the captured database version and mode of depoyment?

 Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.20.0.0.0

What behaviour do you expect?

SCN to be exposed as a numeric value for Prometheus JMX Exporter consumption

What behaviour do you see?

No critical SCN metrics are available in JMX Exporter scrapes

https://debezium.io/documentation/reference/stable/connectors/oracle.html#oracle-streaming-metrics

Do you see the same behaviour using the latest released Debezium version?

Yes

Do you have the connector logs, ideally from start till finish?

I can provide them if necessary, but this problem is already known.

https://stackoverflow.com/questions/73661418/debezium-oracle-connector-jmx-metrics-attribute-type-string-not-populating-to

https://groups.google.com/g/debezium/c/aUO9X5uGRF0

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

Monitoring critical Oracle SCN metrics with Prometheus/Grafana

Implementation ideas (optional)

A quick review of the jmx_exporter scraper code (https://github.com/prometheus/jmx_exporter/blob/main/collector/src/main/java/io/prometheus/jmx/JmxScraper.java) seems to indicate that exposing the SCN number as a BigInteger may work as suggested by ccranfor@redhat.com  since it inherits from Number.