Wrong number of parameters

Whats wrong with this code?
     public void updateProduct(String id, String name, String description, String cost){
          Connection conn = null;
          DataSourceManager dataSource = new DataSourceManager();
          conn = dataSource.getConnection();
          PreparedStatement stmt;
          try {
               String updateString = "UPDATE PRODUCT SET PRODUCT_NAME = ?, DESCRIPTION = ?, COST = ? WHERE PRODUCT_ID LIKE ?";
               stmt = conn.prepareStatement(updateString);
               stmt.setString(1, name);
               stmt.setString(2, description);
               stmt.setDouble(3, Double.parseDouble(cost));
               stmt.setString(4, id);
               stmt.executeUpdate(updateString);
               conn.commit();
          } catch (SQLException sqle) {
               sqle.printStackTrace();
I get:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0100E Wrong number of parameters. SQLSTATE=07001
     at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQLExceptionGenerator.java:256)
     at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQLExceptionGenerator.java:193)
     at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(SQLExceptionGenerator.java:444)
     at COM.ibm.db2.jdbc.app.DB2Statement.execute2(DB2Statement.java:435)
     at COM.ibm.db2.jdbc.app.DB2Statement.executeUpdate(DB2Statement.java:381)
     at com.ibm.ejs.cm.cache.CachedStatement.executeUpdate(CachedStatement.java:132)
     at com.ibm.ejs.cm.proxy.StatementProxy.executeUpdate(StatementProxy.java:190)
     at com.bright.coffeeplease.persistence.ProductPersister.updateProduct(ProductPersister.java:114)
     at com.bright.coffeeplease.product.UpdateProductServlet.doGet(UpdateProductServlet.java:24)
     at com.bright.coffeeplease.product.UpdateProductServlet.doPost(UpdateProductServlet.java:12)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:827)
     at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:159)
     at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:286)
     at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:106)
     at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
     at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:1012)
     at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:913)
     at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:403)
     at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:227)
     at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:98)
     at com.ibm.servlet.engine.webapp.InvokerServlet.service(InvokerServlet.java:267)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:827)
     at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:159)
     at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:286)
     at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:106)
     at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
     at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:1012)
     at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:913)
     at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:403)
     at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:227)
     at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:98)
     at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:67)
     at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:123)
     at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
     at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:122)
     at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:315)
     at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:60)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:313)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:242)
     at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)

You don't want to call
stmt.executeUpdate(updateString)
You just want to call executeUpdate() - the prepared statement already knows what you're trying to do.
Hope this helps.
Incidentally, did you really mean "... WHERE PRODUCT_ID LIKE ?" rather than "... WHERE PRODUCT_ID = ?"

Similar Messages

  • Exception has occurred during data insertion ... Wrong number of parameters

    I am using an ADO dataflow source and an ADO dataflow destination to move data from a table on an IBM iSeries DB2 database to another IBM iSeries DB2 database on another machine.  The connection managers for source and destination both use .Net Providers\Odbc
    Data Provider with the Data Source Specification being ODBC connections specified on the Windows Server 2008 r2 machine hosting bids.  All the test connections work...so far so good.
    Issue is when I execute the control flow task the rows get picked up from the source DB2 database no problem but it fails on the insert to the destination DB2 table...The progress tab specifies the exceptions...
    [ADO NET Destination [601]] Error: An exception has occurred during data insertion, the message returned from the provider is: ERROR [07002] [IBM][System i Access ODBC Driver]Wrong number of parameters.
    [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED.  The ProcessInput method on component "ADO NET Destination" (601) failed with error code 0xC020844B while processing input "ADO NET Destination Input" (604). The identified
    component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.  There may be error messages posted before this with more information about the
    failure.
    I put a data viewer on the data flow connection and the records I expect are  getting picked up and look ok. I checked to make sure the source and destination tables have the same number of columns in their record layout and identical data
    types and they look fine.
    Could someone kindly tell me whats going wrong?  Does the error message indicate that some of the columns are getting dropped from the dataset before the insert?
    Thanks much in advance for any help, Roscoe

    Hi Roscoe,
    Glad to hear that you have found the root cause. So, the issue occurs because numeric values with no decimal cannot be inserted into the Decimal data type column in the DB2 table. In SSIS, data type Decimal of DB2 database is mapped to data type DT_NUMERIC.
    To address the issue, you can do a data conversion for the column in question to define its precision and scale such as DT_NUMERIC(9,2) by using the Data Conversion Transformation before the ADO NET Destination.
    Regards,
    Mike Yin
    If you have any feedback on our support, please click
    here
    Mike Yin
    TechNet Community Support

  • Wrong number of parameters exception when using PreparedStatement

    Hi,
    I'm getting Wrong number of parameters exception when using a prepared statement. It's very weird. The code is:
    sqlstmt="update blah1 set blah2=? where blah3=?";
    myps = Conn.prepareStatement(sqlstmt);
    myps.setString(1, p1);
    myps.setInt(2, p2);
    myps.executeUpdate(sqlstmt);
    The error is:
    SQLException: [IBM][CLI Driver] CLI0100E Wrong number of parameters. SQLSTATE=07001:07001
    Could someone please help? Thanks
    Mahdad

    Hi and thanks for the reply.
    Actually this is the try block...
    The variable's defintions are correct.
    PreparedStatement myps;
    try {
    sqlstmt="update blah1 set blah2=? where blah3=?";
    myps = Conn.prepareStatement(sqlstmt);
    myps.setString(1, blah4);
    myps.setInt(2, blah5);
    myps.executeUpdate(sqlstmt);
    catch (SQLException e) {
    System.out.println("SQLException: " + e.getMessage() + ":" + e.getSQLState());
    blah6++;

  • Why 'wrong number of parameters' error in this call to a stored procedure?

    A stored procedure exists that inserts a new record and returns the newly generated record ID. This stored procedure is called from a WinForms application but at the ExecuteNonQuery time an exception is thrown indicating that the wrong number of parameters
    has been supplied. If I take out the one parameter that is marked as ParameterDirection.Output then the ExecuteNonQuery does not throw an exception.
    CREATE PROCEDURE [dbo].[API_InsertIntoManu]
    @Name nvarchar(50),
    @Description nvarchar(2000)
    AS
    SET NOCOUNT ON
    INSERT INTO Manu (
    [Name],
    [Description]
    VALUES (
    @Name,
    @Description
    SELECT SCOPE_IDENTITY() As InsertedID
    END
    GO
    The C# code that calls the above SP looks like this:
    using (SqlConnection conn = new SqlConnection( "<snipped>" ))
    using (SqlCommand cmd = new SqlCommand( "[dbo].[API_InsertIntoManu]", conn ))
    cmd.CommandType = CommandType.StoredProcedure;
    cmd.Parameters.Add( Name, SqlDbType.NVarChar, 50 ).Value = "some name";
    cmd.Parameters.Add( Title, SqlDbType.NVarChar, 200 ).Value = "some title";
    // This parameter is supposed to receive the new row's ID but instead triggers a 'wrong number of args' exception.
    cmd.Parameters.Add( "InsertedID",SqlDbType.Int ).Direction = ParameterDirection.Output;
    conn.Open();
    // This is where the exception gets thrown.
    cmd.ExecuteNonQuery();
    iReturn = (int)cmd.Parameters[InsertedID].Value;
    Richard Lewis Haggard

    In you sp the size of Title var is 2000 and not 200, correct this:
    cmd.Parameters.Add( "@Title", SqlDbType.NVarChar, 200 ).Value
    Fouad Roumieh

  • Wrong Number Of Parameters For A Method

    Exactly like the title. If I pass in too many or too few parameters in a method, am I allowed to add a customized error message?
    JW, Thanks.

    It's not possible to pass in too many or too few characters. The compiler would prevent it, and generate its own error message.
    I suppose you could do something like this if you were using varargs....but why bother?

  • Wrong number of parameters error

    We are using jpub and sqlj in Solaris to generate Java Classes for our app.
    We also have a set of .sql scripts which in effect clone a schema.
    When we run jpub/sqlj against packages in the original schema, everything is fine, but against the clone, while jpub creates sqlj code which is identical to that from the first schema, sqlj complains (when on-line checking is turned on):
    A: "JDBC: reports more than one return value for <function name>" and advises that we update our driver;
    B:"Did not find <func name> with <n> arguments. found <func name> with <n + a bunch> of arguments" and tells us to check the call.
    We have no idea what might be causing this, and when we turn off the on-line checking for sqlj, everything appears to work fine.
    Any ideas/suggestions ?

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by SQLJ Development ([email protected]):
    Mmmh. This may be a bug in the way SQLJ resolves functions/stored procedures. Could you send me your infile/.sql/.sqlj files so that I can reproduce your problem? Thanks!
    In the meantime, if everything works at runtime, you may have to ignore the errors and do your final compile offline.<HR></BLOCKQUOTE>
    I haven't forgotten. We've got a lot of code, and will try to boil down to an illustrative example when we can.
    At the moment, an off-line compile seems to work - though you might want to check my other post today :-)
    null

  • Wrong number or types of parameters after upgrading to ODP 11.2.0.1.1 Beta

    Hi,
    I have the below Oracle procedure with two parameters , the first one i IS TABLE OF number INDEX BY BINARY_INTEGER, and the second one is of type Ref cursor of predifned RECORD type.
    PROCEDURE Proc1(p_proj_comp_no_list IN core_util.ref_t,
    p_proj_comp_post_query_cursor OUT t_proj_comp_post_query_cursor
    ) IS
    This has been working fine while we were using DEVART Oracle drivers. however, as soon we move to ODP 11.2.0.1.1 Beta version we get the below error while executing the procedure via ODP.
    {"ORA-06550: line 1, column 7:\nPLS-00306: wrong number or types of arguments in call to 'PROJ_COMP_POST_QUERY'\nORA-06550: line 1, column 7:\nPL/SQL: Statement ignored"}
    Below is the debug watch result of the two parameters of the COMMAND being executed.
    Best Regards,
    Prabhakar
    +          *base     {P_PROJ_COMP_NO_LIST}     System.Data.Common.DbParameter {Oracle.DataAccess.Client.OracleParameter}*
              ArrayBindSize     null     int[]
              ArrayBindStatus     null     Oracle.DataAccess.Client.OracleParameterStatus[]
              CollectionType     None     Oracle.DataAccess.Client.OracleCollectionType
              DbType     String     System.Data.DbType
              Direction     Input     System.Data.ParameterDirection
              IsNullable     false     bool
              Offset     0     int
              OracleDbType     Long     Oracle.DataAccess.Client.OracleDbType
              OracleDbTypeEx     Long     Oracle.DataAccess.Client.OracleDbType
              ParameterName     "P_PROJ_COMP_NO_LIST"     string
              Precision     0     byte
              Scale     0     byte
              Size     1     int
              SourceColumn     ""     string
              SourceColumnNullMapping     false     bool
              SourceVersion     Current     System.Data.DataRowVersion
              Status     Success     Oracle.DataAccess.Client.OracleParameterStatus
              UdtTypeName     ""     string
    +          Value     {long[1]}     object {long[]}
    +          Static members          
    +          Non-Public members          
    -          [1]     {P_PROJ_COMP_POST_QUERY_CURSOR}     object {Oracle.DataAccess.Client.OracleParameter}
    +          *base     {P_PROJ_COMP_POST_QUERY_CURSOR}     System.Data.Common.DbParameter {Oracle.DataAccess.Client.OracleParameter}*
              ArrayBindSize     null     int[]
              ArrayBindStatus     null     Oracle.DataAccess.Client.OracleParameterStatus[]
              CollectionType     None     Oracle.DataAccess.Client.OracleCollectionType
              DbType     Object     System.Data.DbType
              Direction     Output     System.Data.ParameterDirection
              IsNullable     false     bool
              Offset     0     int
              OracleDbType     RefCursor     Oracle.DataAccess.Client.OracleDbType
              OracleDbTypeEx     RefCursor     Oracle.DataAccess.Client.OracleDbType
              ParameterName     "P_PROJ_COMP_POST_QUERY_CURSOR"     string
              Precision     0     byte
              Scale     0     byte
              Size     0     int
              SourceColumn     ""     string
              SourceColumnNullMapping     false     bool
              SourceVersion     Current     System.Data.DataRowVersion
              Status     Success     Oracle.DataAccess.Client.OracleParameterStatus
              UdtTypeName     ""     string
    +          Value     {}     object {System.DBNull}
    +          Static members          
    +          Non-Public members

    Hi,
    Can you please show the actual code that creates and appends the parameters instead, along with cmd.commandtext?
    Thanks
    Greg
    Edited by: gdarling on Jun 30, 2010 11:54 AM
    Also note that unless you're using Oracle Developer Tools for VS to generate the code, this would probably be more appropriate in the ODP forum:
    ODP.NET

  • Getting error wrong number or type of parameters for EAM_PROCESS_WO_PUB

    Hi All,
    I am Getting error wrong number or type of parameters for EAM_WO_PROCESS_PUB.PROCESS_WO API, pls any body can help me,pls send code for
    EAM_WO_PROCESS_PUB.PROCESS_WO API.
    Thanks&Reagrds,
    Hanimi Reddy.

    Hi srini,
    I developed code for work order api EAM_PROCESS_WO_PUB.PROCESS_MASTER_CHILD_WO following and i am getting error wrong number or types of arguments in call to 'PROCESS_MASTER_CHILD_WO, pls see the code and help me
    CREATE OR REPLACE PROCEDURE SANG_WR_TO_WO_API/*(ERRBUF OUT VARCHAR2, RETCODE OUT VARCHAR2)*/ IS
    v_created_by number;
    v_updated_by number;
    v_updated_name varchar2(30);
    V_ENTITY_ID VARCHAR2(30);
    l_EAM_WO_RELATIONS_TBL EAM_PROCESS_WO_PUB.EAM_WO_RELATIONS_TBL_type ;
    --:= EAM_PROCESS_WO_PUB.g_miss_EAM_WO_RELATIONS_rec;
    l_eam_wo_tbl EAM_PROCESS_WO_PUB.eam_wo_rec_type; --:= EAM_PROCESS_WO_PUB.G_MISS_EAM_WO_rec;
    l_eam_op_tbl EAM_PROCESS_WO_PUB.eam_op_tbl_type ;--:= EAM_PROCESS_WO_PUB.G_MISS_eam_op_tbl;
    l_eam_op_network_tbl EAM_PROCESS_WO_PUB.eam_op_network_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_op_network_tbl;
    l_eam_res_tbl EAM_PROCESS_WO_PUB.eam_res_tbl_type;--:= EAM_PROCESS_WO_PUB.G_MISS_eam_res_tbl;
    l_eam_res_inst_tbl EAM_PROCESS_WO_PUB.eam_res_inst_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_res_inst_tbl;
    l_eam_sub_res_tbl EAM_PROCESS_WO_PUB.eam_sub_res_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_sub_res_tbl ;
    -- l_eam_res_usage_tbl EAM_PROCESS_WO_PUB.eam_res_usage_tbl_type := EAM_PROCESS_WO_PUB.G_MISS_eam_res_usage_tbl;
    l_eam_mat_req_tbl EAM_PROCESS_WO_PUB.eam_mat_req_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_mat_req_tbl ;
    l_eam_direct_items_tbl EAM_PROCESS_WO_PUB.eam_direct_items_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_direct_items_tbl ;
    l_x_eam_wo_tbl EAM_PROCESS_WO_PUB.eam_wo_rec_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_wo_rec;
    l__x_EAM_WO_RELATIONS_TBL EAM_PROCESS_WO_PUB.EAM_WO_RELATIONS_TBL_type ;--:= EAM_PROCESS_WO_PUB.g_miss_EAM_WO_RELATIONS_TBL;
    l_x_eam_op_tbl EAM_PROCESS_WO_PUB.eam_op_rec_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_op_rec ;
    l_x_eam_op_network_tbl EAM_PROCESS_WO_PUB.eam_op_network_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_op_network_tbl;
    l_x_eam_res_tbl EAM_PROCESS_WO_PUB.eam_res_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_res_tbl;
    l_x_eam_res_inst_tbl EAM_PROCESS_WO_PUB.eam_res_inst_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_res_inst_tbl ;
    l_x_eam_sub_res_tbl EAM_PROCESS_WO_PUB.eam_sub_res_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_sub_res_tbl;
    -- l_x_eam_res_usage_tbl EAM_PROCESS_WO_PUB.eam_res_usage_tbl_type := EAM_PROCESS_WO_PUB.G_MISS_eam_res_usage_tbl ;
    l_x_eam_mat_req_tbl EAM_PROCESS_WO_PUB.eam_mat_req_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_mat_req_tbl;
    l_x_eam_direct_items_tbl EAM_PROCESS_WO_PUB.eam_direct_items_tbl_type; --:= EAM_PROCESS_WO_PUB.G_MISS_eam_direct_items_tbl ;
    l_x_return_status VARCHAR2(30);
    l_x_msg_count NUMBER;
    l_x_debug VARCHAR2(30);
    l_output_dir VARCHAR2(30);
    l_debug_filename VARCHAR2(30) ;
    l_debug_file_mode VARCHAR2(30) ;
    CURSOR CUR_WTW IS
    SELECT
    EWR.WIP_ENTITY_ID
    ,EWR.WIP_ENTITY_NAME
    ,EWR.ORGANIZATION_ID
    ,WAC.ORGANIZATION_CODE
    ,EWR.DESCRIPTION
    ,EWR.ASSET_GROUP_ID
    ,EWR.ASSET_NUMBER
    ,EWR.ASSET_NUMBER_DESCRIPTION
    ,WAC.ACCOUNTING_CLASS
    ,WAC.MATERIAL_ACCOUNT
    ,WAC.MATERIAL_OVERHEAD_ACCOUNT
    ,WAC.RESOURCE_ACCOUNT
    ,WAC.OUTSIDE_PROCESSING_ACCOUNT
    ,WAC.MATERIAL_VARIANCE_ACCOUNT
    ,WAC.RESOURCE_VARIANCE_ACCOUNT
    ,WAC.OUTSIDE_PROC_VARIANCE_ACCOUNT
    ,WAC.STD_COST_ADJUSTMENT_ACCOUNT
    ,WAC.OVERHEAD_ACCOUNT
    ,WAC.OVERHEAD_VARIANCE_ACCOUNT
    ,EWR.WORK_REQUEST_OWNING_DEPT_ID
    ,EWR.WORK_REQUEST_OWNING_DEPT
    ,EWR.WORK_REQUEST_PRIORITY_ID
    ,EWR.WORK_REQUEST_PRIORITY
    ,EWR.WORK_REQUEST_STATUS_ID
    ,WAC.ORGANIZATION_NAME
    FROM
    WIP_EAM_WORK_REQUESTS_V EWR
    ,WIPFV_ACCOUNTING_CLASSES WAC
    ,WIP_EAM_PARAMETERS WAP
    WHERE
    EWR.ORGANIZATION_ID = WAC.ORGANIZATION_ID
    AND WAC.ORGANIZATION_ID = WAP.ORGANIZATION_ID
    AND WAC.ACCOUNTING_CLASS = WAP.DEFAULT_EAM_CLASS
    AND EWR.WORK_REQUEST_STATUS = 'Awaiting Work Order';
    BEGIN
    --i number := 1;
    FND_GLOBAL.apps_initialize (1001255, 50326, 700, 0);
    V_CREATED_BY := FND_GLOBAL.USER_ID;
    V_UPDATED_BY := FND_GLOBAL.USER_ID;
    v_updated_name := FND_GLOBAL.USER_name;
    for rec in cur_wtw loop
    l_eam_wo_tbl.WIP_ENTITY_ID := rec.wip_entity_id;
    l_eam_wo_tbl.ORGANIZATION_ID := rec.ORGANIZATION_ID ;
    l_eam_wo_tbl.ASSET_NUMBER := rec.ASSET_NUMBER;
    l_eam_wo_tbl.ASSET_GROUP_ID := rec.ASSET_GROUP_ID ;
    l_eam_wo_tbl.DESCRIPTION := rec.DESCRIPTION ;
    --SELECT WIP_ENTITIES_S.NEXTval INTO V_ENTITY_ID FROM DUAL;
    EAM_PROCESS_WO_PUB.PROCESS_MASTER_CHILD_WO
    (P_PO_IDENTIFIER => 'EAM'
    ,P_API_VERSION_NUMBER => 1.0
    ,P_INIT_MSG_LIST => FALSE
    ,P_EAM_WO_RELATIONS_TBL => l_EAM_WO_RELATIONS_TBL
    ,P_EAM_WO_tbl => l_eam_wo_tbl
    , p_eam_op_tbl => l_eam_op_tbl
    , p_eam_op_network_tbl => l_eam_op_network_tbl
    , p_eam_res_tbl => l_eam_res_tbl
    , p_eam_res_inst_tbl => l_eam_res_inst_tbl
    , p_eam_sub_res_tbl => l_eam_sub_res_tbl
    --, p_eam_res_usage_tbl => l_eam_res_usage_tbl
    , p_eam_mat_req_tbl => l_eam_mat_req_tbl
    , p_eam_direct_items_tbl => l_eam_direct_items_tbl
    , x_eam_wo_tbl => l_x_eam_wo_tbl
    , X_EAM_WO_RELATIONS_TBL => l__x_EAM_WO_RELATIONS_TBL
    , x_eam_op_tbl => l_x_eam_op_tbl
    , x_eam_op_network_tbl => l_x_eam_op_network_tbl
    , x_eam_res_tbl => l_x_eam_res_tbl
    , x_eam_res_inst_tbl => l_x_eam_res_inst_tbl
    , x_eam_sub_res_tbl => l_x_eam_sub_res_tbl
    -- , x_eam_res_usage_tbl =>l_x_eam_res_usage_tbl
    , x_eam_mat_req_tbl => l_x_eam_mat_req_tbl
    , x_eam_direct_items_tbl => l_x_eam_direct_items_tbl
    , x_return_status => l_x_return_status
    , x_msg_count => l_x_msg_count
    ,p_commit =>'N'
    , p_debug => 'N'
    , p_output_dir => NULL
    , p_debug_filename => 'EAM_WO_DEBUG.log'
    , p_debug_file_mode => 'w'
    END LOOP;
    END SANG_WR_TO_WO_API;
    COMMIT;
    Thanks ,
    Hanimi

  • PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMI

    I am trying to submit the payables open interface import program using BPEL process. BUT I am unable to submit the concurrent program. The invoke function is failing with below message.
    [2010/08/25 17:06:22] Faulted while invoking operation "OFAPOPIIMPORT" on provider "OFAPOPIIMPORT".less
    -<messages>
    -<input>
    -<Invoke_1_OFAPOPIIMPORT_InputVariable>
    -<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="InputParameters">
    -<InputParameters xmlns:db="http://xmlns.oracle.com/pcbpel/adapter/db/APPS/XX_BPEL_FND_REQUEST_SUBMIT_REQ/FND_REQUEST-24SUBMIT_REQUEST/" xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/APPS/XX_BPEL_FND_REQUEST_SUBMIT_REQ/FND_REQUEST-24SUBMIT_REQUEST/">
    <db:APPLICATION>200</db:APPLICATION>
    <db:PROGRAM>APXIIMPT</db:PROGRAM>
    <db:DESCRIPTION>Test</db:DESCRIPTION>
    <db:START_TIME/><db:SUB_REQUEST/>
    <db:OperatingUnit>NYSIF</db:OperatingUnit>
    <db:Source>DBL</db:Source>
    <db:Group/>
    <db:BatchName>TESTRAMBPEL1</db:BatchName>
    <db:HoldName/>
    <db:HoldReason/>
    <db:GLDate/>
    <db:Purge>N</db:Purge>
    <db:TraceSwitch>N</db:TraceSwitch>
    <db:DebugSwitch>N</db:DebugSwitch>
    <db:SummarizeReport>N</db:SummarizeReport>
    <db:CommitBatchSize>1000</db:CommitBatchSize>
    <db:UserID>4842</db:UserID>
    <db:LoginID>1683090</db:LoginID>
    </InputParameters>
    </part>
    </Invoke_1_OFAPOPIIMPORT_InputVariable>
    </input>
    -<fault>
    -<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
    -<part name="code">
    <code>6550
    </code>
    </part>
    -<part name="summary">
    <summary>
    file:/C:/product/10.1.3.1/OraBPEL_1/bpel/domains/default/tmp/.bpel_APOPIIMPORT_1.0_91d4c6c1050ed25d005bc0d396a9db24.tmp/OFAPOPIIMPORT.wsdl [ OFAPOPIIMPORT_ptt::OFAPOPIIMPORT(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'OFAPOPIIMPORT' failed due to: Error while trying to prepare and execute an API.
    An error occurred while preparing and executing the APPS.XX_BPEL_FND_REQUEST_SUBMIT_REQ.FND_REQUEST$SUBMIT_REQUEST API. Cause: java.sql.SQLException: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    [Caused by: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    ; nested exception is:
         ORABPEL-11811
    Error while trying to prepare and execute an API.
    An error occurred while preparing and executing the APPS.XX_BPEL_FND_REQUEST_SUBMIT_REQ.FND_REQUEST$SUBMIT_REQUEST API. Cause: java.sql.SQLException: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    [Caused by: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    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>
    -<part name="detail">
    <detail>
    Internal Exception: java.sql.SQLException: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    Error Code: 6550
    </detail>
    </part>
    </remoteFault>
    </fault>
    </messages>
    [2010/08/25 17:06:22] "{http://schemas.oracle.com/bpel/extension}remoteFault" has been thrown. More...
    -<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
    -<part name="code">
    <code>6550
    </code>
    </part>
    -<part name="summary">
    <summary>
    file:/C:/product/10.1.3.1/OraBPEL_1/bpel/domains/default/tmp/.bpel_APOPIIMPORT_1.0_91d4c6c1050ed25d005bc0d396a9db24.tmp/OFAPOPIIMPORT.wsdl [ OFAPOPIIMPORT_ptt::OFAPOPIIMPORT(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'OFAPOPIIMPORT' failed due to: Error while trying to prepare and execute an API.
    An error occurred while preparing and executing the APPS.XX_BPEL_FND_REQUEST_SUBMIT_REQ.FND_REQUEST$SUBMIT_REQUEST API. Cause: java.sql.SQLException: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    [Caused by: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    ; nested exception is:
         ORABPEL-11811
    Error while trying to prepare and execute an API.
    An error occurred while preparing and executing the APPS.XX_BPEL_FND_REQUEST_SUBMIT_REQ.FND_REQUEST$SUBMIT_REQUEST API. Cause: java.sql.SQLException: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    [Caused by: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    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>
    -<part name="detail">
    <detail>
    Internal Exception: java.sql.SQLException: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    Error Code: 6550
    </detail>
    </part>
    </remoteFault>
    I thought I am providing the values for the required parameters. But still I am unable to submit. Could some one help me on fixing this issue?
    Thanks,

    That's probably your problem.
    Look at http://download-west.oracle.com/docs/cd/B31017_01/integrate.1013/b28351/T430238T430241.htm
    Search for "One-time Workaround for Concurrent Programs" in that document.

  • Java Applet in a HTML page: failing with PLS-00306: wrong number of args

    We are trying to use a Java Applet in a HTML page. as our system needs to be able to retrieve a predefined set of data from a third party system that uses Dynamic Data Exchange Protocol (DDE) and are encountering errors from APEX and in IE itself.
    We are using JavaDde from www.nevaobject.com that enables our Java applet to interact with Windows applications (Third Party System) using DDE.
    This functionality is currently used in our Web Form 6i application and we are trying to use the same in the new ApEx application.
    We are using ApEx version : 2.1 and actually aer encountering 2 problems:
    Problem 1: ApEx failing with PLS-00306: wrong number or types of arguments in call to 'ACCEPT'
    Problem 2: IE crashes if Applet used in a complex page with several regions (1 Context, 4 Report Regions, 2 level Tabs, Links)
    This problem does not occur in the page where there is only applet and one region. In the case of complex page the IE crashes if the page is reloaded
    Test scenario:
    1- Create a simple page with the HTML region.
    2- Define the Source of the above region as follows
    <OBJECT CLASSID="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
    CODEBASE="http://java.sun.com/products/plugin/autodl/jinstall-1_4-windows-i586.cab#version=1,4,0,0"
    WIDTH="1"
    HEIGHT="1"
    ID="simpleApplet"
    NAME="simpleApplet">
    <PARAM NAME="code" VALUE="simpleApplet.class" >
    <PARAM NAME="archive" VALUE="simpleApplet.jar" />
    <PARAM NAME="type" VALUE="application/x-java-applet;version=1.4">
    </OBJECT>
    3- Create a simple Java applet "simpleApplet" - for the test its enough if the applet will have just the init method printing out the mesage to the console
    4- Create a Submit Button (not redirect) in Region Header and create unconditional (do not set When Button Pressed property) Page Branch to navigate to another page (the page without the applet)
    6- Run the page and Submit -
    The error below is returned by the engine:
    In our case our applet is called ddeApplet - I do not know why is ApEx passing the Applet's ID down to the wwv_flow.accept method as a parameter
    Tue, 24 Jul 2007 08:15:39 GMT
    ORA-06550: line 7, column 2:
    PLS-00306: wrong number or types of arguments in call to 'ACCEPT'
    ORA-06550: line 7, column 2:
    PL/SQL: Statement ignored
    DAD name: rbdev2_ax
    PROCEDURE : wwv_flow.accept
    URL : http://castor:7778/pls/rbdev2_ax/wwv_flow.accept
    PARAMETERS :
    ============
    P_FLOW_ID:
    147
    P_FLOW_STEP_ID:
    500
    P_INSTANCE:
    6986070096861669560
    P_PAGE_SUBMISSION_ID:
    1005758
    P_REQUEST:
    CRASH
    P_ARG_NAMES:
    100380029717786501
    P_T01:
    147
    P_T02:
    101
    P_T03:
    5000044
    P_T04:
    1
    P_T05:
    S
    DDEAPPLET:
    Ddeapplet[panel0,0,0,1x1,layout=java.awt.BorderLayout,rootPane=javax.swing.JRootPane[,0,0,1x1,layout=javax.swing.JRootPane$RootLayout,alignmentX=null,alignmentY=null,border=,flags=385,maximumSize=,minimumSize=,preferredSize=],rootPaneCheckingEnabled=true]
    P_MD5_CHECKSUM:
    ENVIRONMENT:
    ============
    PLSQL_GATEWAY=WebDb
    GATEWAY_IVERSION=2
    SERVER_SOFTWARE=Oracle HTTP Server Powered by Apache/1.3.19 (Unix) mod_fastcgi/2.2.10 mod_perl/1.25 mod_oprocmgr/1.0
    GATEWAY_INTERFACE=CGI/1.1
    SERVER_PORT=7778
    SERVER_NAME=castor
    REQUEST_METHOD=POST
    QUERY_STRING=
    PATH_INFO=/pls/rbdev2_ax/wwv_flow.accept
    SCRIPT_NAME=/pls
    REMOTE_HOST=
    REMOTE_ADDR=192.168.66.169
    SERVER_PROTOCOL=HTTP/1.1
    REQUEST_PROTOCOL=HTTP
    REMOTE_USER=
    HTTP_CONTENT_LENGTH=661
    HTTP_CONTENT_TYPE=application/x-www-form-urlencoded
    HTTP_USER_AGENT=Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
    HTTP_HOST=castor:7778
    HTTP_ACCEPT=image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, application/x-shockwave-flash, */*
    HTTP_ACCEPT_ENCODING=gzip, deflate
    HTTP_ACCEPT_LANGUAGE=en-us
    HTTP_ACCEPT_CHARSET=
    HTTP_COOKIE=ISCOOKIE=true; LOGIN_USERNAME_COOKIE=rdanko; ORACLE_PLATFORM_REMEMBER_UN=RDANKO:ngrb; WWV_FLOW_USER2=70FBB00945FE46B9; V6_AUTHENTICATION_COOKIE=70FBB00945FE46B9
    Authorization=
    HTTP_IF_MODIFIED_SINCE=
    HTTP_REFERER=http://castor:7778/pls/rbdev2_ax/f?p=147:500:6986070096861669560:::::
    HTTP_SOAPACTION=

    "theArrow",
    It looks like whatever HTML you're including on your page is creating HTML input form elements inside the HTML form "wwv_flow". This form is posted to wwv_flow.accept, and of course, the PL/SQL procedure wwv_flow.accept doesn't know anything these additional arguments/form elements you're attempting to POST.
    Joel

  • TOP n sometimes gives wrong number of lines (SSRS 2008 SP1)

    Hello all,
    a workmate has created a dashboard report which contains (among other items) a top n chart item. The user can select the value of n using a report parameter. We have observered that for some values of n and specific values of the other parameters the chart shows the wrong number of lines (bars), e.g. I choose to select TOP 5, but the chart shows in some cases the TOP 6.
    Is such a behaviour already known?
    I will try to create a minimal sample for reproducing this behaviour during the next few days.
    Thanks in advance and best regards,
    Gerald

    Hi Jerry, I already tried this but for some reosan when i add the second filter data mismatches, I have used sort on $$ which is a requirement in my case.
    Data with one filter($$) and Sort on ($$):
    NBR
    Desc
    QTY
    $$
    Perc
    67
    MG
    MIS
    105
    $7,197.44
    64.02%
    67
    BR
    BRO
    21
    $1,439.49
    12.80%
    67
    CH
    CHI
    10
    $685.47
    6.10%
    67
    CR
    CRA
    7
    $479.83
    4.27%
    67
    LT
    LSE 
    5
    $342.74
    3.05%
    67
    CF
    FINISH
    4
    $274.19
    2.44%
    67
    PW
    PACKED
    3
    $205.64
    1.83%
    67
    BL
    BLIS
    2
    $137.09
    1.22%
    67
    DN
    DENT
    2
    $137.09
    1.22%
    67
    CL
    CLOU
    1
    $68.55
    0.61%
    67
    CP
    PURCHASE
    1
    $68.55
    0.61%
    67
    IC
    CONSTRUCTION
    1
    $68.55
    0.61%
    67
    SH
    SCRA
    1
    $68.55
    0.61%
    67
    SS
    SPLIT
    1
    $68.55
    0.61%
    Data when second filter($$ and Desc) added
    NBR
    Desc
    QTY
    $$
    Perc
    67
    MG
    MIS
    105
    $7,197.44
    64.02%
    67
    CR
    CRA
    7
    $479.83
    4.27%
    67
    LT
    LSE
    5
    $342.74
    3.05%
    67
    PW
    PACKED
    3
    $205.64
    1.83%
    67
    DN
    DENT
    2
    $137.09
    1.22%
    67
    CL
    CLOU
    1
    $68.55
    0.61%
    67
    CP
    PURCHASE
    1
    $68.55
    0.61%
    67
    IC
    CONSTRUCTION
    1
    $68.55
    0.61%
    67
    SH
    SCRA
    1
    $68.55
    0.61%
    67
    SS
    SPLIT
    1
    $68.55
    0.61%
    It displays only ten rows but you can see some of the rows Bro, Chi are missing(not sorted as above) when second filter is added on Desc column

  • Wrong number or types of arguments in call to 'P_RETRIEVE_OPPTY_ORDER_STATU

    I have been strucK at a point in invoking the procedure which has a boolean parameter which when called from java program get error saying that "wrong number or types of arguments in call to 'P_RETRIEVE_OPPTY_ORDER_STATUS'". the procedure is given below along with the calling java code , and the Errors.
    If i change the parameter data type to VARCHAR2 (the parameter hilighted in red) in the in the procedure and invoke it with the same method it works fine, even if i change the "callableStatement.setBoolean(1, true); to callableStatement.setInt(1, 1); it works fine.When i call it with setting the boolean to the procedure from my java i get a error. Im really confused whether is this a issue with oracle? or with java code.
    Please can any body suggest me any kind of solution! to over come this scenario.
    ///// java code
    public void testThePackage() throws ClassNotFoundException { Connection connection = null; connection = (Connection) getConnection(); CallableStatement callableStatement = null; try { callableStatement = connection .prepareCall("{call L_test.p_retrieve_oppty_order_status(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}"); callableStatement.setBoolean(1, true); // callableStatement.setString(1, "YES"); // callableStatement.setInt(1, 1); // callableStatement.setLong(1, 1L); callableStatement.setString(2, "SFA"); callableStatement.setString(3, "123421"); callableStatement.setLong(4, 1L); callableStatement.setLong(5, 123L); callableStatement.setLong(6, 345L); callableStatement.setInt(7, 10); callableStatement.setInt(8, 2435); callableStatement.setInt(9, 5675); callableStatement.registerOutParameter(10, Types.NUMERIC); // on_return_status callableStatement.registerOutParameter(11, Types.VARCHAR); // os_duns_no callableStatement.registerOutParameter(12, Types.VARCHAR); // os_hq_duns_no callableStatement.registerOutParameter(13, Types.NUMERIC); // on_approval_id callableStatement.registerOutParameter(14, Types.NUMERIC); // on_approval_amt callableStatement.registerOutParameter(15, Types.VARCHAR); // os_message callableStatement.registerOutParameter(16, Types.VARCHAR); // os_approval_cd callableStatement.registerOutParameter(17, Types.VARCHAR); // os_security_term_cd callableStatement.registerOutParameter(18, Types.VARCHAR); // action // code callableStatement.registerOutParameter(19, Types.VARCHAR); // action // message // txt callableStatement.execute(); connection.commit(); } catch (SQLException e) { System.out.println(e.getMessage()); } } [/code] /////procedure  CREATE OR REPLACE PACKAGE BODY cust.L_test IS  PROCEDURE p_retrieve_oppty_order_status          (isNonAttilaAttempt boolean          , is_system_cd VARCHAR2          , is_order_id VARCHAR2          , in_oppty_id NUMBER          , in_company_id VARCHAR2          , in_acct_id NUMBER          ,in_local_rev NUMBER          ,in_switched_rev NUMBER          ,in_dedicated_rev NUMBER          , on_return_status  OUT NUMBER          , os_duns_no OUT VARCHAR2          , os_hq_duns_no OUT VARCHAR2          , on_approval_id OUT NUMBER          , on_credit_balance OUT NUMBER            , os_message OUT VARCHAR2      , os_approval_cd OUT VARCHAR2      , os_security_term_cd OUT VARCHAR2      ,os_action_cd  OUT VARCHAR2      ,os_action_txt_msg OUT VARCHAR2) IS      io_return l_cdt_util.return_data_t;            action_cd VARCHAR2(20):= NULL;      flag boolean:=false;  BEGIN  if isNonAttilaAttempt =[color=red]true[/color]  then --'YES'  true  flag:=true;  end if;  insert into example (id,data,deleted) values(1,'Test','YES');        END p_retrieve_oppty_order_status;    END cust.L_test;      CREATE OR REPLACE PACKAGE BODY cust.L_test IS PROCEDURE p_retrieve_oppty_order_status         (isNonAttilaAttempt boolean         , is_system_cd VARCHAR2         , is_order_id VARCHAR2         , in_oppty_id NUMBER         , in_company_id VARCHAR2         , in_acct_id NUMBER         ,in_local_rev NUMBER         ,in_switched_rev NUMBER         ,in_dedicated_rev NUMBER         , on_return_status  OUT NUMBER         , os_duns_no OUT VARCHAR2         , os_hq_duns_no OUT VARCHAR2         , on_approval_id OUT NUMBER         , on_credit_balance OUT NUMBER         , os_message OUT VARCHAR2     , os_approval_cd OUT VARCHAR2     , os_security_term_cd OUT VARCHAR2     ,os_action_cd  OUT VARCHAR2     ,os_action_txt_msg OUT VARCHAR2) IS     io_return l_cdt_util.return_data_t;        action_cd VARCHAR2(20):= NULL;     flag boolean:=false; BEGIN if isNonAttilaAttempt =[color=red]true[/color]  then --'YES'  true flag:=true; end if; insert into example (id,data,deleted) values(1,'Test','YES');       END p_retrieve_oppty_order_status; END cust.L_test;    /////error ORA-06550: line 1, column 7:  wrong number or types of arguments in call to 'P_RETRIEVE_OPPTY_ORDER_STATUS'  line 1, column 7:  PL/SQL: Statement ignored                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    Hi YoungWinston,
    I realy appriciate your comments on the standard of the code , i also accept procedure and code may not be readable,
    but the problem is not because of bloated call its just beacause of the Boolean parameter being passed throught the java code, and where as the SQL/PL does not allow BOOLEAN as paramater, please refer the below link for justification.
    what am expecting is , is there any solution to this problem (not a work arround solution).
    Please provide me with some sort of solution/hints or suggestions in achieving this solution,
    I would realy your effort
    Thanks
    ud
    http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28370/datatypes.htm#CJACJGBG
    Predefined PL/SQL BOOLEAN Data Type
    The BOOLEAN data type stores logical values, which you can use in logical operations. The logical values are the Boolean values TRUE and FALSE and the value NULL.
    The syntax for specifying an BOOLEAN data item is:
    BOOLEAN
    SQL has no data type equivalent to BOOLEAN; therefore you cannot use BOOLEAN variables or parameters in the following:
    SQL statements
    Built-in SQL functions (such as TO_CHAR)
    PL/SQL functions invoked from SQL statements
    You cannot insert the value TRUE or FALSE into a database column. You cannot retrieve the value of a database column into a BOOLEAN variable.
    To represent BOOLEAN values in output, use IF-THEN or CASE constructs to translate BOOLEAN values into another type (for example, 0 or 1, 'Y' or 'N', 'true' or 'false').

  • Oracle XML Gateway- Mapping XML to Oracle Apps API - Wrong Number or types

    XML GATEWAY INBOUND – CALLING AN API (PL/SQL record type IN variable) TO INSERT THE DATA INTO SAMPLE TABLE
    Hi,
    I am using XML Gateway to push data into Oracle Apps using a procedure call with “Record Type” as the parameter. I am getting a “wrong number” or types of arguments mismatch error inspite of following the process described in the Oracle XML Gateway User’s Guide
    Steps followed:
    DB
    1. I Created a sample table XX_CUST_HIST(ID NUMBER, ACCOUNT_NAME VARCHAR2(50), FIRST_NAME VARCHAR2(50), LAST_NAME VARCHAR2(50), TITLE VARCHAR2(50))
    2. I then Created a package ‘XX_XML_DEMO_API’ in which we have defined a record type and a procedure.
    3. The Record type ‘customerRecordType’ holds account_name , first_name, last_name and the title.
    4. The Procedure ‘insert_customer_r’ takes 2 IN arguments :
    1. p_ id number
    2. p_customer customerRecordType
    5. The procedure will insert the values into xx_cust_hist table
    p_id -> id
    p_customer.account_name -> account_name
    p_customer.first_name -> first_name
    p_customer.last_name -> last_name
    p_customer.title -> title
    Now I need to call the procedure ‘XX_XML_DEMO_API . insert_customer_r’ from XML gateway.
    Following are the steps to call the procedure:
    [1] Create DTD
    ELEMENT NEW_CUSTOMER_APIR (DATAAREA)
    ELEMENT DATAAREA (CUSTOMER_DATA)
    ELEMENT CUSTOMER_DATA (ID, CUSTOMER_RECORD)
    ELEMENT ID (#PCDATA) ELEMENT CUSTOMER_RECORD (ACCOUNT_NAME, FIRST_NAME, LAST_NAME, TITLE)
    ELEMENT ACCOUNT_NAME (#PCDATA)
    ELEMENT FIRST_NAME (#PCDATA)
    ELEMENT LAST_NAME (#PCDATA)
    ELEMENT TITLE (#PCDATA)
    [2] Creation of XML map Data Definition type for Source and Destination are set to XML.
    While executing the procedure ‘XX_XML_DEMO_API . insert_customer_r’ in post_process from the message designer, instead of 2 (p_id IN number , p_customer IN customerRecordType) parameters it is showing 6 parameters (p_id IN number, p_customer IN customerRecordType, account_name IN varchar2, first_name IN varchar2, last_name IN varchar2, title IN varchar2). Six parameters are getting mapped, instead of the 2 that the procedure really needs.
    [3] Testing of XML map. Error message in transaction monitor:
    ORA-06550: line 1, column 7: PLS-00306: wrong number or types of arguments in call to 'INSERT_CUSTOMER_R' ORA-06550: line 1, column 7: PL/SQL: Statement ignored -
    ECX_ACTIONS.BIND_PROC_VARIABLES
    The process executed and produced the error message given in the step 3. The standard documentation is unclear on how this should be done. Being a newbie to the XML Gateway technology I am unable to get a clue about what the error message could be and which step of the process produced the message. Could anyone help me to proceed further?
    Thanks in advance.

    Hi Siva,
    It seems like the walletkey property of event type is defined incorrectly. Please try by defining the event as follows:
    <wlevs:property name="walletkey" type="char" length="20"/>
    Use "char" instead of "char[]".
    Best Regards,
    Sandeep

  • FDPSTP failed due to ORA-06550: line1 ,column:" Wrong number of types of ar

    Hi All
    I am tying to submit the concurrent request through buttom, when i press the button.. the request is submitting but showing the error"FDPSTP failed due to ORA-06550: line1 ,column:" Wrong number of types of argument in call"
    What are the paramerter i submited in SRS window( normal submition not throu button) is are equall submition throw button.... And in procedure also i am using errbuf and retcode...
    Can any one help regarding the issue where i am doing the mistake...
    PROCEDURE Einvoice(ERRBUF OUT VARCHAR2,RETCODE OUT VARCHAR2,P_INVOICE_TYPE RA_CUST_TRX_TYPES_all.type%TYPE,
    P_INVOICE_FROM RA_CUSTOMER_TRX_PARTIAL_V.TRX_NUMBER%TYPE,
    P_INVOICE_TO RA_CUSTOMER_TRX_PARTIAL_V.TRX_NUMBER%TYPE,
    P_CUSTOMER_ID RA_CUSTOMER_TRX_PARTIAL_V.SOLD_TO_CUSTOMER_ID%TYPE,
    P_DOCUMENT_NUM NUMBER,
    P_reprint_flag VARCHAR2
    In the button trigger
    FND_REQUEST.SUBMIT_REQUEST('GETSAR'
    ,'EINVOICE'
    ,NULL ,NULL ,FALSE
    ,:main_b.invoice_type
    ,to_number(:main_b.From_Invoice_number)
    ,to_number(:main_b.to_invoice_number)
    ,:main_b.customer_id
    ,to_number(:main_b.document_no_from)
    ,:main_b.reprint_flag
    ,'') up to 100 parameters
    We need to change any datatypes in procedure ?????????????

    Duplicate post.
    "FDPSTP failed due to ORA-06550: line1 ,column:" Wrong number of types of
    "FDPSTP failed due to ORA-06550: line1 ,column:"   Wrong number of types of

  • PLS-00306: wrong number or types of arguments in call

    Hi,
    Oracle9i
    created a procedure which will retrieve the records.
    As the procedure is to only retrieve the records so it does not have any IN parameters
    But on executing the procedure gets the below error:
    PLS-00306: wrong number or types of arguments in call to 'GET_PRODUCT_DETAILS'
    I have called the procedure as below:
    =======================
    Declare
    v_cur ...%type;
    BEGIN
    Package_name.GET_PRODUCT_DETAILS(v_cur);
    END;
    Procedure Body
    ==========
    create or replace PROCEDURE GET_PRODUCT_DETAILS( v_cur OUT      Cursor)
    is
    begin
    end;
    /

    Try creating the procedure with the out parameter as sys_refcursor.
    create or replace PROCEDURE GET_PRODUCT_DETAILS( v_cur OUT sys_refCursor)
    And declare the variable in your outer block also as sys_refcursor.
    Declare
    v_cur sys_refcursor;
    BEGIN
    Package_name.GET_PRODUCT_DETAILS(v_cur);
    END;
    Of course this would require that your actual procedure GET_PRODUCT_DETAILS should have a statement like
    " open V_cur for some select statement that you use to retrieve the records".
    You could also create GET_PRODUCT_DETAILS with the same %type decalration which you use in the outer block
    eg
    create or replace PROCEDURE GET_PRODUCT_DETAILS( v_cur OUT x.y%type)
    Declare
    v_cur x.y%type;
    BEGIN
    Package_name.GET_PRODUCT_DETAILS(v_cur);
    END;
    /

Maybe you are looking for