Skip to content

ut.run - ORA-22921 #352

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pocelka opened this issue Jun 14, 2017 · 3 comments
Closed

ut.run - ORA-22921 #352

pocelka opened this issue Jun 14, 2017 · 3 comments

Comments

@pocelka
Copy link

pocelka commented Jun 14, 2017

Downloaded the latest version, however when running sample test, I'm getting ORA-22921.
`c:\Downloads\X2\utPLSQLv3.0.0\examples\between_string>sqlplus user/pass@db@run_betwnstr_test.sql

SQL*Plus: Release 11.2.0.3.0 Production on Wed Jun 14 17:20:54 2017

Copyright (c) 1982, 2011, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options

Function created.

Package created.

Package body created.

ORA-06512: at "SYS.DBMS_LOB", line 1146
ORA-06512: at "UT3.UT_UTILS", line 327
O
ORA-22921: length of input buffer is smaller than amount requested

BEGIN ut.run(user||'.test_betwnstr'); END;

ERROR at line 1:
ORA-22921: length of input buffer is smaller than amount requested
ORA-06512: at "UT3.UT_RUNNER", line 87
ORA-06512: at "UT3.UT_RUNNER", line 111
ORA-06512: at "UT3.UT", line 292
ORA-06512: at "UT3.UT", line 320
ORA-06512: at line 1

Package dropped.

Function dropped.`

Seems like fix in #348 was only partiall and overload procedure append_to_clob was forgotten. Changing lenght to dbms_lob.getlength helped.

@jgebal
Copy link
Member

jgebal commented Jun 14, 2017

If you are using the release v3.0.0, the fix is not there.
The fix is inly present in develop branch - not yet released.

@pocelka
Copy link
Author

pocelka commented Jun 14, 2017

Ah OK. I downloaded the latest version.

So this might be an issue.

@jgebal
Copy link
Member

jgebal commented Jun 14, 2017

We are waiting for one more fix to be merged before releasing v3.0.1

@pocelka pocelka closed this as completed Jun 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants