I will put my outcomes about Detected Oracle driver stuck during Statement initialization error.
When running tests without file mapping it runs ok. See:
Microsoft Windows [Version 10.0.19042.867]
(c) Корпорация Майкрософт (Microsoft Corporation), 2020. Все права защищены.
C:\Users\usr\Desktop\test>C:\Oracle\utPLSQL-cli\bin\utplsql.bat run stat_adm/stat_adm@dev ^
Продолжить? -d ^
Продолжить? -p="STAT_INT_TESTS:ods" ^
Продолжить? -include="STAT_INT.SA_METRIC_PKG" ^
Продолжить? -f=UT_COVERAGE_HTML_REPORTER -o=coverage1.html
Picked up JAVA_TOOL_OPTIONS: -Duser.language=en
2021-03-30 11:46:45 [main] INFO org.utplsql.cli.RunAction - ################# utPLSQL cli #################
# #
# utPLSQL-cli 3.1.8-SNAPSHOT.local #
# utPLSQL-java-api 3.1.8.546 #
# Java-Version: 1.8.0_271 #
# ORACLE_HOME: null #
# NLS_LANG: AMERICAN_AMERICA.WE8ISO8859P1 #
# #
# Thanks for testing! #
# #
###############################################
2021-03-30 11:46:45 [main] INFO org.utplsql.cli.RunAction -
2021-03-30 11:46:45 [main] DEBUG o.u.c.d.TestedDataSourceProvider - NLS settings: BEGIN
EXECUTE IMMEDIATE q'[ALTER SESSION SET NLS_LANGUAGE='AMERICAN']';
EXECUTE IMMEDIATE q'[ALTER SESSION SET NLS_TERRITORY='AMERICA']';
END;
2021-03-30 11:46:47 [main] INFO o.u.c.d.TestedDataSourceProvider - Use connection string jdbc:oracle:oci8:****/****@dev
2021-03-30 11:46:50 [main] INFO org.utplsql.cli.RunAction - Successfully connected to database. UtPLSQL core: v3.1.9.3268
2021-03-30 11:46:51 [main] INFO org.utplsql.cli.RunAction - Oracle-Version: 19.0.0.0.0
2021-03-30 11:47:10 [main] DEBUG org.utplsql.api.reporter.Reporter - Database-reporter initialized, Type: UT_COVERAGE_HTML_REPORTER, ID: BEBE0B2113E723F6E053C0C50F0AF318
2021-03-30 11:47:13 [pool-1-thread-1] INFO org.utplsql.cli.RunTestRunnerTask - Running tests now.
2021-03-30 11:47:13 [pool-1-thread-1] INFO org.utplsql.cli.RunTestRunnerTask - --------------------------------------
2021-03-30 11:47:13 [pool-1-thread-1] INFO org.utplsql.api.TestRunner - TestRunner initialized
2021-03-30 11:47:13 [pool-1-thread-1] INFO org.utplsql.api.TestRunner - Running on utPLSQL v3.1.9.3268
2021-03-30 11:47:13 [pool-1-thread-1] INFO org.utplsql.api.TestRunner - Initializing reporters
2021-03-30 11:47:15 [pool-1-thread-1] INFO org.utplsql.api.TestRunner - Running tests
2021-03-30 11:48:20 [main] INFO org.utplsql.cli.RunAction - --------------------------------------
2021-03-30 11:48:20 [main] INFO org.utplsql.cli.RunAction - All tests done.
C:\Users\Roman.Shiryaev\Desktop\test>
And when it comes to mapping to source files occasionally it fails after 4 unsuccessfull tries:
When I catch Detected Oracle driver stuck during Statement initialization error I don't see in v$sql any test related stuff (I mean calls to my test packages and tested packages as well). But after getting the error above I still see that new sql statements have its last_active_time refreshed as it is executing even after this error occurs. I'm not fluent in Java but I think maybe cli somehow detaches from db session and the session keeps on going and executing stuff (but strangely without any test calls).
In case of the first run above (I mean the one without file mapping that succeeds) I see the whole bunch of my queries and test calls. Here's a query I use for it:
select d.last_active_time, d.sql_id, d.sql_text, d.module, s.owner, s.object_name, d.program_line#
from v$sql d
left join dba_objects s on d.program_id = s.object_id
where d.module in ('utPLSQL', 'java.exe') -- I found just these modules that are used by utplsql-cli
and d.last_active_time > to_date('30.03.2021 09:20:00', 'DD.MM.YYYY HH24:MI:SS') -- I catch exact time after which I started utplsql-cli
order by 1 desc;
Hi!
I will put my outcomes about
Detected Oracle driver stuck during Statement initializationerror. When running tests without file mapping it runs ok. See:And when it comes to mapping to source files occasionally it fails after 4 unsuccessfull tries:
When I catch
Detected Oracle driver stuck during Statement initializationerror I don't see inv$sqlany test related stuff (I mean calls to my test packages and tested packages as well). But after getting the error above I still see that new sql statements have itslast_active_timerefreshed as it is executing even after this error occurs. I'm not fluent in Java but I think maybeclisomehow detaches from db session and the session keeps on going and executing stuff (but strangely without any test calls).In case of the first run above (I mean the one without file mapping that succeeds) I see the whole bunch of my queries and test calls. Here's a query I use for it:
Here's link with results for the query above in case of "bad" run (with mapping to source files): https://docs.google.com/spreadsheets/d/1AkUbTCBCopTCABeNM_9alzgKIPZyL7WC-dgp7YNH3Bc/edit?usp=sharing
Feel free to ask any questions or offer other test-cases. Let's help our beloved
utPLSQLframework to live long!