Closed database connection in olap worksheet

i have installed analytic workspace manager after applying the pathches ,i tried to log in analytic workspace manager and connect to olap worksheet it gives
me an error as "closed database connection" .My patch
installation was successful and it did not give me any error and my database is also working properly.could anyone help me out with this problem.

I had the same problem. Follow this link for the solution
Re: Cannot connect to AWM

Similar Messages

Change database connection in SQL-Worksheet to a not connected db

Hi,
change the active database connection of a SQL-Worksheet to a currently not connected database does not work. The login window pops up, but the password entry field cannot be activated to enter the password. On dragging the login window the screen does not get refreshed correctly. The only way to get back to work is to kill the sqldeveloper.exe process.
The affected version is 3.2.09.23 on the 32 bit MS Windows plattform.
sincerely yours
Matthias

Hi Matthias,
Thanks for reporting this. It is caused by a deadlock between Java threads. I will log a bug for it.
Regards,
Gary
SQL Developer Team
Edited by: Gary Graham on Aug 23, 2012 4:26 PM
Bug 14532491 - FORUM - DEADLOCK OCCURS WHEN SWITCHING WORKSHEET CONNECTIONS
Edited by: Gary Graham on Aug 23, 2012 4:27 PM
Bug 14534488 - DEADLOCK OCCURS WHEN OPENING WORKSHEET CONNECTION FOR A SQL FILE

Java Database Connections couldn't be closed on PI 7.1 EHP1

Hi, I develop a dynamic web project to PI. And I use Database conection in that web project. Even I closed the connection in java , Connection doesn't closed and after a while PI pooling size reach the maximum size and PI doesn't response. I find open connections on MSSQL and connections' status are sleeping, cmd fields are AWAITING COMMAND. I have to restart PI these to close that connections.
I get Connections like these code
                        InitialContext cxt = new InitialContext();
               final DataSourceManager dsm = (DataSourceManager) cxt
                         .lookup("dbpool");
                        String lookUpName = dsm.getSystemDataSourceDescriptor().getDataSourceName();
               DataSource ds = (DataSource) cxt.lookup("jdbc/" + lookUpName);
               ds.setLoginTimeout(60);
               conn = ds.getConnection();...
and I close connections like these
                        conn = db.getDefaultDatabaseConnection();
               if (conn != null) {
                    try {
                         conn.setAutoCommit(true);
                         String sql = "INSERT INTO
                         pstmt.close();
                         conn.close();
                    } catch (Exception e) {
                                 } finally {
                         try {
                              pstmt.close();
                              conn.close();
                         } catch (SQLException e2) {
                              e.printStackTrace();
                         e.printStackTrace();
I changed system DataSource's   and i give these parameters
Initial Connections: 5
Maximum Connections: 125
Maximum Time to Wait for Connection: 90
Connection Lifetime (Sec.): 60
Cleanup Interval (Sec.) : 90
it didn't work either
Can anyone hepl me ?

I would like to make slight changes in code. . Please close the resources only in finally block.
Dont know you are closing resultset or not. If not, you must close it
conn = db.getDefaultDatabaseConnection();
try {
if (conn != null) {
conn.setAutoCommit(true);
String sql = "INSERT INTO
} catch (Exception e) {
} finally {
    try{
       if(rs != null){
        rs.close()
     }catch(SqlException se){
        //log it
   try{
       if(stmt != null){
            stmt.close();
     }catch(SqlException se){
        //log it
try{
   if(conn != null){
     conn.close();
} catch(SQLException ss){
// log it
} // end of finally
Hope this help.

Database connection not closing on time out

Hi All,
Not sure if this is the right place for this question but..
I've moved my app (built using jdev10.1.2., adf bc's and jsp's) to an app server. For some reason, the database connection is not closing. I have 46 connections to the database and I''m the only one with the URL, not good.
So can anyone shed any light on this? I thought it should disconnect after a time out but its not.
Any ideas would be gratfully received.
Thanks in advance

or try this one..
Go to the bottom of the tutorial, you will find the configuration...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bc9baf90-0201-0010-479a-b49b25598ebf

[Bug] Or feature? Database connection closed if given a name after first op

I am not sure if this is a bug or a feature.
oracle.javatools.db.Database db = oracle.javatools.db.DatabaseFactory.findOrCreateDatabase("sample", conn);
If I supply a name for the database as the above line using "sample", the database connection is closed after the first op, i.e., you can call
db.listObjects once, but the second time, it will fail with StackOverFlowException. But the culprit is the database connection is closed after the first op.
However, if I don't give it a name, using null,
oracle.javatools.db.Database db = oracle.javatools.db.DatabaseFactory.findOrCreateDatabase(null, conn);
There's no problem at all.
Is this a bug or a feature?
If a feature, the JavaDoc made it worse, by using the following example:
http://www.oracle.com/technology/products/jdev/esdk/api1013/oracle/javatools/db/DatabaseFactory.html
The DatabaseFactory should be used over the DBObjectProviderFactory when a Database specifically is required, and the name and Connection of that Database are available.
e.g.
java.sql.Connection conn = // the Connection to the db
DatabaseFactory.findOrCreateDatabase( "ora10g", conn );
The example sure sounds like a name is mandatory. Or perhaps the name is not some random name, but TNSName? If so, the Doc should certainly mention that.

I am not sure if this is a bug or a feature.
oracle.javatools.db.Database db = oracle.javatools.db.DatabaseFactory.findOrCreateDatabase("sample", conn);
If I supply a name for the database as the above line using "sample", the database connection is closed after the first op, i.e., you can call
db.listObjects once, but the second time, it will fail with StackOverFlowException. But the culprit is the database connection is closed after the first op.
However, if I don't give it a name, using null,
oracle.javatools.db.Database db = oracle.javatools.db.DatabaseFactory.findOrCreateDatabase(null, conn);
There's no problem at all.
Is this a bug or a feature?
If a feature, the JavaDoc made it worse, by using the following example:
http://www.oracle.com/technology/products/jdev/esdk/api1013/oracle/javatools/db/DatabaseFactory.html
The DatabaseFactory should be used over the DBObjectProviderFactory when a Database specifically is required, and the name and Connection of that Database are available.
e.g.
java.sql.Connection conn = // the Connection to the db
DatabaseFactory.findOrCreateDatabase( "ora10g", conn );
The example sure sounds like a name is mandatory. Or perhaps the name is not some random name, but TNSName? If so, the Doc should certainly mention that.

Database Connections Not Closing

I'm using iBatis for PostgreSQL database access and frequently have problems with connections not being closed. Here is a copy of my sqlMapConfig file:
============================
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE sqlMapConfig
PUBLIC "-//iBATIS.com//DTD SQL Map Config 2.0//EN"
"http://www.ibatis.com/dtd/sql-map-config-2.dtd">
<sqlMapConfig>
<properties resource="ibatis.properties" />
<settings
lazyLoadingEnabled="true"
cacheModelsEnabled="true"
enhancementEnabled="false"
useStatementNamespaces="false"
/>
<transactionManager type="JDBC" commitRequired="true">
<dataSource type="DBCP">
<property name="driverClassName" value="${driver}" />
<property name="url" value="${url}" />
<property name="username" value="${username}" />
<property name="password" value="${password}" />
<property name="maxActive" value="10"/>
<property name="maxIdle" value="5"/>
<property name="maxWait" value="5000"/>
<property name="logAbandoned" value="true"/>
<property name="removeAbandoned" value="true"/>
<property name="removeAbandonedTimeout" value="1"/>
<property name="Driver.logUnclosedConnections" value="true"/>
</dataSource>
</transactionManager>
<sqlMap resource="job-sqlMap.xml" />
</sqlMapConfig>
============================
Due to the logAbandoned and removeAbandoned settings, I get a report in my log file whenever there is a connection that was not properly closed. Here is one of those log entries:
23:22:51.483 (10) Finalizing a Connection that was never closed:
java.lang.Throwable: Connection was created at this point:
at org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:175)
at org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
at org.postgresql.jdbc3.Jdbc3Connection.<init>(Jdbc3Connection.java:24)
at org.postgresql.Driver.makeConnection(Driver.java:393)
at org.postgresql.Driver.connect(Driver.java:267)
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1148)
at org.apache.commons.dbcp.AbandonedObjectPool.borrowObject(AbandonedObjectPool.java:84)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)
at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTransaction.init(JdbcTransaction.java:48)
at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTransaction.getConnection(JdbcTransaction.java:89)
at com.ibatis.sqlmap.engine.mapping.statement.MappedStatement.executeQueryForList(MappedStatement.java:139)
at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForList(SqlMapExecutorDelegate.java:567)
at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForList(SqlMapExecutorDelegate.java:541)
at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.queryForList(SqlMapSessionImpl.java:118)
at com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.queryForList(SqlMapClientImpl.java:94)
at edu.calpoly.lib.multimedia.big.db.AutomaticPeriodUpdateIBatisImplDBHandler.getGamesWithAutomaticUpdatePolicy(AutomaticPeriodUpdateIBatisImplDBHandler.java:154)
at edu.calpoly.lib.multimedia.big.game.AutoUpdateThread.run(AutoUpdateThread.java:155)
The file: AutomaticPeriodUpdateIBatisImplDBHandler.java contains an iBatis call on line # 154:
--> list = sqlMap.queryForList("getGamesWithAutoPolicy", null);
from the map file:
<select id="getGamesWithAutoPolicy" resultClass="java.util.HashMap">
<![CDATA[
SELECT gameid, policy
FROM update_policy
]]>
</select>
Here is the code for the entire method that uses this transaction:
============================
public List getGamesWithAutomaticUpdatePolicy() throws BIGDatabaseFacadeException
List list = new ArrayList();
try
sqlMap.startTransaction();
list = sqlMap.queryForList("getGamesWithAutoPolicy", null);
sqlMap.commitTransaction();
catch(SQLException sqle)
throw new BIGDatabaseFacadeException(sqle);
finally
try
sqlMap.endTransaction();
catch(SQLException sqle)
throw new BIGDatabaseFacadeException(sqle);
return list;
============================
I know that this should be handled as an automatic transaction, but I tried adding the start, commit and end transaction commands in my desperate attempt to fix this problem (but it still didn't help).
Here is my code for creation of sqlMap -
--> sqlMap = SqlMapClientBuilder.buildSqlMapClient(Resources.getResourceAsReader("sqlMaps.xml"));
Except for the fact that occasionally connections are not closed, overall my database access using iBatis works very well.
In the course of trying to fix this problem I've worked to update all my lib files to the latest versions, and here is current status:
My iBatis lib file: ibatis-2.3.4.726.jar
My JDBC driver: postgresql-8.4-701.jdbc3.jar
Required commons files:
commons-dbcp-1.2.2.jar
commons-pool-1.5.3.jar
Note that I tried adding --> commitRequired="true" to the transactionManager in sqlMaps.xml, hoping it might help, but no joy.
Please help me figure out why my database connections often do not close. Thank you very much!

I'm sorry, but I don't understand what you mean by "close the session." I believe iBatis is supposed to take care of all that automatically. My understanding is that all the user does is create the sqlMapClient and then use it along with various map files to query and update the database. iBatis does the rest.

Database connection closing in JSF

This is regarding Database connection closing in JSF.
in servlets we have destroy method where we will be closing the database connections, similarly in JSF where should we close the database connections? is it taken care by the framework?
is there a way where we could capture the end of session and then close the database connection?
I am creating database connection in backing bean as I am not supposed to create a pool of connection objects(I am using tomcat 5.5)
Thanks in advance for any suggestions about this.

k_srinivas wrote:
This is regarding Database connection closing in JSF.OK.
in servlets we have destroy method where we will be closing the database connectionsThis is at its own already a very bad practice. All database resources like Connection, Statement and ResultSet must be acquired and closed in the shortest possible scope. You should never keep them open as an instance variable and for sure not in a servlet (which lives as long as the application lives). If you keep a connection open that long, it will timeout sooner or later and your application will crash.
, similarly in JSF where should we close the database connections? is it taken care by the framework?
is there a way where we could capture the end of session and then close the database connection?No, just acquire and close the resources in the shortest possible scope. To improve performance, introduce connection pooling. But this doesn't mean that you can write the JDBC code the other way. You still need to acquire and close the resources quickly. The connection pooling implementation will worry about actually closing the connection or releasing the connection to the pool.
I am creating database connection in backing bean as I am not supposed to create a pool of connection objects(I am using tomcat 5.5)
Thanks in advance for any suggestions about this.This makes no sense. Just make use of Tomcat's own connection pooling facility.
For more about doing the database access logic the proper way, you may find this tutorial useful: [http://balusc.blogspot.com/2008/07/dao-tutorial-data-layer.html].

Closing the database connection after report in a server application

I searched these forums and the internet for a definitive answer on asking the Crystal SDK for java to close the jdbc connection after it has generated a report. We have been using the Crystal Report SDK to generate reports within our JEE application, built upon the Spring framework, for the past two years. It works well, especially if you prepare views in the database for your reports.
From what I can tell once you have used ReportClientDocument to create your report you all the close() method to release resources associated with report generation, but this does not close the jdbc database connection.
Further research states that if you are using the CrystalReportViewer you can call the dispose method to close the database connection. We are not using JSP nor this class, so that does us little good.
Finally I found a post that one could call ((AdvancedReportDocument)reportClientDocument.getReportSource()).dispose(). This doesn't drop the connection either.
Each report actually opens 3 connections according to SQL Server. Each report will reuse the connections it has open, so for 50 reports, theoretically, we could have up to 150 connections. We explained to our client those connections remain inactive, however this is unacceptable to our client as they would like to minimize the number of connections left open to their database.
If anyone can post any further information on this issue, it is much appreciated.

Yes, another team member found the issue. Quite embarrassing really I didn't see it. I was looking for the answer within Crystal's libraries. It had nothing to do with Crystal.
The developer who wrote the helper code for using Crystal first opened a connection to the datasource for the live production database and read that connection information for the report. Next he set that connection information in the report template's PropertyBag, then ran the report. The developer however forgot to close the connection he used to look up the connection info, leaving a memory leak and using up all the connections.
I'm glad you inquired. I forgot to post the resolution here.

How to correct close database connection after report generation

Hello
I have problem a with alive database connection after report creation and report closing. How to properly to close connection to database?
Best regards
Edited by: punkers84 on Jun 17, 2011 10:38 AM

that's what I am doing... after viewing the report, I call the close method on the window closing event of the container window. but the connection is still open. I had a lot of other issues with my jdbc driver but after downgrading to an older version those issues are resolved.Only this one is still there! Is there any other way to close the connection (like using dbcontroller or etc.)?

MySQL Database Connection (two databases at the same time)

I have never had to open more than one MySQL database from within the same website before, but I do now. The website I have is designed where all the content comes from within the main database. I am building an Inventory system that I want within it's own database, in the event I would ever need to move the application to another server or something, I don't want this data residing in the main database.
Currently, I open the database connection from within a file called "common.php" that resides in a directory called "lib" that can be accessed from the root directory. Below is the proposed code that would be placed within the "common.php" file:
// Define Database Variables
$dbserver = "127.0.0.1";
$dbuser = array('clevelan_user1', 'clevelan_user2');
$dbpass = array('P@ssw0rd', 'P@ssw0rd2');
$dbname = array('clevelan_database1', 'clevelan_database2');
// Start Session
session_start();
// Connect to Databases
connectdb($dbserver, $dbuser[0], $dbpass[0], $dbname[0]);
connectdb2($dbserver, $dbuser[1], $dbpass[1], $dbname[1]);
// Database 1 Connection
function connectdb($dbserver, $dbuser, $dbpass, $dbname) {
// connects to db
global $connection;
$connection = @mysql_connect($dbserver, $dbuser, $dbpass) or die ("could not connect to server");
$db = @mysql_select_db($dbname, $connection) or die ("could not select databsase");
return $connection;
// Database 2 Connection
function connectdb2($dbserver, $dbuser, $dbpass, $dbname) {
// connects to db
global $connection2;
$connection2 = @mysql_connect($dbserver, $dbuser, $dbpass) or die ("could not connect to server");
$db2 = @mysql_select_db($dbname, $connection2) or die ("could not select databsase");
return $connection2;
//End of Code Within the "common.php"
From within any page of the website, I want to access both connections by placing an include at the top of each page:
include_once("lib/common.php");
Currently, when I run the code above, any page within the website (the home page) provides error messages with regards to database connectivity (the pages are looking for there content from within the second database. It's as if the second database is the only database seen by the website.
I need help figuring out how I can have two MySQL databases open at the same time (the second database will only be open for short periods of time and then closed). But the main database is always open.

Create one project using one copy of the exact tables.
create 2 different sessions.xml files each pointing to the same project. Set the login information in the sessions.xml files.
That should work fine.
Peter

Database connection remains open after close being called

I am using oracle OC4J as my application server. I am not using connection pool and I am using non-pooled datasource to get connection. The database connection is made at runtime and then closed. I want to test if the users' connection sessions have been killed after they logout the application. But when I checked the table v$session in the database, it shows one connection remaining. I checked my program, the close method has been called. Does anybody know the solution?

Hi Chen,
This is just a suggestion for something to try -- only if you haven't
already tried it, that is!
Try running OC4J in "debug" mode. Here are details on how to do that:
http://kb.atlassian.com/content/atlassian/howto/orionproperties.jsp
Hope this helps you!
Good Luck,
Avi.

BEST PRACTICES FOR CREATING DISCOVERER DATABASE CONNECTION -PUBLIC VS. PRIV

I have enabled SSO for Discoverer. So when you browse to http://host:port/discoverer/viewer you get prompted for your SSO
username/password. I have enabled users to create their own private
connections. I log in as portal and created a private connection. I then from
Oracle Portal create a portlet and add a discoverer worksheet using the private
connection that I created as the portal user. This works fine...users access
the portal they can see the worksheet. When they click the analyze link, the
users are prompted to enter a password for the private connection. The
following message is displayed:
The item you are requesting requires you to enter a password. This could occur because this is a private connection or
because the public connection password was invalid. Please enter the correct
password now to continue.
I originally created a public connection...and then follow the same steps from Oracle portal to create the portlet and display the
worksheet. Worksheet is displayed properly from Portal, when users click the
analyze link they are taken to Discoverer Viewer without having to enter a
password. The problem with this is that when a user browses to
http://host:port/discoverer/viewer they enter their SSO information and then
any user with an SSO account can see the public connection...very insecure!
When private connections are used, no connection information is displayed to
SSO users when logging into Discoverer Viewer.
For the very first step, when editing the Worksheet portlet from Portal, I enter the following for Database
Connections:
Publisher: I choose either the private or public connection that I created
Users Logged In: Display same data to all users using connection (Publisher's Connection)
Users Not Logged In: Do no display data
My question is what are the best practices for creating Discoverer Database
Connections.
Is there a way to create a public connection, but not display it in at http://host:port/discoverer/viewer?
Can I restrict access to http://host:port/discoverer/viewer to specific SSO users?
So overall, I want roughly 40 users to have access to my Portal Page Group. I then want to
display portlets with Discoverer worksheets. Certain worksheets I want to have
the ability to display the analyze link. When the SSO user clicks on this they
will be taken to Discoverer Viewer and prompted for no logon information. All
SSO users will see the same data...there is no need to restrict access based on
SSO username...1 database user will be set up in either the public or private
connection.

You can make it happen by creating a private connection for 40 users by capi script and when creating portlet select 2nd option in Users Logged in section. In this the portlet uses there own private connection every time user logs in.
So that it won't ask for password.
Another thing is there is an option of entering password or not in ASC in discoverer section, if your version 10.1.2.2. Let me know if you need more information
thnaks
kiran

Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.

Hi,
I am using APEX version 4.2.1.00.08 with Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
I've developed an application, that was working fine till 3 days ago...
At the moment, I can log into the application but when I enter my ID/PW it takes me to my 1st page but then it runs for a mint or so (trying to load charts) and then generates following error message
No data received
Unable to load the webpage because the server sent no data.
Here are some suggestions:
Reload this webpage later.
Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.
interestingly, I haven't changed anything within the application
I've tried it with Chrome Version 27.0.1453.116 m and IE 8.0...
with IE 8.0, it shows I/O Error in place of my graphs and get's a pop up message that displays "Error - error unknown"
The only thing that I can recall doing differently is logging via remote desktop connection, but I've used remote desktop in the past as well and it worked.
Please advice

anyone...?

Too many inactive database connections (c#, webapp, Oracle)

 I have a web application that uses the CrystalDecisions.Web.CrystalReportViewer to display my reports. The application opens a connection to an Oracle database with SetDatabaseLogon(). I have not yet implemented anything to free the connections when they're not needed anymore. I read in the Crystal help that the best place to call ReportDocument.Close() is in the Page_Unload method.The problem is that my reports have dynamic cascading parameters that make the page reload (ie Page_Unload -> Page_Load) several times. I can eventually call ReportDocument.Close() in a Global.asax method, like Session_End(), but I'm not sure it is optimal, as my report object is not known in this scope and I have extra code to write to handle this. Is there a better way to manage database connection ? Can anyone provide a working sample ?thanks 

I'm not aware of a better way. Your connections are definately being held up because you are not closing the Report. Possibly you could put a conditional ReportDocument.close() call in your unload method. You would need to check to make sure that the document was available and that you weren't loading parameters. I'm sure that this would work. Rob Horne<a href="/blog/10">Rob's blog - http://diamond.businessobjects.com/blog/10</a>

Financial Reports error message Java API can't connect to olap

Hi,
On version 11.1.1.3, after reapplication of 11.1.1.3 because of other problems with shared services, get the following message on the diagnostics for the financial reporting server.
Launch external checker with next command: E:\Hyperion\common\validation\9.5.0.0\launchEssbaseJavaAPI.bat EssbaseJAPIConnect admin ****** hypolap.msj.org http://hypapp2.msj.org:13080/aps/JAPI
Error: Result: -1; Error message: Cannot connect to olap service. Cannot connect to Essbase Server. Error:Essbase Error(1051293): Login fails due to invalid login credentials
Recommended Action: Make sure external checker is working.
Financial reports over the Web can not connect to the essbase server. Financial reports through the studio works fine. Any suggestions how to troubleshoot or resolve the issue with the login credentials for the Java API to essbase?
Anne

Things to check -
1) Does the user you specified in the connection have the role OLAP_USER
2) Does the user you specified in the connection have access to an OLAP schema (analytic workspace or CWM2 ROLAP schema)
3) Have you installed the correct JDBC files from your database instance into the BI Beans JDBC directory
Keith Laker
Oracle EMEA Consulting
BI Blog: http://oraclebi.blogspot.com/
DM Blog: http://oracledmt.blogspot.com/
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Samples: http://www.oracle.com/technology/products/bi/samples/

Closed database connection in olap worksheet

Similar Messages

Maybe you are looking for