| Migartion from Oracle 7 to 8 causes errors with to_char [message #20557] |
Tue, 04 June 2002 11:18  |
Nina
Messages: 113
Registered: March 2000
|
Senior Member |
|
|
Please, help!!!!!!
We have a crucial production problem, whereby some programs fail to insert dates that are in to_char format. For example...
to_char(&last_paid_date+1,'DD-MON-YYYY')
OR
anything with to_char...
The programs worked great under Oracle 7, inserting the dates that have to_char format. However, under the current version of Oracle (8.1.6) NULLS get inserted instead of dates.
Is anyone aware of any date realted bugs in Orcale 8i?
best regards,
|
|
|
|
| Re: Migartion from Oracle 7 to 8 causes errors with to_char [message #20558 is a reply to message #20557] |
Tue, 04 June 2002 12:31  |
andrew again
Messages: 2577
Registered: March 2000
|
Senior Member |
|
|
The & is probably the place to look.
It seems you are running a SQL script through sqlplus?
If so - do you have an ACCEPT to prompt for last_paid_date? Is the script still prompting for user input in 8.1.6?
In sqlplus - it should look like this:
SQL> show scan
scan ON
SQL> show define
define "&" (hex 26)
SQL>
If not - check in glogin.sql for the defaults which are being set. You can override them with your own settings in login.sql (create in your default directory for sqlplus) or in the top of your script.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
