RE: HOW TO EXECUTE DELETE RECORD.

It’s probably differences in NLS_DATE_FORMAT between the SQL*Plus session and the TOAD session. That wouldn’t be a problem except for, as noted in my earlier email, you are passing a string into a date parameter, and depending on Oracle to convert the datatype for you. So modify your call to your procedure to do explicit conversion on the date, run that version of the call in TOAD, and my bet is you won’t have the problem anymore.

 

Regards,

 

Mike McAllister 

Principal Systems Engineer

Decypher

DSN:                      487-3751

Commercial:       (210) 652-3751

Cell:                       (512) 423-7447

Email:                    [email protected]

 

From: [email protected] [mailto:[email protected]] On Behalf Of Marvin Rios
Sent: Friday, March 09, 2012 12:28 PM
To: [email protected]
Subject: Re: [toad] HOW TO EXECUTE DELETE RECORD. [1 Attachment]

 

  

[Attachment(s) from Marvin Rios included below] 

Yes in Toad send these errror  ORA-00904: "HOR": identificador no válido

 

 

Becouse?

 

Thank you

 

  _____  

From: "Simoneau, Roger" <[email protected]>
To: "'[email protected]'" <[email protected]> 
Sent: Friday, March 9, 2012 11:33 AM
Subject: RE: [toad] HOW TO EXECUTE DELETE RECORD.

 

  

>> C:\>sqlplus

…

>> Procedimiento PL/SQL terminado correctamente.

 

It looks like it worked properly.  As Michael indicated, a best practice is to explicitly identify your date conversion… but if it had failed on that, it would be a different error then originally identified.

 

Marvin: does the proper execution of the procedure mean you can no longer duplicate the issue?  Or did you change the variable name hor to something else and it worked?

 

Or is there something we’re missing that you haven’t quite told us like: It works in sqlplus but gives the error in a Toad editor?

 

Roger S.

 

  _____  

This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply.