Hi.
We have a Solaris system, running OE 11.7.10.
We have had a few occurrences in the past few months where the system has "hung up", database allowing no writes/reads.
Extents all ok, BI ok, AI's all set to variable length and plenty of AI extents available and empty.
At the point where the system beings unresponsive, AI management halts on the effected database.
It does not perform a switch after the normal 5minutes.
Current AI setup is archiving every 5minutes directly to a NFS mount storage, the exact same AI setup is in place on the other 6 databases that the system uses.
Checked log files etc, there's nothing in there that suggests anything strange, no mention of an AI stall etc etc which is how the behavior seems.
Only "fix" for the issue is to force close the effected database and then restart it, as soon as its restarted AI continues and switches every 5mins as usual.
Could archiving AI's directly to the NFS mount be causing this at all? Maybe at the exact second it goes to switch/archive it cannot write to the mount for some reason?
Thanks for any response.
We have a Solaris system, running OE 11.7.10.
We have had a few occurrences in the past few months where the system has "hung up", database allowing no writes/reads.
Extents all ok, BI ok, AI's all set to variable length and plenty of AI extents available and empty.
At the point where the system beings unresponsive, AI management halts on the effected database.
It does not perform a switch after the normal 5minutes.
Current AI setup is archiving every 5minutes directly to a NFS mount storage, the exact same AI setup is in place on the other 6 databases that the system uses.
Checked log files etc, there's nothing in there that suggests anything strange, no mention of an AI stall etc etc which is how the behavior seems.
Only "fix" for the issue is to force close the effected database and then restart it, as soon as its restarted AI continues and switches every 5mins as usual.
Could archiving AI's directly to the NFS mount be causing this at all? Maybe at the exact second it goes to switch/archive it cannot write to the mount for some reason?
Thanks for any response.