ORA-12827 insufficient parallel query slaves available

Hi,
In our sql statements , we are using PARALLEL_MIN_PERCENT = 100 for getting 100% parallel slaves.
But sometimes,it fails with ORA-12827.
if we remove PARALLEL_MIN_PERCENT = 100 , then obviously the query execution time will increase.
How to make sure that the query always get 100% parallel query slaves?
Is there any work around for this other than removing or changing PARALLEL_MIN_PERCENT?
Thanks

Increase parallel_min_servers. What happens is as follows. At instance startup oracle starts parallel_min_servers processes to handle PQO (Parallel Query Option). Assume, for example parallel_min_servers = 4. Assume table has degree of parallelism 6. When you set PARALLEL_MIN_PERCENT = 100 you are requesting PQO to start 6 slave processes while only 4 are available.
SY.

Similar Messages

ORA-12827: insufficient parallel query slaves

Hi All,
We are hitting ORA-12827 after setting up parameters related to parallelism. It was a suggestion from Oracle , just to boost up the performance by setting up auto parallelism and few other parameters complementing to it. We have made changes on 2 Database , but we are hitting this only one database, which has similar in configuration in terms of hardware (32 cpus, gobs of ram , sufficient I/O) but it has less SGA setup (7G) over 30G on other database, which seems fine as if now. Here ,ORA-12827 , clearly suggest that , the server does not have sufficient parallel slaves , may be , already in use by different users. I have a question here , what do you think , what is causing this issue to occur , is it no of users or memory or anything else. I know, parallel stuff is not scalable in terms of no of increased users. Also, since we are on 11GR2, we can go for "parallel statement queuing" and that will not fail us ,because of resources getting exhausted completely, right ? What do you think , would it be a right approach to go with or you would you go different approach? thanks a lot for all of your help in past.
OS -- Enterprise Linux Server release 5.8 (Tikanga)
DB --- 11.2.0.3.0
------------- Parameters suggested by Oracle -----------------------------
change parallel_min_servers=8
change parallel_max_servers=128
change parallel_degree_limit=8
change parallel_degree_policy=AUTO
change parallel_min_percent=50
----------------------------------- Current SGA and Parallel Settings ---------------------
NAME                                 TYPE                              VALUE
fast_start_parallel_rollback         string                            LOW
parallel_adaptive_multi_user         boolean                           TRUE
parallel_automatic_tuning            boolean                           FALSE
parallel_degree_limit                string                            8
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                           128
parallel_min_percent                 integer                           50
parallel_min_servers                 integer                           8
parallel_min_time_threshold          string                            AUTO
parallel_server                      boolean                           FALSE
parallel_server_instances            integer                           1
parallel_servers_target              integer                           128
parallel_threads_per_cpu             integer                           2
recovery_parallelism                 integer                           0
SQL> show parameter sga_
NAME                                 TYPE                              VALUE
sga_max_size                         big integer                       7G
sga_target                           big integer                       7GRegards

why posted this question then?Fran, it's not about the "ORA-12827" only. I also asked the , what is the reason , one can think of , when comparing other database , which has more memory other then that , pretty much identical. Please go through my question once again , you would realize , what was the question actually.
Regards

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

Need Parallel Querying

Hi Friends,
What you get from the following info?
Will I be able to use parallel query effectively in my datawarehousing database.
Oracle DB version Enterprise Edition 10g 10.2.0.3.0 64 bit
SQL> show parameter parallel
NAME                                 TYPE        VALUE
fast_start_parallel_rollback         string      LOW
parallel_adaptive_multi_user         boolean     TRUE
parallel_automatic_tuning            boolean     FALSE
parallel_execution_message_size      integer     2152
parallel_instance_group              string
parallel_max_servers                 integer     160
parallel_min_percent                 integer     0
parallel_min_servers                 integer     0
parallel_server                      boolean     FALSE
parallel_server_instances            integer     1
parallel_threads_per_cpu             integer     2
recovery_parallelism                 integer     0
SQL> select name,value from v$sysstat where name like 'Parallel%';
NAME                                                                  VALUE
Parallel operations not downgraded                                   461273
Parallel operations downgraded to serial                              91484
Parallel operations downgraded 75 to 99 pct                              33
Parallel operations downgraded 50 to 75 pct                              10
Parallel operations downgraded 25 to 50 pct                            1474
Parallel operations downgraded 1 to 25 pct                                9
6 rows selected.
SQL>Thanks.
Edited by: user523372 on Jun 18, 2010 7:43 AM

What was unclear in 'multipe disks'?
If all of those parallel query slaves are going to hit 1 single disk, you will get an IO bottleneck.
And performance problems are typically NOT resolved by enabling parallel execution.
It is not unlikely it will make things worse.
I was afraid you are a fan of silver bullets. It appears indeed you are.
Sybrand Bakker
Senior Oracle DBA

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
SQL Error: ORA-12801: error signaled in parallel query server P007.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.
Reason and Prerequisites
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.
 Note 963760 - 'ORA-20000: Insufficient privileges' for creating statistics
For Error -for SQL Error: ORA-01418: specified index does not exist
check note below-
Note 337830 - BW: ORA-1418 in system log
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.

Note 1003360 - BW fact tables: Deleting index from process chain terminates
If it relates your error it requires corrections for SP-12.
Hope it Helps
Chetan
@CP..

Apply causes ORA-12805: parallel query server died unexpectedly

Hi gurus,
I created an apply with a user-defined message handler for a queue. When a message is enqueued, the apply tries to do its work, but then is aborted because a fatal error has occurred: ORA-12805: parallel query server died unexpectedly.
Could anyone help me with this? I am desperate now.
Here is what comes from the log:
Dump file c:\oracle\product\10.2.0\admin\byzz10g\bdump\byzz10g_a002_640.trc
Fri Sep 22 09:15:05 2006
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Windows XP Version V5.1 Service Pack 2
CPU : 1 - type 586
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:405M/1014M, Ph+PgF:1795M/2442M, VA:1575M/2047M
Instance name: byzz10g
Redo thread mounted by this instance: 1
Oracle process number: 32
Windows thread id: 640, image: ORACLE.EXE (A002)
*** 2006-09-22 09:15:05.366
*** SERVICE NAME:(SYS$USERS) 2006-09-22 09:15:05.366
*** SESSION ID:(141.21) 2006-09-22 09:15:05.366
error 12805 in STREAMS process
ORA-12805: parallel query server died unexpectedly
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-12805: parallel query server died unexpectedly
Thank you very much!

Hi myora9i,
I saw similar report in MetaLink. (Bugid:3658975)
It was 9.2.0.5 on Solaris.
Unfortunately, this problem has left unsolved for 2 years due to luck of information to analyze the situation.
I couldn't get a detail of problem, but the document says "Apply process abort".
And error messages are same to yours. So I think your problem is related to the bug.
Just FYI
Regards,

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

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

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

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-12827 insufficient parallel query slaves available

Similar Messages

Maybe you are looking for