Concurrency in Database
Hi, i have a Web App and i have a problem when i insert values into a table. Let's say that I have two tables A and B, in order to insert a value in A i have to read, first, a value from table B, this value in table B is just like a sequence, i mean is a number that is increased everytime i register a row in table A. This works well when there is just one client registering values in A, but the problem is when i have two clients trying to register in table A at the same time, both are reading the same value in B so when they are trying to register in A an exception of "a repeated primary key" appears and just one of the clients can register in A meanwhile the other gets an exception.
This problem is about concurrency and right now i'm using the autocommit option on, how can i deal with this kind of problem?, keeping in mind that is more likely to have in my web application more than 2 people trying to register a row in table A.
You have a couple of choices. As has already been suggested you can synchronize the methods in your Java code where the updates / inserts begin. Or you can effectively synchronize the db by having the record in table B lock when it is being read or updated.
Which is the correct method is entirely a matter of personal taste and platform. Some databases are better at managing record locks than others. I would generally lean towards putting the lock in the database because it is entirely possible that some other mechanism than my application may be updating the database as well and that would allow me to protect the reads and writes to the db regardless of where they originate.
All of that said, be aware that there is a performance price to be paid regardless of how you choose to do it. You're blocking one attempt while another finishes. That's going to translate directly into one user waiting for an indeterminant amount of time before they can finish their commit. They may never notice it, but be aware that it is there.
Hope this helps,
PS.
Similar Messages
-
Kernel parameter for large concurrent connections database.
Hi,
Does any one have suggestion about kernel parameters we have to modify for large concurrent connections database (about 20000 concurrent connections) ? We would like to use Sun M8000 as our database server. Oracle installation guide indicated many parameters and values, but it seems ok for general database, not the one we need. Please somebody help us. Thanks !I certainly don't have any idea where the 150G memory usage for 20000 concurrent users come about. That's 7.5MB per user session.
The session memory usage is depends on Oracle version, OS , Database configuration and application behavior etc..
From following query we can tell, average session memory usage is around 1.5M in normal usage on 10g linux platform.
It could go up to 20-30M if user session doing large data manipulation.
SYS@test > l
1 select value, n.name|| '('||s.statistic#||')' , sid
2 from v$sesstat s , v$statname n
3 where s.statistic# = n.statistic#
4 and n.name like '%ga memory%'
5* order by sid
SYS@azerity > /
VALUE N.NAME||'('||S.STATISTIC#||')' SID
486792 session pga memory max(26) 66
486792 session pga memory(25) 66
225184 session uga memory(20) 66
225184 session uga memory max(21) 66
225184 session uga memory max(21) 70
486792 session pga memory max(26) 70
486792 session pga memory(25) 70
225184 session uga memory(20) 70
225184 session uga memory(20) 72
486792 session pga memory max(26) 72
225184 session uga memory max(21) 72
486792 session pga memory(25) 72
486792 session pga memory max(26) 74
225184 session uga memory(20) 74
486792 session pga memory(25) 74
225184 session uga memory max(21) 74
......Aggregate by SID
1 select sum(value),sid
2 from v$sesstat s , v$statname n
3 where s.statistic# = n.statistic#
4 and n.name like '%ga memory%'
5 group by sid
6* order by sid
SYS@test > /
SUM(VALUE) SID
1423952 66
1423952 70
1423952 72
1423952 74
1423952 75
1423952 77
1423952 87
1423952 101
2733648 104
1423952 207
23723248 209
23723248 210
1293136 215
7370320 216
......... -
How can I use SQL TOOLKIT concurrently with Database Connectivity ?
I have installed LabVIEW 6.1 with the Database Connectivity Toolkit and the SQL Compatibility Toolkit (e.g. _SQL folder). I am trying to make the transition from the SQL Toolkit VIs to the Database Connectivity toolkits, but for compatability with existing systems I would like to be able to run the two sets of VIs concurrently (but not in the same app).
When I read into 6.1 a connection VI that I wrote with LabVIEW 6.0 and the SQL toolkit the connection reference type gets changed from a number to type connection (see attachments) . Does compatbility mean that my SQL toolkit VIs are converted to a form compatible with the new ADO ?
Can I use the SQL Toolkit VIs or the Database connectivit
y VIs in the same installation of 6.1 ?
Can I have the SQL Toolkit VIs appear on the functions pallette and function as they did when only the SQL toolkit was installed ?
Attachments:
CNNCT.vi 20 KB
CNNCT.vi 22 KBIn response to your #2 below:
Actually it is possible to have the old SQL Toolkit and new Database
connectivity in the same installation of LabVIEW. I have only tried it on
6i, but don't see why it wouldn't work on 6.1. The trick is not to install
the SQL toolkit compatabitily VI's. The old SQL toolkit uses the Intersolve
dll through ODBC while the new Database connectivity uses ADO so it is
possible to use both methods not only in the same LabVIEW install, but it
the same running application. It has been a while since I originally did
this, so I am posting only to mention that it is possible and not exactly
how to do it. If anyone is interested in more details just respond.
Brian
"Jeff B" wrote in message
news:[email protected]...
> First, direct answers to your direct questions:
>
> 1. Does compatbility mean that my SQL toolkit VIs are converted to a
> form compatible with the new ADO ?
>
> Yes
>
> 2. Can I use the SQL Toolkit VIs or the Database connectivity VIs in
> the same installation of 6.1 ?
>
> No
>
> 3. Can I have the SQL Toolkit VIs appear on the functions pallette
> and function as they did when only the SQL toolkit was installed ?
>
> No
>
>
> Now an elaboration:
>
> Having the old SQL Toolkit and the new Database Connectivity Toolset
> installed on the same version of LabVIEW on the same computer is not
> supported.
>
> Once you install the Database Connectivity Toolset, any VIs written
> with the SQL Toolkit will run, but with the ADO layer, as you
> suspected.
>
> Internally, the only way we can have both the SQL Toolkit and the
> Database Connectivity Toolset installed on the same computer for
> troubleshooting customer issues is to have them installed on different
> versions of LabVIEW. I, for example, have LabVIEW 5.1.2, 6.0.3, and
> 6.1 all installed on my computer, and I have the SQL Toolkit install
> on LabVIEW 5.1.2, and the Database Connectivity Toolset installed on
> LabVIEW 6.0.3. In this configuration I can still run SQL Toolkit VIs
> independent of the Database Connectivity Toolset if I open and run
> them in LabVIEW 5.1.2. -
Concurrency in Database operations with JDBC
Sorry for the somewhat ignorant question
Here it is Are interactions with a database by multiple
entities on the same db tables managed by the database
or are they supposed to be managed by the application?
In specific, additions, commits, and any other write operations...To be managed by the application.
-
How to configure Oracle 10g Advanced Security to use SSL concurrently with
How to configure Oracle 10g Advanced Security to use SSL concurrently with database User names and passwords
In Oracle Advanced Security Documentation it is mentioned that i can use SSL concurrently with DB user names and passwords. But when i configure the client certificate on the client my DB connection is getting authenticated using the certificate, which out passing user id or password.
We want to connect to Oracle DB over SSL channel so that the data packets are not in clear text. Also we want the user to make a connection using user id and password.
Basically we want SSL with out authentication.
Need your expert adviceRead the documentation (I have given following links assuming you are running a 32 bit architecture)
Server installations:
http://www.oracle.com/pls/db102/to_toc?pathname=install.102%2Fb14316%2Ftoc.htm&remark=portal+%28Books%29
Client installations:
http://www.oracle.com/pls/db102/to_toc?pathname=install.102%2Fb14312%2Ftoc.htm&remark=portal+%28Books%29
You can find the required books (if not using 32 bit architecture) from
http://www.oracle.com/pls/db102/portal.portal_db?selected=3 -
JE 5.0.55 and 4.1.21 available, critical fix for Database renaming
All,
I'd like to point out the critical bug fix that has to do with database renaming. This is fixed in JE 5.0.55 and JE 4.1.21. See below.
--mark
Berkeley DB Java Edition 5.0.55
http://www.oracle.com/us/products/database/berkeley-db/index.html (BDB product page)
http://www.oracle.com/technetwork/database/berkeleydb/overview/index.html (BDB overview)
http://www.oracle.com/technetwork/database/berkeleydb/overview/index-093405.html (BDB JE overview)
Berkeley DB Java Edition 5.0.55 is a patch release consisting of fixes for a number of issues. We strongly recommend that users of the 5.0.x version upgrade to this release. These fixes include:
[#21537] Fixed a critical bug that causes a database to be entirely deleted after a crash (or abnormal shutdown, i.e., when not calling Environment.close). The bug occurs when the database is renamed just prior to the crash (or abnormal shutdown). This bug was introduced in JE 5.0.48.
[#21492] Fixed an inefficiency in the Checkpointer which manifests itself as a large amount of time being spent in com.sleepycat.je.recovery.DirtyINMap.removeNextNode() calling java.util.HashMap$HashIterator.remove() calling java.util.HashMap.removeEntryForKey().
[#21106] An enhancement has been made to DbVerify to show a histogram of BIN counts by utilization percentage.This is a sample of the output:
Verifying database p10
Checking tree for p10
BTree: Composition of btree, types and counts of nodes.
binCount=3,207
binEntriesHistogram=[40-49%: 3,093; 50-59%: 10; 60-69%: 22; 70-79%: 26;
80-89%: 21; 90-99%: 35]
binsByLevel=[level 1: count=3,207]
deletedLNCount=0
inCount=49
insByLevel=[level 2: count=48; level 3: count=1]
lnCount=209,716
mainTreeMaxDepth=3Find the complete list of changes in the change log.
http://download.oracle.com/otndocs/products/berkeleydb/html/je/je-5.0.55_changelog.html
Read the detailed product documentation included in the download package or on the web.
http://www.oracle.com/technetwork/database/berkeleydb/downloads/index-098622.html
http://download.oracle.com/docs/cd/E17277_02/html/index.html
Download the source code.
http://download.oracle.com/otn/berkeley-db/je-5.0.55.tar.gz
http://download.oracle.com/otn/berkeley-db/je-5.0.55.zip
http://download.oracle.com/maven/com/sleepycat/je/5.0.55/je-5.0.55.pom
Review the frequently asked questions (FAQs):
http://www.oracle.com/technetwork/database/berkeleydb/je-faq-096044.html
Join OTN and participate in the Berkeley DB JE Support Forum discussions. Our engineering and support staff are highly active on these forums, if you have questions please ask them there first.
Berkeley DB Java Edition
For further information, or questions about licensing and sales of JE, please contact us at:
mailto:[email protected]
Thank you for your support of Berkeley DB Java Edition.The format change is for BDB Java Edition 5.0 only, and does not apply to other BDB products. It's forward compatible, which means that a BDB JE application using JE 5.0 can use environments written with older versions of JE. However, it's not backwards compatible; once your environment has been opened by JE 5.0, it's been converted to the new format, and can no longer be readable by older versions of JE.
Just for the benefit of others who may not have read the changelog, here's the full text:
JE 5.0.34 has moved to on-disk file format 8.
The change is forward compatible in that JE files created with release 4.1 and earlier can be read when opened with JE 5.0.34. The change is not backward compatible in that files created with JE 5.0 cannot be read by earlier releases. Note that if an existing environment is opened read/write, a new log file is written by JE 5.0 and the environment can no longer be read by earlier releases.
There are two important notes about the file format change.
The file format change enabled significant improvements in the operation performance, memory and disk footprint, and concurrency of databases with duplicate keys. Environments which contain databases with duplicate keys must run an upgrade utility before opening an environment with this release. See the Performance section for more information.
An application which uses JE replication may not upgrade directly from JE 4.0 to JE 5.0. Instead, the upgrade must be done from JE 4.0 to JE 4.1 and then to JE 5.0. Applications already at JE 4.1 are not affected. Upgrade guidance can be found in the new chapter, "Upgrading a JE Replication Group", in the "Getting Started with BDB JE High Availability" guide.I may not have fully understood your question, so let us know if that doesn't answer it.
Edited by: Linda Lee on Dec 1, 2011 10:41 AM -
Are Concurrent Jobs Resumable?
I'm running 11.5.10 on Solaris SPARC.
What happens if I lose concurrent manager, let's say, due to hardware failure, and I have a second concurrent manager on another node? Will the second manager resume the jobs running on the one that crashed? If so, does it roll them back, or can it resume them from the point of failure?
Thanks,
Ted PerskyHi Ted,
Good question. Here's my (theoretical) reply:
Short answer in most cases is no as once a job is running control is passed to the job itself. Rerunnable? Thats a different story.
Some musings:
First you have to consider what type of job it is. Chances are everything will rely on the database process and if your concurrent manager node fails then the database node might continue and complete the job successfully. If the database node fails then you're without your paddle (or at least your second node and everything else won't be running either) so all bets are off. Chances are in hardware failure you'll be wanting to look at the pending/running requests pretty closely anyway.
My understanding is that once a concurrent request starts running the job is marked (committed) as running. If the hardware then fails then the job will still be marked as running even though there are no processes, in which case a cmclean.sql or datafix may be required - the jobs are more than likely not restarted. But I haven't tested this with multi concurrent nodes. Now on my list of things to try!
Jobs that haven't started running (pending) should be fine, but I haven't tested hardware failure to this level of detail lately!
Note one real gotcha in the past is when someone cancels (terminates) a concurrent request. Apps doesn't seem to call the "alter system kill session" on the concurrent request database process, and so that still runs in the background. Something like FA Depreciation is a good example here, I've seen that cancelled with grief a few times coz it continued processing in the background after the request showed Completed Cancelled!
Keen to hear how you get on testing any responses to this question!
Regards,
Gareth
Blog: http://garethroberts.blogspot.com/ -
All,
We are on 12.0.2 / 10.2.0.2 (non-rac) in a split-tier architecture. Web/Forms on the Linux node and Concurrent Managers/Database on the Solaris node. We are now on a project to upgrade this environment to 12.1.1 on 11.1.0.7 db. (Non RAC,Non ASM)
Here are the high level tasks that i laid down
-- Create a project instance (clone from Prod)
-- Upgrade db to 10.2.0.4 from 10.2.0.2
-- Upgrade the techstack Oracle Homes (10.1.2 and 10.1.3)
-- Upgrade the JDK to 1.6.0_X
-- Upgrade 12.0.2 to R12.1.1
-- Upgrade the database to 11.1.0.7
PS: Direct ugprade from 10.2.0.2 to 11.1.0.7 needs us to be on R12 RUP4. So, i decided to do 10g upgrade as an intermediate step. We are following 752619.1 and all the notes that it refers.
We are hitting an issue upgrading the 10.1.3 Oracle home on the Solaris node. The same upgrade completed fine on the Linux node. Here is the description of the issue.
The runInstaller for 10.1.3.4 patchset expects OPMN to be running for a successful patchset installation. On a node with just batch processing enabled, OPMN does not run by default. The installer tries to start OPMN and errors out saying
========
OPMN is failing to start. OPMN must be started in order to correctly install and configure the patchset. Please start OPMN ma
nually in order to continue with the patchset installation.
=========
This is when the installer is at 83%
We tried to start OPMN and managed processes manually using adopmnctl.sh
OPMN starts and is able to start the HTTP server too but not any of the OC4J container components (oacore,forms and oafm). Here are the errors
==========
ias-instance id=afcprj_swafcdev1.swafcdev1.sherwin.com
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ias-component/process-type/process-set:
default_group/oacore/default_group/
Error
--> Process (index=1,uid=1861636864,pid=17677)
failed to start a managed process after the maximum retry limit
Log:
/swafc/applmgr/afcprj/inst/apps/afcprj_swafcdev1/logs/ora/10.1.3/opmn/default_gr
oup~oacore~default_group~1
ias-component/process-type/process-set:
default_group/forms/default_group/
=========
The logfile that it points to does not have any errors. Looking into the other log files within $LOG_HOME/ora/*3/
, we get the following error in oacorestd.err
=========
09/10/05 16:07:10 Error initializing server: Shared library "oracle.ws.jaxrpc" could not be found.
09/10/05 16:07:15 Error: <connector name="OracleASjms" path="OracleASjms.rar" /> will not be bootstrapped since corresponding module declaration was not found in application.xml.
09/10/05 16:07:17 Error initializing server: Shared library "oracle.ws.jaxrpc" could not be found.
========
I saw some notes and tried updating the config xml files and removed the references to oracle.ws.jaxrpc but to no help.
Installer log has the below error when we attempt the "retry" operation in installation screens.
========
fileName = NonExistentFile
searchString = NonExistentString
Query Exception: FileNotFoundException
Query Exception Class: class oracle.sysman.oii.oiil.OiilQueryException
Query Exception: FileNotFoundException
Query Exception Class: class oracle.sysman.oii.oiil.OiilQueryException
===========
Any help on the above issue? We are never going to use OPMN on this node but stuck here currently !!
Deviating a little bit, if we have to consider moving the concurrent managers out of database node to the
web/forms node (just to avoid having to maintain 2 appl_tops and getting away with doing the above tasks 2 times)
, what are the various things to consider?
-- Network latency
-- R12 being Unified APPL_TOP, can we just try to bring up ICM on Web/Forms node? (just enable the service)
-- We are aware that we might have to move the custom top and test custom programs (especially host programs).
Is there any other considerations when moving Concurrent managers from a Solaris node(64 bit) to Linux node (32 bit) ?
One last question: Why are these adoacore/adoafm scripts taking a long time?
Any feedback is highly appreciated.
Thanks,
ArunHi,
Error
--> Process (index=1,uid=1861636864,pid=17677)
failed to start a managed process after the maximum retry limit
Log:
/swafc/applmgr/afcprj/inst/apps/afcprj_swafcdev1/logs/ora/10.1.3/opmn/default_gr
oup~oacore~default_group~1
ias-component/process-type/process-set:
default_group/forms/default_group/Please try the suggested solution in Note: 555214.1 and see if it helps.
Query Exception: FileNotFoundException
Query Exception Class: class oracle.sysman.oii.oiil.OiilQueryExceptionCould you please verify that permissions are set correctly on the application tier node files?
-- R12 being Unified APPL_TOP, can we just try to bring up ICM on Web/Forms node? (just enable the service)Please see (Note: 373611.1 - How to move Concurrent Processing Server from one node to another node) -- Step 3 to 7
-- We are aware that we might have to move the custom top and test custom programs (especially host programs).
Is there any other considerations when moving Concurrent managers from a Solaris node(64 bit) to Linux node (32 bit) ?I would suggest you relink all executable files via adadmin and check then.
Regards,
Hussein -
New major release, JE 5.0, is available
Hi all,
We're pleased to announce a new major release, JE 5.0.34. The release contains a significant number of new features and performance enhancements. Complete information can be found in the JE documentation, specifically in the change log. The release is available via the download site or Maven.
Below is a copy of the major enhancements listed in the release notes. See the change log for a complete list.
<li> The new DiskOrderedCursor class can be used to iterate over all records in a database, for increased performance when transactional guarantees are not required. [#15260]
<li> A new Environment.preload method can be used to preload multiple databases at a time, for increased performance compared to preloading each database individually. [#18153]
<li> The JE environment can now be spread across multiple subdirectories to take advantage of multiple disks or file systems. [#19125]
<li> The new AppStateMonitor class lets the HA application add more application specific information to the notion of node state in a replication group. [#18046]
<li> New options have been added for changing the host of a JE replication node, and for moving a JE replication group. See the Utilities section of the change log.
<li> Replicated nodes can now be opened in UNKNOWN state, to support read only operations in a replicated system when a master is not available. [#19338]
<li> New Cursor methods were added to allow quickly skipping over a specified number of key/value pairs. [#19165]
<li> A per-Environment ClassLoader may now be configured and will be used by JE for loading all user-supplied classes. [#18368]
<li> The java.io.Closeable interface is now implemented by all JE classes and interfaces with a public void close() method. This allows using these objects with the Java 1.7 try-with-resources statement. [#20559]
<li> The Environment.flushLog method has been added. It can be used to make durable, by writing to the log, all preceding non-transactional write operations, without performing a checkpoint. [#19111]
<li> Performance of record update and deletion operations has been significantly improved when the record is not in the JE cache and the application does not need to read the record prior to performing the update or deletion. [#18633]
<li> An internal format change was made for databases with duplicate keys that improves operation performance, reduces memory and disk overhead, and increases concurrency. [#19165]
<li> An improvement has been made that requires significantly less writing per checkpoint, less writing during eviction, and less metadata overhead in the JE on-disk log files. [#19671]
<li> Improved DbCacheSize utility to take into account memory management enhancements and improve accuracy. Added support for key prefixing, databases configured for sorted duplicates, and replicated environments. [#20145]
<li> EnvironmentConfig.TREE_COMPACT_MAX_KEY_LENGTH was added for user configuration of the in-memory compaction of keys in the Btree. [#20120]
-- The JE TeamThe format change is for BDB Java Edition 5.0 only, and does not apply to other BDB products. It's forward compatible, which means that a BDB JE application using JE 5.0 can use environments written with older versions of JE. However, it's not backwards compatible; once your environment has been opened by JE 5.0, it's been converted to the new format, and can no longer be readable by older versions of JE.
Just for the benefit of others who may not have read the changelog, here's the full text:
JE 5.0.34 has moved to on-disk file format 8.
The change is forward compatible in that JE files created with release 4.1 and earlier can be read when opened with JE 5.0.34. The change is not backward compatible in that files created with JE 5.0 cannot be read by earlier releases. Note that if an existing environment is opened read/write, a new log file is written by JE 5.0 and the environment can no longer be read by earlier releases.
There are two important notes about the file format change.
The file format change enabled significant improvements in the operation performance, memory and disk footprint, and concurrency of databases with duplicate keys. Environments which contain databases with duplicate keys must run an upgrade utility before opening an environment with this release. See the Performance section for more information.
An application which uses JE replication may not upgrade directly from JE 4.0 to JE 5.0. Instead, the upgrade must be done from JE 4.0 to JE 4.1 and then to JE 5.0. Applications already at JE 4.1 are not affected. Upgrade guidance can be found in the new chapter, "Upgrading a JE Replication Group", in the "Getting Started with BDB JE High Availability" guide.I may not have fully understood your question, so let us know if that doesn't answer it.
Edited by: Linda Lee on Dec 1, 2011 10:41 AM -
STMS error in ECC 6.0 - DB2 /AIX
Hello Dirk,
This is log file of R3trans -d :
gipapp:prdadm 6> R3trans -d
This is R3trans version 6.14 (release 700 - 20.07.06 - 17:34:00).
unicode enabled version
2EETW169 no connect possible: "DBMS = DB6 --- DB2DB
DFT = 'PRD'"
R3trans finished (0012).
gipapp:prdadm 7> cat trans.log
4 ETW000 R3trans version 6.14 (release 700 - 20.07.06 - 17:34:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 14.02.2007 - 07:35:24
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: R3trans -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc ,00000] Wed Feb 14 07:35:24 2007
55 0.000055
4 ETW000 [dev trc ,00000] db_con_init called
20 0.000075
4 ETW000 [dev trc ,00000] create_con (con_name=R/3)
35 0.000110
4 ETW000 [dev trc ,00000] Loading DB library '/usr/sap/PRD/SYS/exe/run/dbd
b6slib.o' ...
4 ETW000
48 0.000158
4 ETW000 [dev trc ,00000] load shared library (/usr/sap/PRD/SYS/exe/run/db
db6slib.o), hdl 0
4 ETW000
529 0.000687
4 ETW000 [dev trc ,00000] Library '/usr/sap/PRD/SYS/exe/run/dbdb6slib.o' l
oaded
4 ETW000
29 0.000716
4 ETW000 [dev trc ,00000] function DbSlExpFuns loaded from library /usr/sa
p/PRD/SYS/exe/run/dbdb6slib.o
4 ETW000
31 0.000747
4 ETW000 [dev trc ,00000] Version of '/usr/sap/PRD/SYS/exe/run/dbdb6slib.o
' is "700.08", patchlevel (0.52)
4 ETW000
141 0.000888
4 ETW000 [dev trc ,00000] function dsql_db_init loaded from library /usr/s
ap/PRD/SYS/exe/run/dbdb6slib.o
4 ETW000
31 0.000919
4 ETW000 [dev trc ,00000] function dbdd_exp_funs loaded from library /usr/
sap/PRD/SYS/exe/run/dbdb6slib.o
4 ETW000
30 0.000949
4 ETW000 [dev trc ,00000] New connection 0 created
24 0.000973
4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = -000000001 state = DISCO
NNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, oc
c = NO
4 ETW000
35 0.001008
4 ETW000 [dev trc ,00000] db_con_connect (con_name=R/3)
33 0.001041
4 ETW000 [dev trc ,00000] find_con_by_name found the following connection
for reuse:
4 ETW000
29 0.001070
4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = 000000000 state = DISCON
NECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ
= NO
4 ETW000
33 0.001103
4 ETW000 [dev trc ,00000] DB6 (DB2 UDB) UNICODE database interface 700.08
[opt]
4 ETW000
311 0.001414
4 ETW000 [dev trc ,00000] DB6 shared library (dbdb6slib) patchlevels
19 0.001433
4 ETW000 [dev trc ,00000] (0.8) DB6: V8.2.2 optguidelines in OPEN SQL (n
ote 150037)
4 ETW000
30 0.001463
4 ETW000 [dev trc ,00000] (0.8) Support of SDBUPDEXCL (note 847616)
20 0.001483
4 ETW000 [dev trc ,00000] (0.9) DB6: use export file for dbdb6slib (note
835135)
4 ETW000
29 0.001512
4 ETW000 [dev trc ,00000] (0.9) DB6: Core in getAndBindSQLDA (note 83318
3)
4 ETW000
29 0.001541
4 ETW000 [dev trc ,00000] (0.10) DB6: link dbdb6slib.dll on windows with
libdb6.obj (note 761159)
4 ETW000
30 0.001571
4 ETW000 [dev trc ,00000] (0.10) DB6: DUPLICATE_KEY on MERGE -> repeat (
note 851474)
4 ETW000
37 0.001608
4 ETW000 [dev trc ,00000] (0.15) DB6: wrong CAST for short string ABAP t
ype (note 861905)
4 ETW000
30 0.001638
4 ETW000 [dev trc ,00000] (0.17) DB6: special characters in sidadm passw
d (note 865839)
4 ETW000
29 0.001667
4 ETW000 [dev trc ,00000] (0.21) DB6: no SAP_INFO comments (note 873889)
4 ETW000
29 0.001696
4 ETW000 [dev trc ,00000] (0.22) DB6: hints: get correlation names from
view texts (note 868888)
4 ETW000
30 0.001726
4 ETW000 [dev trc ,00000] (0.23) DB6: hints: get correlation names from
view texts (note 868888)
4 ETW000
29 0.001755
4 ETW000 [dev trc ,00000] (0.26) DB6: DB6_DBSL_CLP_COMMAND STRING_BAD_RE
F (note 883402)
4 ETW000
29 0.001784
4 ETW000 [dev trc ,00000] (0.27) DB6: activate value compression (note 8
86231)
4 ETW000
30 0.001814
4 ETW000 [dev trc ,00000] (0.28) DB6: optimization guidelines on views p
art 2 (note 868888)
4 ETW000
29 0.001843
4 ETW000 [dev trc ,00000] (0.30) DB6: no SQL trace for SQLCancel (note 8
92111)
4 ETW000
29 0.001872
4 ETW000 [dev trc ,00000] (0.33) DB6: append SAP_TA comment (note 873889
4 ETW000
29 0.001901
4 ETW000 [dev trc ,00000] (0.34) DB6: activate value compression with qu
oted names (note 886231)
4 ETW000
30 0.001931
4 ETW000 [dev trc ,00000] (0.36) DB6: Repeat isolated DDL statements aft
er SQL0911 (note 901338)
4 ETW000
29 0.001960
4 ETW000 [dev trc ,00000] (0.41) DB6: add V9 to list of supported DB2 re
leases (note 912386)
4 ETW000
30 0.001990
4 ETW000 [dev trc ,00000] (0.50) DB6: reread passwords for secondary con
nections (note 931742)
4 ETW000
29 0.002019
4 ETW000 [dev trc ,00000] (0.52) DB6: double quote table names in optgui
delines (note 868888)
4 ETW000
30 0.002049
4 ETW000 [dev trc ,00000] Supported features:
18 0.002067
4 ETW000 [dev trc ,00000] - CLI LOAD for INSERT ... FULLSELECT
19 0.002086
4 ETW000 [dev trc ,00000] ..retrieving configuration parameters
18 0.002104
4 ETW000 [dev trc ,00000] ..done
91 0.002195
4 ETW000 [dev trc ,00000] Running with UTF-8 Unicode
18 0.002213
4 ETW000 [dev trc ,00000] DB2 library /db2/db2prd/sqllib/lib64/libdb2.a(sh
r_64.o) successfully loaded
4 ETW000
9497 0.011710
4 ETW000 [dev trc ,00000] Wed Feb 14 07:35:26 2007
1490336 1.502046
4 ETW000 [dev trc ,00000] *** ERROR in DB6Connect[dbdb6.c, 1379] (BEGIN)
27 1.502073
4 ETW000 [dev trc ,00000] &+ DbSlConnectDB6( SQLConnect ): [IBM][CLI D
river] SQL1040N The maximum number of applications is already connected
4 ETW000
43 1.502116
4 ETW000 [dev trc ,00000] &+ to the database. SQLSTATE=57030
4 ETW000
32 1.502148
4 ETW000 [dev trc ,00000] &+
4 ETW000
32 1.502180
4 ETW000 [dev trc ,00000] &+
4 ETW000
32 1.502212
4 ETW000 [dev trc ,00000] &+
4 ETW000
31 1.502243
4 ETW000 [dev trc ,00000] *** ERROR in DB6Connect[dbdb6.c, 1379] (END)
20 1.502263
4 ETW000 [dbdb6.c ,00000] *** ERROR => DbSlConnect to 'PRD' as 'sapprd' fa
iled
4 ETW000
54 1.502317
2EETW169 no connect possible: "DBMS = DB6 --- DB2DB
DFT = 'PRD'"
gipapp:prdadm 8>
gipapp:prdadm 8> disp+work -V|more
disp+work information
kernel release 700
kernel make variant 700_REL
DBMS client library DB6_81
DBSL shared library version 700.08
compiled on AIX 2 5 005DD9CD4C00
compiled for 64 BIT
compilation mode UNICODE
compile time Apr 2 2006 20:44:50
update level 0
patch number 52
Standard input
Please help me ASAP
Dabinder Singh
Posts: 19
Questions: 2
Registered: 12/14/06
Forum points: 0
Re: ECC 6.0 installation error - DB2/ AIX
Posted: Feb 14, 2007 2:47 PM in response to: dirk pohl Reply E-mail this post
I am getting this error while executing this db2 connect to prd user db2prd
gipdb:prdadm 1> db2 connect to prd
SQL30082N Attempt to establish connection failed with security reason "3"
("PASSWORD MISSING"). SQLSTATE=08001
gipdb:prdadm 2> db2 connect to prd user db2prd
Enter current password for db2prd:
SQL1040N The maximum number of applications is already connected to the
database. SQLSTATE=57030
Regards,
Gautam.Hello,
Now DB and CI is running in Node A and Dialog Instance is running in Node B. There is no list" db2 list applications " in Node B .
In Node A : db2 list applications :
gipdb:prdadm 2> db2 list applications
Auth Id Application Appl. Application Id DB # of
Name Handle Name Agent
SAPPRD disp+work 40 C0A8D52B.O042.0A0574152020 PRD 1
SAPPRD disp+work 39 C0A8D52B.O041.020CF4152020 PRD 1
SAPPRD disp+work 38 C0A8D52B.O040.0C0E94152020 PRD 1
SAPPRD disp+work 37 C0A8D52B.O03F.000574152019 PRD 1
SAPPRD disp+work 36 C0A8D52B.O03E.020314152019 PRD 1
SAPPRD disp+work 35 C0A8D52B.O03D.0301B4152019 PRD 1
SAPPRD disp+work 34 C0A8D52B.O03C.040234152019 PRD 1
SAPPRD disp+work 33 C0A8D52B.O03B.090D34152018 PRD 1
SAPPRD disp+work 32 C0A8D52B.O03A.070974152018 PRD 1
SAPPRD disp+work 31 C0A8D52B.O039.0F0D14152018 PRD 1
SAPPRD disp+work 30 C0A8D52B.O038.050DB4152018 PRD 1
SAPPRD disp+work 29 C0A8D52B.O037.0B02D4152018 PRD 1
SAPPRD disp+work 28 C0A8D52B.O036.050794152018 PRD 1
SAPPRD disp+work 27 C0A8D52B.O035.040C14152018 PRD 1
SAPPRD disp+work 26 C0A8D52B.O034.0D0D94152014 PRD 1
SAPPRD disp+work 25 C0A8D52B.O032.070034152012 PRD 1
SAPPRD disp+work 24 C0A8D52B.O030.0E0AD4152011 PRD 1
SAPPRD disp+work 23 C0A8D52B.O02F.0B0614152009 PRD 1
SAPPRD disp+work 22 C0A8D52B.O02E.0A0C54152007 PRD 1
SAPPRD disp+work 21 C0A8D52B.O02D.080534152007 PRD 1
SAPPRD disp+work 16 C0A8D52B.O028.0407F4152007 PRD 1
SAPPRD disp+work 20 C0A8D52B.O02C.090974152007 PRD 1
SAPPRD disp+work 15 C0A8D52B.O027.090554152007 PRD 1
SAPPRD disp+work 14 C0A8D52B.O026.000C34152007 PRD 1
SAPPRD disp+work 19 C0A8D52B.O02B.050514152007 PRD 1
SAPPRD disp+work 18 C0A8D52B.O02A.0A0774152007 PRD 1
SAPPRD disp+work 17 C0A8D52B.O029.080814152007 PRD 1
SAPPRD disp+work 13 C0A8D52B.O025.080DB4152007 PRD 1
SAPPRD disp+work 12 C0A8D52B.O024.0B0D34152007 PRD 1
In Node A : db2 get dbm cfg :
gipdb:prdadm 3> db2 get dbm cfg
Database Manager Configuration
Node type = Enterprise Server Edition with local and remote clients
Database manager configuration release level = 0x0a00
CPU speed (millisec/instruction) (CPUSPEED) = 3.581945e-07
Communications bandwidth (MB/sec) (COMM_BANDWIDTH) = 1.000000e+02
Max number of concurrently active databases (NUMDB) = 8
Data Links support (DATALINKS) = NO
Federated Database System Support (FEDERATED) = NO
Transaction processor monitor name (TP_MON_NAME) =
Default charge-back account (DFT_ACCOUNT_STR) =
Java Development Kit installation path (JDK_PATH) = /usr/java14_64
Diagnostic error capture level (DIAGLEVEL) = 3
Notify Level (NOTIFYLEVEL) = 3
Diagnostic data directory path (DIAGPATH) = /db2/PRD/db2dump
Default database monitor switches
Buffer pool (DFT_MON_BUFPOOL) = ON
Lock (DFT_MON_LOCK) = ON
Sort (DFT_MON_SORT) = ON
Statement (DFT_MON_STMT) = ON
Table (DFT_MON_TABLE) = ON
Timestamp (DFT_MON_TIMESTAMP) = ON
Unit of work (DFT_MON_UOW) = ON
Monitor health of instance and databases (HEALTH_MON) = OFF
SYSADM group name (SYSADM_GROUP) = DBPRDADM
SYSCTRL group name (SYSCTRL_GROUP) = DBPRDCTL
SYSMAINT group name (SYSMAINT_GROUP) = DBPRDMNT
SYSMON group name (SYSMON_GROUP) =
Client Userid-Password Plugin (CLNT_PW_PLUGIN) =
Client Kerberos Plugin (CLNT_KRB_PLUGIN) =
Group Plugin (GROUP_PLUGIN) =
GSS Plugin for Local Authorization (LOCAL_GSSPLUGIN) =
Server Plugin Mode (SRV_PLUGIN_MODE) = UNFENCED
Server List of GSS Plugins (SRVCON_GSSPLUGIN_LIST) =
Server Userid-Password Plugin (SRVCON_PW_PLUGIN) =
Server Connection Authentication (SRVCON_AUTH) = NOT_SPECIFIED
Database manager authentication (AUTHENTICATION) = SERVER_ENCRYPT
Cataloging allowed without authority (CATALOG_NOAUTH) = NO
Trust all clients (TRUST_ALLCLNTS) = YES
Trusted client authentication (TRUST_CLNTAUTH) = CLIENT
Bypass federated authentication (FED_NOAUTH) = NO
Default database path (DFTDBPATH) = /db2/PRD
Database monitor heap size (4KB) (MON_HEAP_SZ) = 128
Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 2048
Audit buffer size (4KB) (AUDIT_BUF_SZ) = 0
Size of instance shared memory (4KB) (INSTANCE_MEMORY) = AUTOMATIC
Backup buffer default size (4KB) (BACKBUFSZ) = 1024
Restore buffer default size (4KB) (RESTBUFSZ) = 1024
Sort heap threshold (4KB) (SHEAPTHRES) = 20000
Directory cache support (DIR_CACHE) = NO
Application support layer heap size (4KB) (ASLHEAPSZ) = 16
Max requester I/O block size (bytes) (RQRIOBLK) = 65000
Query heap size (4KB) (QUERY_HEAP_SZ) = 2000
Workload impact by throttled utilities(UTIL_IMPACT_LIM) = 10
Priority of agents (AGENTPRI) = SYSTEM
Max number of existing agents (MAXAGENTS) = 1024
Agent pool size (NUM_POOLAGENTS) = 10
Initial number of agents in pool (NUM_INITAGENTS) = 5
Max number of coordinating agents (MAX_COORDAGENTS) = (MAXAGENTS - NUM_INIT
AGENTS)
Max no. of concurrent coordinating agents (MAXCAGENTS) = MAX_COORDAGENTS
Max number of client connections (MAX_CONNECTIONS) = MAX_COORDAGENTS
Keep fenced process (KEEPFENCED) = YES
Number of pooled fenced processes (FENCED_POOL) = MAX_COORDAGENTS
Initial number of fenced processes (NUM_INITFENCED) = 0
Index re-creation time and redo index build (INDEXREC) = RESTART
Transaction manager database name (TM_DATABASE) = 1ST_CONN
Transaction resync interval (sec) (RESYNC_INTERVAL) = 180
SPM name (SPM_NAME) =
SPM log size (SPM_LOG_FILE_SZ) = 256
SPM resync agent limit (SPM_MAX_RESYNC) = 20
SPM log path (SPM_LOG_PATH) =
TCP/IP Service name (SVCENAME) = sapdb2PRD
Discovery mode (DISCOVER) = SEARCH
Discover server instance (DISCOVER_INST) = ENABLE
Maximum query degree of parallelism (MAX_QUERYDEGREE) = 1
Enable intra-partition parallelism (INTRA_PARALLEL) = NO
No. of int. communication buffers(4KB)(FCM_NUM_BUFFERS) = 4096
Number of FCM request blocks (FCM_NUM_RQB) = AUTOMATIC
Number of FCM connection entries (FCM_NUM_CONNECT) = AUTOMATIC
Number of FCM message anchors (FCM_NUM_ANCHORS) = AUTOMATIC
Node connection elapse time (sec) (CONN_ELAPSE) = 10
Max number of node connection retries (MAX_CONNRETRIES) = 5
Max time difference between nodes (min) (MAX_TIME_DIFF) = 60
db2start/db2stop timeout (min) (START_STOP_TIME) = 10
gipdb:prdadm 4>
For Node B : db2 get dbm cfg
/dev/hd3 2097152 1918984 9% 207 1% /tmp
/dev/fwdump 262144 261776 1% 4 1% /var/adm/ras/platform
/dev/hd1 1048576 851168 19% 170 1% /home
/proc - - - - - /proc
/dev/hd10opt 262144 159828 40% 3067 8% /opt
/dev/fslv00 4194304 3354388 21% 269 1% /fixes
/dev/sapinstdir 41943040 22572388 47% 24562 1% /sapinstdir
/dev/db2 5242880 5220288 1% 222 1% /db2
df -k
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/hd4 1048576 1013496 4% 2396 2% /
/dev/hd2 10485760 8399540 20% 49837 3% /usr
/dev/hd9var 2097152 2038144 3% 867 1% /var
/dev/hd3 2097152 1918984 9% 208 1% /tmp
/dev/fwdump 262144 261776 1% 4 1% /var/adm/ras/platform
/dev/hd1 1048576 851168 19% 170 1% /home
/proc - - - - - /proc
/dev/hd10opt 262144 159828 40% 3067 8% /opt
/dev/fslv00 4194304 3354388 21% 269 1% /fixes
/dev/sapinstdir 41943040 22572388 47% 24562 1% /sapinstdir
/dev/db2 5242880 5220288 1% 222 1% /db2
ifconfig -a
en0: flags=5e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT
,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN>
inet 192.168.0.11 netmask 0xffffff00 broadcast 192.168.0.255
inet 192.168.213.42 netmask 0xffffff00 broadcast 192.168.213.255
tcp_sendspace 131072 tcp_recvspace 65536
en2: flags=5e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT
,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN>
inet 192.167.0.11 netmask 0xffffff00 broadcast 192.167.0.255
inet 192.168.213.44 netmask 0xffffff00 broadcast 192.168.213.255
tcp_sendspace 131072 tcp_recvspace 65536
lo0: flags=e08084b<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT
>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1
df -k
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/hd4 1048576 1013492 4% 2396 2% /
/dev/hd2 10485760 8399540 20% 49837 3% /usr
/dev/hd9var 2097152 2038124 3% 867 1% /var
/dev/hd3 2097152 1918984 9% 207 1% /tmp
/dev/fwdump 262144 261776 1% 4 1% /var/adm/ras/platform
/dev/hd1 1048576 851164 19% 170 1% /home
/proc - - - - - /proc
/dev/hd10opt 262144 159828 40% 3067 8% /opt
/dev/fslv00 4194304 3354388 21% 269 1% /fixes
/dev/sapinstdir 41943040 22572388 47% 24562 1% /sapinstdir
/dev/db2 5242880 5220288 1% 222 1% /db2
df -k
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/hd4 1048576 1013492 4% 2396 2% /
/dev/hd2 10485760 8399540 20% 49837 3% /usr
/dev/hd9var 2097152 2038112 3% 867 1% /var
/dev/hd3 2097152 1918952 9% 207 1% /tmp
/dev/fwdump 262144 261776 1% 4 1% /var/adm/ras/platform
/dev/hd1 1048576 851160 19% 170 1% /home
/proc - - - - - /proc
/dev/hd10opt 262144 159828 40% 3067 8% /opt
/dev/fslv00 4194304 3354388 21% 269 1% /fixes
/dev/sapinstdir 41943040 22572388 47% 24562 1% /sapinstdir
/dev/db2 5242880 5220288 1% 222 1% /db2
df -k
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/hd4 1048576 1013488 4% 2397 2% /
/dev/hd2 10485760 8399540 20% 49837 3% /usr
/dev/hd9var 2097152 2037824 3% 867 1% /var
/dev/hd3 2097152 1918864 9% 206 1% /tmp
/dev/fwdump 262144 261776 1% 4 1% /var/adm/ras/platform
/dev/hd1 1048576 851132 19% 170 1% /home
/proc - - - - - /proc
/dev/hd10opt 262144 159828 40% 3067 8% /opt
/dev/fslv00 4194304 3354388 21% 269 1% /fixes
/dev/sapinstdir 41943040 22572388 47% 24562 1% /sapinstdir
/dev/db2 5242880 5220288 1% 222 1% /db2
gipdb:/export/sapmnt/PRD 5242880 4522896 14% 811 1% /sapmnt/PRD
gipdb:/export/sapPRD/PRD 5242880 3791848 28% 2256 1% /usr/sap/PR
D
gipdb:/export/saptrans/trans 20971520 16987600 19% 655 1% /usr/sa
p/trans
su - prdadm
gipapp:prdadm 1> gipdb:prdadm 2> db2 list applications
Auth Id Application Appl. Application Id gipdb:prdadm: Co
mmand not found.
DB gipapp:prdadm 2> # ogipapp:prdadm 2> f
Auth: Command not found.
gipapp:prdadm 3> Name Handle N
ame Agent
-Name: Command not found.
gipapp:prdadm 4> -
SAPPRD----
: Command not found.
gipapp:prdadm 5> disp+work 40 C0A8D52B.O042.0A0574152020 PRD
1
SAPPRSAPPRD: Command not found.
gipapp:prdadm 6> D disp+work 39 C0A8D52B.O041.020CF4152020 PR
D 1
SAPPRD SAPPRD: Command not found.
gipapp:prdadm 7> disp+work 38 C0A8D52B.O040.0C0E94152020 PRD
1
SAPPRD SAPPRD: Command not found.
gipapp:prdadm 8> disp+work 37 C0A8D52B.O03F.000574152019 PRD
1
SAPPRDSAPPRD: Command not found.
disgipapp:prdadm 9> p+work 36 C0A8D52B.O03E.020314152019 PRD
1
SAPPRD SAPPRD: Command not found.
gipapp:prdadm 10> disp+work 35 C0A8D52B.O03D.0301B4152019 PRD
1
SAPPRD diSAPPRD: Command not found.
gipapp:prdadm 11> sp+work 34 C0A8D52B.O03C.040234152019 PRD
1
SAPPRD SAPPRD: Command not found.
gipapp:prdadm 12> disp+work 33 C0A8D52B.O03B.090D34152018 PRD
1
SAPPRSAPPRD: Command not found.
D dgipapp:prdadm 13> isp+work 32 C0A8D52B.O03A.070974152018 P
RD 1
SAPSAPPRD: Command not found.
gipapp:prdadm 14> PRD disp+work 31 C0A8D52B.O039.0F0D14152018
PRD 1
SAPPSAPPRD: Command not found.
gipapp:prdadm 15> RD disp+work 30 C0A8D52B.O038.050DB4152018
PRD 1
SAPPRSAPPRD: Command not found.
gipapp:prdadm 16> D disp+work 29 C0A8D52B.O037.0B02D4152018 P
RD 1
SAPPRSAPPRD: Command not found.
Dgipapp:prdadm 17> disp+work 28 C0A8D52B.O036.050794152018 P
RD 1
SAPPRSAPPRD: Command not found.
gipapp:prdadm 18> D disp+work 27 C0A8D52B.O035.040C14152018 P
RD 1
SAPPRDSAPPRD: Command not found.
gipapp:prdadm 19> disp+work 26 C0A8D52B.O034.0D0D94152014 PR
D 1
SAPPRD SAPPRD: Command not found.
gipapp:prdadm 20> disp+work 25 C0A8D52B.O032.070034152012 PRD
1
SAPPRSAPPRD: Command not found.
gipapp:prdadm 21> D disp+work 24 C0A8D52B.O030.0E0AD4152011 P
RD 1
SAPSAPPRD: Command not found.
gipapp:prdadm 22> PRD disp+work 23 C0A8D52B.O02F.0B0614152009
PRD 1
SAPSAPPRD: Command not found.
gipapp:prdadm 23> PRD disp+work 22 C0A8D52B.O02E.0A0C54152007
PRD 1
SAPPSAPPRD: Command not found.
gipapp:prdadm 24> RD disp+work 21 C0A8D52B.O02D.080534152007
PRD 1
SASAPPRD: Command not found.
gipapp:prdadm 25> PPRD disp+work 16 C0A8D52B.O028.0407F4152007
PRD 1
SAPPSAPPRD: Command not found.
gipapp:prdadm 26> RD disp+work 20 C0A8D52B.O02C.090974152007
PRD 1
SASAPPRD: Command not found.
gipapp:prdadm 27> PPRD disp+work 15 C0A8D52B.O027.090554152007
PRD 1
SSAPPRD: Command not found.
gipapp:prdadm 28> APPRD disp+work 14 C0A8D52B.O026.000C34152007
PRD 1
SASAPPRD: Command not found.
gipapp:prdadm 29> PPRD disp+work 19 C0A8D52B.O02B.050514152007
PRD 1
SAPPSAPPRD: Command not found.
gipapp:prdadm 30> RD disp+work 18 C0A8D52B.O02A.0A0774152007
PRD 1
SASAPPRD: Command not found.
gipapp:prdadm 31> PPRD disp+work 17 C0A8D52B.O029.080814152007
PRD 1
SAPPSAPPRD: Command not found.
gipapp:prdadm 32> RD disp+work 13 C0A8D52B.O025.080DB4152007
PRD 1
SASAPPRD: Command not found.
gipapp:prdadm 33> PPRD disp+work 12 C0A8D52B.O024.0B0D34152007
PRD 1
SAPPRD: Command not found.
gipapp:prdadm 34> db2 list applications
SQL1032N No start database manager command was issued. SQLSTATE=57019
gipapp:prdadm 35> startsap D01
Checking db Database
gipapp:prdadm 38> db2 get dbm cfg
Database Manager Configuration
Node type = Enterprise Server Edition with local and remote clients
Database manager configuration release level = 0x0a00
CPU speed (millisec/instruction) (CPUSPEED) = 4.000000e-05
Communications bandwidth (MB/sec) (COMM_BANDWIDTH) = 1.250000e+00
Max number of concurrently active databases (NUMDB) = 8
Data Links support (DATALINKS) = NO
Federated Database System Support (FEDERATED) = NO
Transaction processor monitor name (TP_MON_NAME) =
Default charge-back account (DFT_ACCOUNT_STR) =
Java Development Kit installation path (JDK_PATH) = /usr/java14_64
Diagnostic error capture level (DIAGLEVEL) = 3
Notify Level (NOTIFYLEVEL) = 3
Diagnostic data directory path (DIAGPATH) = /db2/PRD/db2dump
Default database monitor switches
Buffer pool (DFT_MON_BUFPOOL) = OFF
Lock (DFT_MON_LOCK) = OFF
Sort (DFT_MON_SORT) = OFF
Statement (DFT_MON_STMT) = OFF
Table (DFT_MON_TABLE) = OFF
Timestamp (DFT_MON_TIMESTAMP) = ON
Unit of work (DFT_MON_UOW) = OFF
Monitor health of instance and databases (HEALTH_MON) = ON
SYSADM group name (SYSADM_GROUP) = DBPRDADM
SYSCTRL group name (SYSCTRL_GROUP) = DBPRDCTL
SYSMAINT group name (SYSMAINT_GROUP) = DBPRDMNT
SYSMON group name (SYSMON_GROUP) =
Client Userid-Password Plugin (CLNT_PW_PLUGIN) =
Client Kerberos Plugin (CLNT_KRB_PLUGIN) =
Group Plugin (GROUP_PLUGIN) =
GSS Plugin for Local Authorization (LOCAL_GSSPLUGIN) =
Server Plugin Mode (SRV_PLUGIN_MODE) = UNFENCED
Server List of GSS Plugins (SRVCON_GSSPLUGIN_LIST) =
Server Userid-Password Plugin (SRVCON_PW_PLUGIN) =
Server Connection Authentication (SRVCON_AUTH) = NOT_SPECIFIED
Database manager authentication (AUTHENTICATION) = SERVER_ENCRYPT
Cataloging allowed without authority (CATALOG_NOAUTH) = NO
Trust all clients (TRUST_ALLCLNTS) = YES
Trusted client authentication (TRUST_CLNTAUTH) = CLIENT
Bypass federated authentication (FED_NOAUTH) = NO
Default database path (DFTDBPATH) = /db2/PRD
Database monitor heap size (4KB) (MON_HEAP_SZ) = 90
Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 2048
Audit buffer size (4KB) (AUDIT_BUF_SZ) = 0
Size of instance shared memory (4KB) (INSTANCE_MEMORY) = AUTOMATIC
Backup buffer default size (4KB) (BACKBUFSZ) = 1024
Restore buffer default size (4KB) (RESTBUFSZ) = 1024
Sort heap threshold (4KB) (SHEAPTHRES) = 20000
Directory cache support (DIR_CACHE) = YES
Application support layer heap size (4KB) (ASLHEAPSZ) = 15
Max requester I/O block size (bytes) (RQRIOBLK) = 32767
Query heap size (4KB) (QUERY_HEAP_SZ) = 1000
Workload impact by throttled utilities(UTIL_IMPACT_LIM) = 10
Priority of agents (AGENTPRI) = SYSTEM
Max number of existing agents (MAXAGENTS) = 1024
Agent pool size (NUM_POOLAGENTS) = 10
Initial number of agents in pool (NUM_INITAGENTS) = 5
Max number of coordinating agents (MAX_COORDAGENTS) = (MAXAGENTS - NUM_INIT
AGENTS)
Max no. of concurrent coordinating agents (MAXCAGENTS) = MAX_COORDAGENTS
Max number of client connections (MAX_CONNECTIONS) = MAX_COORDAGENTS
Keep fenced process (KEEPFENCED) = YES
Number of pooled fenced processes (FENCED_POOL) = MAX_COORDAGENTS
Initial number of fenced processes (NUM_INITFENCED) = 0
Index re-creation time and redo index build (INDEXREC) = RESTART
Transaction manager database name (TM_DATABASE) = 1ST_CONN
Transaction resync interval (sec) (RESYNC_INTERVAL) = 180
SPM name (SPM_NAME) =
SPM log size (SPM_LOG_FILE_SZ) = 256
SPM resync agent limit (SPM_MAX_RESYNC) = 20
SPM log path (SPM_LOG_PATH) =
TCP/IP Service name (SVCENAME) = sapdb2PRD
Discovery mode (DISCOVER) = SEARCH
Discover server instance (DISCOVER_INST) = ENABLE
Maximum query degree of parallelism (MAX_QUERYDEGREE) = ANY
Enable intra-partition parallelism (INTRA_PARALLEL) = NO
No. of int. communication buffers(4KB)(FCM_NUM_BUFFERS) = 4096
Number of FCM request blocks (FCM_NUM_RQB) = AUTOMATIC
Number of FCM connection entries (FCM_NUM_CONNECT) = AUTOMATIC
Number of FCM message anchors (FCM_NUM_ANCHORS) = AUTOMATIC
Node connection elapse time (sec) (CONN_ELAPSE) = 10
Max number of node connection retries (MAX_CONNRETRIES) = 5
Max time difference between nodes (min) (MAX_TIME_DIFF) = 60
db2start/db2stop timeout (min) (START_STOP_TIME) = 10
gipapp:prdadm 39> -
EBS 12.1.3 & OCM: few questions
Hi,
I would need some clarification when using Oracle Configuration Manager (OCM) with EBS 12.1.3. I have multi-node (app node + db node in separate servers) EBS 12.1.3 environment where I've configured OCM as follows.
Installed OCM (setupCCR) and executed the following scripts in DB node:
$ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh collectconfig -s <SID> -r system
$ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh ebs_collectconfig -u apps -w <apps password>
In app node, I've installed (setupCCR) OCM under $ORACLE_HOME (10.1.2).
Is this correct?
In MOS, I see two entries in Dashboard -> Systems with types:
- Oracle E-Business Suite System
- Database Instance
Under "E-Business Suite System" there are two targets:
- Oracle E-Business Suite <ORACLE_SID>appsdb
---> Database Instance <ORACLE_SID>
Under "Database Instance"
---> Database Instance <ORACLE_SID>
If OCM is configured properly for EBS R12 what are the correct entries in Systems section? And, what targets (Oracle Concurrent Manager, Database Instance) should be under which entry?
Also, when raising an SR, there is only database host available in the host list. Is this correct?
Thanks for your replies in advance.
BR,
THIn app node, I've installed (setupCCR) OCM under $ORACLE_HOME (10.1.2).
Is this correct?Yes.
How To Install and Configure OCM 10.3 on e-Business Suite [ID 1084325.1]
How To Install or Reconfigure the Oracle Configuration Manager (OCM) Using the emocmrsp Command [ID 975500.1]
In MOS, I see two entries in Dashboard -> Systems with types:
- Oracle E-Business Suite System
- Database Instance
Under "E-Business Suite System" there are two targets:
- Oracle E-Business Suite <ORACLE_SID>appsdb
---> Database Instance <ORACLE_SID>
Under "Database Instance"
---> Database Instance <ORACLE_SID>
If OCM is configured properly for EBS R12 what are the correct entries in Systems section? And, what targets (Oracle Concurrent Manager, Database Instance) should be under which entry?
Also, when raising an SR, there is only database host available in the host list. Is this correct?OCM ( Oracle Configuration Manager ) and My Oracle Support : FAQ and Troubleshooting [ID 369619.1]
How to install and configure OCM 10.3.1 on an E-Business R12 [ID 818385.1]
Thanks,
Hussein -
Controlling EJB Cache & Warning BEA-010001 in 8.1
Background: Migrated from 6.1 to 8.1. Using CMP with template.j modified (migrated).
Problem:
1. Could not use any Entities which uses Entity Cache. It throws weblogic.ejb20.cache.CacheFullException
during ejbLoad. My existing Cache parameters are (anyway, it is no different from
6.1 where itz working fine)
<pool>
<max-beans-in-free-pool>100</max-beans-in-free-pool>
</pool>
<entity-cache>
<max-beans-in-cache>100</max-beans-in-cache>
<idle-timeout-seconds>610</idle-timeout-seconds>
<read-timeout-seconds>60</read-timeout-seconds>
<concurrency-strategy>Database</concurrency-strategy>
</entity-cache>
Is there any new configuration which needs to be set for 8.1? Redirection to
some checklist for controlling there cache parameter would be helpful?
2. While deploying my Beans it shows up Warning BEA-010001. Documentation says,
specify in weblogic-ejb-jar.xml<weblogic-ejb-jar> <disable-warning>BEA-010001
| BEA-010054</disable-warning>..</weblogic-ejb-jar>. I have thousands of beans
deployed in the server my warning message dumps my console with these messages
hiding critical error messages. Is there any 'additional parameters' to stop
this warning or route this warning to a separate log file?
TIA
JAKHi Jak,
max-beans-in-cache equal 100 is way too low for any real life application.
I'm not sure why it worked for you in 6.1. I remember setting it was broken
in 6.1 at some point.
Regards,
Slava Imeshev
"jak" <[email protected]> wrote in message
news:3f07e7c9$[email protected]..
>
Background: Migrated from 6.1 to 8.1. Using CMP with template.j modified(migrated).
>
Problem:
1. Could not use any Entities which uses Entity Cache. It throwsweblogic.ejb20.cache.CacheFullException
during ejbLoad. My existing Cache parameters are (anyway, it is nodifferent from
6.1 where itz working fine)
<pool>
<max-beans-in-free-pool>100</max-beans-in-free-pool>
</pool>
<entity-cache>
<max-beans-in-cache>100</max-beans-in-cache>
<idle-timeout-seconds>610</idle-timeout-seconds>
<read-timeout-seconds>60</read-timeout-seconds>
<concurrency-strategy>Database</concurrency-strategy>
</entity-cache>
Is there any new configuration which needs to be set for 8.1? Redirectionto
some checklist for controlling there cache parameter would be helpful?
2. While deploying my Beans it shows up Warning BEA-010001. Documentationsays,
specify in weblogic-ejb-jar.xml<weblogic-ejb-jar><disable-warning>BEA-010001
| BEA-010054</disable-warning>..</weblogic-ejb-jar>. I have thousands ofbeans
deployed in the server my warning message dumps my console with thesemessages
hiding critical error messages. Is there any 'additional parameters' tostop
this warning or route this warning to a separate log file?
TIA
JAK -
Best Practice E-Business 12.1.3/11gR2 Hardware Configuration
Hi
We are in the design phase for a new install of E-Business 12.1.3 / 11gR2
From a hardware services point, what is deemed to be the "best practice"?
Option 1
1 x Web/Forms Node
1 x Concurrent Manager Node
1 x Database ode
Option 2
1 x web/forms/concurrent manager node
1 x database node
Option 3
1 x web/forms/concurrent manager/database node
In the past I have always gone with Option 2 so that the database traffic is minimised between conc managers / database. That to me seemed most logical. But wanted to ask the oracle community about their thoughts
We are using redhat linux / Cisco Blades (USC/VMWARE) and all connecting to a NetApp FAS3270.
PLease advise if you pick this up.
ThanksExactly what I was thinking but its nice to get someone elses clarity too.
The PCP option is certainly something I need to take into consideration - but with the new abilities of 12.1.3 cloning processes - it would be easy enough to split the admin Conc Nodes away at a later date should the requirement exist.
i.e.
Initially have 1 x forms/web server plus 1 x database / concurrent manager node
If we need to go to PCP and / or forms load balancing
we could easily go to 2 x forms / web server and add the Conc Node into it brining in PCP too.
I have to admist, the way Oracle have sorted the cloning process is 12 is very good indeed.
Do you agree?I totally agree :)
You just need to run preclone on the source apps tier node, then copy the files to the second node (add new node), and run adcfgclone.pl/adaddnode.pl scripts.
Cloning Oracle Applications Release 12 with Rapid Clone [ID 406982.1] -- Option 3: Adding a New Node to an Existing System
You seem to be pretty active on this forum - I am new to thisWelcome to the forums.
Thanks,
Hussein -
What does open_links parameter mean ?
Say if the value is 4 and remote databases are A,B and C
1. Does it mean you can have only 4 concurrent sqls accessing a remote database (remote database A)
2. Does it mean you can have as many SQL's accessing "A" as long as the total number of concurrent remote database reference does not exceed 4 (N sql's accessing database "A" and M sql's accessing database "B" concurrently where N and M > 4)
Also an explanation of what exactly happens when you query using a database link.http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96536/ch1133.htm#1020574
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96521/ds_concepts.htm#12354 -
Reg LGWR got killed by OS utility
Hi,
Last saturday i faced a strange issue in my database.
My environment:
Oracle EBS.
Two node installation.
Forms and Web in One server and
Concurrent and Database in Another.
We have sheduled backup on every saturday.
Duing last saturday,after backup was completed,We started the instance it was normal,
We also checked the working on instance and concurrent managers by running reports.
it was around 9 pm.
Then sysadmin guy has started restoration from san storage using tivoli client to one mount point in
same database server.
It was around 10.24 pm LGWR process was killed automatically by OOM(out of memory killer) in Linux.
I have copied the alert log entries during that time.
DETAILS FROM bdump from Oracle Database
Sat Jun 5 20:58:20 2010
Starting ORACLE instance (normal)
PMON started with pid=2, OS id=13375
PSP0 started with pid=3, OS id=13377
MMAN started with pid=4, OS id=13379
DBW0 started with pid=5, OS id=13381
DBW1 started with pid=6, OS id=13383
LGWR started with pid=7, OS id=13385
CKPT started with pid=8, OS id=13387
SMON started with pid=9, OS id=13389
RECO started with pid=10, OS id=13391
CJQ0 started with pid=11, OS id=13393
MMON started with pid=12, OS id=13395
MMNL started with pid=13, OS id=13397
Sat Jun 5 22:24:42 2010
Errors in file /oracle/PROD/app/proddb/10.2.0/admin/PROD_dbserv1/bdump/prod_pmon_13375.trc:
ORA-00470: LGWR process terminated with error
Sat Jun 5 22:24:45 2010
Errors in file /oracle/PROD/app/proddb/10.2.0/admin/PROD_dbserv1/bdump/prod_ckpt_13387.trc:
ORA-00470: LGWR process terminated with error
Sat Jun 5 22:24:48 2010
PMON: terminating instance due to error 470
Sat Jun 5 22:24:48 2010
Errors in file /oracle/PROD/app/proddb/10.2.0/admin/PROD_dbserv1/bdump/prod_dbw0_13381.trc:
ORA-00470: LGWR process terminated with error
Sat Jun 5 22:24:48 2010
Errors in file /oracle/PROD/app/proddb/10.2.0/admin/PROD_dbserv1/bdump/prod_psp0_13377.trc:
ORA-00470: LGWR process terminated with error
Sat Jun 5 22:24:48 2010
Errors in file /oracle/PROD/app/proddb/10.2.0/admin/PROD_dbserv1/bdump/prod_mman_13379.trc:
ORA-00470: LGWR process terminated with error
Instance terminated by PMON, pid = 13375
Below are trace file contents.
prod_pmon_13375.trc
*** 2010-06-05 22:24:42.417
*** SERVICE NAME:(SYS$BACKGROUND) 2010-06-05 22:24:38.983
*** SESSION ID:(1000.1) 2010-06-05 22:24:38.983
Background process LGWR found dead
Oracle pid = 7
OS pid (from detached process) = 13385
OS pid (from process state) = 13385
dtp = 0x2000bbf0, proc = 0x52a15e84
error 470 detected in background process
ORA-00470: LGWR process terminated with error
==========
prod_ckpt_13387.trc
*** 2010-06-05 21:34:57.543
*** SERVICE NAME:(SYS$BACKGROUND) 2010-06-05 21:34:56.241
*** SESSION ID:(994.1) 2010-06-05 21:34:56.241
*** 2010-06-05 21:34:56.241 62692 kcrr.c
ARCH: Detected ARCH process failure
*** 2010-06-05 21:40:32.152
*** 2010-06-05 21:40:32.152 62692 kcrr.c
ARCH: Detected ARCH process failure
*** 2010-06-05 21:45:04.723
*** 2010-06-05 21:45:04.723 62692 kcrr.c
ARCH: Detected ARCH process failure
*** 2010-06-05 22:24:45.661
error 470 detected in background process
ORA-00470: LGWR process terminated with error
==================
prod_dbw0_13381.trc
*** 2010-06-05 22:24:48.507
*** SERVICE NAME:(SYS$BACKGROUND) 2010-06-05 22:24:45.800
*** SESSION ID:(997.1) 2010-06-05 22:24:45.800
error 470 detected in background process
ORA-00470: LGWR process terminated with error
===================
prod_psp0_13377.trc
*** 2010-06-05 22:24:48.509
** SERVICE NAME:(SYS$BACKGROUND) 2010-06-05 22:24:46.405
*** SESSION ID:(999.1) 2010-06-05 22:24:46.405
error 470 detected in background process
ORA-00470: LGWR process terminated with error
===================
prod_mman_13379.trc
*** 2010-06-05 22:24:48.510
*** SERVICE NAME:(SYS$BACKGROUND) 2010-06-05 22:24:47.705
*** SESSION ID:(998.1) 2010-06-05 22:24:47.705
error 470 detected in background process
ORA-00470: LGWR process terminated with error
DETAILS FROM /var/log/messages from OS
Jun 5 22:39:24 dbserv2 kernel: Out of Memory: Killed process 27262 (oracle).
Jun 5 22:35:27 dbserv2 kernel: Out of Memory: Killed process 21588 (oracle).
Jun 5 22:30:17 dbserv2 kernel: Out of Memory: Killed process 20745 (oracle).
Jun 5 22:29:59 dbserv2 kernel: Out of Memory: Killed process 20101 (oracle).
Jun 5 22:29:41 dbserv2 kernel: Out of Memory: Killed process 19896 (oracle).
Jun 5 22:29:25 dbserv2 kernel: Out of Memory: Killed process 16243 (oracle).
Jun 5 22:25:23 dbserv2 kernel: Out of Memory: Killed process 13670 (oracle).
Jun 5 22:24:47 dbserv2 kernel: Out of Memory: Killed process 13035 (oracle).
Jun 5 22:24:39 dbserv2 kernel: Out of Memory: Killed process 13385 (oracle). LGWR started with pid=7, OS id=13385
Jun 5 22:24:30 dbserv2 kernel: Out of Memory: Killed process 2436 (oracle).
Jun 5 22:24:30 dbserv2 kernel: Out of Memory: Killed process 2192 (oracle).
Jun 5 22:24:30 dbserv2 kernel: Out of Memory: Killed process 12585 (oracle).
Jun 5 22:23:58 dbserv2 kernel: Out of Memory: Killed process 6985 (oracle).
Jun 5 21:30:47 dbserv2 kernel: Out of Memory: Killed process 20644 (oracle).
If any of you have faced the same issue kindly help me.
Regards
KrishnaFrom OS error message , Looks like there was resource crunch at the time of crash.
What was the CPU/Memory/Swap utilization at time of crash.
Also check out for kernel parameters.
Please follow below MOS note and also raise SR with support. :
Pmon terminated instance due to LGWR termination ORA-470 [ID 431246.1]
BACKGROUND PROCESS DIES, NO TRACE FILE GENERATED [ID 1029808.6]
Regards
Rajesh
Maybe you are looking for
-
Open "Navigate" enabled report in new window - OBI10g.
Hello Experts, May be its novice user question, i have 2 reports, source and target reports. Both reports are connected using "Navigate" functionality. Issue is, i wan to open the target report in new window? is that possible? using GO URL: we have a
-
Internet and email not working. PLEASE help.
So I've had my blackberry for a couple of moths and everything's been fine. Yesterday I stopped receiving emails on my blackberry and I also noticed that my internet wasn't working anymore. It came up with the message 'unable to connec to the interne
-
When OCCI will support GNU GCC v3.3.2?
When OCCI will support GNU GCC v3.3.2? Would like to know when Oracle will release OCCI to support GCC 3.2 or newer version GCC. I plan to estimate OCCI on GCC 3.2.* for Solaris and Linux to help us make decision when will deploy OCCI solution to our
-
File handling in LightR 2.6RC importing from Leica M9
Please help - there is something going on here I don´t understand; 1. I shoot compressed DNG in my Leica - get lovely images! 2. I import to Lightroom 2.6 RC as DNGs via USB cable from the camera/device - usb port set in PTP protocol mode (have not t
-
After install of Mountain Lion I have no facetime. It is nowhere in hd and ap store will not allow download. Will I need to re-instal ML in order to get it back?