Home » SQL & PL/SQL » SQL & PL/SQL » Calling external interface procedure (oracle 10g)
Calling external interface procedure [message #363078] Fri, 05 December 2008 01:00 Go to next message
deepshikhahcl
Messages: 14
Registered: October 2008
Junior Member
Hi I am facing one issue.
I am calling on Stored procedure which exists in some extrnal interface called (NPAD). I have been asked to handle one situation as When the NPAD is down i have to show the error message that "NPAD is down".how to do this and where do i write the code.

Urgent
Re: Calling external interface procedure [message #363094 is a reply to message #363078] Fri, 05 December 2008 01:37 Go to previous messageGo to next message
Michel Cadot
Messages: 64138
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
If NPAD is an external interface, this question has no relation with Oracle or PL/SQL.

You should post this in a forum that talks about NPAD.
Even more if it is urgent as here we don't handle urgencies.

Regards
Michel
Re: Calling external interface procedure [message #363121 is a reply to message #363078] Fri, 05 December 2008 02:46 Go to previous messageGo to next message
JRowbottom
Messages: 5933
Registered: June 2006
Location: Sunny North Yorkshire, ho...
Senior Member
So, is NPAD some other database that you access over a DB link. or is it an application external to the database.

Can you show us the code you are currently using to call it?
Re: Calling external interface procedure [message #363220 is a reply to message #363121] Fri, 05 December 2008 06:55 Go to previous messageGo to next message
deepshikhahcl
Messages: 14
Registered: October 2008
Junior Member
IF p_seed_count > 0 THEN
--generate FROM seeds address information using dpid list
tt_from_dpid_list_seed :=
vas_npad_mpt_interface_pkg.vas_address_lines_fnc(tt_from_dpid_list_seed, v_upper_case_ind, v_error_code, v_sqlerrm );

Above is a call to the NPAD procedure.
vas_npad_mpt_interface_pkg is a package and vas_address_lines_fnc is a function.
I am calling it from my stored procedure
Re: Calling external interface procedure [message #363221 is a reply to message #363220] Fri, 05 December 2008 06:59 Go to previous messageGo to next message
Michel Cadot
Messages: 64138
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Ok, and then? Go on in your explainations.

Regards
Michel
Re: Calling external interface procedure [message #363225 is a reply to message #363220] Fri, 05 December 2008 07:29 Go to previous message
JRowbottom
Messages: 5933
Registered: June 2006
Location: Sunny North Yorkshire, ho...
Senior Member
Ok, so you've shown us the code that you use to call the code that calls NPAD.

HOw about some details about how you actually call NPAD?

This is relevant - If NPAD is something who's absence will cause the calling package to become invalid, then the only way to catch that would be to put some dynamic sql (ie sql that is evaluated at execution, rather than a compile time) into the code.

In NPAd's absence does not invlidate the code, then you should be able to handle things by wrapping the call tio the NPAD access package in a BEGIN...EXCEPTION..END block - or better, adding exception handling to the package that interfaces with NPAD.

This would all be a lot easier to describe if you could be bothered to explain what NPAD actually is, and how you call it.
Previous Topic: DBMS_job/scheduler
Next Topic: Exception handling
Goto Forum:
  


Current Time: Thu Dec 08 06:33:55 CST 2016

Total time taken to generate the page: 0.11013 seconds