Simulate the Cache Buffer Chain latch

Similar Questions

• Cache Buffer Chain latch

  Hi all
  
  What is the CBC lock?
  When it occurs, and why?
  
  What is the inner workings of the latch of the CBC? How can we identify latch of CBC and how to fix it?
  
  -Yasser

  Yasser,

  Database buffer cache is divided into something that is called activities together. Each game has two or three pads inside. These buffers are associated with something called hash strings. When you ask for the buffer for your table, you must acquire the lock of Cache buffer. CBC latch is used to search for your activities of buffer for the necessary buffer based on its Address (DBA) of data block. That's all there is on the latch of the CBC. Rest of the internal components are actually on the cache buffers not on the locking system itself.

  Read this note from Steve Adams for the same institutions,
  http://www.Ixora.com.au/q+a/cache.htm
  HTH
  Aman...

• use of the cache buffer by schema

  Hello world
  
  We have 3 application on the same PB, each using its own scheme.
  
  The sga_target was size to 10 GB and buffer cache is 9 GB (querying V$ SGASTAT).
  
  We need to know the 'quantity' of the buffer cache that each application uses.
  
  Is it possible to do?
  
  Thanks in advance

  Refer to the documentation:
  [url http://docs.oracle.com/cd/E11882_01/server.112/e16638/memory.htm#autoId27] Determine which segments have many buffers in the pool

• latch: cache buffers chains

  Hello dear gurus!
  
  
  

  How to identify a hot block in the database buffer Cache. [163424.1 ID]
  
  This lock is acquired when looking for blocks of data cached in the buffer cache.
  Because the buffer cache is implemented as a sum of channels of blocks, each of these
  channels is protected by a child of this lock when needs to be analyzed.

  Expression protected by that latch children mean that parent latch child lock and buffer to protect protect block and also views
  DBA_HIST_LATCH_PARENT and V$ LATCH_PARENT belongs to the buffers (DBA_HIST_LATCH_CHILDREN, V$ LATCH_CHILDREN belongs to the blocks)?
  
  
  
  Thank you and best regards,
  Pavel

  Hello

  normally when a latch has children, then it doesn't do much on its own: children do most (or all) of the work, for example:

  http://www.freelists.org/post/Oracle-l/difference-between-child-and-parent-LATCHES, 4
  http://learningoracle.WordPress.com/2008/02/19/LATCHES-and-latch-contention/

  I'm not sure if the lock of the buffer cache is also part of this category, but I think your interpretation is wrong.
  Blocks in the buffer cache are organized in a kind of hash buckets, and a child lock protects one or the other or
  several of these buckets, not a specific block of hash. I can't say what function (or even at all) plays exactly the parent latch,
  but the basic logic States that in all cases, it cannot be very restrictive.

  If you need a more precise answer, try the blog of Andrey Nikolaev (andreynikolaev.wordpress.com), or try experimenting with locks
  you on a test system (for example to simulate an activity in the buffer cache and see how the stats for parent and child latches change in time,
  and try to see if stats for parent latches are just the stats are appropriate for their children).

  Best regards
  Nikolai

• LMD are in the DB buffer Cache?

  DB version: 11.2.0.4

  OS: RHEL 6.5

  Oracle documentation defines "database buffer cache" in the following way

  "The buffer of database cache, also called the buffer cache, is the area of memory that stores copies of data in blocks to read data files"

  http://docs.Oracle.com/CD/E25054_01/server.1111/e25789/memory.htm#i10221

  Let's say that the following UPDATE statement updates 100,000 records. The server process go get all the blocks that has the matching records and place it in the DB buffer cache and updates the blocks. This change metadata are recorded in the restore log buffer by progression. At the next checkpoint changed blocks are written to the data files. Right?

  Employee UPDATE

  SET salary = salary * 1.05

  The EMPLOYEE

  WHERE deptnum = 8;

  basically: Yes, once again. Oracle has rewritten Sales buffers (i.e. buffers with different content than the corresponding blocks on the disk) on the drive under certain conditions. If the operation is cancelled, the blocks must be read again in the cache and change must be cancelled (and written).

• Read data larger than the DB buffer Cache

  DB version: 10.2.0.4
  OS: Solarit 5.10
  
  
  We have a DB with 1 GB for DB_CACHE_SIZE. Automatic shared memory management is disabled (SGA_TARGET = 0).
  
  If a query is triggered on a table that will grab the 2 GB of data. Hang in this session? How oracle handles this?

  Tom wrote:
  If the recovered blocks get automatically removed from the buffer cache once it is retrieved by the LRU algorithm, then Oracle must handle this without any problem. Right?

  Yes. No problem in that the "+ a fetch size +" (for example, by selecting 2 GB with a value of lines) need to fit completely in the db (only 1 GB in size) buffer cache.

  As mentioned Sybrand - everything in this case is emptied as blocks of data more recent will be read... and that emptied shortly after thereafter as of the even more recent data blocks are read.

  The ratio / access to the cache will be low.

  But this will not cause Oracle errors or problems - simply that degrade performance as volumes of data being processed exceeds the capacity of the cache.

  It's like running a very broad program that requires more RAM which is available on a PC. The 'additional RAM' is the file on the disk. The APA will be slow because its memory pages (some disk) must be swapped in and out of memory as needed. It will work faster if the PC has an enough RAM. However, the o/s is designed to address this exact situation that requires more RAM than physically available.

  Similar situation with the treatment of large chunks of data than the buffer cache has a capacity of.

• CKPTQ in the database buffer cache and LRU

  Hi experts
  
  
  This feature can settle in cache buffers data base Oracle 10.2 or higher.
  Forums of sources: OTN and 11.2 Concepts guide
  
  According to my readings. To improve the functionality and make it more good American cache database is divided into several zones which are called workareasNow more
  
  Zoom this each activities will store multiple lists to store tampons inside the database buffer cache.
  
  Each wrokarea can have one or more then one lists to keep the wrokordering in there. The list of what each activity will have therefore to list LRU and list CKPTQ. LRU list
  
  is a list of buffers pinned, free and sales and CKPTQ is a list of stamp Sales. We can say THAT CKPTQ is a group of stamps Sales ordering of RBA weak and ready to be flushed from the cache on the disk.
  
  CKPTQ list is maintained by ordering of low RBE.
  As novice let me clearly low RBA and RBA senior first
  
  RBA is stored in the header of the block and we will give the information on which this block is spent and how many times it is changed.
  
  Low RBE: low RBE is the address to redo the first change that was applied to the block since his own last.
  RBA high: the high RBA is the address to redo the last change has been applied to the block.
  
  Now back to CKPTQ
  It can be like this (pathetic CKPTQ diagram)
  
  lowRBA = high RBA
  (Head of the CKPTQ)                         (CKPTQ line)
  
  CKPTQ is a list of stamp Sales. According to the concept of the RBA. The most recent modified buffer is at the tail of CKPTQ.
  
  Now the oracle process starts and try to get the DB cache buffer if she gets a buffer it will put an end SRM to the list.and buffer buffer LRU will become the most
  
  recently used.
  
  Now, if the process cannot find a necessary buffer.then first, he will try to find free tampons to LRU. If he finds his most he will place a datablock to the data file in the
  
  place where free buffer was sitting. (Good enough).
  
  Now, if the process cant fnd a buffer without LRU then first step would be he will find some Sales swabs at the end of the LRU to LRU list and place them on a
  
  CKPTQ (do not forget in the low order of RBA he organize it queue of CKPT). and now the oracle process will buffer required and place it on the end of the MRU of LRU list. (Because space was acclaimed by the displacement of Sales to CKPTQ buffers).
  
  I do not know of CKPTQ buffers (to be more precise tampon Sales) will move to datafiles.all buffers are line up n lower CKPTQ RBA way first. But
  
  emptied to datafile how and in what way and to what event?
  
  That's what I understand after these last three days, flipping through the blogs, forums and concepts guide. Now miss me you please erase me on and off it
  
  I can't bind the following features at this rate... It's
  
  (1) how the work of additional checkpoint with this CKPTQ?
  
  (2) now, what is this 3 second delay?
  
  (Every 3 seconds DBWR process will wake and find if nothing to write about the data files for this DBWR will check only CKPTQ).
  
  Apartment 3) form 3 second funda, when CKPTQ buffers will be moved? (IS IT when the process is unable to find any space in CKPTQ to keep buffers LRU. Its a
  
  moment where CKPTQ buffer will be moved on the disk)
  
  (4) can you please report when the control file will be updated with checkpoint so it can reduce recovery time?
  
  In many ques but I'm trying to build the entire process in mind that its operation may be I can be wrong in any phase in any stage, please correct me upward and
  
  Take me @ the end of the flow.
  
  
  Thank you
  Philippe

  Hi Aman,

  Yes, I a soft copy of ppt or white paper "Harald van Breederode" of 2009.

  -Pavan Kumar N

• clarification of term required for the DB buffer Cache

  Hello!!
  
  Here, I have a very basic conceptual question, DB buffer Cache contains the data read from the data in the file as well reduce the disk i/o of fom and oracle. If suppose that the table is constantly questioned and remains in the DB buffer cache all the time, how does oracle ensures the user gets the latest information?

  The database buffer cache is a part of the zone system Global (SGA), which is responsible for caching of blocks accessed frequently for a segment. The subsequent transactions involving the same blocks can then access them from memory, instead of from the hard disk. The works of cache buffer of database on the basis of least recently used (LRU algorithm), according to which the most frequently accessed blocks are kept in memory while the less frequent are gradually.

  See this link

  http://www.Stanford.edu/dept/ITSS/docs/Oracle/10G/server.101/b10743/memory.htm :)

• What else are stored in the database buffer cache?

  What else are stored in the database buffer cache, except the data reading of data files blocks?

  The nitty gritty on this point, you ask someone smarter than me waaay.

• Trying to simulate the device USB-6366 (without success)

  I read through the tutorials DAQmx and MAX about the simulation of the device, but I can't yet find a way to effectively simulate the acquisition and generation of a signal using a device USB-OR-6366.

  I am a (given at the entrance of this VI) signal using DAQmx Write and then use DAQmx Read to read the signal captured from the internal memory of the card (which has a buffer of 32 MS). To do this, I created a task with DAQmx I feed in the writing block.

  I know that the approach is most likely wrong, but I can't understand not just how to do this in a simple way and documentation of NOR is anything but simple. All I want is to

  (a) test using 2 digital inputs to capture this signal by the device and then read what she has gained from its internal buffer

  (b) send the same signal to 2 digital outputs the signal output again.

  See you soon

  Yes! the simulation is designed to allow you to write a program and check that it works theoretically even if you do not have the material physically available. It has no interface programming to influence on the what the reading functions will return simulated data. And write the function has no notable effect anywhere, working as a receiver of data in nirvana. It is always useful because you can test software without getting all kinds of errors on the non existing hardware access attempt, but it has its limits, of course. However, a programming interface for manipulating that which and how the data are simulated, while it would be a very interesting feature, is almost certainly to complicated not only to implement but also to use.

• SAX parse exception even when the cache xml is correct

  Hello

  I have the bottom of the xml cache and when I start a gemfire Server I get the below error:

  < code >

  ND if read Cache XML file:/C:/vFabric_GemFire_70/insurance_gf_server1/cache.xml. Error while parsing XML, caused by org.xml.sax.SAXParseException: The content of element type "region-attributes" must match "(key-constraint?,value-constraint?,region-time-to-live?,region-idle-time?,entry-time-to-live?,entry-idle-time?,disk-write-attributes?,disk-dirs?,partition-attributes?,membership-attributes?,subscription-attributes?,cache-loader?,cache-writer?,cache-listener*,eviction-attributes?)".

  < code >

  I did check the XML cache and could not find any problems and it is according to the GemFire 7.0 DTD, given below is the xml cache:

  < code >

  <? XML version = "1.0"? >
  <! DOCTYPE PUBLIC cache
  ' - //GemStone systems, declarative Inc.//GemFire 7.0 cached / / IN ".
  " http://www.gemstone.com/DTD/cache7_0.DTD "> "
  < cache lock-location = "120" lock-timeout = '60' research-timeout = '300' is-Server = "true" copy-on-read = "false" >
  < cache-server bind-address port = "${address}" = "${port}" > < / cache server >
  <-critics-bunch-percentage resource manager = "90" expulsion-bunch-percentage = "80" / >
  < record-store name = "insuranceOFDS" allow-force-compression = "true" auto-compact = "true".
  compaction-threshold = "40" oplog-max-size = size of queue "2048" = "1000" interval = "1000" write-buffer-size = "65536" >
  < disk-dirs >
  < disk-dir dir-size "3072" = >$ {GF_SERVER_DS_FOLDER} \insurance_ds < / disc-dir >
  < / disc-dirs >
  < / record store >
  < region attributes id = "defaultRegionAttr" refid = 'PARTITION_REDUNDANT_OVERFLOW' scope = 'distributed-ack ".
  data-policy = "partition" statistical compatible = "true" multicast = 'false' record-store-name = "insuranceOFDS" disc-synchronous = "false" >
  < partition-attributes-redundant copies = '1' total-num-buckets = "113" > < / partition attributes >
  < region-time-to-live >
  < expiry-attributes timeout = "36000" action = "destroy" / >
  < / region-time-to-live >
  < input-time-to-live >
  < expiry-attributes timeout = "900" action = "destroy" / >
  < / entry-time-to-live >
  <>expulsion-attributes
  < lru-memory size maximum = "100" action = "infinity-to-disk" / >
  < / expulsion-attributes >
  < / region-attributes >
  <! - customer area - >
  < name region 'customers' = refid = "defaultRegionAttr" / >
  <! - political region - >
  < name region = "policies" refid = "defaultRegionAttr" / >
  <! - claims region - >
  < name region = "claims" refid = "defaultRegionAttr" / >
  <! - payment area - >
  < name region = 'payments' refid = "defaultRegionAttr" / >
  < / cache >

  < code >

  and the command to start the server:

  < code >

  gfsh start server --name=insurance_gf_server1 --rebalance=true --initial-heap=512M --max-heap=512M --server-bind-address=xxx.xxx.xx.xx --server-port=13490 --J=-DGF_SERVER_DS_FOLDER=C:\vFabric_GemFire_70\insurance_gf_server1,-Daddress=CSCINDAE699524,-Dport=13490,-XX:CMSInitiatingOccupancyFraction=70,-XX:+UseConcMarkSweepGC,-XX:+CMSIncrementalMode,-XX:+CMSIncrementalPacing,-XX:CMSIncrementalDutyCycleMin=0,-XX:CMSIncrementalDutyCycle=10,-XX:+UseParNewGC,-XX:+CMSPermGenSweepingEnabled,-XX:+CMSClassUnloadingEnabled,-XX:MaxGCPauseMillis=250,-XX:MaxGCMinorPauseMillis=100,-XX : + DisableExplicitGC

  < code >

  Can someone help to find the error. Thank you

  The classification is defined by the DTD. This is certainly the case that some DTD defines elements such as the order is not important, but the cache DTD is relatively complex, making this problem very non-negligible.

  See this post SO for general information: http://stackoverflow.com/questions/3022845/dtd-required-elements-ordering

  Then imagine this just apply this to an item in the cache of DTD:

  The DTD would probably increase by several orders of magnitude.

  However, we could certainly make a point by asserting, in the docs, the order is important.

• Application is not able to connect using the Oracle SCAN chain

  Dear Oracle gurus
  
  We have 11g r2 11.2.0.3.0 2 cluster nodes
  
  We have configured the scanning using scan-vip single using/etc/hosts file resolution
  
  Our app to work correctly using the string of double local Vip (10g method)
  
  Scan works very well in the database server when we check using sqlplus
  
  Works very well in the database server Oracle SCAN
  
  Sqlplus DB - 1 test bench / testbed@my-db-scan:1521 / orcl
  
  When we use it below URL JDBC in Tomcat Version-6 then "doesn't allow not to connect even if there will connect a while but connectivity isn't stable when we reboot the tomcat"
  
  Hibernate.Connection.URL=jdbc:Oracle:Thin:@My-DB-Scan:1521/ORCL
  
  Application is not able to connect using the Oracle SCAN chain
  
  [May 13, 2013 12:48:24] [INFO] [0.0.0.0] - [DATA MANAGER FACTORY] unknown: init() Called.
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: adding the data manager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: *.
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 1: com.cmp.mysm.hibernate.core.system.staff.HStaffDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 2: com.cmp.mysm.hibernate.core.system.systemparameter.HSystemParameterDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 3: com.cmp.mysm.hibernate.core.system.profilemanagement.HProfileDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 4: com.cmp.mysm.hibernate.core.system.accessgroup.HAccessGroupDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - [DATA MANAGER FACTORY] unknown: 5: com.cmp.mysm.hibernate.systemaudit.HSystemAuditDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 6: com.cmp.mysm.hibernate.datasource.database.HDatabaseDSDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 7: com.cmp.mysm.hibernate.datasource.ldap.HLDAPDatasourceDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 8: com.cmp.mysm.hibernate.sessionmanager.HSessionManagerDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 9: com.cmp.mysm.hibernate.sessionmanager.HASMDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 10: com.cmp.mysm.hibernate.digestconf.HDigestConfDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 11: com.cmp.mysm.hibernate.radius.clientprofile.HClientProfileDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - [DATA MANAGER FACTORY] unknown: 12: com.cmp.mysm.hibernate.externalsystem.HExternalSystemInterfaceDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 13: com.cmp.mysm.hibernate.servermgr.drivers.HDriverDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 14: com.cmp.mysm.hibernate.servermgr.drivers.subscriberprofile.database.HDatabaseSubscriberProfileDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 15: com.cmp.mysm.hibernate.servermgr.service.HServiceDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 16: com.cmp.mysm.hibernate.servicepolicy.auth.HAuthServicePoilcyDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 17: com.cmp.mysm.hibernate.servicepolicy.acct.HAcctServicePoilcyDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 18: com.cmp.mysm.hibernate.servicepolicy.dynauth.HDynAuthServicePoilcyDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 19: com.cmp.mysm.hibernate.servermgr.server.HServerDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 20: com.cmp.mysm.hibernate.servermgr.service.HServiceDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 21: com.cmp.mysm.hibernate.servermgr.plugin.HPluginDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 22: com.cmp.mysm.hibernate.rm.ippool.HIPPoolDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 23: com.cmp.mysm.hibernate.servermgr.eap.HEAPConfigDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 24: com.cmp.mysm.hibernate.servermgr.alert.HAlertListenerDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 25: com.cmp.mysm.hibernate.servermgr.gracepolicy.HGracePolicyDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 26: com.cmp.mysm.hibernate.radius.clientprofile.HClientProfileDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 27: com.cmp.mysm.hibernate.radius.dictionary.HDictionaryDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 28: com.cmp.mysm.hibernate.radius.policies.accesspolicy.HAccessPolicyDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 29: com.cmp.mysm.hibernate.radius.policies.radiuspolicy.HRadiusPolicyDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 30: com.cmp.mysm.hibernate.radius.radtest.HRadiusTestDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 31: com.cmp.mysm.hibernate.radius.bwlist.HBWListBLManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - [DATA MANAGER FACTORY] unknown: 32: com.cmp.mysm.hibernate.rm.concurrentloginpolicy.HConcurrentLoginPolicyDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 33: com.cmp.mysm.hibernate.wsconfig.HWebServiceConfigDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 34: com.cmp.mysm.hibernate.diameter.dictionary.HDictionaryDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 35: com.cmp.mysm.hibernate.servicepolicy.diameter.naspolicy.HDiameterNASPolicyDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 36: com.cmp.mysm.hibernate.servicepolicy.diameter.creditcontrolpolicy.HCreditControlPolicyDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 37: com.cmp.mysm.hibernate.servicepolicy.diameter.eappolicy.HEAPPolicyDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - [DATA MANAGER FACTORY] unknown: 38: com.cmp.mysm.hibernate.servermgr.drivers.HDiameterDriverDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 39: com.cmp.mysm.hibernate.servermgr.transmapconf.HTranslationMappingConfDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 40: com.cmp.mysm.hibernate.diameter.diameterpolicy.HDiameterPolicyDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 41: com.cmp.mysm.hibernate.servicepolicy.rm.cgpolicy.HCGPolicyDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 42: com.cmp.mysm.hibernate.reports.userstat.HUserStatisticsDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 43: com.cmp.mysm.hibernate.diameter.routingconf.HDiameterRoutingConfDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 44: com.cmp.mysm.hibernate.diameter.diameterpeerprofile.HDiameterPeerProfileDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 45: com.cmp.mysm.hibernate.diameter.diameterpeer.HDiameterPeerDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 46: com.cmp.mysm.hibernate.core.base.HGenericDataManager
  [May 13, 2013 12:48:24] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: *.
  [May 13, 2013 12:48:24] [INFO] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: Data Manager was initialized successfully.
  [May 13, 2013 12:48:29] [ERROR] [0.0.0.0] - unknown [CONFIG MANAGER]: error during the Configuration Manager operation, reason: failed to open the connection
  [May 13, 2013 12:48:29] [TRACE] [0.0.0.0] - unknown [CONFIG MANAGER] com.cmp.mysm.datamanager.DataManagerException: failed to open the connection
  at com.cmp.mysm.hibernate.core.system.systemparameter.HSystemParameterDataManager.getList (HSystemParameterDataManager.java:45)
  at com.cmp.mysm.blmanager.core.system.systemparameter.SystemParameterBLManager.getList (SystemParameterBLManager.java:71)
  at com.cmp.mysm.web.core.system.cache.ConfigManager.init (ConfigManager.java:47)
  at com.cmp.mysm.web.core.system.servlet.myServlet.init (myServlet.java:27)
  at javax.servlet.GenericServlet.init(GenericServlet.java:212)
  at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1206)
  at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1026)
  at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4421)
  at org.apache.catalina.core.StandardContext.start(StandardContext.java:4734)
  at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
  at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
  at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
  at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
  at org.apache.catalina.core.StandardService.start(StandardService.java:525)
  at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
  at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:597)
  at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
  at org.apache.catalina.startup.Bootstrap.main (Bootstrap.java:414)
  Caused by: org.hibernate.exception.GenericJDBCException: failed to open the connection
  at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:140)
  at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:128)
  at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
  at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:52)
  at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:449)
  at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:167)
  at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:161)
  at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1596)
  at org.hibernate.loader.Loader.doQuery(Loader.java:717)
  at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:270)
  at org.hibernate.loader.Loader.doList(Loader.java:2294)
  at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2172)
  at org.hibernate.loader.Loader.list(Loader.java:2167)
  at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:119)
  at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1706)
  at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:347)
  at com.cmp.mysm.hibernate.core.system.systemparameter.HSystemParameterDataManager.getList (HSystemParameterDataManager.java:43)
  ... 21 more
  Caused by: java.sql.SQLException: an attempt by a client to fund a connection has expired.
  at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:106)
  at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:65)
  at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:527)
  at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:128)
  at org.hibernate.connection.C3P0ConnectionProvider.getConnection(C3P0ConnectionProvider.java:78)
  at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:446)
  ... more than 33
  Caused by: com.mchange.v2.resourcepool.TimeoutException: a client has expired while waiting to acquire a resource of com.mchange.v2.resourcepool.BasicResourcePool@47503458--timeout to awaitAvailable()
  at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1317)
  at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:557)
  at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:477)
  at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:525)
  ... 36 more
  
  May 13, 2013 12:48:29 AM org.apache.catalina.startup.HostConfig deployDescriptor
  NEWS: Deployment descriptor configuration host - manager .xml
  May 13, 2013 12:48:29 AM org.apache.catalina.startup.HostConfig deployDescriptor
  NEWS: Deployment configuration descriptor manager.xml
  May 13, 2013 12:48:29 AM org.apache.catalina.startup.HostConfig deployDirectory
  NEWS: Deployment of the directory docs web application
  May 13, 2013 12:48:29 AM org.apache.catalina.startup.HostConfig deployDirectory
  INFO: Examples of Directory deployment web application
  May 13, 2013 12:48:29 AM org.apache.catalina.startup.HostConfig deployDirectory
  INFO: Deploy the web application ROOT directory
  May 13, 2013 org.apache.coyote.http11.Http11Protocol start 12:48:29 AM
  INFO: From Coyote HTTP/1.1 on http-8080
  May 13, 2013 12:48:30 AM org.apache.jk.common.ChannelSocket init
  INFO: JK: ajp13 listening on /0.0.0.0:8009
  May 13, 2013 12:48:30 hours departure from org.apache.jk.server.JkMain
  INFO: Jk running ID = time 0 = 0/15 config = null
  May 13, 2013 12:48:30 hours departure from org.apache.catalina.startup.Catalina
  INFO: Starting the server in 16222 ms
  
  Some time Tomcat to connect to the database*.
  [May 13, 2013 10:02:29] [INFO] [0.0.0.0] - [DATA MANAGER FACTORY] unknown: init() Called.
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: adding the data manager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: *.
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 1: com.cmp.mysm.hibernate.core.system.staff.HStaffDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 2: com.cmp.mysm.hibernate.core.system.systemparameter.HSystemParameterDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 3: com.cmp.mysm.hibernate.core.system.profilemanagement.HProfileDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 4: com.cmp.mysm.hibernate.core.system.accessgroup.HAccessGroupDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - [DATA MANAGER FACTORY] unknown: 5: com.cmp.mysm.hibernate.systemaudit.HSystemAuditDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 6: com.cmp.mysm.hibernate.datasource.database.HDatabaseDSDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 7: com.cmp.mysm.hibernate.datasource.ldap.HLDAPDatasourceDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 8: com.cmp.mysm.hibernate.sessionmanager.HSessionManagerDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 9: com.cmp.mysm.hibernate.sessionmanager.HASMDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 10: com.cmp.mysm.hibernate.digestconf.HDigestConfDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 11: com.cmp.mysm.hibernate.radius.clientprofile.HClientProfileDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - [DATA MANAGER FACTORY] unknown: 12: com.cmp.mysm.hibernate.externalsystem.HExternalSystemInterfaceDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 13: com.cmp.mysm.hibernate.servermgr.drivers.HDriverDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 14: com.cmp.mysm.hibernate.servermgr.drivers.subscriberprofile.database.HDatabaseSubscriberProfileDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 15: com.cmp.mysm.hibernate.servermgr.service.HServiceDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 16: com.cmp.mysm.hibernate.servicepolicy.auth.HAuthServicePoilcyDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 17: com.cmp.mysm.hibernate.servicepolicy.acct.HAcctServicePoilcyDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 18: com.cmp.mysm.hibernate.servicepolicy.dynauth.HDynAuthServicePoilcyDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 19: com.cmp.mysm.hibernate.servermgr.server.HServerDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 20: com.cmp.mysm.hibernate.servermgr.service.HServiceDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 21: com.cmp.mysm.hibernate.servermgr.plugin.HPluginDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 22: com.cmp.mysm.hibernate.rm.ippool.HIPPoolDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 23: com.cmp.mysm.hibernate.servermgr.eap.HEAPConfigDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 24: com.cmp.mysm.hibernate.servermgr.alert.HAlertListenerDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 25: com.cmp.mysm.hibernate.servermgr.gracepolicy.HGracePolicyDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 26: com.cmp.mysm.hibernate.radius.clientprofile.HClientProfileDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 27: com.cmp.mysm.hibernate.radius.dictionary.HDictionaryDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 28: com.cmp.mysm.hibernate.radius.policies.accesspolicy.HAccessPolicyDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 29: com.cmp.mysm.hibernate.radius.policies.radiuspolicy.HRadiusPolicyDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 30: com.cmp.mysm.hibernate.radius.radtest.HRadiusTestDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 31: com.cmp.mysm.hibernate.radius.bwlist.HBWListBLManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - [DATA MANAGER FACTORY] unknown: 32: com.cmp.mysm.hibernate.rm.concurrentloginpolicy.HConcurrentLoginPolicyDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 33: com.cmp.mysm.hibernate.wsconfig.HWebServiceConfigDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 34: com.cmp.mysm.hibernate.diameter.dictionary.HDictionaryDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 35: com.cmp.mysm.hibernate.servicepolicy.diameter.naspolicy.HDiameterNASPolicyDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 36: com.cmp.mysm.hibernate.servicepolicy.diameter.creditcontrolpolicy.HCreditControlPolicyDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 37: com.cmp.mysm.hibernate.servicepolicy.diameter.eappolicy.HEAPPolicyDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - [DATA MANAGER FACTORY] unknown: 38: com.cmp.mysm.hibernate.servermgr.drivers.HDiameterDriverDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 39: com.cmp.mysm.hibernate.servermgr.transmapconf.HTranslationMappingConfDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 40: com.cmp.mysm.hibernate.diameter.diameterpolicy.HDiameterPolicyDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 41: com.cmp.mysm.hibernate.servicepolicy.rm.cgpolicy.HCGPolicyDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 42: com.cmp.mysm.hibernate.reports.userstat.HUserStatisticsDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 43: com.cmp.mysm.hibernate.diameter.routingconf.HDiameterRoutingConfDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 44: com.cmp.mysm.hibernate.diameter.diameterpeerprofile.HDiameterPeerProfileDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 45: com.cmp.mysm.hibernate.diameter.diameterpeer.HDiameterPeerDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: 46: com.cmp.mysm.hibernate.core.base.HGenericDataManager
  [May 13, 2013 10:02:29] [DEBUG] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: *.
  [May 13, 2013 10:02:29] [INFO] [0.0.0.0] - unknown [DATA MANAGER FACTORY]: Data Manager was initialized successfully.
  In data manager: 1
  In data manager: 2
  In data manager: 19
  In data manager: 20
  In data manager: 21
  In data manager: 22
  In data manager: 23
  In data manager: 24
  In data manager: 3
  In data manager: 4
  May 13, 2013 10:02:30 org.apache.catalina.startup.HostConfig deployDescriptor
  NEWS: Deployment configuration descriptor manager.xml
  May 13, 2013 10:02:30 org.apache.catalina.startup.HostConfig deployDescriptor
  NEWS: Deployment descriptor configuration host - manager .xml
  May 13, 2013 10:02:30 org.apache.catalina.startup.HostConfig deployDirectory
  NEWS: Deployment of the directory docs web application
  May 13, 2013 10:02:30 org.apache.catalina.startup.HostConfig deployDirectory
  INFO: Deploy the web application ROOT directory
  May 13, 2013 10:02:30 org.apache.catalina.startup.HostConfig deployDirectory
  INFO: Examples of Directory deployment web application
  10:02:30 org.apache.coyote.http11.Http11Protocol start may 13, 2013
  INFO: From Coyote HTTP/1.1 on http-8080
  May 13, 2013 10:02:30 org.apache.jk.common.ChannelSocket init
  INFO: JK: ajp13 listening on /0.0.0.0:8009
  Org.apache.jk.server.JkMain 10:02:30 starting May 13, 2013
  INFO: Jk running ID = time 0 = 0/14 config = null
  Org.apache.catalina.startup.Catalina 10:02:30 starting May 13, 2013
  INFO: 6176 SP server startup
  
  
  But even once, when we try to stop and start then same problem occurred that we are not able to connect to the database
  
  Thanks in advanace

  We had solved the problem of our self
  to disable the setting of listener_network

  We also increase the connection timeout on the demand side

• Question about the keep buffer Pool and the Recycle Buffer Pool

  What will be the Pool of buffers to keep and recycle Buffer Pool contains actually in the Database Buffer Cache, especially what kind of objects? I know the definitions, but need to know the practical aspects to their topic.

  918868 wrote:
  What will be the Pool of buffers to keep and recycle Buffer Pool contains actually in the Database Buffer Cache, especially what kind of objects? I know the definitions, but need to know the practical aspects to their topic.

  When all else fails, read the Fine

  http://docs.Oracle.com/CD/E11882_01/server.112/e16638/memory.htm#PFGRF94285

• How to disable the hidden buffer?

  Hello
  
  How can I disable the cache Oracle?
  
  I m set db_cache_size = 0, but to do something more?
  
  Concerning

  You can't disable the buffer cache.

  You can rinse with an ALTER SYSTEM FLUSH BUFFER_CACHE
  This does not prevent the blocks still be cached in the OS file system Cache or the Cache of SAN so you can still see reading as being "very fast" if they are served from one of these caches.

  Hemant K Collette

• What is the difference between the CACHE and the PIN code?

  What is the difference between the CACHE and the PIN code?

  Cached, it's when you specify CACHE as part of a CREATE or ALTER an object to say Oracle when the blocks are retrieved this object these blocks should be put to the most recently used end of the LRU (least recently used) list in the buffer cache when a full table scan. Under normal circumstances, when the blocks are retrieved in memory, in that they are placed least recently used end of the LRU list. This means that the data that was most recently viewed typically will remain available in the cache buffers for awhile. Therefore, subsequent runs of the same query should find these blocks already in the buffer cache and not to recover disk again. When you use the CACHE, you say you want to put the blocks retrieved at the end of the list, which means that they will be the first blocks "aged" off the buffer cache when more space is needed.
  A few reasons to use the CACHE are:
  (1) for tables of small (only a few blocks that must be read to retrieve the entire table).
  (2) when you do a select statement returns a huge amount of data, and you do not necessarily have if wait for the query to run any time soon. In both cases, you give Oracle an opportunity to eliminate the blocks quickly to make room for more 'necessary' blocks instead of having to follow in the LRU list.

  Pinning is when you want to keep the objects in memory and to prevent them from being aged by the normal mechanism of the LRU. You use the INVALIDHTOMEH to "pin" PL/SQL code in memory, so that users are not experiencing intermittent slowdowns when code gets years out of the shared pool and must be recharged.

  The bottom line is that caching can blocks be moved quickly while pinning retains the information in memory to avoid the re-loads.