Reported issues for MCPDBWizard

Pod holds 9 of 9 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to MCPDBWizard.

Most discussed

Users urged to download and run 'extraObjects.sql', even when it's just two lines, one blank and one comment.

Download extraObjects.sql — the TYPE definitions this config's collection parameters need. The server creates them itself if it may; hand this to a DBA if the account has no CREATE TYPE.

Read the thread · 2026-09-03 · closed · 2 comments

A TIMESTAMP inside a ref cursor comes back as Oracle's internal form

Tracked on the Known issues page as entry 12.

Bites when: any PL/SQL routine whose OUT (or returned) ref cursor selects a TIMESTAMP column.

FIXED IN 2.0.28. Present in 2.0.27 and every release before it. The fix is in GENERATED code, so a config generated earlier keeps the old behaviour until it is regenerated.

A ref cursor selecting a TIMESTAMP hands the agent Oracle's internal representation instead of a time:…

Read the thread · 2026-09-10 · closed · 1 comment

On Oracle 12c only, a routine taking a record collection IN and returning one OUT will not bind

Tracked on the Known issues page as entry 11.

Bites when: Oracle 12c only, and only that combination.

A routine that takes a collection of records in and returns one out fails on Oracle 12c with

Attempt to set a non-existent parameter number 4; legal range is '1' to '2'

12c only, and only that combination. Same routine, same generated config, measured:

| Routine shape | Oracle 12c | 18c and later…

Read the thread · 2026-09-09 · open · 0 comments

A config with many tools can outgrow Oracle's open_cursors

Tracked on the Known issues page as entry 10.

Bites when: roughly 300 tools or more, at the default setting.

A generated DAO holds one open cursor per distinct tool, for the life of the session. That is statement reuse working as designed — a tool prepares its statement once and keeps it — but it means the cursors a server holds grows with the size of its tool list, not with…

Read the thread · 2026-09-09 · open · 0 comments

No TNS aliases, wallets, TLS to the database, RAC or SCAN

Tracked on the Known issues page as entry 9.

Bites when: any estate that is not reachable as host / port / service.

A connection is built as host, port and SID or service name, and that is the whole of it:

jdbc:oracle:thin:@<host>:<port>/<service>

Which means none of the following works as you would expect it to:

Read the thread · 2026-09-09 · open · 0 comments

A DML SQL statement cannot hand back a generated key

Tracked on the Known issues page as entry 8.

Bites when: an INSERT of your own into an identity or sequence-keyed table.

One of your own INSERT statements, exposed as a tool, always answers

{"executed":true}

and nothing else. If the table has a GENERATED … AS IDENTITY column or a sequence-backed key, the value the database just assigned is not in that reply, so a caller…

Read the thread · 2026-09-09 · open · 0 comments

A VECTOR routine parameter crosses as a dense array only

Tracked on the Known issues page as entry 7.

Bites when: binary or sparse vectors through PL/SQL.

A VECTOR column crosses MCP in all its storage formats — dense, BINARY as base64, and SPARSE as a {length, indices, values} object. A VECTOR routine parameter crosses as a dense array only.

This is a deliberate scope decision rather than an oversight. PL/SQL forbids a…

Read the thread · 2026-09-09 · open · 0 comments

A too-long value names the position, not the field

Tracked on the Known issues page as entry 6.

Bites when: any insert or update that overflows a column.

Overflowing a column gives you

Error while trying to set parameter 3: ORA-17072 Inserted value too large for column: "SOME_VALUE"

The half that names the value is Oracle's and we cannot change it. Ours is the half that says parameter 3 where it could say which field. On a record…

Read the thread · 2026-09-09 · open · 0 comments

Most recent

Record keys are the generated field names, not the column names

Tracked on the Known issues page as entry 3.

Bites when: any record parameter.

A record crosses as a JSON object keyed by the generated Java field name, so a CUSTOMERS%ROWTYPE parameter wants

{ "paramName": "…", "paramCity": "…", "paramZip": 94107 }

and not NAME, CITY, ZIP as the DDL spells them.

This used to be the worst failure in the product: the names were not published,…

Read the thread · 2026-09-09 · open · 0 comments

The remaining reports are on the project's issue tracker.