G
George Potemkin
Guest
> Is there a smart way to close a promon session left running in another OS session, other than killing its process? No. But try to get a protrace file first. BTW, _mprshut processes (including promon) are "fragile" to the SIGUSR1 signal. Under the normal circumstances on the receiving the signal they generate protrace file but then they are terminated. > Is there a risk to damage a database by kiling a promon process? I guess that in our case the promon sessions (more than one) hung because they all are waiting for some database resource. So killing them will crash the database. Does new promon session will hang as well? Do you start them with the -NL? Do you change working area to 3. Primary Recovery Area?
Continue reading...
Continue reading...