Error while executing Guided Procedures Action

Hello,
We are getting the following error when a user is trying to execute an Action in the Guided Procedures Process:
"Cannot complete Action: Activity could not be read".
What can be causing this?
Any help would be highly Appreciated.

Hello,
This is more than likely due to an inconsistency of a GP object at database level. I suggest opening an OSS ticket as this would require detailed analysis.
Thanks and best regards,
Carl Connolly
Senior Support Consultant - Netweaver Web Application Server
AGS Primary Support, Global Support Centre Ireland
Guided Procedures trouble shooting guide:
www.sdn.sap.com/irj/scn/wiki?path=/display/JSTSG/%2528GP%2529Home

Similar Messages

  • Error While executing a procedure

    Hello FOlks,
    When i try to execute this procedure below i get the error saying "Compiled with errors"
    ORA--00942-Table or View does not exist
    SQL Statement ignored at Line 17.
    I tried querying the table and it returns no data. How do i debug this error.
    create or replace procedure Load_FADM_Staging_Area_test(p_data_load_date date) is
    v_start_date                date;
    v_end_date                  date;
    begin
    if  p_data_load_date is null then
        select (sysdate - 7), (sysdate - 1) into v_start_date, v_end_date from dual;
      elsif p_data_load_date is not null then
       select (p_data_load_date - 7), (p_data_load_date - 1) into v_start_date, v_end_date from dual;
      else
        raise_application_error('-20042', 'Data control - GetDataControlAuditData : Date parameter must be a date of this or a previous week.');
      end if;
    insert into STAGE_FADM_HRI_STAGE_BILL
    (select
    a.batch_id 
    ,a.beginning_service_date 
    ,a.bill_id 
    ,a.bill_method 
    ,a.bill_number 
    ,a.bill_received_date 
    ,a.bill_status 
    ,a.bill_type 
    ,a.change_oltp_by 
    ,a.change_oltp_date 
    ,a.client_datafeed_code 
    ,a.client_id 
    ,a.created_date 
    ,a.date_of_incident 
    ,a.date_paid 
    ,a.deleted_oltp_by 
    ,a.deleted_oltp_date 
    ,a.duplicate_bill 
    ,a.ending_service_date 
    ,a.event_case_id 
    ,a.event_id 
    ,a.from_oltp_by 
    ,a.oltp_bill_status 
    ,a.review_status 
    ,'HRI' schema_name
    , sysdate Load_date
    ,'ETLPROCESS001' Load_user
    ,sysdate
    from stage_bill@hri1_read_only_remote a
    where
    --created_date >= to_date('20101031 235959', 'YYYYMMDD HH24MISS')
    created_date >= v_start_date
    and
    --created_date <= to_date('20101111 235959', 'YYYYMMDD HH24MISS')
      created_date <= v_end_date
    and not exists
    (select
    b.batch_id 
    ,b.beginning_service_date 
    ,b.bill_id 
    ,b.bill_method 
    ,b.bill_number 
    ,b.bill_received_date 
    ,b.bill_status 
    ,b.bill_type 
    ,b.change_oltp_by 
    ,b.change_oltp_date 
    ,b.client_datafeed_code 
    ,b.client_id 
    ,b.created_date 
    ,b.date_of_incident 
    ,b.date_paid 
    ,b.deleted_oltp_by 
    ,b.deleted_oltp_date 
    ,b.duplicate_bill 
    ,b.ending_service_date 
    ,b.event_case_id 
    ,b.event_id 
    ,b.from_oltp_by 
    ,b.oltp_bill_status 
    ,b.review_status
    ,b.Row_Effective_Date
    from STAGE_FADM_HRI_STAGE_BILL b))
    select
    e.action_plan  e_action_plan
    ,e.action_plan_status e_action_plan_status
    ,e.batch_id e_batch_id
    ,e.client_cause_code e_client_cause_code
    ,e.client_id e_client_id
    ,e.client_datafeed_code e_client_datafeed_code
    ,e.client_policy_identifier e_client_policy_identifier
    ,e.close_date e_close_date
    ,e.created_date e_created_date
    ,e.date_of_incident e_date_of_incident
    ,e.date_typed e_date_typed
    ,e.discovery_source e_discovery_source
    ,e.employer_group_id e_employer_group_id
    ,e.event_id e_event_id
    ,e.event_status_code  e_event_status_code
    ,e.event_type_code e_event_type_code
    ,e.exclude_from_invoice e_exclude_from_invoice
    ,e.from_ncoa_date e_from_ncoa_date
    ,e.group_contract_funding_type e_group_contract_funding_type
    ,e.hmo_ppo_indemnity_type e_hmo_ppo_indemnity_type
    ,e.insurance_product_name e_insurance_product_name
    ,e.insured_termination_date e_insured_termination_date
    ,e.invoice_date e_invoice_date
    ,e.letter_status e_letter_status
    ,e.letter_status_date e_letter_status_date
    ,e.liability_analysis e_liability_analysis
    ,e.loss_city e_loss_city
    ,e.loss_description e_loss_description
    ,e.loss_state_code e_loss_state_code
    ,e.manually_moved e_manually_moved
    ,e.moved_by_user_id e_moved_by_user_id
    ,e.ncoa_code e_ncoa_code
    ,e.next_steps e_next_steps
    ,e.open_date e_open_date
    ,e.policy_holder_address1 e_policy_holder_address1
    ,e.policy_holder_address2 e_policy_holder_address2
    ,ec.action_plan
    ,ec.action_plan_status
    ,ec.batch_id
    ,ec.case_status_code
    ,ec.client_datafeed_code
    ,ec.client_id
    ,ec.client_party_identifier
    ,ec.close_date
    ,ec.created_date
    ,ec.damaged_party_address1
    ,ec.damaged_party_address2
    ,ec.damaged_party_city
    ,ec.damaged_party_dob
    ,ec.damaged_party_first_name
    ,ec.damaged_party_gender
    ,ec.damaged_party_last_name
    ,ec.damaged_party_ssn
    ,ec.damaged_party_state_code
    ,ec.damaged_party_zip
    ,ec.deductible
    ,ec.deductible_applied
    ,ec.deductible_recovered
    ,ec.deductible_recovered_full
    ,ec.event_case_id
    ,ec.event_id
    ,ec.fee_schedule_code
    ,ec.internal_coverage_code
    ,ec.litigation_flag
    ,ec.loss_injury_description
    ,ec.next_steps
    ,ec.open_date
    ,ec.payment_coverage_code
    ,ec.pursuit_level_code
    ,ec.reject_code
    ,ec.reject_comments
    ,ec.reject_date
    ,ec.reject_date
    ,ec.reject_user_id
    ,ec.setup_type
    ,ec.tot_paid_at_close
    ,eccf.Client_field_data  eccf_client_fleld_data
    ,eccf.Client_field_name eccf_client_field_name
    ,eccf.Client_id eccf_client_id
    ,eccf.Event_case_id eccf_event_case_id
    ,ecf.client_field_data  ecf_client_field_data
    ,ecf.client_field_name ecf_client_field_name
    ,ecf.client_id ecf_client_id
    ,ecf.event_id  ecf_event_id
    from
    event@hri1_read_only_remote e,
    event_case@hri1_read_only_remote ec,
    event_case_client_field@hri1_read_only_remote eccf,
    event_client_field@hri1_read_only_remote ecf,
    stg_fadm_hri_stage_bill sb
    where
    e.event_id = ec.event_id and
    e.event_id = ecf.event_id  and
    ec.event_case_id = eccf.event_case_id and
    e.event_id = ecf.event_id and
    e.client_id = ecf.client_id and
    e.client_id = ec.client_id and
    ec.client_id = ecf.client_id and
    e.event_id = sb.event_id  and
    ec.event_case_id = sb.event_case_id and
    eccf.event_case_id = sb.event_case_id and
    ecf.event_id = sb.event_id;
    end Load_FADM_Staging_Area_TEST;

    Just noticed
    I tried querying the table and it returns no data.Could be your NOT EXISTS clause, you are missing something? - "Something" exists, unless the table is empty.
    Should probably be something like:
    AND NOT EXISTS (SELECT NULL -- You are actually not selecting anything, just probing for existence
                      WHERE  <<Correlation to table "a">>Furthermore, you'll never manage to compile the procedure since your second select does not select INTO anything.
    (A more apprpriate subject would be "Error while compiling a procedure".)
    Finally, When would the ELSE be reached here?
    if p_data_load_date IS NULL then
        select (sysdate - 7), (sysdate - 1) into v_start_date, v_end_date from dual;
    elsif p_data_load_date IS NOT NULL then
        select (p_data_load_date - 7), (p_data_load_date - 1) into v_start_date, v_end_date from dual;
    ELSE
        raise_application_error('-20042', 'Data control - GetDataControlAuditData : Date parameter must be a date of this or a previous week.');
    end if;Regards
    Peter

  • Gettng Error while executing the procedure(oracle 10.2.0.3.0)

    Hi all,
    I am getting following error While executing the package .
        PLS-00103: Encountered the symbol "Truncate" when expecting one of
             the following:
             * & = - + ; < / > at in is mod remainder not rem return
             returning <an exponent (**)> <> or != or ~= >= <= <> and or
             like LIKE2_ LIKE4_ LIKEC_ between into using || multiset bulk
             member SUBMULTISET_I have written follwing query in the package body.
    EXECUTE IMMEDIATE 'TRUNCATE TABLE FORT ';
    EXECUTE IMMEDIATE '
         INSERT INTO FORT (CID,CODE,DESC,SCODE,SES,T_DT,SDN,LANG)
         SELECT
           SERVICES.CID                                                     CID,
           PROFILE.FUCODE                                               CODE,
           TO_DATE(SUBSTR(SERVICES.STAT_CHNG,-7,6),'YYMMDD')   T_DT,
           PHOR.NUM                                                               SDN,
           C_ALL.cLANGUAGE                                      LANG
         FROM
          SERVICES      .....Please give me the solution for this .
    Thank y ou
    Edited by: user636482 on Apr 10, 2009 1:08 AM

    I am getting following errors if I gave " ' " after not null.
    LINE/COL ERROR
    42/8     PLS-00103: Encountered the symbol "AND" when expecting one of the
             following:
             begin case declare end exception exit for goto if loop mod
             null pragma raise return select update while with
             <an identifier> <a double-quoted delimited-identifier>
             <a bind variable> << close current delete fetch lock insert
             open rollback savepoint set sql execute commit forall merge
             pipe
    42/56    PLS-00103: Encountered the symbol "A" when expecting one of the
             following:
    LINE/COL ERROR
             ) , * & | = - + < / > at in is mod remainder not rem => ..
             <an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
             LIKE4_ LIKEC_ between || multiset member SUBMULTISET_
             The symbol ", was inserted before "A" to continue.
    42/74    PLS-00103: Encountered the symbol "D" when expecting one of the
             following:
             * & - + ; / at mod remainder rem return returning
             <an exponent (**)> and or || multiset
             The symbol "* was inserted before "D" to continue.
    LINE/COL ERROR
    45/6     PLS-00103: Encountered the symbol "COMMIT"
    52/3     PLS-00103: Encountered the symbol "PROCEDURE" when expecting one
             of the following:
             end not pragma final instantiable order overriding static
             member constructor map
             The symbol "static" was substituted for "PROCEDURE" to continue.
    85/8     PLS-00103: Encountered the symbol "AND" when expecting one of the
             following:
             begin case declare end exception exit for goto if loop mod
             null pragma raise return select update while with
    LINE/COL ERROR
             <an identifier> <a double-quoted delimited-identifier>
             <a bind variable> << close current delete fetch lock insert
             open rollback savepoint set sql execute commit forall merge
             pipe
    85/56    PLS-00103: Encountered the symbol "A" when expecting one of the
             following:
             ) , * & | = - + < / > at in is mod remainder not rem => ..
             <an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
             LIKE4_ LIKEC_ between || multiset member SUBMULTISET_
             The symbol ", was inserted before "A" to continue.
    LINE/COL ERROR
    85/74    PLS-00103: Encountered the symbol "D" when expecting one of the
             following:
             * & - + ; / at mod remainder rem return returning
             <an exponent (**)> and or || multiset
             The symbol "* was inserted before "D" to continue.
    88/8     PLS-00103: Encountered the symbol "COMMIT"
    95/3     PLS-00103: Encountered the symbol "PROCEDURE" when expecting one
             of the following:
             end not pragma final instantiable order overriding static
    LINE/COL ERROR
             member constructor map
             The symbol "static" was substituted for "PROCEDURE" to continue.
    133/3    PLS-00103: Encountered the symbol "PROCEDURE" when expecting one
             of the following:
             end not pragma final instantiable order overriding static
             member constructor map
             The symbol "static" was substituted for "PROCEDURE" to continue.
    169/3    PLS-00103: Encountered the symbol "PROCEDURE" when expecting one
             of the following:with out adding " ' " I am getting the previous error which I mentioned in Previous thread(TRUNCATE)
    Thank you

  • Getting ORA-06512/ORA-00972 ERROR WHILE EXECUTING THE PROCEDURE????

    Hi ,
    while executing this procedure , I am getting follwoing errors:
    Create or Replace procedure ADD_CUSTOM_INDEX is
    INDX_NOT_EXIST Number;
    CREATE_SQL_STATMENT VARCHAR2(1500);
    ALTER_SQL_STATMENT VARCHAR2(150);
    CURSOR C1 IS select INDEX_NAME,CREATE_DDL FROM W_CUSTOM_TEST, WC_COMPANY_G WHERE W_CUSTOM_TEST.SYS_TENANT_ID = WC_COMPANY_G.BU_ID;
    BEGIN
    for V_ROW in C1 loop
         SELECT COUNT(USER_INDEXES.INDEX_NAME) INTO INDX_NOT_EXIST FROM USER_INDEXES WHERE USER_INDEXES.INDEX_NAME = V_ROW.index_name;
         IF INDX_NOT_EXIST = 0 THEN
         CREATE_SQL_STATMENT := ''|| '"'|| V_ROW.CREATE_DDL ||'"' ||'PARALLEL NOLOGGING';
         EXECUTE IMMEDIATE CREATE_SQL_STATMENT;
         ALTER_SQL_STATMENT := 'ALTER INDEX ' ||'"'|| V_ROW.INDEX_NAME ||'"'|| ' NOPARALLEL LOGGING';
         EXECUTE IMMEDIATE ALTER_SQL_STATMENT;
         END IF;
    END LOOP;
    END ADD_CUSTOM_INDEX;
    ERROR at line 1:
    ORA-00972: identifier is too long
    ORA-06512: at "LOLAP.ADD_CUSTOM_INDEX", line 13
    ORA-06512: at line 1.
    sturtuce of W_custom_test table is as below:
    CREATE TABLE "LOLAP"."W_CUSTOM_TEST"
    ("INDEX_NAME" VARCHAR2(30) NOT NULL ENABLE,
         "SYS_TENANT_ID" VARCHAR2(15) NOT NULL ENABLE,
    "CREATE_DDL" VARCHAR2(1200),
    "COMMENTS" VARCHAR2(200),
         "STAT_CD" VARCHAR2(30) DEFAULT 'Active' NOT NULL ENABLE,
         "CREATED" DATE DEFAULT SYSDATE NOT NULL ENABLE,
         "LAST_UPD" DATE DEFAULT SYSDATE NOT NULL ENABLE
    Any Pointer??????

    Hi
    Instead of giving as below, go for the not null constraints.
    "STAT_CD" VARCHAR2(30) DEFAULT 'Active' NOT NULL ENABLE,
    "CREATED" DATE DEFAULT SYSDATE NOT NULL ENABLE,
    "LAST_UPD" DATE DEFAULT SYSDATE NOT NULL ENABLE
    That should help
    Regards
    Sudheer

  • Runtime error while executing New Hire action in PA40

    Hi All,i am getting short dump while executing PA40 for new hire action typecan anyone look into this and guide as i am new to HCMNote: getting dump only for one user id for rest all other user id i am not getting dump.
    Category               ABAP Programming Error                                                      
    Runtime Errors         SYNTAX_ERROR                                                                
    ABAP Program           /1PAPAXX/HDR_21000A                                                         
    Application Component  Not Assigned                                                                
    Date and Time          21.08.2014 14:07:03                                                         
    Short text                                                                                       
        Syntax error in program "/1PAPAXX/HDR_21000A ".                                              
    What happened?                                                                                   
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
        The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in                     
        include "/1PAPAXX/HDR_21000AO01 " in                                                        
        line 52:                                                                                     
        ""LV_LENGTH" has already been declared"                                                      
        The include has been created and last changed by:                                            
        Created by: "HCM04 "                                                                         
        Last changed by: "HCM03 "                                                                    
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
    What can you do?                                                                                 
        Please eliminate the error by performing a syntax check                                      
        (or an extended program check) on the program "/1PAPAXX/HDR_21000A ".                        
        You can also perform the syntax check from the ABAP Editor.                                  
        If the problem persists, proceed as follows:                                                 
        Note down which actions and inputs caused the error.                                         
        To process the problem further, contact you SAP system                                       
        administrator.                                                                               
        Using Transaction ST22 for ABAP Dump Analysis, you can look                                  
        at and manage termination messages, and you can also                                         
        keep them for a long time.                                                                   
    Error analysis                                                                                   
        The following syntax error was found in the program /1PAPAXX/HDR_21000A :                    
        ""LV_LENGTH" has already been declared"                                                      
    How to correct the error                                                                         
        Probably the only way to eliminate the error is to correct the program.                      
        If you cannot solve the problem yourself and want to send an error                           
        notification to SAP, include the following information:                                      
        1. The description of the current problem (short dump)                                       
           To save the description, choose "System->List->Save->Local File                           
        (Unconverted)".                                                                              
        2. Corresponding system log                                                                  
           Display the system log by calling transaction SM21.                                       
           Restrict the time interval to 10 minutes before and five minutes                          
        after the short dump. Then choose "System->List->Save->Local File                            
        (Unconverted)".                                                                              
        3. If the problem occurs in a problem of your own or a modified SAP                          
        program: The source code of the program                                                      
           In the editor, choose "Utilities->More                                                    
        Utilities->Upload/Download->Download".                                                       
        4. Details about the conditions under which the error occurred or which                      
        actions and input led to the error.                                                          
    System environment                                                                               
        SAP Release..... 731                                                                         
        SAP Basis Level. 0007                                                                        
        Application server... "dc-ds-erp"                                                            
        Network address...... "172.16.23.111"                                                        
        Operating system..... "Linux"                                                                
        Release.............. "3.0.13-0.27-default"                                                  
        Hardware type........ "x86_64"                                                               
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 1                                                                      
        Shortdump setting.... "full"                                                                 
        Database server... "dc-ds-erp"                                                               
        Database type..... "ORACLE"                                                                  
        Database name..... "ECD"                                                                     
        Database user ID.. "SAPSR3"                                                                  
        Terminal.......... "NLC-HP"                                                                  
        Char.set.... "C"                                                                             
        SAP kernel....... 720                                                                        
        created (date)... "Sep 14 2013 06:16:24"                                                     
        create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"                            
        Database version. "OCI_112, 11.2.0.3.0, V1, default"                                         
        Patch level. 500                                                                             
        Patch text.. " "                                                                             
        Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"              
        SAP database version. 720                                                                    
        Operating system..... "Linux 2.6, Linux 3"                                                   
        Memory consumption                                                                           
        Roll.... 0                                                                                   
        EM...... 37708200                                                                            
        Heap.... 0                                                                                   
        Page.... 106496                                                                              
        MM Used. 4666776                                                                             
        MM Free. 3709976                                                                             
    User and Transaction                                                                             
        Client.............. 210                                                                     
        User................ "HCM03"                                                                 
        Language key........ "E"                                                                     
        Transaction......... "PA40 "                                                                 
        Transaction ID...... "53EF470299AB5D67E1000000AC10176F"                                      
        EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"                                  
        EPP Connection ID....... 00000000000000000000000000000000                                    
        EPP Caller Counter...... 0                                                                   
        Program............. "SAPFP50M"                                                              
        Screen.............. "MP000000 1000"                                                         
        Screen Line......... 3                                                                       
        Debugger Active..... "none"                                                                  
    Information on where terminated                                                                  
        Termination occurred in the ABAP program "SAPFP50M" - in                                     
        "GET_HEADER_WITH_TCLAS".                                                                    
        The main program was "MP000000 ".                                                            
        In the source code you have the termination point in line 146                                
        of the (Include) program "FP50MDHD".                                                         
    Source Code Extract                                                                              
    Line
    SourceCde                                                                                  
      116
      CALL FUNCTION 'HR_HEADER_GET'                                                            
      117
          EXPORTING                                                                            
      118
               DHDID                    = FHD_HID                                              
      119
               BEGDA                    = BEGDA                                                
      120
               TCLAS                    = TCLAS                                                
      121
    * Es wird nur einer der folgenden 3 Parameter benutzt.                                     
      122
    * Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.                                 
      123
    * Der erste der nicht initial ist wird ausgewertet.                                        
      124
    *           MOLGA                   =                                                      
      125
               P0001                    = P0001                                                
      126
               PERNR                    = PSPAR-PERNR                                          
      127
          IMPORTING                                                                            
      128
               PROG                     = HEADER_PROG                                          
      129
               DNUM                     = HEADER_DYNNR                                         
      130
           EXCEPTIONS                                                                          
      131
                HEADER_DEACTIVATED          = 1                                                
      132
                HEADER_UNKNOWN              = 2                                                
      133
                HEADER_GENERATE_DEACTIVATED = 3                                                
      134
                HEADER_GENERATE_FAILED      = 4                                                
      135
                INTERNAL_ERROR              = 5                                                
      136
                OTHERS                      = 6.                                               
      137
      138
      IF NOT SY-SUBRC IS INITIAL.                                                              
      139
    * Bei Problemen gibt's eben ein leeres Dynpro.                                             
      140
        HEADER_PROG = 'SAPMP50A'.                                                              
      141
        HEADER_DYNNR = '0090'.                                                                 
      142
      ELSE.  " NOT sy-subrc IS INITIAL.                                   "                    
      143
    * Dann setzen wir jetzt auch noch das Datum fest.                                          
      144
        PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.                         
      145
    * Und schalten auf Uebergabe der PERNR mit globalen Variablen.                             
    >>>>>
        PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).                                       
      147
      ENDIF.  " (ELSE) NOT sy-subrc IS INITIAL.                           "                    
      148
    * Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.                         
      149
    * Wird mit Einfuehrung des Headerobjekts obsolet.                                          
      150
      PERFORM REMEMBER_HEADER  "                             "XYVPH4K015649                    
      151
        USING HEADER_PROG HEADER_DYNNR 'S'.  "               "XYVPH4K015649                    
      152
    ENDFORM.                                                                                   
      153
      154
    *       FORM RE588I                                                   *                    
      155
      156
      157
      158
    *  -->  T588I_DHDID                                                   *                    
      159
    *  -->  T588I_MOLGA                                                   *                    
      160
    *  -->  T588I_TCLAS                         

    Implement SAP Note 1004280.. your issue if fixed
    If your issue is resolved request you to close the thread or else free feel to touch base
    BR
    Anil

  • Error while executing the procedure

    Hi,
    I tried the following example it's compiled but while executing giving the errors
    create or replace PROCEDURE createRZGSet (
            rNm IN VARCHAR2,
            rDsc IN VARCHAR2,
            rId OUT NUMBER
        ) IS
            cId INTEGER;       
        BEGIN
            cId := 1;       
            SELECT q_id.NEXTVAL
              INTO rId
              FROM DUAL;
            INSERT INTO t_set (rid,
    r_nm,
    r_dsc,
    o_id,
    flag)        VALUES (rId,rNm,rDsc,cid,'P');
        END;
    /The above is compiled ... but while executing
    SQL> declare
      2   optval number;
      3  begin
      4   execute createRZGSet('myp','miyapur',optval);
      5  dbms_output.put_line('val returned is:'||optval);
      6  end;
      7  /
    execute createRZGSet('myp','miyapur',optval);
    ERROR at line 4:
    ORA-06550: line 4, column 10:
    PLS-00103: Encountered the symbol "CREATERZGSet" when expecting one
    of the following:
    := . ( @ % ; immediate
    The symbol ":=" was substituted for "CREATERZGSet" to continue.could you please hint me in this error..
    thanx

    The above is compiled ... but while executing
    SQL> declare
    2   optval number;
    3  begin
    4   execute createRZGSet('myp','miyapur',optval);
    5  dbms_output.put_line('val returned is:'||optval);
    6  end;
    7  /remove the execute key word. it belongs to SQL Plus. in pl/sql you can just give the procedure name thats enought.
    SQL> declare
      2   optval number;
      3  begin
      4   createRZGSet('myp','miyapur',optval);
      5  dbms_output.put_line('val returned is:'||optval);
      6  end;
      7  /

  • Error while executing PlSQL Procedure

    Hi Chris,
    Procedure SPR_VISAMAST_SWITCHCATEGORIZE is created in the TimesTen interchange user. and all object used by this procedure also cached in the TimesTen.
    While executing it is giving error.
    I traced out where execution is failing, i found that update query on cached table it is giving error.
    Command> DECLARE
    > SOUTPUT VARCHAR2(4000);
    > BEGIN
    > INTERCHANGE.SPR_VISAMAST_SWITCHCATEGORIZE('123456', 'SWTCH.030709', 'v2.01', 'fl.01' , 'v2.02' , '1' , SOUTPUT);
    > END;
    > /
    5213: Bad Oracle login error in OCISessionBegin(): ORA-01017: invalid username/password; logon denied rc = -1
    5131: Cannot connect to backend database: OracleNetServiceName = "geni11g", uid = "INTERCHANGE", pwd is hidden, TNS_ADMIN = "/u01/app/oracle/product/11.1.0/db_1/network/admin", ORACLE_HOME= "/u01/app/oracle/product/11.1.0/db_1"
    8507: ORA-06512: at "INTERCHANGE.SPR_VISAMAST_SWITCHCATEGORIZE", line 39
    8507: ORA-06512: at line 4
    The command failed.
    Please tell me how to solve this issue.

    So when you execute this procedure it is actually executing as user INTERCHANGE. Any objects that the procedure references whcih do not include an explicit owner will assume the object is owned by user INTERCHANGE and this may mean that an object cannot be found.
    Here is an example...
    Let's say you have a cached table in TimesTen and the table is owned by the user 'CACHEUSER' - CACHEUSER.MyCachedtable.
    If you create a PL/SQL procedure owned by the user INTERCHANGE - INTERCHANGE.Someprocedure and within thie procedure include a statement like SELECT * FROM MyCachedtable then when the procedure is executed it will by default always look for the table INTERCHANGE.MyCachedTable even if the user executing the procedure is 'CACHEUSER'. As a result, it would not find the table MyCachedTable in TimesTen and, depending on the setting for PassThrough it might try and go to Oracle for this table.
    Another possibility is that the PL/SQL procedure is performing some cache operation that requires interaction with the Oracle DB and you did not include 'OraclePWD=xxx' to provide the password for Oracle when you connected. Remember that the procedure will be executing, by default, as the user INTERCHANGE not as the user 'CACHEUSER'.
    Chris

  • Invalid arguments error while executing oracle procedure

    Dear all,
    we have a table hr_emp with fields ecode, ename, edoj.
    the following procedure we created to return the table data to our .net app.
    CREATE OR REPLACE
    PACKAGE pname AS
    TYPE T_hr_cursor IS REF CURSOR;
    PROCEDURE get_hr_list (P_hrlist OUT T_hr_cursor);
    END HRPACK;
    create or replace PACKAGE BODY pname AS
         PROCEDURE get_hr_list (P_hrlist OUT T_hr_cursor)
         IS
         BEGIN
         OPEN P_hrlist FOR
              SELECT *
                   FROM Hr_Emp WHERE edoj>='01-jan-2009';
         END get_hr_list;
    END;
    these code edited in a single file [both package and package body] and created successfully.
    but, while executing, by typing execute get_hr_list, ORA-00304 error, invalid arguments, is coming. How to resolve this, please help.
    also, in sql developer 1.5.3, when we create this, another error is ciming like 'source doesnot have a runnable target'.
    Where is the issue? please help

    Yes, its great dear...
    sqlplus>
    declare
    hr_cursor hrmain.t_hr_cursor;
    begin
    pname.get_hr_list(hr_cursor);
    end;
    Its worked as i got 'pl/sql procedure successfully executed'.
    Also, then how i can call this get_hr_list procedure from .net? im using c# and i want to get the result of hr_emp to c#. how i can call the same from c#? any help please

  • Error while executing a procedure in Package

    ORA-04068: existing state of packages has been discarded
    ORA-04061: existing state of package "PLLODS.LK" has been invalidated
    ORA-04065: not executed, altered or dropped package "PLLODS.LK"
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 1Why did this error arise when I changed a package and recompiled?

    This errors occurs when a package was executed in session A, compiled in session B, and then executed again in session A. The package executed in session A is in Oracle buffer, but its definition was changed in session B (which session A is unaware of). Now session A uses the old definition of the package but Oracle checks what is in buffer to the new definition and finds a difference. Therefore, it generates an error:
    ORA-04068: existing state of packages has been discarded
    and other related errors.
    Just execute the procedure (in the package) again and you should not see the error again.
    Make sure the stae of the package is valid, that is, when it was recompiled, the package compiled successfully.
    Shakti
    http://www.impact-sol.com
    Developers of Guggi Oracle - Tool for Developers and DBAs

  • Getting error while executing a procedure and assign the output in BPEL

    Hi
    I am getting the Following error while deploying BPEL in 10.1.3.1. I have invoked Database Adapter and called a procedure and that procedure returns a output. I have assigned that output to a variable.
    empty variable/expression result.
    xpath variable/expression expression "/ns2:OutputParameters/ns2:GREETING" is empty at line 98, when attempting reading/copying it.
    Please make sure the variable/expression result "/ns2:OutputParameters/ns2:GREETING" is not empty.
    Please reply me with Solutions

    Hi,
    Are you getting this error while deploying or testing ?
    Normally this will happen due to namespace mismatch issue. But if you have auto-created the variables then JDev will take care of it so it should not be a problem
    Also, please check if this also happens if the code is deployed to 10.1.3.3 ?
    Regards,
    ketan

  • Errors while executing a procedure

    Im trying to execute following procedure which in turn has two more procedures in it.These two internal procedures calls a java stored procedure.When im trying to execute im getting errors
    Errors
    PLS-00222: no function with name 'SFDC_LOGIN' exists in this
    scope
    PL/SQL: Item ignored
    PLS-00999: implementation restriction (may be temporary) Java
    methods not permitted here
    Procedure
    CREATE OR REPLACE PROCEDURE account_cur is
    procedure new_account(accnumber varchar2,name varchar2,creditstatus varchar2) as language java NAME 'CreateAccount.createAccount(java.lang.String,java.lang.String,java.lang.String) return int';
    procedure sfdc_login as language java NAME 'CreateAccount.login()';
    CURSOR c1 IS
    SELECT name,accnumber,creditstatus FROM account where flag=0
    FOR UPDATE OF flag NOWAIT;
    result number;
    BEGIN
    if(sfdc_login) then
    FOR i IN c1
    fetch c1 into v_name,v_number,v_status
    LOOP
    result:=new_account(i.v_name,i.v_number,i.v_status);
    IF result=1
    THEN
    UPDATE account
    SET flag=1
    WHERE CURRENT OF c1;
    ELSE
    RAISE_APPLICATION_ERROR
    (-20222, ‘ACCOUNT CREATION FAILED ');
    END IF;
    END LOOP;
    ELSE
    RAISE_APPLICATION_ERROR
    (-20221, ‘LOGIN FAILED');
    END IF;
    END account;
    Can any one please suggest me how to resolve this issue.
    thanks in advance

    Well I suspect (although I have not tried) that Oracle is objecting to you declaring Java methods as local procedures within a procedure.
    Generally advice would be that you should use packages rather than standalone stored procedures - in which case you could move the java methods to be separate procedures within the same package.

  • Error while executing a procedure in pl/sql

    Hi,
    iam execvuting a procedure in pl/sql and i get the following error,
    proc Running: Wed Sep 7 06:13:20 IST 2005
    Table truncated.
    BEGIN <procedure_name> ; END;
    ERROR at line 1:
    ORA-01555: snapshot too old: rollback segment number 75 with name "RBS74" too
    small
    ORA-06512: at "<procedure_name>", line 104
    ORA-06512: at line 1
    could anyone explain what has gone wrong in this case???

    According to the documentation:
    ORA-01555: snapshot too old: rollback segment number string with name "string" too small
    Cause: Rollback records needed by a reader for consistent read are overwritten by other writers.
    Action: If in Automatic Undo Management mode, increase the setting of UNDO_RETENTION. Otherwise, use larger rollback segments.
    Error: ORA-01555: snapshot too old (rollback segment too small)
    Cause: This error can be caused by one of the problems, as described below.
    Action: The options to resolve this Oracle error are:
    This error can be the result of there being insufficient rollback segments.
    A query may not be able to create the snapshot because the rollback data is not available. This can happen when there are many transactions that are modifying data, and performing commits and rollbacks. Rollback data is overwritten when the rollback segments are too small for the size and number of changes that are being performed.
    To correct this problem, make more larger rollback segments available. Your rollback data for completed transactions will be kept longer.
    This error can be the result of programs not closing cursors after repeated FETCH and UPDATE statements.
    To correct this problem, make sure that you are closing cursors when you no longer require them.
    This error can occur if a FETCH is executed after a COMMIT is issued.
    The number of rollback records created since the last CLOSE of your cursor will fill the rollback segments and you will begin overwriting earlier records.

  • End Of communication Error while executing java procedure (Urgent)

    Hi All,
    I am using oracle 10g on linux server. Client machine is on xp. I hava a java procedure which executes the sqlldr on server. Earlier it was working fine, but after reinstalling the oracle 10g on server. It started giving "end of Communication channel error". I am not aware that what paramete has to set. Can some body put light on this error.
    Bye
    Sachin

    This is the most frequently asked question from Oracle developers.. Never mind putting some light on this error, I want to put it alight! ;-)
    First thing. It is not The Error. It is a sympton of an error.
    This message does not come from the database. It comes from the client OCI (of JDBC) drivers - which suddenly discovered that the Oracle connection (usually a TCP socket connection) has been torn down at the server side. It attempts to write to that socket, only to find that the other party has hung up.
    Why has the other party hung up? That party is either a Dedicated Server Process or a Dispatcher Process. If a dedicated server dies (crashes), it will take its socket handles with it to The Great Recycle Bin In The Sky. If you was serviced by a shared server and it died, the Dispatcher (who handles the TCP comms for it), will automatically close that shared server's connection.
    Usually when a process dies on the Oracle server, it leaves behind an error in the alert log, and trace files. That is where you will find the inklings of what The Error was that caused your client to get the EOF on comms channel message.

  • Error while executing DB procedure proxy

    I am getting error 'Database error text: Insufficient privilege: Not Authorized ' when I call a database procedure proxy in a abap report program.
    Can any one help?
    CALL DATABASE PROCEDURE zdpp_oia_topandflop
    EXPORTING iv_number = lv_number
    IMPORTING et_top = lt_top
    et_flop = lt_flop
    I also tried calling a  HANA procedure in an ABAP report program  which works fine .
    Thanks in advance !,
    Sharada

    Hi. Sharada GSharada G
    I had been got in same problem.
    Finally, I solved the issue.
    Just follow below steps.
    1. Log on your HANA System with HANA Studio (SYSYTEM Account)
    2. Add "GET_OBJECT_VERSION" Object Privileges to SAP<SID> Account with only "execute" option.
    3. then Everything will be done.
    I hope you save a couple of day to settle down this problem.....

  • Error While Executing Stored Procedure - SAP BPC 5.0

    Hi all
    I have defined stored procedure 'EP2' in the account transformation rules and which runs fine with all the entities.
    But when I filter particular entity which give no data extrace to the selections made instead of giving the comment:
    0 rows created and update it gives the error below.
    Kindly Help me out if any one has the idea of running stored procedure
    Executing SPRUNCALCACCOUNT "[[FINANCE]],[[ACTUAL]],[[LC]],[[SPSCOPE_367693]],[[SPLOG_887033]],[[EP2]]"
    SPRunCalcAccount Version 2.06
    -ERR- CALC-070 No DATA Extract From FACT Table
    Time to run stored procedure:2.8 sec.
    Edited by: Harish Bysani Kodanda on Mar 14, 2008 8:46 AM
    Edited by: Harish Bysani Kodanda on Mar 14, 2008 8:47 AM
    Edited by: Harish Bysani Kodanda on Mar 14, 2008 8:48 AM

    Yes, the business rules stored procedures surface an error if there is an empty data set to operate on.

Maybe you are looking for

  • When I try to sincronisy my iphone 3g S the computer doesnt recognize it

    and the screem of the cell is frozed in a pic of the itunes anad the cable of the cell

  • Using 'SYSDATE' function in ACCESS 2000?

    'SYSDATE' function is not working in ACCESS 2000 , is there any other alternative function available in access. I use a select statement using SYSDATE, but it did not work.

  • Oracle Sys table index rebuild

    hi, expert I am new to this expert Forums Blow Table Index are rebuild,This table are relation with sys user or not? after rebuild index, getting error in alert log file ORA-00600: internal error code, arguments: [psdnop-1], [1410], [], [], [], [], [

  • Problem in Resource moving Oracle Fail safe

    Hi , I have Os clustering Oracle Fail Safe configured here(10g enterprise Edition) While Performin test ... cluster resources are not moving to another server due to which oracle database are not getting start on another cluster node ... Plz help mee

  • Eprint Enteprise Setup

    Hello! We are currently doing a POC with Eprint Enterprise 2.1 for our business.  We are using this to control printing to iOS devices (iPads, iPhones). I have installed Eprint Enterprise 64 bit 2.1 version on a Windows Server 2008 R2 installation. A