PL/SQL Parser engine

Hi,
I am developing a logging framework, where applications which are initiating PL/SQL transactions also log the same using our framework. The reason being, the application owner can then analyze data from these logs. I was wondering whether there is something in existence like the "General SQL Parser" for a linux based c++ component, so that we can parse the PL/SQL blocks and represent the data in a certain format.
Are there any ORACLE libraries that I can use, which would work with PYTHON or any other scripting languages and parse the PL/SQLs albeit out of the scope of the ORACLE DB itself.
Do let me know,
cheers,
jags

Our logging framework is a generic c++ framework, where applications have a 2 stage approach
1) Execute the SQL transaction to their DB host.
2) The same SQL transaction is then logged to our framework (non DB), we then generate reports on these SQL transactions.
We are already handling parsing the log data for the SQL commands but need something for the PL/SQL blocks.

Similar Messages

  • How the SQL Query Parsing is processing inside SQL/PLSQL engine?

    Hi all,
    Can you explain how the SQL Query Parsing is processing inside SQL/PLSQL engine?
    Thanks,
    Sankar

    Sankar,
    Oracle Database concepts - Chapter 24..
    You will find the explanation required under the heading parsing.
    http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14220/sqlplsql.htm

  • Performance degradation in pl/sql parsing

    We are trying to use xml pl/sql parser and noticed performance degradation as we run multiple times. We zeroed into the following clause:
    doc := xmlparser.getDocument(p);
    The first time the procedure is run the elapsed time at sqlplus is something like .45sec, but as we run repeatedly in the same session the elapsed time keeps on increasing by .02 seconds. If we log out and start fresh, we start again from .45sec.
    We noticed similar degradation with
    p := xmlparser.newParser;
    but we got around by making the 'p' variable as package variable, initializing it once and using the same for all invocations.
    Any suggestions?
    Thank you.

    Can I enhance the PL/SQL code for better performance ? Probably you can enhance it.
    or, is this OK to take so long to process these many rows? It should take a few minutes, not several hours.
    But please provide some more details like your database version etc.
    I suggest to TRACE the session that executes the PL/SQL code, with WAIT events, so you'll see where and on what time is spent, you'll identify your 'problem statements very quickly' (after you or your DBA have TKPROF'ed the trace file).
    SQL> alter session set events '10046 trace name context forever, level 12';
    SQL> execute your PL/SQL code here
    SQL> exitWill give you a .trc file in your udump directory on the server.
    http://www.oracle-base.com/articles/10g/SQLTrace10046TrcsessAndTkprof10g.php
    Also this informative thread can give you more ideas:
    HOW TO: Post a SQL statement tuning request - template posting
    as well as doing a search on 10046 at AskTom, http://asktom.oracle.com will give you more examples.
    and reading Oracle's Performance Tuning Guide: http://www.oracle.com/pls/db102/to_toc?pathname=server.102%2Fb14211%2Ftoc.htm&remark=portal+%28Getting+Started%29

  • Validating XML with PL/SQL parser

    How can i validate a xml that is on a buffer with the grammar
    stored in a BLOB column of o table? I'm using PL/SQL parser and
    i can parse it correctly but i don't know how can i validate it
    because my grammar is stored in DB.
    null

    Ana Lucia (guest) wrote:
    : How can i validate a xml that is on a buffer with the grammar
    : stored in a BLOB column of o table? I'm using PL/SQL parser
    and
    : i can parse it correctly but i don't know how can i validate
    it
    : because my grammar is stored in DB.
    You can't currently but this will be available in our next
    release.
    Oracle XML Team
    http://technet.oracle.com
    Oracle Technology Network
    null

  • Logging errors in PL/SQL Parser

    Using PL/SQL Parser, is it possible to obtain the parsing errors
    output in other place than a file (ref: setErrorLog function)?
    as varchar variables or kind?
    null

    M Leclair (guest) wrote:
    : Using PL/SQL Parser, is it possible to obtain the parsing
    errors
    : output in other place than a file (ref: setErrorLog function)?
    : as varchar variables or kind?
    It is not possible at this time. It has been filed as an
    enhancement request.
    Oracle XML Team
    http://technet.oracle.com
    Oracle Technology Network
    null

  • Does PL/SQL Parser Validate?

    Just wondering if the PL/SQL parser can parse in validation mode?
    I think I remember reading that the PL/SQL parser is a non-validating parser only but I didn't know if this changed.
    Thanks for you help

    I am also experiencing problems with the setDocumentType
    This is my code
    p := xmlparser.newParser;
    xmlparser.parseBuffer(p,'<My_Data/>');
    doc := xmlparser.getDocument(p);
    docNode := xmldom.makeNode(doc);
    xmldom.setVersion(doc, '1.0');
    OuterNode := xmldom.getLastChild(docNode);
    --Get DTD to parse against
    xmlparser.setValidationMode(p,TRUE);
    xmlparser.parseDTD(p,'c:\temp\v109.dtd','My_Data');
    --Set DTD to validate against
    docType := xmlparser.getDoctype(p);
    xmlparser.setDoctype(p,docType);
    xmlparser.freeParser(p);
    The problem I am having is that the output now looks like this
    <?xml version="1.0" encoding="UTF-8"?>
    <My_Data>
    </My_Data>
    <!DOCTYPE My_Data SYSTEM "file:/c:/temp/v109.dtd">
    The xmlparser.parseDTD requires as the third parameter the root element so the !DOCTYPE field comes after the root element and not before as required.
    Hope this code helps a bit and if you solve the problem please let me know
    Owen
    null

  • PL/SQL parser creation

    Hi,
    I have to create a parser for PL/SQL 8i.
    Any help on what to start with would be very helpful.
    I hope to use the EBNF rules for the parsing. Am I in the right direction?
    Are there any open source code for PL/SQL parser ?
    Thanks & Regards
    Aswin Asokan

    Hi,
    I have to create a parser for PL/SQL 8i.
    Any help on what to start with would be very helpful.
    I hope to use the EBNF rules for the parsing. Am I in the right direction?
    Are there any open source code for PL/SQL parser ?
    Thanks & Regards
    Aswin Asokan The direction is right as far as I know but the task
    is really difficult. PL/SQL's syntax is inherited
    from ADA language which is BIG one and very complex to parse.
    And there is SQL part as well. Just look at the
    market - so few products are based on this kind
    of parser (PL/SQL) - as I can guess.
    For example:
    Formatter Plus (www.quest.com),
    ClearSQL (www.clearsql.com),
    CAST PL/SQL Analyzer (www.castsoftware.com),
    LECCO SQL Expert for Oracle (www.leccotech.com ) - as I can assume but I'm not sure.
    Probably you may search the net for a little subset of this
    parser - for ANSI SQL or for ADA to start with.

  • PL/SQL parser for 7.3 DB?

    We have an ORACLE 7.3 DB and are looking for a PL/SQL parser for XML... Some of the posts I've seen seem to suggest that a solution exists, but I'm not having any luck finding out for sure...
    Thanks,
    Jeff

    http://technet.oracle.com/tech/xml/info/index2.htm?Info&plsxml/xml4plsql.htm

  • PL/SQL Parser Bug?

    Hi,
    just came across a strange PL/SQL parser behavior. Why is the following PL/SQL code valid?
    DECLARE
        vEmpNo NUMBER;
    BEGIN
        FOR rEMP IN
          ( SELECT EMPNO
              INTO vEmpNo
              FROM EMP
        LOOP
            dbms_output.put_line('Value: '||vEmpNo);
        END LOOP;
    END;The "INTO vEmpno" doesn't make much sense, but it's successfully compiled and executed.
    Database version is 10.2.0.3.0
    Any idea?
    Patrick
    My APEX Blog: http://www.inside-oracle-apex.com/
    The APEX Builder Plugin: http://builderplugin.oracleapex.info/
    The ApexLib Framework: http://apexlib.sourceforge.net/

    the pl/sql manual gives the syntax of a cursor for loop as
    cursor_for_loop_statement ::=
    [<< label_name >>] FOR record_name IN
    {cursor_name [(cursor_parameter_name
                  [, cursor_parameter_name]...,)]
    | (select_statement)}
    LOOP statement [statement]...
    END LOOP [label_name];and the pl/sql manual defines a "select into" as
    "The SELECT INTO statement retrieves data from one or more database tables, and assigns the selected values to variables or collections. For a full description of the SELECT SQL statement, see Oracle Database SQL Reference."
    and it also says
    "Selecting At Most One Row: SELECT INTO Statement
    If you expect a query to only return one row, you can write a regular SQL SELECT statement with an additional INTO clause specifying the PL/SQL variable to hold the result."
    so, if pl/sql feels that the INTO is just another clause to a regular select statement, and cursor-for-loops work on select statements, then there is no problem. huh?????
    guess in a similar way to v8 pl/sql allowing select of booleans, it just ignores that clause. but since it isn't explicitly stated as being allowed, we can hope that oracle will eventually notice and get rid of it.

  • PL/SQL parser installation error

    I tried to install the XML PL/SQL parser against Oracle 8.1.6 with JServer Release 8.1.6.0.0 and I received a large number of errors about invalid column names including the following:
    Error while resolving class oracle/xml/parser/v2/FromDescendantAttributes
    ORA-00904: invalid column name
    Error while resolving class oracle/xml/parser/v2/XSLNode
    ORA-00904: invalid column name
    Error while resolving class oracle/xml/parser/v2/UnaryExpr
    ORA-00904: invalid column name
    Any suggestions?
    Thanks

    Hi Steven:
    Yep...I just checked our install and there are no java classes in user_objects. We had the init*.ora file shared_pool_size set too low (as indicated under $ORACLE_HOME/javavm/doc/readme.txt).
    So I'll get our DBA to try it again.
    Thanks,
    Derek
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Steven Muench ([email protected]):
    This likely means that the database JavaVM is not properly installed in your Oracle8i database. You need to run the initjvm.sql script as detailed in the JServer documentation before any 'loadjava'
    commands will work.<HR></BLOCKQUOTE>
    null

  • The parsing engine has encountered a fatal error condition......

    I am creating a new Entitilement Segment. When I sync, I get a parsing
    exception. The error stack is described below. The same error message
    is displayed while starting the server.
    Any help is appreciated.
    Kumar
    URI : /contentselectors/GlobalContentSelectors.rls
    Cause : Exception raised when executing create, please see the embedded
    exception.
    StackTrace :
    Exception[com.bea.p13n.expression.internal.parser.ParseException: The
    parsing engine has encountered a fatal error condition; see embedded
    exception for details.]
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:175)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    Caused by: org.xml.sax.SAXParseException: Valid documents must have a
    <!DOCTYPE declaration.
    at org.apache.crimson.parser.Parser2.warning(Parser2.java:3074)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:491)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
    at
    org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
    at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:161)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    Resource key "Corrective Action" not found for class
    com.bea.commerce.tools.server.SynchronizationProgress. null
    ==================================================================
    URI : /entitlements/GlobalEntitlements.rls
    Cause : Exception raised when executing create, please see the embedded
    exception.
    StackTrace :
    Exception[com.bea.p13n.expression.internal.parser.ParseException: The
    parsing engine has encountered a fatal error condition; see embedded
    exception for details.]
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:175)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    Caused by: org.xml.sax.SAXParseException: Valid documents must have a
    <!DOCTYPE declaration.
    at org.apache.crimson.parser.Parser2.warning(Parser2.java:3074)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:491)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
    at
    org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
    at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:161)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    Resource key "Corrective Action" not found for class
    com.bea.commerce.tools.server.SynchronizationProgress. null
    ==================================================================
    URI : /segments/GlobalClassifications.rls
    Cause : Exception raised when executing create, please see the embedded
    exception.
    StackTrace :
    Exception[com.bea.p13n.expression.internal.parser.ParseException: The
    parsing engine has encountered a fatal error condition; see embedded
    exception for details.]
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:175)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    Caused by: org.xml.sax.SAXParseException: Valid documents must have a
    <!DOCTYPE declaration.
    at org.apache.crimson.parser.Parser2.warning(Parser2.java:3074)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:491)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
    at
    org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
    at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:161)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.reposit

    Hi kumar,
    did you find what was the resolution for this.
    thanks

  • Sybase ESP java sdk, SQL parser exception for all queries

    Hi,
    I am new to Sybase ESP java sdk. Trying to use sdk projection subscription, but getting for all the queries including blank string:-
    com.sybase.esp.sdk.exception.ProjectErrorException: SQL parsing error
    at com.sybase.esp.sdk.impl.SubscriberImplV3.doSubscribe(Unknown Source)
    at com.sybase.esp.sdk.impl.SubscriberImpl.subscribeSql(Unknown Source)
    My Example code :-
    Credentials creds = new Credentials.Builder(Credentials.Type.USER_PASSWORD).setUser("user").setPassword("pwd").create();
      Project project = s_sdk.getProject(uri, creds);
      project.connect(WAIT_TIME_60000_MS);
      Subscriber subscriber = project.createSubscriber();
      //subscriber.subscribeStream("Trades");
      subscriber.connect();
                    subscriber.subscribeSql("select UserMaxCpu from wSBW912");
    I am new to sdk and not sure what I am doing wrong here, please suggest.
    Thanks,
    Venkatesh

    The problem you're experiencing is due to your JNDI configuration not matching the JavaDB database where you created the tables.
    If you look at the config for DerbyPool in the Admin Console, you'll see that DerbyPool points to:
    jdbc:derby://localhost:1527/sun-appserv-samples
    In the Admin Console click Resources->Connection Pools->DerbyPool, then click Additional Properties (9.1) or look at the page (9.0).
    You can either modify DerbyPool's config to point to:
    jdbc:derby://localhost:1527/BookDB
    Or you can create the tables in sun-appserv-samples. The create-tables ant task included with the Java EE 5 Tutorial will create the tables in the correct database.
    -ian

  • SQL Parser supporting nested queries

    Hi,
    I require a SQL parser that supprt nested queries. JavaCC doesnt support nested queries so that one is out. If anyone knows of any open sourse parser, please enlighten me. I have already looked enough on Google but not of much use.
    thanks,
    abulkd

    | 1. as suggested , i was able to get the oraclexmlsql.jar
    | from the servlet zip and loading it solved the problem of
    | the jdbc string being printed int he cursor syntax . it
    | works from the xmlgen utility withing pl/sql. but when
    | using OracleXML in a java prog the results still printout
    | the jdbc string.. any ideas...
    Could only be a CLASSPATH problem difference in your two
    tests.
    | 2. Is there anyway to supress the rownum attribute tag in
    | the subquery (cursor) results...that is the
    | setRowIdAttrName .... w/o using xslt
    Not at this time. Rownum supression on the subquery should
    probably follow your settings on the main query. I'll
    suggest to the devs.
    | 3. We are implementing a solution using these tools.... we
    | wanted to know which were the production versions.
    XDK Components for XML and XSLT are production.
    XML SQL Utility and XSQL Servlet are still Technical
    Previews and as such are not yet production.
    null

  • SQL Parsing Errors

    We are running htmldb 1.5. We have an application running without problems on the development server. When we export the application and then import it on another server (QA or Production) we sometimes get the following errors in report regions that are retrieving data based on a page item:
    failed to parse SQL query:
    ORA-06502: PL/SQL: numeric or value error: NULL index table key value
    The form with the page item is displaying the value for the item, but the reports based on the page item fail. If we go into the htmldb development environment and edit the page for viewing purposes, the problem appears to disappear from that point on. We do not make any changes to the page.
    Is there a problem with the export/import process? Is there a way to make sure the page item has the value expected? We are using DML processing to fetch the record for the page. The fetch occurs 'After the Header'. Should the fetch be 'Before the Header'. Should we force a computation that reads the value into the page item again? If so, at what point?
    Usually we invoke the page and set the page item values with a url that looks like:
    f?p=&APP_ID.:510:#APP_SESSION#:UPDATE::510:P510_CLASS_ID:#CLASS_ID#
    Thanks for your help,
    Peter

    M Leclair (guest) wrote:
    : Using PL/SQL Parser, is it possible to obtain the parsing
    errors
    : output in other place than a file (ref: setErrorLog function)?
    : as varchar variables or kind?
    It is not possible at this time. It has been filed as an
    enhancement request.
    Oracle XML Team
    http://technet.oracle.com
    Oracle Technology Network
    null

  • Is SQL Server Engine failover service spported for Orchestrator databases?

    Hi there,
    I have the following question:
    Is SQL Server Engine failover service spported for Orchestrator 2012 R2 databases?
    Thanx in advance.
    Regards,
    Chris

    Hi,
    yes, the issue that Orchestrator does not reconnect when the SQL server is restarted is has been fixed in System Center 2012 Orchestrator Service Pack 1 (http://support.microsoft.com/kb/2768366)
    Orchestrator requires "only "the basic SQL Server features found in the Database Engine Service. No additional features are required.
    Regards,
    Stefan
    www.sc-orchestrator.eu ,
    Blog sc-orchestrator.eu

Maybe you are looking for

  • How do I find and delete invisible files?

    Mac Hard Drive info window says 157.58 GB used and 159.56 GB capacity, leaving 1.99 available.  Total for all folders in Mac HD is 133.344 GB. 14.13 GB  Library 04.81 GB System 114.4 GB Users 16.58  GB Applications .004   GB  User Guides and Info I a

  • Xorg crash on radeon

    Hello, so I posted this issue on reddit already, but now that I was able to register here I thought I would post it: So for a while now my Xorg occasionally crashes. The problem is apparently the gpu driver, because it only occasionally happens when

  • I just upgraded to FF 4.0 on Win7 and I noticed that "Open in new tab" does not work

    I just upgraded to FF 4.0 on Win7 and I noticed that when you click a link and select 'open in new tab' it copies over the correct link to the address bar but doesn't open it.

  • ITunes crashes when I try to access the store?

    It worked perfectly fine before I updated to 10.5, now whenever I click on the Store button, it starts to load. When the progress bar at the top of the screen reaches half way, a Windows dialogue box comes up and says "iTunes has stopped working" and

  • Viewing a file

    I am very new to java server pages and I want to take a file that is saved in my database and let the administrator view that file. These files can be images or .doc's. I want to use a select statment and a where clause to choose the file. I think I