Subject | Re: [firebird-support] Network file access |
---|---|
Author | Ann W. Harrison |
Post date | 2004-04-14T22:02:18Z |
At 05:29 PM 4/14/2004, Nathan Ludkin wrote:
local drive. By default NFS mounted drives are not accessible. There's no
theoretical problem with having one server access a database on an NFS
mounted drive. Having two different servers access the same database at
the same time is both a theoretical and a practical disaster.
You can have many processes on a single system access a single database
using the Firebird classic architecture. Their access is co-ordinated
through a single memory resident lock table so they don't collide. Servers
sharing a database on a network mounted drive are unaware of each other's
existence and rapidly corrupt the database.
The best solution is to install a copy of Firebird on BSLX2K301.
Regards,
Ann
>I have a firebird server running on my local machine.That's normal. Firebird requires that the server access a database on a
>However, if I change the connection string to a database on a mapped network
>drive i.e. G: when connecting I get the error ""Unable to complete network
>request to host BSLX2K301" where BSLX2K301 is the machine name of the
>windows machine where the share is located.
local drive. By default NFS mounted drives are not accessible. There's no
theoretical problem with having one server access a database on an NFS
mounted drive. Having two different servers access the same database at
the same time is both a theoretical and a practical disaster.
You can have many processes on a single system access a single database
using the Firebird classic architecture. Their access is co-ordinated
through a single memory resident lock table so they don't collide. Servers
sharing a database on a network mounted drive are unaware of each other's
existence and rapidly corrupt the database.
The best solution is to install a copy of Firebird on BSLX2K301.
Regards,
Ann