Open TobiasDo1 opened 3 years ago
The issue is with oracle internal packages. For some reason, DBMS_PLSQL_CODE_COVERAGE fails when code has calls to some of SYS packages. I saw this issue myself when code was calling DBMS_STATS package.
There is no solution for this from our side, only workaround. I was wondering if we should implement it at all, but is seems to be quite common issue so maybe workaround is needed.
Hi Jacek, thanks for your reply. So does it mean that you are already aware of a workaround to overcome this? Best regards Tobias
Yes. It requires a change to utPLSQL code.
Great. Then I will wait for your changes to come. Thanks a lot, Jacek
Hi all,
I do have a problem, when executing utplsql based on a tag.
This is what I am executing:
utplsql run <schema>/<pw>@<host>:<port>/<service> --tags=erudities --debug -f=ut_coverage_cobertura_reporter -o=hex_cc_erudities.xml -s --failure-exit-code=0
And this is the output the cmd is spooling:
Other reporters are working and issue is also not coming, if I select another tag. So obviously it is something dealing with the packages that are selected with this tag, but I cannot figure it out from the error message. All packages in schema are in valid state.
Any help is appreciated. Thank you and best regards