Re: [U2] UvRestore error
Chris Austin <[email protected]>
| Newsgroups | gmane.comp.db.u2.general |
|---|---|
| Message-ID | <[email protected]> |
I figured it out. It wasn't one of the @ID's.. rather an I-descriptor that we had indexed on that CLIENT table that was calculating EXACTLY how that message displays. For example, the symbolic (I-Descriptor) for one of the records is calculating > "Z29864873 00000000ýA38385000 00000000" I appreciate the help, this was an issue that was lingering for some time, nice to have an answer and clean it up so we can rebuild the indices faster. Chris > From: [email protected] > To: [email protected] > Date: Wed, 27 Nov 2013 09:50:02 +1100 > Subject: Re: [U2] UvRestore error > > I had this error once. This happens when the @tm, @sm @vm exists in the indexed field (or if the indexed field is > than the maximum key size (as defined in the CONFIG MAXKEYSIZE command) So you may have to write a program to analyse the result of your I-descriptor field used for indexing. > > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Chris Austin > Sent: Wednesday, 27 November 2013 9:32 AM > To: U2 Users List > Subject: Re: [U2] UvRestore error > > I wrote a program to check for @VM, @SVM, and @FM on every record in that table and it didn't find anything so it must be something else. > > The part I'm struggling with is locating what this means > > > Unable to write item "Z29864873 00000000ýA38385000 00000000". > > since there's no ý in the @IDs. I wonder if it comes from a field we have INDEXED (indexed I-descriptor). > > Chris > > > > > From: [email protected] > > To: [email protected] > > Date: Tue, 26 Nov 2013 16:00:48 -0600 > > Subject: Re: [U2] UvRestore error > > > > Thanks Bob, > > > > I like the idea of using an I-descriptor to DCOUNT on the @ID :) > > > > Cheers > > > > Chris > > > > > > > Date: Tue, 26 Nov 2013 13:58:22 -0800 > > > From: [email protected] > > > To: [email protected] > > > Subject: Re: [U2] UvRestore error > > > > > > One of the ways that I've used in the past to check for @VM's, @SVM's, and @TM's is to do a simple SELECT of the file, a SAVE.LIST, then EDIT.LIST. A simple scan usually shows the errant record ID's because they are usually longer than the rest of the record ID's making them stick out like a sore thumb. > > > > > > You could also make an I-descriptor that just does a DCOUNT on @ID. Then you can simply select the I-descriptor for the "bad" keys. > > > > > > > > > -----Original Message----- > > > From: [email protected] > > > [mailto:[email protected]] On Behalf Of Chris > > > Austin > > > Sent: Tuesday, November 26, 2013 1:50 PM > > > To: U2 Users List > > > Subject: Re: [U2] UvRestore error > > > > > > The examples I posted below appear to be when it builds the INDEX on the table CLIENT. I'm just not sure if it's referring to the actual ID of the record.. or a field inside that CLIENT record? > > > > > > > > > > > > > Date: Tue, 26 Nov 2013 13:44:34 -0800 > > > > From: [email protected] > > > > To: [email protected] > > > > Subject: Re: [U2] UvRestore error > > > > > > > > There appear to be some in the examples you posted. They appear as "ý" in a lot of terminal emulations. You can verify how they appear on your screen by editing one into a record: > > > > > > > > ED BP MV.TEST > > > > I ^253 > > > > > > > > -John > > > > > > > > -----Original Message----- > > > > From: [email protected] > > > > [mailto:[email protected]] On Behalf Of Chris > > > > Austin > > > > Sent: Tuesday, November 26, 2013 1:39 PM > > > > To: U2 Users List > > > > Subject: Re: [U2] UvRestore error > > > > > > > > John, Thanks for the reply. > > > > > > > > I'll write a utility to parse the ID's on that table and see if I find any @VM's.. I did notice some unconventional ID's being used when I did a LIST by ID.. probably best to remove those and re-index. > > > > > > > > Chris > > > > > > > > > > > > > Date: Tue, 26 Nov 2013 13:35:42 -0800 > > > > > From: [email protected] > > > > > To: [email protected] > > > > > Subject: Re: [U2] UvRestore error > > > > > > > > > > I'm just guessing, but I think the problem is a value mark (ASCII 253) embedded in the item IDs. The 3rd party backup software we use also balks at backing up items with value marks in the ID because they're not valid UTF-8 characters. > > > > > > > > > > -John > > > > > > > > > > -----Original Message----- > > > > > From: [email protected] > > > > > [mailto:[email protected]] On Behalf Of Chris > > > > > Austin > > > > > Sent: Tuesday, November 26, 2013 8:16 AM > > > > > To: [email protected] > > > > > Subject: [U2] UvRestore error > > > > > > > > > > Hello, > > > > > > > > > > I noticed an error when doing a UVRESTORE. We have a UniVerse > > > > > region with client information and data. When doing a UVRESTORE > > > > > I get the following > > > > > > > > > > > Restoring c:\CHRIS/I_CLIENT (21:35:56) Restoring > > > > > c:\CHRIS/I_CLIENT/INDEX.000 (21:35:56) Restoring c:\CHRIS/I_CLIENT/INDEX.001 (21:35:58) Unable to write item "Z29880000M82800000ýA38385000 00000000". > > > > > Unable to write item "Z29864873 00000000ýA38385000 00000000". > > > > > Unable to write item "Z29860000R61630000ýA38385000 00000000". > > > > > Unable to write item "Z29860000G57600000ýA38385000 00000000". > > > > > Unable to write item "Z29860000D37000000ýA38385000 00000000". > > > > > Unable to write item "Z29860000C28300000ýA38385000 00000000". > > > > > Unable to write item "Z29860000C26938000ýA38385000 00000000". > > > > > Unable to write item "Z29860000C26700000ýA38385000 00000000". > > > > > > > > > > It looks like it's producing the error when attempting to write the INDEX (I_CLIENT/INDEX.001). > > > > > > > > > > Does anyone know how to fix these types of errors or what they might mean? Thanks. > > > > > > > > > > Chris > > > > > > > > > > > > > > > _______________________________________________ > > > > > U2-Users mailing list > > > > > [email protected] > > > > > http://listserver.u2ug.org/mailman/listinfo/u2-users > > > > > _______________________________________________ > > > > > U2-Users mailing list > > > > > [email protected] > > > > > http://listserver.u2ug.org/mailman/listinfo/u2-users > > > > > > > > _______________________________________________ > > > > U2-Users mailing list > > > > [email protected] > > > > http://listserver.u2ug.org/mailman/listinfo/u2-users > > > > _______________________________________________ > > > > U2-Users mailing list > > > > [email protected] > > > > http://listserver.u2ug.org/mailman/listinfo/u2-users > > > > > > _______________________________________________ > > > U2-Users mailing list > > > [email protected] > > > http://listserver.u2ug.org/mailman/listinfo/u2-users > > > _______________________________________________ > > > U2-Users mailing list > > > [email protected] > > > http://listserver.u2ug.org/mailman/listinfo/u2-users > > > > _______________________________________________ > > U2-Users mailing list > > [email protected] > > http://listserver.u2ug.org/mailman/listinfo/u2-users > > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users > -- > Message protected by DealerGuard: e-mail anti-virus, anti-spam and content filtering. > http://www.pentanasolutions.com > > Click here to report this message as spam: > https://login.mailguard.com.au/report/1IsDPGhbpZ/4B52QgcRopFfRW7ZS0GRvd/1.202 > > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users