Parallel query execution on Multiprovider with noncumulative KF

Hello !
We built a multiprovider (MP) on three not overlapping (disjunct?) basis cubes, which are all stock cubes, partitioned by 0PLANT and copies of 0IC_C03.
The Multiprovider-explain of TX RSRT says:
"The MultiProvider query is executed sequentially (reason: NCUM)".
Ok so far, maybe its not possible to execute queries in parallel on that multiprovider even if desirable.
But I found note 781921 which says as symptom:
"If a MultiProvider query with non-cumulative key figures is processed in a parallel way, the system terminates due to a type conflict". That means that queries CAN be executed in parallel on MPs with noncumulative key figures.
Does anybody know if that type of queries can run in parallel or not ??
Any advice is appreciated.
Kind regards, Philipp

Note 717451 solves this.

Similar Messages

Data Driven Subscriptions Error - the query processor could not start the necessary thread resources for parallel query execution

Hi,
We are getting the following error when certain data driven subscriptions are fired off: "the query processor could not start the necessary thread resources for parallel query execution". I've read other posts that have the same error, and
the solution usually involves adjusting MaxDOP to limit the number of queries that are fired off in parallel.
Unfortunately, we cannot change this setting on our server for performance reasons (outside of data driven subscriptions, it negatively impacts our ETL processing times). We tried putting query hints like "OPTION (MAXDOP 2);" in the reports
that are causing the error, but it did not resolve the problem.
Are there any settings within Reporting Services that can be adjusted to limit the number of subscriptions that get fired off in parallel?
Any help is appreciated - thanks!

Yes, that is correct. It's a painful problem, because you don't know which specific subscription failed. For example, we have a data driven subscription that sends out about 800 emails. Lately, we've been having a handful of them fail. You don't know
which ones out of the 800 failed though, even from the RS log files - all it tells you is that "the
query processor could not start the necessary thread resources for parallel query execution".
Thanks, I'll try changing <MaxQueueThreads> and will let you know if it works.
On a side note: I've noticed that it is only reports with cascading parameters (ex. where parameter 2 is dependent on the selection from parameter 1) that get this error message...

Parallel Query/Execution

Guys,
What is parallel quering/execution? How does it help to improve the performance.
Thanks

Hi,
Parallel query is an Oracle feature designed to solve large-scale data warehouse reporting and DML I/O performance issues. It is easy to implement
PARALLEL_AUTOMATIC_TUNING=TRUE, include PARALLEL option on table DDL definition and it is in place.
This feature improves performance when used on a multi-cpu platform, with PARTITIONED tables (i.e... typcially FACT, or transaction records, where rowcount is approaching or greater than 100million). Oracle distributes the SQL workload against each table partition to an individual CPU. Rather than 1 CPU scanning a table, many CPUs are used to scan different table partitions of the same table at the same time (i.e. in parallel).

Partitioning For Optimal Parallel Query Execution

Hi All,
We are trying to design an architecture that benefits from partitioning and parallel query to obtain the best query response times for our system.
Let me start by describing the main table which has five columns:
Columns:
1) DocId ------- Numeric Primary Key Constraint (Unique)
2) Text ------- CLOB of XML Content
3) SCode ------- Varchar 12 ( service code Can be one of 200 values)
4) A_Date ------- Oracle Date ( The arrival date )
5) A_Month ------- Numeric partition key, the month number (1-12)
We insert 100,000 records daily so a month of data will contain 3,000,000 rows. The Text varies from 4k to 200k bytes and on average is around 30k bytes per document. A_Date is obtained when the C++ application receives a client connection. After document transmission is complete the DocId is obtained from an Oracle sequence. It is true that A_Date and DocId increase together. However because of varying document sizes and transmission rates, there is no guarantee that consistent order between the two columns exists.
For Example: If time (t) increases and the connection times are: t1, t2, t3, t4 and the document at t2 took long to transmit, we can have:
A_Date -------- DocId (From Oracle Sequence)
t2 -------------- 1004
t4 -------------- 1003
t3 -------------- 1002
t1 -------------- 1001
A_Month is simply the month number (1-12) extracted from the transmission entry timestamp. It is also our Partition Key (see below). When the year wraps around from 2006 to 2007, data for January will simpy fall into the 1st partition bucket, and so on..
QUERY NEEDS: Our queries are centered around a DateTime interval Where the left endpoint is current day/time. They can query the current day, current to 1 month back, current to 2 months back, .. current to 15 months back. We MUST RETURN a list of DocId's sorted in DESCENDING ORDER for screen display purposes.
In General we need to return sub-second for the 1st month. As we query further back in time longer response times between 1 and 4 seconds are acceptable.
PARTITIONING AND INDEXES:
The table is partitioned by A_Month as shown below:
Create Table IndexTable
PARTITION BY RANGE (A_Month)
( PARTITION p1 VALUES LESS THAN 1.1 ...
PARTITION p2 VALUES LESS THAN 2.1 ...
PARTITION p3 vALUES LESS THAN 3.1 ...
There are GLOBAL INDEXES on DocId, Text(Domain Index), and SCode.
A_Date is a LOCAL INDEX.
QUERY STRUCTURE:
My Query structure looks like this (for a 2 month query):
SELECT DocId from IndexTable WHERE
Contains (Text, 'BUSH and EARNINGS') > 0 AND
SCode in ('S1', 'S2', 'S3', 'S4') AND
A_Date Between '2006-01-15 11:00:00' AND '2006-03-15 11:00:00'
Order By DocId DESC;
QUESTIONS (THERE ARE THREE)
#### QUESTION 1 ####
As I examine various explain plans, the PSTART and PSTOP do not reflect consistency with my A_Date range. It seems to always display:
PStart PStop
RowId RowId
no matter what my A_Date range is.. I don't see it pruning my partitions. I cannot find documentation as to what RowId means or how it affects the optimizer's plan.
#### QUESTION 2 ####
I have tried parallelization hints on the table and indexes such as
/*+ PARALLEL( IndexTable, 4) */ and on the A_Date index
/*+ PARALLEL_INDEX( IndexTable, A_Date_Index, 4) */.
I can't really tell if the parallel hints make a difference.
However, the FIRST_ROWS hint makes a big difference if I nest the query inside a rownum clause as:
SELECT * from
( Select /+* first_rows */ ... WHERE CONTAINS... > 0 AND... )
Where ROWNUM <=20;
#### QUESTION 3 ####
I'm running close to the latest RedHat Linux and Oracle 10g2 and I have read about Parallel Slave Processes in Tom Kyte's Expert Oracle Architecture book in which he says you should see processes like:
ora...p000..
ora...p001..
ora...pnnn..
Which are the parallel slave processes. I have NEVER seen any oracle processes numbered as such running on my system when I run test queries. I have seen some q_ processes and others, but not the pnnn processes..
Can I benefit from parallel query without ever seeing these processes??
I Greatly Appreciate Any Advice To Any Of These Questions..
Joe

Well I can tell you this much. You will never get partition pruning if you don't have the partition key in the where clause.
I'm not sure about the parallel query. There was a time that this wasn't supported with Text indexes, but not sure if that still applies today.
In theory there are two levels of partitioning that can be defined that you may want to test out.
1st, range partition the base table and create a partitioned text index based on that. This is what you are currently doing.
2nd, in the storage preference for the $I table specify a range or hash partition (I've never tried this, but in theory it should work) on the token_text column. Try this out and see if it works.

Problem with temp space allocation in parallel query

Hello
I've got a query which matches two large result sets (25m+ rows) against each other and does some basic filtering and aggregation. When I run this query in serial it takes about 30 mins and completes successfully. When I specify a parallel degree of 4 for each result set, it also completes successfully in about 20 minutes. However, when I specify that it should be run in parallel but don't specify a degree for each result set, it spawns 10 parallel servers and after a couple of minutes, bombs out from one of the parallel servers with:
ORA-12801: error signaled in parallel query server P000
ORA-01652: unable to extend temp segment by 64 in tablespace TEMPThis appears to be when it is about to perform a large hash join. The execution plan does not change whether the parallel degree is specified or not, and there is several GB of temp space available.
I'm at a bit of a loss as to how to track down specifically what is causing this problem. I've looked at v$sesstat for all of the sessions involved and it hasn't really turned anything up. I've tried tracing the main session and that hasn't really turned up much either. From what I can tell, one of the sessions seems to try to allocate massive amounts of temp space that it just does not need, but I can figure out why.
Any ideas of how to approach finding the cause of the problem?
David

Hello
I've finally resolved this and the resolution was relatively simple - and was also the main thing that Mark Rittman said he did in his article: reduce the size of the hash join.
After querying v$sql_workarea_active I could see what was happening which was that the sum of the temp space for all of the parallel slaves was exceeding the total amount of temp space available on the system. When run in serial, it was virtually at the limit. I guess the extra was just the overhead for each slave maintaining it's own hash table.
I also made the mistake of misreading the exectuion plan - assuming that the data being pushed to the hash join was filtered to eliminate the data that was not of interest. Upon reflection, this was a rather stupid assumption on my part. Anyway, I used sub query factoring with the materialize hint to ensure that the hash join was only working on the data it should have been. This significantly reduced the size of the hash table and therefore the amount of temp space required.
I did speak to oracle support and they suggested using pga_aggregate_target rather than the separate *area_size parameters. I found that this had very little impact as the problem was related to the volume of data rather than whether it was being processed in memory or not. That said, I did try upping the hash_area_size for the session with some initial success, but ultimately it didn't prove to be scalable. We are however now using pga_aggregate_target in prod.
So that's that. Problem sorted. And as the title of Mark Rittman's article suggests, I was trying to be too clever! :-)
HTH
David

9i Query Execution (Parallel vs Serial)

I have a table (test) containing 1000000 (10 lac) records.
1) I issued the Query with parallel option "SELECT /*+ parallel (test,4) */count(*) FROM test". The query will use 4 parallel servers to execute.
2) After this i executed the Query without parallel option "SELECT /*+ parallel count(*) FROM test".
The execution time of both the queries is same. Why the parallel option is not executing the query will shorter time as compared to serial execution?
Thanks in Advance,
Shafiq

Hi,
To optimize parrallel query, the number of CPUs is very important. How have you CPU ? If not least 4 CPUs, it's not very recommend.
Have you make explain plan ?
explain plan for ....
and
@$ORACLE_HOME/rdbms/admin/utlxplp (for parallel query)
@$ORACLE_HOME/rdbms/admin/utlxpls (for serial quey)
Is your table partionned ?
Please post explain.
Btw, I don't think that for a count(*) parallel query improve performance...
Nicolas.

ORA-1555 with Parallel query problem

Hi
We are getting many ora-1555 errors with parallel query stuff. Few queries are throwing with hint /* Q98989129 NO_EXPAND INDEX or /* Q908231094 INDEX_RRS. Our applicaiton is like DSS kind with bulk loading and big reports. I have doubled the undo retention and undo size to 200G and set the trace event. But most of the queries are parallel queries. We are not using the following query in applicaiton. seems like it is parallel sub queries. I need to know the exact mechanism how to devide the parallel queries with its degree of parallalism.
SELECT /*+ Q277874009 INDEX_RRS(A1 "PK_TF_UTRAN_UCELL10_TAB") */ A1."TSTAMP" C0,A1."INSTANCE_ID" C1,A1."PMNOFOIRATHOM
ULTIGSMFAILURE" C2,A1."PMNOFOIRATHOCS57GSMFAIL" C3,A1."PMNOFOSPEECHGSMFAILURE" C
4,A1."PMNOFOHOSTANDGSMFAILURE" C5 FROM "FLEXPM"."ERC_TF_UTRAN_UCELL10_TAB" PX_G
RANULE(0, BLOCK_RANGE, DYNAMIC) A1 WHERE A1."TSTAMP"(+)<=TO_DATE('2006-09-25 23:
45:00', 'yyyy-mm-dd hh24:mi:ss')
Thanks

Hi,
probably the error is due to wrong execution plans choosen by the optimizer.
Are the table statistics up to date? Did You use parallel w/o and degree (ex. defining parallel on object using DEFAULT clause instead of a DEGREE)?
Normally, parallel execution can be done in 2 ways, considering the driving object:
1. like in previous versions, like 7.3, w/o partitioning, the object is split, by rowid, directly from the parallel coordinator to the query slaves (normally a number that can be equivalent to the degree of parallelism or the double in case of sort e/o joins).
2. considering a partitioned object, for every partition/subpartition (phisical segment), a query slaves is made in charge.
In both ways, the original session (SID) is the parallel coordinator that coordinates the salves executions.
The hints and statements that You've reported are tipical queries used by slave process.
In my experience, setting the PARALLEL degree to DEFAULT (no degree during CREATE or ALTER of the object after PARALLEL clause) will cause an "explosion" of slaves startup that can conduct to yr errors.
Hope this helps
Max

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

Oracle11g RAC with partitioning and cross instance parallel query problem

I have set up a 300gb TPC-H database using a 4 node RAC environment (8 cpu per node, 16 GB memory, 2 GHz processors) the system is served by 2.5 terabytes of SSD for its IO subsystem managed by a combination of ASM and OCFS2.
When I run a large parallel query (number 9 in the TPCH query set) I get:
ORA-00600: internal error code, arguments [kxfrGraDistNum3],[65535],[4]
with all other arguments blank. There were some reports of this in version 9, but it was supposedly fixed. Has any one seen this behavior or have a work around?
Mike

Good Idea! Why didn't I think of that? Oh yea...I did. Unfortunately TMS CSI is an update only partner type CSI so I cannot submit a SR. The 600 lookup was how I found the old stuff, but it didn't have any 11g references. I hoped maybe someone in the community had encountered this and had a workaround. By the way, the querey looks like so:
select
nation,
o_year,
sum(amount) as sum_profit
from
select
n_name as nation,
extract(year from o_orderdate) as o_year,
l_extendedprice * (1 - l_discount) - ps_supplycost * l_quantity as amount
from
h_part,
h_supplier,
h_lineitem,
h_partsupp,
h_order,
h_nation
where
s_suppkey = l_suppkey
and ps_suppkey = l_suppkey
and ps_partkey = l_partkey
and p_partkey = l_partkey
and o_orderkey = l_orderkey
and s_nationkey = n_nationkey
and p_name like '%spring%'
) as profit
group by
nation,
o_year
order by
nation,
o_year desc;
the other 21 queries, all using the same tables and degrees of paralell and cross instance settings, executed ok.
Mike

Parallel query hint with stored outlines

Hi,
Can I use parallel query hint with stored outlines.
Regards
MMU

I'm not quite sure what you're asking, since stored outlines themselves implement hints to try to maintain plan stability.
If you're asking if stored outlines will utililze the parallel query hints I'd have to assume "yes" but would test the idea anyway.
Message was edited by:
riedelme

Database stopped with Error:ORA-10388: parallel query server interrupt (fai

Hi Team,
My Oracle 10g Database stopped automatically. When i checked the alert log i found the below Errors:
Errors in file /opt/oracle/admin/DWS/bdump/dws_p000_10374.trc:
ORA-10388: parallel query server interrupt (failure)
Fri Mar 2 18:55:18 2012
SMON: Restarting fast_start parallel rollback
Fri Mar 2 18:55:47 2012
Thread 1 advanced to log sequence 384310 (LGWR switch)
Current log# 3 seq# 384310 mem# 0: +DBDG/dws/onlinelog/group_3.259.733426831
Fri Mar 2 18:57:48 2012
Errors in file /opt/oracle/admin/DWS/bdump/dws_p000_10374.trc:
ORA-10388: parallel query server interrupt (failure)
Fri Mar 2 18:57:49 2012
Errors in file /opt/oracle/admin/DWS/bdump/dws_smon_10337.trc:
ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], []
Fri Mar 2 19:18:31 2012
Errors in file /opt/oracle/admin/DWS/bdump/dws_pmon_10277.trc:
ORA-00474: SMON process terminated with error
Fri Mar 2 19:18:31 2012
PMON: terminating instance due to error 474
======================================================================
A week before we stopped oracle using "Shutdown abort" command. But two days before we stopped using "shutdown immediate", it went fine and system up and run fine.
But today it stopped with this error message.
Operating system : SOlaris 10
I changed the parameter parameter fast_start_parallel_rollback to HIGH from LOW, but no use
SQL> ALTER SYSTEM SET FAST_START_PARALLEL_ROLLBACK=HIGH SCOPE=BOTH;
System altered.
SQL> show parameter fast_start_parallel_rollback
NAME TYPE VALUE
fast_start_parallel_rollback string HIGH
Usually The dead transaction will be rolled back after raising the Priority from LOW to HIGH. But this time its not rolled back. still etting the same error.
Your answers will help to stop the oracle getting down in the LIVE production server. please share your experience guys.
Thanks and Regards,
Deeban

Hi,
Here im pasting the Trace file content for the error "ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], []".
[10:20pm] root@dws41: # cat /opt/oracle/admin/DWS/bdump/dws_pmon_10277.trc
/opt/oracle/admin/DWS/bdump/dws_pmon_10277.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /opt/oracle/product/10.2.0
System name: SunOS
Node name: dws41
Release: 5.10
Version: Generic_138888-06
Machine: sun4u
Instance name: DWS
Redo thread mounted by this instance: 1
Oracle process number: 3
Unix process pid: 10277, image: oracle@dws41 (PMON)
**** 2012-03-02 19:18:31.509*
**** SERVICE NAME:(SYS$BACKGROUND) 2012-03-02 19:18:31.504*
**** SESSION ID:(1511.1) 2012-03-02 19:18:31.504*
Background process SMON found dead
Oracle pid = 8
OS pid (from detached process) = 10337
OS pid (from process state) = 10337
dtp = 380017a10, proc = 7fd001048
Dump of memory from 0x0000000380017A10 to 0x0000000380017A58
380017A10 0000007C 00000000 00000007 FD001048 [...|...........H]
380017A20 00000000 00000000 00000000 534D4F4E [............SMON]
380017A30 00020000 00000000 00002861 00000000 [..........(a....]
380017A40 00000000 4F507D38 00000001 327FA838 [....OP}8....2..8]
380017A50 00040081 00000000 [........]
Dump of memory from 0x00000007FD001048 to 0x00000007FD001830
7FD001040 02010000 00000000 [........]
7FD001050 00000000 00000000 00000000 00000000 [................]
7FD001060 00000000 00000000 00000007 FD6D0CD0 [.............m..]
7FD001070 00000007 FD700328 00000007 FD546D78 [.....p.(.....Tmx]
7FD001080 00000005 3C6FD110 00000000 00000000 [....<o..........]
7FD001090 00000005 3C6FD198 00000005 3C6FD198 [....<o......<o..]
7FD0010A0 00000007 FD700318 01160800 00000000 [.....p..........]
7FD0010B0 00000007 FD53FF88 00000007 FD544698 [.....S.......TF.]
7FD0010C0 00000008 00000000 00000000 00000000 [................]
7FD0010D0 00000000 00000000 00000000 00000000 [................]
7FD0010E0 00000007 FD6CE770 00000007 FD6D0D00 [.....l.p.....m..]
7FD0010F0 00000000 00000000 00000000 00000000 [................]
Repeat 3 times
7FD001130 00000000 00000000 00000012 00000000 [................]
7FD001140 00000000 00000000 0000000F 00000000 [................]
7FD001150 00000000 00000000 00000012 00000000 [................]
Repeat 1 times
7FD001170 00000000 00000000 0000000F 00000000 [................]
Repeat 1 times
7FD001190 00000000 00000000 00000012 00000000 [................]
Repeat 1 times
7FD0011B0 00000000 00000000 0000000E 00000000 [................]
7FD0011C0 00000000 00000000 00000008 00000000 [................]
7FD0011D0 00000000 00000000 00000012 00000000 [................]
7FD0011E0 00000000 00000000 00000000 00000000 [................]
Repeat 2 times
7FD001210 00000000 00000000 00000004 00000000 [................]
7FD001220 00000000 00000000 00000000 00000000 [................]
7FD001230 4F50FF9A 00000000 00000000 00000000 [OP..............]
7FD001240 00000000 00000000 00000000 00000000 [................]
Repeat 1 times
7FD001260 00000007 FD001260 00000007 FD001260 [.......`.......`]
7FD001270 00000000 00000000 00000000 FFFFFFFF [................]
7FD001280 00000007 FD001280 00000007 FD001280 [................]
7FD001290 00000000 00000000 00000005 00000000 [................]
7FD0012A0 00000000 00000000 00000000 00000000 [................]
7FD0012B0 000000AB BABCDEFA 00000000 00000000 [................]
7FD0012C0 00000000 00000000 000000FF 7FFFC971 [...............q]
7FD0012D0 00000021 00000026 0008CBAA 00039976 [...!...&.......v]
7FD0012E0 00000005 3C003FB8 00000006 7E0037D0 [....<.?.....~.7.]
7FD0012F0 00000001 00000000 00000000 00000000 [................]
7FD001300 00000000 00000000 00000000 00000000 [................]
Repeat 1 times
7FD001320 00000000 00000000 00002861 00000000 [..........(a....]
7FD001330 00000000 00000000 00000000 00000000 [................]
Repeat 2 times
7FD001360 00000000 00000000 00000007 FD001048 [...............H]
7FD001370 00000000 00000000 00000000 00000000 [................]
Repeat 4 times
7FD0013C0 00000000 00000000 00000001 00000000 [................]
7FD0013D0 00000000 00000000 00000000 00000000 [................]
Repeat 1 times
7FD0013F0 4F50FF9A 00000000 00000007 FD0013F8 [OP..............]
7FD001400 00000007 FD0013F8 00000000 00000000 [................]
7FD001410 00010000 00000000 00000000 01000057 [...............W]
7FD001420 0000000C 00000000 00002861 00000000 [..........(a....]
7FD001430 00000000 4F507D38 00000001 00000000 [....OP}8........]
7FD001440 00000000 00000000 00000000 00000000 [................]
Repeat 3 times
7FD001480 0000000F FFFFFFFF 00000000 00000000 [................]
7FD001490 00000000 00000000 00000000 00000000 [................]
Repeat 2 times
7FD0014C0 00000000 00000000 00000020 00000000 [........... ....]
7FD0014D0 00000000 00000000 00000000 00000000 [................]
Repeat 8 times
7FD001560 00000000 00000000 6F726163 6C650000 [........oracle..]
7FD001570 00000000 00000000 00000000 00000000 [................]
7FD001580 00000000 00000000 00000000 00000006 [................]
7FD001590 64777334 31000000 00000000 00000000 [dws41...........]
7FD0015A0 00000000 00000000 00000000 00000000 [................]
Repeat 2 times
7FD0015D0 00000000 00000005 554E4B4E 4F574E00 [........UNKNOWN.]
7FD0015E0 00000000 00000000 00000000 00000000 [................]
7FD0015F0 00000000 00000000 00000000 00000008 [................]
7FD001600 31303333 37000000 00000000 00000000 [10337...........]
7FD001610 00000000 00000000 00000000 00000005 [................]
7FD001620 6F726163 6C654064 77733431 2028534D [oracle@dws41 (SM]
7FD001630 4F4E2900 00000000 00000000 00000000 [ON).............]
7FD001640 00000000 00000000 00000000 00000000 [................]
7FD001650 00000000 00000013 00000000 00000002 [................]
7FD001660 00000000 00000000 00000000 00000000 [................]
Repeat 9 times
7FD001700 00000000 00020000 00000000 00000000 [................]
7FD001710 00000000 00000000 00000000 00000000 [................]
7FD001720 00000003 BD4FFA28 00000005 3C0026F8 [.....O.(....<.&.]
7FD001730 00000006 7E000F40 00000000 00000000 [....~..@........]
7FD001740 00000003 BC691FD8 00000000 00000000 [.....i..........]
7FD001750 00000000 00000000 00000000 00000000 [................]
7FD001760 00000000 00000000 00000007 FD001768 [...............h]
7FD001770 00000007 FD001768 00000000 09EF0000 [.......h........]
7FD001780 00000000 086F0000 00000000 017A17D9 [.....o.......z..]
7FD001790 00000000 00273A49 00000000 13B817D9 [.....':I........]
7FD0017A0 00000000 00015030 00000000 0000A848 [......P0.......H]
7FD0017B0 00000000 001350A0 00000000 00000828 [......P........(]
7FD0017C0 00000000 000000E0 00000000 00000828 [...............(]
7FD0017D0 00000000 00000000 00000000 00000000 [................]
Repeat 4 times
7FD001820 32B310E7 000152FB 00000003 00000000 [2.....R.........]
error 474 detected in background process
ORA-00474: SMON process terminated with error
[10:20pm] root@dws41: #

How Can I reduce Query Execution time with use of filter

Dear Experts,
In a query execution is faster when there is no product filter and these products can be a list contaning mare than 300 items.
I am using In operator for that filter.

Maybe if you posted the quer[y][ies] we could get a better idea.

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

Oracle 10g and parallel query question

Hi Oracle on SAP Gurus!
We are currently thinking of activating parallel query for certain segments (large application tables and indexes). We searched in SAPNet and SDN and have also studied the SAP Note 651060. But we did not find a complete answer to the following question which is very important for us:
Which kinds of queries (despite from full table scan and index scan in partitioned indexes) support parallel queries and which ones do not support parallel queries?
This is important for us to find out whether we have candidates for parallel queries or not.
Thanx for any hint!
Regards,
Volker

But why do you not propose to use parallel query in OLTP systems?
If the queries are accessed very frequently you will just run out of cpu and io ressources. OLTP systems are (historical) typically multi user systems. You can off course use PQ for 'single user' activities, like index rebuilds, some batchjobs, but you shouldn't do for frequent user queries.
If you have time look at this interesting Article [Suck It Dry - Tuning Parallel Execution|http://doug.burns.tripod.com/px.html]
It is quite old, and you don't have to read all tech details, but i recommend having a look at the conclusions at the end.
May it make sense to use partitioning of these tables in conjunction with parallel query?
I know some guys, who do partitioning on OLTP systems, even SAP systems. But they don't use PQ then. The use partitioning to work on a smaller set of data. In your case the range scans, would need to scan only one partition, saving buffer cache and effectively speeding up execution. So you don't need PQ to scan all partitions at all, this would be a typical OLAP approach.
Best regards
Michael

Parallel query in Oracle 11g

We use Oracle 11g DB on windows2008R2.
We wrote very long and heavy SELECT SQL query usign several table join and sub-queries and it take very long time to get result.
We did SQL statement tuning as much as we can do so far. ( I will get the Execution Plan and ADDM, etc access right)
I today notice about Parallel query function.
Where could I write parallel hint phrases in very long SELECT SQL query ?
In each selected tables like below ?
/sample in Oracle Doc/
SELECT /*+ PARALLEL(employees 4) PARALLEL(departments 4)
USE_HASH(employees) ORDERED */ MAX(salary), AVG(salary)
FROM employees, departments
WHERE employees.department_id = departments.department_id
GROUP BY employees.department_id;

You need to be careful with some of the examples in the docs. The example you quote includes an unnecessary join. Before considering parallel query, it should have been re-written to this:
SELECT MAX(salary), AVG(salary)
FROM employees
WHERE department_id is not null
GROUP BYdepartment_id;
Later versions of the CBO may do this re-write for you, but it is important to understand why the SQL is inefficient before throwing parallel servers at it. Are you sure that all your joins are actually necessary? (I know you are just going to say "yes", but you might want to think about it first.)

Parallel query execution on Multiprovider with noncumulative KF

Similar Messages

Maybe you are looking for