Ora:getElement erroring out at runtime

I use this function to process set of detail records one by one. I used the function as follows:
<copy>
<from expression="ora:getElement('var61104DC','/ns5:PIXBridge/PIX',bpws:getVariableData('varI'))"/>
<to variable="varDC" query="/ns5:PIXBridge/PIX"/>
</copy>
where var61104DC and varDC are variable of type Element. When we use element type variable we don't have the 'part' parameter to pass to the function.
When we use the same function for message type variable we are not getting any errors.
Can anyone had this kind of problem? Please let me know the work around for this issue. I am getting the following error:
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: XPath expression failed to execute.
Error while processing xpath expression, the expression is "ora:getElement('var61104DC','/ns5:PIXBridge/PIX',bpws:getVariableData('varI'))", the reason is FOTY0001: type error.
Please verify the xpath query.
Thanks.

Hi, we are noticing the same behaviour. did you find a solution?
Richard

Similar Messages

Runtime constant (Filename) errors out in BPM

Hi,
I have a BPMCollectTime scenario to collect the Source files. The filename (Message Mapping/Transformation) from the files is captured in TRANSFORM STEP(before sending them out from BPM). The file is sent to SEND step one at a time.
Question : Filename of the source file is captured through user defined function.
Following is the code.
================
String v_result_time; //test Variable
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
if (key == null) { v_result_time= "Create Key Failed";}
else
{v_result_time= "Create Key worked";
String valueOld = conf.get(key);
v_result_time = valueOld;
return v_result_time;
The Mapping gives a runtime error in the BPM. This is a sporadic error.
I have selected the Adapter specific attribute(File name).
The BPM errors out sometimes? I am not sure if I am missing any setting. If I delete the work item and run the same scenario it works.
Question 1 : What is the cause of the above error?
Question 2 : Does BPM support Adapter specific attribute such as filename?
Kindly Advice.
Thanks,
Gowri

Hi Everyone,
Thanks for all the help.
DTN will not change the response filename to source filename. This option cannot be used. The correlation id is defined as response file name. Response filename is fixed for invoice file.
Here is the example.
For invoice file name HDTN20070430163110.TXT, response file received is nav1_2b5.rsp file. For HDTN20070430163314.TXT , response file is nav1_2b5.rsp
So my correlation id is dummy fixed value. I have known the fact that it is not possible to use context object filename.
Bhavesh - I have defined transform step for accessing filename using dynamic configuration. Following is the code used in mapping.
================
String v_result_time; //test Variable
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
if (key == null) { v_result_time= "Create Key Failed";}
else
{v_result_time= "Create Key worked";
String valueOld = conf.get(key);
v_result_time = valueOld;
return v_result_time;
====================================
BPM errors out sometime with following error
Component mapping has returned error.
com/sap/xi/tf/_MM_DTNData_2_DTNFilename_java.lang.NullpointerException.
Error: Exception CX_MERGE_SPLIT occurred (program: CL_MERGE_SPLIT_SERVICE========CP, include: CL_
If I delete this workitem and repeat the same scenario, it works. I have still not understood, why the scenario works sometime.
Kindly Advice.
Thanks,
Gowri

Custom Interface Program Errors out with ORA-01722: invalid number in R12

Hi,
We were upgrading to R12 in which our custom interface load program errors out with "ORA-01722: invalid number". Please find structure of control file as below :
LOAD DATA
APPEND
INTO TABLE RRAT_RCAP_GIO_MAN_ADJ_STG
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED by '"'
TRAILING NULLCOLS
PERIOD_NAME CHAR "ltrim(rtrim(:PERIOD_NAME))"
,SOURCE_TYPE CHAR "ltrim(rtrim(:SOURCE_TYPE))"
,ADJ_ACCOUNT CHAR "ltrim(rtrim(:ADJ_ACCOUNT))"
,USD_NET INTEGER EXTERNAL
,ERROR_CODE CONSTANT 'LOADED DATA'
,PROCESS_FLAG CONSTANT 1
,CREATED_BY "fnd_global.user_id"
,CREATION_DATE sysdate
,LAST_UPDATED_BY "fnd_global.user_id"
,LAST_UPDATE_DATE sysdate
,LAST_UPDATE_LOGIN "fnd_global.login_id"
,REQUEST_ID "fnd_global.conc_request_id"
=====================================Log file ================
Record 1: Rejected - Error on table "XXATORCL"."XXAT_VCAP_GIO_MAN_ADJ_STG", column USD_NET.
ORA-01722: invalid number
===================sample file ==========================
JUL-11,Manual,8213-880011-00000000-259390-1Z-0000-0000,1001
JUL-11,Manual,8213-880011-00000000-253701-1Z-0000-0000,73
==========================================
I had tried with last successfully uploaded file as well which is also now not uploading.
Please help me in this issue.
Thanks,
Piyush

i am using R12 now. Please avoide INTEGER EXTERNAL part from the control file. please refer below :
LOAD DATA
APPEND
INTO TABLE RRAT_RCAP_GIO_MAN_ADJ_STG
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED by '"'
TRAILING NULLCOLS
PERIOD_NAME CHAR "ltrim(rtrim(:PERIOD_NAME))"
,SOURCE_TYPE CHAR "ltrim(rtrim(:SOURCE_TYPE))"
,ADJ_ACCOUNT CHAR "ltrim(rtrim(:ADJ_ACCOUNT))"
,USD_NET
,ERROR_CODE CONSTANT 'LOADED DATA'
,PROCESS_FLAG CONSTANT 1
,CREATED_BY "fnd_global.user_id"
,CREATION_DATE sysdate
,LAST_UPDATED_BY "fnd_global.user_id"
,LAST_UPDATE_DATE sysdate
,LAST_UPDATE_LOGIN "fnd_global.login_id"
,REQUEST_ID "fnd_global.conc_request_id"
====================
Srini,
Just one thing i want to explain you that previously it was working fine but suddenly (might after upgrading in R12) started giving error. I had tested with old data files also which were loaded successfully in the system. but now it is giving error. Please help me in this issue.
Regards,

RACUST errors out - racina: ORA-01422: exact fetch returns more than reques

Hi,
We are using standard RACUST interface( r12, 12.0.0). All the records are successsfully validated however, the standard program errors out at run time with the following error
racina: ORA-01422: exact fetch returns more than requested number of rows

Pl see if MOS Doc 802175.1 (Customer Interface Creates Duplicate Party Sites Used in Multi-Org (MOAC)) can help
HTH
Srini

While using the Old syntax of outer join i encountered Ora-01719 error .

This is quite strange when i used the Old way of using Outer Joins(+), i encountered the Ora-01719 error saying Outer Joins not allowed in Or and IN operator.Whereas when i use the ANSI sql i query gets executed without any error.Any idea what might be the reason..is it that i myself is making mistake.
Please find the select statement below..
SELECT d4.c2, d4.c8, vw_rpt_prod_ln_grp.prod_grp_desc, d4.c10, d4.c5, d4.c3,
CASE
WHEN d4.c6 = 'Closed'
THEN d4.c6
WHEN d4.c6 = 'Closed (w/o Action)'
THEN d4.c6
WHEN d4.c6 =
'Closed, Supporting Process(es) Active'
THEN d4.c6
WHEN d4.c6 = 'Cancelled'
THEN d4.c6
WHEN t3.workflow_compnt_id = 1
THEN 'Definition'
WHEN t3.workflow_compnt_id = 2
THEN 'Root Cause'
WHEN t3.workflow_compnt_id = 3
THEN 'Solution'
WHEN t3.workflow_compnt_id = 4
THEN 'Implementation'
WHEN t3.workflow_compnt_id = 5
THEN 'Feedback'
WHEN t3.workflow_compnt_id = 9
THEN 'Preliminary Root Cause'
WHEN t3.workflow_compnt_id = 2001
THEN 'Report'
WHEN t3.workflow_compnt_id = 2002
THEN 'Sent'
WHEN t3.workflow_compnt_id = 2003
THEN 'Add. Info Needed'
WHEN t3.workflow_compnt_id = 2004
THEN 'Open'
WHEN t3.workflow_compnt_id = 2007
THEN 'Solution Feedback'
END issue_workflow_status,
CASE
WHEN d4.c6 = 'Closed'
THEN 0
WHEN d4.c6 = 'Closed (w/o Action)'
THEN 0
WHEN d4.c6 =
'Closed, Supporting Process(es) Active'
THEN 0
WHEN d4.c6 = 'Cancelled'
THEN 0
ELSE t3.workflow_compnt_id
END issue_workflow_status_code,
d4.c6, d4.c9,
CASE t3.issue_step_status_cd
WHEN 'In Progress'
THEN t3.step_target_submit_dt
WHEN 'Needs Additional Information'
THEN t3.step_target_submit_dt
WHEN 'Awaiting Approval'
THEN t3.step_target_closed_dt
ELSE NULL
END target_date,
CASE
WHEN CASE t3.issue_step_status_cd
WHEN 'In Progress'
THEN t3.step_target_submit_dt
WHEN 'Needs Additional Information'
THEN t3.step_target_submit_dt
WHEN 'Awaiting Approval'
THEN t3.step_target_closed_dt
ELSE NULL
END IS NULL
THEN 'N'
WHEN CASE t3.issue_step_status_cd
WHEN 'In Progress'
THEN t3.step_target_submit_dt
WHEN 'Needs Additional Information'
THEN t3.step_target_submit_dt
WHEN 'Awaiting Approval'
THEN t3.step_target_closed_dt
ELSE NULL
END < TRUNC (CURRENT_DATE)
THEN 'Y'
ELSE 'N'
END step_is_late,
t3.orig_user_full_nm, t3.champ_user_full_nm, t3.champ_org_nm,
vw_rpt_defntn.modl_yr_nbr, vw_rpt_vpps_lvl.level1_vpps_desc,
vw_rpt_vpps_lvl.level2_vpps_desc, vw_rpt_vpps_lvl.level3_vpps_desc,
vw_rpt_vpps_lvl.level4_vpps_desc,
Mv_RPT_CONCAT_ENGN_OPTN_ALL.concat_engn_optn,
vw_rpt_incdnt_src_three_level.level1_incdnt_src_desc,
vw_rpt_incdnt_src_three_level.level2_incdnt_src_desc,
vw_rpt_incdnt_src_three_level.level3_incdnt_src_desc,
vw_rpt_warranty_labr_code.concat_warranty_labr_code_desc, d4.c4, d4.c7,
vw_cust_survey_type.cust_survey_type_desc,
vw_complaint_ctg.complaint_ctg_cd,
vw_prob_main_cause.prob_main_cause_desc, soltn_step.confidence_lvl_id,
d4.c12, d4.c13
FROM (SELECT DISTINCT vw_rpt_issue.project_id c0,
vw_rpt_issue.prts_prod_ln_id c1,
vw_rpt_issue.issue_id c2,
vw_rpt_issue.disply_issue_nbr c3,
vw_rpt_issue.issue_sevrty_cd c4,
vw_rpt_issue.proj_nbr c5,
vw_rpt_issue.issue_status_cd c6,
vw_rpt_issue.primry_metric_score_nbr c7,
vw_rpt_issue.issue_type_cd c8, vw_rpt_issue.title c9,
vw_rpt_issue.prts_prod_ln_desc c10,
vw_rpt_leadtime.issue_id c11,
vw_rpt_leadtime.definition_start_dt c12,
vw_rpt_leadtime.definition_close_dt c13,
vw_rpt_leadtime.root_cause_start_dt c14,
vw_rpt_leadtime.root_cause_close_dt c15,
vw_rpt_leadtime.solution_start_dt c16,
vw_rpt_leadtime.solution_end_dt c17,
vw_rpt_leadtime.implementation_start_dt c18,
vw_rpt_leadtime.implementation_close_dt c19,
vw_rpt_leadtime.feedback_start_dt c20,
vw_rpt_leadtime.feedback_end_dt c21,
vw_rpt_leadtime.prc_start_dt c22,
vw_rpt_leadtime.prc_end_dt c23,
defntn_step.issue_id c24,
defntn_step.workflow_compnt_id c25,
defntn_step.complaint_ctg_id c26,
defntn_step.contnmt_actn_plan_id c27,
defntn_step.direct_run_imprvm_pct c28,
defntn_step.direct_run_loss_pct c29,
defntn_step.drive_type_id c30,
defntn_step.driving_cond_id c31,
defntn_step.eng_pgm_nbr c32,
defntn_step.engn_serial_nbr c33,
defntn_step.envrnmtl_cond_id c34,
defntn_step.ergo_rating_id c35,
defntn_step.evaltn_complt_pct c36,
defntn_step.evaltn_procdr_id c37,
defntn_step.gca_50_or_safety_issue_flag c38,
defntn_step.gca_value_amt c39,
defntn_step.gm_rating_id c40,
defntn_step.hardware_stage_id c41,
defntn_step.incdnt_discvrd_by_nm c42,
defntn_step.incdnt_discvr_dept_nm c43,
defntn_step.incdnt_discvr_ph_nbr c44,
defntn_step.incdnt_first_rptd_dt c45,
defntn_step.incdnt_src_id c46,
defntn_step.intrnl_measmt_info_owner_nm c47,
defntn_step.intrnl_measmt_plt_faclty_id c48,
defntn_step.intrnl_measmt_rpt_dt c49,
defntn_step.issue_clasfn_id c50,
defntn_step.issue_ctg_id c51,
defntn_step.issue_intgrtn_id c52,
defntn_step.modl_yr_id c53,
defntn_step.modl_yr_qtr_id c54,
defntn_step.odmtr_msmt_unit_id c55,
defntn_step.odmtr_rdng_msmt_unit_id c56,
defntn_step.odmtr_rdng_nbr c57,
defntn_step.odmtr_rdng_beginning_nbr c58,
defntn_step.odmtr_rdng_ending_nbr c59,
defntn_step.part_drblty_msmt_unit_id c60,
defntn_step.part_drblty_nbr c61,
defntn_step.part_test_msmt_unit_id c62,
defntn_step.part_test_nbr c63,
defntn_step.pe_me_trial_issue_flag c64,
defntn_step.pim_nbr c65,
defntn_step.plt_asmbly_doc_nbr c66,
defntn_step.productivity_nbr c67,
defntn_step.suspect_parts_avbl_flag c68,
defntn_step.suspect_parts_loc_txt c69,
defntn_step.trnsmn_serial_nbr c70,
defntn_step.veh_ident_nbr c71,
defntn_step.veh_proprt_nbr c72,
defntn_step.veh_test_msmt_unit_id c73,
defntn_step.veh_test_nbr c74,
defntn_step.vpps_id_nbr c75,
defntn_step.wrkstn_id c76,
defntn_step.road_surface_id c77,
defntn_step.cost_redctn_rpt_dt c78,
defntn_step.cost_redctn_trackg_nbr c79,
defntn_step.cost_redctn_type_id c80,
defntn_step.cust_survey_dt c81,
defntn_step.warnty_impct_rpt_dt c82,
defntn_step.field_prod_rpt_nbr c83
FROM (SELECT DISTINCT mv_rpt_issue_all.project_id
project_id,
mv_rpt_issue_all.prts_prod_ln_id
prts_prod_ln_id,
mv_rpt_issue_all.issue_id issue_id,
mv_rpt_issue_all.disply_issue_nbr
disply_issue_nbr,
mv_rpt_issue_all.issue_sevrty_cd
issue_sevrty_cd,
mv_rpt_issue_all.proj_nbr proj_nbr,
mv_rpt_issue_all.issue_status_cd
issue_status_cd,
mv_rpt_issue_all.primry_metric_score_nbr
primry_metric_score_nbr,
mv_rpt_issue_all.issue_type_cd
issue_type_cd,
mv_rpt_issue_all.title title,
mv_rpt_issue_all.prts_prod_ln_desc
prts_prod_ln_desc
FROM mv_rpt_issue_all,
vw_sec_acs_grp_proj acs_grp_proj
WHERE acs_grp_proj.acs_grp_id IN
(1,
4,
42,
43,
44,
51,
52,
53,
54,
266,
366,
386,
526,
546,
547,
548,
566,
846,
946,
966,
1006,
1066,
1087
AND mv_rpt_issue_all.prts_prod_ln_id =
acs_grp_proj.prts_prod_ln_id
AND mv_rpt_issue_all.project_id =
acs_grp_proj.project_id
AND mv_rpt_issue_all.issue_type_cd =
'Current Production') vw_rpt_issue,
vw_rpt_leadtime,
vw_defntn_step defntn_step
WHERE vw_rpt_issue.issue_id = vw_rpt_leadtime.issue_id
AND vw_rpt_issue.issue_id = defntn_step.issue_id) d4,
vw_rpt_incdnt_src_three_level,
vw_rpt_warranty_labr_code,
vw_rpt_prod_ln_grp,
(SELECT t1.issue_id issue_id, t1.workflow_compnt_id workflow_compnt_id,
t1.issue_step_status_cd issue_step_status_cd,
t1.step_target_closed_dt step_target_closed_dt,
t1.step_target_submit_dt step_target_submit_dt,
t1.orig_user_full_nm orig_user_full_nm,
t1.champ_user_full_nm champ_user_full_nm,
t1.champ_org_nm champ_org_nm
FROM prts_syst.vw_rpt_issue_step_dtl_all t1
WHERE t1.current_step_flag = 'Y') t3,
vw_complaint_ctg,
root_cause_step,
vw_prob_main_cause,
Mv_RPT_CONCAT_ENGN_OPTN_ALL,
vw_rpt_vpps_lvl,
soltn_step,
vw_rpt_defntn_all vw_rpt_defntn,
vw_cust_survey_impct_dtl cust_survey_impct_dtl,
vw_cust_survey_type
WHERE d4.c46 = vw_rpt_incdnt_src_three_level.level3_incdnt_src_id(+)
Or d4.c46=vw_rpt_incdnt_src_three_level.level2_incdnt_src_id(+))
And vw_rpt_incdnt_src_three_level.level3_incdnt_src_id IS NULL
AND d4.c2 = vw_rpt_warranty_labr_code.issue_id(+)
AND d4.c1 = vw_rpt_prod_ln_grp.prts_prod_ln_id(+)
AND d4.c2 = t3.issue_id(+)
AND d4.c26 = vw_complaint_ctg.complaint_ctg_id(+)
AND d4.c2 = root_cause_step.issue_id(+)
AND root_cause_step.prob_main_cause_id = vw_prob_main_cause.prob_main_cause_id(+)
AND d4.c2 = Mv_RPT_CONCAT_ENGN_OPTN_ALL.issue_id(+)
AND d4.c75 = vw_rpt_vpps_lvl.vpps_id_nbr(+)
AND d4.c2 = soltn_step.issue_id(+)
AND d4.c2 = vw_rpt_defntn.issue_id(+)
AND d4.c2 = cust_survey_impct_dtl.issue_id(+)
AND cust_survey_impct_dtl.cust_survey_type_id = vw_cust_survey_type.cust_survey_type_id(+)
AND vw_rpt_prod_ln_grp.prod_grp_desc IN
('DB Admin', 'GM - All Vehicles', 'GMAP - DAT', 'GMAP - Holden')
AND d4.c6 IN
('Cancelled',
'Closed',
'Closed (w/o Action)',
'Closed, Supporting Process(es) Active',
'Draft',
'Open'
);

Hi,
Maestro_Vineet wrote:
This is quite strange when i used the Old way of using Outer Joins(+), i encountered the Ora-01719 error saying Outer Joins not allowed in Or and IN operator.Whereas when i use the ANSI sql i query gets executed without any error.Any idea what might be the reason..is it that i myself is making mistake.No, I don't think you're making any mistake. Some things are simply not allowed with the "+" outer-join syntax.
There are work-arounds, but they are harder to code and slower to run than simply using ANSI syntax.
I recommend always using ANSI syntax, especially for outer joins.

Error ORA-01002: fetch out of sequence

Hi all,
I created 3 cursors. The scenario is like following :
Begin Cur A
Begin FOR xx IN Cur B LOOP
Begin FOR xx IN Cur C LOOP
End LOOP Cur C;
commit;
End LOOP Cur B;
End Cur A;
When i run the program its display error ORA-01002: fetch out of sequence.
The objective of my program is to insert into table and commit every transaction.
Kindly share info with me why this error happened.
TQ.
tim

Tim,
Refer to the following:
ORA-01002: fetch out of sequence
Cause: This error means that a fetch has been attempted from a cursor which is no longer valid.
Note that a PL/SQL cursor loop implicitly does fetches, and thus may also cause this error. There are a number of possible causes for this error, including:
1) Fetching from a cursor after the last row has been retrieved and the ORA-1403 error returned.
2) If the cursor has been opened with the FOR UPDATE clause, fetching after a COMMIT has been issued will return the error.
3) Rebinding any placeholders in the SQL statement, then issuing a fetch before reexecuting the statement.
Action:
1) Do not issue a fetch statement after the last row has been retrieved - there are no more rows to fetch.
2) Do not issue a COMMIT inside a fetch loop for a cursor that has been opened FOR UPDATE.
3) Reexecute the statement after rebinding, then attempt to fetch again.
HTH,
Thierry
Edited by: Thierry H. on May 4, 2011 12:30 PM Reformatting

ProC code- error ORA-1002 fetch out of sequence

Hi,
we have an application currntly running on an HP UX system that uses Oracle 9i database.
the pro*C codes work fine with Oracle 9i, on the older system. however now we are migrating it to LINUX system (ORACLE 10g). in the new system we are facing issues with fetch statement
here is how we have the code:
the cursor statement:
EXEC SQL DECLARE diff_cns_list CURSOR FOR
select PREV.CNS_CODE,
PREV.CNS_DESCRIPTION,
PREV.CGP_CODE,
CURR.CNS_DESCRIPTION,
CURR.CGP_CODE
from NCIP_CNS_LIST PREV, NCIP_CNS_LIST CURR
where CURR.SAMPLE_DATE =
to_date('01' || :currdate || ' 00:00','ddyymm hh24:mi')
and PREV.SAMPLE_DATE =
to_date('01' || :prevdate || ' 00:00','ddyymm hh24:mi')
and PREV.CNS_CODE = CURR.CNS_CODE
and (PREV.CGP_CODE != CURR.CGP_CODE or
PREV.CNS_DESCRIPTION != CURR.CNS_DESCRIPTION);
======================
currdate=1106 (i.e. june 2011)
prevdate=1105 (i.e. may 2011)
======================
cursor is opened and then following fetch statement is run:
while( 1 )
exec sql FETCH diff_cns_list INTO :prev_vcns,
:prev_vdesc,
:prev_vcgp,
:curr_vdesc,
:curr_vcgp;
/* If no data found then exit from loop */
if( sqlca.sqlcode == 1403 )
break;
else if( sqlca.sqlcode != 0 )
vLOG_Msg(LOG_MSG_ERROR,"fniCmpNcipCnsList",
"ORACLE error on fetching diff_cns_list %s", sqlca.sqlerrm.sqlerrmc);
return( ERROR );
oravarterm( prev_vcns );
oravarterm( prev_vdesc );
oravarterm( prev_vcgp );
oravarterm( curr_vdesc );
oravarterm( curr_vcgp );
fprintf( output_fp,"'%s','%s','%s','%s','%s'\r\n",prev_vcns.arr,
prev_vdesc.arr,
prev_vcgp.arr,
curr_vdesc.arr,
curr_vcgp.arr);
the code runs fine in the old operating system (HP UX) where oracle 9i was used.
but fails in Oracle 10g(OS-LINUX).
the probable reason that we found out is that:
the fetch statement returns zero rows, that is the reason why this error is being displayed.
but Oracle 9i seemed to work out well with this.
we tried reducing the cursor conditions, where it fetches 3 rows. this is when is the fetch statement works fine.
the functionality of the code is that it should work fine even with no rows selected. Is there a way we can modfy the code to work with zero rows as well.
the error we are getting is : ORA-01002: fetch out of sequence
==========================
as per what is given in Oracle sites:
1) Fetching from a cursor after the last row has been retrieved and the ORA-1403 error returned. 2) If the cursor has been opened with the FOR UPDATE clause, fetching after a COMMIT has been issued will return the error. 3) Rebinding any placeholders in the SQL statement, then issuing a fetch before reexecuting the statement.
========================
we have checked:
1>this is not the case and ORA-1403 not returned
2>No update statements involved , there is a insert statement which inserts data in this table
3>i am not clear with this one.
Could anyone please guide us through this, please?

Note the name of this forum is SQL Developer (Not for general SQL/PLSQL questions) - so for issues with the SQL Developer tool. Please post these questions under the dedicated OCCI forum (you've posted there before).
Regards,
K.

Data Load is erroring out with ORA-12801 ORA-01031

Hello,
I am having Oracle 11.1.0.7 on AIX and we are loading data through Informatica.
There are 7 tables in the database that are big and we enabled parallelism with the degree of 2.
When we run the informatica session for loading data the session is failing with the error -
Severity     Timestamp     Node     Thread     Message Code     Message
ERROR     5/10/2011 4:33:09 PM     node01_wpg1pedw001     POST-SESS     TM_6159     An error occurred executing the stored procedure.
TM_6159 [4294965496] [
ORA-12801: error signaled in parallel query server P000
ORA-01031: insufficient privileges
ORA-06512: at "POL_ODS.DELETE_LATEST_POLICY_1", line 4
ORA-06512: at line 2
Database driver error...
Function Name : ExecuteSP
Oracle Fatal Error
Database driver error...
Function Name : ExecuteSP
Oracle Fatal Error]Trace file is giving me this output -
=====================
PARSING IN CURSOR #3 len=152 dep=1 uid=73 oct=7 lid=73 tim=2806650507771 hv=2692072913 ad='700000b32b206c0' sqlid='835qyt2h7bjfj'
DELETE FROM LIENHOLDER WHERE LIEN_POLICY_12_SEGMENT_ID IN (SELECT POL_SEG_12_ID FROM POLICY12SEGMENT WHERE POLICY_ID IN (SELECT POLICY_ID FROM DEL_POL))
END OF STMT
PARSE #3:c=20000,e=31779,p=0,cr=181,cu=3,mis=1,r=0,dep=1,og=1,plh=449661848,tim=2806650507771
kxfpgsg
        Error 12801 encountered
EXEC #3:c=10000,e=111135,p=0,cr=28,cu=0,mis=0,r=0,dep=1,og=1,plh=449661848,tim=2806650618906
ERROR #3:err=12801 tim=2806650618906
STAT #3 id=1 cnt=0 pid=0 pos=1 obj=0 op='DELETE LIENHOLDER (cr=0 pr=0 pw=0 time=0 us)'
STAT #3 id=2 cnt=0 pid=1 pos=1 obj=0 op='PX COORDINATOR (cr=0 pr=0 pw=0 time=0 us)'
STAT #3 id=3 cnt=0 pid=2 pos=1 obj=0 op='PX SEND QC (RANDOM) :TQ10002 (cr=0 pr=0 pw=0 time=0 us cost=95123 size=6011574 card=117874)'
STAT #3 id=4 cnt=0 pid=3 pos=1 obj=0 op='HASH JOIN RIGHT SEMI (cr=0 pr=0 pw=0 time=0 us cost=95123 size=6011574 card=117874)'
STAT #3 id=5 cnt=0 pid=4 pos=1 obj=0 op='PX RECEIVE (cr=0 pr=0 pw=0 time=0 us cost=88665 size=1472328 card=113256)'
STAT #3 id=6 cnt=0 pid=5 pos=1 obj=0 op='PX SEND BROADCAST :TQ10001 (cr=0 pr=0 pw=0 time=0 us cost=88665 size=1472328 card=113256)'
STAT #3 id=7 cnt=0 pid=6 pos=1 obj=0 op='VIEW VW_NSO_1 (cr=0 pr=0 pw=0 time=0 us cost=88665 size=1472328 card=113256)'
STAT #3 id=8 cnt=0 pid=7 pos=1 obj=0 op='HASH JOIN (cr=0 pr=0 pw=0 time=0 us cost=88665 size=1925352 card=113256)'
STAT #3 id=9 cnt=0 pid=8 pos=1 obj=0 op='BUFFER SORT (cr=0 pr=0 pw=0 time=0 us)'
STAT #3 id=10 cnt=0 pid=9 pos=1 obj=0 op='PX RECEIVE (cr=0 pr=0 pw=0 time=0 us cost=27 size=314700 card=62940)'
STAT #3 id=11 cnt=0 pid=10 pos=1 obj=0 op='PX SEND BROADCAST :TQ10000 (cr=0 pr=0 pw=0 time=0 us cost=27 size=314700 card=62940)'
STAT #3 id=12 cnt=0 pid=11 pos=1 obj=55756 op='TABLE ACCESS FULL DEL_POL (cr=0 pr=0 pw=0 time=0 us cost=27 size=314700 card=62940)'
STAT #3 id=13 cnt=0 pid=8 pos=2 obj=0 op='PX BLOCK ITERATOR (cr=0 pr=0 pw=0 time=0 us cost=88594 size=160428864 card=13369072)'
STAT #3 id=14 cnt=0 pid=13 pos=1 obj=70801 op='TABLE ACCESS FULL POLICY12SEGMENT (cr=0 pr=0 pw=0 time=0 us cost=88594 size=160428864 card=13369072)'
STAT #3 id=15 cnt=0 pid=4 pos=2 obj=0 op='PX BLOCK ITERATOR (cr=0 pr=0 pw=0 time=0 us cost=6434 size=265286208 card=6981216)'
STAT #3 id=16 cnt=0 pid=15 pos=1 obj=70798 op='TABLE ACCESS FULL LIENHOLDER (cr=0 pr=0 pw=0 time=0 us cost=6434 size=265286208 card=6981216)'
CLOSE #3:c=0,e=0,dep=1,type=0,tim=2806650618906
EXEC #2:c=30000,e=142914,p=0,cr=209,cu=3,mis=0,r=0,dep=0,og=1,plh=0,tim=2806650618906
ERROR #2:err=12801 tim=2806650618906
=====================The Table LIENHOLDER is not set for parallelism and is not amount 7 of those tables. But even when we enabled parallelism with degree of 2 on LIENHOLDER, it is still thowing out this error message.
I have granted DBA role to POL_ODS who owns this procedure POL_ODS.DELETE_LATEST_POLICY_1.
Waiting for your inputs and hope to hear from the Oracle & Informatica experts soon.
Thanks!

Thanks for your reply Karluk & hoek.
Just to let you know, we are encountering this problem when I enable parallelism on the 7 tables.
TABLE_NAME                     DEGREE
POLICY30SEGMENT                         2
POLICY03SEGMENT                         2
POLICY                                  2
POLICY12SEGMENT                         2
POLICY35SEGMENT                         2
POLICY45SEGMENT                         2
VEHICLECOVERAGE                         2Proc DELETE_LATEST_POLICY_1 is owned by POL_ODS and this job is run by POL_ODS itself. This PROC does delete. Yes, LEINHOLDER is owned by POL_ODS only so there is no need to grant DELETE on this table to it's own schema.
As stated in my the trace file, the DELETE statement that it was running was -
DELETE FROM LIENHOLDER WHERE LIEN_POLICY_12_SEGMENT_ID IN (SELECT POL_SEG_12_ID FROM POLICY12SEGMENT WHERE POLICY_ID IN (SELECT POLICY_ID FROM DEL_POL))In this POLICY12SEGMENT is enabled for parallelism but not LIENHOLDER or DEL_POL.
If I don't have parallelism on these 7 tables then the PROC runs fine and it does the delete as expected.
Hope I am clear this time.
Thanks for your time Guys!
Edited by: user608897 on May 10, 2011 6:32 PM

ORA-01002: fetch out of sequence- error when accesing oracle sp from c#

We have a stored procedure when we exceute it from Sql plus tool ot Toad works fine. But when we call it from C# .ne code gives us the following error.
ORA-01002: fetch out of sequence ORA-02063: preceding line from SQA1
Please help.

with out these lines it works
(fae_primary_agent_ind = 'X') or
((fae_primary_agent_ind is null) and (agn_agt_comp_st_cd = ‘65’)
This is the stored proc. It works in oracle. It does not work only when we call it from C#.
CREATE OR REPLACE
PROCEDURE abc (
p_report_date IN VARCHAR2,
p_cur OUT Getadrdata.t_cursor,
p_run_mode OUT NUMBER
AS
v_report_dt DATE;
backed_out NUMBER := 0;
previously_paid NUMBER := 0;
BEGIN
v_report_dt := TO_DATE (p_report_date, 'DDMMYYYY');
SELECT COUNT (*)
INTO backed_out
FROM r2t_adr_payment a, DUAL
WHERE a.fap_acctg_dt = v_report_dt
AND a.fap_status_cd = 'B';
IF backed_out = 0
THEN
SELECT COUNT (*)
INTO previously_paid
FROM r2t_adr_payment a, DUAL
WHERE a.fap_acctg_dt = v_report_dt
AND a.fap_status_cd = 'P';
END IF;
IF backed_out > 0 or previously_paid > 0
THEN
p_run_mode := 2;
OPEN p_cur FOR
SELECT fae_agent_nbr agent_nbr, fae_ssn_last_4digits ssn_nbr,
fae_address_ln1 address_line1, fae_address_ln2 address_line2,
fae_city_nm city, fae_state_cd state, fae_zip_cd zip,
fae_bus_phone business_phone, fae_supv_region_cd region,
fae_territory_cd territory, fae_market_cd market,
-- FAE_AGT_COMP_ST_CD COMP_STAT_CD,
agn_agt_comp_st_cd comp_stat_cd, fae_emplmt_dt emp_date,
fae_agent_type_cd status_cd, fae_first_nm first_name,
fae_last_nm last_name,
rpt_agent_bonus_class_id p_agent_bonus_class_id
FROM r2t_adr_epc_agent_info LEFT OUTER JOIN rgt_points
ON fae_agent_nbr = rpt_agent_nbr
LEFT OUTER JOIN p1t_tot_agent ON fae_agent_nbr =
agn_agent_nbr
INNER JOIN r2t_adr_payment
ON fae_agent_nbr = fap_primary_agent_nbr
WHERE FAE_AGENT_TYPE_CD = '41'
AND rpt_acctg_dt = v_report_dt
AND v_report_dt BETWEEN agn_start_eff_dt AND agn_end_eff_dt
AND fap_acctg_dt = v_report_dt
AND fap_status_cd = 'B'
UNION ALL
SELECT fae_agent_nbr agent_nbr, fae_ssn_last_4digits ssn_nbr,
fae_address_ln1 address_line1, fae_address_ln2 address_line2,
fae_city_nm city, fae_state_cd state, fae_zip_cd zip,
fae_bus_phone business_phone, fae_supv_region_cd region,
fae_territory_cd territory, fae_market_cd market,
-- FAE_AGT_COMP_ST_CD COMP_STAT_CD,
agn_agt_comp_st_cd comp_stat_cd, fae_emplmt_dt emp_date,
fae_agent_type_cd status_cd, fae_first_nm first_name,
fae_last_nm last_name,
0 p_agent_bonus_class_id
FROM r2t_adr_epc_agent_info
LEFT OUTER JOIN p1t_tot_agent ON fae_agent_nbr =
agn_agent_nbr
INNER JOIN r2t_adr_payment
ON fae_agent_nbr = fap_primary_agent_nbr
WHERE fae_agent_type_cd = '13'
AND v_report_dt BETWEEN agn_start_eff_dt AND agn_end_eff_dt
AND fap_acctg_dt = v_report_dt
AND fap_status_cd = 'B';
ELSE
p_run_mode := 1;
OPEN p_cur FOR
SELECT fae_agent_nbr agent_nbr, fae_ssn_last_4digits ssn_nbr,
fae_address_ln1 address_line1, fae_address_ln2 address_line2,
fae_city_nm city, fae_state_cd state, fae_zip_cd zip,
fae_bus_phone business_phone, fae_supv_region_cd region,
fae_territory_cd territory, fae_market_cd market,
-- FAE_AGT_COMP_ST_CD COMP_STAT_CD,
agn_agt_comp_st_cd comp_stat_cd, fae_emplmt_dt emp_date,
fae_agent_type_cd status_cd, fae_first_nm first_name,
fae_last_nm last_name,
rpt_agent_bonus_class_id p_agent_bonus_class_id
FROM r2t_adr_epc_agent_info LEFT OUTER JOIN rgt_points
ON fae_agent_nbr = rpt_agent_nbr
LEFT OUTER JOIN p1t_tot_agent ON fae_agent_nbr =
agn_agent_nbr
WHERE rpt_acctg_dt = v_report_dt
-- Next line for testing of a subset of data - testing purposes only
-- AND FAE_SUPV_REGION_CD ='002'
AND FAE_AGENT_TYPE_CD = '41'
AND (
(RPT_AGENT_BONUS_CLASS_ID = '3' AND SUBSTR(FAE_EMPLMT_DT,1,2) <> '01' AND ADD_MONTHS(FAE_EMPLMT_DT, 7 ) <= v_report_dt) OR
(RPT_AGENT_BONUS_CLASS_ID = '3' AND SUBSTR(FAE_EMPLMT_DT,1,2) = '01' AND ADD_MONTHS(FAE_EMPLMT_DT, 6 ) <= v_report_dt) OR
(RPT_AGENT_BONUS_CLASS_ID = '1')
AND (
(fae_primary_agent_ind = 'X') or
((fae_primary_agent_ind is null) and (agn_agt_comp_st_cd = ‘65’)
AND v_report_dt BETWEEN agn_start_eff_dt AND agn_end_eff_dt
UNION ALL
SELECT fae_agent_nbr agent_nbr, fae_ssn_last_4digits ssn_nbr,
fae_address_ln1 address_line1, fae_address_ln2 address_line2,
fae_city_nm city, fae_state_cd state, fae_zip_cd zip,
fae_bus_phone business_phone, fae_supv_region_cd region,
fae_territory_cd territory, fae_market_cd market,
-- FAE_AGT_COMP_ST_CD COMP_STAT_CD,
agn_agt_comp_st_cd comp_stat_cd, fae_emplmt_dt emp_date,
fae_agent_type_cd status_cd, fae_first_nm first_name,
fae_last_nm last_name, 0 p_agent_bonus_class_id
FROM r2t_adr_epc_agent_info LEFT OUTER JOIN p1t_tot_agent
ON fae_agent_nbr = agn_agent_nbr
WHERE fae_agent_type_cd = '13'
-- Next line for testing of a subset of data - testing purposes only
-- AND FAE_SUPV_REGION_CD ='002'
AND fae_primary_agent_ind = 'X'
AND v_report_dt BETWEEN agn_start_eff_dt AND agn_end_eff_dt;
END IF;
EXCEPTION
WHEN NO_DATA_FOUND
THEN
--DBMS_OUTPUT.PUT_LINE ('no data ' || SQLERRM);
NULL;
WHEN OTHERS
THEN
--DBMS_OUTPUT.PUT_LINE ('error ' || SQLERRM);
--OPEN p_cur FOR
-- SELECT NULL
-- FROM DUAL;
RAISE;
END abc;

ORA-01002: fetch out of sequence error when using Oracle Thin Driver 9i with Weblogic 6.1

The simple program below is a client that executes a SELECT query -
there are 13 rows in the table, of which 10 are printed when I run the
program, then after that the ORA-01002 error is reported. I am not
doing anything with LOBs, or updates. I've tried putting
con.setAutoCommit(false) as well, but that does not do anything.
Why am I getting this error? Can anyone help.
Thanks
-H
Context ctx = null;
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL,
"t3://127.0.0.1:7001");
PreparedStatement stmt = null;
ResultSet rs = null;
UserTransaction ut = null;
try {
ctx = new InitialContext(ht);
javax.sql.DataSource ds
= (javax.sql.DataSource) ctx.lookup ("jtaXADS");
java.sql.Connection conn = ds.getConnection();
// You can now use the conn object to create
// Statements and retrieve result sets:
ut = (UserTransaction)
ctx.lookup("javax.transaction.UserTransaction");
ut.begin();
stmt = conn.prepareStatement("select firstname,surname from
EMPLOYEE ");
stmt.executeQuery();
rs = stmt.getResultSet();
// Close the statement and connection objects when you are finished:
while (rs.next())
System.out.println("Result is " + rs.getString("firstname") + " " +
rs.getString("surname"));
ut.commit();
stmt.close();
conn.close();
catch (Exception e) {
e.printStackTrace();
// a failure occurred
finally {
try {ctx.close();
rs.close();}
catch (Exception e) {
// a failure occurred
e.printStackTrace();

Thanks everybody.
I have tried this, calling ut.begin() first before getConnection,
however no difference. However the problem goes away if I call
stmt.setFetchSize(100);
But I would prefer not to have to code this in every time!!!
I see there is a setting within Weblogic Admin console to see the
row-prefetch, but that is already set to 45 rows, so why do have to
explicitly call stmt.setFetchSize(100)!!!
Thanks
-H
"Carl Lawstuen" <[email protected]> wrote in message news:<[email protected]>...
Agreed. The transaction must start before the connection. This is what
is most likely causing the error.
"Nils Winkler" <[email protected]> wrote in message
news:[email protected]...
Hi,
one more thing: The UserTransaction has to be started before you obtain
the connection, not after.
Nils
Humphrey wrote:
The simple program below is a client that executes a SELECT query -
there are 13 rows in the table, of which 10 are printed when I run the
program, then after that the ORA-01002 error is reported. I am not
doing anything with LOBs, or updates. I've tried putting
con.setAutoCommit(false) as well, but that does not do anything.
Why am I getting this error? Can anyone help.
Thanks
-H
Context ctx = null;
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL,
"t3://127.0.0.1:7001");
PreparedStatement stmt = null;
ResultSet rs = null;
UserTransaction ut = null;
try {
ctx = new InitialContext(ht);
javax.sql.DataSource ds
= (javax.sql.DataSource) ctx.lookup ("jtaXADS");
java.sql.Connection conn = ds.getConnection();
// You can now use the conn object to create
// Statements and retrieve result sets:
ut = (UserTransaction)
ctx.lookup("javax.transaction.UserTransaction");
ut.begin();
stmt = conn.prepareStatement("select firstname,surname from
EMPLOYEE ");
stmt.executeQuery();
rs = stmt.getResultSet();
// Close the statement and connection objects when you are finished:
while (rs.next())
System.out.println("Result is " + rs.getString("firstname") + " " +
rs.getString("surname"));
ut.commit();
stmt.close();
conn.close();
catch (Exception e) {
e.printStackTrace();
// a failure occurred
finally {
try {ctx.close();
rs.close();}
catch (Exception e) {
// a failure occurred
e.printStackTrace();
============================
[email protected]

ORA 01002 error - Fetch out of sequence

I am using COMMIT statement inside CURSOR FOR LOOP after inserting records. I am not using FOR UPDATE. But still I see fetch out of sequence error. I need to do commit intervals of every 1000 insert statements. How to resolve this error?

The reason of your error from oracle point of view is --
ORA-01002: fetch out of sequence
Cause: This error means that a fetch has been attempted from a cursor which is no longer valid. Note that a PL/SQL cursor loop implicitly does fetches, and thus may also cause this error. There are a number of possible causes for this error, including: 1) Fetching from a cursor after the last row has been retrieved and the ORA-1403 error returned. 2) If the cursor has been opened with the FOR UPDATE clause, fetching after a COMMIT has been issued will return the error. 3) Rebinding any placeholders in the SQL statement, then issuing a fetch before reexecuting the statement.
Action: 1) Do not issue a fetch statement after the last row has been retrieved - there are no more rows to fetch. 2) Do not issue a COMMIT inside a fetch loop for a cursor that has been opened FOR UPDATE. 3) Reexecute the statement after rebinding, then attempt to fetch again.
Now, my question is - are attempting any fetches inside any for loop - which will throw this error? Just check it - and let us know your feedback.
Regards.
Satyaki De.

ORA-01002: fetch out of sequence error

Hello friends,
I m facing a prob using a cursor for update.
here is a piece of code:
DECLARE
               CURSOR c_tot_inv_qty (p_prd_id tr_periods.period_id%TYPE) IS
SELECT total_inv_qty, item_id, period_id, dc_id
FROM inv_dc_tmp
WHERE period_id = p_prd_id + 1
FOR UPDATE OF total_inv_qty;
BEGIN
          FOR pd IN (     SELECT period_id
                         FROM tr_periods
                         WHERE status_flag = 1
                         AND period_id >= 46
LOOP
               FOR t_tot_inv_qty IN c_tot_inv_qty(pd.period_id) LOOP
                    BEGIN
SELECT inv_forecast_qty
INTO l_inv_fc_qty
FROM inv_dc_tmp
WHERE item_id = t_tot_inv_qty.item_id
AND period_id = pd.period_id
AND dc_id = t_tot_inv_qty.dc_id;
                    EXCEPTION
                         WHEN NO_DATA_FOUND THEN
                              l_inv_fc_qty := 0;
                    END;
UPDATE inv_dc_tmp
SET total_inv_qty = l_inv_fc_qty
WHERE CURRENT OF c_tot_inv_qty;
               END LOOP;
          END LOOP;
          COMMIT;
END;
i have written commit after the loop..but still it raise an error ORA-01002: fetch out of sequence
i m unable to find out the soln
i need ur help.
Thanks
RSD

I'm not sure what your code is trying to accomplish, but give this a whirl. It might be better than all that looping and cursors. I don't have any sample data/tables so I'm largely guessing here.
update inv_dc_tmp i
set    i.total_inv_qty =
          (select sum(t.inv_forecast_qty)
           from   inv_dc_tmp t
                 ,tr_periods p
           where t.period_id = p.period_id
           and    p.status_flag = 1
           and    p.period_id >= 46
           and    t.period_id     = i.period_id - 1
           and    t.item_id       = i.item_id
           and    t.dc_id         = i.dc_id
where exists
          (select 1
           from   tr_periods p
           where p.period_id = i.period_id - 1
           and    p.status_flag = 1
           and    p.period_id >= 46
;Extremely UNtested.

Ora-08102 - error help me out

dear all,
Im getting ora-8102 error
"ORA-00604: error occurred at recursive SQL level 1
ORA-08102: index key not found, obj# 49, file 47, block 25578 (2)" while im creating index on newly created table . I found the suggestion doc from metalink for the same. but it didn't work. because the obj#49 is the index (I_CON2) which related to table CON$. so im not able to rebuild the index as suggested in metalink.
Im getting the same erorr for all schema even creating new table with constraints.
Thanks
mohan

Why not ?Just a guess, since there is no error message from OP, Probably because:
SQL> alter index I_CON2 rebuild ;
alter index I_CON2 rebuild
ERROR at line 1:
ORA-00701: object necessary for warmstarting database cannot be altered
SQL> disc
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production
SQL>

ORA-00604: error occurred at recursive SQL level 2

Hello,
I am trying to create a simple table and I am getting a ora error as below.
SQL> create table album(name varchar2(100),image blob);
create table album(name varchar2(100),image blob)
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 2
ORA-01422: exact fetch returns more than requested number of rows
how to resolve this?Any help..
Thanks,
Ranz.

Hi,
*@Anurag Tibrewal,*
I followed as per the order od statements you gave. Initially there was no table "ALBUM" when I executed the first 2 statements.
3rd staement i created a table "ALBUM" and then 4th and 5th statement showed that I have a table called "ALBUM".
Now when again I wanted to drop the table I am getting the same error.
SQL> drop table album
2 ;
drop table album
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-01422: exact fetch returns more than requested number of rows
*@Jean-Valentin*
I am not finding the trace file for today as i checked the alert log. When i searched for the the error I found the error for March 4. No ora-00604 error from today.
As shown in ALERT LOG.
Thu Mar 04 10:50:41 2010
Errors in file d:\oracle\product\10.2.0\admin\raneeshtest\bdump\*raneeshtest_j000_5976.trc*:
ORA-00604: error occurred at recursive SQL level 1
ORA-04030: out of process memory when trying to allocate 172 bytes (Typecheck,seg:kggfaAllocSeg)
ORA-12012: error on auto execute of job 1
ORA-04030: out of process memory when trying to allocate 16428 bytes (pga heap,kgh stack)
Trace file details:
Dump file d:\oracle\product\10.2.0\admin\raneeshtest\bdump\raneeshtest_j000_5976.trc
Thu Mar 04 10:50:31 2010
ORACLE V10.2.0.3.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Personal Oracle Database 10g Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
Windows NT Version V6.0 Service Pack 1
CPU : 2 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:27M/2037M, Ph+PgF:341M/4352M, VA:4M/2047M
Instance name: raneeshtest
Redo thread mounted by this instance: 1
Oracle process number: 15
Windows thread id: 5976, image: ORACLE.EXE (J000)
*** 2010-03-04 10:50:31.224
*** ACTION NAME:() 2010-03-04 10:50:30.276
*** MODULE NAME:() 2010-03-04 10:50:30.195
*** SERVICE NAME:(SYS$USERS) 2010-03-04 10:50:30.195
*** SESSION ID:(137.401) 2010-03-04 10:50:30.195
*********START PLSQL RUNTIME DUMP************
***Got internal error Exception caught in pfrrun() while running PLSQL***
***Got ORA-4030 while running PLSQL***
PACKAGE SYSMAN.MGMT_ADMIN_DATA:
library unit=3416af50 line=128 opcode=117 static link=0 scope=0
FP=3ca31374 PC=30f42000 Page=0 AP=3ca47b2c ST=3ca32778
DL0=3ca46564 GF=3ca465b0 DL1=3ca46584 DPF=3ca465a8 DS=30f421e4
DON library unit variable list instantiation
0 3416af50 3ca465b0 3ca2005c
1
2
3
4
5
6
7
scope frame
2 0
1 3ca31374
package variable address size
0 3ca46698 16
1 3ca466a8 16
2 3ca466b8 16
3 3ca466c8 16
4 3ca466d8 16
5 3ca466e8 20
6 3ca466fc 16
7 3ca4670c 20
8 3ca46720 16
9 3ca46730 4
10 3ca46734 4
11 3ca46738 4
12 3ca4673c 4
13 3ca46740 4
14 3ca46744 4
15 3ca46748 4
16 3ca4674c 4
17 3ca46750 4
18 3ca46754 4
19 3ca46758 4
20 3ca4675c 4
21 3ca46760 20
22 3ca46774 20
23 3ca46788 20
24 3ca4679c 20
25 3ca467b0 4
26 3ca467b4 4
27 3ca467b8 4
28 3ca467bc 4
29 3ca467c0 16
30 3ca467d0 16
31 3ca467e0 8
32 3ca467e8 39
33 3ca46810 39
34 3ca46838 521
35 3ca46a44 521
36 3ca46c50 140
37 3ca46cdc 140
38 3ca46d68 30
39 3ca46d88 30
40 3ca46da8 30
41 3ca46dc8 30
42 3ca46de8 30
43 3ca46e08 30
44 3ca46e28 30
45 3ca46e48 30
46 3ca46e68 30
47 3ca46e88 30
48 3ca46ea8 30
49 3ca46ec8 30
50 3ca46ee8 140
51 3ca46f74 140
52 3ca47000 30
53 3ca47020 30
54 3ca47040 30
55 3ca47060 30
56 3ca47080 39
57 3ca470a8 39
version=43123476 instantiation size=2920
line pcode offset
1 2
4 620
5 632
6 632
7 638
8 644
14 650
29 810
44 970
47 992
48 1000
49 1008
50 1016
51 1024
52 1032
53 1040
54 1048
55 1056
56 1064
57 1072
60 1080
128 1814
196 2548
197 2554
198 2560
199 2566
205 2572
206 2578
438 2584
1 2586
***********END PLSQL RUNTIME DUMP************
*** 2010-03-04 10:50:40.690
ORA-12012: error on auto execute of job 1
ORA-04030: out of process memory when trying to allocate 16428 bytes (pga heap,kgh stack)
*** 2010-03-04 10:50:41.206
ORA-00604: error occurred at recursive SQL level 1
ORA-04030: out of process memory when trying to allocate 172 bytes (Typecheck,seg:kggfaAllocSeg)
ORA-12012: error on auto execute of job 1
ORA-04030: out of process memory when trying to allocate 16428 bytes (pga heap,kgh stack)
SQL> select * from dual;
D
X
SQL>
This is the output. Its returning corredclty. Now what is the problem? Pls help me.

Oracle Report raises ORA-01002 Fetch out of sequence

ORA-01002 Fetch out of sequence in runtime execution of
oracle report 3.0 and 2.5 in client/server environment.
The same sql query works in sqlplus without any problem.
If I change the criteria (where clause) the error sometime
disappear. I can't explain this weird behaviour.
Oracle server version is 7.1.5 on Digital VMS.
Any Help will be welcome.
null

ORA-01002 Fetch out of sequence in runtime execution of
oracle report 3.0 and 2.5 in client/server environment.
The same sql query works in sqlplus without any problem.
If I change the criteria (where clause) the error sometime
disappear. I can't explain this weird behaviour.
Oracle server version is 7.1.5 on Digital VMS.
Any Help will be welcome.
null

Ora:getElement erroring out at runtime

Similar Messages

Maybe you are looking for