JClient 2 Tier Application Release Connection

We have a 2 tier application with many application modules which can be open at the same time. In each screen we call "Release" when it is closed but in Toad we see it is not releasing the connection.
There is a post on this but nothing about if this was resolved?
How to immediately released database connection in jclient form app ?
Cory

1)3 tier means the database is one tier, the applications server (the fmx) is the second tier, and the browser (where the UI gets displayed) is the 3rd tier. The 3rd Tier is a browser and requires no extra software.
2) You can do this but the power of Forms is that the act of writing your middle tier(application logic) is easy because of the power of Forms. In theory, you could write all your application logic in Java and only write the screens (and the part that interfaces with the Java business Logic) in Forms. But this is not really what Forms is about - you would probably want to look at JDeveloper.
3) Forms makes the interation with the database soooo easy - however if you have a load of business logic already written in Java you can integrate it with Forms using the Java importer.
Regards
Grant Ronald
Forms Product Management

Similar Messages

Sessions problem in a 3-tier application

Dear All,
I am trying to create a 3-tier application using Apache Tomcat and Toplink:
1. As a part of my servlet startup I create a ServerSession
session = project.createServerSession();
and store it as a static variable. Upon connect I can see that TopLink creates multiple connections. (I assume they are to be pooled between client sessions)
2. All subsequent DB operations are performed using client sessions acquired from that server session:
session.acquireClientSession()
I am running into the following problem:
After very mosdest usage (1 user) I manage to freeze the application as follows:
[TopLink Finer]: 2007.08.19 11:31:44.093--ServerSession(2285943)--Thread(Thread[http-8080-Processor25,5,main])--client acquired
[TopLink Finest]: 2007.08.19 11:31:44.109--ClientSession(15960898)--Thread(Thread[http-8080-Processor25,5,main])--Execute query ReadAllQuery(com.ligolab.application.domain.reporting.PatientResultReport)
[TopLink Fine]: 2007.08.19 11:31:44.109--ServerSession(2285943)--Connection(21849501)--Thread(Thread[http-8080-Processor25,5,main])-- MY SELECT QUERY HERE
[TopLink Finer]: 2007.08.19 11:31:44.921--ClientSession(15960898)--Thread(Thread[http-8080-Processor25,5,main])--client released
---------------------------------------------- [I hit Refresh on my browser here] ---------------
[TopLink Finer]: 2007.08.19 11:31:46.125--ServerSession(2285943)--Thread(Thread[http-8080-Processor24,5,main])--client acquired
[TopLink Finest]: 2007.08.19 11:31:46.125--ClientSession(28210421)--Thread(Thread[http-8080-Processor24,5,main])--Execute query ReadAllQuery(com.ligolab.application.domain.reporting.PatientResultReport)
[TopLink Fine]: 2007.08.19 11:31:46.125--ServerSession(2285943)--Connection(21849501)--Thread(Thread[http-8080-Processor24,5,main])-- MY SELECT QUERY HERE
[TopLink Finer]: 2007.08.19 11:31:47.265--ClientSession(28210421)--Thread(Thread[http-8080-Processor24,5,main])--client released
---------------------------------------------- [I hit Refresh on my browser here] ---------------
[TopLink Finer]: 2007.08.19 11:31:49.062--ServerSession(2285943)--Thread(Thread[http-8080-Processor25,5,main])--client acquired
[TopLink Finest]: 2007.08.19 11:31:49.062--ClientSession(25506524)--Thread(Thread[http-8080-Processor25,5,main])--Execute query ReadAllQuery(com.ligolab.application.domain.reporting.PatientResultReport)
[TopLink Fine]: 2007.08.19 11:31:49.062--ServerSession(2285943)--Connection(21849501)--Thread(Thread[http-8080-Processor25,5,main])-- MY SELECT QUERY HERE
[TopLink Finer]: 2007.08.19 11:31:50.000--ClientSession(25506524)--Thread(Thread[http-8080-Processor25,5,main])--client released
---------------------------------------------- [I hit Refresh on my browser here] ---------------
[TopLink Finer]: 2007.08.19 11:31:56.890--ServerSession(2285943)--Thread(Thread[http-8080-Processor24,5,main])--client acquired
[TopLink Finest]: 2007.08.19 11:31:56.890--ClientSession(19507034)--Thread(Thread[http-8080-Processor24,5,main])--Execute query ReadAllQuery(com.ligolab.application.domain.reporting.PatientResultReport)
After last refresh my Query does not get executed and the application just hangs. If I PAUSE it in debug mode I observe that it is stuck waiting in the ConnectionPool.acquireConnection()
I would appreciate any suggestions!
Tony.

Tony,
TopLink does have its own internal connection pooling by default with a Server Session. This can be changed to use the data sources of the container you are running if available and wanted.
Each read query acquires a connection and releases it once the query is completed. One exception to this is when cursored streams or scrollable cursors are used. These require the connection to be held out of the pool until the application closes the cursor/stream. Do your queries make use of this?
Doug

How to create a .mdf SQL Server database from a Data-Tier Application file that has data?

This is a noob question, though I do use SQL Server databases all the time with Entity Framework when I code in C# using Visual Studio 2013. The development environment is found below at [A]. I am trying to make a clone of a SQL Server 2008 R2
database (.mdf) that exists online. I can read, connect and work with this database in Visual Studio 2013, but I wish to make a local copy of the database, as an .MDF file. Somewhere in my notes I have a way of creating a local copy from
an online database when using Visual Studio but I forgot how (it seems, reviewing my notes, that it deals with ADO.NET which is deprecated in Visual Studio 2013 these days, or so it seems). So I'm looking for another way. What I did was create
(or export) a "Data-Tier Application File" from the online SQL Server database, with data, and it seems to have worked in that this Data-Tier Application file exists on my hard drive and seems to have data in it ("SQL Server Replication Snapshot"
is the format it seems). It contains skeleton code to create a database, but when I tried to execute it with SQL Server 2014 Management Studio, I got a bunch of errors.
So my question is:
1) Can I somehow create a .MDF SQL Server Database from an Data-Tier Application file that has data? What tool do I use? I saw this link, http://social.technet.microsoft.com/wiki/contents/articles/2639.how-to-use-data-tier-application-import-and-export-with-a-windows-azure-sql-database.aspx
and it relates to Azure, but is there a tool for C#Visual Studio 2013, standalone?
2) If there's an easy way to create a .mdf SQL Server Database file from an online file, within SQL Server Management Studio? I don't think so, since it would require Administrator permissions on the online server, which I don't have. I have permission
to read, update, delete the online database file, but strangely not to download it (the service I use has a tool for backup, but not for download).
3) same question as 2), but for Visual Studio 2013? I don't think so, since I notice none of the templates even mentions ADO.NET anymore, but instead they go with Entity Framework. Using EF I can of course do anything I want with the online database
(CRUD), but it remains online. Maybe there's a switch to make a local copy? I guess I could write a short program to suck all the data out of the online database and put it into a new, duplicate database having the same tables, that I create on
my localhost, but my question here is if there's an easier way than this, maybe a tool or command I can run from inside Visual Studio?
Any advice on any of the above questions is appreciated.
Thank you,
Paul
[A] Microsoft Visual Studio Professional 2013
Version 12.0.21005.1 REL
Microsoft .NET Framework
Version 4.5.51641
Microsoft Web Developer Tools 2013   2.0.40926.0
SQL Server Data Tools   12.0.30919.1
Microsoft SQL Server Data Tools
Windows Azure Mobile Services Tools   1.0
Windows Azure Mobile Services Tools

Thanks but these links are too general to help.
"2. what do you mean by online file?" - I mean the SQL Server database file is on a remote web server that I rent from, but I am not the administrator of. I can access my database using SQL Server Authentication, but nothing more.
Paul
What do you mean by too general? It explains on how you can use data tier application to create and deploy databases
May be this will help you to understand better
http://www.databasejournal.com/features/mssql/article.php/3911041/Creating-Data-Tier-Applications--in-SQL-Server-2008-R2.htm
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

KIMYONG : Applications Database Connection Pool 관련 parameter 설명

Purpose
JVM 이 과도한 CPU / Memory를 사용하게 되어 Application Performance에 영향을 미칠때가 있으며 이럴경우 Connection Pool 관련하여 Parameter Tunning을 해야 할때가 있습니다. 이때 사용되는 Parameter들의 의미를 설명하고자 합니다.
The Applications Database Connection Pool is a pool of JDBC database connections that are shared among java applications. Applications obtain connections from the pool by using the getJDBCConnection(...) methods of AppsContext.
Essentially, each AppsContext has a single database connection associated with it at all times.
The AOL/J layer internally borrows and returns this connection to the pool as needed to maintain connection reference that is properly initialized for the current Java tier AOL security context and NLS state.
FND_MAX_JDBC_CONNECTIONS
============================
The maximum pool size is the maximum allowed sum of the number of available connections and thenumber of locked connections. If the pool reaches the maximum size and all connections are locked, new clients will not be able to borrow a connection until one of the current clients has returned one. The default setting for this parameter is essentially unlimited (about 2 billion).
FND_JDBC_BUFFER_MIN
======================
The buffer minimum is the minimum number of connections that the pool should try to maintain in the available list. When the buffer size falls below the buffer minimum, the pool maintenance thread will be notified to create new connections. When notified, the thread will immediately attempt to create the number of connections to fill the difference. New connections will not be created if the pool is already at its maximum size. When creating new connections the thread uses the attributes of the most recent client request that resulted in a new connection being created.
Setting this parameter to "0" will disable maintenance of the buffer minimum.
However, the buffer maximum will still be maintained.
Setting this parameter to a number greater than the maximum pool size(FND_MAX_JDBC_CONNECTIONS) will disable all buffer maintenance.
FND_JDBC_BUFFER_MAX
======================
The buffer maximum is the maximum number of connections that the pool should try to maintain in the available list. During heavy usage, the buffer may exceed this maximum. However, during periods of low usage, the maintenance thread will decrease the buffer size until the buffer maximum is reached.
If the value of this parameter is an integer, (for example "20") the buffer maximum is static. If the value is a percent (for example, "20%"), the buffer maximum is not constant but instead is calculated dynamically as a percent of total pool size. The buffer minimum is also taken into account when
determining a dynamic buffer maximum.
The exact expression used is:
maximum(t) = buffer minimum + ( (FND_JDBC_BUFFER_MAX/100) * size(t) )
where maximum(t) and size(t) are the buffer maximum and pool size at some time t.
The thread is configured to periodically check the buffer size. If the buffer size is greater than the maximum, the thread will remove either the number of available connections specified by FND_JDBC_BUFFER_DECAY_SIZE or the number of connections in excess of the buffer minimum, whichever is smaller. When connections are removed from the available list, the least recently used ones are removed first.
Setting this parameter to100%, or to a number equal to FND_MAXIMUM_JDBC_CONNECTIONS, or to a number less than or equal to FND_JDBC_BUFFER_MIN will effectively prevent the maintenance thread from ever removing any connections.
FND_JDBC_BUFFER_DECAY_INTERVAL
===================================
The buffer decay interval specifies how often the connection pool maintenance thread should check the buffer size. The thread will check the buffer size at most once every FND_JDBC_BUFFER_DECAY_INTERVAL seconds. The actual time between consecutive thread cycles will vary somewhat depending on the JVM load.
This parameter, along with FND_JDBC_BUFFER_DECAY_SIZE, allows the buffer decay rate to be tuned. For example, if the buffer decay size is 2 and the buffer decay interval is one minute, the buffer decay rate will never exceed two connections per minute. When connections are removed, the least recently used ones are removed first.
FND_JDBC_BUFFER_DECAY_SIZE
=============================
The buffer decay size specifies the maximum number of connections that should be removed during any single thread cycle during which the number of available connections is greater than the buffer size. This parameter, along with FND_JDBC_BUFFER_DECAY_INTERVAL, allows the buffer decay rate to be tuned.
FND_JDBC_MAX_WAIT_TIME
=========================
The maximum wait time specifies how much time a client should spend trying to get a connection. The borrow algorithm, used to borrow an object from the pool, contains check points at which the elapsed time is compared to the maximum wait time. If it exceeds the maximum wait time, then a null object will be returned to the client. The pre-configured value for the maximum wait time is
10 seconds.
FND_JDBC_SELECTION_POLICY
============================
The selection policy determines how a connection is selected from the list of available connections for a particular client. The connection pool is pre-configured to use a cost-based selection algorithm, which selects the connection that will require the smallest amount of initialization to match the
client's context.
FND_JDBC_USABLE_CHECK
===========================
The FND_JDBC_USABLE_CHECK parameter governs whether a pl/sql query is performed before giving a connection to a client. The pool checks whether a connection is usable before handing it to a client. This always involves checking that the connection is not null and is not closed. If FND_JDBC_USABLE_CHECK is set to true, then it also verifies that the connection can be used to perform a simple PL/SQL query. (This parameter may have to be set to "true" in order to clean up
connections to a database that has been restarted.)
FND_JDBC_CONTEXT_CHECK
==========================
The FND_JDBC_CONTEXT_CHECK parameter governs whether the AOL security context and NLS state is obtained from the database when the connection is returned to the pool. If FND_JDBC_CONTEXT_CHECK is "true", when the connection is returned to the pool, the AOL security context and NLS state will be obtained from the database. (This is implemented in the DBConnObj.isReusable() method). This check must be done when the connection is returned (rather than when it is borrowed) so that the selection matching algorithm has access to the actual
session context of the connections in the available list.
FND_JDBC_PLSQL_RESET
========================
The PL/SQL reset flag, set using the variable FND_JDBC_PLSQL_RESET, governs whether the PL/SQL state associated with a connection should be freed before the pool hands the connection to the client. By default this flag is false.
If the flag is set by true, by including the line "FND_JDBC_PLSQL_RESET=true" in the .dbc file, each connection to the database will have its PL/SQL state cleared before the pool returns the connection to the client.
This is how it works. After the pool selects a connection from the available list for a client, it initializes the connection. One of the things initialization does is to set a flag that is later used by SessionManager to determine if the apps initialization routine needs to be performed for the connection. When FND_JDBC_PLSQL_RESET has been set to "true", this flag will always be set to true. After the pool initializes the connection, it also checks whether the connection is usable. In this case, this check will include a call to DBMS_SESSION.RESET_PACKAGE, which frees the PL/SQL state. The table below summaries the affect of FND_JDBC_PLSQL_RESET and the other safety check parameters on borrowing a connection from the pool.
The FND_JDBC_PLSQL_RESET parameter has been added to only to address the case where production PL/SQL global bugs are known to exist. The performance of the pool is reduced by setting this flag to true.
Reference : Note 264599.1

Purpose
JVM 이 과도한 CPU / Memory를 사용하게 되어 Application Performance에 영향을 미칠때가 있으며 이럴경우 Connection Pool 관련하여 Parameter Tunning을 해야 할때가 있습니다. 이때 사용되는 Parameter들의 의미를 설명하고자 합니다.
The Applications Database Connection Pool is a pool of JDBC database connections that are shared among java applications. Applications obtain connections from the pool by using the getJDBCConnection(...) methods of AppsContext.
Essentially, each AppsContext has a single database connection associated with it at all times.
The AOL/J layer internally borrows and returns this connection to the pool as needed to maintain connection reference that is properly initialized for the current Java tier AOL security context and NLS state.
FND_MAX_JDBC_CONNECTIONS
============================
The maximum pool size is the maximum allowed sum of the number of available connections and thenumber of locked connections. If the pool reaches the maximum size and all connections are locked, new clients will not be able to borrow a connection until one of the current clients has returned one. The default setting for this parameter is essentially unlimited (about 2 billion).
FND_JDBC_BUFFER_MIN
======================
The buffer minimum is the minimum number of connections that the pool should try to maintain in the available list. When the buffer size falls below the buffer minimum, the pool maintenance thread will be notified to create new connections. When notified, the thread will immediately attempt to create the number of connections to fill the difference. New connections will not be created if the pool is already at its maximum size. When creating new connections the thread uses the attributes of the most recent client request that resulted in a new connection being created.
Setting this parameter to "0" will disable maintenance of the buffer minimum.
However, the buffer maximum will still be maintained.
Setting this parameter to a number greater than the maximum pool size(FND_MAX_JDBC_CONNECTIONS) will disable all buffer maintenance.
FND_JDBC_BUFFER_MAX
======================
The buffer maximum is the maximum number of connections that the pool should try to maintain in the available list. During heavy usage, the buffer may exceed this maximum. However, during periods of low usage, the maintenance thread will decrease the buffer size until the buffer maximum is reached.
If the value of this parameter is an integer, (for example "20") the buffer maximum is static. If the value is a percent (for example, "20%"), the buffer maximum is not constant but instead is calculated dynamically as a percent of total pool size. The buffer minimum is also taken into account when
determining a dynamic buffer maximum.
The exact expression used is:
maximum(t) = buffer minimum + ( (FND_JDBC_BUFFER_MAX/100) * size(t) )
where maximum(t) and size(t) are the buffer maximum and pool size at some time t.
The thread is configured to periodically check the buffer size. If the buffer size is greater than the maximum, the thread will remove either the number of available connections specified by FND_JDBC_BUFFER_DECAY_SIZE or the number of connections in excess of the buffer minimum, whichever is smaller. When connections are removed from the available list, the least recently used ones are removed first.
Setting this parameter to100%, or to a number equal to FND_MAXIMUM_JDBC_CONNECTIONS, or to a number less than or equal to FND_JDBC_BUFFER_MIN will effectively prevent the maintenance thread from ever removing any connections.
FND_JDBC_BUFFER_DECAY_INTERVAL
===================================
The buffer decay interval specifies how often the connection pool maintenance thread should check the buffer size. The thread will check the buffer size at most once every FND_JDBC_BUFFER_DECAY_INTERVAL seconds. The actual time between consecutive thread cycles will vary somewhat depending on the JVM load.
This parameter, along with FND_JDBC_BUFFER_DECAY_SIZE, allows the buffer decay rate to be tuned. For example, if the buffer decay size is 2 and the buffer decay interval is one minute, the buffer decay rate will never exceed two connections per minute. When connections are removed, the least recently used ones are removed first.
FND_JDBC_BUFFER_DECAY_SIZE
=============================
The buffer decay size specifies the maximum number of connections that should be removed during any single thread cycle during which the number of available connections is greater than the buffer size. This parameter, along with FND_JDBC_BUFFER_DECAY_INTERVAL, allows the buffer decay rate to be tuned.
FND_JDBC_MAX_WAIT_TIME
=========================
The maximum wait time specifies how much time a client should spend trying to get a connection. The borrow algorithm, used to borrow an object from the pool, contains check points at which the elapsed time is compared to the maximum wait time. If it exceeds the maximum wait time, then a null object will be returned to the client. The pre-configured value for the maximum wait time is
10 seconds.
FND_JDBC_SELECTION_POLICY
============================
The selection policy determines how a connection is selected from the list of available connections for a particular client. The connection pool is pre-configured to use a cost-based selection algorithm, which selects the connection that will require the smallest amount of initialization to match the
client's context.
FND_JDBC_USABLE_CHECK
===========================
The FND_JDBC_USABLE_CHECK parameter governs whether a pl/sql query is performed before giving a connection to a client. The pool checks whether a connection is usable before handing it to a client. This always involves checking that the connection is not null and is not closed. If FND_JDBC_USABLE_CHECK is set to true, then it also verifies that the connection can be used to perform a simple PL/SQL query. (This parameter may have to be set to "true" in order to clean up
connections to a database that has been restarted.)
FND_JDBC_CONTEXT_CHECK
==========================
The FND_JDBC_CONTEXT_CHECK parameter governs whether the AOL security context and NLS state is obtained from the database when the connection is returned to the pool. If FND_JDBC_CONTEXT_CHECK is "true", when the connection is returned to the pool, the AOL security context and NLS state will be obtained from the database. (This is implemented in the DBConnObj.isReusable() method). This check must be done when the connection is returned (rather than when it is borrowed) so that the selection matching algorithm has access to the actual
session context of the connections in the available list.
FND_JDBC_PLSQL_RESET
========================
The PL/SQL reset flag, set using the variable FND_JDBC_PLSQL_RESET, governs whether the PL/SQL state associated with a connection should be freed before the pool hands the connection to the client. By default this flag is false.
If the flag is set by true, by including the line "FND_JDBC_PLSQL_RESET=true" in the .dbc file, each connection to the database will have its PL/SQL state cleared before the pool returns the connection to the client.
This is how it works. After the pool selects a connection from the available list for a client, it initializes the connection. One of the things initialization does is to set a flag that is later used by SessionManager to determine if the apps initialization routine needs to be performed for the connection. When FND_JDBC_PLSQL_RESET has been set to "true", this flag will always be set to true. After the pool initializes the connection, it also checks whether the connection is usable. In this case, this check will include a call to DBMS_SESSION.RESET_PACKAGE, which frees the PL/SQL state. The table below summaries the affect of FND_JDBC_PLSQL_RESET and the other safety check parameters on borrowing a connection from the pool.
The FND_JDBC_PLSQL_RESET parameter has been added to only to address the case where production PL/SQL global bugs are known to exist. The performance of the pool is reduced by setting this flag to true.
Reference : Note 264599.1

Weblogic Data source is not releasing connections

Hi All,
Weblogic JDBC data source is not releasing connection until JDBC connection is deleted and created again. Could you please let me know this is a database issue or weblogic jdbc driver issue. We are using weblogic 10.1. Please see the following xml for JDBC driver.
Although maximum connections are set to 300, it stills keeps increasing connections over 300. This issue is resolved only when jdbc data source is deleted and created again.
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
<name>abc_admin_STGNCB</name>
<jdbc-driver-params>
<url>jdbc:oracle:thin:@10.151.43.54:1521:STGNCB</url>
<driver-name>oracle.jdbc.OracleDriver</driver-name>
<properties>
<property>
<name>user</name>
<value>abc_admin</value>
</property>
<property>
<name>portNumber</name>
<value>1521</value>
</property>
<property>
<name>SID</name>
<value>STGNCB</value>
</property>
<property>
<name>serverName</name>
<value>10.151.43.54</value>
</property>
</properties>
<password-encrypted>{3DES}wc5vg5GIbPtt+b8vWY0i5Q==</password-encrypted>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<initial-capacity>20</initial-capacity>
<max-capacity>300</max-capacity>
<capacity-increment>10</capacity-increment>
<connection-creation-retry-frequency-seconds>30</connection-creation-retry-frequency-seconds>
<statement-cache-size>200</statement-cache-size>
<pinned-to-thread>true</pinned-to-thread>
<identity-based-connection-pooling-enabled>true</identity-based-connection-pooling-enabled>
</jdbc-connection-pool-params>
<jdbc-data-source-params>
<jndi-name>jdbc/ABC_TX_DATASOURCE</jndi-name>
<jndi-name>jdbc/ABC_NON_TX_DATASOURCE</jndi-name>
<jndi-name>jdbc/ABC_TX_EVENT_DATASOURCE</jndi-name>
<jndi-name>jdbc/ABC_NON_TX_EVENT_DATASOURCE</jndi-name>
<jndi-name>jdbc/ABC_DATASOURCE</jndi-name>
<jndi-name>abc.cdb.DataSource</jndi-name>
<global-transactions-protocol>EmulateTwoPhaseCommit</global-transactions-protocol>
</jdbc-data-source-params>
</jdbc-data-source>
Edited by: bpenugon on Aug 24, 2010 8:02 AM

The root cause is pinned-to-thread is enabled. When the application finishes using the connection and calls connection.close(), WebLogic Server keeps the connection with the execute thread and does not return it to the connection pool. The connection pool maximum capacity is ignored when pinned-to-thread is enabled. So you saw the number of connections in connection pool keeps increasing over 300.
Set pinned-to-thread to false can solve the problem.

How do the application servers connect the new database after failing over from primary DB to standby DB

How do the application servers connect the new database after failing over from primary DB to standby DB?
We have setup a DR environment with a standalone Primary server and a standalone Physical Standby server on RHEL Linux 6.4. Now our application team would like to know:
When the primary DB server is crashed, the standy DB server will takeover the role of primary DB through the DataGuard fast failover. As the applications are connected by the primary DB IP before,currently the physical DB is used as a different IP or listener. If this is happened, they need to stop their application servers and re-configure their connection so the they coonect the new DB server, they cannot tolerate these workaround.
Whether does oracle have the better solution for this so that the application can automatically know the role's transition and change to the new IP without re-confige any connection and shutdown their application?
Oracle support provides us the answer as following:
==================================================================
Applications connected to a primary database can transparently failover to the new primary database upon an Oracle Data Guard role transition. Integration with Fast Application Notification (FAN) provides fast failover for integrated clients.
After a failover, the broker publishes Fast Application Notification (FAN) events. These FAN events can be used in the following ways:
Applications can use FAN without programmatic changes if they use one of these Oracle integrated database clients: Oracle Database JDBC, Oracle Database Oracle Call Interface (OCI), and Oracle Data Provider for .NET ( ODP.NET). These clients can be configured for Fast Connection Failover (FCF) to automatically connect to a new primary database after a failover.
JAVA applications can use FAN programmatically by using the JDBC FAN application programming interface to subscribe to FAN events and to execute event handling actions upon the receipt of an event.
FAN server-side callouts can be configured on the database tier.
FAN events are published using Oracle Notification Services (ONS) and Oracle Streams Advanced Queuing (AQ).
=======================================================================================
Who has the experience and the related documentation or other solutions? we don't have the concept of about FAN.
Thank very much in advance.

Hi mesbeg,
Thanks alot.
For example, there is an application JBOSS server connecting the DB, we just added another datasource and put the standby IP into the configuration file except adding a service on DB side like this following:
        <subsystem xmlns="urn:jboss:domain:datasources:1.0">
        <datasources>
                <datasource jta="false" jndi-name="java:/jdbc/idserverDatasource" pool-name="IDServerDataSource" enabled="true" use-java-context="true">
                    <connection-url>jdbc:oracle:thin:@<primay DB IP>:1521:testdb</connection-url>
                    <connection-url>jdbc:oracle:thin:@<standby DB IP>:1521:testdb</connection-url>
                    <driver>oracle</driver>
                    <pool>
                        <min-pool-size>2</min-pool-size>
                        <max-pool-size>10</max-pool-size>
                        <prefill>true</prefill>
                    </pool>
                    <security>
                        <user-name>TEST_USER</user-name>
                        <password>Password1</password>
                    </security>
                    <validation>
                        <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"/>
                        <validate-on-match>false</validate-on-match>
                        <background-validation>false</background-validation>
                        <use-fast-fail>false</use-fast-fail>
                        <stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"/>
                        <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/>
                    </validation>
                </datasource>
                <drivers>
                    <driver name="oracle" module="com.oracle.jdbc">
                        <xa-datasource-class>oracle.jdbc.OracleDriver</xa-datasource-class>
                    </driver>
                </drivers>
            </datasources>
        </subsystem>
If the failover is occurred, the JBOSS will automatically be pointed to the standby DB. Additional actions are not needed.

Cloning Oracle Applications Release 12 with Rapid Clone

Hi,
I was going through metalink doc 406982.1 Cloning Oracle Applications Release 12 with Rapid Clone.
I couldn't understand a few points.
I would appreciate if someone can guide me regarding the following queries.
There is a statement in the doc
1)An important principle in Oracle Applications cloning is that the system is cloned, rather than the topology ....
--What is meant by topology in this description?
2)The Cloning methodology posted on this document requires full Autoconfig complience.
--didn't get this point.
3)Note: In the copying tasks below, UNIX/Linux users should ensure that the symbolic links (soft links) are preserved when copying. On most UNIX platforms, this can be accomplished with the cp -RH command. Consult the UNIX man page for the cp command to check the parameters available on your platform.
--what soft links are being talked about?will the regular cp -R command not preserve the soft links?
4)For patching AutoConfig on the E-Business Suite R12 instance, AutoConfig needs to be enabled on both the applications tier and the database tier. (387859.1)
--HOw do I check if AutoConfig is enabled or not?
5)Why do I need to synchronize appsutil on database tier from application tier?
6)Why do we need to maintaain snapshot information?
What does snapshot actually do?
Thannks,
Rushi

This is what I get when doing "grep rror" from 9239089 logfile.
will be ignored without error.
will be ignored without error.
will be ignored without error.
0 files had fatal errors.
0 files had fatal errors.
Performing second half of mirrored copies...
No mirrored copies were executed in this patch.
oracle/apps/ad/splice/adError [120.0.12010000.1] {oracle/apps/ad/splice/adError.class }
Cause: Error while trying to read metadata from file /appldev/apps/tech_st/10.1.2/forms/java/frmall.jar: No metadata entry META-INF/JRIMETA.DAT found
Cause: Error while trying to read metadata from file /appldev/apps/tech_st/10.1.2/jlib/ewt3.jar: No metadata entry META-INF/JRIMETA.DAT found
Cause: Error while trying to read metadata from file /appldev/apps/tech_st/10.1.2/jlib/ewt3-nls.jar: No metadata entry META-INF/JRIMETA.DAT found
Cause: Error while trying to read metadata from file /appldev/apps/tech_st/10.1.3/lib/xmlparserv2.jar: No metadata entry META-INF/JRIMETA.DAT found
Cause: Error while trying to read metadata from file /appldev/apps/tech_st/10.1.3/j2ee/oafm/applications/mapviewer/web/WEB-INF/lib/mvclient.jar: No metadata entry META-INF/JRIMETA.DAT found
Cause: Error while trying to read metadata from file /appldev/apps/tech_st/10.1.3/j2ee/home/lib/mail.jar: No metadata entry META-INF/JRIMETA.DAT found
Cause: Error while trying to read metadata from file /appldev/apps/tech_st/10.1.3/j2ee/home/lib/activation.jar: No metadata entry META-INF/JRIMETA.DAT found
oracle/apps/media/ieu_status_error
oracle/xml/parser/v2/XMLErrorMsg
oracle/xml/parser/v2/mesg/XMLErrorMesg
oracle/xml/parser/v2/mesg/XMLErrorMesg_ar_AE
oracle/xml/parser/v2/mesg/XMLErrorMesg_ca_ES
oracle/xml/parser/v2/mesg/XMLErrorMesg_cs_CZ
oracle/xml/parser/v2/mesg/XMLErrorMesg_da_DK
oracle/xml/parser/v2/mesg/XMLErrorMesg_de_DE
oracle/xml/parser/v2/mesg/XMLErrorMesg_el_GR
oracle/xml/parser/v2/mesg/XMLErrorMesg_en_US
oracle/xml/parser/v2/mesg/XMLErrorMesg_es_AR
oracle/xml/parser/v2/mesg/XMLErrorMesg_es_ES
oracle/xml/parser/v2/mesg/XMLErrorMesg_fi_FI
oracle/xml/parser/v2/mesg/XMLErrorMesg_fr_FR
oracle/xml/parser/v2/mesg/XMLErrorMesg_hu_HU
oracle/xml/parser/v2/mesg/XMLErrorMesg_it_IT
oracle/xml/parser/v2/mesg/XMLErrorMesg_iw_IL
oracle/xml/parser/v2/mesg/XMLErrorMesg_ja_JP
oracle/xml/parser/v2/mesg/XMLErrorMesg_ko_KR
oracle/xml/parser/v2/mesg/XMLErrorMesg_nl_NL
oracle/xml/parser/v2/mesg/XMLErrorMesg_no_NO
oracle/xml/parser/v2/mesg/XMLErrorMesg_pl_PL
oracle/xml/parser/v2/mesg/XMLErrorMesg_pt_BR
oracle/xml/parser/v2/mesg/XMLErrorMesg_pt_PT
oracle/xml/parser/v2/mesg/XMLErrorMesg_ro_RO
oracle/xml/parser/v2/mesg/XMLErrorMesg_ru_RU
oracle/xml/parser/v2/mesg/XMLErrorMesg_sk_SK
oracle/xml/parser/v2/mesg/XMLErrorMesg_sv_SE
oracle/xml/parser/v2/mesg/XMLErrorMesg_tr_TR
oracle/xml/parser/v2/mesg/XMLErrorMesg_zh_CN
oracle/xml/parser/v2/mesg/XMLErrorMesg_zh_TW
Errors and warnings are listed in the log file
Also I am getting same kind of errors for patches 8919489,9171651,9833058 and 12404574.
Although there were neither failures nor any ORA- error in any of the log files.
Please guide what needs to be done regarding the shown errors for the patches.
after executing adpreclone on db tier I got the following message in logfile.
error while preclone on db tier:Attempt to remove existing adcrdb.zip failed
What could have been wrong?
Is the message normal and can it be safely ignored?
As a pre-install task of patch 9239089,I executed adgrantsall.sql
which gave me a prompt Enter a value for 1:
I entered apps (apps schemaname/username)
Is it ok?
Thanks,
Rushi

Cloning Oracle Applications Release 11i

Hi,
for Cloning Oracle Applications Release 11i , is it ncessary to copy jre, oui and oraInventory directories from source database tier file system to trget ?
Many thanks before.

Applications / EBS is discussed in this category http://forums.oracle.com/forums/category.jspa?categoryID=11 (and there are more, if you look at the forums home page)
But, in general the oraInventory must exist to be able to patch or otherwise maintain the installation. Wouldn't think copying directories is a supported cloning method... Again, check with the proper forum. And use the Search function!

Problem if three tier application run through WebStart

I developed a three tier application (Messaging Service (JMS,JNDI))
When i run this applivation without web start it run without problem
but when i run this application through web start the middel tier (JBoss) throwing some exception relATED TO CONNECTION
Can u give me any hint to solve this problem
regards
tushar

I had no problem with my application .i have a swing based client application that connects to JBoss Application Server to connect to Session Beans, JDO,etc. IT works fine. You need to distribute JBoss-all-client.jar.
Can you describe your error

Error deploying data tier application to SQL Azure at "Registering metadata for database" step ... should I care?

I'd like to move an on-premesis SQL Server Database to SQL Azure. I've used SQL Mgmt Studio to Extract Data Tier Application and save my db as a dacpac file. Now I'm connected to my Azure server and I've chosen to Deploy Data Tier Application. I select my
dacpac and the deploy starts but then on the last step "Registering metadata for database" it times out. I've tried it a couple of times and each time the deployed database is there and appears to be fully populated, but I'm not sure if I can ignore
that error and continue. What is supposed to happen in that step, and should I expect it to fail when deploying to SQL Azure?
I'm following the steps here http://msdn.microsoft.com/en-us/library/hh694043.aspx in the Using Migration Tools > Data-tier Application DAC Package section, except that to deploy there's no SQL Mgmt Studio > Object Explorer [server]
> Management >"Data Tier Applications" node, so I'm deploying by right-clicking on the server name and choosing "Deploy Data-tier Application".
My (total) guess here is that it's deployed the database fine and it's doing whatever magic happens when you register a data tier application, except that it's not working for SQL Azure.
I'm running against a server created for the new Azure service tiers, not against a Web/Business edition server.
The full details of error I get are below.
thanks,
Rory
TITLE: Microsoft SQL Server Management Studio
Could not deploy package.
Warning SQL0: A project which specifies SQL Server 2008 as the target platform may experience compatibility issues with SQL Azure.
(Microsoft.SqlServer.Dac)
ADDITIONAL INFORMATION:
Unable to register data-tier application: Unable to reconnect to database: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft.Data.Tools.Schema.Sql)
Unable to reconnect to database: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft.Data.Tools.Schema.Sql)
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.9213&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
The wait operation timed out
BUTTONS:
OK

Hello,
The registration process creates a DAC definition that defines the objects in the database, and register the DAC definition in the master system database in Windows Azure SQL Database.
Based on the error message, there is timeout error when connect to SQL Database. Did you deploy a large database? When move large data to Azure SQL Database, it is recommended to use SQL Server Integration Services (SSIS) and BCP utility.
Or you can try to create a client application with the Data-Tier Application Framework (DACFx) client tool to import database and handle connection loss it by re-establish the connection.
Reference: http://sqldacexamples.codeplex.com/
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

Application designer connection to App Server

Hii,
I have a very basic level doubt, we all know that App Designer is 2 tier application/editor. But I observed lot of times, if I shutdown App server and try to connect through App designer, I get some debug error.Please can anybody tell me App server process connectivity with App Desigenr
Thanks in Advance

Thanks a lot Ajit and Nicolos.. Please find below error message
"Debugging disabled.Communication failure during rec(): WSAECONNRESET(10054) connection reset by peer
(143,41)"
How I am getting this error:
After login in App designer (in 2 tier mode), when I am shutting down App server (normal mode), I am getting this error only one time.
So my confusion here is how App designer debugging feature depends on App server?
Thanks

How can I create a mobile application to connect with my php system

II have few question to ask all expert here :
1. Im using Netbeans IDE, how can I compile the .java file to .jar ?
2. Currently, I have created a point of sales application using php and I hope to create a Mobile application to connect with tis system. So, anyone can let me know what I need to start ?
3. Im using postgresql database, anyone here know how to connect with mobile application?

!. When you build java application in NetBeans (standard one) you just click 'Build' or 'Clean and Build' and your jar file is waiting for you inside 'dist' directory of your project
2. Connecting MIDP application to the server running PHP scripts is not a problem, just connect using simple HTTP with GET or POST and you are done, google on it!
3. You can connect to the database using some kind of PHP/JSP/ASP or whatever application you want and then using method from point 2 to send and retrive values, you can do it with web services as well, possibilities are endless
Hope this helps!
Kris

Unable to create application server connection in Jdeveloper 10.1.3.3

Hi All,
I am using Jdeveloper 10.1.3.3. As my soa environement is clustered and we have 2 nodes on server.
While create application server connection jeveloper is giving error as : **Bad OPMN server host address*. I am able to accesss application using mozila or internet explorer. Will it provide different host name while soa is installed in clustered environment. Please help me in this.
Regards,
Adhi

Hi ,
Are you behind a proxy in Firefox or IE?
If so try to give the same proxy and the proxy avoidance IP's in JDeveloper proxy configuration.
If server couldnot be communicated from Jdev then this will be the first place i will look into .
Thanks,
Praveen

Error While creating Application server connection

Hi ,
I am a newbie to SOA suite . I have installed Oracle XE Database , Oracle Jdeveloper 10.1.3.3.0.3 and Oracle SOA Suite 10g (10.1.3.1) ( file name soa_windows_x86_
101310_disk1.zip) on my windows XP machine
Now I created a "Hello World Bepel Process '" . For deploying it I was trying to create an application server connection . I am not sure that I need to install anymore things or not .
Here are the steps which happened while I was trying to make connection to application server.
1> Connection Name : Gave as "AppServerConnection1"
Connection Type as "Standalone OC4J 10g 10.1.3"
2> UserName as : oc4jadmin
Password : Gave my password
3> Hostname : localhost
RMI Port was coming as 23791 as default ( Please note that I checked opmn folder and tried to use the RMI from the xml file too)
4> While testing I was getting error as "For input string: "23791home"
Not sure if i need to install anything ( Probably Application Server ) more .
Please let me know what I need to do and if i need to install anything else where will I find the file ?
Thanks in advance

Hi,
Connection Type as "Standalone OC4J 10g 10.1.3"
When choosing the connection you need to select the connection as Oracle Application Server 10.1.3 not Standalone OC4J 10g 10.1.3

Preblem facing in creating application server connection in Jdeveloper

Hi All,
I am using weblogic 10.3.1 and Jdeveloper 10.1.3.5.
I want to deploy an ear file in my weblogic server. Can anyone plesae guide me how can I create a application server connection in Jdeveloper 10.1.3.5
Thanks in Advance!!

Can't you just go to the connections navigator, right-click and select New Application Server Connection, and then just use the wizard? What is the problem you are facing?
Try selecting Oracle Application Server 10 or OC4J 10g.

JClient 2 Tier Application Release Connection

Similar Messages

Maybe you are looking for