| Title: | The Replication Option for Rdb |
| Notice: | Product renamed to Replication Option for Rdb |
| Moderator: | BROKE::PROTEAU |
| Created: | Wed Mar 02 1994 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 287 |
| Total number of notes: | 1231 |
hi all,
the "$RMU/CLOSE/ABORT/WAIT DDAL$TRANSFER_DATABASE" in DDAL$STOP_TR_MON.COM
generate close database cluster wide.
I have a cluster with 2 vax. The first system perform @DDAL$STOP_TR_MON.COM,
the 2nd receive:
15-APR-1997 07:48:30.53 - received cluster-wide CLOSE FORCEX request
- for database "DSA0:[SYS3.SYSCOMMON.SYSEXE]DDAL$TR_DB.RDB;1"
- starting forced-exit shutdown of database "DSA0:[SYS3.SYSCOMMON.SYSEXE]DDAL
- "%RDMS-F-OPERCLOSE, database operator requested database shutdown"
- sending image force exit to process 6080022C
- database shutdown waiting for active users to terminate
after few second the ROR monitor in then 2nd system is OFF.
Why?
I suppose that is "expected behaviour" but is "mandatory"?
Why the ROR shutdown on the 2nd node should be invasive on the first node?
ciao
GIovanni
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 279.1 | Fixed in version 7.0 | BROKE::PROTEAU | Jean-Claude Proteau | Tue Apr 15 1997 12:17 | 11 |
Giovanni,
The answer, from my point of view, is that it shouldn't. That is why I
fixed this in version 7.0 of the Replication Option. If it were a
simple correction, we'ld have made the change in version 6.0 as well,
but ...
Ciao,
Claude
| |||||
| 279.2 | Ok... | itvms1.it.oracle.com::GTACCHIN | Giovanni Tacchini | Tue Apr 15 1997 12:28 | 5 |
thank, ciao GIovanni | |||||