Excluding off-line SQL databases and StatusError768

[banched]

We have a W2K cluster with TDP for SQL 2.2.1. Recently 2 of the 9 SQL databases were taken off-line, and are no longer to be used.



This means that whenever the TDP runs the backup, it tries to include the off-line databases. The error in the log file is as follows (the databases are called UMR2k and UMRfinish):



06/05/2003 15:52:09 Backup of SQL Database UMR2K will not be attempted.

06/05/2003 15:52:09 SQL Database Status: StatusError768

06/05/2003 15:52:09 ACO5422E Received the following from the MS SQL server:

06/05/2003 15:52:09 [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'UMR2K' cannot be opened because it is offline. Microsoft SQL-DMO (ODBC SQLState: 42000) (HRESULT:0x800403ae)

06/05/2003 15:52:09 Backup of SQL Database UMRfinish will not be attempted.

06/05/2003 15:52:09 SQL Database Status: StatusError768

06/05/2003 15:52:09 ACO5422E Received the following from the MS SQL server:

06/05/2003 15:52:09 [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'UMRfinish' cannot be opened because it is offline. Microsoft SQL-DMO (ODBC SQLState: 42000) (HRESULT:0x800403ae)







I have tried editing the dsm.opt file to use EXCLUDE statements, but it doesn't make any difference. Examples of my efforts are:



EXCLUDE "\MPLVSQL1\MPLVSQL1\UMR2K"

EXCLUDE "\MPLVSQL1\MPLVSQL1\data\UMR2K"

EXCLUDE "\MPLVSQL1\MPLVSQL1\meta\UMR2K"

EXCLUDE "\...\UMR2K\*"

EXCLUDE "\...\UMRfinish\...\log*"

EXCLUDE "\...\UMRfinish\...\*"

EXCLUDE "*:\UMR2K_data.mdf"







Has anyone experienced the same? Tivoli support appear to have had similar cases logged, but no-one has an answer which proves to work (as yet).

 

[rscherrer47]

:-o Dont know if you have tried this but in the sqlcmd do you still have those databases included?????????? If so, that may be the issue, versus the dsm.opt file exclusions, so edit the sqlcmd file and then try.

 

[stenbs]

I may be stating the obvious here, but did you remember to restart the scheduler service after editing the dsm.opt file?

 

[sgabriel62]

Along with the scheduler, take a look into your SQL server and see if there are any schedules still active. Perhaps disable their ODBC drivers on those machines.

Check your dsm.opt to see if you are polling or being prompted. If you are polling

change to prompted. At the TSM server level, you could also remove the client's association with a schedule.



Good luck



Steven

 

[mokados]

SOLVED

this problem is solved with the TDP SQL 5.5 versions. You can exclude the databases using /EXCLUDEDB.

Read this for more info:

https://www-304.ibm.com/support/docview.wss?uid=swg21269094