This is a discussion on using "call" for packaged procedure? within the Oracle Miscellaneous forums, part of the Oracle Database category; --> After moving a procedure into a package I discovered I can no longer use "call" to invoke the procedure. ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| After moving a procedure into a package I discovered I can no longer use "call" to invoke the procedure. Can someone explain why this is? Many TIA! old code: call p4_add(:typeid,:reposid,:depotFile,:rev,:tmstamp) new code (broken): call p4.add(:typeid,:reposid,:depotFile,:rev,:tmstamp) ORA-01747: invalid user.table.column,table.column, or column specification new code (works): begin p4asset.add(:typename,:repos,:depotFile,:rev); end -- Mark Harrison Pixar Animation Studios |
| |||
| mh@pixar.com wrote: > After moving a procedure into a package I discovered I can > no longer use "call" to invoke the procedure. > > Can someone explain why this is? > Many TIA! > > > old code: > > call p4_add(:typeid,:reposid,:depotFile,:rev,:tmstamp) > > new code (broken): > > call p4.add(:typeid,:reposid,:depotFile,:rev,:tmstamp) > > ORA-01747: invalid user.table.column,table.column, > or column specification > > new code (works): > > begin p4asset.add(:typename,:repos,:depotFile,:rev); end Are there typos in your posting? Because if not, then the solution would be obvious: CALL p4asset.add(:typename,:repos,:depotFile,:rev); Yours, Laurenz Albe |
| ||||
| On Aug 29, 2:35*am, Laurenz Albe <inv...@spam.to.invalid> wrote: > m...@pixar.com wrote: > > After *moving a procedure into a package I discovered I can > > no longer use "call" to invoke the procedure. > > > Can someone explain why this is? > > Many TIA! > > > old code: > > > * *call p4_add(:typeid,:reposid,:depotFile,:rev,:tmstamp) > > > new code (broken): > > > * *call p4.add(:typeid,:reposid,:depotFile,:rev,:tmstamp) > > > * *ORA-01747: invalid user.table.column,table.column, > > * * * * * * * or column specification > > > new code (works): > > > * *begin p4asset.add(:typename,:repos,:depotFile,:rev); end > > Are there typos in your posting? > > Because if not, then the solution would be obvious: > > CALL p4asset.add(:typename,:repos,:depotFile,:rev); > > Yours, > Laurenz Albe- Hide quoted text - > > - Show quoted text - Mark, it took me a couple of readings but it does appear that Laurenz is pointing out that your spelled the package name different in your example of what failed and what worked. Based on this the error message was telling you the truth. Be there, done that. LOL. It is time for the weekend! HTH -- Mark D Powell -- |
| Thread Tools | |
| Display Modes | |
|
|
| ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| processing flow for <map:call resource=""/> (was: <map:serializetype="{1}"/>) | Joerg Heinicke | Apache Users | 0 | 08-15-2008 09:02 PM |
| "CREATE TABLESPACE" cannot run within a Stored Procedure - "Inside a transaction bloc" | Abraham, Danny | pgsql Admins | 0 | 04-10-2008 08:47 AM |
| Store procedure -------------- !!!!!!!!!!!!!! URGENTE """"""""""""""" | =?iso-8859-1?Q?Adelson_-_Inform=E1tica?= | Pgsql General | 1 | 04-08-2008 08:44 PM |
| Why "execute count" larger than "user call" in v$sysstat. | anysql@gmail.com | Oracle Database | 1 | 02-24-2008 02:23 PM |
| amavisd "Can't call method "lookup_re" on" | bulba008 | comp.unix.bsd.openbsd.misc | 0 | 02-16-2008 06:53 AM |