PMR.
>
> Del
>
>
>
> "ADSM: Dist Stor Manager" wrote on 06/05/2014
> 05:45:50 AM:
>
> > From: Hans Christian Riksheim
> > To: ADSM-L@vm.marist.edu
> > Date: 06/05/2014 05:46 AM
> > Subject: Re: SQL-backup
Hi Hans,
I agree with you. Please open a PMR.
Del
"ADSM: Dist Stor Manager" wrote on 06/05/2014
05:45:50 AM:
> From: Hans Christian Riksheim
> To: ADSM-L@vm.marist.edu
> Date: 06/05/2014 05:46 AM
> Subject: Re: SQL
Hi,
thanks for the answer.
I may have explained the problem poorly. New try.
If we have in a sqlful.bat script:
tdpsqlc backup * full /configfile=someconfig.cfg
and the file "someconfig.cfg" does not exist, the command runs along with
default config and returns with rc=0.
Problem with that is
Hi,
There is an APAR for this issue -> IC98441. Here's the link to track ->
http://www.ibm.com/support/docview.wss?uid=swg1IC98441
In addition to the fixing levels listed in the APAR link, we are also
planning to to include this APAR in the DP SQL 7.1.0.1 interim fix. This is
targeted for deliver
Alex,
This looks vaguely familiar. Open a PMR with IBM support.
The service team will assist you in resolving the problem.
Thanks,
Del
"ADSM: Dist Stor Manager" wrote on 05/31/2011
09:17:17 AM:
>> From: Alex Amtrup Sørensen
>> To: ADSM-
Hi Eric,
I'm seeing the exact same thing on a few large oracle servers. My hypothesis
was, until I read your e-mail, that we were suffering from severe network
congestion on the server side, causing enough TCP SYN frames to get dropped to
cause this. Unfortunately, I have no proof for my hypoth
Thando,
This is not enough information to troubleshoot this problem.
I suspect some type of configuration problem with
Data Protection for SQL.
What is the result of this command?
TDPSQL QUERY TSM
Does it return valid information?
If so, can you try just using one stripe for backup?
TDPSQ
Thando -
See the ACO5436E and ANS1017E error notes which are collected in
http://people.bu.edu/rbs/ADSM.QuickFacts . These have been seen before.
Begin by reviewing the dsierror.log, and go on to the TSM server
Activity Log
for possibly more info about the session.
Richard Sims
Kevin,
Try searching the IBM knowledge base:
Go to:
www.ibm.com
Search for:
ACO5422E
You will find seven matches. One of them actually shows the error:
[ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead())
Looks like a direct match. The IBM article will point you to
Microsoft
Matt,
You are correct, this is an OS/SQL server issue.
You didn't say which SQL Server SP you were running...
We have seen a few problems lately when people have upgraded to
Windows SP4... and then their SQL backups would hang or fail.
This has been fixed by upgrading to SQL 2000 SP3a.
I am sure
> 01/09/2002 16:15:08 ANR0444W Protocol error on session 17311 for
> node DP4PP2SQL (TDP MSSQL NT) - out-of-sequence
> verb (type Data) received.
Niklas,
A few things to try... make sure you are at the latest TSM API.
I have seen some protocol errors caused by the TSM API level.
I have also se
Are you sure you are using the correct options (.opt) file?
Try using the /TSMOPTFile to ensure you are pointing to
the correct options file...
Thanks,
Bill
William Degli-Angeli
IGS TDP Development
Endicott, NY
(607) 752-6749
TieLine: 852-6749
Internet: [EMAIL PROTECTED]
Bo,
-2147024891 is AccessDenied.
This is a security/permissions/access rights error code.
Does the SQL Server user id used by TDP for SQL have the
SQL Server SysAdmin Fixed Server Role?
Does the Windows NT user id that actually runs the
scheduler for TDP for SQL have admin authority?
The retur
Hi Bo!
Check the tdpsql.log, the dsierror.log and the dsmerror.log. Maybe you will
find more usefull information there?
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: Bo Nielsen [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 27, 2001 12:44
To: [EMAIL P
$)C
Iykim,
You didn't say if you are running version 1 or version 2
of Tivoli Data Protection for Microsoft SQL.
This makes a difference. Look here for requirements:
http://www.tivoli.com/support/storage_mgr/tdp_ms.html#SQL
For your environment, the requirements for
Tivoli Data Protection
Peter,
Did this just started happening? If so, what changed?
Have you ever been able to run a backup with TDP for SQL?
I have seen this happen when the TSM API is backlevel.
Make sure you are running at least 1.1.2 of TDP for SQL.
(The latest version is are available from "ftp.software.ibm.com"
Robert, this is a SQL Server restriction. In the SQL Server Books Online
section "Backing Up the master Database" there is "Note Only full database
backups of master can be created".
To use the command "tdpsqlc backup * log" you can enter an exclude
statement in the TSM options file (default "dsm
You probably have SQL 7.0 Database. We had same problem. There is a patch from
Tivoli. Briefly it is caused by DB's that were 6.0 or 6.5 being upgraded to 7.0 and
Tivoli didn't get info that there is a "compatibility mode" in that some can't
recognize some 7.0 TSQL commands.
David B. Longo
Bo,
This is most likely APAR IC26111. There is a fix for this.
This is FIXTEST Version 1.1.2.01. It includes the following fix:
- IC26111
If a SQL Server 7.0 database is at compatibility level 60 or 65, an
attempt to backup the database or its transaction log would result
in the DB-
Bo, this is a known problem. From the fix's readme:
This is FIXTEST Version 1.1.2.01. It includes the following fix:
- IC26111
If a SQL Server 7.0 database is at compatibility level 60 or 65, an
attempt to backup the database or its transaction log would result
in the
I take it that you create a clone by means other than backup/restore
and that you create a snapshot using EMC hardware or the like.
SQL Server won't let you restore transaction logs unless you've first
restored the database, or at least a database file group or file. Then
you have to restore all
Not answering as an ADSM guy, but addressing the philosophy involved in
protecting a large database...
150 to 500gb? Once an hour? That seems overwhelming, unless I'm
missing something...
We tend to do a two tiered system. We periodically backup everything,
say once per week, with transaction
This from our MS-SQL person who has implemented TDP on a cluster:
>For that large of a database (150-500 GB) there really is no such thing as
>a quick restore. Having a hot spare SQL Server is probably the best
>solution -- i.e. another SQL Server that replicates the production SQL
>Server data
23 matches
Mail list logo
