Stored Procedure in NAtive SQL

Hello All,
Where to check the definition of the following stored procedure in NAtive SQL.
EXEC SQL.
    EXECUTE PROCEDURE "APS_PEGID_GET_IO" (
                         IN :LS_GEN_COM_PARAMS,
                         OUT :LV_RC,
                         IN :ET_RC,
                         IN :IT_PEGAREA,
                         IN :IT_PEGID_DESC_CHAR,
                         IN :IT_ORDER_TYPES,
                         IN :IT_ORDER_STATUS,
                         IN :IT_CATEGORY,
                         IN :IT_CHARACT_REQ_OUTNODE,
                         IN :IT_CHARACT_VAL_INPNODE,
                         IN :IT_SUPPLY_AREA,
                         IN :IT_EXT_FIXED,
                         IN :IT_TOPORDER_EXCLUDES,
                         IN :IV_IONODE_PEG_SEL,
                         IN :IV_START_TIME,
                         IN :IV_END_TIME,
                         IN :IT_ORDER_REQTIME,
                         IN :LS_GETIO_OPTIONS,
                         IN :IS_EXCLUDE_FIELDS,
                         IN :ET_POSITIONS,
                         IN :ET_IONODES,
                         IN :ET_IONODES_CONF,
                         IN :ET_CONTI_IO,
                         IN :ET_CHARACT_REQ_INPNODE,
                         IN :ET_CHARACT_VAL_OUTNODE,
                         IN :ET_FIXPEG)
ENDEXEC.
kindly help
its urgent.
thank u in advance.
Regards,
Pranali

Hi Pranali,
Please tell me too if you have resolved the issue.
Thanks & Regards,
Manali

Similar Messages

Running a Stored Procedure in Oqacle SQL Developer

Hi All,
Could anybody elaborate on the procedure to execute a Stored Procedure in Oracle SQL Developer. I feel we need to configure the output for the DBMS_OUTPUT
Cheers,
Bell

on the procedure to execute a Stored Procedure in Oracle SQL Developer.Select the procedure or package spec in the Connections panel. Right click with the mouse. This will bring up a panel with an anonymous block to run the code and property sheets to populate the parameters, etc.
Cheers, APC

Creation of DB Adaptert for calling stored procedure in MS SQL server

Hi,
I need to create a DB adapter to call a stored procedure in MS SQL Server.
I have gone thru the thread MS SQL Server database connection
It mentions that we need to use a command line utility for generating the wsdl and xsd for calling stored procedures in MS SQL server. Please provide information where to find this utility and how to use it.
Any links to tutorials are welcome.
Thanks !!.
Silas.

Command line is required for stored procedures, if you are using the basic options you don't need to worry.
(1) Download MS SQL Server 2005 JDBC Driver from Microsoft Site. http://msdn.microsoft.com/en-us/data/aa937724.aspx
(2) The download is self extracting exe file. Extract this into Program Files on your machine. It should create folder as "Microsoft SQL Server 2005 JDBC Driver"
(3) In above mentioned folder search for sqljdbc.jar copy this file into JDeveloper\JDBC\lib folder.
(4) Open JDeveloper/jdev/bin/jdev.conf file add following entry.
AddJavaLibPath C:/Program files/Microsoft SQL Server 2000 Driver for JDBC/lib
While executing this step make sure that your JDeveloper is closed.
(5) On command prompt go to J Developer folder and execute following command
jdev -verbose
This will open JDeveloper.
(6) Now go to JDeveloper > Connections > Database Connections > New Database Connection
(7) Select Third Party JDBC
(8) Specify MS Sql Server User Name, password and Role.
(9) In connection page specify following
- Driver Class: com.microsoft.sqlserver.jdbc.SQLServerDriver
- For class path browse to C:/Program files/Microsoft SQL Server 2000 Driver for JDBC/lib folder, select sqljdbc.jar add it as library.
- Specify URL as following.
jdbc:sqlserver://SERVERNAME:1433;databaseName=MSSQLDBNAME;
(10) Go to Test page and test it.
cheers
James

Writing a stored procedure to import SQL Server table data into a Oracle table

Hello,
As a new DBA I have been tasked with writing a stored procedure to import SQL Server table data into an Oracle table. I have been given many suggestions on how to do it from SQL Server but I I just need to write a stored procedure to run it from the Oracle side. Suggestions/guidance on where to start would be greatly appreciated! Thank you!
I started to write it based on what I have but I know this is not correct :/
# Here is the select statement for the data source in SQL Server...
SELECT COMPANY
,CUSTOMER
,TRANS_TYPE
,INVOICE
,TRANS_DATE
,STATUS
,TRAN_AMT
,CREDIT_AMT
,APPLD_AMT
,ADJ_AMT
,TRANS_USER1
,PROCESS_LEVEL
,DESCRIPTION
,DUE_DATE
,OUR_DATE
,OUR_TIME
,PROCESS_FLAG
,ERROR_DESCRIPTION
FROM data_source_table_name
#It loads data into the table in Oracle....
Insert into oracle_destination_table_name (
COMPANY,
CUSTOMER,
TRANS_TYPE,
INVOICE,
TRANS_DATE,
STATUS,
TRANS_AMT,
CREDIT_AMT,
APPLD_AMT,
ADJ_AMT,
TRANS_USER1,
PROCESS_LEVEL,
DESCRIPTION,
DUE_DATE,
OUR_DATE,
OUR_TIME,
PROCESS_FLAG,
ERROR_DESCRIPTION)
END;

CREATE TABLE statements would have been better as MS-SQL and Oracle don't have the same data types.
OUR_DATE, OUR_TIME will (most likely) be ONE column in Oracle.
DATABASE LINK
Personally, I'd just load the data over a database link:
insert into oracle_destination_table_name ( <column list> )
select ... <transform data here>
from data_source_table@mssql_db_link
As far as creating the database link from Oracle to MS-SQL ... that is for somebody else to answer.
(most likely you'll need to use an ODBC driver)
EXTERNAL TABLE
If the data from MS-SQL is in a CSV file, just use and external table.
same concept:
insert into oracle_destination_table_name ( <column list> )
select ... <transform data here>
from data_source_external_table
MK

JDBC - CallableStatement - Error in Accessing Stored Procedure of MS SQL

Dear Friends,
The following is the code to access a stored procedure of MS SQL Server 7.0 sp4,
          try
               CallableStatement cstmt;
               ResultSet rst;
               cstmt = connection.prepareCall("{call backupdb[?,?]}");
               cstmt.setString("db_name","SBIREMITLIVE");
               cstmt.setString("path", "c:\testing.bak");
               cstmt.executeQuery();
               System.out.println("Stored Procedure called successfully");
          catch(SQLException se)
               System.out.println(se.toString());
when i execute this i am getting the error as " MS ODBC-MS SQL Server Syntax error or Access Violation "
What's the problem exactly ? anybody came across this issue..if so...kindly help me....
Here is my MS SQL Server stored procedure.....for reference
create procedure backupdb(@db_name varchar(40), @path varchar(100)) as
Backup database @db_name to disk = @path
Regards,
V.Prasanna

Dear DigitalDreamer,
Yes, as per your suggestion, it's working fine...thanks a lot...
here is the code...
               CallableStatement cstmt;
               ResultSet rst;
               cstmt = connection.prepareCall(" exec backupdb ?,? ");
               cstmt.setString(1,"SBIREMITLIVE");
               cstmt.setString(2, "c:\\testing.bak");
               cstmt.execute();
Regards,
V.Prasanna

Calling stored procedure from embedded sql

I'm trying to call a stored procedure from embedded sql. I'm following the examples located in
http://download.oracle.com/docs/cd/B19306_01/appdev.102/a96109/pco06pls.htm#i9641
I have the following section in my .pco file before precompiling.
exec sql execute
begin
docs.grant_access_to_all_categories(:p_sam_id);
end;
end-exec.
When running procob on the file with the above code I get the following error.
Error at line 225, column 13 in file pco\docs_stored_procedures.pco
exec sql execute
............1
PCB-S-00576, PLS-201: identifier 'DOCS.GRANT_ACCESS_TO_ALL_CATEGORIES' must be d
eclared
Error at line 225, column 13 in file pco\docs_stored_procedures.pco
exec sql execute
............1
PCB-S-00576, PLS-0: Statement ignored
Any ideas on what I am doing wrong on calling this stored procedure.

I get the same error when trying to precompile sample11.pco from the demo directory in the oracle client software.
Error at line 70, column 12 in file sample11.pco
EXEC SQL EXECUTE
...........1
PCB-S-00576, PLS-201: identifier 'EMP_DEMO_PKG.OPEN_CUR' must be declared
Error at line 70, column 12 in file sample11.pco
EXEC SQL EXECUTE
...........1
PCB-S-00576, PLS-0: Statement ignored

Turning a stored procedure or PL/SQL into a web (SOAP call)

what is the easiest way of turning a stored procedure or PL/SQL into a web service (soap call).
I need to have detailed way of doing it ...

Have a look at: http://www.oracle.com/technology/tech/webservices/htdocs/samples/dbwebservice/DBWebServices_PLSQL.html

How to invoke a stored procedure on MS Sql Server with Java?

I started writing Enterprise Java Beans and created an ODBC dsn with MS Sql Server 2000 which I can access using jdbc:odbc:mySqlDSN. This all works fine using Java Sql Statements. What kind of Java/Java Sql statement can I use to invoke a stored procedure on the Sql Server? Is it possible to use ADO/ADO command objects with Java? Is it possible to import/implement Mdac2.6 ActiveX data objects libary in Java?
Thanks

Thanks all for your replies. I will search the api for callable statements. I am curious though, the reply that suggests using a prepared statement - can I put the name of a stored procedure in a prepared statment or is this just suggestions an action query like Insert Into, Update, Delete? Like with ADO you can say
cmdObject.CommandType = adStoredProcedure
cmdObject.CommandText = "NameOfStoredProc"
cmdObject.ExecuteNonQuery()
Once I am calling/importing/implementing the proper libraries/interfaces in Java, can a prepared statement reference a stored procedure as above?
Thanks

Getting a DataReader by stored procedure vs. SQL statment (Performance)

Hallo DB-Experts,
I have encountered a performance problem regarding getting a DataReader by stored procedure versus a SQL statment
and I want to know if this is an known issue and how to tune it.
Getting a DataReader through a SQL statment is faster than with a stored procedure,
if the number of data rows are less than about 8000 datarows, although we are using an index.
The stored procedure ist only faster about 8000 datarows.
For the first 20 rows the different is between 50 abd 20 percent and between and 20 and 2000 rows it fall down to 10 percent.
Over 8000 rows the stored procedure is faster!
The time series table looks like:
CREATE TABLE TimeSeries
OBJECT_ID NUMBER(8) NOT NULL,
UNIVERSAL_TIME NUMBER(10) NOT NULL,
LOCAL_TIME DATE NOT NULL,
MOD_TIME NUMBER(10),
USERID NUMBER(10),
VALUE NUMBER NOT NULL,
FLAG NUMBER(2) DEFAULT 0 NOT NULL
The foreinkey is object_id and another index is for universal_time and mod_time
The stored procedure looks like:
PROCEDURE SELECTDATA_UT_MOD (pObjectID IN NUMBER,
pType IN VARCHAR2,
pTable IN VARCHAR2,
pFrom IN NUMBER,
pTo IN NUMBER,
IO_CURSOR OUT T_CURSOR)
IS
SQLString VARCHAR2(1024);
BEGIN
IF pOBJECTID <> 0 THEN
CASE
WHEN UPPER(pTYPE)='A' THEN
SQLString := 'SELECT UNIVERSAL_TIME, VALUE, FLAG, MOD_TIME FROM ' || pTABLE || ' WHERE OBJECT_ID = :t1 AND UNIVERSAL_TIME >= :t2 and UNIVERSAL_TIME < :t3 Order By UNIVERSAL_TIME, MOD_TIME DESC';
OPEN IO_CURSOR FOR
SQLString USING pOBJECTID,pFROM,pTO;
END IF;
END;
The SQL statment for the data reader looks like:
SELECT d.universal_time, d.VALUE, d.flag, 0 AS mod_time
FROM daten d
WHERE object_id = 18465
AND d.universal_time >= 3600
AND d.universal_time < 28803600
ORDER BY d.universal_time, mod_time DESC
Do you have any idea or tip why the sql statment for the first 8000 rows is faster than the stored procedure?
Many thanks in advance and
Best regards
George
Edited by: hakomdba on 09.01.2009 06:39

Hallo DB-Experts,
I have encountered a performance problem regarding getting a DataReader by stored procedure versus a SQL statment
and I want to know if this is an known issue and how to tune it.
Getting a DataReader through a SQL statment is faster than with a stored procedure,
if the number of data rows are less than about 8000 datarows, although we are using an index.
The stored procedure ist only faster about 8000 datarows.
For the first 20 rows the different is between 50 abd 20 percent and between and 20 and 2000 rows it fall down to 10 percent.
Over 8000 rows the stored procedure is faster!
The time series table looks like:
CREATE TABLE TimeSeries
OBJECT_ID NUMBER(8) NOT NULL,
UNIVERSAL_TIME NUMBER(10) NOT NULL,
LOCAL_TIME DATE NOT NULL,
MOD_TIME NUMBER(10),
USERID NUMBER(10),
VALUE NUMBER NOT NULL,
FLAG NUMBER(2) DEFAULT 0 NOT NULL
The foreinkey is object_id and another index is for universal_time and mod_time
The stored procedure looks like:
PROCEDURE SELECTDATA_UT_MOD (pObjectID IN NUMBER,
pType IN VARCHAR2,
pTable IN VARCHAR2,
pFrom IN NUMBER,
pTo IN NUMBER,
IO_CURSOR OUT T_CURSOR)
IS
SQLString VARCHAR2(1024);
BEGIN
IF pOBJECTID <> 0 THEN
CASE
WHEN UPPER(pTYPE)='A' THEN
SQLString := 'SELECT UNIVERSAL_TIME, VALUE, FLAG, MOD_TIME FROM ' || pTABLE || ' WHERE OBJECT_ID = :t1 AND UNIVERSAL_TIME >= :t2 and UNIVERSAL_TIME < :t3 Order By UNIVERSAL_TIME, MOD_TIME DESC';
OPEN IO_CURSOR FOR
SQLString USING pOBJECTID,pFROM,pTO;
END IF;
END;
The SQL statment for the data reader looks like:
SELECT d.universal_time, d.VALUE, d.flag, 0 AS mod_time
FROM daten d
WHERE object_id = 18465
AND d.universal_time >= 3600
AND d.universal_time < 28803600
ORDER BY d.universal_time, mod_time DESC
Do you have any idea or tip why the sql statment for the first 8000 rows is faster than the stored procedure?
Many thanks in advance and
Best regards
George
Edited by: hakomdba on 09.01.2009 06:39

How to execute stored procedure in the SQL Commands page

i'm oracle express edition newbie :) i have this stored procedure. it not belong to a package.
create or replace procedure "LIST_MEMBERS"
("MEMBER_CUR" OUT SYS_REFCURSOR)
is
begin
OPEN MEMBER_CUR FOR
SELECT * FROM members;
end;
now, in the SQL Commands page, how to run the stored procedure and return the records. i do this:
begin
execute list_members();
end;
but i'm getting some errors. just need some immediate help :) thanks!!!

Example of using a ref cursor:
SQL> ed
Wrote file afiedt.buf
1 create or replace procedure open_cur(c IN OUT SYS_REFCURSOR) is
2 begin
3    open c for 'select rownum rn from dual connect by rownum <= 10';
4* end;
SQL> /
Procedure created.
SQL> ed
Wrote file afiedt.buf
1 declare
2    c     SYS_REFCURSOR;
3    v_val NUMBER;
4 begin
5    open_cur(c);
6    loop
7      fetch c INTO v_val;
8      exit WHEN c%NOTFOUND;
9      dbms_output.put_line(v_val);
10    end loop;
11    close c;
12* end;
SQL> /
1
2
3
4
5
6
7
8
9
10
PL/SQL procedure successfully completed.
SQL>

How can I Use a Stored Procedure from Microsoft SQL Server?

Hi All,
Would like to use stored procedure as my data service in Visual Composer.
Our version is VC7.0 SP20.
Is stored procedure feasible? What is the system that i need to create in Enterprise Portal? Currently i have BI JDBC System which only allows me to search for tables from SQL Server.
Much appreciate your help.
Thanks & Regards,
Sarah

Hi Skif,
Referring to my post: JDBC System Connection VS BI JDBC System Connection
I do not even able to view list of stored procedure. I need help too..maybe you can show me how do you set the connection? What are the mandatory connection properties? I have filled up:
- Connection URL
- Driver class name
- User Administration: User, Admin (I did user mapping too)
The error message that i got is:
com.sap.guimachine.portalconnector.commandhandler.CommandException: Failed to connect to backend system. Check your system definition and user privileges.#
I had assigned full control to the DB user, and map my portal user to that DB user.
Many Thanks,
Sarah

DB Adapter calling stored procedure in MS SQL Server.

Hi
i am calling a stored procedure in a MS SQL Server.
I configured a Datasource for MS SQL Server driver as Oracle's MS SQL Server Driver(Type 4) Versions: 7.0 and later and provide all db details of sql server. I tested the data source and was getting success message. My BPEL code is just talking with input parameter and then calling the stored procedure in sql server. I was able to compile the code in jdeveloper and deploy to weblogic. But when i am testing the code. i am getting an error.
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'IDMService' failed due to: JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
Test:IDMService [ IDMService_ptt::IDMService(InputParameters,OutputParameters) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: javax.resource.spi.IllegalStateException: [Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to re-lookup Connection Factory eis/sql/idm from JNDI and get a new Connection Handle.
Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections.
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.</faultstring>
<faultactor/>
<detail>
<exception>[Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to re-lookup Connection Factory eis/sql/idm from JNDI and get a new Connection Handle.</exception>
</detail>
</env:Fault>
What is the problem with connection . How cna i rectify it.
Thanks,
Venu Raja

followed the steps mentioned in meatalnk..
JCA-12563 - Unable to Establish an Outbound JCA CCI Connection [ID 1235943.1]
Metalink ID - 1235943.1

Stored Procedure Vs PL-SQL Block

Hi,
I came across an interesting problem last week. Fortunately, I was able to solve it or find an acceptable workaround for myself. But wanted to get some clarification from the experts. So posting it here.
Also, I am new to Orcle, so please excuse any shortcomings in the post.
My data model has following tables-
TABLE_PARENT (ID, other columns)
TABLE_CHILD (ID, other columns, PARENT_ID_FK)
Here, ID is the primary key column for the respective tables; PARENT_ID_FK is the foreign key referencing the ID column from the TABLE_PARENT.
I created a stored procedure programmatically (using MS Excel) to insert records in the two tables. The stored procedure has insert statements for an indefinite number of records in the parent table and for every such record, there's a corresponding record inserted in the child table. Here's the sample code.
BEGIN
/*first record*/
parent_id := MY_SEQUENCE_GENERATOR.NEXTVAL;
INSERT INTO TABLE_PARENT(ID, other columns) VALUES (parent_id, other values);
INSERT INTO TABLE_CHILD(ID, other values,parent_id );
/*second record*/
parent_id := MY_SEQUENCE_GENERATOR.NEXTVAL;
INSERT INTO TABLE_PARENT(ID, other columns) VALUES (parent_id, other values);
INSERT INTO TABLE_CHILD(ID, other values,parent_id );
/*third record*/
parent_id := MY_SEQUENCE_GENERATOR.NEXTVAL;
INSERT INTO TABLE_PARENT(ID, other columns) VALUES (parent_id, other values);
INSERT INTO TABLE_CHILD(ID, other values,parent_id );
/*and so on*/
END
When I run this stored procedure, I keep getting following exception intermittently-
ORA-02291: integrity constraint violated-parent key not found tips.
My thinking is that it comes because the insert statements are executing ahead of turn of the parent_id assignment statement. And this is happening possibly because of some parallelism that is taking place during the execution of the stored procedure, or, some sort of optmization that the DB server does (though erroneously) when it compiles the stored procedure.
I tried out everything that I could think of but it didn't go away. Finally, when I executed the same set of statements as a PL-SQL block, it worked fine.
To understand it better, I am looking for clarification on the following questions.
1) Why does the exception come with stored procedure but not with PL-SQL block? Is my reasoning given above correct (parallelism or some sort of optimization coming into play)?
2) If it is due to parallelism, how to run a Oracle stored procedure with defree of prallelism set to 1?
3) If it is due to optimization done by the compiler, how to instruct the compiler to not do any such optimization. Also, in any case, isn't it an error to optimize but lose program semantics?
4) Another question related to the same piece of work I have is to use transactions in the PL-SQL block, I had to explicitly COMMIT/ROLLBACK it in the code. In whatever references I had read, it was said that by default the transaction begins with BEGIN statement and commits with END. Also, it seems to work with a Stored Proedure though. So is it that a PL_SQL block needs explicity call to COMMIT/ROLLBACK to achive transactions but stored procedures do not?
Any inputs/clarifications will be much appreciated.
Thank you
Neelesh

Ok, your last couple of paragraphs were helpful. Here're the details that were missing in my earlier post.
- I am on Oracle 10.2.0.
- Table definitions-
CREATE TABLE "MYUSER"."TABLE_PARENT"
*(     "ID" NUMBER(19,0) NOT NULL ENABLE,*
*     "NAME" VARCHAR2(30),*
*     "DESCRIPTION" VARCHAR2(80),*
*     "RULETYPE" NUMBER(10,0) NOT NULL ENABLE,*
*     "OPERATOR" NUMBER(10,0),*
*     "MININTERCEPT" FLOAT(126),*
*     "PRIORITY" NUMBER(10,0),*
*     "PENALTY" NUMBER(10,0),*
*     "STATUS" NUMBER(10,0),*
*     PRIMARY KEY ("ID")*
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 131072 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS" ENABLE,
*) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING*
STORAGE(INITIAL 131072 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS"
CREATE TABLE "MYUSER"."TABLE_CHILD"
*(     "ID" NUMBER(19,0) NOT NULL ENABLE,*
*     "WEIGHT" NUMBER(19,0),*
*     "PARENTID_FK" NUMBER(19,0),*
*     PRIMARY KEY ("ID")*
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 131072 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS" ENABLE,
*     CONSTRAINT "FK3A78BF1E6A9DCE51" FOREIGN KEY ("PARENTID_FK")*
*     REFERENCES "MYUSER"."TABLE_PARENT" ("ID") ENABLE*
*) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING*
STORAGE(INITIAL 131072 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS"
- The Stored procedure definition is-
CREATE OR REPLACE PROCEDURE LOAD_RULES_SP AS
ruleid NUMBER(19,0);
tempid NUMBER(19,0);
BEGIN
*/* First parent record */*
SELECT IDGENERATOR.NEXTVAL INTO ruleid FROM dual;
INSERT INTO TABLE_PARENT (ID, NAME, DESCRIPTION, RULETYPE, OPERATOR, MININTERCEPT, PRIORITY, penalty, STATUS) VALUES (ruleid, 'Rule 1',null,3,0,0,null,null,1);
*/* Corresponding child records */*
SELECT IDGENERATOR.NEXTVAL INTO tempid FROM dual;
INSERT INTO TABLE_CHILD (id, weight, PARENTID_FK)
VALUES (tempid, 0.2, ruleid);
SELECT IDGENERATOR.NEXTVAL INTO tempid FROM dual;
INSERT INTO TABLE_CHILD (id, weight, PARENTID_FK)
VALUES (tempid, 0.5, ruleid);
SELECT IDGENERATOR.NEXTVAL INTO tempid FROM dual;
INSERT INTO TABLE_CHILD (id, weight, PARENTID_FK)
VALUES (tempid, 0.3, ruleid);
*/* First parent record */*
SELECT IDGENERATOR.NEXTVAL INTO ruleid FROM dual;
INSERT INTO TABLE_PARENT (ID, NAME, DESCRIPTION, RULETYPE, OPERATOR, MININTERCEPT, PRIORITY, penalty, STATUS) VALUES (ruleid, 'Rule 1',null,3,0,0,null,null,1);
*/* Corresponding child records */*
SELECT IDGENERATOR.NEXTVAL INTO tempid FROM dual;
INSERT INTO TABLE_CHILD (id, weight, PARENTID_FK)
VALUES (tempid, 0.2, ruleid);
SELECT IDGENERATOR.NEXTVAL INTO tempid FROM dual;
INSERT INTO TABLE_CHILD (id, weight, PARENTID_FK)
VALUES (tempid, 0.5, ruleid);
SELECT IDGENERATOR.NEXTVAL INTO tempid FROM dual;
INSERT INTO TABLE_CHILD (id, weight, PARENTID_FK)
VALUES (tempid, 0.3, ruleid);
*/* And so on for a few parent records more */*
END;
Can you throw some light on the exception I was seeing now? Note that when I changed from stored procedure to an anonymous block, it worked fine.
One correction in my earlier post is that as the code snippet shows, there are multiple inserts in the child table for every record inserted in the parent one.

Please Help!!!!! Problem Migrating from sql 2000 stored procedure to PL/SQL

I have used a tool to convert my sql 2000 stored procedure to Oracle 10g PL/SQL, here is an example
SQL 2000 Stored Procedure
CREATE PROCEDURE [GetEmployees]
AS
Select * from EMPMST ORDER BY emp_name
GO
After Transformation i got 2 files, one was a procedure and other a package
CREATE OR REPLACE PACKAGE GLOBALPKG
AS
     TYPE RCT1 IS REF CURSOR;
     TRANCOUNT INTEGER := 0;
     IDENTITY INTEGER;
END;
CREATE OR REPLACE PROCEDURE GetEmployees
     RCT1 IN OUT      GLOBALPKG.RCT1
AS
BEGIN
     OPEN RCT1 FOR
     SELECT *
     FROM EMPMST
     ORDER BY emp_name;
END;
When i execute the procedure GetEmployees i got this error :
SQL> execute GetEmployees;
BEGIN GetEmployees; END;
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'GETEMPLOYEES'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
Please Help me in debugging this error. Thanks in advance.

As the poster above mentioned you cannot call "GetEmployees" without a parameter.
Note that the procedure declaration has the following line
RCT1 IN OUT GLOBALPKG.RCT1
This means that whenever you want to call the procedure you must pass it a variable of type GLOBALPKG.RCT1
However unless this is merely a homework or learning exercise (i.e. you are not porting the code of a production application) i would strongly recommend that you do not attempt to simply convert the code to PL/SQL.
The reasoning behind this is that Oracle's architecture will be completely different to the source of the original code and if you attempt to simply port the code (especially using an automatic tool) you will almost certainly hit problems.
For example the SQL Server's 2000 code may (should be) be written based on SQL Server's locking strategy. Oracle's locking strategy is completly different if you try to use the same techniques as you do in SQL Server the performance will suffer.
Porting a code or a database schema from one platform to another involves a lot of analysis in order to take advantage of the features of the destination platform.
As I said this may not be important to you depending on why you are attempting a port.
Good Luck.

Calling Managed CLR Stored Procedure from C++ SQL Server 2008 fails with Msg 2809

I am trying to call a stored procedure from C++ (VS 2010).
Here is what the stored procedure looks like:
public class Validate
[Microsoft.SqlServer.Server.SqlProcedure(Name = "ClientTest")]
public static void ClientTest(out String res )
{ res = "50";}
To create a stored procedure I deploy at first the assembly
USE [test]
GO
CREATE ASSEMBLY ClientTestAssembly
AUTHORIZATION testLogin
FROM 'C:\Users\test\Documents\Visual Studio 2010\Projects\TestCreationAssemblyCSharp\TestCreationAssemblyCSharp\bin\x64\Debug\TestCreationAssemblyCSharp.dll'
and call
USE test
GO
CREATE PROCEDURE ClientTest (@res NVARCHAR(40) OUTPUT)
AS
EXTERNAL NAME ClientTestAssembly.Validate.ClientTest
I can call my procedure direct in SQL Server Management Studio without any errors
declare @res nvarchar(10)
execute ClientTest @res OUTPUT
print @res
But when I try to call this procedure from C++ using CALL syntax
SQLBindParameter(sqlstatementhandle, 1, SQL_PARAM_OUTPUT, SQL_C_CHAR,
SQL_VARCHAR , 40, 0, version, sizeof(version) ,
&pcbValue);
res = SQLExecDirect(sqlstatementhandle, (SQLCHAR*)("{CALL ClientTest(?) }"), SQL_NTS);
I get the Error 2809 with SQLSTATE 42000 and with statement
The request for 'ClientTest'
(procedure) failed because 'ClientTest' is a procedure object.
However, if I wrap my CLR stored procedure into a T-SQL stored procedure, like
CREATE PROCEDURE myProc (@res NVARCHAR(40) OUTPUT)
AS
EXEC ClientTest @res OUTPUT
and call then myProc instead of ClientTest
res = SQLExecDirect(sqlstatementhandle, (SQLCHAR*)("{CALL myProc(?) }"), SQL_NTS);
everithing works fine and I get 50 as result.
I have no ideas what is the reason for that behavior.
Thanks very much for any suggestion.
Christina

I'm not an ODBC expert, but you might try following the sample here:
Process Return Codes and Output Parameters (ODBC)
To see if it also behaves differently for your CLR proc.
David
David http://blogs.msdn.com/b/dbrowne/

Stored Procedure in NAtive SQL

Similar Messages

Maybe you are looking for