Count of IN/OUT Parameters.

Hello Gurus,
Is there anyway I can get the Count or list of IN/OUT parameters which are suplied to Procedure or function. It would be great if its Generic statement.
Thanx in advance,
Pritam

You can quyer out the data dictionary :
User_Arguments
All_Arguments
i.e.
select object_name, package_name, object_id, argument_name,
position, data_type, default_value,
default_length,
data_length, data_precision,
in_out
from all_arguments
where object_name = '&Enter_Proc_Or_Func_Name'
/

Similar Messages

I am facing a problem in passing multiple values as out parameters from fo

Hi All,
i am facing a problem in passing multiple values as out parameters from for loop.
EX:
i have a select statment inside a loop like.....
PACKAGE SPEC:
create or replace PACKAGE EMP_PKG AS
TYPE TAB_NUM IS TABLE OF SCOTT.EMP.EMPNO%TYPE;
TYPE TAB_NAME IS TABLE OF SCOTT.EMP.ENAME%TYPE;
TYPE TAB_JOB IS TABLE OF SCOTT.EMP.JOB%TYPE;
temp_table TAB_NUM;
procedure test(temp_TAB_e_no OUT TAB_NUM,
temp_TAB_e_name OUT TAB_NAME,
temp_TAB_e_job OUT TAB_JOB);
END EMP_PKG;
PACKAGE BODY:
create or replace PACKAGE BODY EMP_PKG AS
v_e_no NUMBER;
procedure test(temp_TAB_e_no OUT TAB_NUM,
temp_TAB_e_name OUT TAB_NAME,
temp_TAB_e_job OUT TAB_JOB) IS
BEGIN
select EMPNO bulk collect into temp_table from emp;
for i in 1..temp_table.count loop
v_e_no := temp_table(i);
select empno,
ename,
job
into temp_TAB_e_no(i),
temp_TAB_e_name(i),
temp_TAB_e_job(i)
from emp
where empno = v_e_no;
end loop;
end test;
END EMP_PKG;
PROBLEM FACING IS:
I am expecting all rows returning from bellow select statment ...
select empno,
ename,
job
into temp_TAB_e_no(i),
temp_TAB_e_name(i),
temp_TAB_e_job(i)
from emp
where empno = v_e_no;
But,while running the SP , i am getting error like
ORA-06531: Reference to uninitialized collection
ORA-06512: at "SCOTT.EMP_PKG", line 16
why i am not getting all values as out parameters.please provide a solution for me.
Thanks in advance my friend.

user9041629 wrote:
Hi All,
i am facing a problem in passing multiple values as out parameters from for loop.
EX:
i have a select statment inside a loop like.....
PACKAGE SPEC:
create or replace PACKAGE EMP_PKG AS
TYPE TAB_NUM IS TABLE OF SCOTT.EMP.EMPNO%TYPE;
TYPE TAB_NAME IS TABLE OF SCOTT.EMP.ENAME%TYPE;
TYPE TAB_JOB IS TABLE OF SCOTT.EMP.JOB%TYPE;
temp_table TAB_NUM;
procedure test(temp_TAB_e_no OUT TAB_NUM,
temp_TAB_e_name OUT TAB_NAME,
temp_TAB_e_job OUT TAB_JOB);
END EMP_PKG;
PACKAGE BODY:
create or replace PACKAGE BODY EMP_PKG AS
v_e_no NUMBER;
procedure test(temp_TAB_e_no OUT TAB_NUM,
temp_TAB_e_name OUT TAB_NAME,
temp_TAB_e_job OUT TAB_JOB) IS
BEGIN
select EMPNO bulk collect into temp_table from emp;
for i in 1..temp_table.count loop
v_e_no := temp_table(i);
select empno,
ename,
job
into temp_TAB_e_no(i),
temp_TAB_e_name(i),
temp_TAB_e_job(i)
from emp
where empno = v_e_no;
end loop;
end test;
END EMP_PKG;
PROBLEM FACING IS:
I am expecting all rows returning from bellow select statment ...
select empno,
ename,
job
into temp_TAB_e_no(i),
temp_TAB_e_name(i),
temp_TAB_e_job(i)
from emp
where empno = v_e_no;
But,while running the SP , i am getting error like
ORA-06531: Reference to uninitialized collection
ORA-06512: at "SCOTT.EMP_PKG", line 16
why i am not getting all values as out parameters.please provide a solution for me.
Thanks in advance my friend.Probably not a bad thing that this isn't working for you.
This is a horrible way to return the contents of a table.
Are you doing this for educational purpose, or ... what is your goal here? If you just want to return a result set to a client you'd want to look in to using a REF CURSOR and not a bunch of arrays combined with horribly procedural (slow) code.

OCCI call PL/SQL Procedure with 2 IN/OUT Parameters..BUS ERROR!!

Hi~ All,
I am new user for using OCCI. Util now, I encountered a problem with OCCI when I call a procedure with 2 IN/OUT parameters. Then,I got an error(core dump), Why?
CREATE OR REPLACE PROCEDURE demo_proc (v1 in integer, v2 in out varchar2, v3 in out varchar2);
==== OCCI Code ========
stmt = conn->createStatement
("BEGIN demo_proc(:v1, :v2, :v3); END;");
cout << "Executing the block :" << stmt->getSQL() << endl;
stmt->setInt (1, 10);
stmt->setString (2, "Test1");
stmt->setString (3, "First");
int updateCount = stmt->executeUpdate ();
cout << "Update Count:" << updateCount << endl;
cout << "Printing the INOUT & OUT parameters:" << endl;
string c1 = stmt->getString (2);
cout << c1 << endl;
string c2 = stmt->getString (3);
==== RUN RESULT ====
Bus error(coredump)
But, If i just only got one of string from v1 or v2,I could get correct result!! Why? Does some one know how to avoid this two IN/OUT parameters issue?

Hi~ Amoghavarsha,
Thanks for your response! I solved the problem by myself. I found the root cause, it seems very strange in
initializing environment variable.
=== FAILED ===
Environment *env;
=== SUCCESS ===
Environment *env = NULL; <---Why??
cout << "occidml - createEnvironment" << endl;
env = Environment::createEnvironment (Environment::OBJECT);
Eventually, I fixed this issue in Win2K and HP-UX 11.
Best Regards,

Procedure multiple out parameters into a cursor

Hi,
I have a procedure that returns multiple out parameters. How do I combine those and return as a cursor?
Here is the procedure I use (modified for forums)
PROCEDURE SAMPLEPROCEDURE
(in_param1 IN NUMBER,
in_param2   IN VARCHAR2,
output_ONE   IN VARCHAR2,
output_TWO   IN VARCHAR2,
output_THREE   IN VARCHAR2,
output_FOUR   IN VARCHAR2,
output_FIVE   IN VARCHAR2,
output_SIX   IN VARCHAR2,
IS
BEGIN
      output_one := 'YAH!';
     SELECT count(*) into output_TWO FROM   tablea WHERE tablea.columnB = in_param1;
     IF (variable1 = 0) THEN
        output_one := 'SOMETHING MISSING';
        RETURN;
     END IF;
      SELECT count(*) into CHECKINGACCOUNT_COUNT from ACCOUNT WHERE   TABLE = in_param1 AND ACCOUNT.TYPE = 'CHECKING';
   IF (CHECKINGACCOUNT_COUNT <> 0) then
SELECT count(*) into output_THREE FROM   tableB WHERE tableB.columnB = in_param1;
SELECT columnC into output_FOUR FROM   tableC WHERE tableC.columnC = in_param1;
SELECT SUM(columnD) into output_FIVE FROM   tableD WHERE tableD.columnD = in_param1;
   if(output_FIVE >= input_param2) then
output_FIX := 'RETURN VALUE';
   end if;
END IF;
end SAMPLEPROCEDURE;

Should Use 'OUT' for Output parameter instead of 'IN' in your procedure, its wrong.
For fetching more than one row from procedure, use REFCURSOR.
Follow the Code:
CREATE OR REPLACE PROCEDURE proc_cursor (in_n_sal
IN
NUMBER,
ov_n_sumsal
OUT NUMBER,
ov_n_empno
OUT sys_refcursor,
ov_cr_details
OUT sys_refcursor)
AS
BEGIN
   SELECT   SUM (sal)
INTO   ov_n_sumsal
FROM   emp
WHERE   sal = in_n_sal; /*here , the query returns only one row*/
open ov_n_empno for
   SELECT   empno
FROM   emp
WHERE   sal = in_n_sal;/*here the query may return more than one row , so i used refcursor for fetching the result set*/
open ov_cr_details for
   SELECT   SUM (sal), empno
FROM   emp
WHERE   sal = in_n_sal
group by empno;/*here also i used refcursor , to achieve more than one row and two more columns result set*/
END;
EXECUTION:
SQL> variable OV_N_SUMSAL number;
SQL> variable OV_N_EMPNO number;
SQL> variable OV_N_EMPNO refcursor;
SQL> variable OV_CR_DETAILS refcursor;
SQL> EXECUTE PROC_CURSOR ( 800, :OV_N_SUMSAL, :OV_N_EMPNO, :OV_CR_DETAILS );
PL/SQL procedure successfully completed.
SQL> PRINT OV_N_SUMSAL;
OV_N_SUMSAL
       1600
SQL> PRINT OV_N_EMPNO;
     EMPNO
      1888
      1239
SQL> PRINT OV_CR_DETAILS;
SUM(SAL)      EMPNO
       800       1888
       800       1239
SQL>
I hope this one will help you.

"Formal OUT and IN OUT parameters can be returned in any order"

Hi,
From the PL/SQL Language Reference (11.2):
Formal OUT and IN OUT parameters can be returned in any order. In this example, the final values of x and y are undefined:
CREATE OR REPLACE PROCEDURE p (x OUT INTEGER, y OUT INTEGER) AS
BEGIN
x := 17; y := 93;
END;
What does this mean? How are the values of x and y in any doubt here? I tested it and x and y were set to 17 and 93 respectively.
Thanks in advance,
Jason

FrankKulash wrote:
I wouldn't count on variable a being 93 after running this (though it has been 93 every time I've tried it).
Right, even though it is quite logical OUT parameters are assigned in parameter number order (which is what Oracle is using in 10G & 11G - can't test on older versions), I didn't see it in documentation, so we can't assume it.
SQL> CREATE OR REPLACE PROCEDURE p (x OUT INTEGER, y OUT INTEGER) AS
2 BEGIN
3 x := 17;
4 y := 93;
5 END;
6 /
Procedure created.
SQL> DECLARE
2      a   INTEGER;
3 BEGIN
4      p (a, a);
5      dbms_output.put_line (a || ' = a aftr calling p (a, a)');
6 END;
7 /
93 = a aftr calling p (a, a)
PL/SQL procedure successfully completed.
SQL> CREATE OR REPLACE PROCEDURE p (x OUT INTEGER, y OUT INTEGER) AS
2 BEGIN
3 y := 93;
4 x := 17;
5 END;
6 /
Procedure created.
SQL> DECLARE
2      a   INTEGER;
3 BEGIN
4      p (a, a);
5      dbms_output.put_line (a || ' = a aftr calling p (a, a)');
6 END;
7 /
93 = a aftr calling p (a, a)
PL/SQL procedure successfully completed.
SQL> CREATE OR REPLACE PROCEDURE p (y OUT INTEGER, x OUT INTEGER) AS
2 BEGIN
3 x := 17;
4 y := 93;
5 END;
6 /
Procedure created.
SQL> DECLARE
2      a   INTEGER;
3 BEGIN
4      p (a, a);
5      dbms_output.put_line (a || ' = a aftr calling p (a, a)');
6 END;
7 /
17 = a aftr calling p (a, a)
PL/SQL procedure successfully completed.
SQL> CREATE OR REPLACE PROCEDURE p (y OUT INTEGER, x OUT INTEGER) AS
2 BEGIN
3 y := 93;
4 x := 17;
5 END;
6 /
Procedure created.
SQL> DECLARE
2      a   INTEGER;
3 BEGIN
4      p (a, a);
5      dbms_output.put_line (a || ' = a aftr calling p (a, a)');
6 END;
7 /
17 = a aftr calling p (a, a)
PL/SQL procedure successfully completed.
SQL>
SY.

How to get multiple out parameters from a pl/sql stored procedure in ADF Jdeveloper 11g release2

I´m trying to call from AppModuleImpl a stored procedure from my oracle DB which receives one input parameter and returns 5 out parameters.
I´m using jdeveloper 11g release2 ADF and I have created a java bean "ProRecallPlatesBean " with the atributes and accesors and I serialize it. just like in this article http://docs.oracle.com/cd/E24382_01/web.1112/e16182/bcadvgen.htm#sm0297
This is my code so far:
public ProRecallPlatesBean getCallProRecallPlates(String numPlates) {
CallableStatement st = null;
try {
          // 1. Define the PL/SQL block for the statement to invoke
          String stmt = "begin CTS.Pk_PreIn.proRecallPlates(?,?,?,?,?,?); end;";
          // 2. Create the CallableStatement for the PL/SQL block
          st = getDBTransaction().createCallableStatement(stmt,0);
          // 3. Register the positions and types of the OUT parameters
          st.registerOutParameter(2,Types.VARCHAR);
st.registerOutParameter(3,Types.VARCHAR);
st.registerOutParameter(4,Types.VARCHAR);
st.registerOutParameter(5,Types.VARCHAR);
st.registerOutParameter(6,Types.VARCHAR);
// 4. Set the bind values of the IN parameters
st.setString(1,numPlates);
// 5. Execute the statement
st.executeUpdate();
// 6. Create a bean to hold the multiple return values
ProRecallPlatesBean result = new ProRecallPlatesBean();
// 7. Set values of properties using OUT params
result.setSpfVal(st.getString(2));
result.setTransportTypeVal(st.getString(3));
result.setTransportCompanyVal(st.getString(4));
result.setCompanyDescrVal(st.getString(5));
result.setDGAPrint(st.getString(6));
// 8. Return the result
return result;
} catch (SQLException e) {
throw new JboException(e);
} finally {
if (st != null) {
try {
// 9. Close the JDBC CallableStatement
st.close();
catch (SQLException e) {}
In Jdeveloper I went into AppModule.xml JAVA>Client Interface section and expose "getCallProRecallPlates" Then I can see "getCallProRecallPlates" in Data Controls, I drag and drop it to a JSF page, an input text component and a button are generated in order to put in there the procedure input parameter (numPlates).
I don't know if I'm on the right track.
When I click the button, the "result" variable is supposed to be filled with data from the stored procedure. I want each of those values to be displayed in Output text or input text adf components but I dont know how. Thank you very much in advance I´m a newbie and i'll appreciate your help!

What version are you on?
Works fine for me on my 11g:
SQL> create or replace procedure testxml (clob_out out clob)
2 is
3     l_clob   clob;
4     l_ctx    dbms_xmlquery.ctxhandle;
5 begin
6     l_ctx := dbms_xmlquery.newcontext ('select * from dual');
7     l_clob := dbms_xmlquery.getxml (l_ctx);
8     clob_out := l_clob;
9     dbms_xmlquery.closecontext (l_ctx);
10 end testxml;
11 /
Procedure created.
SQL>
SQL> variable vout clob;
SQL>
SQL> exec testxml (:vout)
PL/SQL procedure successfully completed.
SQL>
SQL> print vout
VOUT
<?xml version = '1.0'?>
<ROWSET>
   <ROW num="1">
      <DUMMY>X</DUMMY>
   </ROW>
</ROWSET>But definitely you can optimize your proc a bit: Try
create or replace procedure testxml (clob_out in out nocopy clob)
is
   l_ctx    dbms_xmlquery.ctxhandle;
begin
   l_ctx := dbms_xmlquery.newcontext ('select * from dual');
   clob_out := dbms_xmlquery.getxml (l_ctx);
   dbms_xmlquery.closecontext (l_ctx);
end testxml;
/

Is there a way to dynamically determine the number of out parameters for a server side procedure?

Hi,
Below is a helper method used for calling a server-side function which loops through the inbound bindVars parameter to populate the function's IN parameters. Is there a way to dynamically determine the IN/OUT parameters based on the procedure name in the stmt parameter? No members of the CallableStatement class seemed promising, but the getParameterMetaData() method in the PreparedStatement class seemed like it could be helpful lead. However, I have not found any detailed descriptions (yet) of how to use it.
protected Object callStoredFunction(int sqlReturnType, String stmt,
Object[] bindVars) {
CallableStatement st = null;
try {
// 1. Create a JDBC CallabledStatement
st = getDBTransaction().createCallableStatement(
"begin ? := "+stmt+";end;",0);
// 2. Register the first bind variable for the return value
st.registerOutParameter(1, sqlReturnType);
if (bindVars != null) {
// 3. Loop over values for the bind variables passed in, if any
for (int z = 0; z < bindVars.length; z++) {
// 4. Set the value of user-supplied bind vars in the stmt
st.setObject(z + 2, bindVars[z]);
// 5. Set the value of user-supplied bind vars in the stmt
st.executeUpdate();
// 6. Return the value of the first bind variable
return st.getObject(1);
catch (SQLException e) {
throw new JboException(e);
finally {
if (st != null) {
try {
// 7. Close the statement
st.close();
catch (SQLException e) {}
James

The PreparedStatement.getParameterMetaData() object is exactly what you need for this task.
Once you have the ParameterMetaData you can ask it how many parameters are present and which mode they are. The parameters are numbered from 1 to n and you can use ParameterMetaData.getParameterMode(1); to get the mode of the 1st parameter. The modes are defined as static values in the ParameterMetaData object. Check out the doc at http://docs.oracle.com/javase/7/docs/api/java/sql/ParameterMetaData.html
Timo

Missing IN or OUT parameters randomly

Hi,
I got the error "Missing IN or OUT parameters".
The bind variable setting was already set according to the suggestion found in the internet. However, the error is persisted. As I checked in the log file, the query executed are different between when there was no error and when the error occured even though it is the same action and the same code.
Is there anybody experienced this problem? Why are the query different and how can I fix this?
Thanks.
nat...
Note: Below are parts of log detail....
This is the query when it is ok...
SELECT * FROM (SELECT
CoverageEO.CLAIM_ID,
CoverageEO.CONTRACT_ID,
CoverageEO.COVERAGE_REF_ID,
CoverageEO.VERSION_NO,
CoverageEO.COVERAGE_CODE,
CoverageEO.COVERAGE_TYPE,
CoverageEO.EFFECTIVE_DATE,
CoverageEO.EXPIRE_DATE,
CoverageEO.POLICY_REF,
CoverageEO.MEMBER_PARTNER_ID,
CoverageEO.SALARY,
CoverageEO.MEMBER_POLICY_STATUS,
CoverageEO.MEMBER_INCEPTION_DATE,
CoverageEO.PLAN_INT_ID,
CoverageEO.COMP_PARTNER_ID,
CoverageEO.COMP_CONTRACT_ID,
CoverageEO.COMP_POLICY_REF,
CoverageEO.COMP_STATUS,
CoverageEO.COMP_STATUS_DATE,
CoverageEO.COMP_FIRST_EFF_DATE,
CoverageEO.WAITING_PERIOD,
CoverageEO.WAITING_PERIOD_UNIT,
CoverageEO.TRANSFER_DATE,
CoverageEO.TRANSFER_FLAG,
CoverageEO.LIVING_CLM_PAY_TO,
CoverageEO.LIVING_CLM_PAYMENT_METHOD,
CoverageEO.DEATH_CLM_PAY_TO,
CoverageEO.DEATH_CLM_PAYMENT_METHOD,
CoverageEO.REFUND_PREM_PAY_TO,
CoverageEO.REFUND_PREM_PAYMENT_METHOD,
CoverageEO.ER_PAY_TO,
CoverageEO.ER_PAYMENT_METHOD,
CoverageEO.CONTINUOUS_DAYS,
CoverageEO.ELIGIBLE_STATUS_INITIAL,
CoverageEO.ELIGIBLE_STATUS,
CoverageEO.TOTAL_ACTUAL_AMOUNT,
CoverageEO.TOTAL_APPROVED_AMOUNT,
CoverageEO.TOTAL_NET_APPROVED_AMOUNT,
CoverageEO.TOTAL_EXCEED_AMOUNT,
CoverageEO.TOTAL_EXCEED_PAID_TO_MSP,
CoverageEO.TOTAL_EXCEED_NOT_PAID,
CoverageEO.NOT_COVER_ACTUAL_AMOUNT,
CoverageEO.NOT_COVER_EXCEED_AMOUNT,
CoverageEO.TOTAL_CO_INS_AMOUNT,
CoverageEO.TOTAL_COPAY_AMOUNT,
CoverageEO.TOTAL_FDD_AMOUNT,
CoverageEO.DECISION_STATUS,
CoverageEO.DECISION_DATE,
CoverageEO.DECISION_BY,
CoverageEO.PAYMENT_STATUS,
CoverageEO.CONT_CLM_GRP,
CoverageEO.CONT_PARENT_CLAIM_ID,
CoverageEO.CREATED_BY,
CoverageEO.CREATED_DATE,
CoverageEO.LAST_UPDATED_BY,
CoverageEO.LAST_UPDATED_DATE,
CoverageEO.TOP_INDICATOR,
CoverageEO.COVER_END_DATE,
CoverageEO.COVER_START_DATE,
CoverageEO.AGENT_CODE1,
CoverageEO.AGENT_CODE2,
CoverageEO.NEXT_DUE_DATE,
CoverageEO.CREDIT_TERM,
CoverageEO.CYCLE_END_DATE,
CoverageEO.CYCLE_START_DATE,
CoverageEO.VALID_DATE_FLAG,
CoverageEO.IS_CONTINUOUS,
CoverageEO.BENEFIT_AMOUNT,
CoverageEO.NET_PAID_AMOUNT,
CoverageEO.REMARK_CUSTOMER,
CoverageEO.REMARK_MSP,
CoverageEO.POLICY_YEAR,
CoverageEO.NOT_COVER_EXCEED_FLAG,
CoverageEO.FDD_EXCEED_AMOUNT,
CoverageEO.FDD_EXCEED_FLAG,
CoverageEO.CO_INS_EXCEED_AMOUNT,
CoverageEO.CO_INS_EXCEED_FLAG,
CoverageEO.COPAY_EXCEED_AMOUNT,
CoverageEO.COPAY_EXCEED_FLAG,
CoverageEO.FDD_AMOUNT,
CoverageEO.CO_INS_PERCENT,
CoverageEO.CO_INS_AMOUNT,
CoverageEO.COPAY_AMOUNT,
CoverageEO.EXCEED_REASON,
CoverageEO.EXCEED_REASON_OTH
, (SELECT U.ASSESSOR_ID FROM ECS_USERS U
WHERE LOWER(CoverageEO.DECISION_BY) = LOWER(U.USERNAME)) ASSESSOR_ID
FROM
GCS_T_COVERAGE CoverageEO
ORDER BY
CoverageEO.CLAIM_ID, CoverageEO.POLICY_REF, CoverageEO.COVERAGE_CODE) QRSLT WHERE CLAIM_ID = :Bind_ClaimId
This is the query when we got the error...
SELECT * FROM (SELECT
CoverageEO.CLAIM_ID,
CoverageEO.CONTRACT_ID,
CoverageEO.COVERAGE_REF_ID,
CoverageEO.VERSION_NO,
CoverageEO.COVERAGE_CODE,
CoverageEO.COVERAGE_TYPE,
CoverageEO.EFFECTIVE_DATE,
CoverageEO.EXPIRE_DATE,
CoverageEO.POLICY_REF,
CoverageEO.MEMBER_PARTNER_ID,
CoverageEO.SALARY,
CoverageEO.MEMBER_POLICY_STATUS,
CoverageEO.MEMBER_INCEPTION_DATE,
CoverageEO.PLAN_INT_ID,
CoverageEO.COMP_PARTNER_ID,
CoverageEO.COMP_CONTRACT_ID,
CoverageEO.COMP_POLICY_REF,
CoverageEO.COMP_STATUS,
CoverageEO.COMP_STATUS_DATE,
CoverageEO.COMP_FIRST_EFF_DATE,
CoverageEO.WAITING_PERIOD,
CoverageEO.WAITING_PERIOD_UNIT,
CoverageEO.TRANSFER_DATE,
CoverageEO.TRANSFER_FLAG,
CoverageEO.LIVING_CLM_PAY_TO,
CoverageEO.LIVING_CLM_PAYMENT_METHOD,
CoverageEO.DEATH_CLM_PAY_TO,
CoverageEO.DEATH_CLM_PAYMENT_METHOD,
CoverageEO.REFUND_PREM_PAY_TO,
CoverageEO.REFUND_PREM_PAYMENT_METHOD,
CoverageEO.ER_PAY_TO,
CoverageEO.ER_PAYMENT_METHOD,
CoverageEO.CONTINUOUS_DAYS,
CoverageEO.ELIGIBLE_STATUS_INITIAL,
CoverageEO.ELIGIBLE_STATUS,
CoverageEO.TOTAL_ACTUAL_AMOUNT,
CoverageEO.TOTAL_APPROVED_AMOUNT,
CoverageEO.TOTAL_NET_APPROVED_AMOUNT,
CoverageEO.TOTAL_EXCEED_AMOUNT,
CoverageEO.TOTAL_EXCEED_PAID_TO_MSP,
CoverageEO.TOTAL_EXCEED_NOT_PAID,
CoverageEO.NOT_COVER_ACTUAL_AMOUNT,
CoverageEO.NOT_COVER_EXCEED_AMOUNT,
CoverageEO.TOTAL_CO_INS_AMOUNT,
CoverageEO.TOTAL_COPAY_AMOUNT,
CoverageEO.TOTAL_FDD_AMOUNT,
CoverageEO.DECISION_STATUS,
CoverageEO.DECISION_DATE,
CoverageEO.DECISION_BY,
CoverageEO.PAYMENT_STATUS,
CoverageEO.CONT_CLM_GRP,
CoverageEO.CONT_PARENT_CLAIM_ID,
CoverageEO.CREATED_BY,
CoverageEO.CREATED_DATE,
CoverageEO.LAST_UPDATED_BY,
CoverageEO.LAST_UPDATED_DATE,
CoverageEO.TOP_INDICATOR,
CoverageEO.COVER_END_DATE,
CoverageEO.COVER_START_DATE,
CoverageEO.AGENT_CODE1,
CoverageEO.AGENT_CODE2,
CoverageEO.NEXT_DUE_DATE,
CoverageEO.CREDIT_TERM,
CoverageEO.CYCLE_END_DATE,
CoverageEO.CYCLE_START_DATE,
CoverageEO.VALID_DATE_FLAG,
CoverageEO.IS_CONTINUOUS,
CoverageEO.BENEFIT_AMOUNT,
CoverageEO.NET_PAID_AMOUNT,
CoverageEO.REMARK_CUSTOMER,
CoverageEO.REMARK_MSP,
CoverageEO.POLICY_YEAR,
CoverageEO.NOT_COVER_EXCEED_FLAG,
CoverageEO.FDD_EXCEED_AMOUNT,
CoverageEO.FDD_EXCEED_FLAG,
CoverageEO.CO_INS_EXCEED_AMOUNT,
CoverageEO.CO_INS_EXCEED_FLAG,
CoverageEO.COPAY_EXCEED_AMOUNT,
CoverageEO.COPAY_EXCEED_FLAG,
CoverageEO.FDD_AMOUNT,
CoverageEO.CO_INS_PERCENT,
CoverageEO.CO_INS_AMOUNT,
CoverageEO.COPAY_AMOUNT,
CoverageEO.EXCEED_REASON,
CoverageEO.EXCEED_REASON_OTH
, (SELECT U.ASSESSOR_ID FROM ECS_USERS U
WHERE LOWER(CoverageEO.DECISION_BY) = LOWER(U.USERNAME)) ASSESSOR_ID
FROM
GCS_T_COVERAGE CoverageEO
ORDER BY
CoverageEO.CLAIM_ID, CoverageEO.POLICY_REF, CoverageEO.COVERAGE_CODE) QRSLT WHERE ((CLAIM_ID = :Bind_ClaimId) AND CLAIM_ID = :fbkKy__0 AND CONTRACT_ID = :fbkKy__1 AND COVERAGE_REF_ID = :fbkKy__2 AND VERSION_NO = :fbkKy__3)
<ViewObjectImpl> <bindParametersForCollection> [5143] (0) ViewObjectImpl.bindParametersForCollection(21441) Bind params for ViewObject: [com.aacp.gcs.vo.base.CoverageVO]ClaimAssessmentAM.CoverageVO_1046_findByKey_
<OracleSQLBuilderImpl> <bindParamValue> [5144] (0) OracleSQLBuilderImpl.bindParamValue(4657) Binding param "fbkKy__0": 372610
<OracleSQLBuilderImpl> <bindParamValue> [5145] (0) OracleSQLBuilderImpl.bindParamValue(4657) Binding param "fbkKy__1": 1986116
<OracleSQLBuilderImpl> <bindParamValue> [5146] (0) OracleSQLBuilderImpl.bindParamValue(4657) Binding param "fbkKy__2": 19749
<OracleSQLBuilderImpl> <bindParamValue> [5147] (0) OracleSQLBuilderImpl.bindParamValue(4657) Binding param "fbkKy__3": 1
It seems :Bind_ClaimId variable is missing but all :fbkKy__x variables are binded.

Hi Frank,
Already run the application in the debug mode and got log files. The long queries posted here were from the log files. That's why I saw the queries executed when the error occurred and when there was no error were different.
When there was no error, the sql statement invoked had only 1 variable and it was binded correctly. But when the error occurred, the system used the different sql statement with 4 variables and no value assigned to the Bind_ClaimId variable.
I wonder why the sql statement executed from the same action and the same code are different. What is the constraint/ condition for the system to generate the sql statement? Is it related to view link or data model in AM? How to fix this?
Thanks.
nat...

PL/SQL Web Service. Out Parameters are included in Request.

I am using JDEVELOPER 11.1.1.3.0. I generated a web service from PL/SQL successfully.
When the web service is generated and deployed (Deployed to the IntegratedWeblogicServer) it wants the output parameters to be included with the request.
Here is an example of my wsdl.
<wsdl:message name="AMP_WS_getCustomerDetails">
<wsdl:part name="pGuid" type="xsd:string"/>
<wsdl:part name="pCustName_out" type="xsd:string"/>
<wsdl:part name="pCustomerId_out" type="xsd:decimal"/>
<wsdl:part name="pStatus_out" type="xsd:decimal"/>
<wsdl:part name="pMessage_out" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="AMP_WS_getCustomerDetailsResponse">
<wsdl:part name="pCustName_out" type="xsd:string"/>
<wsdl:part name="pCustomerId_out" type="xsd:decimal"/>
<wsdl:part name="pStatus_out" type="xsd:decimal"/>
<wsdl:part name="pMessage_out" type="xsd:string"/>
</wsdl:message>
In the AMP_WS_getCustomerDetails I am not expecting pCustName_out, pCustomerId_out, pStatus_out, or pMessage_out to be included. They are out parameters in the pl/sql.
Has anyone else run into this?
Thanks for any help.

Parameters relate to procedures. Web Services require XML messages.
Where are the parameters coming from? You cannot pass a dynamic number of parameters into a procedure, but you can pass a structured type as a parameter which can contain multiple values, whether that is an array/collection type or an XML document itself.
Just package up the values into the XML and pass it to the web service.
If this doesn't answer your question, please post more information, with some example data and code. Read the FAQ: {message:id=9360002}

Time out parameters for ABAP and JAVA instance

Hello All,
We are looking for Time out parameters for our ABAP and JAVA instances.
As users are complaining that they are getting time out error
while they are trying to access Cprojects from Portal.
I was able to check/collect the ABAP instance parameters from SMICM Tcode.
Can anybody tell me which parameters we need to look for JAVA instance.
Thanks in advance.
Regards,
Amber S

jstart/shutdownTimeout
(jstartup/shutdown_timeout)
Specifies the shutdown timeout, i.e. the grace period for the AS Java instance to shut down before the Java process terminates itself. Unt is in Seconds. Default is 120
j2ee/ms/connectTimeout
(jstartup/wait_for_scs)
Specifies the timeout for the first connection to the message server. The AS Java instance fails to start if this timeout expires.Unt is in Seconds.Default is 60
j2ee/ms/reconnectTimeout
(jstartup/wait_for_reconnect)
Specifies the timeout for the reconnecting to the message server.The AS Java instance shuts down when this timeout expires.Unt is inSeconds.Default is 3600 (one hour)
Thanks

Problem with database adapter on plsql procedure with in/out parameters

running BPEL 10.1.3.1 and using the database adapter on a plsql procedure with in/out parameters I get errors
the plsql procedure:
create or replace procedure proc_with_clob_inout_parameter(
p_string in varchar2,
p_clob in out clob)
is
begin
p_clob := p_string;
end proc_with_clob_inout_parameter;
In BPEL I call this procedure. When I only assign a value to the p_string parameters (in a BPEL assign) all is well. When I also assign a value to the p_clob parameter the error occurs:
<part name="summary">
<summary>
file:/ora1/app/oracle/as101.3/bpel/domains/digitaaldossier/tmp/.bpel_janb_inout_1.0_f6908ccf864581b7265c362444e88075.tmp/twee.wsdl
[ twee_ptt::twee(InputParameters,OutputParameters) ] - WSIF JCA Execute of
operation 'twee' failed due to: Error while trying to prepare and execute
an API.
An error occurred while preparing and executing the
JANB.PROC_WITH_CLOB_PARAMETER2 API. Cause: java.sql.SQLException: Parameter
Type Conflict [Caused by: Parameter Type Conflict]
; nested exception is:
ORABPEL-11811
Error while trying to prepare and execute an API.
An error occurred while preparing and executing the
JANB.PROC_WITH_CLOB_INOUT_PARAMETER API. Cause: java.sql.SQLException: Parameter
Type Conflict [Caused by: Parameter Type Conflict]
Check to ensure that the API is defined in the database and that the
parameters match the signature of the API. Contact oracle support if error
is not fixable.
</summary>
</part>
In BPEL 10.1.2.0 this isn't a problem. I tested it against a 10.2.0.1 and a 10.2.0.2 database and in both situations I get the error with BPEL 10.1.3.1 and no error with BPEL 10.1.2.0
it appears to be a problem in the database adapter...
anyone with the same problems and/or a solution?

Not of any use to you, but we had exactly the same problem on Friday when we applied AS 10.1.2.2 Patchset on top of BPEL 10.1.2.0.2.
The clob in our pl/sql proc wan't declared as in/out but for some reasons JDeveloper had created a clob on the Output Parameter type in the db partner link xsd. I removed this and it worked. This code had been untouched , and working fine, for months.
I'll be raising an SR today.
Rob J

Using a StoredProcedure with OUT parameters in CrystalReports

Hi All,
I am creating a report using CrystalReport Designer 2008.I have a StoredProcedure which takes 2 input parameters,2 output parameters and a cursor.I am not able to add this SP directly using the DatabaseExpert. if I use
'call SP1(input1,input2,input3,input4,@output1,@output2)' from AddCommand option then it gets added as a Command but the tree under Command does not expand and it does not allow me to use the output parameters in my reports.
Hence,can anyone please help me here such that how should I use this SP with out parameters in my CrystalReports.Also note that I am able to use StoredProcedure with only input parameters,with input parameters and cursor in my CrystalReports.Should I do something extra to add this StoredProcedure in my CrystalReports?
Any help for this issue would be highly appreciated.
Regards.
Ajit

Ajit,
If you are using a Command, you execute a SP in CR with the same syntax that you would in the databases native environment.The only difference is that you'll need to add CR parameters so that the inputs can be added to the SP's input parameters.
So, using your example... 'call SP1({?input1}, {?input2}, {?input3} , {?input4}, output1, output2)'
I'm not familiar with this particular syntax but hopefully you get the idea.
If you want to hard code the input parameters (and not have them prompt in CR), just hard code them in the command.
HTH,
Jason
Edited by: Jason Long on Aug 25, 2010 2:15 PM

Time out parameters for java servers

Dear Gurus,
I'm trying to identify if there are any time out parameters/attributes which can be set for the users at Java level.
I'm wondering if it's possible to limit a user from running a report/query for a long period of time.
Or a parameter to limit the number of sessions one user can have.
The reason I'm asking this is because my java server nodes have experience OutOfMemory errors every once in a while, and this is caused by high workload by the users. I'm trying to prevent or decrease the number of these OutOfMemory errors.
Appreciate any feedback on this.
Thanks.
Regards,
Keat

Hi Mark,
Currently, parameter DefaultExpirationTime = 3600, i think this is okay.
I've located other parameters which might be related to user/system timeout settings.
HttpMonitoringCacheTimeoutMillis = 1500
KeepAliveTimeout = 15
SessionTableTimeout = -1
InputStreamAddTimeout = 0
TransactionTimeout = 0
sap.defaultMaxNumberOfConnections = 10
I'm thinking about tweaking these parameters as well.
Any comments???
Regards,
Keat

IN OUT parameters in Stored Procedures

can anybody explain in detail what is in and out parameters in oracle stored procedures.
thanks in advance

IN is used to specify parameters that are input to the stored procedures. OUT is used to specify parameters that can be returned from the stored procedures.
Please don't get confused with procdures returning value.. You don't need to write a return statement.. just assigning the values to OUT parameters is good ebnough to retireve there values outside stored procedures.
Hope it helps.

SQLJ : sending refcursors via out parameters of PL/SQL functions possible ?

Hello,
in SQLJ it's possible to get a refcursor back from a PL/SQL
function via
the return value(the usual case in the online examples).
Is it also possible to give a refcursor back via an out
parameter
so that the return value could be used for others ways ?
SQLJ generation in JDeveloper handles the first way, but we
didn't
get it to work with the out parameter.
Thank you for your help.

It's certainly possible to have a stored procedure with an OUT parameter that is a REF CURSOR and use that to return data to JDBC. That's actually the most common way that JDBC programmers get ResultSets from stored procedures. I would have to assume that SQLJ would facilitate that?
Is there a reason that you're looking to use a stored function rather than a stored procedure? The latter seems like a much more logical construct when you have OUT parameters. I've never seen a stored function that was defined with any OUT parameters.
Justin
Distributed Database Consulting, Inc.
www.ddbcinc.com

Count of IN/OUT Parameters.

Similar Messages

Maybe you are looking for