[WLS 8.1] DataDirect/Bea SQL drivers reliable?

Hi,
For the third time in a few days, I get the following message while trying to shutdown the server :
<Notice> <WebLogicServer> <BEA-000374> <Waiting for ExecuteQueue weblogic.kernel.Default to finish 1 pending requests>
and the server never ends its shutdows...
When I look in SQL Server Entreprise Manager, I see that there is a task with the status "RUNNING" on database master. This task calls "master..xp_jdbc_recover2;1", but it seems to never end. (I already tried to leave id several days)
I'm tempted to stop WLS with a Ctrl-C, but I know it might never start again as long as the SQL task is there.
I suppose this is related to what I found in another thread "jdbc thread stuck while reserving a connection..." from march 2004 :
(From Joe Weinstein)
We are aware of a Microsoft bug in it's SQLServer XA
DLLs, where we have also seen calls to recover() hang.
It's not a weblogic or a driver issue, so we're waiting
on this as well. MS purported to have fixed this
recently with an MS/SQLServer upgrade, but they
were wrong, and have to do it again...Are there some news about this?
The server version is SqlServer 2000 SP2. Would the SP3 help?
Is there a clean way to stop this SQL task? (other than a server reboot)
Thanks in advance,
Didier D

Hi,
We installed sqlServer 2000 SP3 and the problem seems to be history.
Good.
Didier D

Similar Messages

  • SQL Drivers with DataDirect

    After a power outage on the JS machine, when I try to run our standard job I get the following error message -
    |Dataflow DF_Extract_CRS_mtblApplication|Reader QRY_CRS_mtblApplication
    SQL submitted to ODBC data source <CRS> resulted in error <[DataDirect][ODBC SQL Server Driver]The DataDirect ODBC driver you
    are attempting to access has been provided to you by Business Objects Data Integration, Inc. for exclusive use with
    BusinessObjects Data Integrator.  You are not licensed to use this driver with any application other than BusinessObjects Data
    Integrator.  If you would like to purchase a driver for some other use, please call 800-876-3101 or visit DataDirect at
    We have rebooted the box via a controlled restart, but still get the same message.
    Any ideas please ?

    is this happening on unix or windows? I am assuming its unix
    was the job running fine before that ?
    is you settings for rebranding set in $LINK_DIR\bin
    odbc.ini file
    what is the driver file that you are using in the DSN in $LINK_DIR\bin
    odbc.ini and Driver odbc.ini file ?

  • [[DataDirect][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Column name or number of supplied values does not match table definition.]

    Hii ..
    need help on this ..
    This what I am doing ..
    I am using a DATAEXPORT function to export level0 data from my essbase 11.1.2.2 to Microsoft SQL 2008 tables.
    So what I did first I exported the level0 data to a flat file using DATAEXPORT and the created the SQL columns by the same  in that order only in my SQL table.
    When I run it fails with this error:
    ODBC Layer Error: [21S01] ==> [[DataDirect][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Column name or number of supplied values does not match table definition.]
    [Tue Jul 23 18:26:07 2013]Local/dataexp/dataexp/admin@Native Directory/1209813312/Info(1021014)
    ODBC Layer Error: Native Error code [213]
    [Tue Jul 23 18:26:07 2013]Local/dataexp/dataexp/admin@Native Directory/1209813312/Error(1012085)
    Unable to export data to SQL table [dataexp]. Check the Essbase server log and the system console to determine the cause of the problem.
    [Tue Jul 23 18:26:07 2013]Local/dataexp/dataexp/admin@Native Directory/1209813312/Info(1021002)
    SQL Connection is Freed
    [Tue Jul 23 18:26:07 2013]Local/dataexp/dataexp/admin@Native Directory/1209813312/Warning(1080014)
    Transaction [ 0x1c50001( 0x51ee7d66.0x80342 ) ] aborted due to status [1012085].
    [Tue Jul 23 18:26:07 2013]Local/dataexp/dataexp/admin@Native Directory/1209813312/Info(1012579)
    Total Calc Elapsed Time for [test.csc] : [1.44] seconds
    =============================================================
    I did a simple test on my Sample.basic application then ..
    loaded the calc data to it and then used the below script to export to a flat file
    //ESS_LOCALE English_UnitedStates.Latin1@Binary
    SET DATAEXPORTOPTIONS
                    DataExportLevel "Level0";
                    DataExportOverwriteFile ON;
                    DataExportColFormat OFF;
                    DataExportDimHeader OFF;
    FIX(
                "Jan",
                "Sales",
                "Actual"
    /*DATAEXPORT "File" "," "/home/hypadmin/samtest.txt";*/
    DATAEXPORT "DSN" "Abhitest" "sample" "sa" "welcome1";
    ENDFIX
    out put as below:
    "Sales"
    "100-30","California"
    "Jan","Actual",145
    Now In sql I created only 3 columns with name Jan/Sales/Actual and when I run this script again with comments removed .. I get the same error as what I have got in my first test case with other application ..
    but when I create the columns with same name as what its in export
    Sales/100-30/Califirnia/Jan/Actual
    It created the new rows successfully ..
    So with this I think the error which I am getting with my other application might be because of the same column issue  .. but then I have created all the columns by looking at the export file only as I did in sample ..
    Any idea would be helpful ..
    Thanks
    Abhishek
    I

    First make sure you add
    DataExportRelationalFile ON;
    to your set commands it is missing
    I alwats like to also add
    DataExportColHeader dimensionName;
    so I am sure what dimension is getting put into the columns.
    Then count the number of dimensions in your outline (exclude attribute dimensions). You need at least that many columns in your table  -1 + the number of  members you will be returning as columns in the export
    Taking your example Sample basic has 5 dimensions
    Measures
    Years
    Scenario
    Product
    Market
    Since you did not specify a dataexportcolheader it took the dense dimension Scenario as the columns. Your fix statement is limiting that to one member. Doing the math
    5 -1 + 1 = 5 columns in your table which is what you found works.  Suppose you fixed on bothe Actual and budget in scenario then you would need 6 columns 5 -1 +2

  • Using Entity Framework with SQL Azure - Reliability

    (This is a cross post from http://stackoverflow.com/questions/5860510/using-entity-framework-with-sql-azure-reliability since I have yet to receive any replies there)
    I'm writing an application for Windows Azure. I'm using Entity Framework to access SQL Azure. Due to throttling and other mechanisms in SQL Azure, I need to make sure that my code performs retries if an SQL statement has failed. I'm trying to come up with
    a solid method to do this.
    (In the code below, ObjectSet returns my EFContext.CreateObjectSet())
    Let's say I have a function like this:
      public Product GetProductFromDB(int productID)
         return ObjectSet.Where(item => item.Id = productID).SingleOrDefault();
    Now, this function performs no retries and will fail sooner or later in SQL Azure. A naive workaround would be to do something like this:
      public Product GetProductFromDB(int productID)
         for (int i = 0; i < 3; i++)
            try
               return ObjectSet.Where(item => item.Id = productID).SingleOrDefault();
            catch
    Of course, this has several drawbacks. I will retry regardless of SQL failure (retry is waste of time if it's a primary key violation for instance), I will retry immediately without any pause and so on.
    My next step was to start using the Transient Fault Handling library from Microsoft. It contains RetryPolicy which allows me to separate the retry logic from the actual querying code:
      public Product GetProductFromDB(int productID)
         var retryPolicy = new RetryPolicy<SqlAzureTransientErrorDetectionStrategy>(5);
         var result = _retryPolicy.ExecuteAction(() =>
               return ObjectSet.Where(item => item.Id = productID).SingleOrDefault;
         return result;
    The latest solution above is described as ahttp://blogs.msdn.com/b/appfabriccat/archive/2010/10/28/best-practices-for-handling-transient-conditions-in-sql-azure-client-applications.aspx Best Practices for Handling Transient Conditions in SQL Azure Client
    Application (Advanced Usage Patterns section).
    While this is a step forward, I still have to remember to use the RetryPolicy class whenever I want to access the database via Entity Framework. In a team of several persons, this is a thing which is easy to miss. Also, the code above is a bit messy in my
    opinion.
    What I would like is a way to enforce that retries are always used, all the time. The Transient Fault Handling library contains a class called ReliableSQLConnection but I can't find a way to use this with Entity Framework.
    Any good suggestions to this issue?

    Maybe some usefull posts
    http://blogs.msdn.com/b/appfabriccat/archive/2010/12/11/sql-azure-and-entity-framework-connection-fault-handling.aspx
    http://geekswithblogs.net/iupdateable/archive/2009/11/23/sql-azure-and-entity-framework-sessions-from-pdc-2009.aspx

  • Difference between oracle and BEA JDBC Drivers

    One of our application plan to move from BEA JDBC drives to Oracle drivers.
    We use Weblogic 9.2 as application server and Oracle 10g as the database.
    Questions
    =======
    1. What is the basic difference between these drivers and how do we decide which one to use.
    2. What can be the impact of moving to Oracle drives from BEA on the overall application...?
    3. Other than change in the jdbc.datasource.url = jdbc:oracle:thin:@, do we need to take anything else into consideration.
    Pls. let me know in case any further details are required.
    Thanks in advance.

    "1. What is the basic difference between these drivers and how do we decide which one to use."
    They are totally different products made independently by different companies.
    "2. What can be the impact of moving to Oracle drives from BEA on the overall application...?"
    As long as your application uses standard JDBC APIs, the impacts will be minimized, and
    unpredictable, some running faster, some slower... Any bug list for one driver will be
    different than for the other. If you use any driver-specific extension APIs, they won't
    be in the other driver.
    "3. Other than change in the jdbc.datasource.url = jdbc:oracle:thin:@, do we need to take anything else into consideration."
    Also changing the diver/datasource class name, and reviewing any arguments/driver properties.
    Property names and functions are usually driver-specific.
    Joe

  • WLS 10.3.3 - BEA-280061 The persistent store could not be deployed

    Hi,
    We have an application which is using WLS 10.3.3. After installing, whenever we start a managed server, it fails with:
    <BEA-280061> <The persistent store "XYZ" could not be deployed: java.io.IOException: [Store:280044]The file store directory "/<PATH TO STORE>/XYZ" does not exist
    java.io.IOException: [Store:280044]The file store directory "/<PATH TO STORE>/XYZ" does not exist
         at weblogic.store.io.file.StoreDir.throwIOException(StoreDir.java:173)
         at weblogic.store.io.file.StoreDir.createDirectory(StoreDir.java:226)
         at weblogic.store.admin.FileAdminHandler.prepareCommon(FileAdminHandler.java:158)
         at weblogic.store.admin.FileAdminHandler.prepare(FileAdminHandler.java:104)
         at weblogic.management.utils.GenericManagedService.prepareDeployment(GenericManagedService.java:204)
         at weblogic.management.utils.GenericServiceManager.prepareDeployment(GenericServiceManager.java:121)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:628)
         at weblogic.management.internal.DeploymentHandlerHome.prepareInitialDeployments(DeploymentHandlerHome.java:408)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:98)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    On investigation, the data/store directory does exist and the path is correct, but the store name directory does not - so for example if the store is called XYZ, there is no folder XYZ in data/store.
    There are no errors in the managed server log at all up until this point.
    We can get this working by:
    * Starting the Managed server
    * It fails
    * ShutDown the Managed Server
    * Create the folder XYZ using mkdir
    * Start the Managed Server (this works)
    This is the associated section from the config.xml:
    <file-store>
    <name>XYZ</name>
    <target>manserv-1</target>
    </file-store>
    This is a four node cluster and this store is deployed to all of the nodes - all four nodes have the same issue.
    Obviously I'd like to know why this is happening so we can correct it. I have looked round the web but can't see this particular error anywhere.
    Thanks in advance for any help
    Edited by: 843385 on Mar 10, 2011 6:03 AM

    Make sure the directory to which the file store points in available.
    - Target attribute of the file store (The server instances or migratable targets defined in the current domain that are candidates for hosting the
    file store. In a clustered environment, a recommended best practice is to target a custom file store to the same migratable target as the migratable
    JMS service, so that a member server will not be a single point of failure. A file store can also be configured to automatically migrate from an
    unhealthy server instance to a healthy server instance with the help of the server health monitoring services.)
    - Directory attribute of the file store (The path name to the file system directory where the file store maintains its data files. When targeting a
    file store to a migratable target, the store directory must be accessible from all candidate server members in the migratable target. For highest
    availability, you can use a SAN (Storage Area Network) disk.)
    Note that a filestore is a singleton service and is targetted to one server in the cluster at a time, in your case manserv-1.
    So on the machine where manserv-1 runs you must make sure the directory "/<PATH TO STORE>/XYZ exists.

  • Errors loading MS SQL drivers to DB using loadjava

    we have a Oracle9iDB running in linux.
    From Pl/SQl we need to connect to an SQL server DB. To do that we invoked a java class to connect from SQL Server. When loading the MSSQL drivers
    mssqlserver.jar, msutil.jar, msbase.jar to the DB, there were many errors.
    whats wrong?
    regards,
    Anton

    we need to connect Oracle on Linux to MSSQL via JDBC. Some way or another heterogeneous services is not available with our DB setup.
    In a command line, my class executes normally it can connect to the MSSQL server because im setting the msbase.jar, mssqlserver.jar, etc in the CLASSPATH.
    Now in the case of running my class on the DB, my class is looking for msbase.jar, and the other jar files in the DB, which are not there since i havent loaded it. Now when i load the jar files in the DB. i have many errors.
    i think the problem with this is that msbase.jar, and the other jar files, are looking
    for the java jars i.e. classes12.zip and rt.jar, etc. in the DB which is not loaded by default on the OracleDB. I did try to load the classes12.zip and rt.jar first but i have access permissions denied errors. I think this is part of the Security of Oracle not to expose the DB to all Java classes.
    Do you think I should continue with this approach?
    regards,
    Anton
    Message was edited by:
    user450391

  • [WLS 10.3]- XAConnection java.sql.SQLException

    Hi All,
    I HAC getting the following exception while deploying an application
    He is using Weblogic 10.3 with Oracle 10
    He is able to create the connection pool with XA driver which comes with Weblogic
    After that he is trying to deploy the application and getting the following exception
    2506: [01/22/2009 15:16:43:365 EST, [ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)']: Onex System Error: OnexConnection.<init> java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_PROTO start() failed
    on resource 'onexDataSource': XAER_PROTO : Routine was invoked in an inproper context
    oracle.jdbc.xa.OracleXAException
    at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1101)
    at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:237)
    at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
    at weblogic.jdbc.jta.DataSource.start(DataSource.java:695)
    at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1183)
    at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1116)
    at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:275)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:511)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:438)
    at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1406)
    at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1330)
    at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:425)
    at weblogic.jdbc.jta.DataSource.connect(DataSource.java:382)
    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:338)
    at com.onexchange.db.OnexConnection.<init>(OnexConnection.java:35)
    at com.onexchange.db.PersistenceManager.getConnection(PersistenceManager.java:63)
    at com.onexchange.db.PersistenceManager.getOnexConn(PersistenceManager.java:36)
    at com.onexchange.db.DBHelper.query(DBHelper.java:44)
    at com.onexchange.db.DBHelper.query(DBHelper.java:106)
    at com.onexchange.notify.SubscriberNotification.get(SubscriberNotification.java:84)
    at com.onexchange.notify.SubscriberNotification.getEmails(SubscriberNotification.java:122)
    at com.onexchange.notify.handlers.SerializableNotification.getRecipient(SerializableNotification.java:110)
    at com.onexchange.notify.handlers.SerializableNotification.<init>(SerializableNotification.java:37)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at com.onexchange.notify.NotifyTableEntry.getGenerator(NotifyTableEntry.java:182)
    at com.onexchange.notify.NotifyMessageBean.onMessage(NotifyMessageBean.java:56)
    at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
    at weblogic.ejb.container.internal.MDListener.run(MDListener.java:744)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    In my research I found these patches but they are for 9.1 and 8.1
    http://bugs.bea.com/WebClarify/CRView?CR=CR249009
    http://bugs.bea.com/WebClarify/CRView?CR=180008
    While creating connection pool and testing he is not getting any exception
    He is getting this while deploying an application
    He is getting this exception irrespective of application deployment
    I need your pointers on this
    Regards,
    Hari

    Set the value of the test-connections-on-reserve data source property to true in the DOMAIN_HOME\config\jdbc\cgDataSource-jdbc.xml file as shown below:
    <jdbc-connection-pool-params>
    <test-connections-on-reserve>true</test-connections-on-reserve>
    <seconds-to-trust-an-idle-pool-connection>0</seconds-to-trust-an-idle-pool-connection>
    </jdbc-connection-pool-params>
    Please refer CR383232
    http://download.oracle.com/docs/cd/E13160_01/wli/docs10gr3/relnotes/relnotesLimit.html#wp1388424
    Edited by: dvohra on Feb 16, 2009 12:13 PM

  • Microsoft SQL Server JDBC driver and WLS JMS problem?

              Greetings,
              I'm using the Microsoft SQL Server JDBC driver with WLS with JMS
              persisted to SQL Server, during WLS startup the JMS attempts to
              read the JMSStore and JMSState tables in the db, if they are
              already present (say, from a previous run) the driver kicks out:
              java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
              not re-read row data for column 1.
              If the tables are not present, then WLS creates them and
              everything proceeds fine. Now, its not a good thing to attempt
              to reread row data for a ResultSet, especially for portability. Why is WLS JMS
              doing this? is there some config I can use to adjust JMS startup behavior for
              persisted JMS stores?
              Jay Houghton
              Centiv
              [email protected]
              long exception trace follows:
              <Oct 1, 2002 8:29:11 AM EDT> <Info> <JMS> <User connection factory "BroadcastTopicFactory"
              is started.>
              <Oct 1, 2002 8:29:18 AM EDT> <Info> <JMS> <JMSServer "EnergizerJMSServer", Opening
              JDBC store tables "JMSStore
              " and "JMSState" using connection pool "JMSConnectionPool".>
              <Oct 1, 2002 8:29:20 AM EDT> <Alert> <JMS> <JMSServer "EnergizerJMSServer", store
              failed to open, java.io.IOEx
              ception: JMS JDBC store, connection pool = <JMSConnectionPool>, prefix = <null>:
              recover
              java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
              not re-read row data for colum
              n 1.
              at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
              at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
              at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
              at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:618)
              at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:728)
              at weblogic.jms.store.JMSStore.recover(JMSStore.java:112)
              at weblogic.jms.backend.BEStore.open(BEStore.java:179)
              at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:330)
              at weblogic.jms.JMSService.createBackEnd(JMSService.java:923)
              at weblogic.jms.JMSService.addJMSServer(JMSService.java:1277)
              at weblogic.jms.JMSService.addDeployment(JMSService.java:1174)
              at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
              at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
              at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:23
              3)
              at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
              at java.lang.reflect.Method.invoke(Native Method)
              at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
              at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
              at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
              at $Proxy40.updateDeployments(Unknown Source)
              at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub
              .java:2734)
              at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:362
              at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:154)
              at java.lang.reflect.Method.invoke(Native Method)
              at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
              at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
              at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
              at $Proxy57.start(Unknown Source)
              at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean
              _CachingStub.java:480)
              at weblogic.management.Admin.startApplicationManager(Admin.java:1151)
              at weblogic.management.Admin.finish(Admin.java:571)
              at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:508)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
              at weblogic.Server.main(Server.java:35)
              

              Tom,
              thanks for the info, I'll bring this to support.
              I did try the weblogic jDriver for SQL Server and it works fine, so i think it
              must be the way JMS is interacting with the MS driver.
              here are my components:
              WLS 6.1sp1
              Microsoft® SQL Server™ 2000 Driver for JDBC™ is a (Type 4 JDBC) which provides
              partial JDBC 2 support (no blobs, clobs, etc)
              MS SQL Server 2000 (sp2?)
              thanks!
              Jay Houghton
              [email protected]
              Tom Barnes <[email protected]> wrote:
              >Hi Jay,
              >
              >This is not a known issue at BEA as far as I know, perhaps it is the
              >result
              >of a new driver/database combination. Try using a different driver,
              >or a different
              >version of the current driver. Meanwhile, use a file store (just as
              >reliable but faster) and log a case with customer support, including
              >information on your version, service-pack, and what driver you are using.
              >
              >Tom, BEA
              >
              >Jay Houghton wrote:
              >
              >> Greetings,
              >>
              >> I'm using the Microsoft SQL Server JDBC driver with WLS with JMS
              >> persisted to SQL Server, during WLS startup the JMS attempts to
              >> read the JMSStore and JMSState tables in the db, if they are
              >> already present (say, from a previous run) the driver kicks out:
              >>
              >> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet
              >can
              >> not re-read row data for column 1.
              >>
              >> If the tables are not present, then WLS creates them and
              >> everything proceeds fine. Now, its not a good thing to attempt
              >> to reread row data for a ResultSet, especially for portability. Why
              >is WLS JMS
              >> doing this? is there some config I can use to adjust JMS startup behavior
              >for
              >> persisted JMS stores?
              >>
              >> Jay Houghton
              >> Centiv
              >> [email protected]
              >>
              >> long exception trace follows:
              >>
              >> <Oct 1, 2002 8:29:11 AM EDT> <Info> <JMS> <User connection factory
              >"BroadcastTopicFactory"
              >> is started.>
              >> <Oct 1, 2002 8:29:18 AM EDT> <Info> <JMS> <JMSServer "EnergizerJMSServer",
              >Opening
              >> JDBC store tables "JMSStore
              >> " and "JMSState" using connection pool "JMSConnectionPool".>
              >> <Oct 1, 2002 8:29:20 AM EDT> <Alert> <JMS> <JMSServer "EnergizerJMSServer",
              >store
              >> failed to open, java.io.IOEx
              >> ception: JMS JDBC store, connection pool = <JMSConnectionPool>, prefix
              >= <null>:
              >> recover
              >> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet
              >can
              >> not re-read row data for colum
              >> n 1.
              >> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
              >> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
              >> at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
              >> at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:618)
              >> at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:728)
              >> at weblogic.jms.store.JMSStore.recover(JMSStore.java:112)
              >> at weblogic.jms.backend.BEStore.open(BEStore.java:179)
              >> at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:330)
              >> at weblogic.jms.JMSService.createBackEnd(JMSService.java:923)
              >> at weblogic.jms.JMSService.addJMSServer(JMSService.java:1277)
              >> at weblogic.jms.JMSService.addDeployment(JMSService.java:1174)
              >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
              >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
              >> at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:23
              >> 3)
              >> at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
              >> at java.lang.reflect.Method.invoke(Native Method)
              >> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
              >> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
              >> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
              >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
              >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
              >> at $Proxy40.updateDeployments(Unknown Source)
              >> at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub
              >> java:2734)
              >> at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:362
              >> )
              >> at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:154)
              >> at java.lang.reflect.Method.invoke(Native Method)
              >> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
              >> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
              >> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
              >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
              >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
              >> at $Proxy57.start(Unknown Source)
              >> at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean
              >> _CachingStub.java:480)
              >> at weblogic.management.Admin.startApplicationManager(Admin.java:1151)
              >> at weblogic.management.Admin.finish(Admin.java:571)
              >> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:508)
              >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
              >> at weblogic.Server.main(Server.java:35)
              >
              

  • ODBC error state: 60 code: 102 message: [DataDirect][ODBC 20101 driver][Microsoft SQL Server]Incorrect syntax near

    Hi,
    I am currently receiving the following error in BI Answers when I run a query against a Microsoft SQL 2005 Server.
    View Display Error
    Odbc driver returned an error (SQLExecDirectW).
      Error Details
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 16001] ODBC error state: 60 code: 8180 message: [DataDirect][ODBC 20101 driver][Microsoft SQL Server]Statement(s) could not be prepared.. [nQSError: 16001] ODBC error state: 60 code: 102 message: [DataDirect][ODBC 20101 driver][Microsoft SQL Server]Incorrect syntax near 'UserName'.. [nQSError: 16002] Cannot obtain number of columns for the query result. (HY000)
    SQL Issued: SELECT 0 s_0, "SD&A_Dashboard_Test"."BORIS_ALIAS_ETMS_Users"."Id" s_1, "SD&A_Dashboard_Test"."BORIS_ALIAS_ETMS_Users"."UserName" s_2 FROM "SD&A_Dashboard_Test" WHERE ("BORIS_ALIAS_ETMS_Users"."UserName" = 'trowe') FETCH FIRST 65001 ROWS ONLY 
    I am able to connect successfully to the Data Source and run a query against the database using the NQCMD command line tool so believe I have configured the DataDirect 7.0.1 drivers correctly, also I am able to view the Table Data in the RPD Physical Layer in the BI Administration Tool. So don't understand why I am getting this error.
    I have also activated the nquery.log but that doesn't really give me any further information.
    [2015-04-28T16:37:22.000+00:00] [OracleBIServerComponent] [TRACE:4] [USER-34] [] [ecid: 4a9e440f990ba0a4:-1995d2c5:14d00d3ef04:-8000-00000000000001c6,0:1:1:5] [tid: 5f] [requestid: 6f11000b] [sessionid: 6f110000] [username: borisdev] -------------------- Query Status: [nQSError: 16002] Cannot obtain number of columns for the query result. [[
    [nQSError: 16001] ODBC error state: 60 code: 102 message: [DataDirect][ODBC 20101 driver][Microsoft SQL Server]Incorrect syntax near 'UserName'..
    [nQSError: 16001] ODBC error state: 60 code: 8180 message: [DataDirect][ODBC 20101 driver][Microsoft SQL Server]Statement(s) could not be prepared..
    [nQSError: 43119] Query Failed:
    I was wondering if anyone could shed any light on what could possibly be causing the [DataDirect][ODBC 20101 driver][Microsoft SQL Server]Incorrect syntax near 'UserName'.. error ? And also provide any suggestions on how I can troubleshoot this issue further as I am now completely out of ideas of what to do next having tried numerous things i.e. setting  IDENTIFIER_QUOTE_CHAR = '' in DBFeatures.INI which I found in similar posts on the subject all to no avail
    Regards,
    Tom Rowe

    Hi Rajagopal,
    Thanks for your reply after doing some further investigations this morning I found and corrected the problem...
    The DataDirect Driver does not like double quotes in the query for some reason, testing  using the BI Answers generated SQL with the nqcmd tool below...
    With double quotes “” it fails immediately
    Give SQL Statement: select T18706."Id" as c1, T18706."UserName" as c2 from "ETMS_Users" T18706 where ( T18706."UserName" = 'trowe' )
    select T18706."Id" as c1, T18706."UserName" as c2 from "ETMS_Users" T18706 where ( T18706."UserName" = 'trowe' )
    [102][State: S1000] [DataDirect][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Incorrect syntax near 'Id'.
    Statement execute failed
    With double quotes removed for just the columns I now get the Error near ‘ETMS_Users’ which still had the double quotes
    Give SQL Statement: select T18706.Id as c1, T18706.UserName as c2 from "ETMS_Users" T18706 where ( T18706.UserName = 'trowe' )
    select T18706.Id as c1, T18706.UserName as c2 from "ETMS_Users" T18706 where ( T18706.UserName = 'trowe' )
    [102][State: S1000] [DataDirect][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Incorrect syntax near 'ETMS_Users'.
    Statement execute failed
    With all double quotes removed it works !
    Give SQL Statement: select T18706.Id as c1, T18706.UserName as c2 from ETMS_Users T18706 where ( T18706.UserName = 'trowe' )
    select T18706.Id as c1, T18706.UserName as c2 from ETMS_Users T18706 where ( T18706.UserName = 'trowe' )
    c1           c2
    42499        trowe
    Row count: 1
    Give SQL Statement:
    The solution to fix the problem is...
    In the BI Admin Tool Physical Layer Database, Properties Features tab is to delete the double quote in the Value column for IDENTIFIER_QUOTE_CHAR, setting this in the DBFeatures.INI file does not resolve the problem possibly it did in earlier versions of the product.
    Regards,
    Tom Rowe

  • Microsoft Drivers for PHP 5.6+ for SQL Server

    Hi there! I'm trying to migrate all of the sites running on Joomla 3, PHP 5.6, from mySQL to MSSQL server 2014. I can only find Microsoft SQL driver 3 which supports
    until PHP 5.4 but I'm currently running PHP 5.6. Joomla will NOT even recognize SQL driver PHP 5.4 since I'm running PHP 5.6. Based on my research, it seems as Microsoft DO NOT have SQL driver for PHP 5.6 and don't seem to worry about it. Is there any support
    for SQL Drivers for PHP in the future (PHP 5.6+)? Any suggestions? These current sites we are supporting do get PHP upgrades, as well as Joomla. Any help is greatly appreciated. Thanks.

    Microsoft as a whole don't worry about PHP, PHP is not a product of Microsoft. The support for PHP was just because of over requests of PHP users and developers so Microsoft supported PHP on Windows. 
    Microsoft, might, in future support 5.6 and so on, but these features are not as much supported by Microsoft as MS SQL Server, Windows, ASP.NET are supported and updated frequently.
    So, as you've already found. The bid is that you go, and find a third-party plugin. Or, you can however read the manuals (developer documentation) of SQL Server and try to create a plugin in PHP that would connect to SQL Server. If I had to do this, I would
    have created a new plugin rather than trying to use an old third-party plugin. Microsoft's product are land-locked so you can't say any plugin would fully function with Microsoft's products.
    ~!Firewall!~

  • Installing another WLS 6.0 instance in same root /bea directory

    I have a running WLS 6x instance in /bea/wls6***. I want to put another
    instance in /bea directory as a totally separate instance (/bea/wls6trn
    e.g.) Is this a valid way to do this or do I need to go ahead and install to
    another separate filesystem.
    daryl

    Daryl,
    What is it you are trying to accomplish? You do not need to install the software
    multiple times to have multiple instances running on the same machine. In fact, I
    always recommend to our customers that they never use the BEA-HOME directory
    structure to store ther application-specific data. If all you want to do is create
    two separate domains on the same machine, do the following:
    1.) Install the WebLogic Server 6.1 (or 6.0) software (it will go under
    $BEA_HOME/wlserver6.1).
    2.) Create some other directory somewhere outside of the $BEA_HOME directory
    structure (e.g., /usr/myApp1).
    3.) Copy the $BEA_HOME/wlserver6.1/config directory to /usr/myApp1 (you can delete
    the examples and PetStore directories under /usr/myApp1/config directory).
    4.) Edit the /usr/myApp1/config/mydomain/startWebLogic.sh script to reflect the
    fact that the WebLogic software is installed elsewhere.
    5.) Repeat steps 2 through 4 as many times as you want to create as many instances
    as you want...
    Hope this helps,
    Robert
    BEA Weblogic Support wrote:
    Hi Daryl
    That is a weblogic 6.x design constraint. Weblogic 6.x keeps the history of
    versions under BEA-HOME, in the registry.xml file. So, if you have already
    installed same weblogic version with same service pack level then the installer
    won't allow you to install it second time. You should have different bea-homes.
    I hope this clarifies your query.
    Thanks & Regards
    BEA Customer Support
    Daryl Davis wrote:
    I believe you. But I do have a question. If two different versions work,
    why won't two of the same?
    daryl
    "BEA Weblogic Support" <[email protected]> wrote in message
    news:[email protected]...
    Hi Daryl
    Greetings...!
    How are you doing?.
    You can have different versions under same BEA-HOME. For example
    BEA-HOME is /bea
    ----/wlserver6.1(weblogic6.1 build)
    ----/wlserver6.1sp1 (weblogic 6.1 with sp1build)
    ----/wlserver6.0sp2 (weblogic6.0 with sp2 build)
    But you can't have more than one wls instance of same version under one
    BEA-HOME. You have to choose different BEA-HOME, /beatrans
    Thanks & Regards
    BEA Customer Suppot
    Daryl Davis wrote:
    I have a running WLS 6x instance in /bea/wls6***. I want to put
    another
    instance in /bea directory as a totally separate instance (/bea/wls6trn
    e.g.) Is this a valid way to do this or do I need to go ahead andinstall to
    another separate filesystem.
    daryl

  • Weblogic 8.1 SP4 & SQL Server 2005 - Moving to Prod - Will we have issues?

    Ok,
    Can't track down our account holder this afternoon to create a case, so i'll just throw it out there for now.
    Our whole system is running swimmingly on SP4 with BEA SQL Server Driver connecting to SQL Server 2005 (9.0.3042).
    Its been through QA, now its in the training environment...
    Pool Config
    &lt;JDBCConnectionPool
    DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
    Name="myPool" PasswordEncrypted="{3DES}jkjkjkj/GFg="
    Properties="user=XXXXXX;*SendStringParametersAsUnicode*=false;*portNumber*=1433;*databaseName*=XXXXXXXXXX_mo;*serverName*=XXXXXXXXXXX"
    Targets="xxxxxxxx" TestConnectionsOnCreate="true"
    TestConnectionsOnRelease="true" TestConnectionsOnReserve="true"
    TestTableName="SQL SELECT 1" URL="jdbc:bea:sqlserver://XXXXXXXXXXXXXX:1433"/&gt;
    I see alot of posts about people using 2005 on SP6, and there is even a patch out there to go ontop of that....
    [http://commerce.bea.com/d2d/wlplat81sp6_sqlserver2005_patch.jsp]
    And in the official docs it says 2005 is only supported in SP6.
    [http://edocs.beasys.com/wls/docs81/jdbc_drivers/mssqlserver.html#1074559]
    We are using the standard non-XA version of the drivers.
    So my questions are
    * Why is it working on SP4?
    * Do i need to worry about it moving to production using SP4?
    Thanks
    Mike

    Hi. We don't update docs well... You should have zero problems. I might
    recommend contacting official support to get the latest version of our
    JDBC driver package, but it may not be necessary.
    Joe

  • Dump produced after install WLS 8.1 SP3

    Hi there,
         I am sending you the DUMP file generated a lot of times after we had just installed the SP 3. I am not sending the MDUMP file because its size is larger then 180Mb. The same code that generated this error worked fine when we were using the SP 2. It has never occured a DUMP while we were using the SP 2.
         My server configuration:
         before the SP3 installation:
              - WLS 8.1 SP2
              - BEA WebLogic JRockit(TM) 1.4.2_04 JVM (build ari-29212-20040415-1348-win-ia32)
              - SQL Server 2000
              - DB JDBC Driver weblogic.jdbc.sqlserver.SQLServerDriver
         after the SP3 installation:
              - WLS 8.1 SP3
              - BEA WebLogic JRockit(TM) 1.4.2_04 JVM (build ari-31788-20040616-1132-win-ia32)
              - SQL Server 2000
              - DB JDBC Driver weblogic.jdbc.sqlserver.SQLServerDriver
         Piece of code where the error occured:
         public void executeData(String sql) throws DAOException {
              if (Util.isEmpty(sql)){
                   return;
              Connection con = null;
              Statement st = null;
              try {
              con = getConnection();
                   st = con.createStatement();
                   if (logger.isDebugEnabled())
                        logger.debug("Antes do execute do sql no DAO " + sql); // the sql variable has lots of "update" statements (more then 100)
                   int rs = st.executeUpdate(sql); // THE ERROR OCCURES HERE
                   st.close();
              } catch (SQLException sqe) {
                   logger.error(sqe.toString(), sqe);
                   throw new DAOException(sqe);
              } catch (Exception ex) {
                   logger.error("Erro inesperado na aplicação do sql no banco", ex);
              throw new DAOException(ex);
              } finally {
                   cleanup(con, st);
         Thanks
    ===== BEGIN DUMP =============================================================
    JRockit dump produced after 0 days, 02:49:43 on Thu Sep 09 10:05:17 2004
    Additional information is available in:
    D:\bea\user_projects\Mercador_PROD\jrockit.3332.dump
    D:\bea\user_projects\Mercador_PROD\jrockit.3332.mdmp
    Please send the file(s), information about your system
    setup and the program you were running to [email protected]. Thank you.
    Error Message: Stack overflow
    Version : BEA WebLogic JRockit(TM) 1.4.2_04 JVM ari-31788-20040616-1132-win-ia32
    Threads / GC : Native Threads, GC strategy: parallel
    : mmHeap->data = 0x10020000, mmHeap->top = 0x54C20000
    : mmStartCompaction = 0x303C0000, mmEndCompaction = 0x359B0000
    Number CPUs : 2
    Tot Phys Mem : 2683813888
    OS version : Microsoft Windows 2000 Service Pack 4 (Build 2195)
    State : JVM is running
    Command Line : -Djava.class.path=D:\bea\jrockit81sp3_142_04\lib\tools.jar;D:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;D:\bea\WEBLOG~1\server\lib\weblogic.jar;D:\bea\WEBLOG~1\common\eval\pointbase\lib\pbserver44.jar;D:\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;D:\bea\jrockit81sp3_142_04\jre\lib\rt.jar;D:\bea\WEBLOG~1\server\lib\webservices.jar;D:\bea\weblogic81\server\lib\JSQLConnect.jar; -Xgc:parallel -XXfullsystemgc -Xmanagement -Xms1100m -Xmx1100m -Dweblogic.Name=Mercador -Dweblogic.management.username= -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true -Djava.security.policy=D:\bea\WEBLOG~1\server\lib\weblogic.policy -Dsun.java.command=weblogic.Server
    Environment : JAVA_HOME=D:\bea\jrockit81sp3_142_04, java.home=D:\bea\jrockit81sp3_142_04\jre, java.class.path=D:\bea\jrockit81sp3_142_04\lib\tools.jar;D:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;D:\bea\WEBLOG~1\server\lib\weblogic.jar;D:\bea\WEBLOG~1\common\eval\pointbase\lib\pbserver44.jar;D:\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;D:\bea\jrockit81sp3_142_04\jre\lib\rt.jar;D:\bea\WEBLOG~1\server\lib\webservices.jar;D:\bea\weblogic81\server\lib\JSQLConnect.jar;, java.library.path=D:\bea\jrockit81sp3_142_04\jre\bin;.;C:\WINNT\system32;C:\WINNT;D:\bea\jrockit81sp3_142_04\jre\bin;D:\bea\WEBLOG~1\server\bin;D:\bea\jrockit81sp3_142_04\jre\bin;D:\bea\jrockit81sp3_142_04\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;D:\bea\WEBLOG~1\server\bin\oci920_8
    C Heap : Good; no memory allocations have failed
    Registers:
    Converted EIP: 004ef5dd
    EAX = 00000000 EBX = 5be2a26c
    ECX = 5be0fc40 EDX = 5e2c103d
    ESI = 5be0fc40 EDI = 1e45ad90
    EIP = 004ef5dd ESP = 5e2c1000
    EBP = 5be2a1e0 EFL = 00010202
    CS = 001b DS = 0023 ES = 0023
    SS = 0023 FS = 0038 GS = 0000
    Stack:
    5e2c1000 :5be2a26c 00000000 00000000 00000000 00000000 5be2a1e0
    5e2c1018 :0056ae00 0055f017 5be0fc40 5be2a1e0 5e2c1038 5be2a2dc
    5e2c1030 :5be0fc40 55f70707 5be2a26c 54c99368 5be2a2dc 00000000
    5e2c1048 :5be0fc40 5be2a1e0 5be2a26c 1e45ae08 1e45ae0d 55f70758
    5e2c1060 :54c2d910 1e45ad90 5be0fc40 22f30898 55f70b00 00000058
    5e2c1078 :00000022 6e000aa3 00000053 1e45ad90 22f307f0 00000010
    5e2c1090 :1e45ad90 000df4ab 6e0001d3 1e45ad68 5be2a1e0 6e0004f4
    5e2c10a8 :000df49b 000df49a 1e45ad68 22f30820 6e0005cc 1e45aea0
    5e2c10c0 :000df493 22f307b8 1e45ad68 6e001e1f 22f30770 5be2a1e0
    5e2c10d8 :000df492 1e45aea0 000df448 1e45ad90 6e001225 00000007
    5e2c10f0 :22f303a8 1e45ad68 5be2a1e0 22f303a8 22f303a8 22f303a8
    5e2c1108 :00000001 22f30320 000df447 22f30340 1e45ad68 5be2a1e0
    5e2c1120 :6e001710 22f302e8 22f302e8 22f302e8 22f302e8 22f302e8
    5e2c1138 :22f302e8 22f2f108 1e45ad68 22f2f0b0 6e0017f2 22f2f0b0
    5e2c1150 :22f2f0b0 22f2f0b0 22f2f0b0 22f2f0b0 22f2f0b0 22f2e388
    5e2c1168 :1e45ad68 22f2e330 6e0017f2 22f2e330 22f2e330 22f2e330
    5e2c1180 :22f2e330 22f2e330 22f2e330 22f2d4a0 1e45ad68 22f2d448
    5e2c1198 :6e0017f2 22f2d448 22f2d448 22f2d448 22f2d448 22f2d448
    5e2c11b0 :22f2d448 22f2c938 1e45ad68 22f2c8e0 6e0017f2 22f2c8e0
    5e2c11c8 :22f2c8e0 22f2c8e0 22f2c8e0 22f2c8e0 22f2c8e0 000df0a3
    5e2c11e0 :1e45ad68 22f2be38 6e0017f2 22f2be38 22f2be38 22f2be38
    5e2c11f8 :22f2be38 22f2be38 22f2be38 000df094 1e45ad68 22f2bc80
    5e2c1210 :6e0017f2 22f2bc80 22f2bc80 22f2bc80 22f2bc80 22f2bc80
    5e2c1228 :22f2bc80 22f2b708 1e45ad68 22f2b6b0 6e0017f2 22f2b6b0
    5e2c1240 :22f2b6b0 22f2b6b0 22f2b6b0 22f2b6b0 22f2b6b0 000defc6
    5e2c1258 :1e45ad68 22f2ac50 6e0017f2 22f2ac50 22f2ac50 22f2ac50
    5e2c1270 :22f2ac50 22f2ac50 22f2ac50 000defb7 1e45ad68 22f2aa98
    5e2c1288 :6e0017f2 22f2aa98 22f2aa98 22f2aa98 22f2aa98 22f2aa98
    5e2c12a0 :22f2aa98 22f2a510 1e45ad68 22f2a4b8 6e0017f2 22f2a4b8
    5e2c12b8 :22f2a4b8 22f2a4b8 22f2a4b8 22f2a4b8 22f2a4b8 000deee8
    5e2c12d0 :1e45ad68 22f29a68 6e0017f2 22f29a68 22f29a68 22f29a68
    5e2c12e8 :22f29a68 22f29a68 22f29a68 000deed9 1e45ad68 22f298b0
    5e2c1300 :6e0017f2 22f298b0 22f298b0 22f298b0 22f298b0 22f298b0
    5e2c1318 :22f298b0 22f29340 1e45ad68 22f292e8 6e0017f2 22f292e8
    5e2c1330 :22f292e8 22f292e8 22f292e8 22f292e8 22f292e8 000dee0d
    5e2c1348 :1e45ad68 22f28898 6e0017f2 22f28898 22f28898 22f28898
    5e2c1360 :22f28898 22f28898 22f28898 000dedfe 1e45ad68 22f286c0
    5e2c1378 :6e0017f2 22f286c0 22f286c0 22f286c0 22f286c0 22f286c0
    5e2c1390 :22f286c0 22f28150 1e45ad68 22f280f8 6e0017f2 22f280f8
    5e2c13a8 :22f280f8 22f280f8 22f280f8 22f280f8 22f280f8 22f27938
    5e2c13c0 :1e45ad68 22f278e0 6e0017f2 22f278e0 22f278e0 22f278e0
    5e2c13d8 :22f278e0 22f278e0 22f278e0 000debeb 1e45ad68 22f25ba0
    5e2c13f0 :6e0017f2 22f25ba0 22f25ba0 22f25ba0 22f25ba0 22f25ba0
    5e2c1408 :22f25ba0 22f256b0 1e45ad68 22f25658 6e0017f2 22f25658
    5e2c1420 :22f25658 22f25658 22f25658 22f25658 22f25658 000deb54
    5e2c1438 :1e45ad68 22f24c70 6e0017f2 22f24c70 22f24c70 22f24c70
    5e2c1450 :22f24c70 22f24c70 22f24c70 22f24788 1e45ad68 22f24730
    5e2c1468 :6e0017f2 22f24730 22f24730 22f24730 22f24730 22f24730
    5e2c1480 :22f24730 22f23ba0 1e45ad68 22f23b48 6e0017f2 22f23b48
    5e2c1498 :22f23b48 22f23b48 22f23b48 22f23b48 22f23b48 22f22620
    5e2c14b0 :1e45ad68 22f225c8 6e0017f2 22f225c8 22f225c8 22f225c8
    5e2c14c8 :22f225c8 22f225c8 22f225c8 22f20f58 1e45ad68 22f20f00
    5e2c14e0 :6e0017f2 22f20f00 22f20f00 22f20f00 22f20f00 22f20f00
    5e2c14f8 :22f20f00 22f201c0 1e45ad68 22f20168 6e0017f2 22f20168
    5e2c1510 :22f20168 22f20168 22f20168 22f20168 22f20168 22f1ef58
    5e2c1528 :1e45ad68 22f1ef00 6e0017f2 22f1ef00 22f1ef00 22f1ef00
    5e2c1540 :22f1ef00 22f1ef00 22f1ef00 22f1e1c0 1e45ad68 22f1e168
    5e2c1558 :6e0017f2 22f1e168 22f1e168 22f1e168 22f1e168 22f1e168
    5e2c1570 :22f1e168 22f1cf58 1e45ad68 22f1cf00 6e0017f2 22f1cf00
    5e2c1588 :22f1cf00 22f1cf00 22f1cf00 22f1cf00 22f1cf00 22f1c1c0
    5e2c15a0 :1e45ad68 22f1c168 6e0017f2 22f1c168 22f1c168 22f1c168
    5e2c15b8 :22f1c168 22f1c168 22f1c168 22f1af58 1e45ad68 22f1af00
    5e2c15d0 :6e0017f2 22f1af00 22f1af00 22f1af00 22f1af00 22f1af00
    5e2c15e8 :22f1af00 22f1a1c0 1e45ad68 22f1a168 6e0017f2 22f1a168
    5e2c1600 :22f1a168 22f1a168 22f1a168 22f1a168 22f1a168 22f18f58
    5e2c1618 :1e45ad68 22f18f00 6e0017f2 22f18f00 22f18f00 22f18f00
    5e2c1630 :22f18f00 22f18f00 22f18f00 22f181c0 1e45ad68 22f18168
    5e2c1648 :6e0017f2 22f18168 22f18168 22f18168 22f18168 22f18168
    5e2c1660 :22f18168 22f16f58 1e45ad68 22f16f00 6e0017f2 22f16f00
    5e2c1678 :22f16f00 22f16f00 22f16f00 22f16f00 22f16f00 22f161c0
    5e2c1690 :1e45ad68 22f16168 6e0017f2 22f16168 22f16168 22f16168
    5e2c16a8 :22f16168 22f16168 22f16168 22f14f58 1e45ad68 22f14f00
    5e2c16c0 :6e0017f2 22f14f00 22f14f00 22f14f00 22f14f00 22f14f00
    5e2c16d8 :22f14f00 22f141c0 1e45ad68 22f14168 6e0017f2 22f14168
    5e2c16f0 :22f14168 22f14168 22f14168 22f14168 22f14168 22f132a8
    5e2c1708 :1e45ad68 22f13250 6e0017f2 22f13250 22f13250 22f13250
    5e2c1720 :22f13250 22f13250 22f13250 22f12718 1e45ad68 22f126c0
    5e2c1738 :6e0017f2 22f126c0 22f126c0 22f126c0 22f126c0 22f126c0
    5e2c1750 :22f126c0 000ddc2e 1e45ad68 22f11b70 6e0017f2 22f11b70
    5e2c1768 :22f11b70 22f11b70 22f11b70 22f11b70 22f11b70 000ddc1f
    5e2c1780 :1e45ad68 22f119b8 6e0017f2 22f119b8 22f119b8 22f119b8
    5e2c1798 :22f119b8 22f119b8 22f119b8 22f11428 1e45ad68 22f113d0
    5e2c17b0 :6e0017f2 22f113d0 22f113d0 22f113d0 22f113d0 22f113d0
    5e2c17c8 :22f113d0 000ddb41 1e45ad68 22f10898 6e0017f2 22f10898
    5e2c17e0 :22f10898 22f10898 22f10898 22f10898 22f10898 000ddb32
    5e2c17f8 :1e45ad68 22f106c0 6e0017f2 22f106c0 22f106c0 22f106c0
    Code:
    004ef4dd :44890000 548b1424 78a11424 8b005ada c0851004 80c71b74
    004ef4f5 :000000c0 00000000 00c4808b c0850000 ff500774 58210015
    004ef50d :75f68500 6a046a2e cd946801 4c8d0058 396a2424 83d3ff51
    004ef525 :f88314c4 8d077339 52182454 706805eb e80058cd 00019e33
    004ef53d :8b04c483 8b0c2444 5bb2400d 81348900 63980d8b 3b40005b
    004ef555 :244489c1 248c0f0c 5effffff c4835b5d ccccc348 cccccccc
    004ef56d :8bcccccc 5b63980d 85c03300 8b167ec9 5bb24015 348b5600
    004ef585 :c13b4082 000006c7 f27c0000 ccccc35e cccccccc cccccccc
    004ef59d :a1cccccc 005bb244 0f75c085 0b9d7eb8 4ecde800 44a30008
    004ef5b5 :8b005bb2 4f71e8c8 ff250008 997fffff 63983df7 c28b005b
    004ef5cd :83ccccc3 4c8b18ec 84a11c24 53005bb2 8b575655 db330c79
    004ef5e5 :89ffff83 8910245c 751c2444 b244a12d c33b005b 7eb80f75
    004ef5fd :e8000b9d 00084e7b 5bb244a3 e8c88b00 00084f1f ffffff25
    004ef615 :3df7997f 005b6398 7c89fa8b 40a11824 8b005bb2 758bb82c
    004ef62d :89f68500 8924246c 74142474 009b8d34 8b000000 24548916
    004ef645 :24548b20 24448b24 244c8b14 b10ff020 0fc63b0a 0000ce84
    004ef65d :00758b00 7489f685 d7751424 5bb240a1 244c8b00 75c98510
    004ef675 :55006a3f b23c15ff 4c8b005b 158b2424 005bb284 3b08c483
    004ef68d :ff850fd1 85000000 0e850fc0 8b000001 bb2c2454 00000001
    004ef6a5 :10245c89 ff0c42c7 e9ffffff ffffff6e 6398158b 3b47005b
    004ef6bd :33027cfa b80c8bff 8b003983 7518244c 3bff8b15 471374f9
    004ef6d5 :027cfa3b 348bff33 003e83b8 f93bed74 01bb3e75 53000000
    Loaded modules:
    (* denotes the module causing the exception)
    0x77f80000-0x77ffcfff C:\WINNT\system32\ntdll.dll
    0x7c570000-0x7c627fff C:\WINNT\system32\KERNEL32.dll
    0x7c2d0000-0x7c331fff C:\WINNT\system32\ADVAPI32.dll
    0x77d30000-0x77da0fff C:\WINNT\system32\RPCRT4.DLL
    0x78000000-0x78044fff C:\WINNT\system32\MSVCRT.dll
    0x00410000-0x0060efff* D:\bea\jrockit81sp3_142_04\jre\bin\jrockit\jvm.dll
    0x77570000-0x7759ffff C:\WINNT\system32\WINMM.dll
    0x77e10000-0x77e74fff C:\WINNT\system32\USER32.DLL
    0x77f40000-0x77f7dfff C:\WINNT\system32\GDI32.DLL
    0x782f0000-0x78537fff C:\WINNT\system32\SHELL32.dll
    0x70a70000-0x70ad4fff C:\WINNT\system32\SHLWAPI.DLL
    0x71710000-0x71793fff C:\WINNT\system32\COMCTL32.DLL
    0x75030000-0x75043fff C:\WINNT\system32\WS2_32.dll
    0x75020000-0x75027fff C:\WINNT\system32\WS2HELP.DLL
    0x7c340000-0x7c395fff D:\bea\jrockit81sp3_142_04\jre\bin\MSVCR71.dll
    0x10000000-0x10018fff D:\bea\jrockit81sp3_142_04\jre\bin\java.dll
    0x00b30000-0x00b3dfff D:\bea\jrockit81sp3_142_04\jre\bin\verify.dll
    0x74fd0000-0x74fedfff C:\WINNT\system32\msafd.dll
    0x75010000-0x75016fff C:\WINNT\System32\wshtcpip.dll
    0x692e0000-0x69306fff C:\WINNT\system32\pdh.dll
    0x76b30000-0x76b6dfff C:\WINNT\system32\comdlg32.dll
    0x77a50000-0x77b3efff C:\WINNT\system32\ole32.dll
    0x779b0000-0x77a4afff C:\WINNT\system32\OLEAUT32.dll
    0x69280000-0x69288fff C:\WINNT\system32\perfos.dll
    0x782c0000-0x782cbfff C:\WINNT\System32\rnr20.dll
    0x77980000-0x779a3fff C:\WINNT\system32\DNSAPI.DLL
    0x75050000-0x75057fff C:\WINNT\system32\WSOCK32.DLL
    0x77340000-0x77352fff C:\WINNT\system32\iphlpapi.dll
    0x77520000-0x77524fff C:\WINNT\system32\ICMP.DLL
    0x77320000-0x77336fff C:\WINNT\system32\MPRAPI.DLL
    0x75150000-0x7515efff C:\WINNT\system32\SAMLIB.DLL
    0x75170000-0x751befff C:\WINNT\system32\NETAPI32.DLL
    0x59810000-0x5981efff C:\WINNT\system32\SECUR32.DLL
    0x751c0000-0x751c5fff C:\WINNT\system32\NETRAP.DLL
    0x77950000-0x77979fff C:\WINNT\system32\WLDAP32.DLL
    0x773b0000-0x773defff C:\WINNT\system32\ACTIVEDS.DLL
    0x77380000-0x773a2fff C:\WINNT\system32\ADSLDPC.DLL
    0x77830000-0x7783dfff C:\WINNT\system32\RTUTILS.DLL
    0x77880000-0x7790dfff C:\WINNT\system32\SETUPAPI.DLL
    0x7c0f0000-0x7c150fff C:\WINNT\system32\USERENV.DLL
    0x774e0000-0x77512fff C:\WINNT\system32\RASAPI32.DLL
    0x774c0000-0x774d0fff C:\WINNT\system32\RASMAN.DLL
    0x77530000-0x77551fff C:\WINNT\system32\TAPI32.DLL
    0x77360000-0x77378fff C:\WINNT\system32\DHCPCSVC.DLL
    0x777e0000-0x777e7fff C:\WINNT\System32\winrnr.dll
    0x777f0000-0x777f4fff C:\WINNT\system32\rasadhlp.dll
    0x621c0000-0x621c5fff D:\bea\jrockit81sp3_142_04\jre\bin\ioser12.dll
    0x06640000-0x06644fff D:\bea\weblogic81\server\bin\wlntio.dll
    0x6cd60000-0x6ce20fff D:\bea\jrockit81sp3_142_04\jre\bin\dbghelp.dll
    0x77820000-0x77826fff C:\WINNT\system32\VERSION.dll
    0x759b0000-0x759b5fff C:\WINNT\system32\LZ32.DLL
    0x690a0000-0x690aafff C:\WINNT\system32\psapi.dll
    Java Thread ID = 0x00000880, lastJavaFrame = 0x5E2C103C, Name = ExecuteThread: '4' for queue: 'weblogic.kernel.Default'
    Thread Stack Trace:
    at _mmAllocateThreadLocalAreaMemory+13()@0x004EF5DD
    at jrockit/vm/MemSystem.getMoreTLAMemory(Native Method)@0x55F706C0
    at jrockit/vm/MemSystem.getMoreTLAMemoryWrapper(Native Method)@0x55F70758
    at jrockit/vm/MemSystem.allocArray2(Native Method)@0x55F70B00
    at weblogic/jdbc/base/BaseSQLScanner$BaseSQLScannerIDOrKeywordState.processChar(Optimized Method)@0x6E000AA3
    at weblogic/jdbc/base/BaseSQLScanner.getNextToken(Optimized Method)@0x6E0001D3
    at weblogic/jdbc/base/BaseSQLParser.matchWhiteSpaceOrComment(Optimized Method)@0x6E0004F4
    at weblogic/jdbc/base/BaseSQLParser.matchWhiteSpaceOrComment(Optimized Method)@0x6E0005CC
    at weblogic/jdbc/base/BaseSQLParser.parseParenthesizedExpression(Optimized Method)@0x6E001E1F
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E001710
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
    at weblogic/jdbc/base/B

    The dump is caused by a stackoverflow condition. For some reason JRockit is not able to throw the StackOverFlowError (this can be really tricky in a JVM when there is no stack left).
    The cause seems to be that weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents calls itself recursively quite a few times. I don't anything about that code so I couldn't tell you why there are are so many recursive calls. Maybe there is something in your SQL statement that causes the driver to do this?
    The reason this happens after the SP3 installation can be a couple of things: 1) code in the driver has changed 2) code in WLS has changed 3) changes in JRockit may cause the stackoverflow to happen in a "bad" place which we cannot handle.
    You can try increasing the stack size with the -Xss parameter. I think the default is 64kB, so try the double or more.
    Maybe you should contact support for the db driver and ask them why the recursive calls happen.
    Regards,
    /Staffan

  • ODBC connect to SQL Server 2005 from Oracle 10.2.0.3 32bit Linux

    I’m unable to establish a connection from Oracle 10.2.0.3 32bit Linux to SQL Server 2005.
    The ODBC driver is the 32bit DataDirect 5.3 drivers and when I do a status on the listener it does have a handler for SQLDB
    Any help is appreciated.
    Received the following error:
    SQL> select count(*) from columns@SQLDB;
    select count(*) from columns@SQLDB
    ERROR at line 1:
    ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
    [Generic Connectivity Using ODBC]DRV_InitTdp: DB_ODBC_INTERFACE (718): ; [C077]
    Could not find symbol 'SQLAllocConnect' in dynamic library
    DB_ODBC_INTERFACE (722): ; [C079] Failed to load dynamic library
    '/app/DataDirect/lib/libodbc.so'
    ORA-02063: preceding 3 lines from SQLDB
    -----Contents of trace file------------------
    Oracle Corporation --- THURSDAY JUL 10 2008 10:17:16.251
    Version 10.2.0.3.0
    hoagprd (2): ; hoagprd Entered.
    HOACONN.C (244): ; [Generic Connectivity Using ODBC] version: 4.8.2.0.0080
    HOACONN.C (288): ; Class version: 250
    hoagprd (2): ; hoagprd Exited with retcode = 0.
    hoainit (3): ; hoainit Entered.
    (0): ; connect string is: defTdpName=SQLDB;SYNTAX=(ORACLE8_HOA, BASED_ON=
    ORACLE8, IDENTIFIER_QUOTE_CHAR="", CASE_SENSITIVE=CASE_SENSITIVE_QUOTE);
    BINDING=<navobj><binding><datasources><datasource name='SQLDB' type='GENERIC_
    ODBC_FOR_HS' connect='SQLDB'><driverProperties/></datasource></datasources><
    remoteMachines/><environment><optimizer noFlattener='true'/><misc
    year2000Policy='-1' consumerApi='1' sessionBehavior='4'/><queryProcessor
    parserDepth='2000' tokenSize='1000' noInsertParameterization='true'
    noThreadedReadAhead='true' noCommandReuse='true'/><debug driverTrace='true'
    generalTrace='true'/></environment></binding></navobj>
    ORACLE GENERIC GATEWAY Log File Started at 2008-07-10T10:17:16
    hoainit (3): ; hoainit Exited with retcode = 0.
    hoalgon (7): ; hoalgon Entered. name = dbuser.
    sysbase.c (677): ; libodbcinst.so: cannot open shared object file: No such
    file or directory
    DB_ODBC_INTERFACE (718): ; [C077] Could not find symbol 'SQLAllocConnect' in
    dynamic library
    DB_ODBC_INTERFACE (722): ; [C079] Failed to load dynamic library '/app/
    DataDirect/lib/libodbc.so'
    DB_ODBC_INTERFACE (727): ; [C077] Could not find symbol 'SQLAllocConnect' in
    dynamic library
    DRV_InitTdp: DB_ODBC_INTERFACE (718): ; [C077] Could not find symbol '
    SQLAllocConnect' in dynamic library
    DB_ODBC_INTERFACE (722): ; [C079] Failed to load dynamic library '/app/
    DataDirect/lib/libodbc.so'
    nvRETURN (./drv_bind.c 230): -2220
    nvRETURN (./nav_bind.c 298): -2220
    hoalgon (7): ; hoalgon Exited with retcode = 28500.
    hoaexit (6): ; hoaexit Entered.
    hoaexit (6): ; hoaexit Exited with retcode = 0.
    (0): ; Closing log file at THU JUL 10 10:17:16 2008.
    --------------end of trace file ---------------
    --------TNS entry ----------
    SQLDB=
    (DESCRIPTION =
    (ADDRESS =(PROTOCOL = TCP)
    (Host = oracledbhost)
    (Port = 1521)
    (CONNECT_DATA = (SID =SQLDB)
    (HS=OK)
    -------Listener.ora entry----------
    (SID_DESC=
    (SID_NAME=SQLDB)
    (ORACLE_HOME=/app/oracle10g/product/10.2)
    (PROGRAM=hsodbc)
    -------initSQLDB.ora----------
    # This is a sample agent init file that contains the HS parameters that are
    # needed for an ODBC Agent.
    # HS init parameters
    HS_FDS_CONNECT_INFO = SQLDB
    HS_FDS_TRACE_LEVEL = 4
    HS_FDS_TRACE_FILE_NAME=/app/DataDirect/SQLDB.trc
    HS_FDS_SHAREABLE_NAME=/app/DataDirect/lib/libodbc.so
    # ODBC specific environment variables
    set ODBCINI=/app/DataDirect/odbc.ini
    ------odbc.ini entry------------
    [SQLDB]
    Driver=/app/DataDirect/lib/ivmsss23.so
    Description=DataDirect 5.2 SQL Server Wire Protocol
    Address=SQLServerhost,1401
    AlternateServers=
    AnsiNPW=Yes
    ConnectionRetryCount=0
    ConnectionRetryDelay=3
    Database=SQLServerDB
    LoadBalancing=0
    LogonID=
    Password=
    QuotedId=No
    SnapshotSerializable=0

    The error message is indicating problems loading the driver manager.
    A common issue on Linux (especially on Suse Linux) is related to library caching. First of all make sure you add the LD_LIBRARY_PATH to your listener.ora file to guarantee the correct libraries will be loaded. Your SID section will then look like:
    (SID_DESC=
    (SID_NAME=SQLDB)
    (ORACLE_HOME=/app/oracle10g/product/10.2)
    (ENVS=LD_LIBRARY_PATH=/app/oracle10g/product/10.2/lib:/app/DataDirect/lib)
    (PROGRAM=hsodbc)
    After changing the listener.ora file stop and start the listener.
    Details about the set up can be found in Metalink note:
    Note.264567.1 P216. How To Setup Generic Connectivity - HSODBC - on Linux
    If this does not help enable strace and check out from which location libodbc.so is being loaded.
    Please be also aware HSODBC has been desupported 15th of March. As you start a new project you should proceed with the follow up product DG4ODBC.

Maybe you are looking for

  • How to Add and Remove Apps from Launchpad?

    I have noticed that I have apps missing in launchpad that I do have in my apps folder. How do I add these to launchpad. On the flip side, then how can I remove apps from launchpad that I hardly ever use?

  • Recalculate sum of More than One Asset asset values

    Hi Team, Can you please guide whether there exists any T-code through which we can  Recalculate  sum of more than One Asset values  at single point of time. ex: iif we go asset master (AS02), in the Edit tab,recalucates values, in the asset master we

  • Question concerning variables in MDT's provider

    I have a simple script that copies a file to a share that my creds have access to.  Using the run powershell command in MDT 2013 it fails with access denied.  Does the powershell command not run under my creds. I've found some conversations regarding

  • Urgent--Problem in Date validations in Javascript.

    Hi , I am facing problem in date validation in javascript.The requirement is my PO delivery date should be greater than my Sysdate.For that I wrote Javascript programme as below- function sysValidate(item){                     var itemValue=item; //

  • Can Wi-fi channels be changed in iPhone?

    My iPhone recognizes other people's wi-fis in my building but not mine. The wi-fi is working or I would not be able to send this on my computer. Is there a way to adjust the settings on the iPhone other than just turning the wi-fi on? Thanks.