Handling no_Data_found and handling the cursor context not found exceptions

Question

hi all,
when the value is not there in table, we will get the no_data_found exception.
im sending the sample procedure.
check that one.
create or replace procedure registration.P_GetPatientDetails(in_UHID in Patient.Uhid%Type,
ocursor_Component1 OUT SYS_REFCURSOR,
---ocursor_Component2 OUT SYS_REFCURSOR,
ocursor_Component3 OUT SYS_REFCURSOR,
ocursor_Component4 OUT SYS_REFCURSOR
AS
in_RegistrationID varchar2(50);
ln_genderLovID NUMBER(10);
ln_rhfactorLovID NUMBER(10);
BEGIN
SELECT RegistrationId
into in_RegistrationID
from Patient
where (Upper(UHID) = Upper(in_UHID)) ;
/* COMMIT;*/
/*dbms_output.put_line(in_RegistrationID);*/
OPEN ocursor_Component1 FOR
SELECT RegistrationID,PreRegistrationNo,EmergencyNo,UHID
FROM patient p LEFT OUTER JOIN EHIS.Titlemaster TM ON p.title = tm.titlecode LEFT OUTER JOIN EHIS.SuffixMaster SM on p.sufix = SM.SUFFIXCODE LEFT OUTER JOIN EHIS.Maritalstatusmaster MSM ON MSM.MARITALSTATUSID = p.maritalstatus LEFT OUTER JOIN EHIS.Bloodgroupmaster BGM ON BGM.BLOODGROUPID = p.bloodgroup LEFT OUTER JOIN EHIS.LovDetail LD ON(LD.LOVDETAILID = p.gender AND LD.LOVID = ln_genderLovID) LEFT OUTER JOIN EHIS.LovDetail rf ON(rf.LOVDETAILID = p.rhfactor AND rf.LOVID = ln_rhfactorLovID)
WHERE RegistrationID = in_RegistrationID AND p.Status = 1 ;
OPEN ocursor_Component3 FOR
SELECT RegistrationID,ResidenceNumber,MobileNumber,PrimaryEmail
FROM AddressMaster
WHERE UPPER(RegistrationID) = UPPER(in_RegistrationID) AND Status = 1 AND
AddressTypeID =
(SELECT AddressTypeID
FROM AddressTypeMaster
WHERE AddressTypeName = 'PermanentAddress');
/* COMMIT;*/
OPEN ocursor_Component4 FOR
SELECT ResidenceNumber, MobileNumber,EmergencyNumber,PrimaryEmail
FROM AddressMaster am LEFT OUTER JOIN EHIS.Countrymaster CM ON CM.COUNTRYID = am.country LEFT OUTER JOIN EHIS.Statemaster SM ON SM.STATEID = am.state LEFT OUTER JOIN EHIS.Districtmaster DM ON DM.DISTRICTID = am.district LEFT OUTER JOIN EHIS.Citymaster CM1 ON CM1.CITYID = am.city
WHERE UPPER(RegistrationID) = UPPER(in_RegistrationID) AND Status = 1 AND
AddressTypeID =
(SELECT AddressTypeID
FROM AddressTypeMaster
WHERE AddressTypeName = 'CurrentAddress');
/* COMMIT;*/
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE(TO_CHAR(SQLCODE) || SQLERRM);
END;
if the data is not there for teh given uhid,
we are displaying the err msg in exception block
but from .net environment ,
they will define the cursors as out params.
if they wont get the data,
in .net environment, the exception is raised.
how to handle these situations.

Answer 1

Implicit cursors are prone to both the NO_DATA_FOUND and TOO_MANY_ROWS errors. They MUST return precisely one row or you get to do extra coding in the form of exception handlers. Using explicit cursors (declared in the DECLARE SECTION) will avoid both errors, though they have their own considerations. When an explict cursor doesn't find something it doens't put NULL into the destination variable(s); it leaves them alone so its a good idea to null out variables and records before fetching into them.