| Title: | DEC Rdb against the World |
| Moderator: | HERON::GODFRIND |
| Created: | Fri Jun 12 1987 |
| Last Modified: | Thu Feb 23 1995 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1348 |
| Total number of notes: | 5438 |
A customer who is not very technical told me that it was taking all
weekend for their batch Ingres job to run. There work around is to
unload the database to a batch file (this takes about 2 hours), run the
batch job, and reload the database (this takes about 3 hours).
I forgot to ask how big the database was. Does this sound unusually
slow when there is minimal activity on the system over the weekend?
Anyone else run into this? We are trying to get them to use ACMS
and/or convert to Rdb.
Patti
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1083.1 | NOVA::MOY | Michael G. Moy, Rdb/VMS Engineering | Mon Feb 10 1992 20:32 | 13 | |
Your question can't really be answered as it is too general, and we
have no description of the workload. They could have:
1) Design problems
2) Product problems
3) Application code problems
4) Or expected behaviour for the work with their hardware
configuration.
5) May need system tuning help.
It might be helpful to have an EIS consultant look at this. If a
remedial problem is suspected, then support (Ingres or us if it's
ULTRIX/SQL) could be contacted.
| |||||