home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.ingres
- Path: sparky!uunet!gatech!concert!uvaarpa!cv3.cv.nrao.edu!mail-to-news-gateway
- From: cor@cs.sun.ac.za (Cor Winckler)
- Subject: Re: Copying Ingres database to another machine?
- Message-ID: <m0nEjk2-000QDxC@cs.sun.ac.za>
- Sender: root@nrao.edu (Operator)
- Organization: National Radio Astronomy Observatory
- Date: Thu, 21 Jan 1993 01:01:30 GMT
- Lines: 34
-
- > >> FETCH error in ii_id: 40100 (E_OO0018) [PRESS RETURN]
- > > in via the reload.
- >
- > Wow. That's not supposed to happen. The error you encountered clearly
- > indicates that you have multiple rows in the ii_id frontend system
- > catalog. You can check this yourself:
- >
- > I'd sure be interested to hear what else you found out about this
- > problem, and if you identified the real cause.
-
- We had this problem once or twice.
-
- The problem is that some people had ING_SET setup with readlock=nolock
- for session. Thus two people could access the ii_id table at the same
- time with no protection for concurrent updates. Euraka ! Duplicates.
-
- We fixed it by physically deleting the smallest object_id in ii_id. That
- fixed the symptom, but the problem is people not knowing what the
- possible consecuences of readlock=nolock could be.
-
- On our site we have applications that were designed to work with
- readlock=nolock, thus everyone has it set up in their environment, and
- few people realise that they need to undo it before going into ABF or
- Vision.
-
- Did something similar happen on your site?
-
- Hope this helps.
-
- --
- Cor
-
- Cor Winckler | Computer Science Departement
- Internet: cor@cs.sun.ac.za | University of Stellenbosch, South Africa
-