Re: [U2] blink error?
I have not seen that in a long time. Used to occasionally get it in UniVerse on an AIX box. I think it stands for backward link (blink). Simply listing or selecting the file will fail when it hits the offending data. If you can detect the key that is failing, the simple solution used to be to try to copy the record to a temp file, delete the original record (which fixes the link), then copy it back. If that fails, you will likely need to run the fix file utility. Again, I have not seen this in 10 years or so, so my memory may be a little off. Good luck! JRI -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Holt, Jake Sent: Thursday, April 18, 2013 12:20 PM To: U2 Users List Subject: [U2] blink error? Never seen this error message before, no sure on the severity but I hope it's easy to fix: File 'E:\dbms\LIVE\DATAFLO/SHIPMENTS/SHIPMENTS': Computed blink of 0x765800 does not match expected blink of 0x765000! Detected within group starting at address 0x1068E000! Any input as to what I need to do to resolve it? Thanks, Jake Holt l samsill l Information Technology Director (817) 536 - 1906 x 217 l jh...@samsill.com www.samsill.com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] blink error?
Also check the size of the file (e.g. ls -l SHIPMENTS) - some systems have a 2GB limit per file Mark -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: Thursday, April 18, 2013 9:26 AM To: U2 Users List Subject: Re: [U2] blink error? I have not seen that in a long time. Used to occasionally get it in UniVerse on an AIX box. I think it stands for backward link (blink). Simply listing or selecting the file will fail when it hits the offending data. If you can detect the key that is failing, the simple solution used to be to try to copy the record to a temp file, delete the original record (which fixes the link), then copy it back. If that fails, you will likely need to run the fix file utility. Again, I have not seen this in 10 years or so, so my memory may be a little off. Good luck! JRI -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Holt, Jake Sent: Thursday, April 18, 2013 12:20 PM To: U2 Users List Subject: [U2] blink error? Never seen this error message before, no sure on the severity but I hope it's easy to fix: File 'E:\dbms\LIVE\DATAFLO/SHIPMENTS/SHIPMENTS': Computed blink of 0x765800 does not match expected blink of 0x765000! Detected within group starting at address 0x1068E000! Any input as to what I need to do to resolve it? Thanks, Jake Holt l samsill l Information Technology Director (817) 536 - 1906 x 217 l jh...@samsill.com www.samsill.com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] blink error?
I found what I believed was the offending shipment and copied it out and back, uvfixfile reported another id, I just deleted that shipment since it was open and can be regenerated. When I run UFF I get: UVFIXFILE SHIPMENTS Beginning TRACE of SHIPMENTS/SHIPMENTS. ERROR: Processing Primary group 3786, Overflow group 134428. Invalid group buffer chain at address 0x1068e000. Bad link to overflow buffer 134428. TRACE of SHIPMENTS/SHIPMENTS completed. Scanning overflow buffers. Scan complete. 104281 group(s) processed. 131647 group buffer(s) processed. 315627 record(s) processed. Number of data bytes = 197531808. Do I need to add an argument or something to actually fix the issue? -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: Thursday, April 18, 2013 11:26 AM To: U2 Users List Subject: Re: [U2] blink error? I have not seen that in a long time. Used to occasionally get it in UniVerse on an AIX box. I think it stands for backward link (blink). Simply listing or selecting the file will fail when it hits the offending data. If you can detect the key that is failing, the simple solution used to be to try to copy the record to a temp file, delete the original record (which fixes the link), then copy it back. If that fails, you will likely need to run the fix file utility. Again, I have not seen this in 10 years or so, so my memory may be a little off. Good luck! JRI -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Holt, Jake Sent: Thursday, April 18, 2013 12:20 PM To: U2 Users List Subject: [U2] blink error? Never seen this error message before, no sure on the severity but I hope it's easy to fix: File 'E:\dbms\LIVE\DATAFLO/SHIPMENTS/SHIPMENTS': Computed blink of 0x765800 does not match expected blink of 0x765000! Detected within group starting at address 0x1068E000! Any input as to what I need to do to resolve it? Thanks, Jake Holt l samsill l Information Technology Director (817) 536 - 1906 x 217 l jh...@samsill.com www.samsill.com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] blink error?
Nevermind. I remembered how to spell HELP -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: Thursday, April 18, 2013 11:26 AM To: U2 Users List Subject: Re: [U2] blink error? I have not seen that in a long time. Used to occasionally get it in UniVerse on an AIX box. I think it stands for backward link (blink). Simply listing or selecting the file will fail when it hits the offending data. If you can detect the key that is failing, the simple solution used to be to try to copy the record to a temp file, delete the original record (which fixes the link), then copy it back. If that fails, you will likely need to run the fix file utility. Again, I have not seen this in 10 years or so, so my memory may be a little off. Good luck! JRI -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Holt, Jake Sent: Thursday, April 18, 2013 12:20 PM To: U2 Users List Subject: [U2] blink error? Never seen this error message before, no sure on the severity but I hope it's easy to fix: File 'E:\dbms\LIVE\DATAFLO/SHIPMENTS/SHIPMENTS': Computed blink of 0x765800 does not match expected blink of 0x765000! Detected within group starting at address 0x1068E000! Any input as to what I need to do to resolve it? Thanks, Jake Holt l samsill l Information Technology Director (817) 536 - 1906 x 217 l jh...@samsill.com www.samsill.com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] blink error?
Sorry, I hate to keep bombing this with questions especially since this might be a totally unanswerable question, but generally is fixing the file a long process? It's a 268mb file and it's been running for 38 minutes. Is that typical? Just making sure it's not something that should have taken 38 seconds and there is something else getting in the way. Been sitting here since I started it: UVFIXFILE SHIPMENTS FIX Beginning TRACE of SHIPMENTS/SHIPMENTS. ERROR: Processing Primary group 3786, Overflow group 134428. Invalid group buffer chain at address 0x1068e000. Bad link to overflow buffer 134428. Attempting to unlink buffer at 0x1068e000. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: Thursday, April 18, 2013 11:26 AM To: U2 Users List Subject: Re: [U2] blink error? I have not seen that in a long time. Used to occasionally get it in UniVerse on an AIX box. I think it stands for backward link (blink). Simply listing or selecting the file will fail when it hits the offending data. If you can detect the key that is failing, the simple solution used to be to try to copy the record to a temp file, delete the original record (which fixes the link), then copy it back. If that fails, you will likely need to run the fix file utility. Again, I have not seen this in 10 years or so, so my memory may be a little off. Good luck! JRI -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Holt, Jake Sent: Thursday, April 18, 2013 12:20 PM To: U2 Users List Subject: [U2] blink error? Never seen this error message before, no sure on the severity but I hope it's easy to fix: File 'E:\dbms\LIVE\DATAFLO/SHIPMENTS/SHIPMENTS': Computed blink of 0x765800 does not match expected blink of 0x765000! Detected within group starting at address 0x1068E000! Any input as to what I need to do to resolve it? Thanks, Jake Holt l samsill l Information Technology Director (817) 536 - 1906 x 217 l jh...@samsill.com www.samsill.com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] blink error?
It must examine each group, looking at the forward and backward links of all the overflow. You could for example, pick a small file, and start a new session and run it on a small file of say 30 groups or 300 groups and time it. -Original Message- From: Holt, Jake jh...@samsill.com To: U2 Users List u2-users@listserver.u2ug.org Sent: Thu, Apr 18, 2013 10:23 am Subject: Re: [U2] blink error? Sorry, I hate to keep bombing this with questions especially since this might be a totally unanswerable question, but generally is fixing the file a long process? It's a 268mb file and it's been running for 38 minutes. Is that typical? Just making sure it's not something that should have taken 38 seconds and there is something else getting in the way. Been sitting here since I started it: UVFIXFILE SHIPMENTS FIX Beginning TRACE of SHIPMENTS/SHIPMENTS. ERROR: Processing Primary group 3786, Overflow group 134428. Invalid group buffer chain at address 0x1068e000. Bad link to overflow buffer 134428. Attempting to unlink buffer at 0x1068e000. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: Thursday, April 18, 2013 11:26 AM To: U2 Users List Subject: Re: [U2] blink error? I have not seen that in a long time. Used to occasionally get it in UniVerse on an AIX box. I think it stands for backward link (blink). Simply listing or selecting the file will fail when it hits the offending data. If you can detect the key that is failing, the simple solution used to be to try to copy the record to a temp file, delete the original record (which fixes the link), then copy it back. If that fails, you will likely need to run the fix file utility. Again, I have not seen this in 10 years or so, so my memory may be a little off. Good luck! JRI -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Holt, Jake Sent: Thursday, April 18, 2013 12:20 PM To: U2 Users List Subject: [U2] blink error? Never seen this error message before, no sure on the severity but I hope it's easy to fix: File 'E:\dbms\LIVE\DATAFLO/SHIPMENTS/SHIPMENTS': Computed blink of 0x765800 does not match expected blink of 0x765000! Detected within group starting at address 0x1068E000! Any input as to what I need to do to resolve it? Thanks, Jake Holt l samsill l Information Technology Director (817) 536 - 1906 x 217 l jh...@samsill.com www.samsill.com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] blink error?
Jake, You do not say what release of UV you are running but as of 9.5.1C you really should be using fixtool. See extracts from whitepaper below 1) Description fixtool is the replacement for UVFIXFILE (uvfixfile from the OS shell) and was introduced at 9.5.1C to support both 32-bit and 64-bit files. Initially it had a limited command line interface as it was intended to be used from the UVAdmin GUI client. When 9.6 was introduced, fixtool was enhanced with a few command line arguments to provide logging of the groups it traced, but could not be limited to a certain number of groups. By 9.6.2.x, it was further enhanced to permit group range traces, which no longer required exclusive access to the file. 11) Final details fixtool was originally designed to by used with the UniVerse administration client, then UVAdmin (pre-release 10) and now UniAdmin (release 10 and higher). It was designed as the replacement to UVFIXFILE, which is has not been enhanced since UniVerse release 9.5.27. Of the two file repair tools it is the only one designed to work with both 23-bit and 64-bit files. It was not documented in any UniVerse publication except in the UniVerse Troubleshooting guide and this white paper. The administration clients do not call it with any arguments other than specifying –file and –fix8. Enhancements to UniAdmin to include more options from fixtool similar to the command line are planned for UniVerse 10.1. fixtool works only on 32-bit and 64-bit UniVerse files, and supports file types 2 – 18 and 30. fixtool requires UniVerse to be running. At releases earlier than 10.0, it may only run on the release for which it was built as the signature in the program is compared to the disk shared memory signature. As of release 10.1, fixtool from any 10.0.x release will work within 10.0.x. For example, a build of fixtool at 10.0.4 for Windows will work at 10.0.0 for Windows. This is a very powerful tool and should be used in preference to uvfixfile. I have never found a file it couldn't fix/help fix. It is in the bin directory of the main uv account and should be run as root/administrator. HTH, Andy From: Holt, Jake jh...@samsill.com To: U2 Users List u2-users@listserver.u2ug.org Sent: Thursday, 18 April 2013, 18:23 Subject: Re: [U2] blink error? Sorry, I hate to keep bombing this with questions especially since this might be a totally unanswerable question, but generally is fixing the file a long process? It's a 268mb file and it's been running for 38 minutes. Is that typical? Just making sure it's not something that should have taken 38 seconds and there is something else getting in the way. Been sitting here since I started it: UVFIXFILE SHIPMENTS FIX Beginning TRACE of SHIPMENTS/SHIPMENTS. ERROR: Processing Primary group 3786, Overflow group 134428. Invalid group buffer chain at address 0x1068e000. Bad link to overflow buffer 134428. Attempting to unlink buffer at 0x1068e000. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: Thursday, April 18, 2013 11:26 AM To: U2 Users List Subject: Re: [U2] blink error? I have not seen that in a long time. Used to occasionally get it in UniVerse on an AIX box. I think it stands for backward link (blink). Simply listing or selecting the file will fail when it hits the offending data. If you can detect the key that is failing, the simple solution used to be to try to copy the record to a temp file, delete the original record (which fixes the link), then copy it back. If that fails, you will likely need to run the fix file utility. Again, I have not seen this in 10 years or so, so my memory may be a little off. Good luck! JRI -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Holt, Jake Sent: Thursday, April 18, 2013 12:20 PM To: U2 Users List Subject: [U2] blink error? Never seen this error message before, no sure on the severity but I hope it's easy to fix: File 'E:\dbms\LIVE\DATAFLO/SHIPMENTS/SHIPMENTS': Computed blink of 0x765800 does not match expected blink of 0x765000! Detected within group starting at address 0x1068E000! Any input as to what I need to do to resolve it? Thanks, Jake Holt l samsill l Information Technology Director (817) 536 - 1906 x 217 l jh...@samsill.com www.samsill.com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] blink error?
Where is this whitepaper at natively? -Original Message- From: andy baum andyb...@yahoo.co.uk To: U2 Users List u2-users@listserver.u2ug.org Sent: Thu, Apr 18, 2013 10:56 am Subject: Re: [U2] blink error? Jake, You do not say what release of UV you are running but as of 9.5.1C you really should be using fixtool. See extracts from whitepaper below 1) Description fixtool is the replacement for UVFIXFILE (uvfixfile from the OS shell) and was introduced at 9.5.1C to support both 32-bit and 64-bit files. Initially it had a limited command line interface as it was intended to be used from the UVAdmin GUI client. When 9.6 was introduced, fixtool was enhanced with a few command line arguments to provide logging of the groups it traced, but could not be limited to a certain number of groups. By 9.6.2.x, it was further enhanced to permit group range traces, which no longer required exclusive access to the file. 11) Final details fixtool was originally designed to by used with the UniVerse administration client, then UVAdmin (pre-release 10) and now UniAdmin (release 10 and higher). It was designed as the replacement to UVFIXFILE, which is has not been enhanced since UniVerse release 9.5.27. Of the two file repair tools it is the only one designed to work with both 23-bit and 64-bit files. It was not documented in any UniVerse publication except in the UniVerse Troubleshooting guide and this white paper. The administration clients do not call it with any arguments other than specifying –file and –fix8. Enhancements to UniAdmin to include more options from fixtool similar to the command line are planned for UniVerse 10.1. fixtool works only on 32-bit and 64-bit UniVerse files, and supports file types 2 – 18 and 30. fixtool requires UniVerse to be running. At releases earlier than 10.0, it may only run on the release for which it was built as the signature in the program is compared to the disk shared memory signature. As of release 10.1, fixtool from any 10.0.x release will work within 10.0.x. For example, a build of fixtool at 10.0.4 for Windows will work at 10.0.0 for Windows. This is a very powerful tool and should be used in preference to uvfixfile. I have never found a file it couldn't fix/help fix. It is in the bin directory of the main uv account and should be run as root/administrator. HTH, Andy From: Holt, Jake jh...@samsill.com To: U2 Users List u2-users@listserver.u2ug.org Sent: Thursday, 18 April 2013, 18:23 Subject: Re: [U2] blink error? Sorry, I hate to keep bombing this with questions especially since this might be a totally unanswerable question, but generally is fixing the file a long process? It's a 268mb file and it's been running for 38 minutes. Is that typical? Just making sure it's not something that should have taken 38 seconds and there is something else getting in the way. Been sitting here since I started it: UVFIXFILE SHIPMENTS FIX Beginning TRACE of SHIPMENTS/SHIPMENTS. ERROR: Processing Primary group 3786, Overflow group 134428. Invalid group buffer chain at address 0x1068e000. Bad link to overflow buffer 134428. Attempting to unlink buffer at 0x1068e000. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: Thursday, April 18, 2013 11:26 AM To: U2 Users List Subject: Re: [U2] blink error? I have not seen that in a long time. Used to occasionally get it in UniVerse on an AIX box. I think it stands for backward link (blink). Simply listing or selecting the file will fail when it hits the offending data. If you can detect the key that is failing, the simple solution used to be to try to copy the record to a temp file, delete the original record (which fixes the link), then copy it back. If that fails, you will likely need to run the fix file utility. Again, I have not seen this in 10 years or so, so my memory may be a little off. Good luck! JRI -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Holt, Jake Sent: Thursday, April 18, 2013 12:20 PM To: U2 Users List Subject: [U2] blink error? Never seen this error message before, no sure on the severity but I hope it's easy to fix: File 'E:\dbms\LIVE\DATAFLO/SHIPMENTS/SHIPMENTS': Computed blink of 0x765800 does not match expected blink of 0x765000! Detected within group starting at address 0x1068E000! Any input as to what I need to do to resolve it? Thanks, Jake Holt l samsill l Information Technology Director (817) 536 - 1906 x 217 l jh...@samsill.com www.samsill.com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http
Re: [U2] blink error?
Thanks for the help all. I ended up just restoring the file from last night, they weren't interested in waiting anymore. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson Sent: Thursday, April 18, 2013 1:05 PM To: andyb...@yahoo.co.uk; u2-users@listserver.u2ug.org Subject: Re: [U2] blink error? Where is this whitepaper at natively? -Original Message- From: andy baum andyb...@yahoo.co.uk To: U2 Users List u2-users@listserver.u2ug.org Sent: Thu, Apr 18, 2013 10:56 am Subject: Re: [U2] blink error? Jake, You do not say what release of UV you are running but as of 9.5.1C you really should be using fixtool. See extracts from whitepaper below 1) Description fixtool is the replacement for UVFIXFILE (uvfixfile from the OS shell) and was introduced at 9.5.1C to support both 32-bit and 64-bit files. Initially it had a limited command line interface as it was intended to be used from the UVAdmin GUI client. When 9.6 was introduced, fixtool was enhanced with a few command line arguments to provide logging of the groups it traced, but could not be limited to a certain number of groups. By 9.6.2.x, it was further enhanced to permit group range traces, which no longer required exclusive access to the file. 11) Final details fixtool was originally designed to by used with the UniVerse administration client, then UVAdmin (pre-release 10) and now UniAdmin (release 10 and higher). It was designed as the replacement to UVFIXFILE, which is has not been enhanced since UniVerse release 9.5.27. Of the two file repair tools it is the only one designed to work with both 23-bit and 64-bit files. It was not documented in any UniVerse publication except in the UniVerse Troubleshooting guide and this white paper. The administration clients do not call it with any arguments other than specifying –file and –fix8. Enhancements to UniAdmin to include more options from fixtool similar to the command line are planned for UniVerse 10.1. fixtool works only on 32-bit and 64-bit UniVerse files, and supports file types 2 – 18 and 30. fixtool requires UniVerse to be running. At releases earlier than 10.0, it may only run on the release for which it was built as the signature in the program is compared to the disk shared memory signature. As of release 10.1, fixtool from any 10.0.x release will work within 10.0.x. For example, a build of fixtool at 10.0.4 for Windows will work at 10.0.0 for Windows. This is a very powerful tool and should be used in preference to uvfixfile. I have never found a file it couldn't fix/help fix. It is in the bin directory of the main uv account and should be run as root/administrator. HTH, Andy From: Holt, Jake jh...@samsill.com To: U2 Users List u2-users@listserver.u2ug.org Sent: Thursday, 18 April 2013, 18:23 Subject: Re: [U2] blink error? Sorry, I hate to keep bombing this with questions especially since this might be a totally unanswerable question, but generally is fixing the file a long process? It's a 268mb file and it's been running for 38 minutes. Is that typical? Just making sure it's not something that should have taken 38 seconds and there is something else getting in the way. Been sitting here since I started it: UVFIXFILE SHIPMENTS FIX Beginning TRACE of SHIPMENTS/SHIPMENTS. ERROR: Processing Primary group 3786, Overflow group 134428. Invalid group buffer chain at address 0x1068e000. Bad link to overflow buffer 134428. Attempting to unlink buffer at 0x1068e000. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: Thursday, April 18, 2013 11:26 AM To: U2 Users List Subject: Re: [U2] blink error? I have not seen that in a long time. Used to occasionally get it in UniVerse on an AIX box. I think it stands for backward link (blink). Simply listing or selecting the file will fail when it hits the offending data. If you can detect the key that is failing, the simple solution used to be to try to copy the record to a temp file, delete the original record (which fixes the link), then copy it back. If that fails, you will likely need to run the fix file utility. Again, I have not seen this in 10 years or so, so my memory may be a little off. Good luck! JRI -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Holt, Jake Sent: Thursday, April 18, 2013 12:20 PM To: U2 Users List Subject: [U2] blink error? Never seen this error message before, no sure on the severity but I hope it's easy to fix: File 'E:\dbms\LIVE\DATAFLO/SHIPMENTS/SHIPMENTS': Computed blink of 0x765800 does not match expected blink of 0x765000! Detected within group starting at address 0x1068E000! Any input as to what I need to do to resolve it? Thanks
RE: [U2] Blink Error - Dictionary Related
I have a situation were I have a Prod box and a Dev Box both with Universe installed. On the Prod box we have a samba share that is pointing to the Dev box and we have voc entries pointing to Dev files. But when I execute a command such as: Copy from file to Test.file The records will copy over to the Dev box, but it always results in a Blink error. Has anyone experienced this or know how to fix it? Henry M. Database Administrator -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bessel, Karen Sent: Friday, May 09, 2008 3:57 PM To: u2-users@listserver.u2ug.org Subject: [U2] Blink Error - Dictionary Related A client is experiencing a blink error when using a certain I-descriptor in a SORT, but not in a LIST or SELECT. I can't copy the code into the post because of copyright purposes, but this is the dictionary item: 0001: I 0002: IF CASE.PERSON.ID # THEN SUBR(CJ.READ.PERSON,CASE.PERSON.ID,1,) E LSE 0003: S;*;*** No Defendant *** 0004: Defendant 0005: 30L 0006: S The dictionary item referenced by the I-descriptor: 0001: A 0002: 1 0003: CASE.PERSON.ID 0004: 0005: M 0006: 0007: 0008: 0009: R 0010: 8 0011: 0012: COMMON Attribute 1 should be single-valued but there are 27 records in this file that have multiple values in this field. On our in-house system, we also have a handful of records that have multiple values in this field, and I can't recreate the problem here. There are commons involved in the subroutine referenced by the I-descriptor. This issue just came to me and the people who worked on it before did all of the data related things I would have done: searched for control characters, fix tool, deleted the file then recreated it, etc. I don't know if I've provided enough information to explain the problembut has anyone seen this? If you've experienced an application-related blink error, I'd be interested in hearing from you. Karen Bessel Software Developer Tyler Technologies, Inc. 6500 International Parkway, Suite 2000 Plano, TX 75093 Phone: 972.713.3770 ext:6227 Fax: 972.713.3777 Email: [EMAIL PROTECTED] Web: http://www.tylertech.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Blink Error - Dictionary Related
Are both boxes on the same release of UniVerse and the same operating system (same release)? Jerry Banker Senior Programmer Analyst IBM Certified Solutions Expert -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martel, Henry Sent: Monday, May 12, 2008 12:59 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Blink Error - Dictionary Related I have a situation were I have a Prod box and a Dev Box both with Universe installed. On the Prod box we have a samba share that is pointing to the Dev box and we have voc entries pointing to Dev files. But when I execute a command such as: Copy from file to Test.file The records will copy over to the Dev box, but it always results in a Blink error. Has anyone experienced this or know how to fix it? Henry M. Database Administrator -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bessel, Karen Sent: Friday, May 09, 2008 3:57 PM To: u2-users@listserver.u2ug.org Subject: [U2] Blink Error - Dictionary Related A client is experiencing a blink error when using a certain I-descriptor in a SORT, but not in a LIST or SELECT. I can't copy the code into the post because of copyright purposes, but this is the dictionary item: 0001: I 0002: IF CASE.PERSON.ID # THEN SUBR(CJ.READ.PERSON,CASE.PERSON.ID,1,) E LSE 0003: S;*;*** No Defendant *** 0004: Defendant 0005: 30L 0006: S The dictionary item referenced by the I-descriptor: 0001: A 0002: 1 0003: CASE.PERSON.ID 0004: 0005: M 0006: 0007: 0008: 0009: R 0010: 8 0011: 0012: COMMON Attribute 1 should be single-valued but there are 27 records in this file that have multiple values in this field. On our in-house system, we also have a handful of records that have multiple values in this field, and I can't recreate the problem here. There are commons involved in the subroutine referenced by the I-descriptor. This issue just came to me and the people who worked on it before did all of the data related things I would have done: searched for control characters, fix tool, deleted the file then recreated it, etc. I don't know if I've provided enough information to explain the problembut has anyone seen this? If you've experienced an application-related blink error, I'd be interested in hearing from you. Karen Bessel Software Developer Tyler Technologies, Inc. 6500 International Parkway, Suite 2000 Plano, TX 75093 Phone: 972.713.3770 ext:6227 Fax: 972.713.3777 Email: [EMAIL PROTECTED] Web: http://www.tylertech.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Blink Error - Dictionary Related
Henry That is a really really bad idea. Each UniVerse keeps its lock table in memory, used to coordinate access at the group level whilst reading and writing as well as the record lock handling. As soon as you access a file on another system without coordinating with the remote lock table, you are just begging for database corruption. If you are going to do this there is a product called uvNet that coordinates the activity on both ends. Or make up a uniobjects connection from your dev box and copy across that. Or open the remote box as an ODBC source. Or write a simple middleware pipe. But you must must ensure that the write is done by the remote universe, not by your universe against a share. Brian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martel, Henry Sent: 12 May 2008 18:59 To: u2-users@listserver.u2ug.org Subject: RE: [U2] Blink Error - Dictionary Related I have a situation were I have a Prod box and a Dev Box both with Universe installed. On the Prod box we have a samba share that is pointing to the Dev box and we have voc entries pointing to Dev files. But when I execute a command such as: Copy from file to Test.file The records will copy over to the Dev box, but it always results in a Blink error. Has anyone experienced this or know how to fix it? Henry M. Database Administrator -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bessel, Karen Sent: Friday, May 09, 2008 3:57 PM To: u2-users@listserver.u2ug.org Subject: [U2] Blink Error - Dictionary Related A client is experiencing a blink error when using a certain I-descriptor in a SORT, but not in a LIST or SELECT. I can't copy the code into the post because of copyright purposes, but this is the dictionary item: 0001: I 0002: IF CASE.PERSON.ID # THEN SUBR(CJ.READ.PERSON,CASE.PERSON.ID,1,) E LSE 0003: S;*;*** No Defendant *** 0004: Defendant 0005: 30L 0006: S The dictionary item referenced by the I-descriptor: 0001: A 0002: 1 0003: CASE.PERSON.ID 0004: 0005: M 0006: 0007: 0008: 0009: R 0010: 8 0011: 0012: COMMON Attribute 1 should be single-valued but there are 27 records in this file that have multiple values in this field. On our in-house system, we also have a handful of records that have multiple values in this field, and I can't recreate the problem here. There are commons involved in the subroutine referenced by the I-descriptor. This issue just came to me and the people who worked on it before did all of the data related things I would have done: searched for control characters, fix tool, deleted the file then recreated it, etc. I don't know if I've provided enough information to explain the problembut has anyone seen this? If you've experienced an application-related blink error, I'd be interested in hearing from you. Karen Bessel Software Developer Tyler Technologies, Inc. 6500 International Parkway, Suite 2000 Plano, TX 75093 Phone: 972.713.3770 ext:6227 Fax: 972.713.3777 Email: [EMAIL PROTECTED] Web: http://www.tylertech.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Blink Error - Dictionary Related
I agree with Brian. Blink errors are VERY bad. If you can get the 2 dbs in a stable state with no users on either system, copying is fine. Other than that, Brian has the right idea. Blink errors can be the kiss of death, so be careful. John Israel Sr. Programmer/Analyst Dayton Superior Corporation 721 Richard St. Dayton, OH 45342 937-866-0711 x44380 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martel, Henry Sent: Monday, May 12, 2008 1:59 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Blink Error - Dictionary Related I have a situation were I have a Prod box and a Dev Box both with Universe installed. On the Prod box we have a samba share that is pointing to the Dev box and we have voc entries pointing to Dev files. But when I execute a command such as: Copy from file to Test.file The records will copy over to the Dev box, but it always results in a Blink error. Has anyone experienced this or know how to fix it? Henry M. Database Administrator -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bessel, Karen Sent: Friday, May 09, 2008 3:57 PM To: u2-users@listserver.u2ug.org Subject: [U2] Blink Error - Dictionary Related A client is experiencing a blink error when using a certain I-descriptor in a SORT, but not in a LIST or SELECT. I can't copy the code into the post because of copyright purposes, but this is the dictionary item: 0001: I 0002: IF CASE.PERSON.ID # THEN SUBR(CJ.READ.PERSON,CASE.PERSON.ID,1,) E LSE 0003: S;*;*** No Defendant *** 0004: Defendant 0005: 30L 0006: S The dictionary item referenced by the I-descriptor: 0001: A 0002: 1 0003: CASE.PERSON.ID 0004: 0005: M 0006: 0007: 0008: 0009: R 0010: 8 0011: 0012: COMMON Attribute 1 should be single-valued but there are 27 records in this file that have multiple values in this field. On our in-house system, we also have a handful of records that have multiple values in this field, and I can't recreate the problem here. There are commons involved in the subroutine referenced by the I-descriptor. This issue just came to me and the people who worked on it before did all of the data related things I would have done: searched for control characters, fix tool, deleted the file then recreated it, etc. I don't know if I've provided enough information to explain the problembut has anyone seen this? If you've experienced an application-related blink error, I'd be interested in hearing from you. Karen Bessel Software Developer Tyler Technologies, Inc. 6500 International Parkway, Suite 2000 Plano, TX 75093 Phone: 972.713.3770 ext:6227 Fax: 972.713.3777 Email: [EMAIL PROTECTED] Web: http://www.tylertech.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Blink Error - Dictionary Related
A blink (Backward Link) error is an error in the structure of a database file doug chanco wrote: For those of us new to universe (or have never heard of it) what exactly is a blink error thanks dougc Martel, Henry wrote: I have a situation were I have a Prod box and a Dev Box both with Universe installed. On the Prod box we have a samba share that is pointing to the Dev box and we have voc entries pointing to Dev files. But when I execute a command such as: Copy from file to Test.file The records will copy over to the Dev box, but it always results in a Blink error. Has anyone experienced this or know how to fix it? Henry M. Database Administrator -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bessel, Karen Sent: Friday, May 09, 2008 3:57 PM To: u2-users@listserver.u2ug.org Subject: [U2] Blink Error - Dictionary Related A client is experiencing a blink error when using a certain I-descriptor in a SORT, but not in a LIST or SELECT. I can't copy the code into the post because of copyright purposes, but this is the dictionary item: 0001: I 0002: IF CASE.PERSON.ID # THEN SUBR(CJ.READ.PERSON,CASE.PERSON.ID,1,) E LSE 0003: S;*;*** No Defendant *** 0004: Defendant 0005: 30L 0006: S The dictionary item referenced by the I-descriptor: 0001: A 0002: 1 0003: CASE.PERSON.ID 0004: 0005: M 0006: 0007: 0008: 0009: R 0010: 8 0011: 0012: COMMON Attribute 1 should be single-valued but there are 27 records in this file that have multiple values in this field. On our in-house system, we also have a handful of records that have multiple values in this field, and I can't recreate the problem here. There are commons involved in the subroutine referenced by the I-descriptor. This issue just came to me and the people who worked on it before did all of the data related things I would have done: searched for control characters, fix tool, deleted the file then recreated it, etc. I don't know if I've provided enough information to explain the problembut has anyone seen this? If you've experienced an application-related blink error, I'd be interested in hearing from you. Karen Bessel Software Developer Tyler Technologies, Inc. 6500 International Parkway, Suite 2000 Plano, TX 75093 Phone: 972.713.3770 ext:6227 Fax: 972.713.3777 Email: [EMAIL PROTECTED] Web: http://www.tylertech.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -- Jeff Schasny - Denver, Co, USA jschasny at gmail dot com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Blink Error - Dictionary Related
Blink = Backward Link. Mumbo jumbo for the internal guts of how the pieces of the file all hook together. I have seen different results on different versions on UniVerse. However, in the worse case scenario (which was the most common), we could never recover cleanly and had to reload from a backup. This error appeared to only be in a single group, so as long as we did not hit that group, we were OK (but that was still taking a chance). John Israel Sr. Programmer/Analyst Dayton Superior Corporation 721 Richard St. Dayton, OH 45342 937-866-0711 x44380 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of doug chanco Sent: Monday, May 12, 2008 3:00 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Blink Error - Dictionary Related For those of us new to universe (or have never heard of it) what exactly is a blink error thanks dougc Martel, Henry wrote: I have a situation were I have a Prod box and a Dev Box both with Universe installed. On the Prod box we have a samba share that is pointing to the Dev box and we have voc entries pointing to Dev files. But when I execute a command such as: Copy from file to Test.file The records will copy over to the Dev box, but it always results in a Blink error. Has anyone experienced this or know how to fix it? Henry M. Database Administrator -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bessel, Karen Sent: Friday, May 09, 2008 3:57 PM To: u2-users@listserver.u2ug.org Subject: [U2] Blink Error - Dictionary Related A client is experiencing a blink error when using a certain I-descriptor in a SORT, but not in a LIST or SELECT. I can't copy the code into the post because of copyright purposes, but this is the dictionary item: 0001: I 0002: IF CASE.PERSON.ID # THEN SUBR(CJ.READ.PERSON,CASE.PERSON.ID,1,) E LSE 0003: S;*;*** No Defendant *** 0004: Defendant 0005: 30L 0006: S The dictionary item referenced by the I-descriptor: 0001: A 0002: 1 0003: CASE.PERSON.ID 0004: 0005: M 0006: 0007: 0008: 0009: R 0010: 8 0011: 0012: COMMON Attribute 1 should be single-valued but there are 27 records in this file that have multiple values in this field. On our in-house system, we also have a handful of records that have multiple values in this field, and I can't recreate the problem here. There are commons involved in the subroutine referenced by the I-descriptor. This issue just came to me and the people who worked on it before did all of the data related things I would have done: searched for control characters, fix tool, deleted the file then recreated it, etc. I don't know if I've provided enough information to explain the problembut has anyone seen this? If you've experienced an application-related blink error, I'd be interested in hearing from you. Karen Bessel Software Developer Tyler Technologies, Inc. 6500 International Parkway, Suite 2000 Plano, TX 75093 Phone: 972.713.3770 ext:6227 Fax: 972.713.3777 Email: [EMAIL PROTECTED] Web: http://www.tylertech.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Blink Error - Dictionary Related
Blink is short for Backward link. Two blocks of random memory that represent a logically contiguous object that is = two blocks large will have header data that point to each other. The first will have a forward link to the second and a zero in the backward link to indicate it's the first in the chain. The second will have a forward link of zero (no more blocks) and a backward link to the first. If the second block does not point back (is zero or references a different block), this implies that something has gone really, really wrong with the memory management of the system. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of doug chanco Sent: Monday, May 12, 2008 12:00 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Blink Error - Dictionary Related For those of us new to universe (or have never heard of it) what exactly is a blink error thanks dougc Martel, Henry wrote: I have a situation were I have a Prod box and a Dev Box both with Universe installed. On the Prod box we have a samba share that is pointing to the Dev box and we have voc entries pointing to Dev files. But when I execute a command such as: Copy from file to Test.file The records will copy over to the Dev box, but it always results in a Blink error. Has anyone experienced this or know how to fix it? Henry M. Database Administrator -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bessel, Karen Sent: Friday, May 09, 2008 3:57 PM To: u2-users@listserver.u2ug.org Subject: [U2] Blink Error - Dictionary Related A client is experiencing a blink error when using a certain I-descriptor in a SORT, but not in a LIST or SELECT. I can't copy the code into the post because of copyright purposes, but this is the dictionary item: 0001: I 0002: IF CASE.PERSON.ID # THEN SUBR(CJ.READ.PERSON,CASE.PERSON.ID,1,) E LSE 0003: S;*;*** No Defendant *** 0004: Defendant 0005: 30L 0006: S The dictionary item referenced by the I-descriptor: 0001: A 0002: 1 0003: CASE.PERSON.ID 0004: 0005: M 0006: 0007: 0008: 0009: R 0010: 8 0011: 0012: COMMON Attribute 1 should be single-valued but there are 27 records in this file that have multiple values in this field. On our in-house system, we also have a handful of records that have multiple values in this field, and I can't recreate the problem here. There are commons involved in the subroutine referenced by the I-descriptor. This issue just came to me and the people who worked on it before did all of the data related things I would have done: searched for control characters, fix tool, deleted the file then recreated it, etc. I don't know if I've provided enough information to explain the problembut has anyone seen this? If you've experienced an application-related blink error, I'd be interested in hearing from you. Karen Bessel Software Developer Tyler Technologies, Inc. 6500 International Parkway, Suite 2000 Plano, TX 75093 Phone: 972.713.3770 ext:6227 Fax: 972.713.3777 Email: [EMAIL PROTECTED] Web: http://www.tylertech.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Blink Error - Dictionary Related
Yes, I misspoke it not a samba share it's a nfs mount. Just to clarify the copy is done from within Universe and not the Unix level. How do I know if UvNet is installed? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of JPB-U2UG Sent: Monday, May 12, 2008 3:00 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Blink Error - Dictionary Related Are both boxes on the same release of UniVerse and the same operating system (same release)? Jerry Banker Senior Programmer Analyst IBM Certified Solutions Expert -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martel, Henry Sent: Monday, May 12, 2008 12:59 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Blink Error - Dictionary Related I have a situation were I have a Prod box and a Dev Box both with Universe installed. On the Prod box we have a samba share that is pointing to the Dev box and we have voc entries pointing to Dev files. But when I execute a command such as: Copy from file to Test.file The records will copy over to the Dev box, but it always results in a Blink error. Has anyone experienced this or know how to fix it? Henry M. Database Administrator -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bessel, Karen Sent: Friday, May 09, 2008 3:57 PM To: u2-users@listserver.u2ug.org Subject: [U2] Blink Error - Dictionary Related A client is experiencing a blink error when using a certain I-descriptor in a SORT, but not in a LIST or SELECT. I can't copy the code into the post because of copyright purposes, but this is the dictionary item: 0001: I 0002: IF CASE.PERSON.ID # THEN SUBR(CJ.READ.PERSON,CASE.PERSON.ID,1,) E LSE 0003: S;*;*** No Defendant *** 0004: Defendant 0005: 30L 0006: S The dictionary item referenced by the I-descriptor: 0001: A 0002: 1 0003: CASE.PERSON.ID 0004: 0005: M 0006: 0007: 0008: 0009: R 0010: 8 0011: 0012: COMMON Attribute 1 should be single-valued but there are 27 records in this file that have multiple values in this field. On our in-house system, we also have a handful of records that have multiple values in this field, and I can't recreate the problem here. There are commons involved in the subroutine referenced by the I-descriptor. This issue just came to me and the people who worked on it before did all of the data related things I would have done: searched for control characters, fix tool, deleted the file then recreated it, etc. I don't know if I've provided enough information to explain the problembut has anyone seen this? If you've experienced an application-related blink error, I'd be interested in hearing from you. Karen Bessel Software Developer Tyler Technologies, Inc. 6500 International Parkway, Suite 2000 Plano, TX 75093 Phone: 972.713.3770 ext:6227 Fax: 972.713.3777 Email: [EMAIL PROTECTED] Web: http://www.tylertech.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Blink Error - Dictionary Related
I would try re-writing the A type as a D...I'm not sure I-types always play well with A/S types. Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bessel, Karen Sent: Friday, May 09, 2008 12:57 PM To: u2-users@listserver.u2ug.org Subject: [U2] Blink Error - Dictionary Related A client is experiencing a blink error when using a certain I-descriptor in a SORT, but not in a LIST or SELECT. I can't copy the code into the post because of copyright purposes, but this is the dictionary item: 0001: I 0002: IF CASE.PERSON.ID # THEN SUBR(CJ.READ.PERSON,CASE.PERSON.ID,1,) E LSE 0003: S;*;*** No Defendant *** 0004: Defendant 0005: 30L 0006: S The dictionary item referenced by the I-descriptor: 0001: A 0002: 1 0003: CASE.PERSON.ID 0004: 0005: M 0006: 0007: 0008: 0009: R 0010: 8 0011: 0012: COMMON Attribute 1 should be single-valued but there are 27 records in this file that have multiple values in this field. On our in-house system, we also have a handful of records that have multiple values in this field, and I can't recreate the problem here. There are commons involved in the subroutine referenced by the I-descriptor. This issue just came to me and the people who worked on it before did all of the data related things I would have done: searched for control characters, fix tool, deleted the file then recreated it, etc. I don't know if I've provided enough information to explain the problembut has anyone seen this? If you've experienced an application-related blink error, I'd be interested in hearing from you. Karen Bessel Software Developer Tyler Technologies, Inc. 6500 International Parkway, Suite 2000 Plano, TX 75093 Phone: 972.713.3770 ext:6227 Fax: 972.713.3777 Email: [EMAIL PROTECTED] Web: http://www.tylertech.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Blink Error - Dictionary Related
I believe that I have seen a closely-related problem. A talented programmer on this list suggested keeping the dictionary entries 1 through 6 and delteting 7 and above. I sort-of recall that 7 and above may be used to relate U2 to SQL. If there is no SQL linkage, consider making a backup copy, purging DICT items 7 and above, and then give it a try. I did this in maybe one dozen dictionaries. The other ten dozen dictionaries here were clean. It was as though one of my predecessors started a SQL link project here a long time ago that was never fully realized. HTH. --Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Bessel, Karen Sent: Friday, May 09, 2008 3:57 PM To: u2-users@listserver.u2ug.org Subject: [U2] Blink Error - Dictionary Related A client is experiencing a blink error when using a certain I-descriptor in a SORT, but not in a LIST or SELECT. I can't copy the code into the post because of copyright purposes, but this is the dictionary item: 0001: I 0002: IF CASE.PERSON.ID # THEN SUBR(CJ.READ.PERSON,CASE.PERSON.ID,1,) E LSE 0003: S;*;*** No Defendant *** 0004: Defendant 0005: 30L 0006: S The dictionary item referenced by the I-descriptor: 0001: A 0002: 1 0003: CASE.PERSON.ID 0004: 0005: M 0006: 0007: 0008: 0009: R 0010: 8 0011: 0012: COMMON Attribute 1 should be single-valued but there are 27 records in this file that have multiple values in this field. On our in-house system, we also have a handful of records that have multiple values in this field, and I can't recreate the problem here. There are commons involved in the subroutine referenced by the I-descriptor. This issue just came to me and the people who worked on it before did all of the data related things I would have done: searched for control characters, fix tool, deleted the file then recreated it, etc. I don't know if I've provided enough information to explain the problembut has anyone seen this? If you've experienced an application-related blink error, I'd be interested in hearing from you. Karen Bessel Software Developer Tyler Technologies, Inc. 6500 International Parkway, Suite 2000 Plano, TX 75093 Phone: 972.713.3770 ext:6227 Fax: 972.713.3777 Email: [EMAIL PROTECTED] Web: http://www.tylertech.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Blink Error - Backward Link error
Good Catch Karl! Light bulb went off... Yes it truncates the group, not the file. I remember Mark talking that if a file is tremendously undersized and has lots of overflow groups, the damage would be more severe. Really makes sense now. Steve Correction, you should only see loss of data after the BLINK error in he affected group only. Karl Pearson Senior uniVerse DBA and one who cut his teeth fixing blinks by hand (thanks to Mark Baldridge and Joel Yates). quote who=Stephen O'Neal Anmol, ...When they fix the file, the file will be truncated at the group where this occurred. This can be anywhere in the file, because the group extended for overflow can be anywhere in the file. You may end up with a file that is considerably smaller than your original file! A wake up call for others: Watch out for your 2gb file limits on static files. Good luck in recovering your data! Regards, Steve Anmol Chandrakant Khopade [EMAIL PROTECTED] Hi, I am receiving the following error: Computed blink of 0xB44 does not match expected blink of 0x0! Detected within group starting at address 0x8000! Internal data error. ... Warm regards Anmol --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Blink Error - Backward Link error
Why, oh why, doesn't UV fail the write before it corrupts the file? It is trivial to know that this is about to happen. Martin Phillips Ladybridge Systems 17b Coldstream Lane, Hardingstone, Northampton NN4 6DB +44-(0)1604-709200 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Blink Error - Backward Link error
Wow, what a concept! But then, that would reduce a bit of job security for folks like me, wouldn't it? I've always told clients going in that if I do my job right, I'll be out of a job. Yes, I tell my clients that. It's basically true, but there are certainly glaring exceptions. Karl quote who=Martin Phillips Why, oh why, doesn't UV fail the write before it corrupts the file? It is trivial to know that this is about to happen. Martin Phillips Ladybridge Systems 17b Coldstream Lane, Hardingstone, Northampton NN4 6DB +44-(0)1604-709200 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -- karl _/ _/ _/ _/_/_/ __o _/ _/ _/ _/_/ _-\._ _/_/_/ _/_/_/ (_)/ (_) _/ _/ _/ _/ .. _/ _/ arl _/_/_/ _/ earson[EMAIL PROTECTED] -- IT Director, ATS Industrial Supply, Inc. http://www.atsindustrial.com Toll-free: 800-789-9300 x29 Direct2Desk: 801-978-4429 Facsimile: 801-972-3888 -- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Blink Error - Backward Link error
This is a good explanation I'd forgotten about. You were probably the one who explained it to me a little time ago... Long time... Karl quote who=Glenn Herbert Because of the manner in which the write subsystem was implemented, it is NOT a trivial task to either pre-detect or recover from a system write failure, which is usually the cause of the corruption. The group structure (which will be comprised of one or more buffers) is modified in memory, and then shipped off to the system for writing; there is no way to determine if in fact any particular write actually made it TO disk. If a write() operation returned successful, then that is the only validation we can check; if the system burps on that buffer later down the chain, there is no way to detect that. Having spent better than 10 years in the file system, there was serious discussion of how to do this, but unfortunately required a very serious rewrite of the write subsystem; obviously, that work would never be done. The various recovery tools shipped with the product do a pretty decent job of recovering as much of the file as possible. Hope this helps. __ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stevenson, Charles [EMAIL PROTECTED] Sent: Wednesday, September 28, 2005 8:10 AM To: u2-users@listserver.u2ug.org Subject: FW: [U2] Blink Error - Backward Link error Do I detect an enhancement suggestion? Whether this is trivial or hard is beyond me, but I tend to believe Mr. Phillips. (On this subject, anyway. I don't know his opinion of the British Royals, for example.) cds -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Phillips Sent: Wednesday, September 28, 2005 1:11 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Blink Error - Backward Link error Why, oh why, doesn't UV fail the write before it corrupts the file? It is trivial to know that this is about to happen. Martin Phillips Ladybridge Systems 17b Coldstream Lane, Hardingstone, Northampton NN4 6DB +44-(0)1604-709200 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -- karl _/ _/ _/ _/_/_/ __o _/ _/ _/ _/_/ _-\._ _/_/_/ _/_/_/ (_)/ (_) _/ _/ _/ _/ .. _/ _/ arl _/_/_/ _/ earson[EMAIL PROTECTED] -- IT Director, ATS Industrial Supply, Inc. http://www.atsindustrial.com Toll-free: 800-789-9300 x29 Direct2Desk: 801-978-4429 Facsimile: 801-972-3888 -- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Blink Error - Backward Link error
Anmol, I don't have good news. You have a broken file due to a mismatched backward link (blink). This occurred when the file attempted to expand past the 2gb limit on a static file by trying to extend an overflow block. Any attempt to SELECT or SSELECT the file will fail when it reaches the broken group. :^( Your alternatives at this point are: 1) restore the last know valid backup of the file and rebuild the data 2) contact the company where you purchased your U2 licenses. Their U2 Support organization will put you in touch with someone that can fix the file (for a fee). When they fix the file, the file will be truncated at the group where this occurred. This can be anywhere in the file, because the group extended for overflow can be anywhere in the file. You may end up with a file that is considerably smaller than your original file! A wake up call for others: Watch out for your 2gb file limits on static files. Good luck in recovering your data! Regards, Steve Stephen M. O'Neal, CDP IBM U2 Certified Services Sales Specialist North America U2 Lab Services Information Management, IBM Software Group Anmol Chandrakant Khopade [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09/27/2005 07:37 PM Please respond to u2-users To u2-users@listserver.u2ug.org cc Subject [U2] Blink Error Hi, I am receiving the following error: Computed blink of 0xB44 does not match expected blink of 0x0! Detected within group starting at address 0x8000! Internal data error. I am having a 2GB Data 30 file, which got locked due to unix restriction on file size. A unibasic program has been written to purge the data in this file. I imported the 2GB file to another universe box which is a replica of the original box and also contains the above file, and reconfigured the VOC pointer of the local file to point to the 2GB file. This error came in while selecting the records. Please let me know if any one knows a work around or has any information about this. Thanks in advance Warm regards Anmol CAUTION - Disclaimer * This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS End of Disclaimer INFOSYS*** --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Blink Error - Backward Link error
Correction, you should only see loss of data after the BLINK error in he affected group only. Karl Pearson Senior uniVerse DBA and one who cut his teeth fixing blinks by hand (thanks to Mark Baldridge and Joel Yates). quote who=Stephen O'Neal Anmol, I don't have good news. You have a broken file due to a mismatched backward link (blink). This occurred when the file attempted to expand past the 2gb limit on a static file by trying to extend an overflow block. Any attempt to SELECT or SSELECT the file will fail when it reaches the broken group. :^( Your alternatives at this point are: 1) restore the last know valid backup of the file and rebuild the data 2) contact the company where you purchased your U2 licenses. Their U2 Support organization will put you in touch with someone that can fix the file (for a fee). When they fix the file, the file will be truncated at the group where this occurred. This can be anywhere in the file, because the group extended for overflow can be anywhere in the file. You may end up with a file that is considerably smaller than your original file! A wake up call for others: Watch out for your 2gb file limits on static files. Good luck in recovering your data! Regards, Steve Stephen M. O'Neal, CDP IBM U2 Certified Services Sales Specialist North America U2 Lab Services Information Management, IBM Software Group Anmol Chandrakant Khopade [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09/27/2005 07:37 PM Please respond to u2-users To u2-users@listserver.u2ug.org cc Subject [U2] Blink Error Hi, I am receiving the following error: Computed blink of 0xB44 does not match expected blink of 0x0! Detected within group starting at address 0x8000! Internal data error. I am having a 2GB Data 30 file, which got locked due to unix restriction on file size. A unibasic program has been written to purge the data in this file. I imported the 2GB file to another universe box which is a replica of the original box and also contains the above file, and reconfigured the VOC pointer of the local file to point to the 2GB file. This error came in while selecting the records. Please let me know if any one knows a work around or has any information about this. Thanks in advance Warm regards Anmol CAUTION - Disclaimer * This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS End of Disclaimer INFOSYS*** --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -- karl _/ _/ _/ _/_/_/ __o _/ _/ _/ _/_/ _-\._ _/_/_/ _/_/_/ (_)/ (_) _/ _/ _/ _/ .. _/ _/ arl _/_/_/ _/ earson[EMAIL PROTECTED] -- IT Director, ATS Industrial Supply, Inc. http://www.atsindustrial.com Toll-free: 800-789-9300 x29 Direct2Desk: 801-978-4429 Facsimile: 801-972-3888 -- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
