Re: SYSDATE problem - Oracle - Solaris

bunky wrote:
>
> Background:
> Dev database - Solaris 2.x, Oracle 8.1.7.1
> Test database - Solaris 8.x, Oracle 8.1.7.1
>
> Issue: I have a stored procedure which contains the following
> assignment:
> v_date := SYSDATE;
>
> This procedure runs fine on our Dev database, but when we tried to run
> it on the Test database (note environment differences above) it makes
> the stored procedure throw off errors and eventually I receive the
> generic ORA-03113 end-of-file communication channel error.
>
> On the Test database, I changed this SP code to perform a more
> traditional assignment of the date:
> Select SYSDATE into v_date from dual;
>
> This works fine on the Test database.
>
> Any ideas as to why the first assignment of SYSDATE is causing errors
> on my Test database?

817 was the first release for a while I think to start getting sysdate via a direct call (and thus avoid the overhead of an implicit 'select from dual'). Presumably 8171 had some probs with the transition - I can vouch for the fact that 8174 solaris works fine in this regard

hth
connor

-- 
Connor McDonald
Co-author: "Mastering Oracle PL/SQL - Practical Solutions"
ISBN: 1590592174

web: http://www.oracledba.co.uk
web: http://www.oaktable.net
email: connor_mcdonald_at_yahoo.com

Coming Soon! "Oracle Insight - Tales of the OakTable"

"GIVE a man a fish and he will eat for a day. But TEACH him how to fish,
and...he will sit in a boat and drink beer all day"

------------------------------------------------------------