Parallel query Server BI (with DOP > 1)?

Hi guys,.

I have some performance problems with certain reports. These reports are very siple, no aggregation, no action... a few columns from different dimensions.
The problem is that the size of her varied dimensions of 1 million 10 million records and some dimensions are linked by relationships "outer join". The physical motion generated by the BI server takes about 22 minutes, but if I change the same query by adding the paralellism for the tables involved (for example select / * + PARALLEL (mytable 4) * /...) I get the result in 5 minutes (1/4 of the time).

So is it possible to force the BI server to use a degree (DOP) > 1 for all/some physical tables?

What about using index (I have not create any index again, maybe I should start to use for the primary/foreign keys)?

Of course, other solutions for this problem are appretiated! :-)

Thanks in advance,
Nazza

Nazza,

Have you tried the HINT function (physical Table-> > general tab-->> HINT) available in the physical layer. You can use parallel index it and the generated query would use the same throughout, shooting it to the database.
Indexex are good to have but to check with your DBA, what rating would be more profitable to your query.

See you soon
Blackburn

Tags: Business Intelligence

Similar Questions

  • When you encounter ORA-12805: parallel query server died suddenly

    What is the best practical appproach for dealiing with ORA-12805: parallel query server died suddenly? 
    $ oerr ora 12805
12805, 00000, "parallel query server died unexpectedly"
// *Cause: A parallel query server died unexpectedly, PMON cleaning
//         up the process.
// *Action: Check your system for anomalies and reissue the statement.
//          If this error persists, contact Oracle Support Services.
//          See trace file for more details.

  • ORA-12801: error reported in the P004 parallel query server

    Hi all

    I am using Oracle 10 g on Linux and I get the error msg below
      [sqlplus] ORA-12801: error signaled in parallel query server P004
  [sqlplus] ORA-01114: IO error writing block to file 201 (block # 612165)
  [sqlplus] ORA-27072: File I/O error
  [sqlplus] Linux-x86_64 Error: 11: Resource temporarily unavailable
  [sqlplus] Additional information: 4
  [sqlplus] Additional information: 612165
  [sqlplus] Additional information: 69632
  [sqlplus] ORA-01114: IO error writing block to file 201 (block # 612165)
  [sqlplus] ORA-27072: File I/O error
  [sqlplus] Linux-x86_64 Error: 11: Resource temporarily unavailable
  [sqlplus] Additional information: 4
  [sqlplus] Additional information: 612165
  [sqlplus] Additional information: 69632
    Pls someone put light on this.

    Thanks in advance
    SAZ

    Dear Saaz Ena,

    I don't think that is related with the TEMP tablespace but you can run under query to discover their space;

    SELECT NAME, TS#, BYTES/1024/1024 "Size in GB"
FROM V$TEMPFILE
ORDER BY 3 DESC;

    Hope that helps.

    Ogan

  • ORA-12801: error reported in the parallel query P002 Server

    Hello

    I get the below error
    ORA-12801: error signaled in parallel query server P002
ORA-01722: invalid number

INSERT INTO TMP
                ( TABLE_NAME, COLUMN_NAME, ATTR,     
                    ATTRIBUTE, ATTRIBUTE_TYPE, ATTR_DESCRIPTION  ,     
                    CODE_NAME, CODE_DESCRIPTION,  LANGUAGE_CODE  )
SELECT 'BLDG', 'FEATURE_TYPE', NULL, NDV.PBL_VLS,
                'C', NDV.LONG_NAME,  ND.DOM_NM, ND.LONG_NAME,
                'ENG'
FROM DOM_VUL NDV, DOM ND
WHERE ND.DOM_NM = 'FEATURE'
AND NDV.VALUE >= 2005000 AND NDV.VALUE <=2005999 
AND ND.DOM_IDS = NDV.DOM_IDS;
    When I comment on AND NDV. VALUE > = 2005000 AND NDV. VALUE < = 2005999 it works

    Published by: Saaz Ena on March 11, 2010 21:11

    Hello

    It looks like NDV. VALUE contains values that is not a number, so you get this error.

    Concerning

  • Please help with parallel query

    Hi all

    I am "playing" with a parallel query and try to see if it could improve some more long running queries, but can't do the database that you want to use a parallel execution plan, no matter what I do! I hope someone can point me in the right direction!

    ORACLE Version is 11.2.0.2
    OS Win 2008 R2 server
    UC = 32
    64 GB OF RAM
    AMM enabled, memory_target = M 50560
    SQL > show the parallel parameter

    VALUE OF TYPE NAME
    ------------------------------------ ----------- --------------
    fast_start_parallel_rollback string LOW
    parallel_adaptive_multi_user Boolean TRUE
    parallel_automatic_tuning boolean FALSE
    parallel_degree_limit string CPU
    parallel_degree_policy string AUTO
    parallel_execution_message_size integer 16384
    parallel_force_local boolean FALSE
    parallel_instance_group string
    parallel_io_cap_enabled boolean FALSE
    PARALLEL_MAX_SERVERS integer 985
    parallel_min_percent integer 0

    VALUE OF TYPE NAME
    ------------------------------------ ----------- --------------
    parallel_min_servers integer 16
    parallel_min_time_threshold channel 5
    parallel_server boolean FALSE
    parallel_server_instances integer 1
    parallel_servers_target integer 512
    parallel_threads_per_cpu integer 2
    recovery_parallelism integer 0
    I also ran the calibration of IO which resultet
    Max e/s per second 21569
    Max Mo / second 989
    I collected statistics of the system, the 1 hour time. the results are:
    Select pname, sys.aux_stats pval1 $;
    STATUS
    DSTART
    DSTOP
    FLAGS 0
    CPUSPEEDNW 915
    IOSEEKTIM 10
    IOTFRSPEED 4096
    SREADTIM 0.589
    MREADTIM 0.841
    CPUSPEED 1355
    MBRC 11
    MAXTHR 679936
    SLAVETHR
    I changed all my tables and indexes using 'ALTER TABLE xxx PARALLEL' then when I query the dba_tables, the DEGREE is DEFAULT for all objects invoked in my queries.

    what I've learned so far, I put all the necessary parameters.
    From my understanding, all queries who believe more than 5 seconds, should be tried to run in parallel (parallel_min_time_threshold = 5). But not a single query is doing at least this forced manually with a / * + PARALLEL * / tip! It drives me crazy. Choose manually a degree of 16 for example allows to speed up some queries from 15 minutes to 1 minute, but why ORACLE does not by itself?
    Given that it is a Siebel application, that we are talking about, there is no possibility of adding tips for SQL.

    example:

    This query took 29 seconds to complete, but was executed in SERIES
    SQL_ID, atzj0dmhshb23, number of children 0
    -------------------------------------
    SELECT T7. CONFLICT_ID, T7. LAST_UPD, T7. CREATED,
    T7. LAST_UPD_BY, T7. CREATED_BY, T7. MODIFICATION_NUM,
    T7. ROW_ID, T9. MAIN_PH_NUM, T9.NAME, T9. REGION,
    T9. X_SUB_REGION, T20. ATTRIB_44, T20. ATTRIB_26,
    T20. ATTRIB_45, T20. ATTRIB_27, T20. ATTRIB_03,
    T33. SUPPRESS_MAIL_FLG, T33. EMAIL_ADDR, T33. MID_NAME,
    T33. PR_DEPT_OU_ID, T33. LAST_NAME, T33. SEX_MF,
    T33. PR_PER_ADDR_ID, T33. PR_POSTN_ID, T30. PR_ADDR_ID,
    T33. HOME_PH_NUM, T33. OWNER_PER_ID, T33. WORK_PH_NUM,
    T33. FAX_PH_NUM, T33. FST_NAME, T20. ATTRIB_07,
    T3. INTEGRATION_ID, T33. PR_PER_PAY_PRFL_ID, T33. PRIV_FLG,
    T33. PR_MKT_SEG_ID, T33. PR_REP_SYS_FLG,
    T33. PR_REP_MANL_FLG, T33. PR_REP_DNRM_FLG, T33. PR_OPTY_ID,
    T33. PR_GRP_OU_ID, T33. EMP_FLG, T8. OWN_INST_ID,
    T8. INTEGRATION_ID, T33. PERSON_UID, T7. NAM

    Hash value of plan: 35208051

    ---------------------------------------------------------------------------------------------------------------------------------
    | ID | Operation | Name | Lines | Bytes | Cost (% CPU). Time |
    ---------------------------------------------------------------------------------------------------------------------------------
    | 0 | SELECT STATEMENT | 34 (100) |
    | 1. NESTED EXTERNAL LOOPS | 10. 42440 | 34 (0) | 00:00:01 |
    | 2. NESTED EXTERNAL LOOPS | 10. 42300 | 33 (0) | 00:00:01 |
    | 3. NESTED EXTERNAL LOOPS | 10. 42160 | 32 (0) | 00:00:01 |
    | 4. NESTED EXTERNAL LOOPS | 10. 42020 | 31 (0) | 00:00:01 |
    | 5. NESTED LOOPS | 10. 41880 | 30 (0) | 00:00:01 |
    | 6. NESTED EXTERNAL LOOPS | 11. 45947 | 29 (0) | 00:00:01 |

    | 7. NESTED LOOPS | 11. 45716 | 28 (0) | 00:00:01 |
    | 8. NESTED EXTERNAL LOOPS | 11. 45364 | 27 (0) | 00:00:01 |
    | 9. NESTED EXTERNAL LOOPS | 11. 45243 | 26 (0) | 00:00:01 |
    | 10. NESTED EXTERNAL LOOPS | 11. 45122 | 25 (0) | 00:00:01 |
    | 11. NESTED EXTERNAL LOOPS | 11. 43648 | 24 (0) | 00:00:01 |
    | 12. NESTED EXTERNAL LOOPS | 11. 37070 | 23 (0) | 00:00:01 |
    | 13. NESTED EXTERNAL LOOPS | 11. 34661 | 22 (0) | 00:00:01 |
    | 14. NESTED EXTERNAL LOOPS | 11. 34430 | 21 (0) | 00:00:01 |
    | 15. NESTED EXTERNAL LOOPS | 11. 33891 | 20 (0) | 00:00:01 |
    | 16. NESTED EXTERNAL LOOPS | 11. 33253 | 19 (0) | 00:00:01 |
    | 17. NESTED EXTERNAL LOOPS | 11. 32362 | 18 (0) | 00:00:01 |
    | 18. NESTED EXTERNAL LOOPS | 11. 31999 | 17 (0) | 00:00:01 |
    | 19. NESTED EXTERNAL LOOPS | 11. 29337 | 16 (0) | 00:00:01 |
    | 20. NESTED EXTERNAL LOOPS | 11. 28556 | 15 (0) | 00:00:01 |
    | 21. NESTED EXTERNAL LOOPS | 11. 28061 | 14 (0) | 00:00:01 |
    | 22. NESTED EXTERNAL LOOPS | 11. 26400 | 13 (0) | 00:00:01 |
    | 23. NESTED EXTERNAL LOOPS | 11. 26169 | 12 (0) | 00:00:01 |
    | 24. NESTED EXTERNAL LOOPS | 11. 25465 | 10 (0) | 00:00:01 |
    | 25. NESTED EXTERNAL LOOPS | 11. 21131. 9 (0) | 00:00:01 |
    | 26. NESTED EXTERNAL LOOPS | 11. 18326. 8 (0) | 00:00:01 |
    | 27. NESTED LOOPS | 11. 13651 | 7 (0) | 00:00:01 |
    | 28. NESTED EXTERNAL LOOPS | 11. 12452. 6 (0). 00:00:01 |
    | 29. NESTED EXTERNAL LOOPS | 11. 10978. 5 (0) | 00:00:01 |
    | 30. NESTED LOOPS | 11. 9504. 4 (0) | 00:00:01 |
    | 31. NESTED EXTERNAL LOOPS | 4. 360 | 3 (0) | 00:00:01 |
    | 32. NESTED LOOPS | 4. 228. 2 (0) | 00:00:01 |
    | * 33 | INDEX UNIQUE SCAN | S_PARTY_P1 | 1. 11. 1 (0) | 00:00:01 |
    | 34. TABLE ACCESS BY INDEX ROWID | S_CONTACT_BU | 4. 184. 1 (0) | 00:00:01 |
    | * 35 | INDEX RANGE SCAN | S_CONTACT_BU_M1 | 4 | | 1 (0) | 00:00:01 |
    | 36. TABLE ACCESS BY INDEX ROWID | S_ORG_EXT | 1. 33. 1 (0) | 00:00:01 |
    | * 37 | INDEX UNIQUE SCAN | S_ORG_EXT_U3 | 1 | | 1 (0) | 00:00:01 |
    | * 38 | TABLE ACCESS BY INDEX ROWID | S_CONTACT. 3. 2322 | 1 (0) | 00:00:01 |
    | * 39 | INDEX UNIQUE SCAN | S_CONTACT_P1 | 1 | | 1 (0) | 00:00:01 |
    | 40. TABLE ACCESS BY INDEX ROWID | S_MED_SPEC | 1. 134. 1 (0) | 00:00:01 |
    | * 41. INDEX UNIQUE SCAN | S_MED_SPEC_P1 | 1 | | 1 (0) | 00:00:01 |
    | 42. TABLE ACCESS BY INDEX ROWID | S_PRI_LST | 1. 134. 1 (0) | 00:00:01 |
    | * 43. INDEX UNIQUE SCAN | S_PRI_LST_P1 | 1 | | 1 (0) | 00:00:01 |
    | * 44 | TABLE ACCESS BY INDEX ROWID | S_PARTY | 1. 109. 1 (0) | 00:00:01 |
    | * 45 | INDEX UNIQUE SCAN | S_PARTY_P1 | 1 | | 1 (0) | 00:00:01 |
    | 46. TABLE ACCESS BY INDEX ROWID | S_CONTACT_SS | 1. 425. 1 (0) | 00:00:01 |
    | * 47 | INDEX RANGE SCAN | S_CONTACT_SS_U1 | 1 | | 1 (0) | 00:00:01 |
    | 48. TABLE ACCESS BY INDEX ROWID | S_CONTACT_LOYX | 1. 255. 1 (0) | 00:00:01 |
    | * 49 | INDEX RANGE SCAN | S_CONTACT_LOYX_U1 | 1 | | 1 (0) | 00:00:01 |
    | * 50 | INDEX RANGE SCAN | S_DQ_CON_KEY_U1 | 1. 394. 1 (0) | 00:00:01 |
    | * 51 | TABLE ACCESS FULL | S_CASE | 1. 64. 0 (0) |
    | 52. TABLE ACCESS BY INDEX ROWID | S_POSTN | 1. 21. 1 (0) | 00:00:01 |
    | * 53 | INDEX UNIQUE SCAN | S_POSTN_U2 | 1 | | 1 (0) | 00:00:01 |
    | 54. TABLE ACCESS BY INDEX ROWID | S_EMP_PER | 1. 151. 1 (0) | 00:00:01 |
    | * 55 | INDEX UNIQUE SCAN | S_EMP_PER_U1 | 1 | | 1 (0) | 00:00:01 |
    | 56. TABLE ACCESS BY INDEX ROWID | S_POSTN_CON | 1. 45. 1 (0) | 00:00:01 |
    | * 57 | INDEX RANGE SCAN | S_POSTN_CON_M3 | 4 | | 1 (0) | 00:00:01 |
    | 58. TABLE ACCESS BY INDEX ROWID | S_ORG_EXT_FNX | 1. 71. 1 (0) | 00:00:01 |
    | * 59 | INDEX RANGE SCAN | S_ORG_EXT_FNX_U1 | 1 | | 1 (0) | 00:00:01 |
    | 60. TABLE ACCESS BY INDEX ROWID | S_ORG_EXT_X | 1. 242. 1 (0) | 00:00:01 |
    | * 61. INDEX RANGE SCAN | S_ORG_EXT_X_U1 | 1 | | 1 (0) | 00:00:01 |
    | 62. TABLE ACCESS BY INDEX ROWID | S_CON_ADDR | 1. 33. 1 (0) | 00:00:01 |
    | * 63. INDEX RANGE SCAN | S_CON_ADDR_M51 | 1 | | 1 (0) | 00:00:01 |
    | 64. TABLE ACCESS BY INDEX ROWID | S_ADDR_PER | 1. 51 M | 1 (0) | 00:00:01 |
    | * 65 | INDEX UNIQUE SCAN | S_ADDR_PER_P1 | 1 | | 1 (0) | 00:00:01 |
    | 66. TABLE ACCESS BY INDEX ROWID | S_ADDR_PER | 1. 58. 1 (0) | 00:00:01 |
    | * 67. INDEX UNIQUE SCAN | S_ADDR_PER_P1 | 1 | | 1 (0) | 00:00:01 |
    | 68. TABLE ACCESS BY INDEX ROWID | S_ORG_EXT | 1. 49. 1 (0) | 00:00:01 |
    | * 69 | INDEX UNIQUE SCAN | S_ORG_EXT_U3 | 1 | | 1 (0) | 00:00:01 |
    | 70. TABLE ACCESS BY INDEX ROWID | S_POSTN | 1. 21. 1 (0) | 00:00:01 |
    | * 71 | INDEX UNIQUE SCAN | S_POSTN_U2 | 1 | | 1 (0) | 00:00:01 |
    | 72. TABLE ACCESS BY INDEX ROWID | S_ORG_EXT | 1. 219. 1 (0) | 00:00:01 |
    | * 73 | INDEX UNIQUE SCAN | S_ORG_EXT_U3 | 1 | | 1 (0) | 00:00:01 |
    | 74. TABLE ACCESS BY INDEX ROWID | S_ORG_EXT | 1. 598. 1 (0) | 00:00:01 |
    | * 75 | INDEX UNIQUE SCAN | S_ORG_EXT_U3 | 1 | | 1 (0) | 00:00:01 |
    | 76. TABLE ACCESS BY INDEX ROWID | S_CONTACT_X | 1. 134. 1 (0) | 00:00:01 |
    | * 77 | INDEX RANGE SCAN | S_CONTACT_X_U1 | 1 | | 1 (0) | 00:00:01 |
    | * 78 | INDEX UNIQUE SCAN | S_PARTY_P1 | 1. 11. 1 (0) | 00:00:01 |
    | * 79 | INDEX UNIQUE SCAN | S_PARTY_P1 | 1. 11. 1 (0) | 00:00:01 |
    | 50 M | TABLE ACCESS BY INDEX ROWID | S_POSTN_CON | 1. 32. 1 (0) | 00:00:01 |
    | * 81 | INDEX RANGE SCAN | S_POSTN_CON_M3 | 1 | | 1 (0) | 00:00:01 |
    | 82. TABLE ACCESS BY INDEX ROWID | S_POSTN | 1. 21. 1 (0) | 00:00:01 |
    | * 83 | INDEX UNIQUE SCAN | S_POSTN_U2 | 1 | | 1 (0) | 00:00:01 |
    | * 84 | INDEX UNIQUE SCAN | S_PARTY_P1 | 1. 11. 1 (0) | 00:00:01 |
    | 85. TABLE ACCESS BY INDEX ROWID | S_USER | 1. 14. 1 (0) | 00:00:01 |
    | * 86 | INDEX UNIQUE SCAN | S_USER_U2 | 1 | | 1 (0) | 00:00:01 |
    | 87. TABLE ACCESS BY INDEX ROWID | S_USER | 1. 14. 1 (0) | 00:00:01 |
    | * 88. INDEX UNIQUE SCAN | S_USER_U2 | 1 | | 1 (0) | 00:00:01 |
    | 89. TABLE ACCESS BY INDEX ROWID | S_USER | 1. 14. 1 (0) | 00:00:01 |
    | * 90 | INDEX UNIQUE SCAN | S_USER_U2 | 1 | | 1 (0) | 00:00:01 |
    | 91. TABLE ACCESS BY INDEX ROWID | S_USER | 1. 14. 1 (0) | 00:00:01 |
    | * 92 | INDEX UNIQUE SCAN | S_USER_U2 | 1 | | 1 (0) | 00:00:01 |
    ---------------------------------------------------------------------------------------------------------------------------------

    Information of predicates (identified by the operation identity card):
    ---------------------------------------------------

    33 - access("T15".") ROW_ID "(=:2)"
    35 - access("T1".") BU_ID "(=:2)"
    37 - access("T2".") PAR_ROW_ID "(=:2)"
    38 - filter ((NLS_UPPER ("LAST_NAME", '= "GENERIC_BASELETTER" nls_sort') AS
    NLS_UPPER(:3,'nls_sort=''GENERIC_BASELETTER''') AND 'T33 '. "PRIV_FLG"(='N')) "
    39 - access("T33".") ROW_ID '= 'T1'.' CONTACT_ID')
    41 - access("T33".") MED_SPEC_ID '= 'T5'.' ROW_ID")
    43 - access("T33".") CURR_PRI_LST_ID "="T18"." ROW_ID")
    44 - filter("T7".") PARTY_TYPE_CD' <>'Suspect')
    45 - access("T7".") ROW_ID "= 'T33'." PAR_ROW_ID')
    47 - access("T7".") ROW_ID "="T8"." PAR_ROW_ID')
    49 - access("T7".") ROW_ID "="T12"." PAR_ROW_ID')
    50 - access("T7".") ROW_ID "="T19"." CONTACT_ID')
    51 - filter("T7".") ROW_ID "= 'T25'." PR_SUBJECT_ID')
    53 - access("T33".") PR_POSTN_ID "="T21"." PAR_ROW_ID')
    55 - access("T7".") ROW_ID "="T23"." PAR_ROW_ID')
    57 - access("T30".") POSTN_ID ' =: 1 AND "T7".» ROW_ID "= 'T30'." CON_ID')
    59 - access("T33".") PR_DEPT_OU_ID '= 'T22'.' PAR_ROW_ID')
    61 - access("T33".") PR_DEPT_OU_ID "="T14"." PAR_ROW_ID')
    63 - access("T33".") PR_OU_ADDR_ID '= 'T11'.' ADDR_PER_ID' AND 'T33 '. "PR_DEPT_OU_ID"= "T11". ("' ACCNT_ID")
    65 - access("T33".") PR_PER_ADDR_ID "="T32"." ROW_ID")
    67 - access("T33".") PR_OU_ADDR_ID "="T17"." ROW_ID")
    69 - access("T33".") PR_DEPT_OU_ID '= 'T3'.' PAR_ROW_ID')
    71 - access("T3".") PR_POSTN_ID '= 'T31'.' PAR_ROW_ID')
    73 - access("T33".") PR_DEPT_OU_ID "="T9"." PAR_ROW_ID')
    75 - access("T33".") PR_DEPT_OU_ID '= 'T13'.' PAR_ROW_ID')
    77 - access("T7".") ROW_ID "="T20"." PAR_ROW_ID')
    78 - access("T33".") PR_DEPT_OU_ID '= 'T4'.' ROW_ID")
    79 - access("T33".") PR_SYNC_USER_ID '= 'T16'.' ROW_ID")
    81 - access("T33".") PR_POSTN_ID '= 'T29'.' POSTN_ID' AND 'T33 '. "ROW_ID"= 'T29'. ("' CON_ID")
    83 - access("T29".") POSTN_ID "="T6"." PAR_ROW_ID')
    84 - access("T29".") POSTN_ID "= 'T27'." ROW_ID")
    86 - access("T6".") PR_EMP_ID "="T26"." PAR_ROW_ID')
    88 - access("T21".") PR_EMP_ID '= 'T28'.' PAR_ROW_ID')
    90 - access("T31".") PR_EMP_ID '= 'T24'.' PAR_ROW_ID')
    92 - access("T33".") PR_SYNC_USER_ID '= 'T10'.' PAR_ROW_ID')

    Note
    -----
    -dynamic sample used for this survey (level = 5)
    -Automatic DOP: calculated degree of parallelism is 1 because of the parallel threshold
    -Profile SQL SYS_SQLPROF_013b617a8f0b005f used for this statement
    Looks like ORACLE considers all my questions with '1 second' which is the parallel threshold (5 seconds) and so works in series? Or am I completely wrong?


    (continued)

    Edited by: Penky 5 December 2012 09:37

    Penky wrote:
    Randolf,

    db_file_multiblock_read_count find not at all as far as I know, so it translates the default of 128 to 11 g. I read somewhere that it's not recommended to set it manually 10 or 11 and following.

    Thank you for the values. Which is recommended, fix, but still a lot together sites of value to something by default. I don't know yet where this MB_IO_COUNT = 8 comes, however.

    Furthermore, if you do want to play with the DOP Auto, you could just stick to the old manual DOP. If you set your PARALLEL_DEGREE_POLICY MANUAL, but have the objects marked as PARALLEL, you should get a PARALLEL query, it has provided is no less available to the optimizer serial plan.

    The default DOP is very susceptible to high (64 per node with your given configuration), you can set the PARALLEL degree to something lower.

    You could also play with ALTER SESSION FORCE PARALLEL QUERY PARALLEL x if you want / can limit this to specific sessions, then you have even to mark objects as PARALLEL, such that it could have side effects to other processes that you do not want to run in parallel.

    Randolf

  • Why doesn't a parallel query in parallel?

    Hello

    I hope someone can help me.

    I tested (several times and different ways) to see if the parallel server will work and help on my queries.

    My version is 11.2 on Solaris 10.

    I have a table with more 100,000 records and set autotrace and calendar on for testing purposes.

    I confirmed PARALLEL_MIN_SERVERS = 30 and PARALLEL_MAX_SERVERS = 160 and PARRALLEL_SERVERS_PER_CPU = 2.
    (my server has 4 CPU)

    I tested the full table running scan (select * from table) and time taken about 13:30 minutes.

    Then, I changed the table and set 4 Parallels.
    Run the test again and he ran more slowly (about 16 minutes).

    Then I ran select / * + parallel (manual) * / and it was always about 14 minutes.

    Then I ran select / * + parallel 4 * / and it took about 14:30 minutes.

    Then I reset the degree of parallel to the table to 1.
    Then, ran select / * + parallel 4 * / and it took a little less than 13:30 minutes.

    So, it seems that it does not use any parallel query. Why not?
    SQL> sho parameter cpu

NAME                                 TYPE                             VALUE
------------------------------------ -------------------------------- ---------
cpu_count                            integer                          4
parallel_threads_per_cpu             integer                          2
resource_manager_cpu_allocation      integer                          4

SQL> sho parameter parallel

NAME                                 TYPE                             VALUE
------------------------------------ -------------------------------- ---------
fast_start_parallel_rollback         string                           LOW
parallel_adaptive_multi_user         boolean                          TRUE
parallel_automatic_tuning            boolean                          FALSE
parallel_degree_limit                string                           CPU
parallel_degree_policy               string                           MANUAL
parallel_execution_message_size      integer                          16384
parallel_force_local                 boolean                          FALSE
parallel_instance_group              string
parallel_io_cap_enabled              boolean                          FALSE
parallel_max_servers                 integer                          160
parallel_min_percent                 integer                          0
parallel_min_servers                 integer                          30
parallel_min_time_threshold          string                           AUTO
parallel_server                      boolean                          FALSE
parallel_server_instances            integer                          1
parallel_servers_target              integer                          64
parallel_threads_per_cpu             integer                          2
recovery_parallelism                 integer                          0

SQL> sho parameter servers

NAME                                 TYPE                             VALUE
------------------------------------ -------------------------------- ---------
max_shared_servers                   integer
parallel_max_servers                 integer                          160
parallel_min_servers                 integer                          30
parallel_servers_target              integer                          64
shared_servers                       integer                          1

    PX COORDINATOR stage is something that you will see that when the plan uses parallel queries that are steps PX SEND QC (RANDOM) and PX BLOCK ITERATOR. You will also see that data in the column of PQ Distrib if parallel query is used. And the reference to the column of the IN-OUT backwards-> operations S indicates a transition between the parallel operations to the series (i.e. several parallel slaves, aggregated by one master series).

    Justin

  • The WPS54G Wireless Print Server works with Vista?

    The WPS54G Wireless Print Server works with Vista? I have a new Dell Vista laptop and unable to connect to the print server. The other XP machines on my network will connect correctly.

    I just got credit working mine in the answers above with a few small differences.

    1. Add the appropriate printer from the control panel > printers > add printer

    2. Select local printer, and then select [Create New Port] > [Standard TCP/IP Port]

    3. [device type] > [TCP/IP device]. Host name or IP address must be the IP address of the print server device.  I use a linksys router and difficulty mine to 192.168.2.10.  Check and are not [query the printer for and auto...]

    4. once nothing is detected, select [custom] > settings

    5. Select LPR, L2 the name value in the queue for a USB printer.  Turn on [LPR active of counting bytes.  Queue names are distinguished by the printer and I think as Mfg ("queue name" search and replacing your printer for queue names.)

    6. Select the Mfg and printer

    7. If the test page does not have a last thing, it is turn on [Control Panel] LPR Print Services > [programs and features] > [activate Windows features ON OFF] pane.  Go to [Print Services] and check on [LPR Port Monitor]

    Hope that makes the magic for you.

  • Volume shadow copy Service information: could not start the Server COM with CLSID {790f2886-9889-4c99-8ef5-531add05d044} and name SW_PROV. [0 x 80110802]

    Problems with VSS and DTC... dunno how or serious errors are

    One of the two messages I get the message this is the right place to post

    Volume shadow copy Service information: could not start the Server COM with CLSID {790f2886-9889-4c99-8ef5-531add05d044} and name SW_PROV. [0 x 80110802]

    Operation:
    Get an interface that can be called by for this provider
    List of interfaces for all providers support this context

    Context:
    Provider ID: {262b716e-bb23-41b5-aaef-e2c15e767167}
    Class ID: {790f2886-9889-4c99-8ef5-531add05d044}
    Snapshot context: 0
    Snapshot context: 0

    Hey artinusa,.

    Welcome to the Microsoft Answers site.

    This error message is seen only in a Windows Server environment.

    The community more suited for this problem would be the Microsoft TechNet community. Please post your query it better support.

    http://social.technet.Microsoft.com/forums/en-us/winserverfiles/threads

    Have a great day.

    Kind regards

    Shinmila H - Microsoft Support

    Visit our Microsoft answers feedback Forum and let us know what you think.

  • How to specify SQL custom querying the db with option to delete logical adapter

    Hi all

    I write a composite SOA application using JDeveloper SOA Suite 11.1.1.4 connection to a SQL Server database with the help of a Secretary of the poll the DB adapter with the logical delete option to send data to a BPEL process.

    I have requirements that go beyond what is supported in the UI JDeveloper for polling of the adaptor DB options, namely:
    * update several columns to mark each line read, and
    * specify different SQL to remove operation logic based on if bpel surveyed data processing was successful or not.
    A complicating factor is that the query contains two tables. Here is my complete use case:

    (1) mark will select data from two tables: for example 'headers' and 'details' simplified for this example:
    Table: headers
    HID - primary key
    name - plate
    status - "raw", "transformed" or "error".
    processedDate - null when the data is loaded, the DateTime current when the treatment of the line
    Table: Details
    HID - foreign key pointing header.hid
    attr - name attribute of data
    value - value of the attribute data

    2) there are a many relationship: 1 from detail lines to the header through the hidden columns. The adapter db SELECT the voting clerk must return results of an outer join consisting of line a header and the associated detail rows where header.status = 'no' and header.hid = details.hid. (This is supported by the UI Jdeveloper)

    (3) the survey data will be sent to be processed by a bpel process:
    (3.1) if the bpel treatment is successful, the logical delete operation (UPDATE) must set header.status = 'transformed' and header.processedDate = 'getdate() '.
    (3.2) if bpel treatment fails (for example hits a data error during the processing of the selected data) the logical delete operation (UPDATE) must be set to 'impossible' = header.status, header.processedDate = 'getdate()' and header.errorMsg = '{of the text returned by bpel}.

    Several parts of the #3 are not supported by the UI JDeveloper: update several columns to mark the addressed line, using getdate() to fill a value of one of these updates to the column, update of different operations based on the results of the BPEL, processing of the data (success or error) and using data from BPEL treating it as a value of these updates of column (error message).

    I found examples that describe the specification that is customized by using querying SQL Delete option to create a template and then modify the toplink files to specify custom select and update SQL to implement a logical deletion. (for example, http://dlimiter.wordpress.com/2009/11/05/advanced-logic-in-oracle-bpel-polling-database-adapter/ and http://myexperienceswithsoa.blogspot.com/2010/06/db-adapter-polling-tricks.html). But none of them match what I have in my project, in the first case because maybe because I use a newer version of JDeveloper and the second I think because in my case, two tables are involved.

    Any suggestion would be appreciated. Thank you, John

    Hi John,.

    You raised a good script.
    First of all, let me say that the purpose of the DB of the election operation, is to have an option to start the process of a DB table/view and not update several fields in a table (or have other complex manipulations on the table).
    Thus, when choose update a field in a record, after reading it, you "say" the engine not to question this record again. Of course, I guess you can find a solution/workaround for it, but I don't think that this is the way...

    The question now is what to do?
    You can have another DB adapter where you can update the data after you have completed the process. In this case, after reading the data (on the query operation) - updated the "transformed" for example = header.status and after processing the selected data update the rest fields.

    Hope it make sense for you.

    Arik

  • Paraller error query server when creating the database using DBCA on UNIX

    Hi all
    I'm trying to create the database on UNIX platform of database 11g R1.
    At the end of the creation of the database using DBCA, I got the error:

    ORA - 12801:error reported in the parallel query P077 Server
    ORA-00018: maximum number of sessions exceeded
    ORA-06512: at "SYS." UTL_RECOMP", line 760
    ORA-06512: at "SYS." UTL_RECOMP", line 773
    ORA-06512: at line 1

    Please suggest what I can do to remove this problem.

    Concerning
    Girish Sharma

    He doesn't have to run in parallel, but it is probably

    Bug 8343487: UTLRP. PARALLEL EXECUTION, REGARDLESS OF THE CONFIGURATION OF SQL

    Werner

  • Session of parallel query of murder

    Hello
    I'm under Oracle 11.2.0.1.0 on Solaris 5.10.

    A few hours ago, I ran a job through DBMS_JOB (Yes, I need to use dbms_schedular), and in the work, I used a parallel query. Now, I want to delete the task. I would also like to clean up the sessions. I can remove the work by DBMS_JOB.remove (identification). Is it possible that I have killed a parallel query session Coordinator and he would automatically kill all sessions of the slave?

    Thanks and greetings

    Published by: Fahd Mirza on April 22, 2010 11:57

    Very simple, run

    Select "Co-ordinator of the query" qcsid, count (*) as 'Slaves Count' of the Group v$ px_session by qcsid;

    kill the request coordinators and all his servants will be killed too.

  • Calendar Server responds with 403 Forbidden' operation CalDAVWriteEntityQueueableOperation.

    With the latest version of Mac server (5.1.5 on OS X 10.11.6), when I try to migrate a large calendar via a client computer, it takes a long time and then I get an endless series of

    The server responds with an error.

    Access to the "[name of the cal event]' in '[the calendar name]' account"[account name]"is not allowed.

    The server responded:

    "HTTP/1.1 403 Forbidden.

    operating CalDAVWriteEntityQueueableOperation.

    [Go offline]  [Back to the server.

    errors.  I have to leave something heavy press enter for a few hours to get rid of all the errors.

    Migration of the small calendars to the server (by importing data in iCal on the calendar of the hosted account) works for most (it may be a mistake or 2).

    I found a suggestion of years ago on another Board that permissions can be screwed to the top and use this Terminal command:

    sudo chown-r _calendar:_calendar/Library/CalendarServer/Documents

    However, this suggestion was for the 10.6 Server and may no longer apply.

    Any thoughts?

    Today, I had the idea of trying to download the calendar from the same computer that is serving the calendars.  Should be faster and better (and the same OS!)!

    So, an account on it hosting Mac and started the import process, which seemed to go more smoothly, but then seemed the same thing happening: most of the CPU has been get taken up with various activities related to the calendar and then after a while, it started spitting out errors, but they were slightly different.  There are too many mistakes all move just above.  Also, try to add more events to this calendar also fails.

    Now, they say:

    The event "[name of event]" was rejected by '[Server]' because the maximum number of resources has been reached.

    Is there a limit to the size if a calendar?

    I do something wrong or is this a limit of the software?

  • iCal locked w / "the server responds with an error."

    I created a new reminder that I think was too long, so it doesn't have to deal with, but rather "the server responded with an error," appears in a separate imposed on the calendar window that contains the whole long Encore but freeze the iCal program, so I can't go to preferences and change anything. I have to force quit iCal and try & try again, but each time only a few seconds, the message reappears and everything is frozen. HELP PLEASE.

    OK friends, in another string of comments that I found my solution, simple - press the enter/return key and delete key at the same time, and the reminder was sent to the desert. God thank you... happy happy

  • Acquisition parallel to 25 MHz with a PXI-7854R

    Hello

    For an application, I need to acquire a bus parallel to 25 MHz with a 7854R.

    I search for information on the forum and I am a little lost. I have seen that we can create derivatives clock on my FPGA.

    I can create a clock of 100 MHz and use it in a SCTL to check if a rising edge appears on my clock line and acquire the line data (24 rows of data), but I do not understand what means the limit of 40 MHz for EID.

    At what rate data are updated if I used a SCTL clocked at 100 MHz to read a digital input?

    Do you know if it the best way, or if it is possible to acquire my bus with this material?

    Thanks in advance for your answer

    The clock of the FPGA is of 40 MHz.  This is the maximum rate of the input/output of the FPGA (digital i/o).  What you could do is use a method node on the clock line to "wait on a side on the rise", read the data and send the data to a FIFO or DMA.  Put this inside a loop, and you should be good to go.

  • I had Windows server 2008 with microsoft web apps 2010 and I am unable to install KB2553095 to (MS11-072)

    I had Windows server 2008 with microsoft web apps 2010 and I am unable to install KB2553095. While trying to manually download and install its giving message "there are no products made by this package installed on your system", but I had windows web apps 2010 SP1 is installed on all my servers.

    Security bulletins: MS11-072
    Security bulletins: MS11-072

    Security Bulletin: MS11-072

    Hello

    Note that your computer is under domain, you must contact the TechNet forum, where we are the support technicians who are well equipped with knowledge on the issues of domain, do please visit the link provided below.

    http://social.technet.Microsoft.com/forums/en-us/winserverfiles/threads

Maybe you are looking for