hi guys,
we have sybsecurity database of data 512M and 1G. we also have sybsecurtity archive for the audit information. later last week i've been encountering logsegment full on archive database. archive database composed of 2G of data and 1G of log. there's also a trigger procedure that would fire to archive database once reach its threshold point. somehow i can't understand its behavior how archive db syslogs full. no options defined for both audit database.
the error log says that sybsecurity archive logsegment is full..
anyone has inputs, or even share on how do you handle this situation.
TIA
we have sybsecurity database of data 512M and 1G. we also have sybsecurtity archive for the audit information. later last week i've been encountering logsegment full on archive database. archive database composed of 2G of data and 1G of log. there's also a trigger procedure that would fire to archive database once reach its threshold point. somehow i can't understand its behavior how archive db syslogs full. no options defined for both audit database.
the error log says that sybsecurity archive logsegment is full..
anyone has inputs, or even share on how do you handle this situation.
TIA