Thank you friends,
But we finally figured out. Actually the OUT parameter is procedure is
useless as Shailesh pointed out , there is no variable to put the OUT value
in auto-execute.
So this is what we did. Kept the OUT parameter ( we could took it out but
developer insisted to keep it as they
Dear List,
I have a package which I want to execute using dba_jobs.
Within that package I run procedure which has one OUT parameter ( errno)
When I submit the job
declare
jobno number;
errno number;
begin
dbms_job.submit(jobno,'l_load_weekly_aps.p_load_ocn(:errno);',sysda
te,'sysdate');
Sandesh,
You are not handling the out parameter. Since you have an out parameter,
there should be some variable to recieve the value of same. In this
situation when it will be auto-executed it cannot return the output and it
will error out.
Shailesh
-Original Message-
Sent: Monday,
I believe that you could try and change the settings in the sqlnet.ora file
on the server side, SQLNET EXPIRE_TIME = 0. This may help:)
KK
-Original Message-
[EMAIL PROTECTED]
Sent: Monday, July 16, 2001 2:50 AM
To: Multiple recipients of list ORACLE-L
We have a network that have
Beware that SQLNET.EXPIRE_TIME=0 doesn't activate this
feature. Is the same that set it with huge value.
Regards.
--- Kevin Kostyszyn [EMAIL PROTECTED] wrote:
I believe that you could try and change the settings
in the sqlnet.ora file
on the server side, SQLNET EXPIRE_TIME = 0. This
may
Title: RE: A lazy connection!
Are any profiles implemented? I believe that's the error I get when a profile has kicked me out.
Lisa Koivu
Data Bored Administrator
Ft. Lauderdale, FL, USA
-Original Message-
From: Kevin Kostyszyn [SMTP:[EMAIL PROTECTED]]
Sent: Monday, July 16
There is not any profile defined, except default profile. There is a
problem only for the computers that has an acces with leased line. There is
other computers that has an acces using a local network and everything is
OK here.
-Original Message-
To: '[EMAIL PROTECTED]' [EMAIL PROTECTED];
My first suspicion would be a firewall; check with your network people. I
would set the sqlnet.expire time to ten minutes to keep the firewall from
kicking idle sql*net connections.
--Michael
-Original Message-
[mailto:[EMAIL PROTECTED]]
Sent: Monday, July 16, 2001 11:12 AM
To:
I meant that if you want to use expire_time feature,
you'll need to set it with a value greater than 0.
Remember that the value is in minutes. F.e.:
SQLNET.EXPIRE_TIME=20 .means that every twenty
minute SQL*Net or Net8 polls each connection
SQLNET.EXPIRE_TIME=0.means that SQL*NET or
My first about this was about the SQLNET.EXPIRE_TIME
and I didn't look the first mail. And referring to the
question in that mail: there are two ways to forbid
the connection through TCP: protocol.ora file or
Connection Manager.
Regards.
--- Jenkins, Michael [EMAIL PROTECTED]
wrote:
My first
I was under the impression that setting it to zero meant that the
connnections would wait indefinately. Like when I was receiving end of
file on communication errors setting it to 0 was suggested.
KK
-Original Message-
Trassens
Sent: Monday, July 16, 2001 11:46 AM
To: Multiple
A setting of zero tells the server to never poll the connections and verify
that they are active. This allows firewalls and various other middlemen to
terminate inactive connections based on the fact that there is no sql*net
traffic coming through the network. By setting it to anything other
12 matches
Mail list logo
