Skip to content
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

Randomly occuring error during comparing two cursors #827

Closed
lwasylow opened this Issue Jan 24, 2019 · 4 comments

Comments

Projects
None yet
2 participants
@lwasylow
Copy link
Member

lwasylow commented Jan 24, 2019

When running a test with comparing two cursors from time to time error occurs.

ORA-06553: PLS-306: wrong number or types of arguments in call to 'COMPARE'

ORA-06512: at "UT3.UT_COMPOUND_DATA_VALUE", line 172

ORA-06512: at "UT3.UT_DATA_VALUE_REFCURSOR", line 253

ORA-06512: at "UT3.UT_EQUAL", line 236

ORA-06512: at "UT3.UT_EXPECTATION", line 24

ORA-06512: at "UT3.UT_EXPECTATION", line 136

ORA-06512: at "SPD.UT_SPI_ENGINE_TRA", line 239

ORA-06512: at line 6
@lwasylow

This comment has been minimized.

Copy link
Member Author

lwasylow commented Feb 26, 2019

Its still showing randomly which is annoying. I think worth to put some braces around these lines to make sure that there is no empty nulls passing so we can handle this gracefully.

@jgebal

This comment has been minimized.

Copy link
Member

jgebal commented Feb 26, 2019

Interesting why we would get nulls passed to COMPARE. As you say. This should never happer.
We will need better trapping and logging to be able to investigate it.
We can add some safety checks to prevent this error but this will not fix the problem I guess.

@lwasylow

This comment has been minimized.

Copy link
Member Author

lwasylow commented Feb 26, 2019

I think where possible we should not let to the situation where the system error occurs by invoking a sys code with invalid argument. I know it might be impossible task but if we limit at least these scenarios where we know about will be easier for user to understand error. This one above for example is very cryptic and doesn't tell you what happened there.

@lwasylow lwasylow added the bug label Feb 26, 2019

@lwasylow

This comment has been minimized.

Copy link
Member Author

lwasylow commented Mar 8, 2019

This is new code version can occurs only in SQL when comparing two columns extract from XML.
We could try run nvl on that nvl(s.column_value.getclobval(),empty_clob()) to make sure is always initialised.

@lwasylow lwasylow added this to the v3.1.4 milestone Mar 8, 2019

@jgebal jgebal closed this in #801 Mar 15, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.