%META:TOPICPARENT{name="ErrorMessagesU"}%

==Error Messages (U)==

[[UDAErrorMessages|A]] [[ErrorMessagesB|B]] [[ErrorMessagesC|C]] [[ErrorMessagesD|D]] [[ErrorMessagesE|E]] [[ErrorMessagesF|F]] [[ErrorMessagesG|G]] [[ErrorMessagesH|H]] [[ErrorMessagesI|I]] [[ErrorMessagesJ|J]] [[ErrorMessagesK|K]] [[ErrorMessagesL|L]] [[ErrorMessagesM|M]] [[ErrorMessagesN|N]] [[ErrorMessagesO|O]] [[ErrorMessagesP|P]] [[ErrorMessagesQ|Q]] [[ErrorMessagesR|R]] [[ErrorMessagesS|S]] [[ErrorMessagesT|T]] [[ErrorMessagesU|U]] [[ErrorMessagesV|V]] [[ErrorMessagesW|W]] [[ErrorMessagesX|X]] [[ErrorMessagesY|Y]] [[ErrorMessagesZ|Z]] [[ErrorMessagesSymbols|#]]

===Unable to open or create . lg, error 2. (2257)===

If you receive "Unable to open or create dbname.lg" errors, take the following action:

1. Login to your Progress database server. Use the Progress user id. 
2. cd into the directory which contains your actual Progress database. For example:

{{{
$ cd /usr/lpp/progress/dbs/
}}}

3. Type ls, and see if the .lg file exists. For example:

{{{
$ ls demo.b1 demo.d1 demo.db demo.lg
}}}

4. If the .lg file exists, use chmod to insure that the <nop>OpenLink user has write privileges on the .lg file. For example:

{{{
$ chmod a=w demo.lg
}}}

5. If the .lg file does not exist, create an empty .lg file in your Progress database directory. Then, use chmod to provide write privileges. For example:

{{{
$ touch demo.lg $ chmod a=w demo.lg
}}}

6. Test.


===Evidence===

Request Broker Log