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

Similar Messages

  • 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

  • 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

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

  • ORA-12801: error signaled in parallel query server P002

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

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

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

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

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

  • How to kill the blocking session

    hi expert,
    when i m going to run the below query
    Update rcv_transactions_interface rti set rti.processing_mode_code ='BATCH'  where rti.interface_transaction_id = 3671265
    it gives the error:
    ORA-00054 resource busy and acquire with NOWAIT specified.
    i find out the blocking session by using the blow query;
    SELECT  a.SESSION_ID, a.SESSION_SERIAL#, min(A.SAMPLE_TIME) start_time,max(A.SAMPLE_TIME) end_time,a.inst_id, a.blocking_session,a.user_id,s.sql_text,A.EVENT,O.OBJECT_NAME,max(A.SAMPLE_TIME) - min(A.SAMPLE_TIME) 
    FROM GV$ACTIVE_SESSION_HISTORY a  ,gv$sql s, dba_objects o
    where a.sql_id=s.sql_id
    and A.CURRENT_OBJ# = O.OBJECT_ID
    and blocking_session is not null
    and a.user_id  != 0 -- exclude SYS user
    and a.sample_time > sysdate - 7
    and a.event = 'enq: TX - row lock contention'
    group by a.SESSION_ID, a.SESSION_SERIAL#, a.inst_id,a.blocking_session,a.user_id,s.sql_text,A.EVENT,O.OBJECT_NAME
    it gives the output
    SESSION_ID
    SESSION_SERIAL#
    START_TIME
    END_TIME
    INST_ID
    BLOCKING_SESSION
    USER_ID
    SQL_TEXT
    EVENT
    OBJECT_NAME
    MAX(A.SAMPLE_TIME)-MIN(A.SAMPLE_TIME)
    369
    45,849
    9/4/2013 8:29:33.119 AM
    9/4/2013 11:40:27.508 AM
    1
    554
    173
    SELECT POL.UNIT_PRICE   FROM PO_LINES POL  WHERE POL.PO_LINE_ID = :b1
    enq: TX - row lock contention
    PO_LINES_ALL
    +00 03:10:54.389000
    554
    18,872
    9/4/2013 8:29:33.119 AM
    9/4/2013 11:40:27.508 AM
    1
    365
    173
    SELECT POL.UNIT_PRICE,POL.QUANTITY,POL.UNIT_MEAS_LOOKUP_CODE,POL.AMOUNT   FROM PO_LINES POL  WHERE POL.PO_LINE_ID = :b1
    enq: TX - row lock contention
    JA_IN_PO_LINE_LOCATION_TAXES
    +00 03:10:54.389000
    572
    168
    9/4/2013 8:29:33.119 AM
    9/4/2013 11:40:27.508 AM
    1
    554
    173
    select line_location_id into :b0 from po_line_locations_all where line_location_id=:b1 for update of line_location_id
    enq: TX - row lock contention
    PO_LINE_LOCATIONS_ALL
    +00 03:10:54.389000
    581
    4,973
    9/4/2013 10:49:38.157 AM
    9/4/2013 10:50:39.259 AM
    1
    572
    173
    Update rcv_transactions_interface rti set rti.processing_mode_code ='BATCH'  where rti.interface_transaction_id = 3671265
    enq: TX - row lock contention
    RCV_TRANSACTIONS_INTERFACE
    +00 00:01:01.102000
    my problem is in the above  output among 4 which i have to delete so sove my issue.
    its very urgent for me.
    plz plz suggest me and how can i kill the session.
    thanks & regards
    pritesh ranjan

    priteshranjan wrote:
    hi expert,
    when i m going to run the below query
    Update rcv_transactions_interface rti set rti.processing_mode_code ='BATCH'  where rti.interface_transaction_id = 3671265
    it gives the error:
    ORA-00054 resource busy and acquire with NOWAIT specified.
    i find out the blocking session by using the blow query;
    SELECT  a.SESSION_ID, a.SESSION_SERIAL#, min(A.SAMPLE_TIME) start_time,max(A.SAMPLE_TIME) end_time,a.inst_id, a.blocking_session,a.user_id,s.sql_text,A.EVENT,O.OBJECT_NAME,max(A.SAMPLE_TIME) - min(A.SAMPLE_TIME)
    FROM GV$ACTIVE_SESSION_HISTORY a  ,gv$sql s, dba_objects o
    where a.sql_id=s.sql_id
    and A.CURRENT_OBJ# = O.OBJECT_ID
    and blocking_session is not null
    and a.user_id  != 0 -- exclude SYS user
    and a.sample_time > sysdate - 7
    and a.event = 'enq: TX - row lock contention'
    group by a.SESSION_ID, a.SESSION_SERIAL#, a.inst_id,a.blocking_session,a.user_id,s.sql_text,A.EVENT,O.OBJECT_NAME
    it gives the output
    SESSION_ID
    SESSION_SERIAL#
    START_TIME
    END_TIME
    INST_ID
    BLOCKING_SESSION
    USER_ID
    SQL_TEXT
    EVENT
    OBJECT_NAME
    MAX(A.SAMPLE_TIME)-MIN(A.SAMPLE_TIME)
    369
    45,849
    9/4/2013 8:29:33.119 AM
    9/4/2013 11:40:27.508 AM
    1
    554
    173
    SELECT POL.UNIT_PRICE   FROM PO_LINES POL  WHERE POL.PO_LINE_ID = :b1
    enq: TX - row lock contention
    PO_LINES_ALL
    +00 03:10:54.389000
    554
    18,872
    9/4/2013 8:29:33.119 AM
    9/4/2013 11:40:27.508 AM
    1
    365
    173
    SELECT POL.UNIT_PRICE,POL.QUANTITY,POL.UNIT_MEAS_LOOKUP_CODE,POL.AMOUNT   FROM PO_LINES POL  WHERE POL.PO_LINE_ID = :b1
    enq: TX - row lock contention
    JA_IN_PO_LINE_LOCATION_TAXES
    +00 03:10:54.389000
    572
    168
    9/4/2013 8:29:33.119 AM
    9/4/2013 11:40:27.508 AM
    1
    554
    173
    select line_location_id into :b0 from po_line_locations_all where line_location_id=:b1 for update of line_location_id
    enq: TX - row lock contention
    PO_LINE_LOCATIONS_ALL
    +00 03:10:54.389000
    581
    4,973
    9/4/2013 10:49:38.157 AM
    9/4/2013 10:50:39.259 AM
    1
    572
    173
    Update rcv_transactions_interface rti set rti.processing_mode_code ='BATCH'  where rti.interface_transaction_id = 3671265
    enq: TX - row lock contention
    RCV_TRANSACTIONS_INTERFACE
    +00 00:01:01.102000
    my problem is in the above  output among 4 which i have to delete so sove my issue.
    its very urgent for me.
    plz plz suggest me and how can i kill the session.
    thanks & regards
    pritesh ranjan
    According to the above, your session_id is 581 which is blocked by session_id 572 so you need to kill the 3rd session in the list.
    Thanks,
    Hussein

  • How to kill particular Oracle Session from the multiple Session of User

    Hi,
    I am working on Web Application using ASP.NET , C# with Oracle. I am excuting queries from multiple connection of same user. I want to kill particular user session. I have tried to Kill session by using ALTER SYSTEM KILL SESSION 'sid,serial#' it is working fine but how can i identify which session is generated by particular connection so that i can kill that particular session.
    Suppose there us user 'abc' there are multple instance of this user and all are active but same USERNAME. So Please tell me how can i identify that session through which i am executing the query.
    Thanks,
    Nitin

    Some ideas for how to pick the right session:
    -Look at the time the session was connected (logon_time)
    -Look at the time the session last started it's most recent statement (last_call_et)
    -Look at the sql that the session is running (join with sql_address and sql_hash_value over to v$sqltext_with_newlines or one of the other views that show you the sql they are running)
    That usually gets me most of the way, if it's possible to distinguish them. ("Yeah I just started this query and I want you to kill it." is different than "I started five different queries at about the same time and I'm not sure which one I need killed.")

  • Parallel query question

    How do i figure out which sessions are involved in a parallel query and how do i tell what the master session is?

    Try this...QC would be the coordinator:
    select
    decode(px.qcinst_id,NULL,username,
    ' - '||lower(substr(pp.SERVER_NAME,
    length(pp.SERVER_NAME)-4,4) ) )"Username",
    decode(px.qcinst_id,NULL, 'QC', '(Slave)') "QC/Slave" ,
    to_char( px.server_set) "SlaveSet",
    to_char(s.sid) "SID",
    to_char(px.inst_id) "Slave INST",
    decode(sw.state,'WAITING', 'WAIT', 'NOT WAIT' ) as STATE,
    case sw.state WHEN 'WAITING' THEN substr(sw.event,1,30) ELSE NULL end as wait_event ,
    decode(px.qcinst_id, NULL ,to_char(s.sid) ,px.qcsid) "QC SID",
    to_char(px.qcinst_id) "QC INST",
    px.req_degree "Req. DOP",
    px.degree "Actual DOP"
    from gv$px_session px,
    gv$session s ,
    gv$px_process pp,
    gv$session_wait sw
    where px.sid=s.sid (+)
    and px.serial#=s.serial#(+)
    and px.inst_id = s.inst_id(+)
    and px.sid = pp.sid (+)
    and px.serial#=pp.serial#(+)
    and sw.sid = s.sid
    and sw.inst_id = s.inst_id
    order by
    decode(px.QCINST_ID, NULL, px.INST_ID, px.QCINST_ID),
    px.QCSID,
    decode(px.SERVER_GROUP, NULL, 0, px.SERVER_GROUP),
    px.SERVER_SET,
    px.INST_ID
    /

  • Parallel query feature

    Hi to utilize the parallel query option in database in 9i 10 g how can me modify the sql staments or the procedures.Whether it will use the parallel query feature without giving the parallel query hint?
    with regards
    ramya

    When we have to handle a lot of data in operations, like full table scans of large tables, or the creation of large indices, we can divide the work. Instead of using a single process for one statement, the work can be spread to multiple processes. This is called parallel execution or parallel processing. Parallel execution normally reduces response time when you are accessing large amount of data, but it is not always faster than a serial operation.
    Parallel execution is useful for many types of operations like:
    * Queries requiring large table scans, joins, or partitioned index scans
    * Creation of large indices and large tables
    * Bulk inserts, updates and deletes
    * Aggregations
    We have the following hints to influence the use of parallel execution
    * PARALLEL
    * NOPARALLEL
    * PQ_DISTRIBUTE
    * PARALLEL_INDEX
    * NOPARALLEL_INDEX
    From the session where the query run, type:
    select * from v$pq_sesstat;
    SELECT slave_name,status, cpu_secs_total
    FROM v$pq_slave;
    Performance summary:
    It cannot be stressed strongly enough that parallel query is not always quicker than serial. Some queries are more suited to parallel operations than others. If you are using parallel execution, then you should endeavour to maximize I/O throughput to your disk. Ensure that:
    * you have enough slaves to retrieve the data efficiently
    * you do not have too many slaves (avoid maxing out the CPU)
    * you set realistic memory parameters (sort_area_size etc.) so that you do not max out memory and cause swapping
    * the data is spread over multiple disk spindles so that slaves do not contend for I/O resource
    * the type of query your are attempting to execute in parallel is suitable for parallelisation.
    * watch for non-uniform loading on slave processes as this could indicate data skew.
    http://www.jlcomp.demon.co.uk/pqcosts.html
    courtesy from oracle metalink.
    SJH
    OCP DBA

  • Parallell query performance

    Hi Experts,
    I could not find any reference with regards to performance of parallel query when the SMT(simultaneous multi-thread) enabled on AIX. Could you please share your thoughts based on experience?

    What are you asking to compare?  The performance of parallel query on AIX vs the performance of a single-threaded query?  The performance of parallel query on AIX with SMT enabled vs. the performance of parallel query on AIX with SMT disabled?  Something else?
    Realistically, any sort of discussion about performance will be highly dependent on the specifics of your query/ queries and the load characteristics of your system.  It is entirely possible for parallel query to make a single-threaded query slower.  It is entirely possible for parallel query to allow a single poorly-performing query to consume all the available resources on the system and to make every other session grind to a halt.  It is entirely possible for parallel query to create large improvements in the performance of a query and of a system.  Without knowing your queries, your workload, your system, your configuration, etc it is impossible to guess what would happen on your system.  That is even more true when we're talking about tweaking operating system configuration knowing nothing about your database.
    Justin

  • TuxRacer kill my x session!!

    I installed tuxracer:
    pacman -Sy tuxracer
    it worked fine.
    when i ran it the first time, he could not find libstdc++.so.6
    so:
    pacman -S gcc
    it installed it, and now when I run tux racer it kills my x session.

    nvidia-installer log file '/var/log/nvidia-installer.log'
    creation time: Mon May 10 14:53:08 2004
    option status:
      license pre-accepted    : true
      update                  : false
      force update            : false
      expert                  : false
      uninstall               : false
      driver info             : false
      no precompiled interface: true
      no ncurses color        : false
      query latest driver ver : false
      OpenGL header files     : false
      no questions            : true
      silent                  : false
      XFree86 install prefix  : /usr/X11R6
      OpenGL install prefix   : /usr
      Installer install prefix: /usr
      kernel source path      : (not specified)
      kernel install path     : (not specified)
      proc mount point        : /proc
      ui                      : none
      tmpdir                  : /tmp
      ftp site                : ftp://download.nvidia.com
    Using built-in stream user interface
    -> License accepted by command line option.
    -> There appears to already be a driver installed on your system (version: 1.0-
       5336).  As part of installing this driver (version: 1.0-5336), the existing
       driver will be uninstalled.  Are you sure you want to continue? ('no' will a
       bort installation) (Answer: Yes)
    -> Not probing for precompiled kernel interfaces.
    -> Kernel source path: '/lib/modules/2.6.3/build'
    -> Performing cc_version_check with CC="cc".
    -> Cleaning kernel module build directory.
       executing: 'cd ./usr/src/nv; make clean'...
       rm -f -f nv.o os-agp.o os-interface.o os-registry.o nv.o os-agp.o os-interfa
       ce.o os-registry.o nvidia.mod.o
       rm -f -f build-in.o nv-linux.o *.d .*.{cmd,flags}
       rm -f -f nvidia.{o,ko,mod.{o,c}} nv_compiler.h *~
    -> Building kernel module:
       executing: 'cd ./usr/src/nv; make module SYSSRC=/lib/modules/2.6.3/build'...
         HOSTCC  scripts/fixdep
         HOSTCC  scripts/split-include
         HOSTCC  scripts/conmakehash
         HOSTCC  scripts/docproc
         HOSTCC  scripts/kallsyms
         CC      scripts/empty.o
         HOSTCC  scripts/mk_elfconfig
         MKELF   scripts/elfconfig.h
         HOSTCC  scripts/file2alias.o
         HOSTCC  scripts/modpost.o
         HOSTLD  scripts/modpost
         HOSTCC  scripts/pnmtologo
         HOSTCC  scripts/bin2c
         SPLIT   include/linux/autoconf.h -> include/config/*
       *** Warning: Overriding SUBDIRS on the command line can cause
       ***          inconsistencies
         CC      arch/i386/kernel/asm-offsets.s
         CHK     include/asm-i386/asm_offsets.h
       echo #define NV_COMPILER "`cc -v 2>&1 | tail -n 1`" > /tmp/selfgz362/NVID
       IA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv_compiler.h
         CC [M]  /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.o
       In file included from include/linux/sched.h:23,
                        from include/linux/module.h:10,
                        from /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/
       nv/nv-linux.h:52,
                        from /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/
       nv/nv.c:14:
       include/linux/smp.h:33: error: conflicting types for 'smp_send_reschedule'
       include/asm/smp.h:41: error: previous declaration of 'smp_send_reschedule' w
       as here
       include/linux/smp.h:33: error: conflicting types for 'smp_send_reschedule'
       include/asm/smp.h:41: error: previous declaration of 'smp_send_reschedule' w
       as here
       /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c: In function `
       nvos_malloc_pages':
       /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:385: warning:
       use of cast expressions as lvalues is deprecated
       /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c: In function `
       nvos_create_alloc':
       /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:513: warning:
       use of cast expressions as lvalues is deprecated
       /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:523: warning:
       use of cast expressions as lvalues is deprecated
       /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c: At top level:
       /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:1185: warning:
       initialization from incompatible pointer type
       /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c: In function `
       nv_alloc_file_private':
       /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:1193: warning:
       use of cast expressions as lvalues is deprecated
       /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:1204: warning:
       use of cast expressions as lvalues is deprecated
       /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c: In function `
       nv_kern_open':
       /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:1265: warning:
       use of cast expressions as lvalues is deprecated
       /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c: In function `
       nv_kern_ctl_open':
       /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:1914: warning:
       use of cast expressions as lvalues is deprecated
       make[3]: *** [/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.o]
       Error 1
       make[2]: *** [/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv] Erro
       r 2
       nvidia.ko failed to build!
       make[1]: *** [module] Error 1
       make: *** [module] Error 2
    -> Error.
    ERROR: Unable to build the NVIDIA kernel module.
    ERROR: Installation has failed.  Please see the file
           '/var/log/nvidia-installer.log' for details.  You may find suggestions
           on fixing installation problems in the README available on the Linux
           driver download page at www.nvidia.com.

  • 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: #

  • 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

  • How to kill a query?

    I moved from TOAD to SQL Developer and am not an experienced programmer.
    When a query gets away from me that I want to kill, I hit the red X button. SQL Developer will hang. Sometimes I will actually have to stop and restart the Oracle service to kill the query.
    How do I kill a query immediately?

    This is probably due to the nature of your query rather than an sqldev bug, so the database won't let you cancel and sqldev just hangs there until it completes anyway.
    You shouldn't have any trouble canceling a normal select. If you do, get back with DB/sqldev version and a reproducible script.
    Also, it would be great if you can compare the same statement with TOAD. If it can be canceled there, it should be possible in sqldev too.
    Last, you can always kill the whole session through sqldev's Monitor Sessions tool (in a second instance since the first one is blocked by your statement), the Enterprise Manager or the OS' KILL command.
    Regards,
    K.

Maybe you are looking for