Skip to Main Content

Oracle Database Free

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

ORA-54400: Invalid BLOB size when loading ONNX model in Oracle 23ai Free

djoga98Feb 8 2025

I am using Oracle Database 23ai Free and trying to load an ONNX model for text embedding using DBMS_VECTOR.LOAD_ONNX_MODEL. My model (LaBSE) is approximately 1.88GB in size.

Here is my PL/SQL block:

BEGIN
 DBMS_VECTOR.DROP_ONNX_MODEL (
   model_name => 'LaBSE',
   force => TRUE);
 DBMS_VECTOR.LOAD_ONNX_MODEL (
   directory  => 'model_dir',
   file_name  => 'LaBSE.onnx',
   model_name => 'LaBSE');
END;

However, I get the following error:

ORA-54400: Invalid BLOB size
ORA-06512: at "SYS.DBMS_VECTOR", line 2150
ORA-06512: at "SYS.DBMS_DATA_MINING", line 5767
ORA-06512: at "SYS.DBMS_VECTOR", line 2145
ORA-06512: at line 6

I checked the Oracle documentation for ORA-54400 and ORA-06512 but couldn't find a clear resolution.

Is there a size limit for ONNX models in Oracle 23ai Free? If so, is there a way to increase it or work around this issue? Any guidance would be appreciated.

Thanks!

This post has been answered by gsalem-Oracle on Feb 18 2025
Jump to Answer

Comments

MartinBach-Oracle Jan 8 2025

Hi Salomon,

please have a look at this blog post written by @ulrike-schwinn-oracle :

https://blogs.oracle.com/coretec/post/easy-sql-statement-tracking-in23c

I hope this answers your question, if not, please shout!

- Martin

Solomon Yakobson Jan 8 2025

@martinbach-oracle - No, it doesn't answer my question. Article you pointed to shows uses:

SQL> alter system set sql_history_enabled=true scope=both;

And in my post I said “Works fine when enabled on system level”. My question was about

SQL> ALTER SESSION SET SQL_HISTORY_ENABLED = TRUE;

where I showed SQL history was NOT captured even though it should be based on SQL_HISTORY_ENABLED:

Modifiable **ALTER SESSION**, ALTER SYSTEM

SY.

MartinBach-Oracle Jan 8 2025

As per the article I shared the situation is as follows at the moment

  • You must enable SQL history PDB-wide (only a DBA can do that) so there's a certain level of control over the feature
  • Your session has access to the SQL history
  • If you don't want to record anything, set sql_history_enabled to false.

I'm currently assessing if that's intended behaviour (in which case the documentation should be amended) or a feature not working as it should (in which case it needs fixing). The parameter is indeed session-modifyable, but not in the sense you expected.

We'll keep you posted.

- Martin

Solomon Yakobson Jan 8 2025

Do you mean it must be enabled on system level and not on session level and all session can do is disabe it for the session?

SY.

MartinBach-Oracle Jan 14 2025

Yes,

that's correct as of Oracle Database Free 23.6.

- Martin

Solomon Yakobson Jan 14 2025

Thanks Martin, I hope this will be added to 23AI docs soon.

SY.

1 - 6

Post Details

Added on Feb 8 2025
1 comment
105 views