Karen, When I reply to your post it does not seem to go through, let's see if this one does...
This is what I posted: Karen, You missed one step. The first thing I did after I downloaded was a RELOAD which recreated the database minus OWNER and PASSWORD. I simply added the OWNER and PASSWORD. My database is named PMSDB. I did: RELOAD PMSDB_NEW After the new version was created, I renamed the original to PMSDB_ORIG and the newly created PMSDB_NEW to the original name of PMSDB. The newly created version did not have an OWNER or PASSWORD assigned like the original did (apparently RELOAD strips these off) so I had to add those, obviously if you database does not have them you don’t need this step. I tested it locally by opening several concurrent sessions and it worked fine so I uploaded it to their server and it worked correctly after that. BTW, the first thing I did was to make sure that there were no open connections/files on the server, but this step did not help with the original problem. Javier, Javier Valencia, PE O: 913-829-0888 H: 913-397-9605 C: 913-915-3137 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Javier Valencia Sent: Tuesday, October 13, 2015 9:51 AM To: [email protected] Subject: [RBASE-L] - Re: connection Interesting. I ran into a similar problem 3 weeks ago when users were unable to connect to the database and it appeared that MULTI was changed to OFF. I would get an error along the lines of ...the database is opened in a state that does not allow you to connect...or words to that effect. I downloaded the database to my computer where I could access it but was unable to get it to behave. R:Scope showed no problems. I had a post ready for the List when I decided to do a RELOAD and then added the owner and password and it worked fine after that; a few records were missing as well which would appear to indicate network drive problem. I am still not sure why it happened but my bests guess is that a network (drive) glitch affected the setting somehow. In short, while I do not have an answer why it happened, I did find a workaround to get it back in service. Hopefully it can help you as well. Javier, Javier Valencia, PE O: 913-829-0888 H: 913-397-9605 C: 913-915-3137 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle Sent: Tuesday, October 13, 2015 8:59 AM To: [email protected] Subject: [RBASE-L] - Re: connection Karen, WOW! That is strange. I do think it has to do with the network connect as well. I also looked at the settings when connected to my C drive and the multi was on as it should be. We use a compiled application so the DB settings on the server is the only concern we should have. Someone on site will have to care for this since I am out of the area. I forwarded your response to him. Thanks again. James Belisle Making Information Systems People Friendly Since 1990 [cid:[email protected]] From: [email protected] [mailto:[email protected]] On Behalf Of Karen Tellef Sent: Tuesday, October 13, 2015 8:47 AM To: Jim Belisle Subject: [RBASE-L] - Re: connection How funny this is happening to you, it's happening to me as we speak. Someone was connected to the database when apparently a network connection issue happened. Now no one can connect, getting a "database is unavailable" command. Network shows no one as having the database open. I can copy it to my c: drive, database is healthy, reloaded. I copy it back up to the network and only the first person who connects to it can see it. All others are then locked out. To make sure it's done right, I copy it up, get to the R> prompt, set multi on, connect to it, check my staticdb setting, no issue. No one else can connect. Copy it back up, have someone else connect, same issue. It's as if there's an internal "set multi off" command. This happened at that client once before, last year. We had to reboot the server and restore a backup copy from before it happened. Then it worked fine, but we had to do both. We're about to do this again but have to wait til overnight. So check the staticdb settings for everyone trying to connect, see if only the first person can connect and locks out others. Or the big one -- backup and reboot. Karen -----Original Message----- From: Jim Belisle <[email protected]<mailto:[email protected]>> To: karentellef <[email protected]<mailto:[email protected]>> Sent: Tue, Oct 13, 2015 8:36 am Subject: [RBASE-L] - connection Early this morning, my office people were able to connect to RBASE as normal. Our shop people started having problems, then RBASE got disconnected from the server. Since that time, no one has been able to connect to the database. I checked all aspects of the DB with RSCOPE and no errors showed up. I copied the DB to my C drive and was able to connect just fine. I did a rebuild on the C drive and no errors came up. Two questions: 1) Is it possible the server just will not connect RBASE properly for some reason? (all other server based programs are working.) 2) If I remember correctly, I will not be able to overwrite the G based DB with my rebuilt C based DB if the DB "sees" a connection. How then to correct that problem if my DB thinks it is in a multi off mode? James Belisle Making Information Systems People Friendly Since 1990 [cid:[email protected]<mailto:[email protected]>]
