Progress_Learner
Member
Hello All,
During a planned downtime activity, we were not able to start our database due to the error messages of “wrong creation date of AI extents”. Below are DB logs for the same:
We had to disable OpenEdge replication and AI to start the database. We recreated replication server after that and currently replication is in sync with LIVE.
It’s very strange for me that AI extent creation date in DB logs is Jan 1 01:00:00 1970 and this message is for all AI extents. Please help to find the cause and suggest what to do if this issue comes again.
Progress Version: 10.2B08
OS Version: Red Hat Enterprise Linux 6.10 64 Bit
Please suggest.
Regards,
Learner
During a planned downtime activity, we were not able to start our database due to the error messages of “wrong creation date of AI extents”. Below are DB logs for the same:
Code:
(9212) Extent /ai /db-name.a1 has the wrong creation date Thu Jan 1 01:00:00 1970,
(9216) Control Area has a creation date of Sat Nov 25 14:47:28 2017.
(605) Probable backup/restore error.
(9214) Creation date mismatch.
We had to disable OpenEdge replication and AI to start the database. We recreated replication server after that and currently replication is in sync with LIVE.
It’s very strange for me that AI extent creation date in DB logs is Jan 1 01:00:00 1970 and this message is for all AI extents. Please help to find the cause and suggest what to do if this issue comes again.
Progress Version: 10.2B08
OS Version: Red Hat Enterprise Linux 6.10 64 Bit
Please suggest.
Regards,
Learner