on 05-15-2016 4:47 PM
Hi,
In the past (sybase 12.5.4) , I was able to run 2 agents loading each one a transaction on a different database, now, under 15.7 sp63, it works for a little while and then my database gets status 384 or even worse.
The status is updatable and after a server restart everything goes back ok, but I cannot handle such situation, it there an open ticket on this on the next sybase server version ?
Thanks.
PS : Replication server is not an option, we use log shipping.
As the database is ending up marked suspect, I would expect there to be some error getting raised during the LOAD TRAN and sent to either the client (agent), the ASE erorrlog, or the backupserver errorlog. Identifying the issue is likely to be much easier if we know the details of the error that caused the database to be marked suspect. I don't find anything obvious based on the facts so far.
-bret
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.