SQL Anywhere database - Read failed error code: (64)

Author

Read failed error code: (64)

Steve

2005-07-18, 8:23 pm

I'm attempting to use dbsrv9.exe to start a number of
databases. During an attempt to start the database server,
I will receive a bunch of the following errors....

"A read failed error code: (64), the specified network name
is no longer available"

Followed by...

"Unable to start database 'path\to\db.db'"

Can anyone please shed some light on this situation. I
cannot seem to find any reading material on the matter.

Thanks

Chris Keating \(iAnywhere Solutions\)

2005-07-18, 8:23 pm

Are any of the databases or related files running on a network drive (or
share or mapped drive).

<Steve> wrote in message news:42dc03e1.22c2.1681692777@sybase.com...
> I'm attempting to use dbsrv9.exe to start a number of
> databases. During an attempt to start the database server,
> I will receive a bunch of the following errors....
>
> "A read failed error code: (64), the specified network name
> is no longer available"
>
> Followed by...
>
> "Unable to start database 'path\to\db.db'"
>
> Can anyone please shed some light on this situation. I
> cannot seem to find any reading material on the matter.
>
> Thanks

Joshua Savill

2005-07-18, 8:23 pm

Steve,

Is the database file located locally to the physical server, or are you
attempting to start the database from a network share? From the error, it
looks to me like you are attempting to start the database from a network
share, but the share no longer exists. If you are trying to start the
database as a Windows Service, the System does not have access to the
network shares, and therefore cannot find the database files.

**NOTE: It is NOT recommended running the database file and transaction log
across a network share. The database file has a greater chance of becoming
corrupted when running from a network share. It is recommended that the
database file and transaction log be local to the physical server. Not only
will this decrease the chance of database corruption, this will also
increase the performance of the database.**

ASA Database Administration Guide
Backup and Data Recovery
Configuring your database for data protection
Protecting against media failure on the database file

Online:
http://www.ianywhere.com/developer/...n9/00000438.htm

--
Joshua Savill
iAnywhere Solutions - Product Support Analyst

<Steve> wrote in message news:42dc03e1.22c2.1681692777@sybase.com...
> I'm attempting to use dbsrv9.exe to start a number of
> databases. During an attempt to start the database server,
> I will receive a bunch of the following errors....
>
> "A read failed error code: (64), the specified network name
> is no longer available"
>
> Followed by...
>
> "Unable to start database 'path\to\db.db'"
>
> Can anyone please shed some light on this situation. I
> cannot seem to find any reading material on the matter.
>
> Thanks

steve_oquin@hotmail.com

2005-07-18, 8:23 pm

Here's the deal gents. I do believe you are correct in that
I'm attempt to start the engine in the local "c:\program
files\sybase\...\win32" folder, but the the databases are
located on the mapped network drive.

However, I have also attempted to take the databases and
start them in a local folder on the c drive... I will
receive the same error messages.

I can connect through dbeng9.exe with a succesful
connection. I have been able to get into Central and our
application this way. I can also, sometimes, get the engine
to start succesfully. I will then shut the engine down and
attempt again only to see it fail with the same errors.

Pretty wierd stuff going on here.

> Steve,
>
> Is the database file located locally to the physical
> server, or are you attempting to start the database from
> a network share? From the error, it looks to me like you
> are attempting to start the database from a network share
> , but the share no longer exists. If you are trying to
> start the database as a Windows Service, the System does
> not have access to the network shares, and therefore
> cannot find the database files.
>
> **NOTE: It is NOT recommended running the database file
> and transaction log across a network share. The database
> file has a greater chance of becoming corrupted when
> running from a network share. It is recommended that the
> database file and transaction log be local to the physical
> server. Not only will this decrease the chance of
> database corruption, this will also increase the
> performance of the database.**
>
> ASA Database Administration Guide
> Backup and Data Recovery
> Configuring your database for data protection
> Protecting against media failure on the database file
>
> Online:
>
http://www.ianywhere.com/developer/...n9/00000438.htm
>
> --
> Joshua Savill
> iAnywhere Solutions - Product Support Analyst
>
> <Steve> wrote in message
> databases. During an attempt to start the database server
>
>

Joshua Savill

2005-07-18, 8:23 pm

What version and build of SQL Anywhere are you running (dbsrv9 -v)? What OS
is the machine?

--
Joshua Savill
iAnywhere Solutions - Product Support Analyst

<steve_oquin@hotmail.com> wrote in message
news:42dc0b21.2318.1681692777@sybase.com...[color=darkred]
> Here's the deal gents. I do believe you are correct in that
> I'm attempt to start the engine in the local "c:\program
> files\sybase\...\win32" folder, but the the databases are
> located on the mapped network drive.
>
> However, I have also attempted to take the databases and
> start them in a local folder on the c drive... I will
> receive the same error messages.
>
> I can connect through dbeng9.exe with a succesful
> connection. I have been able to get into Central and our
> application this way. I can also, sometimes, get the engine
> to start succesfully. I will then shut the engine down and
> attempt again only to see it fail with the same errors.
>
> Pretty wierd stuff going on here.
>
> http://www.ianywhere.com/developer/...n9/00000438.htm

STEVE

2005-07-18, 8:23 pm

Actually, I think you are absolutely correct. I forgot to
tell my server.cfg file to look at the c drive for the
databases. Once I did that... I can succesfully start them
up again.

Let me try to talk the IT guy into not using a network drive
for the databases...

Thanks for the help

> Steve,
>
> Is the database file located locally to the physical
> server, or are you attempting to start the database from
> a network share? From the error, it looks to me like you
> are attempting to start the database from a network share
> , but the share no longer exists. If you are trying to
> start the database as a Windows Service, the System does
> not have access to the network shares, and therefore
> cannot find the database files.
>
> **NOTE: It is NOT recommended running the database file
> and transaction log across a network share. The database
> file has a greater chance of becoming corrupted when
> running from a network share. It is recommended that the
> database file and transaction log be local to the physical
> server. Not only will this decrease the chance of
> database corruption, this will also increase the
> performance of the database.**
>
> ASA Database Administration Guide
> Backup and Data Recovery
> Configuring your database for data protection
> Protecting against media failure on the database file
>
> Online:
>
http://www.ianywhere.com/developer/...n9/00000438.htm
>
> --
> Joshua Savill
> iAnywhere Solutions - Product Support Analyst
>
> <Steve> wrote in message
> databases. During an attempt to start the database server
>
>

Stephen Rice

2005-07-18, 8:23 pm

STEVE wrote:[color=darkred
]
> Actually, I think you are absolutely correct. I forgot to
> tell my server.cfg file to look at the c drive for the
> databases. Once I did that... I can succesfully start them
> up again.
>
> Let me try to talk the IT guy into not using a network drive
> for the databases...
>
> Thanks for the help
>
>
>
> http://www.ianywhere.com/developer/...n9/00000438.htm
>

here's a doc with some ammo for your conversation with IT

http://www.ianywhere.com/developer/.../> emotely.html

Good Luck

/steve

--
Stephen Rice
Technical Services Manager
iAnywhere Solutions

--- Please Post ---
Whitepapers, Tech Docs, Solved Cases, Bug Fixes and
"Report a bug" are all available on www.ianywhere.com

David Kerber

2005-07-19, 7:23 am

In article <42dc0d55.3834.1681692777@sybase.com>, STEVE says...
> Actually, I think you are absolutely correct. I forgot to
> tell my server.cfg file to look at the c drive for the
> databases. Once I did that... I can succesfully start them
> up again.
>
> Let me try to talk the IT guy into not using a network drive
> for the databases...

Tell him it will dramatically reduce his network traffic <grin>.

.....

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).

Sponsored Links