Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     Error in calling an oracle procedure

Read-Only Read-Only Topic
Go
Search
Notify
Tools
Error in calling an oracle procedure
 Login/Join
 
<Adesh>
posted
Hi i am calling an oracle packeged procedure
this is how i am calling it
ENGINE SQLORA SET DEFAULT_CONNECTION (Connector Name)
SQL SQLORA
EX Package_Name.Procedure_Name;

TABLE FILE SQLOUT
PRINT
*
END

when i do this i am getting the following error message.

"(FOC1400) SQLCODE IS 6564 (HEX: 000019A4)
: ORA-06564: object does not exist
L (FOC1405) SQL PREPARE ERROR"


But, when i call the same procedure with user name (EX User_Name.Package_Name.Procedure_Name; ) it's working fine.

Can anyone explain why the user name is required?

Note: Stand alone procedure works fine without user name.

Thanks
Adesh
 
Report This Post
TexasStingray
Master
posted Hide Post
Just guessing but it could be a couple of reasons

1. the ID used to connect to Oracle not the same as the user you enter in the SQL procedure.

2. There are more then one object with the same name.




Scott

 
Posts: 865 | Registered: May 24, 2004Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     Error in calling an oracle procedure

Copyright © 1996-2020 Information Builders