| Title: | SQL/Services Forum |
| Notice: | kits(3) ft info(7) QAR access (8) SPR access (10) |
| Moderator: | SQLSRV::MAVRIS |
| Created: | Thu Oct 13 1988 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2214 |
| Total number of notes: | 8586 |
Hi,
SQL/Services V7.0
VAX VMS V6.1
A customer of mine is seeing a service get shut down when its database
is closed.
What he does is close the database to do a backup. He just shuts the
database down without shutting down its service.
Users on the client end continue to try to make connections, which
means that the service still tries to attach to the database.
The service continues to try to attach, then becomes a failed service &
shuts itself down. The only way to get this service back is to restart
it.
In the sqs...disp.log he gets the error
%SQLSRV-F-EXECSTARTEXCEED, Max executor startup failures exceeded for
service.
In the previous version of SQL/Services he used, there didn't seem to
be a maximum number of retries, so shutting down the database wasn't a
problem.
He would rather have the same behaviour as before.
What can he do get it back?
Thanks,
Louise.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2177.1 | why? | M5::JBALOGH | Tue Mar 25 1997 16:31 | 6 | |
If the service is unusable, ie, the database is unavailable, wouldn't
it be better to shut down the service first? Why not just stop/restart
the service in his backup script? Especially if his users are banging
on it while the DB is down...
John
| |||||
| 2177.2 | ukvms3.uk.oracle.com::LWILES | Louise Wiles, UK Rdb support | Thu Apr 10 1997 08:38 | 16 | |