Oracle Parallel query

Hi,
I want to know what happens if we dont specify degree of parallelism in the parallel hint? It caused issues in our production database when patch upgraded from 9.2.0.5.0 to 9.2.0.7.0. there is one parallel hint on the table without DOP which worked before patch upgrade and did not work after patch upgrade. when i give definite parallelism it worked fine.
Any suggestions on this?
Thanks
Venkat.

The rest of the page from the link you gave explains how the execution worksYeah, it does .. but there is nowhere defined what a "separate process" means... means it a new shadow process (as a child of the coordinator) or only threads?
In the Data Warehousing Guide... it seems like both... look here...
-- >"The query coordinator does the following:
--> "Allocates one or two set of slaves (threads or processes)"
hmmm but what now? a new shadow process or an additional thread by the coordinator...
I hope you know, what my question is ;-)
Regards
Stefan

Similar Messages

  • 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.)

  • ORACLE V7.1 PARALLEL QUERY OPTION(PQO) TEST

    제품 : ORACLE SERVER
    작성날짜 : 2004-08-13
    SCOPE
    8~10g Standard Edition 에서는 지원하지 않습니다.
    Subject: Oracle V7.1 PQO 테스트 결과
    1.테스트 장비 : Sequent2000-S750
    512MB M/M, 16GB H/D, 20 CPUs
    2.테스트 S/W : Oracle V7.1.1 Beta (Parallel Query Option)
    3.DB file구성 : 10개의 hard disk를 strapping raw device로 구성
    data tablespace : 1.9 GB
    4.Data Load : 2개의 테이블 사용(5KB , 1MB)
    5.테스트 결과.
    - Sort Merge Join (Default SQL: using 1 CPU) : 6m21s - 6m33s
    * Sort Merge Join (Parallel 20 option: using 20 CPU) : 0m59s
    * Parallel index create (1Mega table) : 1m18s - 1m28s
    - Nested Loop Join (Default SQL: using 1 CPU) : 1m15s - 1m23s
    * Nested Loop Join (Parallel 20 option: using 20 CPU) : 0m02s - 0m03s
    - Execute PL/SQL procedure (Default SQL: using 1 CPU) : 1m54s
    (embeded compiled PL/SQL procedure : user define function)
    * Execute PL/SQL procedure (Parallel option : 20 CPU) : 0m13s
    (embeded compiled PL/SQL procedure : user define function)
    결과적으로 SQL문의 종류에 따라 7배 - 40배 정도의 성능 향상을 보여줌.
    6. 본사에서 recommand한 자료에 의하면 18배 이상의 성능 향상 을 얘기하는데
    이결과는 테스트 장비 구성의 차이라고 할 수 있습니다.
    본사 테스트 장비 : Sequent5000 model, 1GB M/M, Pentium CPU, 20 H/Ds
    cab로서 장비 구성요소 만으로도 2.5배 이상의 성능의 효과가 기대되는 상황.

    Can you try running the following query and see if parallelism is used. I have used table alias "a" and included that in the parallel hint
    select /*+ parallel(a, 8) */
    colA,
    colB
    from abc.mytable a
    where my_date between to_date('01/01/2011','mm/dd/yyyy') and to_date('12/31/2011','mm/dd/yyyy') AND
    CD = '35';
    Thanks

  • Oracle error-parallel query

    Hi Experts,
    While i'm running a parallel query through a procedure...
    its throwing the below error.....
    when others Error ORA-12801: error signaled in parallel query server P006
    ORA-01114: IO error writing block to file  (block # )
    ORA-01114: IO error writing block to file 1025 (block # 2790848)
    ORA-27063: number of byte with query
    Can you people suggest me?
    Thanks in advance!!!

    You probably meant 11.2.0.3 instead of 11.2.3.0?
    Did you (or your DBA) check the alert log?
    What happens if you remove your WHEN OTHERS and rerun the code?
    Do you get any additional information?

  • 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

  • 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.

  • Error on Parallel Query

    Hi,
    My application throws the following error when Iam processing a parallel query on my database. Can any one help me to resolve this.
    ERROR at line 1:
    ORA-29903: error in executing ODCIIndexFetch() routine
    ORA-20000: Oracle Text error:
    DRG-50857: oracle error in drekrgm (one piece lob read)
    ORA-01555: snapshot too old: rollback segment number with name "" too small
    ORA-22924: snapshot too old
    Regards
    Venkat

    HI,
    Thanks for the article. I read the article but my problem is getting addressed. I have enough disk space and rollback segments.
    7 rollback segments (1 default 200 MB + 6 created for my executing wtih 1GB each ). All of them are auto extended 10M per block.
    Apart from this I have a free space for 25 GB in the drive left out. Inspite of all of these. I am getting this error.
    I am not able to understand the "DreKrgm" part.
    Can you throw some light on this part.

  • Problem in running parallel query

    Hi All,
    We have an Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 installed on Microsoft Windows 2000 Advanced Server 5.0.2195 Service Pack 4 Build 2195.
    And we have a stored procedure which does lots of works.
    In this procedure, there is a select statement which joins a huge table with milions of records(lets call it table X) to some other almost huge tables. This table X
    is partitioned and parallel processing has been enabled on it. Every thing has been fine until a week ago. From then on, we are getting the following error in that procedure:
    ORA-12801: error signaled in parallel query server P014
    ORA-04030: out of process memory when trying to allocate 4194328 bytes (QERHJ hash-joi,QERHJ list array)
    We have made some changes in that select statement which are very common changes like adding some additional where clauses and selecting some additional columns. The From List of select statement has not been changed.
    I don't exactly know what is realy going on.
    The available memory is about 2 GB when the mentioned procedure crashes.
    Any Idea?
    My Best,
    Alireza Vali

    Is it a 32bit installation (32bit Windows, 32bit Oracle) ?
    What are your MEMORY_TARGET, SGA_TARGET, SGA_MAX_SIZE and PGA_AGGREGATE_TARGET parameters set to ? (If you have MEMORY_TARGET set, it is not necessary that the other parameters be set).
    ORA-4030 relates to PGA memory, not SGA memory. But Oracle on Windows is a single, multi-threaded process. Therefore, all Oracle "processes" (threads in the Windows process) share the same memory (address) space, even the SGA and PGA.
    Hemant K Chitale

  • 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

  • Killing Parallel Query Session

    Hi,
    I am running Oracle 11.2.0.1.0 on Solaris 5.10.
    Couple of hours ago, I ran a job through DBMS_JOB (Yes, I need to use dbms_schedular), and in the job I used parallel query. Now I want to remove the job. Also I want to clean up the sessions. I can remove the job by doing DBMS_JOB.remove(job id). Is there a way that I kill one parallel query coordinator session, and it would automatically kill all the slave sessions?
    Thanks and regards
    Edited by: Fahd Mirza on Apr 22, 2010 11:57 AM

    Thanks for the answer.
    I have run the following query with output:
    SQL> select ps.sid,s.username,ps.qcsid
    from v$session s, v$px_session ps
    where s.sid=ps.sid
    and s.username='BIADM';  2    3    4
           SID USERNAME                            QCSID
            91 BIADM                                 147
           267 BIADM                                 147
           290 BIADM                                 147
           332 BIADM                                 147
           345 BIADM                                 147
            69 BIADM                                 147
            92 BIADM                                 147
           102 BIADM                                 147
           222 BIADM                                 147
           112 BIADM                                 147
            73 BIADM                                 147
           126 BIADM                                 147
           136 BIADM                                 147
           145 BIADM                                 147
           170 BIADM                                 147
           180 BIADM                                 147
           276 BIADM                                 147
           190 BIADM                                 147
           221 BIADM                                 147
           234 BIADM                                 147
           214 BIADM                                 147
           246 BIADM                                 147
           270 BIADM                                 147
           256 BIADM                                 147
           278 BIADM                                 147
           291 BIADM                                 147
           309 BIADM                                 147
           298 BIADM                                 147
           323 BIADM                                 147
           344 BIADM                                 147
             2 BIADM                                 147
           331 BIADM                                 147
           134 BIADM                                  94
           125 BIADM                                  94
           156 BIADM                                  94
           168 BIADM                                  94
           181 BIADM                                  94
           205 BIADM                                  94
           191 BIADM                                  94
           215 BIADM                                  94
           232 BIADM                                  94
           245 BIADM                                  94
           255 BIADM                                  94
           269 BIADM                                  94
           292 BIADM                                  94
           302 BIADM                                  94
           280 BIADM                                  94
           311 BIADM                                  94
           147 BIADM                                 147
            94 BIADM                                  94
    50 rows selected.If I kill sessions with sid 147 and 94, shouldn'it it be killing all the sessions of BIADM?
    REGARDS

  • 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
    <b>SQL Error: ORA-12801: error signaled in parallel query server P007.</b>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.
    <b>Reason and Prerequisites</b>
    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.
    <b> Note 963760 - 'ORA-20000: Insufficient privileges' for creating statistics</b> 
    For Error -for SQL Error: ORA-01418: specified index does not exist
    check note below-
    <b>Note 337830 - BW: ORA-1418 in system log</b>
    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.
    <b>
    Note 1003360 - BW fact tables: Deleting index from process chain terminates</b>
    If it relates your error it requires corrections for SP-12.
    Hope it Helps
    Chetan
    @CP..

  • Error in Parallel query server

    Please help!
    SELECT SUM(DECODE(r.sexe,�M�,1,0)) H, SUM(DECODE(r.sexe,�F�,1,0))F, FLOOR(MONTHS_BETWEEN(TO_DATE(:p_date),r.date_naissance)/12) age
    FROM resource r
    GROUP BY FLOOR(MONTHS_BETWEEN(TO_DATE(:p_date), r.date_naissance)/12)
    This �select� worked on Oracle 7 but gives the following error messages on Oracle 8i:
    ORA-1281: Error signaled in parallel query server P_004.
    ORA-00979: Not a group by expression.
    Thanks.

    user10699277 wrote:
    I got the following error while import data.You are doing import with datapump or imp ?
    If so, look at the import log where ORA-01452 is mentioned, you should find the name of the table there for which ORA-01452 is raised.
    Hi All,
    ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys foundYou are trying to create unique index on the column where duplicate values exists.
    By the definition of unique index, that would be impossibe.
    So, either remove 'unique' from the create index syntax , or make sure there are no duplicate values in the coulumn on which you are creating unique index.
    Could you resolve it?No, that should be your responsibility.

  • 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.

Maybe you are looking for