Re: HOW TO EXECUTE DELETE RECORD. [1 Attachment]
Marvin Rios <[email protected]>
| Newsgroups | gmane.comp.db.oracle.toad.free |
|---|---|
| Message-ID | <[email protected]> |
Microsoft Windows [Versión 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\soporte>cd..
C:\Documents and Settings>cd..
C:\>sqlplus
SQL*Plus: Release 11.1.0.6.0 - Production on Vie Mar 9 08:17:18 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Introduzca el nombre de usuario: SMART3G
Introduzca la contrase±a:
Conectado a:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> exec AGREGA_ESTAD_PKG.sp_hua_algorithm_hor ('07-NOV-11',1);
Procedimiento PL/SQL terminado correctamente.
________________________________
From: "Simoneau, Roger" <[email protected]>
To: "'[email protected]'" <[email protected]>
Sent: Thursday, March 8, 2012 11:47 AM
Subject: RE: [toad] HOW TO EXECUTE DELETE RECORD.
Hey Marvin;
>> ORA-00904: "HOR": identificador no válido
Interesting puzzle. The error message would indicate the column HOR is invalid. The error seems quite misleading given HOR is a parameter for the procedure.
I created a table called hua_algorithm_hor using the columns identified and used it as both tables in the query, the procedure compiles and executes cleanly.
The tables listed are:
Smart3g.hua_algorithm_hor
Hua_algorithm_hor (if different from the schema specified above)
Hua_algorithm_min
Perhaps describing the tables might give some clue as to what the issue is.
In the alternative, a test might be to change the input parameter hor to something else that couldn’t possibly normally exist like zzzzxxyyyy and see if the error repeats. Perhaps hor is some kind of reserved word.
It might be helpful to also identify the exact command you are running that generates the error.
My test was a simple: exec sp_hua_algorithm_hor(sysdate, 1);
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.