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?

I suspect that the "default" date format is different between the 2 DBs. I suspect that "v_date" is of datatype VARCHAR2 and not of type DATE; which is forcing an implicit datatype conversion (which is failing). Received on Sat Jun 12 2004 - 09:03:15 CDT