Exception in dataSource lookup

HI,
I get Exception in dataSource lookup everytime in my code. How to solve this problem.
I use java,tomcat and sql server
ERROR [ajp-apr-8009-exec-9] 08:37:18,898 com.general.EditBean - Exception in dataSource lookup.
java.sql.SQLException: Exception in dataSource lookup.
    at com.dbmodel.DSUtil.getConnection(DSUtil.java:41)
    at com.dbmodel.DSUtil.getConnection(DSUtil.java:49)
    at com.general.EditBean.getEditRecord(EditBean.java:91)
    at org.apache.jsp.lr.blendedtrainingplan_jsp._jspService(blendedtrainingplan_jsp.java:873)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
    at com.upside.lms.servlets.GlobalFilter.doFilter(GlobalFilter.java:54)
    at com.upside.lms.servlets.GlobalFilter.doFilter(GlobalFilter.java:38)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:208)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
    at com.googlecode.psiprobe.Tomcat60AgentValve.invoke(Tomcat60AgentValve.java:30)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
    at org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:197)
    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:565)
    at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:1812)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:722)
Caused by: javax.naming.NameNotFoundException: Name [null] is not bound in this Context. Unable to find [null].
    at org.apache.naming.NamingContext.lookup(NamingContext.java:820)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:154)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:831)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:154)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:831)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:168)
    at org.apache.naming.SelectorContext.lookup(SelectorContext.java:158)
    at javax.naming.InitialContext.lookup(InitialContext.java:411)
    at com.dbmodel.DSUtil.getConnection(DSUtil.java:39)
    ... 30 more

Hello,
"JNDI names are registered in the registry, if you try to access the name which is not registered or by the wrong format, you would get the javax.naming.NameNotFoundException"
Source:
http://www.javabeat.net/javax-naming-namenotfoundexception/
Please look at the following resource too:
http://stackoverflow.com/questions/6468109/javax-naming-namenotfoundexception-name-jdbc-is-not-bound-in-this-context
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

  • DataSource lookup: where to put it ?

    Hi all,
    I have the following question: what's the most correct method for DataSource lookup in a Session Bean? I look it up in the setSessionContext method:
    DataSource ds;
    public void setSessionContext(SessionContext ctx) { 
    this.ctx = ctx;
    ds = (javax.sql.DataSource) new InitialContext().lookup ("myPool");
    do you have other suggestions? for example I have read somewhere in this forum to use static-inizializers to populate instance variables of SSB....
    comments?
    thanks
    Francesco

    hi ,
    i am also facing the same problem ,
    if u had sol. for it, then try to give sol. for it
    but i have error as the following
    i am getting a problem (Exception)when my bean trys to connect with database.
    SQLException: java.sql.SQLException: Io exception: Connection refused(DESCRIPTI
    ON=(TMP=)(VSNNUM=135294976)(ERR=12505)(ERROR_STACK=(ERROR=(CODE=12505)(EMFI=4)))
    and i am using following in resource properties file
    jdbcDataSource.5.name=jdbc/TimeSpanDB
    jdbcDataSource.5.url=jdbc:oracle:thin:@myserver:1521:timeDB,scott,tiger;create=true
    and also i try out with following changes
    jdbcDataSource.5.name=jdbc/TimeSpanDB
    jdbcDataSource.5.url=jdbc:oracle:thin:@99.0.0.201:1521:timeDB,scott,tiger;create=true
    but both the time it is giving same sql connection exception
    waiting for ur sol.
    deepal

  • What's this?--Exception creating DataSource: org.hsql.jdbcDriver

    How to register the MS-SQL Server2000 DataSource in Tomcat4.04?
    Hi friends,
         I only have the MS SQL Server 2000 Database,and prog with jsp and Tomcat.
    Since the MS issue their JDBC Driver for SQL Server,I always use "DriverManager"
    to get the database connection,
    eg:
         Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
         Connection conn = DriverManager.getConnection
    ("jdbc:microsoft:sqlserver://server1:1433","username","password");
    Now I want to use "DataSource" to get connection in my prog,and I know it is necessary to register the DataSouce with JNDI in Tomcat before I can use it.
    But how to register and use the SQL Server DataSource in Tomcat4.04? I had tried some times and all failed,tomcat throws a exception like this:"javax.servlet.ServletException: Exception creating DataSource: org.hsql.jdbcDriver"
    what is "org.hsql.jdbcDriver"? may be it is tomcat's build in,but how can make my sql server driver work?
         Any Commnet Will Be Appreicate!
    ----Below is my fail trail when try to config the Tomcat--------------------
    Fellow the Tomcat's document,I modify the
    "$CATALINA_HOME/conf/server.xml" like this.
    <Context path="/MySite" docBase ="MySite" debug = "0" privileged = "true">
    <Resource name="jdbc/pubsDb" auth="Container"
    type="javax.sql.DataSource"/>
    <ResourceParams name="jdbc/pubsDb">
    <parameter>
              <name>user</name>
              <value>LJS</value>
         </parameter>
         <parameter>
              <name>password</name>
              <value>121212</value>
         </parameter>
    <parameter>
              <name>driverClassName</name>
    <value>com.microsoft.jdbcx.sqlserver.SQLServerDriver</value>
    </parameter>
    <parameter>
    <name>driverName</name>
    <value>jdbc:microsoft:sqlserver://localhost:1433/pubs</value>
    </parameter>
    </ResourceParams>     
    </Context>
    PS: the MSSQL Sever2000 has installed and had a user named "LJS" which password is 121212
    and default database is "pubs".
    Then,I modified the $CATALINA_HOME/webapps/MySite/WEB-INF/web.xml like this
         <resource-ref>
              <description>
                   Resource reference to a factory for java.sql.Connection
                   instances that may be used for talking to a particular
                   database that is configured in the server.xml file.
              </description>
              <res-ref-name>
                   jdbc/pubsDB
              </res-ref-name>
              <res-type>
                   javax.sql.DataSource
              </res-type>
              <res-auth>
                   Container
              </res-auth>
         </resource-ref>     
    finally I code a DB.jsp like this
    <%@ page content="text/html"%>
    <%@ page import="java.sql.*,javax.sql.*,java.naming.*"%>
    <%
         Context ctx = new InitialContext();
         DataSource ds = (DataSource)(new InitialContext().lookup("java:comp/env/jdbc/pubsDB"));
    %>
         after all done, I launch the Tomcat 4.0 and type "http://localhost:8080/MySite/DS.jsp" in
    my browser.
         then Tomcat throw exception like this:
    javax.servlet.ServletException: Exception creating DataSource: org.hsql.jdbcDriver
         at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:471)
         at org.apache.jsp.DS$jsp._jspService(DS$jsp.java:83)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:201)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
         at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027)
         at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
         at java.lang.Thread.run(Thread.java:484)
    root cause
    javax.naming.NamingException: Exception creating DataSource: org.hsql.jdbcDriver
         at
    org.apache.naming.factory.TyrexDataSourceFactory.getObjectInstance(TyrexDataSourceFactory.java:233)
         at org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFactory.java:165)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
         at org.apache.naming.NamingContext.lookup(NamingContext.java:835)
         at org.apache.naming.NamingContext.lookup(NamingContext.java:181)
         at org.apache.naming.NamingContext.lookup(NamingContext.java:822)
         at org.apache.naming.NamingContext.lookup(NamingContext.java:194)
         at org.apache.jsp.DS$jsp._jspService(DS$jsp.java:70)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:201)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
         at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
         at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
         at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027)
         at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
         at java.lang.Thread.run(Thread.java:484)

    Hi,
    don't know if you've already found a solution to this problem. Anyway, I had the same problem and the cause turned out to be a non-valid server.xml file.
    Here is my (working) server.xml:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!-- Example Server Configuration File --><!-- Note that component elements are nested corresponding to their
    parent-child relationships with each other --><!-- A "Server" is a singleton element that represents the entire JVM,
    which may contain one or more "Service" instances. The Server
    listens for a shutdown command on the indicated port.
    Note: A "Server" is not itself a "Container", so you may not
    define subcomponents such as "Valves" or "Loggers" at this level.
    --><Server debug="0" name="TestServer" port="8005" shutdown="SHUTDOWN">
    <!-- A "Service" is a collection of one or more "Connectors" that share
    a single "Container" (and therefore the web applications visible
    within that Container). Normally, that Container is an "Engine",
    but this is not required.
    Note: A "Service" is not itself a "Container", so you may not
    define subcomponents such as "Valves" or "Loggers" at this level.
    -->
    <!-- Define the Tomcat Stand-Alone Service -->
    <Service name="Tomcat-Standalone">
    <!-- A "Connector" represents an endpoint by which requests are received
    and responses are returned. Each Connector passes requests on to the
    associated "Container" (normally an Engine) for processing.
    By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
    You can also enable an SSL HTTP/1.1 Connector on port 8443 by
    following the instructions below and uncommenting the second Connector
    entry. SSL support requires the following steps:
    * Download and install JSSE 1.0.2 or later, and put the JAR files
    into "$JAVA_HOME/jre/lib/ext".
    * Edit "$JAVA_HOME/jre/lib/security/java.security" and add
    security.provider.2=com.sun.net.ssl.internal.ssl.Provider
    * Execute: keytool -genkey -alias tomcat -keyalg RSA
    with a password value of "changeit".
    By default, DNS lookups are enabled when a web application calls
    request.getRemoteHost(). This can have an adverse impact on
    performance, so you can disable it by setting the
    "enableLookups" attribute to "false". When DNS lookups are disabled,
    request.getRemoteHost() will return the String version of the
    IP address of the remote client.
    -->
    <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
    <Connector acceptCount="10" className="org.apache.catalina.connector.http.HttpConnector" connectionTimeout="60000" debug="0" enableLookups="true" maxProcessors="75" minProcessors="5" port="8080" redirectPort="8443"/>
    <!-- Note : To disable connection timeouts, set connectionTimeout value
    to -1 -->
    <!-- Define an SSL HTTP/1.1 Connector on port 8443 -->
    <!--
    <Connector className="org.apache.catalina.connector.http.HttpConnector"
    port="8443" minProcessors="5" maxProcessors="75"
    enableLookups="true"
         acceptCount="10" debug="0" scheme="https" secure="true">
    <Factory className="org.apache.catalina.net.SSLServerSocketFactory"
    clientAuth="false" protocol="TLS"/>
    </Connector>
    -->
    <!-- Define a Proxied HTTP/1.1 Connector on port 8081 -->
    <!-- See proxy documentation for more information about using this. -->
    <!--
    <Connector className="org.apache.catalina.connector.http.HttpConnector"
    port="8081" minProcessors="5" maxProcessors="75"
    enableLookups="true"
    acceptCount="10" debug="0" connectionTimeout="60000"
    proxyPort="80"/>
    -->
    <!-- Define a non-SSL HTTP/1.0 Test Connector on port 8082 -->
    <!--
    <Connector className="org.apache.catalina.connector.http10.HttpConnector"
    port="8082" minProcessors="5" maxProcessors="75"
    enableLookups="true" redirectPort="8443"
    acceptCount="10" debug="0"/>
    -->
    <!-- An Engine represents the entry point (within Catalina) that processes
    every request. The Engine implementation for Tomcat stand alone
    analyzes the HTTP headers included with the request, and passes them
    on to the appropriate Host (virtual host). -->
    <!-- Define the top level container in our container hierarchy -->
    <Engine debug="0" defaultHost="localhost" name="Standalone">
    <!-- The request dumper valve dumps useful debugging information about
    the request headers and cookies that were received, and the response
    headers and cookies that were sent, for all requests received by
    this instance of Tomcat. If you care only about requests to a
    particular virtual host, or a particular application, nest this
    element inside the corresponding <Host> or <Context> entry instead.
    For a similar mechanism that is portable to all Servlet 2.3
    containers, check out the "RequestDumperFilter" Filter in the
    example application (the source for this filter may be found in
    "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
    Request dumping is disabled by default. Uncomment the following
    element to enable it. -->
    <!--
    <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
    -->
    <!-- Global logger unless overridden at lower levels -->
    <Logger className="org.apache.catalina.logger.FileLogger" prefix="catalina_log." suffix=".txt" timestamp="true"/>
    <!-- Because this Realm is here, an instance will be shared globally -->
    <Realm className="org.apache.catalina.realm.MemoryRealm"/>
    <!-- Define the default virtual host -->
    <Host appBase="webapps" debug="0" name="localhost" unpackWARs="true">
    <!-- Normally, users must authenticate themselves to each web app
    individually. Uncomment the following entry if you would like
    a user to be authenticated the first time they encounter a
    resource protected by a security constraint, and then have that
    user identity maintained across all web applications contained
    in this virtual host. -->
    <!--
    <Valve className="org.apache.catalina.authenticator.SingleSignOn"
    debug="0"/>
    -->
    <!-- Access log processes all requests for this virtual host. By
    default, log files are created in the "logs" directory relative to
    $CATALINA_HOME. If you wish, you can specify a different
    directory with the "directory" attribute. Specify either a relative
    (to $CATALINA_HOME) or absolute path to the desired directory.
    -->
    <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" pattern="common" prefix="localhost_access_log." suffix=".txt"/>
    <!-- Logger shared by all Contexts related to this virtual host. By
    default (when using FileLogger), log files are created in the "logs"
    directory relative to $CATALINA_HOME. If you wish, you can specify
    a different directory with the "directory" attribute. Specify either a
    relative (to $CATALINA_HOME) or absolute path to the desired
    directory.-->
    <Logger className="org.apache.catalina.logger.FileLogger" directory="logs" prefix="localhost_log." suffix=".txt" timestamp="true"/>
    <!-- Define properties for each web application. This is only needed
    if you want to set non-default properties, or have web application
    document roots in places other than the virtual host's appBase
    directory. -->
    <!-- Tomcat Root Context -->
    <!--
    <Context path="" docBase="ROOT" debug="0"/>
    -->
    <Context docBase="D:\Program Files\IBM\WebSphere Studio\workspaces\Test\StudentWEB\Web Content"
                   path="/StudentWEB"
                   reloadable="true"
                   source="com.ibm.etools.webtools.server:StudentWEB">
                   <Logger className="org.apache.catalina.logger.FileLogger"
         prefix="localhost_DBTest_log." suffix=".txt"
         timestamp="true"/>
                   <Resource name="jdbc/TestDB"
              auth="Container"
    type="javax.sql.DataSource"/>
                   <ResourceParams name="jdbc/TestDB">
                   <parameter>
                        <name>factory</name>
                        <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
                   </parameter>
                   <!-- Maximum number of dB connections in pool. Make sure you
              configure your mysqld max_connections large enough to handle
              all of your db connections. Set to 0 for no limit.
              -->
                   <parameter>
                        <name>maxActive</name>
                        <value>100</value>
                   </parameter>
                   <!-- Maximum number of idle dB connections to retain in pool.
              Set to 0 for no limit.
              -->
                   <parameter>
                        <name>maxIdle</name>
                        <value>30</value>
                   </parameter>
                   <!-- Maximum time to wait for a dB connection to become available
              in ms, in this example 10 seconds. An Exception is thrown if
              this timeout is exceeded. Set to -1 to wait indefinitely.
              -->
                   <parameter>
                        <name>maxWait</name>
                        <value>10000</value>
                   </parameter>
                   <!-- MySQL dB username and password for dB connections -->
                   <parameter>
                        <name>username</name>
                        <value>admin</value>
                   </parameter>
                   <parameter>
                        <name>password</name>
                        <value>admin</value>
                   </parameter>
                   <!-- Class name for mm.mysql JDBC driver -->
                   <parameter>
                        <name>driverClassName</name>
                        <value>org.gjt.mm.mysql.Driver</value>
                   </parameter>
                   <!-- The JDBC connection url for connecting to your MySQL dB.
              The autoReconnect=true argument to the url makes sure that the
              mm.mysql JDBC Driver will automatically reconnect if mysqld closed the
              connection. mysqld by default closes idle connections after 8 hours.
              -->
                   <parameter>
                        <name>url</name>
                        <value>jdbc:mysql://localhost:3306/javatest?autoReconnect=true</value>
                   </parameter>
                   </ResourceParams>
         </Context>
    </Host>
    </Engine>
    </Service>
    <!-- The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0
    as its servlet container. Please read the README.txt file coming with
    the WebApp Module distribution on how to build it.
    (Or check out the "jakarta-tomcat-connectors/webapp" CVS repository)
    To configure the Apache side, you must ensure that you have the
    "ServerName" and "Port" directives defined in "httpd.conf". Then,
    lines like these to the bottom of your "httpd.conf" file:
    LoadModule webapp_module libexec/mod_webapp.so
    WebAppConnection warpConnection warp localhost:8008
    WebAppDeploy examples warpConnection /examples/
    The next time you restart Apache (after restarting Tomcat, if needed)
    the connection will be established, and all applications you make
    visible via "WebAppDeploy" directives can be accessed through Apache.
    -->
    <!-- Define an Apache-Connector Service -->
    <Service name="Tomcat-Apache">
    <Connector acceptCount="10" className="org.apache.catalina.connector.warp.WarpConnector" debug="0" enableLookups="true" maxProcessors="75" minProcessors="5" port="8008"/>
    <!-- Replace "localhost" with what your Apache "ServerName" is set to -->
    <Engine appBase="webapps" className="org.apache.catalina.connector.warp.WarpEngine" debug="0" name="Apache">
    <!-- Global logger unless overridden at lower levels -->
    <Logger className="org.apache.catalina.logger.FileLogger" prefix="apache_log." suffix=".txt" timestamp="true"/>
    <!-- Because this Realm is here, an instance will be shared globally -->
    <Realm className="org.apache.catalina.realm.MemoryRealm"/>
    </Engine>
    </Service>
    </Server>
    My web.xml looks like this:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!DOCTYPE web-app PUBLIC
    "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd">
    <web-app>
    <description>MySQL Test App</description>
    <servlet>
         <servlet-name>TestServlet</servlet-name>
         <display-name>TestServlet</display-name>
         <servlet-class>TestServlet</servlet-class>
    </servlet>
    <servlet-mapping>
         <servlet-name>TestServlet</servlet-name>
         <url-pattern>/TestServlet</url-pattern>
    </servlet-mapping>
    <resource-ref>
    <description>DB Connection</description>
    <res-ref-name>jdbc/TestDB</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </web-app>
    You can of course leave out the comments if you want...
    Please let me know if this works on [email protected].
    Kind regards,
    Johan

  • Using Portable datasource lookup for a java client in OC4J 10g

    Hi,
    I'm in the process of porting a standalone java client to j2ee. At the moment I have a thick java client which uses jndi to access a global datasource configured on the OC4J server (10.1.2.0.2) and it works fine.
    Using the 'Services Guide' I decided the next step was to deploy the client as a J2EE application. At the moment the j2ee application only contains the descriptors (i.e application-client.xml and orion-application-client.xml packaged under META-INF in a .jar. This is, in turn, packaged in an .ear along with application.xml (again under META-INF.)
    This is where I'm hitting problems. The following config produces a 'javax.naming.NameNotFoundException' error
    application.xml
    <application>
         <display-name>appName</display-name>
         <description>appDescription</description>
    </application>
    application-client.xml :-
    <application-client>
         <display-name>appName</display-name>
         <resource-ref>
              <res-ref-name>jdbc/MaptoTest</res-ref-name>
              <res-type>javax.sql.DataSource</res-type>
              <res-auth>Container</res-auth>
         </resource-ref>
    </application-client>
    orion-application-client.xml :-
    <orion-application-client>
         <resource-ref-mapping name="jdbc/MaptoTest" location="jdbc/Test"/>
    </orion-application-client>
    jndi.properties :-
    java.naming.factory.initial=com.evermind.server.ApplicationClientInitialContextFactory
    java.naming.provider.url=opmn:ormi://<machine>:6004:<OC4J_INSTANCE>/appName
    java.naming.security.principal=<USERNAME>
    java.naming.security.credentials=<PASSWORD>
    client.class
    ctx = new InitialContext();
    ds = (DataSource)ctx.lookup("java:comp/env/jdbc/jdbc/MaptoTest"));
    "jdbc/Test" was configured through OAS and is present in data-sources.xml (it is the ejb-location property).
    I'm running the client through Jdeveloper. I've used SJSAS previously and was use to configuring and deploying a application module through it's own tool. SJSAS also has a tool (appclient) for running the client. Is there something similar I should be using in OC4J?
    The services guide only mentions web.xml and ejb-jar for portable datasource lookup but I assume it's also possible using application-client.xml.
    It seems to me that my descriptors don't mention the j2ee application explicitly. Am I missing an entry in one of the xml descriptors. Any help would be appreciated this is driving me crazy!
    Thanks in advance for any advice.

    Hi Geoff,
    The configurations for your client.xml files look ok. Question: where did you configure the datasources.xml i.e. under j2ee/<OC4J_Name>/config or under the application-deployments/<appname>, kindly check and let us know.
    Thanks,
    Deepak

  • NameNotFoundException for DataSource lookup

    Hi,
    I have a requirement where i need to push message from a client code (deployed in oc4j 10.1.3) to a remote queue which is deployed on weblogic server. i have used
    Context.INITIAL_CONTEXT_FACTORY = "weblogic.jndi.WLInitialContextFactory". I could send the message to the weblogic 9.2 server queue from oc4j 10.1.3 client code. But all my datasources lookups are failing in oc4j container.
    My lookup code looks as follows : context.lookup("java:comp/env/jdbc/DB");
    If the lookup is done using "jdbc/DB" , it succeeds. But currently, context.lookup("java:comp/env/jdbc/DB"); code is available in 700 places. So it is not possible to change the code.
    Any suggestions why existing data source lookup fails if initial context is set to weblogic specific. I also closed and nullified the initialcontext object related to weblogic server after usage.
    Regards,
    Prashant

    Your code is this:
    javax.sql.DataSource ds = (javax.sql.DataSource) context2.lookup ("mydbsrc");So you're trying to find your DataSource at JNDI location "mydbsrc".
    Your configuration is this:
    <JDBCTxDataSource JNDIName="myserver" Name="mydbsrc" PoolName="MyJDBC Connection Pool" Targets="myserver" />
    So your DataSource is at JNDI location "myserver".
    Change the configuration so that your DataSource's JNDIName is "mydbsrc":
    <JDBCTxDataSource JNDIName="mydbsrc" Name="mydbsrc" PoolName="MyJDBC Connection Pool" Targets="myserver" />
    You can do this via the WebLogic console if you want.
    Hope this helps.

  • Oracle datasource lookup in JBOSS application server

    Hi friends
    i have the below problem while configuring the datasource in JBOSS for oracle pls any body can help me out..........
    i just want to create a data source for oracle in JBOSS 3.2.5 application server and i want to access that datasource from my session bean while accessing it cant finding the JNDI name of the datasource my oracle-ds.xml code is like as below
    <local-tx-datasources>
    <jndi-name>java:OracleDS</jndi-name>
    <use-java-context>false</use-java-context>
    <connection-url>jdbc:oracle:thin:@localhost:1521:EPS</connection-url>
    <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
    <user-name>system</user-name>
    manager
    </local-tx-datasources> my session bean method is like as below
    public void businessMethod1(){
    try{
    javax.naming.Context ctx = new javax.naming.InitialContext();
    javax.sql.DataSource ds = (javax.sql.DataSource) ctx.lookup("OracleDS");
    java.sql.Connection con = ds.getConnection();
    java.sql.PreparedStatement ps = con.prepareStatement("select * from employee");
    java.sql.ResultSet rs = ps.executeQuery();
    while(rs.next()){
    System.out.println("Employee ID "+rs.getInt("empid")+"Employee Name "+rs.getString("ename")+"Employee Designation "+rs.getString("designation"));
    }catch(Exception e){
    e.printStackTrace();
    } but the error i am getting wasl like as below
    14:14:14,039 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
    14:14:14,164 INFO [ChannelSocket] JK2: ajp13 listening on /0.0.0.0:8009
    14:14:14,164 INFO [JkMain] Jk running ID=0 time=0/47 config=null
    14:15:00,883 INFO [STDOUT] javax.naming.NameNotFoundException: OracleDS not bound
    14:15:00,883 INFO [STDOUT] at org.jnp.server.NamingServer.getBinding(NamingServer.java:495)
    14:15:00,883 INFO [STDOUT] at org.jnp.server.NamingServer.getBinding(NamingServer.java:503)
    14:15:00,883 INFO [STDOUT] at org.jnp.server.NamingServer.getObject(NamingServer.java:509)
    14:15:00,883 INFO [STDOUT] at org.jnp.server.NamingServer.lookup(NamingServer.java:282)
    14:15:00,883 INFO [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:530)
    14:15:00,883 INFO [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:509)
    14:15:00,883 INFO [STDOUT] at javax.naming.InitialContext.lookup(InitialContext.java:347)
    14:15:00,883 INFO [STDOUT] at com.ness.training.ejb.FirstSessionBean.businessMethod1(FirstSessionBean.java:13)
    14:15:00,883 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    14:15:00,883 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    14:15:00,883 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    14:15:00,883 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:324)
    14:15:00,883 INFO [STDOUT] at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.j
    ava:683)
    14:15:00,883 INFO [STDOUT] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterce
    ptor.java:185)
    14:15:00,883 INFO [STDOUT] at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterc
    eptor.java:72)
    14:15:00,883 INFO [STDOUT] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:84)
    14:15:00,883 INFO [STDOUT] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:315)
    14:15:00,883 INFO [STDOUT] at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:148)
    14:15:00,883 INFO [STDOUT] at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:120)
    14:15:00,883 INFO [STDOUT] at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
    14:15:00,883 INFO [STDOUT] at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:1
    22)
    14:15:00,883 INFO [STDOUT] at org.jboss.ejb.StatelessSessionContainer.internalInvoke(StatelessSessionContainer.java:331)
    14:15:00,883 INFO [STDOUT] at org.jboss.ejb.Container.invoke(Container.java:723)
    14:15:00,883 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    14:15:00,883 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    14:15:00,883 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    14:15:00,883 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:324)
    14:15:00,883 INFO [STDOUT] at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
    14:15:00,883 INFO [STDOUT] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
    14:15:00,883 INFO [STDOUT] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
    14:15:00,883 INFO [STDOUT] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    14:15:00,883 INFO [STDOUT] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
    14:15:00,883 INFO [STDOUT] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
    14:15:00,883 INFO [STDOUT] at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:360)
    14:15:00,883 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    14:15:00,883 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    14:15:00,883 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    14:15:00,883 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:324)
    14:15:00,883 INFO [STDOUT] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
    14:15:00,883 INFO [STDOUT] at sun.rmi.transport.Transport$1.run(Transport.java:148)
    14:15:00,883 INFO [STDOUT] at java.security.AccessController.doPrivileged(Native Method)
    14:15:00,883 INFO [STDOUT] at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
    14:15:00,883 INFO [STDOUT] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
    14:15:00,883 INFO [STDOUT] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
    14:15:00,883 INFO [STDOUT] at java.lang.Thread.run(Thread.java:536)

    make the changes like this.
    javax.sql.DataSource ds = (javax.sql.DataSource) ctx.lookup("java:/OracleDS");
    Regards
    vanan

  • Problem with DataSource lookup(Urgent)

    HI,
    I am facing a unique problem. I am migratinga application from weblogic to WAS. In a web module I wrote a normal class which will get the initial context of the server and create a connection object for the use of servlets. It is working fine in weblogic but when i have deployed the samething in WAS it is giving exception
    com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of MLJNDI.
    where MLJNDI is my DataSource jndi name.
    can anybody suggest me the solution?.This is very urgent.
    Thanks in advance.
    Ashok.

    It is not clear if you already created a Datasource to a specified database. This can be done via the Visual Admin.
    Services --> JDBC Connector. There you can upload vendor specific drivers and bind it to a database.
    This is possible usings the standards. JDBC 1.x and 2.0 way.
    Success.

  • DataSource lookup error in bpel 10.1.3

    Hi,
    i have a java client program in jdeveloper 10.1.3 from which i am trying to connect bpel 10.1.3 datasource but it is not able to find the datasource even it is able to connect bpel server RMI port where all datasouces has been defined.
    as part of code is-
    Hashtable env = new Hashtable();
    env.put("java.naming.factory.initial",
    "com.evermind.server.ApplicationClientInitialContextFactory");
    env.put("java.naming.provider.url", "ormi://localhost:12401");
    \\ loacl bpel server RMI port connection
    env.put("java.naming.security.principal", "oc4jadmin"); \\username
    env.put("java.naming.security.credentials", "sadmin01"); \\Password
    context = new InitialContext(env);
    \\Till here it is able to create initial context using hashtable
    dataSource = (DataSource) context.lookup("jdbc/XRefFunctionsSource");
    \\ Here it failed to lookup datasource
    I had defined the datasouce in bpel sever through enterprise manager.
    I tried to connect all by default datasources which are there initially but it failed.
    Please tell any suggestion to change in my code to connect datasource.
    Thanks.

    This is the complete piece of code in which i am trying to get DB Connection from jdeveloper 10.1.3 -
    public class Test
    public Test() throws Exception
    static Test instance= null;
    Context context;
    Connection connection;
    DataSource dataSource;
    try{
    * Create access to the naming context, initialized from the
    * Hashtable parameter to the constructor.
    Hashtable env = new Hashtable();
    env.put("java.naming.factory.initial",
    "com.evermind.server.ApplicationClientInitialContextFactory");
    env.put("java.naming.provider.url", "ormi://localhost:12401");
    env.put("java.naming.security.principal", "oc4jadmin");
    env.put("java.naming.security.credentials", "sadmin01");
    context = new InitialContext(env);
    System.out.println("InitialContext created using Hashtable...");
    * Lookup the jdbc/BPELSamplesDataSource object.
    dataSource = (DataSource)
    context.lookup("jdbc/XRefFunctionsSource");
    System.out.println("jdbc/XRefFunctionsSource found...");
    System.out.println("Connecting to database ...");
    //dataSource =
    connection = dataSource.getConnection("orabpel","orabpel");
    System.out.println("Got database connection ...");
    catch(Exception e)
    System.out.println("" + e);
    throw e;
    private static Test instance() throws Exception
    if (instance== null)
    instance = new Test();
    return instance;
    private Connection getConnection() throws Exception
    return connection;
    public static void main(String[] args)
    Connection con = Test.instance().getConnection();
    I tried a lot with different options but still it is not working..
    As i told the same code is working for bpel 10.1.2 using jdeveloper 10.1.2.
    Is there any other way to get DB connection here?
    Thanks,
    Anil
    Message was edited by:
    user516357

  • Datasource Lookup from WSAD using POJO - CastException looking up DB2 Data

    I try to look up datasource from WSAD test server using stand alone POJO.
    Code is like:
    Hashtable properties = new Hashtable();
    properties.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
    properties.put(Context.PROVIDER_URL, serviceURL);
    properties.put(Context.PROVIDER_URL, "iiop://localhost:2813");
    Context context = new InitialContext(properties);
    ds = (DataSource) context.lookup("jdbc/myDS");
    Context and datasource are set properly.
    I get exception below when I look up datasource:
    Exception in thread "P=646891 =0:CT" java.lang.ClassCastException: javax.naming.Reference
    I think additional jar files are needed in class path.
    What additional jar files do I need in build path to look up datasource?
    I am using DB2. Datasource is properly configured in WSAD test server.

    Refer to this article.
    http://www-128.ibm.com/developerworks/websphere/library/techarticles/0310_bhogal/bhogal.html
    It provides all the information you need to perform a JNDI lookup. Quoting from the artice;
    To execute our external Java application, make sure your environment is prepared and use a Java command of the following form to invoke the client application:
    %JAVA_HOME%/bin/java -Xbootclasspath/p:%WAS_BOOTCLASSPATH%
    -classpath <list of the referenced jars, classes, and resource directories>
    -Djava.ext.dirs=%WAS_EXT_DIRS%
    -Djava.naming.provider.url=iiop://<server:orb port>
    -Djava.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory
    %SERVER_ROOT% %CLIENTSAS% <fully qualified main class of the application client>;

  • Exception in RFC Lookup

    Hi Experts,
    I have a query in Graphical RFC Lookup function.
    I am working on Pi 7.1 and scenario is File to Idoc.
    In the file, material number is coming, and I have to find out the corresponding Customer number from ECC table using RFC Lookup.
    I know how to use RFC lookup.
    But here issue is, if Customer Number is not maintained in the ECC table for the incoming material number, then exception should be thrown and processing should be stopped at that moment.
    Please tell me how to throw this exception and hence fail the mapping.
    -Supriya.

    Hi ,
    I guess you want to fail the message transformation at Message mapping level with Red Error in Monitoring , If LOOKUP return Nothing ...
    What You can Do Is , Instead of RFC LOOKUP Function , Use UDF Based RFC LOOKUP , and Inside UDF you can easily raise exception.
    Or
    In Grapphical Message mapping pass the result from RFCLOOKUP To a 1..1 Target , if during transfermation if 1..1 node will not get any value , so mapping will get failed automatoicaly ..
    hope the idea Helps
    regards
    PS

  • Raising exceptions in database lookups in message mapping

    Hi
       We have been able to successfully do a database lookup from within a message mapping - thanks to weblogs already existing out there. However, we have requirement that states that - if the lookup fails ( failure to connect to DB / data retrieved is null ) , then the mapping should fail - and an exception raised.
    How can we go about doing this from within the java code - of the mapping lookup ?
    Any correct pointers /solutions to achieve this will be rewarded rightaway. Thanks in advance for your time.

    Hi,
    you can use Alessandro's way:
    /people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
    this way you can throw smart exceptions:)
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • RuntimePermission exception on RMI lookup on a signed Applet

    Hi everybody,
    Here is my problem : I want to call an ejb from my applet, using RMI.
    But, as it is an applet, I get a security exception when I make the naming lookup :
    java.security.AccessControlException: access denied (java.lang.RuntimePermission accessClassInPackage.sun.rmi.server)
    I have been wandering for two days in the Java Sun sites and forums to find out how to pass through this problem.
    Too many information is no information : I am not sure to have the correct answer; but here is what I have found :
    All I have to do is to make a self-signed Applet (for testing purpose, before having a real certificate), using keytool and jarsigner, and use it with Java Plugin. Doing that will give AllPermission to the signed code, if the user agrees through a Java Plugin dialog.
    (see http://java.sun.com/products/plugin/1.2/docs/nsobjsigning.html)
    But... that doesn't work (who said 'of course' ?) :
    I get the granting dialog, and even if I agree, I always get the same java.lang.RuntimePermission accessClassInPackage exception.
    The strange think is that I tried to write a file on the client machine for testing the permission, and that works fine with this same signed applet.
    I think that AllPermission implies FilePermission and also RuntimePermission, doesn't ?
    Is this behaviour related to my self-signed certificate ? (in this case, why can i write a file ?)
    What am I missing ?
    Any help will be welcome,
    many thanks
    bernard
    PS. : Of course, i don't want the user to modify its java policy or security configuration as it is often "mission impossible".

    Sorry, i forgot : i am using Java Plugin v 1.3.1_02
    B

  • Exception in bean lookup

    I get the below exception from bean client accessing a stateless session bean.What is the possible reason
    An unexpected exception has been detected in native code outside the VM.
    Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x48205586
    Function name=(N/A)
    Library=(N/A)
    NOTE: We are unable to locate the function name symbol for the error
    just occurred. Please refer to release documentation for possible
    reason and solutions.
    Current Java thread:
         at com.kivasoft.eb.EBActivatorCB.getEBHomenative(Native Method)
         at com.kivasoft.eb.EBActivatorCB.getEBHome(Unknown Source)
         at com.netscape.server.ejb.EjbContext.createHomeRef(Unknown Source)
         at com.netscape.server.ejb.EjbContext.getHomeRef(Unknown Source)
         at com.netscape.server.ejb.EjbContext.lookup(Unknown Source)
         at com.netscape.server.jndi.RootContext.lookup(Unknown Source)
         at com.netscape.server.jndi.RootContext.lookup(Unknown Source)
         at javax.naming.InitialContext.lookup(InitialContext.java:350)
         at com.agent.HelloworldEARReferenceProvider.getGreeterHome(HelloworldEARReferenceProvider.java:61)
         at com.agent.HelloworldEARReferenceProvider.getGreeter(HelloworldEARReferenceProvider.java:25)
         at com.agent.GreeterMBean.getGreeting(GreeterMBean.java:26)
         at java.lang.reflect.Method.invoke(Native Method)
         at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:1273)
         at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:906)
         at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:782)
         at javax.management.MBeanServerImpl.getAttribute(MBeanServerImpl.java:925)
         at com.adventnet.manageengine.ruleengine.impl.ConditionImpl.execute(ConditionImpl.java:313)
         at com.adventnet.manageengine.ruleengine.impl.RuleImpl.execute(RuleImpl.java:244)
         at com.adventnet.manageengine.ruleengine.impl.RuleImpl.run(RuleImpl.java:132)
         at com.adventnet.agent.utilities.scheduler.WorkerThread.run(WorkerThread.java:60)
    Dynamic libraries:
    Local Time = Wed Nov 27 12:03:20 2002
    Elapsed Time = 29
    # The exception above was detected in native code outside the VM
    # Java VM: Java HotSpot(TM) Server VM (1.3.1_02-b02 mixed mode)

    Does anyone have the fix for this issue? I am also getting the txt files. I have enclosed below:
    Current Java thread:
         at sun.plugin.services.WPlatformService.waitEvent(Native Method)
         at sun.plugin.viewer.frame.IExplorerEmbeddedFrame.destroy(Unknown Source)
    Dynamic libraries:
    0x00400000 - 0x00419000      C:\Program Files\Internet Explorer\iexplore.exe
    0x7C900000 - 0x7C9B0000      C:\WINDOWS\system32\ntdll.dll
    0x7C800000 - 0x7C8F4000      C:\WINDOWS\system32\kernel32.dll
    0x77C10000 - 0x77C68000      C:\WINDOWS\system32\msvcrt.dll
    0x77D40000 - 0x77DD0000      C:\WINDOWS\system32\USER32.dll
    0x77F10000 - 0x77F57000      C:\WINDOWS\system32\GDI32.dll
    0x77F60000 - 0x77FD6000      C:\WINDOWS\system32\SHLWAPI.dll
    0x77DD0000 - 0x77E6B000      C:\WINDOWS\system32\ADVAPI32.dll
    0x77E70000 - 0x77F01000      C:\WINDOWS\system32\RPCRT4.dll
    0x77760000 - 0x778CE000      C:\WINDOWS\system32\SHDOCVW.dll
    0x77A80000 - 0x77B14000      C:\WINDOWS\system32\CRYPT32.dll
    0x77B20000 - 0x77B32000      C:\WINDOWS\system32\MSASN1.dll
    0x754D0000 - 0x75550000      C:\WINDOWS\system32\CRYPTUI.dll
    0x76C30000 - 0x76C5E000      C:\WINDOWS\system32\WINTRUST.dll
    0x76C90000 - 0x76CB8000      C:\WINDOWS\system32\IMAGEHLP.dll
    0x77120000 - 0x771AC000      C:\WINDOWS\system32\OLEAUT32.dll
    0x774E0000 - 0x7761D000      C:\WINDOWS\system32\ole32.dll
    0x5B860000 - 0x5B8B4000      C:\WINDOWS\system32\NETAPI32.dll
    0x771B0000 - 0x77256000      C:\WINDOWS\system32\WININET.dll
    0x76F60000 - 0x76F8C000      C:\WINDOWS\system32\WLDAP32.dll
    0x77C00000 - 0x77C08000      C:\WINDOWS\system32\VERSION.dll
    0x773D0000 - 0x774D2000      C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
    0x7C9C0000 - 0x7D1D5000      C:\WINDOWS\system32\SHELL32.dll
    0x5D090000 - 0x5D127000      C:\WINDOWS\system32\comctl32.dll
    0x5AD70000 - 0x5ADA8000      C:\WINDOWS\system32\uxtheme.dll
    0x74720000 - 0x7476B000      C:\WINDOWS\system32\MSCTF.dll
    0x75F80000 - 0x7607D000      C:\WINDOWS\system32\BROWSEUI.dll
    0x20000000 - 0x20012000      C:\WINDOWS\system32\browselc.dll
    0x77B40000 - 0x77B62000      C:\WINDOWS\system32\appHelp.dll
    0x76FD0000 - 0x7704F000      C:\WINDOWS\system32\CLBCATQ.DLL
    0x77050000 - 0x77115000      C:\WINDOWS\system32\COMRes.dll
    0x77260000 - 0x77300000      C:\WINDOWS\system32\urlmon.dll
    0x77FE0000 - 0x77FF1000      C:\WINDOWS\system32\Secur32.dll
    0x77A20000 - 0x77A74000      C:\WINDOWS\System32\cscui.dll
    0x76600000 - 0x7661D000      C:\WINDOWS\System32\CSCDLL.dll
    0x77920000 - 0x77A13000      C:\WINDOWS\system32\SETUPAPI.dll
    0x10000000 - 0x1012A000      c:\program files\google\googletoolbar2.dll
    0x71AD0000 - 0x71AD9000      C:\WINDOWS\system32\WSOCK32.dll
    0x71AB0000 - 0x71AC7000      C:\WINDOWS\system32\WS2_32.dll
    0x71AA0000 - 0x71AA8000      C:\WINDOWS\system32\WS2HELP.dll
    0x76B40000 - 0x76B6D000      C:\WINDOWS\system32\WINMM.dll
    0x76380000 - 0x76385000      C:\WINDOWS\system32\MSIMG32.dll
    0x59A60000 - 0x59B01000      C:\WINDOWS\system32\DBGHELP.DLL
    0x76EE0000 - 0x76F1C000      C:\WINDOWS\system32\RASAPI32.DLL
    0x76E90000 - 0x76EA2000      C:\WINDOWS\system32\rasman.dll
    0x76EB0000 - 0x76EDF000      C:\WINDOWS\system32\TAPI32.dll
    0x76E80000 - 0x76E8E000      C:\WINDOWS\system32\rtutils.dll
    0x77C70000 - 0x77C93000      C:\WINDOWS\system32\msv1_0.dll
    0x76D60000 - 0x76D79000      C:\WINDOWS\system32\iphlpapi.dll
    0x722B0000 - 0x722B5000      C:\WINDOWS\system32\sensapi.dll
    0x769C0000 - 0x76A73000      C:\WINDOWS\system32\USERENV.dll
    0x01310000 - 0x01398000      C:\WINDOWS\system32\shdoclc.dll
    0x68000000 - 0x68051000      C:\Program Files\Yahoo!\Companion\Installs\cpn\ycomp5_5_5_0.dll
    0x015A0000 - 0x015AE000      C:\Program Files\Adobe\Acrobat 7.0\ActiveX\AcroIEHelper.dll
    0x7C340000 - 0x7C396000      C:\WINDOWS\system32\MSVCR71.dll
    0x015E0000 - 0x015FB000      C:\WINDOWS\system32\dla\tfswshx.dll
    0x01600000 - 0x0160F000      C:\WINDOWS\system32\tfswapi.dll
    0x01610000 - 0x0164A000      C:\WINDOWS\system32\dla\tfswcres.dll
    0x75E90000 - 0x75F40000      C:\WINDOWS\system32\SXS.DLL
    0x016C0000 - 0x01985000      C:\WINDOWS\system32\xpsp2res.dll
    0x75CF0000 - 0x75D81000      C:\WINDOWS\system32\mlang.dll
    0x71A50000 - 0x71A8F000      C:\WINDOWS\system32\mswsock.dll
    0x662B0000 - 0x66308000      C:\WINDOWS\system32\hnetcfg.dll
    0x71A90000 - 0x71A98000      C:\WINDOWS\System32\wshtcpip.dll
    0x01F30000 - 0x021F6000      C:\WINDOWS\system32\msi.dll
    0x019A0000 - 0x019B9000      c:\progra~1\mcafee.com\vso\McVSSkt.dll
    0x76FC0000 - 0x76FC6000      C:\WINDOWS\system32\rasadhlp.dll
    0x76F20000 - 0x76F47000      C:\WINDOWS\system32\DNSAPI.dll
    0x76FB0000 - 0x76FB8000      C:\WINDOWS\System32\winrnr.dll
    0x605D0000 - 0x605D9000      C:\WINDOWS\system32\mslbui.dll
    0x7DC30000 - 0x7DF1F000      C:\WINDOWS\System32\mshtml.dll
    0x746C0000 - 0x746E7000      C:\WINDOWS\System32\msls31.dll
    0x76BF0000 - 0x76BFB000      C:\WINDOWS\System32\PSAPI.DLL
    0x746F0000 - 0x7471A000      C:\WINDOWS\System32\msimtf.dll
    0x5C2C0000 - 0x5C300000      C:\WINDOWS\ime\sptip.dll
    0x74C80000 - 0x74CAC000      C:\WINDOWS\system32\OLEACC.dll
    0x76080000 - 0x760E5000      C:\WINDOWS\system32\MSVCP60.dll
    0x02B20000 - 0x02B31000      C:\WINDOWS\IME\SPGRMR.DLL
    0x02B40000 - 0x02B9B000      C:\Program Files\Common Files\Microsoft Shared\INK\SKCHUI.DLL
    0x75C50000 - 0x75CBE000      C:\WINDOWS\System32\jscript.dll
    0x66E50000 - 0x66E90000      C:\WINDOWS\System32\iepeers.dll
    0x73000000 - 0x73026000      C:\WINDOWS\System32\WINSPOOL.DRV
    0x73300000 - 0x73367000      C:\WINDOWS\System32\vbscript.dll
    0x73DD0000 - 0x73ECE000      C:\WINDOWS\System32\MFC42.DLL
    0x30000000 - 0x30222000      C:\WINDOWS\system32\Macromed\Flash\Flash8.ocx
    0x763B0000 - 0x763F9000      C:\WINDOWS\system32\comdlg32.dll
    0x72D20000 - 0x72D29000      C:\WINDOWS\system32\wdmaud.drv
    0x72D10000 - 0x72D18000      C:\WINDOWS\system32\msacm32.drv
    0x77BE0000 - 0x77BF5000      C:\WINDOWS\system32\MSACM32.dll
    0x77BD0000 - 0x77BD7000      C:\WINDOWS\system32\midimap.dll
    0x76200000 - 0x76271000      C:\WINDOWS\System32\mshtmled.dll
    0x04CB0000 - 0x04CCC000      C:\Program Files\Adobe\Acrobat 7.0\ActiveX\PDFShell.dll
    0x5DE30000 - 0x5DF07000      C:\Program Files\Common Files\Microsoft Shared\VGX\vgx.dll
    0x76B20000 - 0x76B31000      C:\WINDOWS\system32\ATL.DLL
    0x4EC50000 - 0x4EDF3000      C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.2600.2180_x-ww_522f9f82\gdiplus.dll
    0x767F0000 - 0x76817000      C:\WINDOWS\system32\schannel.dll
    0x0FFD0000 - 0x0FFF8000      C:\WINDOWS\system32\rsaenh.dll
    0x68100000 - 0x68124000      C:\WINDOWS\system32\dssenh.dll
    0x76C00000 - 0x76C2E000      C:\WINDOWS\system32\credui.dll
    0x5E0C0000 - 0x5E0CD000      C:\WINDOWS\system32\pstorec.dll
    0x71B20000 - 0x71B32000      C:\WINDOWS\system32\MPR.dll
    0x75F60000 - 0x75F67000      C:\WINDOWS\System32\drprov.dll
    0x71C10000 - 0x71C1E000      C:\WINDOWS\System32\ntlanman.dll
    0x71CD0000 - 0x71CE7000      C:\WINDOWS\System32\NETUI0.dll
    0x71C90000 - 0x71CD0000      C:\WINDOWS\System32\NETUI1.dll
    0x71C80000 - 0x71C87000      C:\WINDOWS\System32\NETRAP.dll
    0x71BF0000 - 0x71C03000      C:\WINDOWS\System32\SAMLIB.dll
    0x75F70000 - 0x75F79000      C:\WINDOWS\System32\davclnt.dll
    0x73D70000 - 0x73D83000      C:\WINDOWS\System32\shgina.dll
    0x75970000 - 0x75A67000      C:\WINDOWS\system32\MSGINA.dll
    0x76360000 - 0x76370000      C:\WINDOWS\system32\WINSTA.dll
    0x74320000 - 0x7435D000      C:\WINDOWS\system32\ODBC32.dll
    0x01C00000 - 0x01C17000      C:\WINDOWS\system32\odbcint.dll
    0x092D0000 - 0x09349000      C:\WINDOWS\system32\Audiodev.dll
    0x086C0000 - 0x08904000      C:\WINDOWS\system32\WMVCore.DLL
    0x070D0000 - 0x0710B000      C:\WINDOWS\system32\WMASF.DLL
    0x593F0000 - 0x59482000      C:\WINDOWS\system32\wiashext.dll
    0x73BA0000 - 0x73BB3000      C:\WINDOWS\System32\sti.dll
    0x74AE0000 - 0x74AE7000      C:\WINDOWS\System32\CFGMGR32.dll
    0x055B0000 - 0x055B5000      C:\WINDOWS\system32\xpsp3res.dll
    0x69000000 - 0x6900E000      C:\WINDOWS\system32\Macromed\Common\SwSupport.dll
    0x6D430000 - 0x6D43A000      C:\WINDOWS\System32\ddrawex.dll
    0x73760000 - 0x737A9000      C:\WINDOWS\System32\DDRAW.dll
    0x73BC0000 - 0x73BC6000      C:\WINDOWS\System32\DCIMAN32.dll
    0x76820000 - 0x76834000      C:\WINDOWS\system32\HLINK.DLL
    0x76390000 - 0x763AD000      C:\WINDOWS\system32\imm32.dll
    0x71D40000 - 0x71D5C000      C:\WINDOWS\System32\actxprxy.dll
    0x325C0000 - 0x325D2000      C:\Program Files\Microsoft Office\OFFICE11\msohev.dll
    0x6CC60000 - 0x6CC6B000      C:\WINDOWS\System32\dispex.dll
    0x76990000 - 0x769B5000      C:\WINDOWS\system32\ntshrui.dll
    0x76980000 - 0x76988000      C:\WINDOWS\system32\LINKINFO.dll
    0x73B30000 - 0x73B45000      C:\WINDOWS\system32\mscms.dll
    0x6D440000 - 0x6D450000      C:\Program Files\Java\j2re1.4.2\bin\npjpi142.dll
    0x5EDD0000 - 0x5EDE7000      C:\WINDOWS\system32\OLEPRO32.DLL
    0x6D310000 - 0x6D327000      C:\Program Files\Java\j2re1.4.2\bin\jpiexp32.dll
    0x6D380000 - 0x6D397000      C:\Program Files\Java\j2re1.4.2\bin\jpishare.dll
    0x08000000 - 0x08136000      C:\PROGRA~1\Java\J2RE14~1.2\bin\client\jvm.dll
    0x05E50000 - 0x05E57000      C:\PROGRA~1\Java\J2RE14~1.2\bin\hpi.dll
    0x06450000 - 0x0645E000      C:\PROGRA~1\Java\J2RE14~1.2\bin\verify.dll
    0x06460000 - 0x06478000      C:\PROGRA~1\Java\J2RE14~1.2\bin\java.dll
    0x06480000 - 0x0648D000      C:\PROGRA~1\Java\J2RE14~1.2\bin\zip.dll
    0x07510000 - 0x0761A000      C:\Program Files\Java\j2re1.4.2\bin\awt.dll
    0x07000000 - 0x07050000      C:\Program Files\Java\j2re1.4.2\bin\fontmanager.dll
    0x73940000 - 0x73A10000      C:\WINDOWS\system32\D3DIM700.DLL
    0x6D2F0000 - 0x6D304000      C:\Program Files\Java\j2re1.4.2\bin\jpicom32.dll
    0x07F40000 - 0x07F62000      C:\Program Files\Java\j2re1.4.2\bin\dcpr.dll
    0x07F70000 - 0x07F7F000      C:\Program Files\Java\j2re1.4.2\bin\net.dll
    0x5CB00000 - 0x5CB6E000      C:\WINDOWS\System32\shimgvw.dll
    Heap at VM Abort:
    Heap
    def new generation total 576K, used 12K [0x10130000, 0x101d0000, 0x10890000)
    eden space 512K, 2% used [0x10130000, 0x10133120, 0x101b0000)
    from space 64K, 0% used [0x101c0000, 0x101c0000, 0x101d0000)

  • Sun App Sever 8.1  /  JNDI - datasource lookup problems

    I get an error when calling the ctx.lookup function. I have the datasource and the resource set up in the server OK. I can ping successfully and view the table data. I am using NetBeans 4.1 / Sun 8.1
    I have been up all night (11pm - 4:30am) trying to figure this out.
        <%
            java.sql.Connection conn = null;
            java.util.Hashtable env = new java.util.Hashtable();
            javax.naming.Context ctx ;
            javax.sql.DataSource cachedDataSource;
            try {
            env.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY,  "com.sun.jndi.cosnaming.CNCtxFactory");
            ctx = new javax.naming.InitialContext();
            cachedDataSource  = (javax.sql.DataSource)ctx.lookup("jdbc/mysql"); 
            if (cachedDataSource == null)
                {out.println("<h2>The datasource is not getting set properly</h2>");
                conn = cachedDataSource.getConnection();}
            else
            { out.println("<h2>the datasource is not null and seems like it gets initialized.<h2>"); }
            } catch (javax.naming.NamingException ne) {}
              catch (java.sql.SQLException se) {}
            env = null;
            ctx = null;
            conn.close();
            conn = null;
            cachedDataSource = null;
        %>

    RTFM
    http://docs.sun.com/app/docs/doc/819-0079
    The resource lookup in the application code looks like this:
    InitialContext ic = new InitialContext();
    String dsName = "java:comp/env/jdbc/HelloDbDs";
    DataSource ds = (javax.sql.DataSource)ic.lookup(dsName);
    Connection connection = ds.getConnection();
    The resource being queried is listed in the res-ref-name element of the web.xml file as follows:
    <resource-ref>
    <description>DataSource Reference</description>
    <res-ref-name>jdbc/HelloDbDs</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    The resource-ref section in a Sun Java System specific deployment descriptor, for example sun-web.xml, maps the res-ref-name (the name being queried in the application code) to the JNDI name of the JDBC resource. The JNDI name is the same as the name of the JDBC resource as defined in the resource file when the resource is created.
    <resource-ref>
    <res-ref-name>jdbc/HelloDbDs</res-ref-name>
    <jndi-name>jdbc/HelloDbDataSource</jndi-name>

  • Exception throws on lookup()

    I develop a Swing Client, which by RMI a JBoss (on Vista machine) accesses and services implements.
    Properties objProperties = new Properties();
    objProperties.put(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NamingContextFactory");
    objProperties.put(Context.URL_PKG_PREFIXES,"org.jboss.naming:org.jnp.interfaces");
    objProperties.put(Context.PROVIDER_URL, "serverIPv4:2001" );
    javax.naming.InitialContext initial = new javax.naming.InitialContext(objProperties);
    NamingEnumeration ne=initial.list("");
    while(ne.hasMore()){
    System.out.println("Bind Objects :"+ne.next());
    Object ref=initial.lookup("project_projectQ");An exception is thrown with the Swing Client on the Debian machine, here:
    {color:#0000ff}initial.lookup("project_projectQ");{color}
    The exception reads:
    {color:#0000ff}java.lang.ClassNotFoundException: project.query.projectQHome
    {color}(in this moment there is not one reaction in the server log of the JBoss (on Vista machine), also not in the Debug mode)
    The {color:#0000ff}project.query.projectQHome{color} is with us an interface in one project.ear, which is on the JBoss (the Vista machine) deployed.
    The interface {color:#0000ff}project.query.projectQHome{color} does not exist in the.jar file of the Swing Client.
    The Swing Client runs thus completely conflict-free on various Machinen, on which only one network entrance and jre 1.6.0 must be present.
    On the Debian machine all functionalities of the Swing Client normally, also an email dispatch run functioned smoothly, but the exception already becomes here with the attempt of {color:#0000ff}initial.lookup("project_projectQ"){color} thrown. All ports of the JBoss (on Vista machine) of the Debian machine are attainable and visible.
    Main question position:
    1. Why funtioniert {color:#0000ff}initial.lookup("project_projectQ"){color} not on the Debian machine?
    2. From where does the exception know the name of the interface {color:#0000ff}project.query.projectQHome{color}?
    3. Why can in the variable{color:#0000ff} javax.naming.InitialContext initial = new javax.naming.InitialContext (objProperties);{color} obviously existing information for the Naming object "project_projectQ" in {color:#0000ff}*initial*.lookup("project_projectQ");{color} not to be used?
    Regards

    If the interface {color:#0000ff}project.query.ProjectQHome{color} is merged in the.jar file of the Swing Client,
    those of port 2001,2000 and 4444 are used.
    If this interface is not merged, those of port 2001,2000,4444 and *8083* are used.
    When starting of the JBoss the following is logged:
    {color:#003300}08:47:05,244 INFO [WebService] Using RMI server codebase: http://MAINSERV:8083
    08:47:05,986 INFO [NamingService] Started jndi bootstrap jnpPort=2001, rmiPort=2000, backlog=50, bindAddress=/192.168.1.2, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076 {color}
    The WebService Using RMI server code base 8083 has here the attitude on MAINSERV.
    MAINSERV is the computer name of the Vista machine.
    In my opinion that could be the cause for the CommunicationException,
    there all Windows machines in the local network the computer 'MAINSERV' to reach (e.g. http://KOPIASSES:8080/ for the starting side of the JBoss),
    the Debian distribution can so not, but only over the IP address http://192.168.1.2:8080/ for the starting side of the JBoss and http://192.168.1.88:8083/ for the WebService.
    I tried to change the codebase properties for run.bat of JBoss.
    The changes were also accepted according to JBoss for the WebService, e.g.:
    -Djava.rmi.server.codebase=http://192.168.1.2/
    -Djava.rmi.server.codebase=http://192.168.1.2:8083/
    Perhaps a possibility seems to be,
    but that does not function in such a way, because I probably set the wrong data over here.
    The local Windows machines throw then an exception, as before with the Debian machine:
    javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: project.query.ProjectQHome]

Maybe you are looking for

  • Transaction PRAA and SM35

    Hello people, I'm working with transaction PRAA to create a vendor from the HR master record. The transaction generates the batch input correctly, then I process the work file in background in SM35. The session ends successfully in development system

  • Error in RFC Message

    Hi All, I am doing a RFC-File Schenario. I had done all the configuration. I am triggering the RFC thru a ABAP Report. The first time i ran the report i could see the message generated in XI(SXI_MONITOR). But in the payload i can see nothing. Do i ne

  • I' m trying to install Acrobat Pro 10.1.8 Update. I'm getting the Error "Istallation fehlgeschlagen" without Error code  what can I do?

    Hi, I' m trying to install Acrobat Pro 10.1.8 Update. I'm getting the Error "Istallation fehlgeschlagen" without Error code . What can I do? I purchased CS5.1

  • Aggregation Questions

    Hi there Got a couple of questions about OWB 10g R2 aggregations. #1 When I create a cube with aggregations, I cannot for the life of me determine how the aggregations are actually implemented. Are they implemented by separate tables? materialised vi

  • Oracle Developer License

    Hello, My client has an Oracle Licensed Database. I'd like to restore it's dump to create and separate environment locally at my company. Because of the data files size, I can't use the express version. I plan to install another 11g version that has