Queue exceed maximum capacity of '256' elements.

          Has anyone seen this one before??
          Thanks
          Thomas
          weblogic.utils.UnsyncCircularQueue$FullQueueException: Queue exceed maximum capacity
          of: '256' elements.
          weblogic.utils.UnsyncCircularQueue$FullQueueException:      of: '256' elements
          at weblogic.utils.UnsyncCircularQueue.expandQueue(UnsyncCircularQueue.java:72)
          at weblogic.utils.UnsyncCircularQueue.put(UnsyncCircularQueue.java:94)
          at weblogic.kernel.ExecuteThreadManager.execute(ExecuteThreadManager.java:343)
          at weblogic.kernel.Kernel.execute(Kernel.java:338)
          at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:304)
          at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:923)
          at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:844)
          at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:222)
          at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:794)
          at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:570)
          at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:681)
          at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:627)
          at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:123)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Hi,
          The queue in question here is not a JMS queue. Instead,
          this is the "execute queue" of jobs waiting to be
          serviced by a thread in its thread pool.
          I think the size of these queues is configurable on the
          thread pool. Note that if dead-lock is locking up threads
          and causing the problem,
          you will likely need to increase the number of threads
          or dedicate server-side resources to their own thread pools
          rather than (or in addition to) increasing the size
          of the execute queues. (A thread dump helps
          in diagnose dead-locks.)
          Likely this error is on a server side thread pool, so
          there should be warnings/error messages in the server logs
          that describe what is happening.
          Tom
          Thomas Kreig wrote:
          > Has anyone seen this one before??
          > Thanks
          > Thomas
          >
          > weblogic.utils.UnsyncCircularQueue$FullQueueException: Queue exceed maximum capacity
          > of: '256' elements.
          > weblogic.utils.UnsyncCircularQueue$FullQueueException:      of: '256' elements
          > at weblogic.utils.UnsyncCircularQueue.expandQueue(UnsyncCircularQueue.java:72)
          > at weblogic.utils.UnsyncCircularQueue.put(UnsyncCircularQueue.java:94)
          > at weblogic.kernel.ExecuteThreadManager.execute(ExecuteThreadManager.java:343)
          > at weblogic.kernel.Kernel.execute(Kernel.java:338)
          > at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:304)
          > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:923)
          > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:844)
          > at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:222)
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:794)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:570)
          > at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:681)
          > at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:627)
          > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:123)
          > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >

Similar Messages

Errors with Queue exceed maximum capacity of: '65536' elements

I faced this issue recently , where the messaging bridges from an external domain was not able to connect my my domain.
When i checked the logs i found one of the server with the below error.
####<Feb 28, 2011 7:31:23 PM GMT> <Warning> <RMI> <dyh75a03> <managed06_orneop02> <ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <
BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal.BasicServerRef@a - hostID: '4275655823338432757S:dywlms06-orneop02.neo.openreach.co
.uk:[61007,61007,-1,-1,61007,-1,-1,0,0]:dywlms01-orneop02.neo.openreach.co.uk:61002,dywlms02-orneop02.neo.openreach.co.uk:61003,dywlms03-orneop02.neo.openrea
ch.co.uk:61004,dywlms04-orneop02.neo.openreach.co.uk:61005,dywlms05-orneop02.neo.openreach.co.uk:61006,dywlms06-orneop02.neo.openreach.co.uk:61007,dywlms07-o
rneop02.neo.openreach.co.uk:61008,dywlms08-orneop02.neo.openreach.co.uk:61009,dywlms09-orneop02.neo.openreach.co.uk:61010:orneop02:managed06_orneop02', oid:
'10', implementation: 'weblogic.transaction.internal.CoordinatorImpl@f6ede1'
weblogic.utils.UnsyncCircularQueue$FullQueueException: Queue exceed maximum capacity of: '65536' elements.
weblogic.utils.UnsyncCircularQueue$FullQueueException: Queue exceed maximum capacity of: '65536' elements
at weblogic.utils.UnsyncCircularQueue.expandQueue(UnsyncCircularQueue.java:72)
at weblogic.utils.UnsyncCircularQueue.put(UnsyncCircularQueue.java:94)
at weblogic.kernel.ExecuteThreadManager.execute(ExecuteThreadManager.java:374)
at weblogic.kernel.Kernel.execute(Kernel.java:345)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:312)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1113)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1031)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:225)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:805)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:782)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:705)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:651)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:123)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
>
As a workaround , i had restart this server. After this bridges from ext domain was working.
Has any one come across this issue before.
Regards
Deepak

Found this issue again in one of the domains....the threads dumps is showing deadlocks.
Found one Java-level deadlock:
=============================
"ExecuteThread: '3' for queue: 'weblogic.kernel.Default'":
waiting to lock monitor 0868dea4 (object a4e99be8, a weblogic.transaction.internal.TransactionLoggerImpl$IOBuffer),
which is held by "ExecuteThread: '6' for queue: 'weblogic.kernel.Default'"
"ExecuteThread: '6' for queue: 'weblogic.kernel.Default'":
waiting to lock monitor 00255304 (object b23be050, a weblogic.transaction.internal.ServerTransactionImpl),
which is held by "ExecuteThread: '0' for queue: 'weblogic.kernel.Non-Blocking'"
"ExecuteThread: '0' for queue: 'weblogic.kernel.Non-Blocking'":
waiting to lock monitor 086677a4 (object a4e99c00, a weblogic.transaction.internal.TransactionLoggerImpl$IOBuffer),
which is held by "ExecuteThread: '3' for queue: 'weblogic.kernel.Default'"
Java stack information for the threads listed above:
===================================================
"ExecuteThread: '3' for queue: 'weblogic.kernel.Default'":
     at weblogic.transaction.internal.TransactionLoggerImpl$LogDisk.release(TransactionLoggerImpl.java:1323)
     - waiting to lock <a4e99be8> (a weblogic.transaction.internal.TransactionLoggerImpl$IOBuffer)
     - locked <a4e99c00> (a weblogic.transaction.internal.TransactionLoggerImpl$IOBuffer)
     at weblogic.transaction.internal.TransactionLoggerImpl.release(TransactionLoggerImpl.java:389)
     at weblogic.transaction.internal.ServerTransactionImpl.releaseLog(ServerTransactionImpl.java:2767)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.remove(ServerTransactionManagerImpl.java:1466)
     at weblogic.transaction.internal.ServerTransactionImpl.afterCommittedStateHousekeeping(ServerTransactionImpl.java:2645)
     at weblogic.transaction.internal.ServerTransactionImpl.setCommitted(ServerTransactionImpl.java:2669)
     at weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransactionImpl.java:1875)
     at weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransactionImpl.java:1163)
     at weblogic.transaction.internal.SubCoordinatorImpl.startCommit(SubCoordinatorImpl.java:274)
     at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
"ExecuteThread: '6' for queue: 'weblogic.kernel.Default'":
     at weblogic.transaction.internal.ServerTransactionImpl.onDisk(ServerTransactionImpl.java:836)
     - waiting to lock <b23be050> (a weblogic.transaction.internal.ServerTransactionImpl)
     at weblogic.transaction.internal.TransactionLoggerImpl$LogDisk.write(TransactionLoggerImpl.java:1252)
     - locked <a4e99be8> (a weblogic.transaction.internal.TransactionLoggerImpl$IOBuffer)
     - locked <a4e99bb8> (a weblogic.transaction.internal.TransactionLoggerImpl$LogDisk)
     at weblogic.transaction.internal.TransactionLoggerImpl.flushLog(TransactionLoggerImpl.java:614)
     at weblogic.transaction.internal.TransactionLoggerImpl.store(TransactionLoggerImpl.java:305)
     at weblogic.transaction.internal.ServerTransactionImpl.log(ServerTransactionImpl.java:1850)
     at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2118)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:259)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228)
     at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:303)
     at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1279)
     at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1190)
     at weblogic.jms.adapter.JMSBaseConnection$29.run(JMSBaseConnection.java:1989)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1985)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2686)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
"ExecuteThread: '0' for queue: 'weblogic.kernel.Non-Blocking'":
     at weblogic.transaction.internal.TransactionLoggerImpl$LogDisk.release(TransactionLoggerImpl.java:1322)
     - waiting to lock <a4e99c00> (a weblogic.transaction.internal.TransactionLoggerImpl$IOBuffer)
     at weblogic.transaction.internal.TransactionLoggerImpl.release(TransactionLoggerImpl.java:389)
     at weblogic.transaction.internal.ServerTransactionImpl.releaseLog(ServerTransactionImpl.java:2767)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.remove(ServerTransactionManagerImpl.java:1466)
     at weblogic.transaction.internal.ServerTransactionImpl.setRolledBack(ServerTransactionImpl.java:2597)
     at weblogic.transaction.internal.ServerTransactionImpl.ackRollback(ServerTransactionImpl.java:1093)
     - locked <b23be050> (a weblogic.transaction.internal.ServerTransactionImpl)
     at weblogic.transaction.internal.CoordinatorImpl.ackRollback(CoordinatorImpl.java:298)
     at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Found 1 deadlock.

UnsyncCircularQueue$FullQ Queue exceed maximum capacity of: '65536' element

dear friends:
Does anyone knows the problem like this <BEA-002911> <WorkManager ClusterMessaging failed to schedule a request due to weblogic.utils.UnsyncCircularQueue$FullQueueException: Queue exceed maximum capacity of: '65536' elements
weblogic.utils.UnsyncCircularQueue$FullQueueException: Queue exceed maximum capacity of: '65536' elements
why this happend and how to solve it?
thanks a lot!

Hi,
Weblogic has a maximum storage for Pending Request queue configured at 65536. At this point, it will stop accepting incoming request to your Server Socket port.
This means that your Weblogic server / JVM very likely has depleted its internal Thread Pool triggering Weblogic to start queuing incoming requests; eventually reaching its maximum capacity.
From a resolution perspective, you will need to investigate the root cause, Thread Dump generation and analysis will be required in your case.
Please generate a JVM Thread Dump (kill -3 <pid> for UNIX OS) and share detail on Thread contention / problem pattern.
Thanks.
P-H
http://javaeesupportpatterns.blogspot.com/

BEA-000802 : Queue exceed maximum capacity of: '65536' elements.

Hi,
I am getting following error in my weblogic server. Its version is 10.3.3.0
And after some time, server is not showing its state. Usually if the server is running properly, its state is "OK". But after the following error messages, my server is not showing any state and applications are not running.
####<Nov 11, 2010 5:18:50 AM GMT+05:30> <Error> <Kernel> <APP1> <Server1> <[ACTIVE] ExecuteThread: '360' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1289432930650> <BEA-000802> <ExecuteRequest failed
weblogic.utils.UnsyncCircularQueue$FullQueueException: Queue exceed maximum capacity of: '65536' elements.
weblogic.utils.UnsyncCircularQueue$FullQueueException: Queue exceed maximum capacity of: '65536' elements
     at weblogic.utils.UnsyncCircularQueue$FullQueueException.<init>(UnsyncCircularQueue.java:147)
     at weblogic.utils.UnsyncCircularQueue$FullQueueException.<init>(UnsyncCircularQueue.java:144)
     at weblogic.utils.UnsyncCircularQueue.expandQueue(UnsyncCircularQueue.java:71)
     at weblogic.utils.UnsyncCircularQueue.put(UnsyncCircularQueue.java:94)
     at weblogic.rjvm.MsgAbbrevJVMConnection$WritingState.sendNow(MsgAbbrevJVMConnection.java:511)
     at weblogic.rjvm.MsgAbbrevJVMConnection.canSendMsg(MsgAbbrevJVMConnection.java)
     at weblogic.rjvm.MsgAbbrevJVMConnection.sendMsg(MsgAbbrevJVMConnection.java:181)
     at weblogic.rjvm.MsgAbbrevJVMConnection.sendMsg(MsgAbbrevJVMConnection.java:142)
     at weblogic.rjvm.ConnectionManager.sendMsg(ConnectionManager.java:593)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:901)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendOneWay(MsgAbbrevOutputStream.java:400)
     at weblogic.rjvm.BasicOutboundRequest.sendOneWay(BasicOutboundRequest.java:105)
     at weblogic.rmi.internal.BasicRemoteRef.sendOneway(BasicRemoteRef.java:271)
     at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:214)
     at weblogic.management.logging.DomainLogHandlerImpl_1033_WLStub.publishLogEntries(Unknown Source)
     at weblogic.logging.DomainLogBroadcasterClient$2.run(DomainLogBroadcasterClient.java:209)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
And even I am getting out of memory error warning.
####<Nov 11, 2010 7:34:46 AM GMT+05:30> <Critical> <Health> <APP1> <Server1> <weblogic.GCMonitor> <<anonymous>> <> <> <1289441086135> <BEA-310003> <Free memory in the server is 2,953,904 bytes. There is danger of OutOfMemoryError>
My server arguments are
-XX:PermSize=256m -XX:MaxPermSize=256m -Xms1024M -Xmx2048M
Please tell me where the things are going wrong.

This wls instance can't afford huge requests.
See the following error
####<Nov 11, 2010 5:18:50 AM GMT+05:30> <Error> <Kernel> <APP1> <Server1> <[ACTIVE] ExecuteThread: '360' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>>
This ExecuteThread number is 360th.
I think your instance is already too busy.
I guess OOME is second issue.
If i have to solve this problem, i consider several follow things.
1. Check the total requests.
     - I guess we need to sizing of wls instances.
2. Extend wls instance count.
     - Under 100 ExecuteThread per wls instance
3. Find long term requests, especially STUCK thread.
     - Tuning that requests under JTA timeout.
4. Set the -Xms and -Xmx as same value.
     - For performance.
I hope this will be helpful to you

ORA-30951: Element or attribute at Xpath /AC//Doc[@] exceeds maximum length

Hi All,
I am trying to load the XML Files into a Table using the SQL Loader and i am getting the Error
Record 1: Rejected - Error on table COMMONASSETCATALOG.
ORA-30951: Element or attribute at Xpath /AC/T[1]/T[1]/T[1]/T[1]/T[1]/Doc[@] exceeds maximum length
The <Doc> Element which is child of the <T> contains an XML Schema inside it..
The Doc Element is declared in Schema as
<xs:complexType name="AsDocType">
          <xs:annotation>
               <xs:documentation>A (Doc)ument, a container for any type of file</xs:documentation>
          </xs:annotation>
          <xs:sequence minOccurs="0" maxOccurs="unbounded">
               <xs:any namespace="##any" processContents="lax"/>
          </xs:sequence>
          <xs:attributeGroup ref="AsDocAtts"/>
     </xs:complexType>
The Size of the XML Content that <Doc> Node has is around 34Kb.
Could you pls let me know how to resolve this..
Thanks
Sateesh

Hi All,
I am trying to load the XML Files into a Table using the SQL Loader and i am getting the Error
Record 1: Rejected - Error on table COMMONASSETCATALOG.
ORA-30951: Element or attribute at Xpath /AC/T[1]/T[1]/T[1]/T[1]/T[1]/Doc[@] exceeds maximum length
The <Doc> Element which is child of the <T> contains an XML Schema inside it..
The Doc Element is declared in Schema as
<xs:complexType name="AsDocType">
          <xs:annotation>
               <xs:documentation>A (Doc)ument, a container for any type of file</xs:documentation>
          </xs:annotation>
          <xs:sequence minOccurs="0" maxOccurs="unbounded">
               <xs:any namespace="##any" processContents="lax"/>
          </xs:sequence>
          <xs:attributeGroup ref="AsDocAtts"/>
     </xs:complexType>
The Size of the XML Content that <Doc> Node has is around 34Kb.
Could you pls let me know how to resolve this..
Thanks
Sateesh

Lax validation errors on schema import ('version' exceeds maximum length)

I have a schema as per below. I'm trying to import it into Oracle 10.2.0.2.0. However, I'm getting the following lax validation error:
Error loading ora_business_rule.xsd:ORA-30951: Element or attribute at Xpath /schema[@version] exceeds maximum length
I can fix it by modifying the attribute and shortening it but I'd like to know why it's occuring. Insofar as I can tell there is no imposed limit on the size of schema attributes according to the W3C standard. Which then makes me wonder: does Oracle impose limits on the length of all attributes or is this specific to 'version' ? If there is a limit, what is the upper bound (in bytes) ? Where is this documented?
Cheers,
Daniel
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:br="http://foo.com/BusinessRule_PSG_V001" targetNamespace="http://foo.com/BusinessRule_PSG_V001" elementFormDefault="qualified" attributeFormDefault="unqualified" version="last committed on $LastChangedDate: 2006-05-19 11:00:52 +1000 (Fri, 19 May 2006) $">
     <xs:element name="edit">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="edit_id" type="xs:string"/>
                    <xs:element ref="br:business_rule"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="derivation">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="derivation_id" type="xs:string"/>
                    <xs:element ref="br:derivation_type"/>
                    <xs:element ref="br:business_rule"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="derivation_type">
          <xs:simpleType>
               <xs:restriction base="xs:NMTOKENS">
                    <xs:enumeration value="complex"/>
                    <xs:enumeration value="format"/>
                    <xs:enumeration value="formula"/>
                    <xs:enumeration value="recode"/>
                    <xs:enumeration value="SAS code"/>
                    <xs:enumeration value="transfer"/>
                    <xs:enumeration value="count"/>
                    <xs:enumeration value="sum"/>
                    <xs:enumeration value="max"/>
                    <xs:enumeration value="min"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="business_rule"></xs:element>
</xs:schema>

Opps -- Sorry it's a decision we took when looking at Version
When we registered the Schema for Schemas during XDB bootstrap the Version attriubte was mapped to varchar2(12).
SQL> desc xdb.xdb$schema_T
Name                                      Null?    Type
SCHEMA_URL                                         VARCHAR2(700)
TARGET_NAMESPACE                                   VARCHAR2(2000)
VERSION                                            VARCHAR2(12)
NUM_PROPS                                          NUMBER(38)
FINAL_DEFAULT                                      XDB.XDB$DERIVATIONCHOICE
BLOCK_DEFAULT                                      XDB.XDB$DERIVATIONCHOICE
ELEMENT_FORM_DFLT                                  XDB.XDB$FORMCHOICE
ATTRIBUTE_FORM_DFLT                                XDB.XDB$FORMCHOICE
ELEMENTS                                           XDB.XDB$XMLTYPE_REF_LIST_T
SIMPLE_TYPE                                        XDB.XDB$XMLTYPE_REF_LIST_T
COMPLEX_TYPES                                      XDB.XDB$XMLTYPE_REF_LIST_T
ATTRIBUTES                                         XDB.XDB$XMLTYPE_REF_LIST_T
IMPORTS                                            XDB.XDB$IMPORT_LIST_T
INCLUDES                                           XDB.XDB$INCLUDE_LIST_T
FLAGS                                              RAW(4)
SYS_XDBPD$                                         XDB.XDB$RAW_LIST_T
ANNOTATIONS                                        XDB.XDB$ANNOTATION_LIST_T
MAP_TO_NCHAR                                       RAW(1)
MAP_TO_LOB                                         RAW(1)
GROUPS                                             XDB.XDB$XMLTYPE_REF_LIST_T
ATTRGROUPS                                         XDB.XDB$XMLTYPE_REF_LIST_T
ID                                                 VARCHAR2(256)
VARRAY_AS_TAB                                      RAW(1)
SCHEMA_OWNER                                       VARCHAR2(30)
NOTATIONS                                          XDB.XDB$NOTATION_LIST_T
LANG                                               VARCHAR2(4000)
SQL>

XML data value exceeds maximum length - ORA-30951

Hello,
I am receiving ORA-30951: Element or attribute at Xpath /dataroot/Respondent[1]/Response[3]/Value exceeds maximum length error during the XML load.
I have registered the schema and it works fine when the Value is less than 64k but fails if its greater. I tried changing the type of Value to type="xsd:base64Binary" xdb:maintainDOM="false" xdb:SQLName="LOB_DATA" xdb:SQLType="BLOB" but then I get ORA-00932: inconsistent datatypes error.
Can someone please let me know what I am doing wrong or is there a way I can load more than 64k length elements on 10g?
Thanks
Here is my schema.
var SCHEMAURL varchar2(256)
var XMLSCHEMA CLOB
set define off
begin
:SCHEMAURL := 'http://xmlns.example.com/Svy_Resp.xsd';
:XMLSCHEMA := '<?xml version="1.0"; encoding="utf-16"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" version="1.0"; xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" xdb:storeVarrayAsTable="true">
<xsd:element name="dataroot" xdb:defaultTable="SVY_RESP_XML_SCHEMA" type="datarootType" />
<xsd:complexType name="datarootType" xdb:maintainDOM="false"
xdb:SQLType="Dataroot_T">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="Respondent" type="RespondentType" />
</xsd:sequence>
<xsd:attribute name="generated" type="xsd:dateTime" />
</xsd:complexType>
<xsd:complexType name="RespondentType" xdb:maintainDOM="false" xdb:SQLType="Respondent_Type">
<xsd:sequence>
<xsd:element name="RespondentID" type="xsd:int" />
<xsd:element name="KsID" type="xsd:int" />
<xsd:element name="email" type="xsd:string" />
<xsd:element name="SyID" type="xsd:int" />
<xsd:element name="KSuID" type="xsd:int" />
<xsd:element name="Completed" type="xsd:int" />
<xsd:element name="SubmitDateTime" type="xsd:dateTime" />
<xsd:element maxOccurs="unbounded" name="Response" type="ResponseType" />
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ResponseType" xdb:maintainDOM="false" xdb:SQLType="Response_Type">
<xsd:sequence>
<xsd:element name="ResponseID" type="xsd:int" />
<xsd:element name="RespondentID" type="xsd:int" />
<xsd:element name="CID" type="xsd:int" />
<xsd:element name="AID" type="xsd:int" />
<xsd:element name="Value" type="xsd:string"/>
<xsd:element name="QID" type="xsd:int" />
<xsd:element name="SID" type="xsd:int" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>';
end;
/

Thanks for the quick response. I am not able to modify the source file, but will it be possible to set the value to NULL if it exceeds the max length instead of failure?
Thanks

Bex Query: Too many table names in the query The maximum allowable is 256

Hi Experts,
I need your help, Im working on a Query using a multiprovider of 2 datastores, I need to work with cells to assign specific acconts values to specific rows and columns, so I was creating a Structure with elements from a Hierarchy, but I get this error when I'm half way of the structure:
"Too many table names in the query. The maximum allowable is 256.Incorrect syntax near ')'.Incorrect syntax near 'O1'."
Any idea what is happening? is ti possible to fix it? do I need to ask for a modification of my Infoproviders? Some one told me is possible to combine 2 querys, is it true?
Thanks a lot for your time and pacience.

Hi,
The maximum allowable limit is 256 holds true. It is the max no. of characteristics and key figures that can be used in the column side. While creating a structure, you create key figures (restricted or calculated) and formulas etc.. The objects that you use to create these should not be more than 256.
http://help.sap.com/saphelp_nw70/helpdata/EN/4d/e2bebb41da1d42917100471b364efa/frameset.htm
Not sure if combination of 2 query's is possible. You can use RRI. Or have a woorkbook with 2 queries.
Hope it helps.

SQL Loader - data exceeds maximum length

I am having an issue with SQL Loader falsely reporting that a column is too long in a CSV upload file. The offending column, Notes, is defined in the staging table as VARCHAR2(1000). The text in the Notes column in the upload file for the record that is being rejected is only 237 characters long. I examined the raw data file with a hex editor and there are no special cahracters embedded in the column. The CSV upload was recreated but the false error remains.
Any ideas what to check? Any suggestion appreciated.
Here are the pertinent files.
Control File:LOAD DATA
   INFILE 'Mfield_Upl.dat'
   BADFILE 'Mfield_Upl.bad'
   TRUNCATE
   INTO TABLE Mfield_UPL_Staging
   FIELDS TERMINATED BY ',' optionally enclosed by '"'
     ControlNo CHAR,
     PatientID CHAR,
     CollectDate DATE "MM/DD/YYYY",
     TestDate DATE "MM/DD/YYYY",
     AnalyteDesc CHAR,
     Results CHAR,
     HiLoFlag CHAR,
     LoRange CHAR,
     HiRange CHAR,
     UnitOfMeas CHAR,
     Comments CHAR,
     Notes CHAR,
     ClinicalEvent CHAR,
     OwnerLName CHAR,
     OwnerFName CHAR,
     PetName CHAR,
     AssecNo CHAR,
     SpecimenID CHAR
{code}
Staging Table:{code}
CREATE TABLE Mfield_UPL_Staging
    ControlNo      VARCHAR2(20),
    PatientID      VARCHAR2(9),
    CollectDate    DATE,
    TestDate       DATE,
    AnalyteDesc    VARCHAR2(100),
    Results        VARCHAR2(100),
    HiLoFlag       CHAR(10),
    LoRange        VARCHAR2(15),
    HIRange        VARCHAR2(15),
    UnitOfMeas     VARCHAR2(25),
    Comments       VARCHAR2(100),
    Notes          VARCHAR2(1000),
    ClinicalEvent VARCHAR2(20),
    OwnerLName     VARCHAR(50),
    OwnerFName     VARCHAR(50),
    PetName        VARCHAR(50),
    AssecNo        NUMBER(10),
    SpecimenID     NUMBER(10)
{Code}
Error Log File:{code}
SQL*Loader: Release 9.2.0.1.0 - Production on Wed Aug 11 08:22:58 2010
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Control File:   Mfield_UPL_CSV.ctl
Data File:      Mfield_UPL.dat
Bad File:     Mfield_Upl.bad
Discard File: none specified
(Allow all discards)
Number to load: ALL
Number to skip: 0
Errors allowed: 50
Bind array:     64 rows, maximum of 256000 bytes
Continuation:    none specified
Path used:      Conventional
Table MFIELD_UPL_STAGING, loaded from every logical record.
Insert option in effect for this table: TRUNCATE
   Column Name                  Position   Len Term Encl Datatype
CONTROLNO                           FIRST     *   , O(") CHARACTER
PATIENTID                            NEXT     *   , O(") CHARACTER
COLLECTDATE                          NEXT     *   , O(") DATE MM/DD/YYYY
TESTDATE                             NEXT     *   , O(") DATE MM/DD/YYYY
ANALYTEDESC                          NEXT     *   , O(") CHARACTER
RESULTS                              NEXT     *   , O(") CHARACTER
HILOFLAG                             NEXT     *   , O(") CHARACTER
LORANGE                              NEXT     *   , O(") CHARACTER
HIRANGE                              NEXT     *   , O(") CHARACTER
UNITOFMEAS                           NEXT     *   , O(") CHARACTER
COMMENTS                             NEXT     *   , O(") CHARACTER
NOTES                                NEXT     *   , O(") CHARACTER
CLINICALEVENT                        NEXT     *   , O(") CHARACTER
OWNERLNAME                           NEXT     *   , O(") CHARACTER
OWNERFNAME                           NEXT     *   , O(") CHARACTER
PETNAME                              NEXT     *   , O(") CHARACTER
ASSECNO                              NEXT     *   , O(") CHARACTER
SPECIMENID                           NEXT     *   , O(") CHARACTER
Record 1042: Rejected - Error on table MFIELD_UPL_STAGING, column NOTES.
Field in data file exceeds maximum length
Table MFIELD_UPL_STAGING:
3777 Rows successfully loaded.
1 Row not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.
{code}

Try:
-- Etc ...
Notes CHAR(1000),
-- Etc ...SQL*Loader limits string buffer to 256 unless specified different.
:p

ORA-30951: ...exceeds maximum length

Oracle Database 10g Release 10.2.0.1.0 - Production
I am new to XML and having a problem importing data using the XML Repository. I have annotated the schema and validated it using XML Spy. I am able to register the schema w/o errors. I am now working through the issues as they occur during the insertion of xml documents. Thes section below is giving me an error (bottom) that the data exceeds the maximum length. The "DATA" in the xml doc is a pdf file that has been converted to characters by some method. The size element has a data value of 5008. Seems to be too long for a varchar2. I tried RAW, CLOB, BLOB. I was pretty sure they wouldn't work and they didn't. I get an error that the xml/xdb types are incompatible.
How can I modify the schema to get this element to load?
Is it possible to tell oracle to ignore an element so I can eliminate those that are not critical? This would be very helpful.
Thanks!
Schema -
<xs:element name="NpdbReportList" minOccurs="0">
<xs:complexType>
<xs:sequence maxOccurs="unbounded">
<xs:element name="NpdbReport" minOccurs="0">
<xs:complexType>
<xs:all minOccurs="0">
<xs:element name="DCN" minOccurs="0"/>
<xs:element name="DateReport" type="Date" minOccurs="0"/>
<xs:element name="ReportType" type="IdRef" minOccurs="0"/>
<xs:element ref="LOB" minOccurs="0"/>
</xs:all>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="LOB" xdb:SQLType="LOB_T"xdb:maintainDOM="false">
<xs:all>
     <xs:element name="Type" type="IdRef"/>
     <xs:element name="Size"/>
     <xs:element name="Data" xdb:maintainDOM="false" xdb:SQLName="LOB_DATA" xdb:SQLType="VARCHAR2"/>
</xs:all>
</xs:complexType>
ftp> mput *
mput Smyth_Steven_1386367.XML? y
227 Entering Passive Mode (127,0,0,1,83,221)
150 ASCII Data Connection
550- Error Response
ORA-30951: Element or attribute at Xpath /Provider/NpdbReportList/NpdbReport[1]/LOB/Data exceeds maximum length
550 End Error Response
28706 bytes sent in 0.014 seconds (1.9e+03 Kbytes/s)
ftp>

Thanks for your time Marco.
Here is the header:
<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:storeVarrayAsTable="true" xdb:mapStringToNCHAR="true" xdb:mapUnboundedStringToLob="true">
I made the following change -
<xs:element name="Data" xdb:maintainDOM="false" xdb:SQLName="LOB_DATA" xdb:SQLType="CLOB"/>
I received this error -
ORA-31094: incompatible SQL type "CLOB" for attribute or element "Data"
ORA-06512: at "XML_TEST.XML_TEST_SCHEMA_REGISTER", line 48
I did a little more testing after the first post. I used the same type as an element that is defining image data.
<xs:element name="Data" type="xs:base64Binary" xdb:maintainDOM="false" xdb:SQLName="LOB_DATA" xdb:SQLType="BLOB"/>
While this did register and I was able to load a record, I am guessing that this will render the data for this element usless but at least the record loads. I'll still need to resolve this issue as the .pdf data is important.
Thanks
Joe

If Dimension exceeds maximum size then what will we do???

Hi Experts,
If Dimension exceeds maximum size then what will we do???
My dought was how to increase the dimension size in SSAS 2008 R2???
i am using SQL SERVER 2008 R2.
i had faced this question in one of the interview.so,Could you explain with an example.
Best Regards,
sirikumar

You can't exceed the maximum, else you get error. The maximum is a huge number:
Object
Maximum sizes/numbers
Databases in an instance
2^31-1 = 2,147,483,647
Dimensions in a database
2^31-1 = 2,147,483,647
Attributes in a dimension
2^31-1 = 2,147,483,647
Members in a dimension attribute
2^31-1 = 2,147,483,647
User-defined hierarchies in a dimension
2^31-1 = 2,147,483,647
Levels in a user-defined hierarchy
2^31-1 = 2,147,483,647
Cubes in a database
2^31-1 = 2,147,483,647
LINK:
Maximum Capacity Specifications (Analysis Services)
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Reached maximum capacity of pool "eis/PRAdapterCF", making "0" new resource

Hi All,
We configured weblogic with pega. I am getting below error. Any idea ?
I enabled test conection reserve. and increased test frequency 900
####<Nov 13, 2012 1:25:46 PM CST> <Info> <Common> <test4> <PEGA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1352834746443> <BEA-000627> <Reached maximum capacity of pool "eis/PRAdapterCF", making "0" new resource instances instead of "1".>
####<Nov 13, 2012 1:25:46 PM CST> <Info> <Common> <test4> <PEGA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1352834746444> <BEA-000628> <Created "1" resources for pool "eis/PRAdapterCF", out of which "1" are available and "0" are unavailable.>
####<Nov 13, 2012 1:25:46 PM CST> <Info> <Common> <test4> <PEGA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1352834746749> <BEA-000627> <Reached maximum capacity of pool "eis/PRAdapterCF", making "0" new resource instances instead of "1".>
####<Nov 13, 2012 1:25:46 PM CST> <Info> <Common> <test4> <PEGA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1352834746750> <BEA-000628> <Created "1" resources for pool "eis/PRAdapterCF", out of which "1" are available and "0" are unavailable.>
####<Nov 13, 2012 1:25:46 PM CST> <Info> <Common> <test4> <PEGA> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1352834746837> <BEA-Thanks,
Edited by: 834617 on Nov 13, 2012 11:32 AM

Hi Kal,
we already enabled Inactive connection timeout is 900 still its throughing the info.
Thanks,
Edited by: 834617 on Nov 28, 2012 10:39 AM

What is Maximum capacity of InfoCube?

Hi All,
Can anybody tell me the What is Maximum capacity of InfoCube?
Regards,
Kiran

Hi Kiran,
Each keyfiure occupies 10 Bytes of memory
Each Char occupies 6 Bytes of memory
So in an Infocube the maximum number of fields are 256 out of which 233 keyfigure, 16 Dimesions and 6 special char.
So The maximum capacity of a cube
= 233(Key figure)10 + 16(Characteristics)6 + 6(Sp.Char)*6
Hope this will be helpful
Thanks
Rajesh

Field in data file exceeds maximum length

Hi,
I am trying to run the following SQL*Loader control job on my Oracle 11gR2 . Running the SQL*Loader control job results in the ‘Field in data file exceeds maximum length’ error message. Below, I am listing the control file.Please Suggest. Thanks
It's giving me an error when I run SQL Loader on it,
Record 61: Rejected - Error on table RMS_TABLE, column GEOM.SDO_POINT.X.
Field in data file exceeds maximum length.
Here is my SQL Loader Control file,
LOAD DATA
INFILE *
TRUNCATE
CONTINUEIF NEXT(1:1) = '#'
INTO TABLE RMS_TABLE
FIELDS TERMINATED BY '|'
TRAILING NULLCOLS (
   Status NULLIF Status = BLANKS,
   Score,
   Match_type NULLIF Match_type = BLANKS,
   Match_addr NULLIF Match_addr = BLANKS,
   Side NULLIF Side = BLANKS,
   User_fld NULLIF User_fld = BLANKS,
   Addr_type NULLIF Addr_type = BLANKS,
   ARC_Street NULLIF ARC_Street = BLANKS,
   ARC_City NULLIF ARC_City = BLANKS,
   ARC_State NULLIF ARC_State = BLANKS,
   ARC_ZIP NULLIF ARC_ZIP = BLANKS,
   INCIDENT_N NULLIF INCIDENT_N = BLANKS,
   CDATE NULLIF CDATE = BLANKS,
   CTIME NULLIF CTIME = BLANKS,
   DISTRICT NULLIF DISTRICT = BLANKS,
LOCATION
NULLIF LOCATION = BLANKS,
   MAPLOCATIO
NULLIF MAPLOCATIO = BLANKS,
   LOCATION_T
NULLIF LOCATION_T = BLANKS,
   DAYCODE
NULLIF DAYCODE = BLANKS,
   CAUSE
NULLIF CAUSE = BLANKS,
   GEOM COLUMN OBJECT
     SDO_GTYPE       INTEGER EXTERNAL,
     SDO_POINT COLUMN OBJECT
       (X            FLOAT EXTERNAL,
        Y            FLOAT EXTERNAL)
CREATE TABLE RMS_TABLE (
Status VARCHAR2(1),
Score NUMBER,
Match_type VARCHAR2(2),
Match_addr VARCHAR2(120),
Side VARCHAR2(1),
User_fld VARCHAR2(120),
Addr_type VARCHAR2(20),
ARC_Street VARCHAR2(100),
ARC_City VARCHAR2(40),
ARC_State VARCHAR2(20),
ARC_ZIP VARCHAR2(10),
INCIDENT_N VARCHAR2(9),
CDATE VARCHAR2(10),
CTIME VARCHAR2(8),
DISTRICT VARCHAR2(4),
LOCATION VARCHAR2(128),
MAPLOCATIO VARCHAR2(100),
LOCATION_T VARCHAR2(42),
DAYCODE VARCHAR2(1),
CAUSE VARCHAR2(17),
GEOM MDSYS.SDO_GEOMETRY);

Hi,
Looks like you have a problem with record 61 in your data file. Can you please post it in reply.
Regards
Ivan

ORA-01044: size of buffer bound to variable exceeds maximum

Hello Oracle Gurus,
I have a tricky problem.
I have a stored procedure which has to retun more than 100,000 records. In my stored procedure, I have "TABLE OF VARCHAR2(512) INDEX BY BINARY_INTEGER". It fails when I try to get 80,000 records.
I get an error "ORA-01044: size 40960000 of buffer bound to variable exceeds maximum 33554432"
A simple calculation shows that 512*80000=40960000.
Oracle help suggests to reduce buffer size (i.e., number of records being returned or size of variable).
But, reducing the number of records returned or reducing the size of variable is not possible because of our product design constraints.
Are there any other options like changing some database startup parameters to solve this problem?
Thanks,
Sridhar

We are migrating an application running on Oracle 8i to 9i and found the same problem with some of the stored procedures.
Our setup:
+ Oracle 9.2.0.3.0
+ VB6 Application using OLEDB for Oracle ...
+ MDAC 2.8 msdaora.dll - 2.80.1022.0 (srv03_rtm.030324-2048)
I am calling a stored procedure from VB like this one:
{? = call trev.p_planung.GET_ALL_KONTEN(?,?,{resultset 3611, l_konto_id, l_name,l_ro_id, l_beschreibung, l_typ, l_plg_id})}
If setting the parameter "resultset" beyond a certain limit, I will eventually get this ORA-01044 error. This even happens, if the returned number of records is smaller than what supplied in the resultset parameter (I manually set the "resultset" param in the stored procedure string). E.g.:
resultset = 1000 -> ORA-06513: PL/SQL: Index der PL/SQL-Tabelle ungÃ¼ltig fÃ¼r Language-Array vom Host
resultset = 2000 -> OK (actual return: 1043 Recordsets)
resultset = 3000 -> ORA-01044: GrÃ¶Ãe 6000000 des Puffers fÃ¼r Variable Ã¼berschreitet HÃ¶chstwert von 4194304
resultset = 3500 -> ORA-01044: GrÃ¶Ãe 7000000 des Puffers fÃ¼r Variable Ã¼berschreitet HÃ¶chstwert von 4194304
... therefore one record is calculated here 7000000/3500=2000 bytes.
In Oracle 8i we never had this problem. As this is a huge application using a lot stored procedures, changing all "select" stored procedures to "get data by chunks" (suggestet in some forum threads in OTN) ist not an option.
Interesting: I can call the stored procedure above with the same parameters as given in VB from e.g. Quest SQL Navigator or sql plus successfully and retrieve all data!
Is there any other known solution to this problem in Oracle 9i? Is it possible to increase the maximum buffer size (Oracle documentation: ORA-01044 ... Action: Reduce the buffer size.)? What buffer size is meant here - which part in the communication chain supplies this buffer?
Any help highly appreciated!
Sincerely,
Sven Bombach

Queue exceed maximum capacity of '256' elements.

Similar Messages

Maybe you are looking for