Database name is a corrupt file - Veritas Backupexec

I am getting this message while backing up database using
Veritas Software. I need to find what causing this problem.
Thanks,
Mukul Agochiya
magochiya@.hotmail.comThis is the exact wording of error
Operating system error 995(The I/O operation has been
aborted because of either a thre4ad exit or an application
request.)
>--Original Message--
>I am getting this message while backing up database using
>Veritas Software. I need to find what causing this
problem.
>Thanks,
>Mukul Agochiya
>magochiya@.hotmail.com
>.
>|||don't use BE to backup DBs. Backup DBs to files using SQL native tools and
use BE to backup those files to tapes.
"Mukul Agochiya" <magochiya@.hotmail.com> wrote in message
news:13ac01c39258$1667e1f0$a101280a@.phx.gbl...
> I am getting this message while backing up database using
> Veritas Software. I need to find what causing this problem.
> Thanks,
> Mukul Agochiya
> magochiya@.hotmail.com

Database mirroring and Scala ERP system

Hi

We are using in our company an ERP system called iScala.

This software is using SQL server as DBMS.

We would like to use the SQL mirroring feature from SQL 2005.

The software is using the SQL server instance name to connect to databases and when the Main SQL server fails the application can't connect to the Mirror instance.

Unfortunatelly we can't change the connection string (the software is provided by another company).

Do you have a solution?

Thanks

I believe you have to contact the vendor to provide such changes, as this is application issue to talk to the mirror server in the event of failover. If the application is not db mirror aware then you have to find a route from connectivity to talk to other server in such cases.|||

Thanks

You are right.

I'm checking now some solutions for High Availability from Symantec (VERITAS Storage Foundation HA 4.3 for Windows) and Double-Take.

Do you have any information about them?

|||

You could solve this issue using a manual change to DNS.

i.e. MYLIVESQL -> 10.0.0.1 - connection string uses MYLIVESQL as the server name, in the event of a failure you update the DNS record to MYLIVESQL -> 10.0.0.2 (which is the IP address of the mirror server).

Andrew

|||

If the (former) principal instance is still up and running but the database failover occured, then SNAC will automatically learn the location of the mirror and redirect the connection to the mirror, as described here: http://msdn2.microsoft.com/en-us/library/ms366348.aspx. But this works only if the connection string specifies the database and if the principal instance is still running.

But if the vendor is not providing support for mirroring, is highly unlikely that the application will actually work with mirrored database, it may have dependencies outside the database that are not gonna failover (e.g. logins resulting in orphaned users, jobs in msdb etc)

HTH,
~ Remus

|||

Remus,

MOSS 2007 and WSS V3 fall into the category of not supporting mirroring in the connection strings, hence the need to use the cname approach. Microsoft recommend using stsadm to manually change the settings which I think is less elegant.

Andrew

database migration

Hi,
I wonder wether a software or a device (or script) allowing to migrate data
from an existant database to a new database by using correspondant ODBC
drivers existed.
Thanks for your help.How about BACKUP /RESTORE database commans
"ben" <bdugenet@.supralog.com> wrote in message
news:dqieie$rb$1@.news.tiscali.fr...
> Hi,
> I wonder wether a software or a device (or script) allowing to migrate
> data
> from an existant database to a new database by using correspondant ODBC
> drivers existed.
> Thanks for your help.
>

database migration

Hi,
I wonder wether a software or a device (or script) allowing to migrate data
from an existant database to a new database by using correspondant ODBC
drivers existed.
Thanks for your help.
Ben,
Why wouldn't you use possibilities that SQL Server gives you? You can use
backup / restore, Data Transformation Services, ...
Dejan Sarka, SQL Server MVP
Mentor, www.SolidQualityLearning.com
Anything written in this message represents solely the point of view of the
sender.
This message does not imply endorsement from Solid Quality Learning, and it
does not represent the point of view of Solid Quality Learning or any other
person, company or institution mentioned in this message
"ben" <bdugenet@.supralog.com> wrote in message
news:dqieit$s5$1@.news.tiscali.fr...
> Hi,
> I wonder wether a software or a device (or script) allowing to migrate
> data
> from an existant database to a new database by using correspondant ODBC
> drivers existed.
> Thanks for your help.
>

database migration

Hi,

I wonder wether a software or a device (or script) allowing to migrate data
from an existant database to a new database by using correspondant ODBC
drivers existed.

Thanks for your help.Hello Ben,

> I wonder wether a software or a device (or script) allowing to migrate
data
> from an existant database to a new database by using correspondant ODBC
> drivers existed.

Yes, there's such software.

Try our tool, Database Workbench, at www.upscene.com

Here's some info on the Schema Migrator:
http://www.upscene.com/documentatio...emamigrator.htm

--
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com|||ben wrote:
> Hi,
> I wonder wether a software or a device (or script) allowing to migrate data
> from an existant database to a new database by using correspondant ODBC
> drivers existed.
> Thanks for your help.

Do you have some specific problem in mind or is this just a general
enquiry? There are many, many solutions that exist to migrate data
between different data sources. I've included a few links below.
Whether you'll want any of the third party products depends on your
budget and how sophisticated your requirements are.

If you are using SQL Server then first take a look at either using a
linked server or DTS (SQL Server 2000) or Integration Services (SQL
Server 2005). Information on those features can be found in Books
Online.

http://www.microsoft.com/sql/techno...on/default.mspx
www-306.ibm.com/software/data/integration/dis/
www.abinitio.com
www.datamirror.com
www.datawatch.com
www.embarcadero.com/products/dtstudio/index.html
www.informatica.com
www.pervasive.com/solutions/

--
David Portas, SQL Server MVP

Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.

SQL Server Books Online:
http://msdn2.microsoft.com/library/...US,SQL.90).aspx
--

database locking malaise / restarting SQL Server fine points

Our company, primarily a software dev house, also manages an SQL Server
DB for one of our clients. A few days ago, we experienced repeated
timeouts in our .NET web and desktop applications, which threw this
error:
System.Data.SqlClient.SqlException: Timeout expired. The timeout
period elapsed prior to completion of the operation or the server is
not responding.
The timeouts seemed to be caused by locks placed on the database by a
stored proc which adds a new customers, when an order is placed. These
locks could be seen in Enterprise Manager / Management / Current
Activity / Locks, some of the locks' properties pointing to this stored
proc.
Now the strange part: we rebooted the server in question, which had no
apparent effect, ie still lots of locks, timeouts, etc. But a few
hours later, we pushed "Stop" and "Start" in the SQL Server Service
Manager - and everything magically started working again, no further
problems since then (24 hours).
So my key question: when you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
If the answer to these questions is yes, then we can rest a bit easy,
just say the DB got screwy, we had to restart it, but otherwise, we
have some serious investigating to do, to try to prevent this
recurring.
Thanks very much for any advice.
Harlan Wood
sfk3ml4x9w35
_____at_____
thegoldensun.comwhen you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
--both do the same thing, there is nothing that SQL will retain the
locks..in any case, SQL will release the locks..

database locking malaise / restarting SQL Server fine points

Our company, primarily a software dev house, also manages an SQL Server
DB for one of our clients. A few days ago, we experienced repeated
timeouts in our .NET web and desktop applications, which threw this
error:
System.Data.SqlClient.SqlException: Timeout expired. The timeout
period elapsed prior to completion of the operation or the server is
not responding.
The timeouts seemed to be caused by locks placed on the database by a
stored proc which adds a new customers, when an order is placed. These
locks could be seen in Enterprise Manager / Management / Current
Activity / Locks, some of the locks' properties pointing to this stored
proc.
Now the strange part: we rebooted the server in question, which had no
apparent effect, ie still lots of locks, timeouts, etc. But a few
hours later, we pushed "Stop" and "Start" in the SQL Server Service
Manager - and everything magically started working again, no further
problems since then (24 hours).
So my key question: when you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
If the answer to these questions is yes, then we can rest a bit easy,
just say the DB got screwy, we had to restart it, but otherwise, we
have some serious investigating to do, to try to prevent this
recurring.
Thanks very much for any advice.
Harlan Wood
sfk3ml4x9w35
_____at_____
thegoldensun.com
when you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
--both do the same thing, there is nothing that SQL will retain the
locks..in any case, SQL will release the locks..

database locking malaise / restarting SQL Server fine points

Our company, primarily a software dev house, also manages an SQL Server
DB for one of our clients. A few days ago, we experienced repeated
timeouts in our .NET web and desktop applications, which threw this
error:
System.Data.SqlClient.SqlException: Timeout expired. The timeout
period elapsed prior to completion of the operation or the server is
not responding.
The timeouts seemed to be caused by locks placed on the database by a
stored proc which adds a new customers, when an order is placed. These
locks could be seen in Enterprise Manager / Management / Current
Activity / Locks, some of the locks' properties pointing to this stored
proc.
Now the strange part: we rebooted the server in question, which had no
apparent effect, ie still lots of locks, timeouts, etc. But a few
hours later, we pushed "Stop" and "Start" in the SQL Server Service
Manager - and everything magically started working again, no further
problems since then (24 hours).
So my key question: when you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
If the answer to these questions is yes, then we can rest a bit easy,
just say the DB got screwy, we had to restart it, but otherwise, we
have some serious investigating to do, to try to prevent this
recurring.
Thanks very much for any advice.
Harlan Wood
sfk3ml4x9w35
_____at_____
thegoldensun.comwhen you reboot your machine, does SQL server try
to "retain state" in a way that could have retained these locks? And
when you Stop/Start in "Service Manager", is that a different kind of
restart, which may have cleared the state / fixed these issues?
--both do the same thing, there is nothing that SQL will retain the
locks..in any case, SQL will release the locks..