You can try to delete and recreate the object.
MY guess is you will not be able to do that.
We just had a lone thread on here with a similiar problem and RCLSTG was the only way out.
I have seen this before on a few systems. The object in question trying to have journaling started was not damaged, but due to a <b>previous</b> damaged object journaling could not be started on the object.
When I last look at this problem, I think the journal recievers recycle the numbers and remembers the problem sequence number, or it hits a few bad ones. The way around this for me was to change the journal reciver (six time in about 15 mins for me) as the error returned. it then got past its problem and journaling was then OK and remained active.
It still pops up once a year as no down time availble for a RCLSTG but changing journal reciever still fixes it