2 Replies Latest reply: May 2, 2013 10:01 AM by Chiswick Steve RSS

    New install of 2.0.1... - getting ORA-12514 error when accessing console

    Chiswick Steve
      Hello folks,
      I'm going absolutely mad with this one.
      Have created new DB (11.2 EE), installed apex 2 and tried to configure in standalone mode.
      Whatever I try, I get "Default Database connection not configured properly" when starting the listener.
      I've checked all the config files and the correct SID name is there.
      I can connect to the DB via the listener using the APEX_PUBLIC_USER account and the password supplied which is not locked or expired.
      I've configured a different port but doesn't help.

      [oracle@lpgbdwh1004 apex_listener]$ java -jar apex.war
      May 2, 2013 3:28:35 PM oracle.dbtools.standalone.Standalone execute
      INFO: NOTE:

      Standalone mode is designed for use in development and test environments. It is not supported for use in production environments.

      May 2, 2013 3:28:35 PM oracle.dbtools.standalone.Standalone execute
      INFO: Starting standalone Web Container in: /tmp/apex
      May 2, 2013 3:28:35 PM oracle.dbtools.standalone.Deployer deploy
      INFO: Will deploy application path = /tmp/apex/apex/WEB-INF/web.xml
      May 2, 2013 3:28:35 PM oracle.dbtools.standalone.Deployer deploy
      INFO: Deployed application path = /tmp/apex/apex/WEB-INF/web.xml
      May 2, 2013 3:28:35 PM oracle.dbtools.common.config.file.ConfigurationFolder logConfigFolder
      INFO: Using configuration folder: /tmp/apex
      Default Database connection not configured properly
      May 2, 2013 3:28:37 PM oracle.dbtools.rt.web.SCListener contextInitialized
      INFO: Oracle Application Express Listener initialized
      Application Express Listener version : 2.0.1.64.14.26
      Application Express Listener server info: Grizzly/1.9.49

      May 2, 2013 3:28:37 PM com.sun.grizzly.Controller logVersion
      INFO: GRIZZLY0001: Starting Grizzly Framework 1.9.49 - 5/2/13 3:28 PM
      May 2, 2013 3:28:37 PM oracle.dbtools.standalone.Standalone execute
      INFO: http://localhost:9898/apex started.

      ---------------


      default.xml:

      <?xml version="1.0" encoding="UTF-8" standalone="no"?>
      <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
      <properties>
      <comment>Saved on Tue Apr 30 17:13:31 BST 2013</comment>
      <entry key="cache.caching">false</entry>
      <entry key="cache.directory">/tmp/apex/cache</entry>
      <entry key="cache.duration">days</entry>
      <entry key="cache.expiration">7</entry>
      <entry key="cache.maxEntries">500</entry>
      <entry key="cache.monitorInterval">60</entry>
      <entry key="cache.procedureNameList"/>
      <entry key="cache.type">lru</entry>
      <entry key="db.hostname">lpgbdwh1004</entry>
      <entry key="db.password">@05B0A1F12273CBFAAFB6C96465384EE3E01DD95F1081628E42</entry>
      <entry key="db.port">1521</entry>
      <entry key="db.servicename">dwtest4</entry>
      <entry key="debug.debugger">false</entry>
      <entry key="debug.printDebugToScreen">false</entry>
      <entry key="error.keepErrorMessages">true</entry>
      <entry key="error.maxEntries">50</entry>
      <entry key="jdbc.DriverType">thin</entry>
      <entry key="jdbc.InactivityTimeout">1800</entry>
      <entry key="jdbc.InitialLimit">3</entry>
      <entry key="jdbc.MaxConnectionReuseCount">1000</entry>
      <entry key="jdbc.MaxLimit">10</entry>
      <entry key="jdbc.MaxStatementsLimit">10</entry>
      <entry key="jdbc.MinLimit">1</entry>
      <entry key="jdbc.statementTimeout">900</entry>
      <entry key="log.logging">false</entry>
      <entry key="log.maxEntries">50</entry>
      <entry key="misc.compress"/>
      <entry key="misc.defaultPage">apex</entry>
      <entry key="security.disableDefaultExclusionList">false</entry>
      <entry key="security.maxEntries">2000</entry>
      </properties>

      ----------------------

      lsnrctl :

      Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
      STATUS of the LISTENER
      ------------------------
      Alias LISTENER
      Version TNSLSNR for Linux: Version 11.2.0.2.0 - Production
      Start Date 01-MAY-2013 11:52:28
      Uptime 1 days 3 hr. 48 min. 8 sec
      Trace Level off
      Security ON: Local OS Authentication
      SNMP ON
      Listener Log File /u01/app/oracle/diag/tnslsnr/lpgbdwh1004/listener/alert/log.xml
      Listening Endpoints Summary...
      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=lpgbdwh1004.emea.leaseplancorp.net)(PORT=1521)))
      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=lpgbdwh1004.emea.leaseplancorp.net)(PORT=8888))(Presentation=HTTP)(Session=RAW))
      Services Summary...
      Service "+ASM" has 1 instance(s).
      Instance "+ASM", status READY, has 1 handler(s) for this service...
      Service "dwtest4.emea.leaseplancorp.net" has 1 instance(s).
      Instance "dwtest4", status READY, has 1 handler(s) for this service...
      The command completed successfully

      ---------------------------------

      sqlplus:
      [oracle@lpgbdwh1004 apex_listener]$ sqlplus APEX_PUBLIC_USER@dwtest4

      SQL*Plus: Release 11.2.0.2.0 Production on Thu May 2 15:42:08 2013

      Copyright (c) 1982, 2010, Oracle. All rights reserved.

      Enter password:

      Connected to:
      Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
      With the Partitioning, Automatic Storage Management, OLAP, Data Mining
      and Real Application Testing options

      SQL>

      ------------------------------------------------------------------------------------

      apex.xml:

      <entry key="db.hostname">localhost</entry>
      <entry key="db.password">@05C4903B62941343FBB520CF1F6AAD6433CFCACD62D0B748CA</entry>
      <entry key="db.sid">dwtest4</entry>
      <entry key="db.username">APEX_PUBLIC_USER</entry>

      ----------------------

      Accessing console gives me "Service Unavailable" and:

      May 2, 2013 3:32:45 PM oracle.dbtools.rt.web.HttpEndpointBase modApex
      SEVERE: The pool named: apex is not correctly configured, error: Listener refused the connection with the following error:
      ORA-12514, TNS:listener does not currently know of service requested in connect descriptor

      oracle.dbtools.common.jdbc.ConnectionPoolException: The pool named: apex is not correctly configured, error: Listener refused the connection with the following error:
      ORA-12514, TNS:listener does not currently know of service requested in connect descriptor

      at oracle.dbtools.common.jdbc.ConnectionPoolException.badConfiguration(ConnectionPoolException.java:65)
      at oracle.dbtools.common.config.db.DatabaseConfig.badConfiguration(DatabaseConfig.java:166)
      at oracle.dbtools.common.config.db.DatabaseConfig.createPool(DatabaseConfig.java:187)
      at oracle.dbtools.common.config.db.DatabaseConfig.getConnection(DatabaseConfig.java:71)
      at oracle.dbtools.common.jdbc.ora.OraPrincipal.connection(OraPrincipal.java:69)
      at oracle.dbtools.apex.ModApexContext.getConnection(ModApexContext.java:372)
      at oracle.dbtools.apex.Procedure.getProcedure(Procedure.java:167)
      at oracle.dbtools.apex.OWA.validateProcedure(OWA.java:390)
      at oracle.dbtools.apex.security.Security.isValidRequest(Security.java:225)
      at oracle.dbtools.apex.ModApex.validateRequest(ModApex.java:266)
      at oracle.dbtools.apex.ModApex.doGet(ModApex.java:94)
      at oracle.dbtools.apex.ModApex.service(ModApex.java:302)
      at oracle.dbtools.rt.web.HttpEndpointBase.modApex(HttpEndpointBase.java:337)
      at oracle.dbtools.rt.web.HttpEndpointBase.service(HttpEndpointBase.java:130)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at com.sun.grizzly.http.servlet.ServletAdapter$FilterChainImpl.doFilter(ServletAdapter.java:1059)
      at com.sun.grizzly.http.servlet.ServletAdapter$FilterChainImpl.invokeFilterChain(ServletAdapter.java:999)
      at com.sun.grizzly.http.servlet.ServletAdapter.doService(ServletAdapter.java:434)
      at oracle.dbtools.standalone.SecureServletAdapter.doService(SecureServletAdapter.java:65)
      at com.sun.grizzly.http.servlet.ServletAdapter.service(ServletAdapter.java:379)
      at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
      at com.sun.grizzly.tcp.http11.GrizzlyAdapterChain.service(GrizzlyAdapterChain.java:196)
      at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
      at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849)
      at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746)
      at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045)
      at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228)
      at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
      at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
      at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
      at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
      at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
      at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
      at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
      at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
      at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
      at java.lang.Thread.run(Thread.java:679)




      Please help...
      Thanks,
      Steve

      Edited by: Chiswick Steve on 02-May-2013 07:40

      Edited by: Chiswick Steve on 02-May-2013 07:42
        • 1. Re: New install of 2.0.1... - getting ORA-12514 error when accessing console
          Colm Divilly-Oracle
          Chiswick Steve wrote:
          Hello folks,
          I'm going absolutely mad with this one.
          Have created new DB (11.2 EE), installed apex 2 and tried to configure in standalone mode.
          Whatever I try, I get "Default Database connection not configured properly" when starting the listener.
          I've checked all the config files and the correct SID name is there.
          I can connect to the DB via the listener using the APEX_PUBLIC_USER account and the password supplied which is not locked or expired.
          I've configured a different port but doesn't help.

          [oracle@lpgbdwh1004 apex_listener]$ java -jar apex.war
          May 2, 2013 3:28:35 PM oracle.dbtools.standalone.Standalone execute
          INFO: NOTE:

          Standalone mode is designed for use in development and test environments. It is not supported for use in production environments.

          May 2, 2013 3:28:35 PM oracle.dbtools.standalone.Standalone execute
          INFO: Starting standalone Web Container in: /tmp/apex
          May 2, 2013 3:28:35 PM oracle.dbtools.standalone.Deployer deploy
          INFO: Will deploy application path = /tmp/apex/apex/WEB-INF/web.xml
          May 2, 2013 3:28:35 PM oracle.dbtools.standalone.Deployer deploy
          INFO: Deployed application path = /tmp/apex/apex/WEB-INF/web.xml
          May 2, 2013 3:28:35 PM oracle.dbtools.common.config.file.ConfigurationFolder logConfigFolder
          INFO: Using configuration folder: /tmp/apex
          Default Database connection not configured properly
          May 2, 2013 3:28:37 PM oracle.dbtools.rt.web.SCListener contextInitialized
          INFO: Oracle Application Express Listener initialized
          Application Express Listener version : 2.0.1.64.14.26
          Application Express Listener server info: Grizzly/1.9.49

          May 2, 2013 3:28:37 PM com.sun.grizzly.Controller logVersion
          INFO: GRIZZLY0001: Starting Grizzly Framework 1.9.49 - 5/2/13 3:28 PM
          May 2, 2013 3:28:37 PM oracle.dbtools.standalone.Standalone execute
          INFO: http://localhost:9898/apex started.

          ---------------


          default.xml:

          <entry key="db.servicename">dwtest4</entry>
          This db.servicename value is inherited by apex.xml, it is used in preference to db.sid
          Service "dwtest4.emea.leaseplancorp.net" has 1 instance(s).
          This is the service name: dwtest4.emea.leaseplancorp.net NOT: dwtest4

          >
          apex.xml:

          <entry key="db.sid">dwtest4</entry>
          If a db.servicename is specified then that is used, the db.servicename is inherited from defaults.xml,

          Solution:

          1. Fix db.servicename in defaults.xml
          2. remove db.sid in apex.xml
          • 2. Re: New install of 2.0.1... - getting ORA-12514 error when accessing console
            Chiswick Steve
            That is awesomely quick, many thanks.
            I had experimented with both options (SID and SERVICE_NAME) when running setup. so it must have left some config in 1 of those files.

            Thank you very much.

            Edited by: Chiswick Steve on 02-May-2013 08:01