Ora-12801

Does anyone know how to turn off parallel query mode?
SQL*Plus: Release 8.1.7.0.0
HP-UX Left B.11.11 U 9000/800 (ta)
I/O function: O, mode: 1, on file/table: INVC_DTL
ORA-12801: error signaled in parallel query server P000
ORA-00942: table or view does not exist
ORACLE Driver Error [-52]: Open driver request failed.

We currently don't have a dba(maybe that is obvious). I do appreciate your suggestions and YES we are following up on those. I did find the example you mentioned last night, came in this morning and found out I do not have the permissions.. I was able to create the table but not the trigger..go figure.. So I have to get the permission/access
to finish this.
Our sysadmin was late getting in this morning due to weather conditions had other issues to address, was not aware of the log files you mentioned and is currently looking at them as I type this and he'll be providing the permission/access for me.
Per my conversation with him, he asked the question about turning off the parallel query.. I obviously don't have a clue and said I would post the question and see what kind of response we might get??
We are doing the best we can given the circumstances we are operating under.
Thanks for any future guidance that you may direct our way.

Similar Messages

ORA-12801: error signaled in parallel query server

Hi all
What are the basic reasons of this error:
ORA-12801: error signaled in parallel query server
I have received this error while running report

>>>What are the basic reasons of this error:
ORA-12801: error signaled in parallel query server string
Cause: A parallel query server reached an exception condition.
Action: Check the following error message for the cause, and consult your error manual for the appropriate action.

ORA-12801 ORA-08103 while running gather schema stats in R12

Hi All,
We have recently upgraded from 11.5.9 to R12.1.1 on RHEL 4.8
Database version is 10.2.0.5
We are running Gather schema stats on R12.1.1 but its Errored out with below messages.
ORA-12801: error signaled in parallel query server P006
GL.GL_JE_LINES
ORA-08103 : object no longer exists
Please advice if anybdy face this issue.
Thanks
RB

Please see (GATHER SCHEMA STATISTICS COMPLETED WITH ERROR WHEN RUNNING FOR GL SCHEMA. [ID 1068541.1]).
Thanks,
Hussein

Regarding ORA-12801,ORA-01843 error

Hi all,
When I am running the mapping I am getting the
ORA-12801: error signaled in parallel query server P079
ORA-01843: not a valid month error
My mapping was validated and deployed suceesfully.
Please give me the suggestions.
Thanks,
Venkat

Is the source field a date field or a varchar? Sounds like you are hitting a source data error.
Try grabbing the insert (or merge, or whatever) statement from the mapping and running it on its own. If that fails with the same error, then try running the select portion of the statement to debug for the error.
Assuming that you are using a to_Date function and if you are having real trouble finding the data error, you at least know which table the field is being sourced from. Run a little test - something like:
declare
cursor curs is select the_source_field from the_source_table;
begin
for rec in curs loop
     declare
        dateval date
     begin
        dateval := to_Date(rec.the_source_field,'yyyymmdd');   --or whatever format mask it is you are using
     exception
         when others then
             dbms_output.put_line('FAILED TO_DATE ON SOURCEVAL: '||rec.the_source_field||' with error: '||substr(sqlerrm,1,150));
     end;
end loop;
end;Once you know the problems with the data then you can consider how best to deal with them.
Cheers,
Mike

ORA-12801: error signaled in parallel query server P000

Hello All,
Week before one of the APPLY process ABORTED with following error:
ORA-12801: error signaled in parallel query server P000
ORA-04031: unable to allocate 104 bytes of shared memory ("streams pool","unknown object","apply shared t","knalfGetTxn:lcr")
We are using ORACLE 10.2.0.4.0 on HP unix B.11.23
For now, I have started the APPLY process again and it's working properly.
When I looked into the trace file it shows following
A001: [enq: TM - contention] name|mode=544d0002, object #=2a67, table/partition=0
*** 2009-06-15 10:53:57.897
A001: warning -- apply server 1, sid 302 waiting on user sid 267 for event (since 302 seconds):
A001: [enq: TM - contention] name|mode=544d0002, object #=2a67, table/partition=0
*** 2009-06-15 10:58:58.792
A001: warning -- apply server 1, sid 302 waiting on user sid 267 for event (since 603 seconds):
A001: [enq: TM - contention] name|mode=544d0002, object #=2a67, table/partition=0
*** 2009-06-15 12:14:36.679
A001: [enq: TX - row lock contention] name|mode=54580004, usn<<16 | slot=90028, sequence=1b743
*** 2009-06-15 12:19:36.961
A001: warning -- apply server 1, sid 302 waiting on user sid 181 for event (since 300 seconds):
A001: [enq: TX - row lock contention] name|mode=54580004, usn<<16 | slot=90028, sequence=1b743
*** 2009-06-15 12:24:37.417
A001: warning -- apply server 1, sid 302 waiting on user sid 181 for event (since 600 seconds):
A001: [enq: TX - row lock contention] name|mode=54580004, usn<<16 | slot=90028, sequence=1b743
*** 2009-06-15 12:29:37.906
A001: warning -- apply server 1, sid 302 waiting on user sid 181 for event (since 901 seconds):
A001: [enq: TX - row lock contention] name|mode=54580004, usn<<16 | slot=90028, sequence=1b743
*** 2009-06-15 12:34:37.428
A001: warning -- apply server 1, sid 302 waiting on user sid 181 for event (since 1201 seconds):
A001: [enq: TX - row lock contention] name|mode=54580004, usn<<16 | slot=90028, sequence=1b743
*** 2009-06-19 11:26:44.601
A001: [enq: TX - row lock contention] name|mode=54580006, usn<<16 | slot=8001e, sequence=1a4af
*** 2009-06-19 11:31:43.753
A001: warning -- apply server 1, sid 302 waiting on user sid 212 for event (since 300 seconds):
A001: [enq: TX - row lock contention] name|mode=54580006, usn<<16 | slot=8001e, sequence=1a4af
*** 2009-06-19 11:36:44.149
A001: warning -- apply server 1, sid 302 waiting on user sid 212 for event (since 600 seconds):
A001: [enq: TX - row lock contention] name|mode=54580006, usn<<16 | slot=8001e, sequence=1a4af
*** 2009-06-19 11:41:43.775
A001: warning -- apply server 1, sid 302 waiting on user sid 212 for event (since 900 seconds):
A001: [enq: TX - row lock contention] name|mode=54580006, usn<<16 | slot=8001e, sequence=1a4af
*** 2009-06-23 16:55:24.002
A001: [enq: TM - contention] name|mode=544d0004, object #=2c05, table/partition=0
*** 2009-06-29 09:48:58.166
A001: [enq: TM - contention] name|mode=544d0004, object #=2c05, table/partition=0
*** 2009-07-01 06:02:37.236
A001: [enq: TM - contention] name|mode=544d0004, object #=2c05, table/partition=0
*** 2009-07-01 11:46:43.672
error 12801 in STREAMS process
ORA-12801: error signaled in parallel query server P000
ORA-04031: unable to allocate 104 bytes of shared memory ("streams pool","unknown object","apply shared t","knalfGetTxn:lcr")
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-12801: error signaled in parallel query server P000
ORA-04031: unable to allocate 104 bytes of shared memory ("streams pool","unknown object","apply shared t","knalfGetTxn:lcr")
Can you please help to provide details on that how i can fix this problem permanetely.
Any suggestions would be great!
Thanks,
Nick

It seems that you are using Oracle database and not Berkeley Database.
To fix ORA-04031 errors on streams pool, you need to increase streams pool size with
alter system set streams_pool_size=<the right value>;See recommandations in http://download.oracle.com/docs/cd/B19306_01/server.102/b14229/strms_mprep.htm#i1006278

ORA-12801: error signaled in parallel query server P007

Hi friends,
I am running a update on a big table with parallel clause.
I got the below error.Can someone help what should i next? This query takes a long time to execute(nearly 1 hour).
I searched on google and metalink but no success yet.
=======
ORA-12801: error signaled in parallel query server P007
ORA-00001: unique constraint (VEL5APPO.BL1_CHARGE_PK) violated
=======
Cheers,
Kunwar

Kunwar wrote:
Hi friends,
I am running a update on a big table with parallel clause.
I got the below error.Can someone help what should i next? This query takes a long time to execute(nearly 1 hour).
I searched on google and metalink but no success yet.
=======
ORA-12801: error signaled in parallel query server P007
ORA-00001: unique constraint (VEL5APPO.BL1_CHARGE_PK) violated
=======Not sure why you think this a complex and unusual and difficult to understand error. It is very clear what is happening.
WHAT: your code violates constraint VEL5APPO.BL1_CHARGE_PK that says that one or more columns must contain unique values.
Who says it? That is specified by the first line in the error stack.
WHO: parallel query process 7 ran into the constraint error
So what's happening? Your SQL is executed in parallel. Up to 7 PX slaves are used to run your SQL - with each slave running the SAME SQL for DIFFERENT rowid ranges. PX slave 7 attempted an insert/update that would have resulted in a duplicate row. The database constraint protecting the integrity of that table, prevented it.
So the error is very clear as to what is wrong, why it is wrong, and where it is happening.
I fail to understand that you search google and metalink and failed to find answers, when the error is meaningful....?

SQL Error: ORA-12801: error signaled in parallel query server P012 ORA-0001

Dear all
We are in BI 7.0 and oracle 10.2.02 and OS AIX 5.3 and we are getting the ORA -12801 while attribute change run
and aggregates rollup.
plz help
Regards
Amiya Kumar

Hi...
Check SAP Note 934281 - No 'Star Transformation' for a Hierarchy Changerun......
Symptom
The SQL command of a hierarchy changerun is executed with a
PARALLEL hint under ORACLE, and the system therefore always accesses the fact table with a full tablescan although only a little may be read.
Other terms
Query, aggregate, realignment run, ORACLE, Parallel Hint, ORA-12801,
ORA-01652, start transformation, parallel hint
Reason and Prerequisites
The Parallel hint should only be set when the aggregate is built again,
but not with the delta realignment run. There was no check made in case of a hierarchy changerun. So hierarchy changerun was executed with the
parallel hint.
Solution
With the following code correction, the hierarchy changerun also adapts
to star transformation when an aggregate has delta changes.
BW3.0B
           Import Support Package 31 for Release 3.0B (BW3.0B Patch 31 or SAPKW30B31) into your BW system. The Support Package will be available when note 0872272 with the short text "SAPBWNews BW 3.0B Support Package 31", describing this Support Package in more detail, is released for customers.
BW3.1C (Content)
           Import Support Package 25 for Release 3.1C (BW3.1C Patch 25 or SAPKW31025) into your BW system. The Support Package will be available when note 0872274 with the short text "SAPBWNews BW 3.1C Support Package 25", describing this Support Package in more detail, is released for customers.
BW 3.50
           Import Support Package 17 for Release 3.50 (BW3.50 Patch 17 or SAPKW35017) into your BW system. The Support Package will be available when note 0872277 with the short text "SAPBWNews BW SP17 NetWeaver'04 Stack 17", describing this Support Package in more detail, is released for customers.
SAP NetWeaver 2004s BI
           Import Support Package 13 for SAP NetWeaver 2004s BI (BI-Patch 13 or SAPKW70013) into your BI system. The Support Package will be available when note 991093 with the short text "SAPBINews BI 7.0 SP13", describing this Support Package in more detail, is released for customers.
Regards,
Debjani.........
Edited by: Debjani Mukherjee on Oct 10, 2008 12:08 PM

SQL Error: ORA-12801: error signaled in parallel query server P007

Hi all
I am getting the following error when doing aggregation for a cube
SQL Error: ORA-12801: error signaled in parallel query server P007.Job is showing as finished but no aggregation is hapenning.
regards
KK

for ORA- 20000
check the note below it shows you have insufficient authorizations.
Reason and Prerequisites
You are using BW 7.00 with Support Package 07 or higher.
The BW module for the update statistics has been adjusted to SAPDBA or BRConnect (with regard to the heuristic, which is when, how and which statistics are created). To ensure that all table changes are taken into account, the relevant information must be flushed from the Oracle memory before the update statistics is carried out. For this purpose, the SAPCONN role (higher than ORA 10.2) or SAP SAP<sid> oder SAPR3 (ORA 10.1) requires additional authorizations that were not assigned up to now.
 Note 963760 - 'ORA-20000: Insufficient privileges' for creating statistics
For Error -for SQL Error: ORA-01418: specified index does not exist
check note below-
Note 337830 - BW: ORA-1418 in system log
It seems that Index no longer exist which you are trying to delete.The 900 index, which exists on the F table only if the E table is partitioned, is deleted twice and on the second attempt it no longer exists.

Note 1003360 - BW fact tables: Deleting index from process chain terminates
If it relates your error it requires corrections for SP-12.
Hope it Helps
Chetan
@CP..

ORA-12801 and ORA-30563

Hi,
I have a mapping failed with the two error codes. Does anyone know what the cause maybe? Thanks.
ORA-12801: error signaled in parallel query server P002
ORA-30563: outer join operator (+) not allowed in select-list
The failing happened at a point where I have an outer join statement, where one of the join condition uses a function like
...where a.sup_id=b.supid_lookup(pc,sc) (+) and a.plant_code=b.plant_code (+)
I don't see these error when run under debug and the join did not get me the data neither.

well, like the error sais, the (+) is in the SELECT list.
If the error is in fact raised from the WHERE clause, you might to wrap the function call into an inline view. What I don't get from you example, is the meaning of 'b'. you seem to treat it both as a table and as a package containing the function 'supid_lookup'
select * from tab1 a
left outer join (select b.*,supid_lookup(b.pc,b.sc) sup_id from tab2 b) v using (sup_id,plant_code)
But without a description of your tables, I might be making some wrong assumptions.
Cheers

Urgent, ORA-12801: error signaled in parallel query server P000

Hi Guys,
I am using Oracle 9i Enterprise Edition Release 9.2.0.1.0 with Windows 2000 Server.
I have just upgrade my database from 8i to 9i. I am facing this problem in a lot of queries in my application after upgrade. I tried to searched out but unable to find the reason yet.
Is there any parameter which i should /should not use? Or need to change any parameter.
Oracle Error Occured: ORA-12801: error signaled in parallel query server P000
Thanks in advance.
Brgs,
Hassan

Well, the error stack should be displayed along with the 12801 error.
If not, look the comment for the error I posted above: use event 10397 to display the actual error.ALTER SESSION SET EVENTS '10397 trace name context forever, level 1'; and if the error raises, then you'll get the source message, not the PQ message.
See note 21281.1 on Metalink.
Regards,
Yoann.

ERROR - ORA-12801: error signaled in parallel query server P098

Hi Experts,
Today one of our developer complained that they are continously getting the below error in their application logs
ERROR - ORA-12801: error signaled in parallel query server P098
ORA-01461: can bind a LONG value only for insert into a LONG column
When we checked we didn't find any error in our alert log and we have enough space in our temp tablespace as we are unable to understand exactly why are we getting the above error.
Please help..
Thanks....

Please check, Couple of useful MOS Notes
How to Analyze an ORA-12801 (Doc ID 1187823.1)
ORA-01461 Can Bind A Long Value Only For Insert Into A Long Column (Doc ID 387587.1)

"ORA-12801: error signalled in parallel query server"

A client of ours is using our reporting tool, Impromptu 6, to report from an Oracle 8.1.6 database connecting with Net8. He has built a simple report which displays a single item from a single table but it fails with:-
Query Server Error
"ORA-12801: error signalled in parallel query server"
Error number -9:
DMS-E-GENERAL, A general exception has occurred during operation 'asynchronous open'.
According to Oracle documentation, there should be an accompanying error message with the ORA-12801 which gives more information.
The last few lines of the DMAUDFIL show:-
OCI OEXEC LINE 5219:orsgbl.C
OCI OEXEC LINE 5219:orsgbl.C
CHECK_CODE2 -12801 LINE 5249:orsgbl.C
OCI OERHMS -12801,ORA-12801: error signaled in parallel query server
LINE 858:orsmisc.C
The DMAPIFIL shows no error.
The query being sent to the database is:-
select T1."PRD_LVL_PARENT" "c1"
from "JDAOPRD"."PRDMSTEE" T1
where PRD_LVL_PARENT is defined as NUMBER(12)
If they paste the above into SQL*Plus, it works fine.
Reporting any other items from the database do not give this error.
If they use the Oracle ODBC driver, they don't get the problem but it runs a lot slower.

As your ORA-12801 is followed by a ORA-0600 this should be a database bug. First of all I'd bring the database on the last patchlevel (10.2.0.5), and if the error persists you can use the ORA-600/ORA-7445 Troubleshooter (Metalink Note 153788.1). If this doesn't help either you should log a SR with oracle support (you need a support contract to do all those steps).
Also I don't think forms 5 is certified against a 10gR2 database, so this might cause your trouble. For 6i you should use the latest patchset.
If you don't have a valid support contract you might have a chance in putting your query in a database procedure.
cheers

ORA-12801: error signaled in parallel query server P002

We are encountering the below problem frequently in SUN SOLARIS BOX
ORA-12801: error signaled in parallel query server P002
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP

Hi,
This is TEMP tablespace issue.
1. Identify the query(s) for which it is happening.
2. Size your TEMP tablespace by monitoring usage of it.
set lines 200
column osuser format A20
column tablespace format A20
SELECT b.tablespace, b.segfile#, b.segblk#, b.blocks, a.sid, a.serial#,
a.username, a.osuser, a.status
FROM v$session a,v$sort_usage b
WHERE a.saddr = b.session_addr
and a.osuser = nvl('&osuser',a.osuser)
ORDER BY b.tablespace, b.segfile#, b.segblk#, b.blocks;
3. Check all queries have required join conditions or not. Cartezian product of two huge tables creates problem.
Dilipkumar Patel.

Apply process is aborting with:ORA-12801: error signaled in parallel query

hi,
We created a queue of a specific type, capture and apply process on the queue. Then we started the queue capture and the apply process. The problem is that the apply process is getting enabled and with in moments going into aborted state. wea re getting the follwoing error:
ORA-12801: error signaled in parallel query server P000
ORA-00600: internal error code, arguments: [kwqiceval:anyconv], [], [], [], [], [], [], []
Any idea what could have gone wrong?
scripts:
exec dbms_aqadm.create_queue_table(queue_table=>'qt_anc',queue_payload_type=>'type_anc',multiple_consumers=> true, compatible => '9.0');
exec dbms_aqadm.create_queue (queue_name => 'q_anc',queue_table=>'qt_anc');
EXEC DBMS_AQADM.START_QUEUE (queue_name => 'q_anc');
DECLARE
emp_rule_name_dml VARCHAR2(300);
emp_rule_name_ddl VARCHAR2(300);
BEGIN
DBMS_STREAMS_ADM.ADD_TABLE_RULES(
table_name => 'ops.t_anc',
streams_type => 'capture',
streams_name => 'capture_anc',
queue_name => 'strmadmin.q_anc',
include_dml => true,
include_ddl => false,
source_database => null,
dml_rule_name => emp_rule_name_dml,
ddl_rule_name => emp_rule_name_ddl);
DBMS_APPLY_ADM.SET_ENQUEUE_DESTINATION(
rule_name => emp_rule_name_dml,
destination_queue_name => 'strmadmin.q_anc');
END;
DECLARE
emp_rule_name_dml VARCHAR2(300);
emp_rule_name_ddl VARCHAR2(300);
BEGIN
DBMS_STREAMS_ADM.ADD_TABLE_RULES(
table_name => 'ops.t_anc',
streams_type => 'apply',
streams_name => 'apply_anc',
queue_name => 'strmadmin.q_anc',
include_dml => true,
include_ddl => false,
source_database => null,
dml_rule_name => emp_rule_name_dml,
ddl_rule_name => emp_rule_name_ddl);
DBMS_APPLY_ADM.SET_ENQUEUE_DESTINATION(
rule_name => emp_rule_name_dml,
destination_queue_name => 'strmadmin.q_anc');
END;
BEGIN
DBMS_APPLY_ADM.START_APPLY(
apply_name => 'apply_anc');
END;
BEGIN
DBMS_CAPTURE_ADM.START_CAPTURE(
capture_name => 'capture_anc');
END;
/

Hello
The above configuration is never supported. The implicit capture expects the queue payload to be SYS.ANYDATA and same with implicit apply also.
However you can use Streams Messaging capability to achieve this. You need to wrap the messages with SYS.ANYDATA for this to work. The implicit capture uses a persistent logminer session to generate LCRs and it then wraps it with SYS.ANYDATA and enqueues into the capture queue, it then propagated to apply queue. You can generate LCRs and wrap it with SYS.ANYDATA and then enqueue into the capture queue then apply can recognise the messages.
Here is an example on creating LCRs (tested in 10g):
CREATE TABLE lcr_test (col1 NUMBER);
DECLARE
     l_lcr SYS.LCR$_ROW_RECORD;
BEGIN
     l_lcr :=
SYS.LCR$_ROW_RECORD.CONSTRUCT
     source_database_name=>SYS_CONTEXT('USERENV','DB_NAME'),
     command_type=>'INSERT',
     object_owner=>USER,
     object_name=>'LCR_TEST'
     l_lcr.ADD_COLUMN('new','col1',SYS.AnyData.ConvertNumber(99));
     l_lcr.EXECUTE(TRUE);
     COMMIT;
END;
SELECT * FROM lcr_test;
Converting to SYS.ANYDATA:
DECLARE
     l_lcr SYS.LCR$_ROW_RECORD;
     l_anydata SYS.ANYDATA;
BEGIN
     l_lcr :=
SYS.LCR$_ROW_RECORD.CONSTRUCT
     source_database_name=>SYS_CONTEXT('USERENV','DB_NAME'),
     command_type=>'INSERT',
     object_owner=>USER,
     object_name=>'LCR_TEST'
     l_lcr.ADD_COLUMN('new','col1',SYS.AnyData.ConvertNumber(99));
     l_anydata:=SYS.ANYDATA.ConvertObject(l_lcr);
     ENQ_PROC(l_anydata);
     COMMIT;
END;
Thanks,
Rijesh

ORA-12801 error signalled in parallel query with ORA-00018 max # session

Hello,
I've just run dbca to create a new database. On completion I received the following:
ORA-12801 error was signalled in parallel query server
ORA-00018 maximum number of sessions exceeded
ORA-06512 at sys_utl_recomp line 760
ORA-06512 as sys_utl_recomp line 773
ORA-06512 as sys_utl_recomp line 1
The processes are set at 100, sessions is set at 115?
Can you tell how to address this error and resolve the problem? I'm thinking that I should rerun sys_utl_recomp

Hi,
You didn't mention oracle version as well OS.
might be you hit a bug.
check the below link for reference
https://metalink2.oracle.com/metalink/plsql/f?p=130:14:8051847734518941130::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,21564.1,1,1,1,helvetica
Regards,
Taj

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-12801

Similar Messages

Maybe you are looking for