I did some testing and cannot reproduce on Oracle 12.

var x varchar2;
begin
  :x := to_char(sysdate,'yyyy-mm-dd hh24.mi.ss');
  dbms_output.put_line('Start date is:'||:x);
end;
/

begin
  ut.run(ut_coverage_sonar_reporter());
end;
/

begin
  ut.run(ut_coverage_sonar_reporter());
end;
/

select case when count(1) = 2 then 'OK' else 'ERROR' end||' expected 2, got '||count(1) as status
  from plsql_profiler_runs where run_date >= to_date(:x,'yyyy-mm-dd hh24.mi.ss');

The above, gives following results:

Start date is:2017-11-15 07.56.33


PL/SQL procedure successfully completed.

<coverage version="1">
</coverage>


PL/SQL procedure successfully completed.

<coverage version="1">
</coverage>


PL/SQL procedure successfully completed.

OK expected 2, got 2

I got this issue from oracle 11.2. Maybe that is the reason.

Can you tell us which version of utPLSQL you use?

utPLSQL - Version v3.0.2.938

It is v3.0.2

• Can you check and see if reset package state helps
• can you check if executing dbms_profiler.stop helps?
• check if the same issue occurs when you run the same commands from SQLPLUS

reset package state helps , but it somehow repressed the dbms_output
dbms_profiler.stop_profiler doesn't help
Seems issue when running same commands from sqlplus

@email2ying
I've checked again on 11.2.0.2 XE using v3.0.2
There was an undocumented bug in coverage reporter. It was already fixed in v3.0.3 as part of #417.

Yesterday I was checking using develop version of the framework - that is why I could not see the issue occur.

Once you get v3.0.3 or above installed -> it will work fine.