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

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

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

Similar Messages

  • ORA-12801: error signaled in parallel query server

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

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

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

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

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

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

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

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

  • SQL Error: ORA-12801: error signaled in parallel query server 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..

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

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

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

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

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

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

  • ORA-12801: error 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.

  • ORA-12801: error signaled in parallel query server P001 and ORA-01008:

    I am trying to refresh a refresh group i am getting the below error. This refresh group is on a database RIO12. All Mviews on this database point to target database - TRIO23 (which has master tables) using database link. The refresh group has 21 Mviews. Mview ACCOUNT is one of them i am getting the below error.
    BEGIN dbms_refresh.refresh('PLATS.PLATS_RG'); END;
    ERROR at line 1:
    ORA-12048: error encountered while refreshing materialized view "PLATS"."ACCOUNT"
    ORA-12801: error signaled in parallel query server P001
    ORA-01008: not all variables bound
    ORA-02063: preceding 2 lines from TRIO23
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2254
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2460
    ORA-06512: at "SYS.DBMS_IREFRESH", line 683
    ORA-06512: at "SYS.DBMS_REFRESH", line 195
    ORA-06512: at line 1
    TRIO23 is oracle version 10.2.0.5.0, RIO12 is oracle version 10.2.0.3.0
    Refreshing PLATS_RG refresh group has no problems from last 2 years, other 20 MViews when executed manually they are refreshed. Please help me in resolving this error. Thanks.

    Do you have cursor_sharing set to force or similar? if so then you may be hitting bug Bug 5863277. Please confirm with Oracle support.
    thanks

  • 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

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

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

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

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

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

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

  • ORA-12801: error signalled in parallel query sever P0007 ORA-00600:internal

    Clould someone please help me and interpret the meaning of the following error
    "ora-12801:error signaled query server P005-00600: internal error code, arguments:[kxspoc:EXL1]"
    This error occur at post-change trigger of one of the fields in my form9i application.
    The code below is a program unit within the form that it is called at the post-change trigger of "loan_application_no" field that raise the error
    PROCEDURE DRV_LOAN_APPL_DET(
    P_LOAN_APPLICATION_NO IN NUMBER /* Item value */
    ,P_LOAN_CODE IN VARCHAR2 /* Item value */
    ,P_EMP_NO IN VARCHAR2 /* Item value */
    ,P_FIELD_LEVEL IN BOOLEAN ) IS /* Is the trigger item level */
    BEGIN
    DECLARE
    CURSOR C IS
    SELECT LM.LOAN_CODE DSP_LOAN_CODE
    ,LM.LOAN_CODE DSP_LOAN_CODE
    ,LC5.DESCRIPTION DSP_DESCRIPTION
    ,LM.PRINCIPAL_AMOUNT DSP_PRINCIPAL_AMOUNT
    ,LM.TOTAL_PRINCIPAL_PAID DSP_TOTAL_PRINCIPAL_PAID
    FROM LOAN_MASTER LM
    ,LOAN_CODES LC5
    WHERE P_emp_no=emp_no
    and P_loan_application_no = loan_application_no
    AND LC5.LOAN_CODE = LM.LOAN_CODE;
    BEGIN
    OPEN C;
    FETCH C
    INTO
    :one.loan_code
    ,:one.DSP_LOAN_CODE
    ,:one.dsp_DESCRIPTION
    ,:one.dsp_PRINCIPAL_AMOUNT
    ,:one.dsp_TOTAL_PRINCIPAL_PAID ;
    EXCEPTION
    WHEN OTHERS THEN
    CGTE$OTHER_EXCEPTIONS;
    END;
    END;
    please help, thanks
    Joy

    You want to close cursor C ...
    ... or just use a select .... into .... it's much easier (and executes quicker).

  • Error signaled in parallel query server p005 DATE format comparison

    Hello All,
    I have a data like this.
    {code}
    j_id   s_id     b_id    lc   t_date                             my_val1     my_val2
    100    200    300     prs   2013-07-17 16:01:47         myval1     myval2
    100    200   300     prs    2013-07-17 16:01:47         myCval1   myCval2
    {code}
    When i am running a query like this
    {code}
    update my_tab b
            set my_col = 'X'
            where rowid <> ( select max(t.rowid) from my_tab t
                             where
                                    t.J_ID        = b.J_ID   and
                                    t.S_ID = b.S_ID and
                                    t.B_ID      = b.B_ID and
                                    t.LC   = b.LC
                                  and TO_TIMESTAMP(trim(t.t_DATE), 'YYYY-MM-DD HH24:MI:SS.FF')
                                   = TO_TIMESTAMP(trim(b.t_DATE), 'YYYY-MM-DD HH24:MI:SS.FF')
    {code}
    I know i have a DATE format but converting it into TIMESTAMP because my data is random and could contain the time stamp as well.
    My concern here is when i run above update statement i get error
    {code}
    ORA-12801: error signaled in parallel query server P005
    ORA-01862: the numeric value does not match the length of the format item
    {code}
    but when i do like below.. It runs fine. Not sure what i am missing here or doing something wrong. Please help.
    {code}
    select to_timestamp('2013-07-08 17:58:47', 'YYYY-MM-DD HH24:MI:SS.FF') from dual
    where
    to_timestamp('2013-07-08 17:58:47', 'YYYY-MM-DD HH24:MI:SS.FF') = to_timestamp('2013-07-08 17:58:47', 'YYYY-MM-DD HH24:MI:SS.FF')
    {code}
    Thanks!

    user10647455 wrote:
    Hello All,
    I have a data like this.
    {code}
    j_id   s_id     b_id    lc   t_date                             my_val1     my_val2
    100    200    300     prs   2013-07-17 16:01:47         myval1     myval2
    100    200   300     prs    2013-07-17 16:01:47         myCval1   myCval2
    {code}
    When i am running a query like this
    {code}
    update my_tab b
            set my_col = 'X'
            where rowid <> ( select max(t.rowid) from my_tab t
                             where
                                    t.J_ID        = b.J_ID   and
                                    t.S_ID = b.S_ID and
                                    t.B_ID      = b.B_ID and
                                    t.LC   = b.LC
                                  and TO_TIMESTAMP(trim(t.t_DATE), 'YYYY-MM-DD HH24:MI:SS.FF')
                                   = TO_TIMESTAMP(trim(b.t_DATE), 'YYYY-MM-DD HH24:MI:SS.FF')
    {code}
    I know i have a DATE format but converting it into TIMESTAMP because my data is random and could contain the time stamp as well.
    My concern here is when i run above update statement i get error
    {code}
    ORA-12801: error signaled in parallel query server P005
    ORA-01862: the numeric value does not match the length of the format item
    {code}
    but when i do like below.. It runs fine. Not sure what i am missing here or doing something wrong. Please help.
    {code}
    select to_timestamp('2013-07-08 17:58:47', 'YYYY-MM-DD HH24:MI:SS.FF') from dual
    where
    to_timestamp('2013-07-08 17:58:47', 'YYYY-MM-DD HH24:MI:SS.FF') = to_timestamp('2013-07-08 17:58:47', 'YYYY-MM-DD HH24:MI:SS.FF')
    {code}
    Thanks!
    If you have a date column, converting that to a timestamp isn't going to magically add more information to the date.
    Date data types hold time information (not to the fractional precision like timestamps, but up to the second) ... if you are having a problem seeing that information, it's likely because of your NLS_DATE_FORMAT setting (whatever client you are using to view the data isn't showing you all of the information, but it's still there).
    So basically, this boils down to your code not "making sense" at the moment
    Cheers,

  • Error signaled in parallel query server P006

    This is the error stack..
    ERROR at line 1:
    ORA-06502: PL/SQL: numeric or value error
    ORA-06512: at "XXXXX", line 47
    ORA-06512: at "XXXXX", line 171
    ORA-12801: error signaled in parallel query server P006
    ORA-01555: snapshot too old: rollback segment number 4 with name "_SYSSMU4$"
    too small
    ORA-06512: at line 1
    Please help.
    Thanks.

    Hi,
    I wrote the code to uploada to a flat file (.txt format) by using UTL_FILE package in PLSQL. In that code I redirected errors to a error file.
    It is uploading the correct data to the file, and also generating a error file with the below error message.
    Upload Type: cat Error Code: -12801 System Message: 10/21/2008 13:19:39 Oracle Message: ORA-12801: error signaled in parallel query server P026, ins.
    here the word 'cat' is part of my file name passing through exception part in PLSQL code.
    Below is exception part of my PLSQL program:
    EXCEPTION
    WHEN VALUE_ERROR
    THEN
    p_write_to_upload_log ('cat', TO_CHAR (SQLCODE), 'Value error reading Retail upload', SQLERRM);
    WHEN UTL_FILE.invalid_filehandle
    THEN
    p_write_to_upload_log ('cat', TO_CHAR (SQLCODE), 'Write error on upload file', SQLERRM);
    WHEN UTL_FILE.invalid_operation
    THEN
    p_write_to_upload_log ('cat', TO_CHAR (SQLCODE), 'Upload file is not open', SQLERRM);
    WHEN UTL_FILE.read_error
    THEN
    p_write_to_upload_log ('cat', TO_CHAR (SQLCODE), 'OS error during file read', SQLERRM);
    WHEN OTHERS
    THEN
    p_write_to_upload_log ('cat', TO_CHAR (SQLCODE), TO_CHAR (SYSDATE, 'MM/DD/RRRR HH24:MI:SS'), SQLERRM);
    END p_cat_upload;
    Please let me know if you need any more information on this.
    Appriciate your help in resolving this error message.
    Thanks and Regards
    Vedaprakash N

Maybe you are looking for