| Title: | Oracle Rdb - Still a strategic database for DEC on Alpha AXP! |
| Notice: | RDB_60 is archived, please use RDB_70 .. |
| Moderator: | NOVA::SMITHI SON |
| Created: | Fri Mar 18 1994 |
| Last Modified: | Fri May 30 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5118 |
| Total number of notes: | 28246 |
CT has been truncating the snapshots and checking who was stalling on
writing. All he caught was two applications that should be writing
these areas and who were in and out and committed. They are not hanging
arround.
They have no long read transactions either. Okay it is his word only,
but this is an experienced shop and these issues started with 7.0-00 it
seems.
Going back to the truncated snapshot files. Each time the write
application is used the snapshot extends. It looks like they never get
to reuse the space. Is there any reasonable cause for this? What are
they doing wrong that we need to fix? And this is not just trival stuff
either. Since 7.0 they grow snapshot files each day (complete DB
shutdown each night) that are typically 5 times the size of the entire
DB.
None of these problems had shown up in testing, even though this site
was a field test site for 7.0. They are seeing similar, although not so
extreme behaviour on other 7.0 DBs.
Thanks for the help so far...
Colin
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5087.1 | HOTRDB::PMEAD | Paul, [email protected], 719-577-8032 | Thu Feb 27 1997 17:43 | 4 | |
Are they using any new 7.0 features, like Record Cache, for example?
I would say that it is time to enter a BUG if this is significantly
impacting the customer.
| |||||
| 5087.2 | There must be an old transaction | svrav1.au.oracle.com::MBRADLEY | I was dropped on my head as a baby. What's your excuse? | Mon Mar 03 1997 17:03 | 6 |
Use RMU to get the TSN of all transactions. Find the lowest TSN. What is that process doing, and how does that TSN compare to the highest TSN? G'day, Mark. | |||||