Discussion:
dump problem: "there was activity on database since last load"
(too old to reply)
Martin Alexander
2012-06-06 08:11:47 UTC
Permalink
hello,
our Sybase ASE 15.5 have a problem with creating a transaction log. The random time it happens that the transaction log created on the primary database is unable to load at the standby database (which is in the offline state!!).
error message>
----------------
Msg 4306, Level 16, State 1
There was activity on database since last load, unable to load. Must
restart load sequence with the load database to continue.
----------------

does anyone have any idea how to fix it?
b***@msn.com
2012-06-08 15:48:43 UTC
Permalink
On Jun 6, 2:11 am, Martin Alexander
Post by Martin Alexander
hello,
our Sybase ASE 15.5 have a problem with creating a transaction log. The random time it happens that the transaction log created on the primary database is unable to load at the standby database (which is in the offline state!!).
error message>
----------------
Msg 4306, Level 16, State 1
There was activity on database since last load, unable to load. Must
restart load sequence with the load database to continue.
----------------
does anyone have any idea how to fix it?
Are you on 15.5 GA? There was a bug, CR 611164, fixed in 15.5 ESD 1,
that would
sporadically result in 4306 errors when the database was created on
devices using
direct io.

-bret
Martin Alexander
2012-06-21 11:06:11 UTC
Permalink
Are you on 15.5 GA?  There was a bug, CR 611164, fixed in 15.5 ESD 1,
that would
sporadically result in 4306 errors when the database was created on
devices using
direct io.
-bret
Hi Bret,

we use 15.5/EBF 17340 (NO ESD). I try to install the update.

BTW, where is written that the CR 611164 was fixed in ESD 1?
http://www.sybase.com/detail?id=1067335

http://search.sybase.com/kbx/changerequests?bug_id=611164

thanks
b***@sybase.com
2012-06-25 16:24:26 UTC
Permalink
Post by Martin Alexander
BTW, where is written that the CR 611164 was fixed in ESD 1?
http://www.sybase.com/detail?id=1067335
http://search.sybase.com/kbx/changerequests?bug_id=611164
thanks
I don't think the public website connects the dots. You can
see that 611164 is marked closed as a duplicate of another
CR, but not which CR that was or what versions it was fixed in.
I can see from our internal (Sybase) bugs database what 611164
was marked a duplicate of CR 534014. Unfortunately the
public page for that CR isn't showing the exact versions it was fixed
in.

Cheers,
-bret
Post by Martin Alexander
Are you on 15.5 GA?  There was a bug, CR 611164, fixed in 15.5 ESD 1,
that would
sporadically result in 4306 errors when the database was created on
devices using
direct io.
-bret
Hi Bret,
we use 15.5/EBF 17340 (NO ESD). I try to install the update.
BTW, where is written that the CR 611164 was fixed in ESD 1?
http://www.sybase.com/detail?id=1067335
http://search.sybase.com/kbx/changerequests?bug_id=611164
thanks
Are you on 15.5 GA?  There was a bug, CR 611164, fixed in 15.5 ESD 1,
that would
sporadically result in 4306 errors when the database was created on
devices using
direct io.
-bret
Hi Bret,
we use 15.5/EBF 17340 (NO ESD). I try to install the update.
BTW, where is written that the CR 611164 was fixed in ESD 1?
http://www.sybase.com/detail?id=1067335
http://search.sybase.com/kbx/changerequests?bug_id=611164
thanks
Loading...