Thread: SC4.0.10 & SC4.0.10.1

Announcement from Peregrine:



It is not recommended to upgrade to SC4.0.10 and 4.0.10.1 because of issues with hot backup.



Wait for SC4.0.10.2



Additional info:



***From Peregrine Support***



I have included a write-up regarding the 4.0.10 release, we suggest that you

either wait until 4.0.12 or go back to 4.09 or below. Our Support

Administration Group sent out an email to all customers that requested

4.0.10, so an email should have been sent to notify you of the issue and I

apologize if you did not receive the email. Please let me know if you have

any additional questions and thank you for your understanding.



S Y M P T O M



24x7 stoplogging function can terminate abnormally in ServiceCenter 4.0.10

and 4.0.10.1, causing possible data loss.



C A U S E



The ServiceCenter 24 by 7 backup utility (24x7) allows installations to

backup their P4 scdb.db* files without any downtime. Users can continue to

work as normal during the backup process. The utility is started with the

command:



Scenter -startlogging



Once this command completes, no further writing occurs to the scdb.db*

files, and therefore they can be backed up to another device. Data that

would have been written to this file is instead written to a log file

(scdb.pflog) and an index to the entries written to this log file is

maintained in shared storage.



After the backup has been completed, the backup utility is stopped with the

command:



Scenter -stoplogging



This command takes the data from shared storage and from scdb.pflog, writes

the data to the scdb.db* files, then exits.



However, in ServiceCenter 4.0.10 and 4.0.10.1, the stoplogging function has

a high probability of abnormal termination. If an abnormal termination

occurs, there is no way to correct the problem. Other attempts to stop

logging are not allowed because ServiceCenter believes it is already

running. If abnormal termination occurs, the only recourse is to stop the

system immediately to prevent any further updates, then restore the backup

copy of the data that was just taken. This means the loss of all updates

that occurred after issuing the -scenter startlogging command.



W O R K A R O U N D / F I X



Because of critical errors and the potential for lost data, ServiceCenter

4.0.10 and 4.0.10.1 should not be used. ServiceCenter 4.0.10.2 will include

a fix for this problem.



[Edited by admin on 02-04-2002 at 21:21 GMT]

Wow... thats hard!!!

It's even worse. As it turns out, Support/Level2 will not (effectively) support releases 4.0.10 and .10.1, even if issues arise not relating to the official error, being the Hot Backup functionality.



So, if you have started working with 4.0.10, bad luck. I tried to raise an application issue (RAD, so unaffeced by .10 release), refed that it also occurs on a 4.0.7 system, and got it returned...as the error is with 4.0.10 and that's been recalled!