Re: Yesterday I had a perfectly compiling stored procedure ....

Hi,

You defined ss_cur two times. Maybe you wanted

ss_rec ss_cur%ROWTYPE;

instead of

ss_cur ss_rec%ROWTYPE;

Andrew Protasov

In article <7a28kc$v0a$1_at_nnrp1.dejanews.com>,   m_popov_at_hotmail.com wrote:
> Hi
> Yesterday I had a perfectly compiling stored procedure that contained
> 2 cursor definitions.
> Then I added a third cursor definition with totally different
> variables. Now I am getting the following errors. Actually its giving
> me like 100 errors. It compiles perfectly If I comment out the new
> cursor definition.
>
> 46/2 PLS-00305: previous use of 'SS_CUR' conflicts with this use
> 46/2 PL/SQL: Item ignored
> 56/9 PLS-00201: identifier 'SS_REC' must be declared
> 56/9 PL/SQL: Item ignored
>
> There is no other defintion for SS_CUR and no duplicate variables.
> If any of you guys know what's happening , please let me know. The
> error manual is not of much help. This is frustrating...
> Thanks
>
> Mike.
>
> The actual definition of the third cursor is as follows :
>
> cursor ss_cur is
> select sap_sequence_number , shipment_number ,
> center_code , item_number_code ,
> sap_destination_type_indicator ,
> total_volume from
> sap_shipments_at_dmscprod
> where (sap_sequence_number between
> pkg_begin_seq_num and pkg_end_seq_num)
> and sap_destination_type_indicator = 'A'
> order by center_code;
> ss_cur ss_rec%ROWTYPE;
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Sun Feb 14 1999 - 14:26:31 CST