Migrate Applications & database

AIX 5.3
There are Oracle Retail environment we have almost all modules of retek. We are planning to migrate all Production modules to another new separate server.
Example:
Current IP Need change IP
RMS 162.23.124.41 12.60.0.2
RPM 162.23.124.42 12.60.0.3
SIM 162.23.124.43 12.60.0.4
DB 162.23.124.44 12.60.0.4
And many more.
On this point my question is that any dependency to migrate them?
Thanks,
Edited by: user11969485 on Jul 31, 2012 4:55 AM

Hi,
it is maybe to ask a question in another forum about Retail: Retail
Herald ten Dam
http://htendam.wordpress.com

Similar Messages

Service application database 2010 migration to 2013

If we want to migrate e.g. only Managed metadata service application database from 2010 to 2013 environment what will be exact steps?
(I know for content db we have to use Powershell Mount command).
But I guess in case of service application databases Mount command will not work, Can any one say if it true or not?
What are the steps involved to migrate such service application databases through Powershell?

See here for a guide:
http://technet.microsoft.com/en-us/library/jj839719%28v=office.15%29.aspx
In short, you create a new MMS and reference the copy of the MMS database you've moved to the new SQL instance for 2013.

How can I determine what sites are being referenced within Central Admin Upgrade and Migration Manage Databases Upgrade Status?

When I go to Central Admin > Upgrade and Migration > Manage Databases Upgrade Status, I have 2 content databases which have the status:
Database is up to date, but some sites are not completely upgraded.
How can I determine which sites are not completely upgraded?

Manage Databases Upgrade Status will provide you all active and offline DB details, you can get same result
using below PowerShell cmdlet.
Get-SPDatabase and Get-SPContentDatabase will provide all active database/Content DB in Farm which include Service application db, central admin DB.
Get-SPDatabase | Format-Table Name, ID
Coming back to your question, if you find that there are some site are not completely upgraded then run below command and understand the cause if issue on specific DB.
Test-SPContentDatabase WSS_ContentDB_Name
If you find any missing file issue in DB then resolve these issue to upgrade content database.
(verify all customizations referenced within the content database are also installed in the web application. This cmdlet can be issued
against a content database currently attached to the farm, or a content database that is not connected to the farm )
Use the Upgrade-SPContentDatabase cmdlet
to resume a failed database upgrade or begin a build-to-build database upgrade against a SharePoint content database
Upgrade-SPContentDatabase WSS_Content
reference:
http://technet.microsoft.com/en-us/library/ff607813(v=office.15).aspx
http://technet.microsoft.com/en-us/library/ff607941(v=office.15).aspx
If my contribution helps you, please click Mark As Answer on that post and
Vote as Helpful
Thanks, ShankarSingh(MCP)

'Incorrect Login Name' error after migrating application in planning

Hi,
We are doing a migration to Planning 9.2.1 from a pre-system 9 version (3.5), using sql server 2000 as repository
System 9 is installed in a fresh new server, and we are copying the applications/repositories from the old server.
The admin user is the same in old installation and in new one.
At the moment, all products are installed in the same server
We have already sucessfully migrated the essbase applications, including substitution variables and users
We had a problem creating a new application in planning, reading these forums we added External Authentication to Shared Services, and created application succesfully.
We created the UDL for old database in SQL server and new essbase. Test connection was succesfull
Created DSN based on UDL, test connection was succesfull
We inserted application to migrate into PLN database, table HSX_DATASOURCES
Saved SID for admin user (5001)
Opened Desktop Planning, and opened the aplication.
We got the 'upgrade application' message, and we upgraded it. No errors reported.
We replaced the SID with the previously saved one. Actually, they are the same SID
Now, when we try to open the migrated application in Desktop Planning, we get a 'Failled to Open application: M_09 Incorrect login name'
We have already verified that the admin user id dbowner of the database in sql server 2000
The event log only says the following
Error*16*HypAdmin*4/15/2009 11:54:12 AM*CHspSession.cpp*Line 119*Incorrect login name*
Any help will be appreciated!
P.S. please excuse my writing skills, I am not a native english speaker.
Edited by: hectorsosar on 15/04/2009 10:44 AM

Please nevermind my previous post. I didn't read carefully enough, that the SID to save and copy was from the newly created applciation, not from old app. Now everything worls ok.
Thanks, and regards,
Hector

Migrating application from tomcat 3 to tomcat 5

Hello everybody,
Does anyone have information about some kind of manual or tutorial with steps to migrate applications from Tomcat 3 to Tomcat 5??
Thanks a lot,
Johnny

What issues are you having? There have been some important changes between the Servlet and JSP specs between the two but most of these have been additions - nothing that will be too hard to handle.
Does your application use a database? If so there have been configuration changes between Tomcat 3 and 5 but for that the Tomcat 5 docs are very good at telling you what you need.
I would start by trying it and see where you get problems. I think it will be easier than you think, depending on how complicated your app is.

Migrating application from Development to Production

Good day all,
Our development phase came to an end and now we need to "deploy" our application on the production server (with it's own OID). Note that we're on release 10.1.2.
In my mind we need to do the following:
- Export users/groups using the OID utilities.
- Export database objects schema containing tables, procedures, functions... by creating a dump.
- Export Page groups, db providers using transport sets.
Just to confirm, is that what we need to do? Can anyone give me some details (especially on 1 and 2)?
Thanks is advance!
Jaco

These are the steps in general for performing the deployment.
For details on OID utilities, see
http://download-west.oracle.com/docs/cd/B14099_01/manage.1012/b14082/tools.htm#i1041008
In particular you would use ldapsearch (and outputting the result to a file) or ldifwrite (to directly write to the file) and bulkload (to load the data output from the development oid to production oid) utilities in particular to achieve the migration.
For schema migration of database schema - make sure that the schema components (tables, triggers, other objects) are exported and imported and there are no invalid objects that the database provider depends on before you start the next phase of migration (of portal content).

Response time much more in migrated AIX database than in Windows database

We migrated a 9.2.0.6 database from windows to AIX (on same oracle version). Initially we were getting really slow response on direct sqls and batch sqls fom application server. Then we tuned aix database a bit and got a better response time for direct sqls on aix database.
Now queries run faster on aix database than the db on windows.
However, the queries from applciation (ACCURATE application) are still twice slower on aix database compared to windows database.
Can anyone suggest a possible cause or tuning area?
We have checked on network level and found no bottlenecks.
Regards,
Garima

user650817 wrote:
We migrated a 9.2.0.6 database from windows to AIX (on same oracle version). Initially we were getting really slow response on direct sqls and batch sqls fom application server. Then we tuned aix database a bit and got a better response time for direct sqls on aix database.
Now queries run faster on aix database than the db on windows.
However, the queries from applciation (ACCURATE application) are still twice slower on aix database compared to windows database.
Can anyone suggest a possible cause or tuning area?Garima,
if you have particular queries that you know of that are behaving differently, you could start right away by comparing the execution plans and tracing the execution using the SQL trace facility and the "tkprof" trace file analyzer.
If you want to get an overview of the database performance, you should consider installing STATSPACK on both systems if you haven't done so yet and create snapshots to compare statspack reports from both systems for a representative time period. This way you can gather information about the top wait events and top SQLs of the periods analyzed.
By the way, how did you "migrate" the database? Did you use export/import to migrate? What about the statistics for the cost based optimizer, could these be different between the two systems or are you still using the rule based optimizer?
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

Upgrade Application database

How to upgrade Application database from 9.2.0.6 to 9.2.0.8
Solaris 5.9 (64 bit)
appl server version 11.5.10.2
which Doc id i should refer ....plz let me know
do the needful..

Hi
I'm not certain of the exact patch you need but you will find these on MetaLink. The quickest way would be to raise an SR and ask Oracle for the patch number..
You may also want to post this to the database forum as this is the Discoverer forum: General Database Discussions
Best wishes
Michael

Unable to connect Oracle Application Database using Discoverer Admin 10g

Hi,
I have installed oracle Admin 10g on my machine and trying to connect oracle application database but every time i am getting error like "Unable to connect to: user@hostname Failed to connect to database Unable to connect to Oracle Application Database. Invalid username/password".
Installed BI Discoverer Admin 10.1.2.1
Discoverer Admin Client 10.1.2.48.18
Database 9i
I have done following steps:
1. Selected radio button for Connect to Application EUL's.
2.Gateway User ID (GWYUID)/Password :APPLSYSPUB/PUB
3.FNDNAME:APPS
I able to connect discoverer plus.
Thanks
Ravi

Hi Ravi
Glad to hear you solved this. It is very gratifying when one solves it alone, don't you think?
Best wishes
Michael

Migration oracle database 8.1.7.3 to 10.2.0.2

Hi,
I have a problem to migrate my database in 8.1.7.3 to 10.2.0.2 on different database server because the size fo this database is 2200Gigas.
With RMAN or copy it's not possible because the database version are different.
The solution is the export/import but it's probably too long.
Anybody have a solution

The other solution is "Database Upgrade". Here are the basic steps whci you can perform for this:
1) Install oracle 8i (with same patchset as the old one) and oracle 10g on new server
2) Restore the RMAN backup of your 8i database on new server and start the database using 8i home.
3) Apply 8.1.7.4 patch on 8i DB
4) Either run DBUA or use manual update to update you 8i DB to 10g
Here is the doc for Database Upgrade process:
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14238/toc.htm
Daljit Singh

How can i Migrate a database from DB2 to SQL Server 2008r2.

Hi Gurus,
Kindly help me letting me know the process for migrating the database from DB2 to SQL Server.
1) Is there any way to migrate a database from DB2 to SqlServer. (My assumption is we can not migrate database, if wrong correct me gurus).
2) Or we can only transfer data from that DB2 database to SQL Server (Using SSIS packages).
Please help me knowing the process to migrate the data from DB2 server to MSSQL server. Even am reading the documents available in the web.
Thanks in advance.. :)

Microsoft provide a migration assistant for DB2 to SQL Server:
http://www.microsoft.com/en-us/download/details.aspx?id=45296
SQL Server Migration Assistant (SSMA) is a free supported tool from Microsoft that simplifies database migration process from DB2 to SQL Server and Azure SQL DB. SSMA automates all aspects of migration including migration assessment analysis, schema and
SQL statement conversion and data migration.
Hope that helps

Export - Import in Oracle Application Database

The export in Oracle Applications Database works fine.
But the import always show some issue and sometimes never completes.
Even if it completes it complete with error , how to ensure an error free export/import ?
How to handle a table movement if the table consists of a LONG column ?

The errors are cannot import this tables..
Also mostly are of Long tables..Any IMP-XXXXX or ORA-XXXXX messages?
Can you explain how long objects are exported and imported ?What type of objects?
What is the database version?
Are you doing a full database import?
Also sometimes import hangs for 2/3 days?Does it hang when importing a specific object?
Did you follow the steps outlined in the following notes when you did the Export/Import?
Note: 362205.1 - 10g Release 2 Export/Import Process for Oracle Applications Release 11i
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=362205.1
Note: 230627.1 - 9i Export/Import Process for Oracle Applications Release 11i
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=230627.1

Dreamweaver 8 errors on Application - Databases - Viewing Table (MySQL)

I have the database setup for DW8 to use and it works it just gives me errors when I go into Application-Databases and open up a table to inspect the keys inside it.
Dreamweaver 8.0.2 with CF8extensions
Coldfusion 8,0,1,195765
mysql 5.0.67
win2000pro sp4
It pops up "SQL type not recognized: "int unsigned"
Also it gives tells me "Required" text next to each key in the table

xmousex wrote:
> I completely mirrored this setup on a windows 2000 pro
machine and had zero
> problems getting it all hooked up and running in about
15 minutes. Given that
> no one here has demonstrated having even a clue on the
answer, I'm going to
> conclude that Dreamweaver and Mysql do not work together
on windows XP home.
You're free to come to that conclusion, but you would be
totally wrong.
David Powers
Author, "Foundation PHP for Dreamweaver 8" (friends of ED)
Author, "Foundation PHP 5 for Flash" (friends of ED)
http://foundationphp.com/

DB link problem between active Data Guard and report application database

My database version in 11.2.0.2.0 and OS is Oracle Solaris 10 9/10.
I am facing a problem in my Active data guard Database for reporting purpose. Active Data guard information is as below.
SQL> select name, database_role, open_mode from v$database;
NAME DATABASE_ROLE OPEN_MODE
ORCL PHYSICAL STANDBY READ ONLY WITH APPLY
Problem detail is below
I have created a db link (Name: DATADB_LINK) between active data guard and report application database for reporting purpose.
SQL> create database link DATADB_LINK connect to HR identified by hr using 'DRFUNPD';
Database link created.
But when I run a query using db link from my report application database I got this below error.
ORA-01555: snapshot too old: rollback segment number 10 with name "_SYSSMU10_4261549777$" too small
ORA-02063: preceding line from DATADB_LINK
Then I check Active Data Guard database alart log file and get below error
ORA-01555 caused by SQL statement below (SQL ID: 11yj3pucjguc8, Query Duration=1 sec, SCN: 0x0000.07c708c3):SELECT "A2"."BUSINESS_TRANSACTION_REFERENCE","A2"."BUSINESS_TRANSACTION_CODE",MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'feature' THEN "A1"."TRANS_DATA_VALUE" END ),MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'otherFeature' THEN "A1"."TRANS_DATA_VALUE" END )
But the interesting point if I run the report query directly in Active Data Guard database, I never got error.
So is it a problem of DB link between active Data Guard and other database?

Fazlul Kabir Mahfuz wrote:
My database version in 11.2.0.2.0 and OS is Oracle Solaris 10 9/10.
I am facing a problem in my Active data guard Database for reporting purpose. Active Data guard information is as below.
SQL> select name, database_role, open_mode from v$database;
NAME DATABASE_ROLE OPEN_MODE
ORCL PHYSICAL STANDBY READ ONLY WITH APPLY
Problem detail is below
I have created a db link (Name: DATADB_LINK) between active data guard and report application database for reporting purpose.
SQL> create database link DATADB_LINK connect to HR identified by hr using 'DRFUNPD';
Database link created.
But when I run a query using db link from my report application database I got this below error.
ORA-01555: snapshot too old: rollback segment number 10 with name "_SYSSMU10_4261549777$" too small
ORA-02063: preceding line from DATADB_LINK
Then I check Active Data Guard database alart log file and get below error
ORA-01555 caused by SQL statement below (SQL ID: 11yj3pucjguc8, Query Duration=1 sec, SCN: 0x0000.07c708c3):SELECT "A2"."BUSINESS_TRANSACTION_REFERENCE","A2"."BUSINESS_TRANSACTION_CODE",MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'feature' THEN "A1"."TRANS_DATA_VALUE" END ),MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'otherFeature' THEN "A1"."TRANS_DATA_VALUE" END )
But the interesting point if I run the report query directly in Active Data Guard database, I never got error.
So is it a problem of DB link between active Data Guard and other database?
Check this note which is applicable for your environment
*ORA-01555 on Active Data Guard Standby Database [ID 1273808.1]*
also
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:8908307196113

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

Migrate Applications & database

Similar Messages

Maybe you are looking for