Skip to Main Content
Forums

ODP.NET

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Connection String. Idle Timeout, Command Timeout,

dotnetuserJan 20 2020 — edited Jan 20 2020

Hi!

Let's compare oracle and npgsql settings

See https://www.npgsql.org/doc/connection-string-parameters.html

1.

Connection Lifetime vs Connection Idle Lifetime

Connection Lifetime (oracle)

Maximum life time (in seconds) of the connection.

Connection Idle Lifetime (npgsql)
The time (in seconds) to wait before closing idle connections in the pool if the count of all connections exceeds Minimum Pool Size. Since 3.1 only.

In the case of npgsql, it is clear what and why.
There is a similar parameter in oracle, but it doesn’t work like that, you need a game with the pool regulator setting in order to add a similar result.

2. Command Timeout

In oracle, there is no such parameter in the connection string, only the class has it.
BUT, if you look at the library code, then it’s clear that this setting creates a timer that dies after a certain step of command execution and there’s little sense in it.

Comments

thatJeffSmith-Oracle
I understand what you want, however I don't think we have an answer that will give you what you want.

PL/SQL blocks aren't SQL - you're not going to get a resultset back like what if you had run a query in SQL*Plus or SQL Developer.

HOWEVER, if you have your program return the resultset as a REFCURSOR - SQL Developer will 'catch' that output and place it in a 'grid.'

You're other option is to output the format to file or to the output buffer however which way you want - but that's code you're going to have to write yourself.

Here's an example of what REFCURSOR output looks like in SQL Developer

http://www.thatjeffsmith.com/archive/2011/12/sql-developer-tip-viewing-refcursor-output/
unknown-7404
Welcome to the forum!

Whenever you post provide your full sql developer version.
>
But output via PL/SQL is usually done via dbms_output.
>
No - it isn't.

The DBMS_OUTPUT package should NOT be used at all in production code. You should only enable and use it very sparingly and only then for debugging purposes when developing and testing your code.

A line like this: 
    dbms_output.put_line(i || ' ' || i*i);
does nothing more than put text into a buffer in Oracle and uses expensive PGA memory to store it. There is a small default limit on the size of that buffer and you run the risk of an exception if you fill it up.

The client software (sql*plus, sql developer) has to actually access that buffer to get the text or it will NEVER get displayed. And it normally only gets displayed AFTER the completion of the code, not during the execution.

If you are using DBMS_OUTPUT as a general-purpose 'display' mechanism then you are misusing it and should find another alternative.
>
How to get the resulting table not shown in the "dbms output" window, but in the "query result" window?
>
There is no 'table' and there is no 'query result'. If you want a query result put the results into a table or use a REF CURSOR to return them.
thatJeffSmith-Oracle
No - it isn't.
Good catch. Although unfortunately too many folks do rely on this. And of course it's never in production. Sigh.
1 - 3

Post Details

Added on Jan 20 2020
#odp-net
1 comment
3,136 views