Applications database issue

HI
i am getting the issue of addbctl.sh exiting with status 9 when i am trying to start the database
what could be the reason
hoping ur reply
TIA
Nikki

Hi bheetal
LSNRCTL for Linux: Version 9.2.0.5.0 - Production on 01-FEB-2008 10:46:25
Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
Connecting to (ADDRESS=( lsnrctl status PROD1
PROTOCOL=IPC)(KEY=EXTPROCPROD1))
STATUS of the LISTENER
Alias PROD1
Version TNSLSNR for Linux: Version 9.2.0.5.0 - Production
Start Date 01-FEB-2008 10:44:07
Uptime 0 days 0 hr. 2 min. 18 sec
Trace Level off
Security OFF
SNMP OFF
Listener Parameter File /apps/sam/prod1db/9.2.0/network/admin/PROD1_apps/listener.ora
Listener Log File /apps/sam/prod1db/9.2.0/network/admin/prod1.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROCPROD1)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=apps.ces.com)(PORT=1522)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "PROD1" has 1 instance(s).
Instance "PROD1", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
id
uid=501(oraprod) gid=501(dba) groups=501(dba) context=user_u:system_r:unconfined _t
please idea for this solution.
bye
Nikki

Similar Messages

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

Application redraw issue over Citrix and Terminal Server

Hi All,
We provide a client-server application which connects to a SQL Server database. The middle-tier is hosted on an application server (Windows Server 2008 R2) which in turn connects to the SQL Server database. The fat client can either be installed on user laptops/desktops
or published using Citix/Terminal services.
We have a long standing issue which frankly I just cannot fathom. A customer has published the client via Citrix to users and using roaming profiles. If an employee is using the application in London, the roaming profile is created on a server in London and
connects to the middle-tier in London. If an employee is using the application in Glasgow, the roaming profile is created in Edinburgh and the user connects to the middle-tier in London. The customer is also using DFS
The roaming profile consists of the 'My Documents', 'My Pictures', 'My Videos', 'My Music' and 'Windows' folder. Distributed File System (DFS) is used for roaming profile folder replication between offices. See http://technet.microsoft.com/en-gb/library/cc732863%28v=ws.10%29.aspx
The Edinburgh users are experiencing application redraw issue where the interface loads in chunks. For example, when a user scrolls up and down or left and right, the data loads immediately (from SQL Server) but the interface (GUI) loads in blocks. You can
actually see each segment of the GUI components loading. The issue also occurs if connecting via a Terminal Server where the application is also installed.
For London users, it all works fine. If an Edinburgh user comes to London, they have no issues.
The network connection is super fast between the various offices.
The application is built using C++ and Delphi and uses the GDI API to draw the objects.
Any guidance is appreciated.

Hello partner,
Thanks for contacting Microsoft. This is Sophia who is going to help with this issue. From your description, I learnt that users from Edinburgh have application redraw issue. However, London users worked fine. Please let me know if I misunderstand your purpose.
Based on the information, it seems that the issue located in the middle-tier in London. Could you try building a middle-tier in Edinburgh and then test how the issue goes?
Besides, based on my experience and research, by default the allocation of the bandwidth is 70 percent for graphics data and 30 percent for virtual channel data, meaning when bandwidth usage is under pressure, graphics data is guaranteed to get 70 percent
of the available bandwidth. And we can tweak the settings a bit for some scenarios. To change the settings, we can set registry values. Please reference the information below.
===========================================================================================================================================
Note: For these settings to take effect, the computer must be restarted.
Following is the list of registry values that affect the bandwidth allocation behavior. These are all DWORD values under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermDD:
·         FlowControlDisable: When set to 1, this value disables the new flow control algorithm, making it essentially First-In-First-Out (FIFO) for all packet requests. This provides results similar to Windows Server
2003. (The default for this value is 0).
·         FlowControlDisplayBandwidth / FlowControlChannelBandwidth: These two values together determine the bandwidth distribution between display and virtual channels. You can set these values in the range of 0–255.
For example, setting FlowControlDisplayBandwidth = 100 and FlowControlChannelBandwidth = 100 creates an equal bandwidth distribution between video and VCs. The default is 70 for FlowControlDisplayBandwidth and 30 for FlowControlChannelBandwidth, thus making
the default distribution equal to 70–30.
·         FlowControlChargePostCompression: If set to 1, this value bases the bandwidth allocation on post-compression bandwidth usage. The default for this value is 0, which means that the bandwidth distribution is applied
on pre-compressed data.
For more information about RDP Bandwidth, please reference the article below.
================================================
Bandwidth Allocation for Terminal Server connections over RDP
http://blogs.msdn.com/b/rds/archive/2007/04/09/bandwidth-allocation-for-terminal-server-connections-over-rdp.aspx
Top 10 RDP Protocol Misconceptions – Part 1
http://blogs.msdn.com/b/rds/archive/2009/03/03/top-10-rdp-protocol-misconceptions-part-1.aspx
If you have any concerns about the action plan above, feel free to let me know.
Best regards,
Sophia Sun
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Cloud Database issue:-Timeoutexpired. The Timeout perion elapsed prior to completion of the operation or the server is not responding

I am facing following issue in cloud database
Issue: Altering any stored procedure in cloud database, Application throwing time out issue.
If same stored procedure running in backend(SQL),it’s executing without delay i.e. executing in 3 sec, not sure what is happening.
This is not happening on regular basis, After altering procedure if I wait for 15 to 20 minutes(not running any queries) then it will automatically get resolved.
Please let me know if any fix is available for the above issue.

Hello,
Try to enable TCP/IP and Named Pipes using the following article. Restart SQL Server service when done.
http://technet.microsoft.com/en-us/library/ms191294.aspx
Enable and start SQL Server Browser service.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Uploading another person's spreadsheet generates You have not signed on to the required Applications Database error

Greetings,
We are using the 7.2.12.04.25 32 bit version of ADI on an IBM P750 machine running AIX 5.3. The Oracle proper application is version 11.5.10 on a 10G database. We have two users that are unable to upload each others spreadsheets but are able to upload their own. A different user is able to upload the spreadsheets created by both of the users that can't upload each others spreadsheets. The ADI settings appear to be the same and the users are selecting the same responsibility. The database properties seem to be the same inside the spreadsheets as well. An option would be to copy the contents of the other person's spreadsheet into one they created and then upload it but that process is too cumbersome to entertain. Has anyone run into and resolved this issue? The error they are seeing is "You have not signed on to the required Applications Database".
Thank you!
Scott

Do the users need to sign into the same responsibility to upload a spreadsheet the other created? They are both signed into a GL responsibility but not the same one.
Since they are two different responsibilities then I'd give it a try (ask the other user to login to the same responsibility) and see how it behaves.
Thanks,
Hussein

Applications database

Hi
I have some doubts regarding the oracle applications database.
what does the command mean ps -ef |grep applmgr
where applmgr is the applications user.
WHAT does this command mean.Why do we use this command .please explain me
One more query:-----
If the users report that the they are unable to access the database ,then as a dba what are all the things we have to check.What are the files which we have to check when normally some database issue arises.please say me the files which should be normally checked in oracle applications as well as in the database
Regards
Aram

Hi,
what does the command mean ps -ef |grep applmgr
WHAT does this command mean.Why do we use this command .please explain meIt means, list all the active processes at the OS level and filter the output by showing the entries which contain applmgr user (search Google for "man ps").
If the users report that the they are unable to access the database ,then as a dba what are all the things we have to check.What are the files which we have to check when normally some database issue arises.please say me the files which should be normally checked in oracle applications as well as in the database Check the error and search My Oracle Support. Also, review the database log file (alert_<SID>.log) and see if it contains any errors.
Regards,
Hussein

Regarding Sun Java System Application Server Issue with JVM

Regarding Sun Java System Application Server Issue with JVM
Hi
I have installed SJSAS9.1 on solaris system. I m trying to deploy war file which i compiled in windows enviorment by jdk1.5.0_05. Every time i got the following error :
type Exception report
message
descriptionThe server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: PWC6033: Unable to compile class for JSP
PWC6199: Generated servlet error:
[javac] javac: invalid target release: 1.5
[javac] Usage: javac
[javac] where possible options include:
[javac] -g Generate all debugging info
[javac] -g:none Generate no debugging info
[javac] -g:{lines,vars,source} Generate only some debugging info
[javac] -nowarn Generate no warnings
[javac] -verbose Output messages about what the compiler is doing
[javac] -deprecation Output source locations where deprecated APIs are used
[javac] -classpath Specify where to find user class files
[javac] -sourcepath Specify where to find input source files
[javac] -bootclasspath Override location of bootstrap class files
[javac] -extdirs Override location of installed extensions
[javac] -d Specify where to place generated class files
[javac] -encoding Specify character encoding used by source files
[javac] -source Provide source compatibility with specified release
[javac] -target Generate class files for specific VM version
[javac] -help Print a synopsis of standard options
note The full stack traces of the exception and its root causes are available in the Sun Java System Application Server 9.1 logs.
I have cheked jvm version on both system the only difference is :
Solaris points to jdk 1.5.0_09
Windows point to jdk1.5.0_05
Even i tried to run blank jsp also but again i got the same error.
Can any help me to sort out the problem or give me any idea so i can do something by my own.
Thanks in Advance
Gagan

Do you have ANT installed and available?
Thanks,
Kedar

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

Application Deloyment issue...

hi,
i am getting this Deployment error...
we got two servers one for developers at offshore and
one at the onsite...
the strange thing is that it is deploying n running fine on the offshore server.
but not getting deployed on the onsite server!!!
i have put the required references required and
checked them too...!!!
regards,
-Amol Gupta
Oct 18, 2007 11:11:04 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[004]Deployment aborted
Settings
SDM host : bp1xeuaa558
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/amolg/LOCALS1/Temp/temp26291bp.comexmplsupplier_lds_create_adobe.ear
Result
=> deployment aborted : file:/C:/DOCUME1/amolg/LOCALS1/Temp/temp26291bp.comexmplsupplier_lds_create_adobe.ear
Aborted: development component 'exmpl/supplier_lds_create_adobe'/'bp.com'/'LOKAL'/'0.2007.10.18.11.10.17'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application bp.com/exmplsupplier_lds_create_adobe.. Reason: Clusterwide exception: Failed to deploy application bp.com/exmplsupplier_lds_create_adobe. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application bp.com/exmpl~supplier_lds_create_adobe. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted

>
I have oracle PL/SQL application performance issue. To open a screen populated with 7,000 records takes 5 minutes.
I have used SQL Analyze to get Index recomendation. Indexing did not help that much.Switch on a trace on a user who is just about to run that screen - let them rip.
Stop your trace. Get your trace file. Run it through TKProf.
Read the book by Cary Millsap that Sybrand recommends (or take a look
at Chris Lawson) - i.e. read up on trace files and looking at them.
Get the SQL that is run by the user and try running it from SQLPlus
on the server (no network or app issues) - set timing on.
That would be my approach.
Do you think upgrading or replacing with newer machine can improve performance? Getting a newer machine often satisfies the geek's primeval urge to
get his grubby little paws onto fancy shiny hardware - it may well
work for a while, however you're not tackling the underlying cause
of your problem, and it will (probably) reappear when the limits
of the new RAM/CPU have been hit.
If you what is suggested above, at least you'll be able to say
to your management - "well, if we get a new server, performance
will improve by this much, until we have (say) 14.000 records in
the table, when performance will go back to the way it was before".
Until you run a trace, you will have no idea if the problem will
scale linearly with the no. of records or how it will
behave into the future.
You cannon manage what you cannot measure.
Paul...
Taf

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

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

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 you change data on a SQL 2012 application database that uses availability groups from BizTalk server?

If you use the WCF-SQL adapter it is recommend that you set UseAmbientTransaction to true if you are changing data. I think this requires MSDTC to be enabled on the SQL server that you are changing the data on. (http://msdn.microsoft.com/en-us/library/dd787981.aspx)
I think that Availability groups does not support MSDTC. (http://msdn.microsoft.com/en-us/library/ms366279.aspx).
How can you change data on a SQL 2012 application database that uses availability groups from BizTalk server?

Hi,
Yes, Availability groups doesn't support MSDTC. Please refer to the similar discusison which maybe helpfull:
http://dba.stackexchange.com/questions/47108/alwayson-ag-dtc-with-failover
http://stackoverflow.com/questions/17179221/msdtc-in-always-on-availability-groups

Applications database issue

Similar Messages

Maybe you are looking for