Steve,
Did you know that you CAN perform the following house keeping functions in a Multi-User environment IF using the latest R:BASE 6.5++ (Build:1.866xRT03), R:BASE 7.0 and R:Tango 5.0?
. PACK INDEX FOR TableName This will pack all the indices for the specified table, even in a Multi-User environment.
. PACK INDEX This will pack all the indices for currently CONNected database, even in a Multi-User environment.
. PACK PASSWORD command is also supported in a multi-user session.
Very Best R:egards,
Razzak.
At 02:16 PM 11/17/2003 -0600, Steve Folgelson wrote:
Thanks for the info.
Any other way to do this? I forgot to mention that I have a number of apps using R:Tango and would not want to shut them all down.
Thanks
Steve
-----Original Message----- From: A. Razzak Memon [mailto:[EMAIL PROTECTED] Sent: Monday, November 17, 2003 2:11 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: R:Tango Temp Files - Razzak's Reply
Steve,
Once you stop the R:Tango service all R:Tango connections should also stop to free up R:BASE database for in-house maintenance.
You'll need to check for any other non R:Tango users accessing the same database on the network.
At the R> prompt, type:
LIST
You'll notice the following:
Number of Tables in Database dbname is xxx. Number of Columns in Database dbname is xxx. Number of Indexes in Database dbname is xxx. Number of users connected: xxx.
If the number of users connected is 1, that's you, the only connected user to that database. If more than 1, then you have to look for the connected workstation(s).
You can also use (CVAL('CONNECTIONS')) function to find the number of users connected to the same database.
If you are the only one, then try the following at the R> prompt:
DISCONNECT SET MULTI OFF CONNECT dbname RELOAD newdb DISCONNECT DELETE dbname.rb? RENAME newdb.rb? dbname.rb? EXIT
Now you can do some in-house maintenance, including the cleanup of *.$$$ files, etc.
Hope that helps!
Very Best R:egards,
Razzak.
At 01:30 PM 11/17/2003 -0600, Steve Fogelson wrote:
>Razzak, > >Thanks for the quick response. As a follow-up question, I have noticed that >when I try to delete these files, some cannot be deleted as a "session" is >in progress. And I can't move, delete, or copy over the DB files. I have to >wait until I can delete the temp files before I can do perform the above. > >In a production environment, this won't be a good practice anyway. But is >there a way to "close" the database which would not allow any new >connections and/or close existing connections. > >I would like to be able to maintain the DB. IE: Pack (Pack involving connect >to the DB in a single user mode), backup (close the application during the >morning hours), etc. > >Thanks > >Steve > >-----Original Message----- >From: A. Razzak Memon [mailto:[EMAIL PROTECTED] >Sent: Monday, November 17, 2003 12:32 PM >To: RBASE-L Mailing List >Subject: [RBASE-L] - Re: R:Tango Temp Files - Razzak's Reply > > >Steve, > >Update the correspondent RBASE.CFG and OTERRO.CFG >files to include the following: > >Steps: > >01. Locate the RBASE.CFG and OTERRO.CFG files on > Win2K Server > >02. Using the text editor, such as NOTEPAD, edit > both files and search for SCRATCH ON > > (approximately on line 25 in RBASE.CFG and > line 16 in OTERRO.CFG) > > Insert the line right after SCRATCH ON and > type the following: > > SCRATCH C:\Temp > > or use appropriate directory on Win2K Server > with full read/write/delete privileges > > So, the RBASE.CFG and OTERRO.CFG files should > look like the following: > > SCRATCH ON > SCRATCH C:\TEMP > >03. Save the file > >04. STOP R:Tango Service > > Clean (Delete) all *.$$$ files > >05. START R:Tango Service > >That's all there is to it! > >Enjoy and make sure to have fun. > >Very Best R:egards, > >Razzak. > >At 11:54 AM 11/17/2003 -0600, Steve Fogelson wrote: > > >I am using R:Tango 2000, R:Base 6.5, Win2K server > > > >Not sure what these are supposed to be called. A > >sample is 3fb900d2.$$$. I believe a couple are > >created for each user. > > > >Is there a way to define what folder in a web site > >these should be located? > >They presently are created in the root directory. > >It gets to be quite messy.
