|
| 1 | +--- |
| 2 | +name: Bug report |
| 3 | +about: Create a report to help us improve |
| 4 | +title: '' |
| 5 | +labels: '' |
| 6 | +assignees: '' |
| 7 | + |
| 8 | +--- |
| 9 | + |
| 10 | +**Describe the bug** |
| 11 | +A clear and concise description of what the bug is. |
| 12 | + |
| 13 | +**Provide version info** |
| 14 | +Information about utPLSQL and Database version, |
| 15 | +```sql |
| 16 | +set serveroutput on |
| 17 | +declare |
| 18 | + l_version varchar2(255); |
| 19 | + l_compatibility varchar2(255); |
| 20 | +begin |
| 21 | + dbms_utility.db_version( l_version, l_compatibility ); |
| 22 | + dbms_output.put_line( l_version ); |
| 23 | + dbms_output.put_line( l_compatibility ); |
| 24 | +end; |
| 25 | +/ |
| 26 | +select substr(ut.version(),1,60) as ut_version from dual; |
| 27 | +select * from v$version; |
| 28 | +select * from nls_session_parameters; |
| 29 | +select substr(dbms_utility.port_string,1,60) as port_string from dual; |
| 30 | +``` |
| 31 | + |
| 32 | +**Information about client software** |
| 33 | +What client was used to run utPLSQL tests? Was it from TOAD, SQLDeveloper, SQLPlus, PLSQL Developer etc... |
| 34 | + |
| 35 | +**To Reproduce** |
| 36 | +Steps to reproduce the behavior: |
| 37 | +1. Go to '...' |
| 38 | +2. Click on '....' |
| 39 | +3. Scroll down to '....' |
| 40 | +4. See error |
| 41 | + |
| 42 | +**Expected behavior** |
| 43 | +A clear and concise description of what you expected to happen. |
| 44 | + |
| 45 | +**Example code** |
| 46 | +If applicable, add sample code to help explain your problem. |
| 47 | +Please avoid putting your company private/protected code in an issue, as it might violate your company's privacy and security policies. |
| 48 | + |
| 49 | +**Additional context** |
| 50 | +Add any other context about the problem here. |
0 commit comments