Rocket U2 | UniVerse & UniData

Blinks. Our product uses the Universe database with Pick Flavored account running on various Windows OS platforms. What, if anything, can be done to reduce the number of file  blinks that we are seeing? Three causes that we've identified so far are: Power failure, No more disk space, Anti-virus. 

Are any UV versions (or Windows versions) more susceptible than others to Blinks?

Thanks in advance for your inputs.

Blinks. Our product uses the Universe database with Pick Flavored account running on various Windows OS platforms. What, if anything, can be done to reduce the number of file  blinks that we are seeing? Three causes that we've identified so far are: Power failure, No more disk space, Anti-virus. 

Are any UV versions (or Windows versions) more susceptible than others to Blinks?

Thanks in advance for your inputs.

What are the other common causes of blinks and how can we minimize the risks? Will poorly sized files increase the chances of getting a blink on the file?

Blinks. Our product uses the Universe database with Pick Flavored account running on various Windows OS platforms. What, if anything, can be done to reduce the number of file  blinks that we are seeing? Three causes that we've identified so far are: Power failure, No more disk space, Anti-virus. 

Are any UV versions (or Windows versions) more susceptible than others to Blinks?

Thanks in advance for your inputs.

Blinks. Our product uses the Universe database with Pick Flavored account running on various Windows OS platforms. What, if anything, can be done to reduce the number of file  blinks that we are seeing? Three causes that we've identified so far are: Power failure, No more disk space, Anti-virus. 

Are any UV versions (or Windows versions) more susceptible than others to Blinks?

Thanks in advance for your inputs.

------------------------------
Gil Steidle
DEV
DDI System Inc
brick NJ US
------------------------------

Blinks. Our product uses the Universe database with Pick Flavored account running on various Windows OS platforms. What, if anything, can be done to reduce the number of file  blinks that we are seeing? Three causes that we've identified so far are: Power failure, No more disk space, Anti-virus. 

Are any UV versions (or Windows versions) more susceptible than others to Blinks?

Thanks in advance for your inputs.

This is correct.  We here have a task in our Universe scheduler, that every week tells us how much disk space has been used and left.  And emails that to the sysadmin.

Blinks. Our product uses the Universe database with Pick Flavored account running on various Windows OS platforms. What, if anything, can be done to reduce the number of file  blinks that we are seeing? Three causes that we've identified so far are: Power failure, No more disk space, Anti-virus. 

Are any UV versions (or Windows versions) more susceptible than others to Blinks?

Thanks in advance for your inputs.

What is a reliable method to identify files with blinks proactively? Will a simple SELECT or COUNT be effective? I'm thinking to make a scheduled job to check our files for corruption.

This is correct.  We here have a task in our Universe scheduler, that every week tells us how much disk space has been used and left.  And emails that to the sysadmin.

Blinks. Our product uses the Universe database with Pick Flavored account running on various Windows OS platforms. What, if anything, can be done to reduce the number of file  blinks that we are seeing? Three causes that we've identified so far are: Power failure, No more disk space, Anti-virus. 

Are any UV versions (or Windows versions) more susceptible than others to Blinks?

Thanks in advance for your inputs.

What is a reliable method to identify files with blinks proactively? Will a simple SELECT or COUNT be effective? I'm thinking to make a scheduled job to check our files for corruption.

This is correct.  We here have a task in our Universe scheduler, that every week tells us how much disk space has been used and left.  And emails that to the sysadmin.

Blinks. Our product uses the Universe database with Pick Flavored account running on various Windows OS platforms. What, if anything, can be done to reduce the number of file  blinks that we are seeing? Three causes that we've identified so far are: Power failure, No more disk space, Anti-virus. 

Are any UV versions (or Windows versions) more susceptible than others to Blinks?

Thanks in advance for your inputs.

If you wish to use the SELECT or COUNT approach, include a WITH clause that will not select any records. Example: WITH PositiveNumericField < 0.

This ensures the record is read, including any oversize record blocks. Otherwise, this just reads the primary group chain record blocks and ID. 

The most robust approach would use fixtool.

What is a reliable method to identify files with blinks proactively? Will a simple SELECT or COUNT be effective? I'm thinking to make a scheduled job to check our files for corruption.

This is correct.  We here have a task in our Universe scheduler, that every week tells us how much disk space has been used and left.  And emails that to the sysadmin.

Blinks. Our product uses the Universe database with Pick Flavored account running on various Windows OS platforms. What, if anything, can be done to reduce the number of file  blinks that we are seeing? Three causes that we've identified so far are: Power failure, No more disk space, Anti-virus. 

Are any UV versions (or Windows versions) more susceptible than others to Blinks?

Thanks in advance for your inputs.

What is a reliable method to identify files with blinks proactively? Will a simple SELECT or COUNT be effective? I'm thinking to make a scheduled job to check our files for corruption.

This is correct.  We here have a task in our Universe scheduler, that every week tells us how much disk space has been used and left.  And emails that to the sysadmin.

Blinks. Our product uses the Universe database with Pick Flavored account running on various Windows OS platforms. What, if anything, can be done to reduce the number of file  blinks that we are seeing? Three causes that we've identified so far are: Power failure, No more disk space, Anti-virus. 

Are any UV versions (or Windows versions) more susceptible than others to Blinks?

Thanks in advance for your inputs.

Hi Gil,

For us badly sized files has always been the biggest culprit for UniVerse file corruption, that and dynamic files which seem to be susceptible to corruption following system failures.

We have developed our own daily FILE.STAT suite that performs the FILE.STAT on each file on a daily basis overnight, we log and report any Blink errors identified, but with the robustness of UNIX system nowadays we rarely see them. We maintain a history of each file so that we can try to predict forward growth of each file a have the ability to automatically resize files or manually manage the process.

Saying that, there is the Rocket provided ACCOUNT.FILE.STATS which logs each time it's run to a file called STAT.FILE with an internal date/time stamp ID, examining the last run for each file would identify both if the FILE.STAT failed (Blink error) by checking the FILE.STAT attributes (they will not be populated) and as a bonus this also enables you to check that your files are sized correctly so you can remediate as appropriate.

Sample table below below shows the omission of the number of Records (Items) within the file, the first two entries were whilst a Blink error existed on a test file.

SORT STAT.FILE BY @ID FILENAME.LONG FILETYPE FILEMOD FILESEP FILESIZE RECORDS 17:37:06  21-05-24  PAGE 1
ID..................... File Name..................... Type Mod..... Sep File....... Record.
                                                                         Size....... Count..

20596*59877*0012        DUFF                             18      101   2      104448
20596*60074*0012        DUFF                             18      101   2      104448
20596*60200*0012        DUFF                             18      101   2      104448     415
20596*60361*0012        DUFF                             18      101   2      104448     414
20596*60489*0012        DUFF                             18      101   2      104448     414
20596*60881*0012        DUFF                             18      101   2     7135232   58913
20596*61027*0012        DUFF                             18      101   2     7135232   58913
20596*63155*0012        DUFF                             18      101   2      104448       0

Regards

MArk 

What is a reliable method to identify files with blinks proactively? Will a simple SELECT or COUNT be effective? I'm thinking to make a scheduled job to check our files for corruption.

This is correct.  We here have a task in our Universe scheduler, that every week tells us how much disk space has been used and left.  And emails that to the sysadmin.

Blinks. Our product uses the Universe database with Pick Flavored account running on various Windows OS platforms. What, if anything, can be done to reduce the number of file