ODP: adsm restore problem
use tsm instead adsm -Wiadomo oryginalna- Od: Roland Priest [mailto:[EMAIL PROTECTED] Wysano: 13 lutego 2004 14:41 Do: [EMAIL PROTECTED] Temat: adsm restore problem we have a problem restore a back from adsm this morning the is using adms the gig card.. root su - sbl2008v db2 restore db db2008v use adsm. ( into db2008v redirect) this error we get SQL2032N The 14 parameter is not valid. what does this mean thanks Roland Priest AIX Administrator email [EMAIL PROTECTED] office 856-489-4255 office 1800-767-5822 ext.4255 Cell 856-296-6086
ODP: TDP for MSSQL - huge problem
Hi folks, current vaules for commtimeout and idletimout are 1200 and 180. i don't think that increasing these vaules solve my problem. maybe it will stop writing in logs that kind of errors but please remember that i cannot backup up my whole database (ms sql) environment. log for that operation (for scheduled operations only) looks like that : Beginning full backup for database model, 13 of 21. Full: 0 Read: 867840 Written: 867840 Rate: 617.71 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 357.81 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 251.70 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 194.13 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 157.99 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 133.20 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 115.13 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 101.38 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 90.56 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 81.83 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 74.63 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 68.60 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 63.47 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 59.05 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 55.21 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 51.84 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 48.86 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 46.20 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 43.81 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 41.66 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 39.71 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 37.94 Kb/Sec ... Full: 0 Read: 869104 Written: 869104 Rate: 0.74 Kb/Sec so as u can see, the transfer is going lower and lower so the backup operation couldn't finish proper. all the time it stops on database model (msdb). manualy i can backup it without any problems. what's wrong? have u seen similar problem? p.s. oh i almoust forget - i'm using storageagent in version 5.1.7.0. this database server is connected to the san. -Wiadomo oryginalna- Od: alkina [mailto:[EMAIL PROTECTED] Wysano: 29 paYdziernika 2003 10:44 Do: [EMAIL PROTECTED] Temat: Re: TDP for MSSQL - huge problem In dsmserv.opt increase the value of two parameters 1. commtimeout 3000 2. idletimeout some suitable value. Regards Alkina L ADSM: Dist Stor Manager wrote: gt;4 more than one week I've been receiving the error code listed below during gt;my night backup process on MS SQL 7 (NT 4.0): gt; gt;28-10-2003 07:58:40 ANS1512E Scheduled event 'MARTINI_SQLFULL' failed. gt;Return code = -1073741510. gt;28-10-2003 07:58:41 ANS1005E TCP/IP read error on socket = 1320, errno = gt;10054, reason : 'Unknown error'. gt;28-10-2003 07:58:45 ANS1005E TCP/IP read error on socket = 656, errno = gt;10054, reason : 'Unknown error'. gt; gt;The scheduled backup completes just few databases but always stop on msdb. gt;The problem doesn't occur when I start up backup manualy. gt;Yesterday I upgraded the TDP client to the latest 5.2.1 version. It didn't gt;solve this problem. gt;What can I do next? Have u evere had similar problem? gt;Waitin' for some suggestion from ya wizards:-) Sebastian - The 10054 TCP/IP errno reflects a connection being reset by peer, which in TSM terms means that the server terminated the session with the client. Thus, the place to look is in the server Activity Log, which should explain why it did so. It may be that server timeout values are too low. Richard Sims, BU Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for Air Tickets on Air Sahara Flights. For Best Deals, log on to http://airsahara.indiatimes.com and Bid Now !
ODP: ODP: TDP for MSSQL - huge problem
Del, so why manual start backup process finished proper? by the way i have got all latest sp's applied. -Wiadomo oryginalna- Od: Del Hoobler [mailto:[EMAIL PROTECTED] Wysano: 29 paYdziernika 2003 14:40 Do: [EMAIL PROTECTED] Temat: Re: ODP: TDP for MSSQL - huge problem Sebastian, We have seen a hang like this recently when service has been applied to the operating system. The fix for this has been to apply and/or reapply the latest service packs to SQL Server. In most cases, this has been to apply SP3 or SP3a to SQL Server 2000. I see that you are on NT4 and SQL 7. So, you should make sure the latest service packs are applied to the NT 4 and to the SQL 7 Server. If the problem still persists after doing so, please call IBM support. Thanks, Del current vaules for commtimeout and idletimout are 1200 and 180. i don't think that increasing these vaules solve my problem. maybe it will stop writing in logs that kind of errors but please remember that i cannot backup up my whole database (ms sql) environment. log for that operation (for scheduled operations only) looks like that :
ODP: ODP: ODP: TDP for MSSQL - huge problem
Del - u're completely right that it's very difficult to solve this problem in the way i'm trying to do it. But this list is the best knowledge base I have ever seen. So that's why I'm trying to ask u guys about problems I have just seen. by the way below is result of dbcc checkdb : CHECKDB found 0 allocation errors and 0 consistency errors in database 'msdb'. According to Richard recomendation I have changed COMMtimeout values. we will see thanks for all the replies. sebastian -Wiadomo oryginalna- Od: Del Hoobler [mailto:[EMAIL PROTECTED] Wysano: 29 paYdziernika 2003 15:17 Do: [EMAIL PROTECTED] Temat: Re: ODP: ODP: TDP for MSSQL - huge problem Sebastian, I don't know for sure. I haven't seen the configuration of your system. It could have something to do with the default network path connection to the SQL server... which may be different when running from a different userid... if you have set it up that way on your system. Maybe it uses pipes in one case and TCP/IP in another. I really think the best way for you to get this resolved is to place a call with IBM support. It is very difficult to solve something like this without getting more details about your setup and configuration. Thanks, Del so why manual start backup process finished proper? by the way i have got all latest sp's applied.
TDP for MSSQL - huge problem
Hi, 4 more than one week I've been receiving the error code listed below during my night backup process on MS SQL 7 (NT 4.0): 28-10-2003 07:58:40 ANS1512E Scheduled event 'MARTINI_SQLFULL' failed. Return code = -1073741510. 28-10-2003 07:58:41 ANS1005E TCP/IP read error on socket = 1320, errno = 10054, reason : 'Unknown error'. 28-10-2003 07:58:45 ANS1005E TCP/IP read error on socket = 656, errno = 10054, reason : 'Unknown error'. The scheduled backup completes just few databases but always stop on msdb. The problem doesn't occur when I start up backup manualy. Yesterday I upgraded the TDP client to the latest 5.2.1 version. It didn't solve this problem. What can I do next? Have u evere had similar problem? Waitin' for some suggestion from ya wizards:-) Regards, Sebastian
ODP: TDP for MSSQL - huge problem
sth wrong happend cause i cannot see it on adsm list. send it once again. -Wiadomosc oryginalna- Od: Sebastian Szumczyk Wyslano: 28 paYdziernika 2003 11:57 Do: 'ADSM: Dist Stor Manager' Temat: TDP for MSSQL - huge problem Hi, 4 more than one week I've been receiving the error code listed below during my night backup process on MS SQL 7 (NT 4.0): 28-10-2003 07:58:40 ANS1512E Scheduled event 'MARTINI_SQLFULL' failed. Return code = -1073741510. 28-10-2003 07:58:41 ANS1005E TCP/IP read error on socket = 1320, errno = 10054, reason : 'Unknown error'. 28-10-2003 07:58:45 ANS1005E TCP/IP read error on socket = 656, errno = 10054, reason : 'Unknown error'. The scheduled backup completes just few databases but always stop on msdb. The problem doesn't occur when I start up backup manualy. Yesterday I upgraded the TDP client to the latest 5.2.1 version. It didn't solve this problem. What can I do next? Have u evere had similar problem? Waitin' for some suggestion from ya wizards:-) Regards, Sebastian
Error logs - storage agents
Hi, Plenty of times a day I receive error logs from TSM according to Storage Agents sessions. For insance : 2003-07-01 07:39:19 ANR3605E Unable to communicate with storage agent. 2003-07-01 07:39:20 ANR0479W Session 67 for server STA_ORNELLA (Windows) terminated - connection with server severed It fills up the TSM logs (100 lines a day), so it's going to be very dificult to find interested me entries. If u know what is it and how to solve the problem I will be appreciate. Regards, Sebastian
ODP: Error logs - storage agents
Karel, Thx for so quick reply but let me explain sth. I have got a problem with SAN not LAN clients. The difference is, that SAN switch doesn't allow me to change duplex and network speed values. SAN configuration is based on Dell EMC2 and 56F Switch. TSM ver. 5.1 is configured on AIX 5.1. I haven't got any network problems, no delays or interruption with communication through SAN. U descibed that this problem could be caused but not so stable communication. Can u describe it, cause I got a problem with understanding what u exactly mean? WAN can cause such a problems, but SAN works a little bit in a different way. Waiting for reply, Sebastian -Wiadomo oryginalna- Od: Karel Bos [mailto:[EMAIL PROTECTED] Wysano: 1 lipca 2003 09:52 Do: [EMAIL PROTECTED] Temat: Re: Error logs - storage agents Hi, ANR3605E Unable to communicate with storage agent. Explanation: The database server was attempting to communicate with the storage agent but was unable to do so. System Action: The database server operation fails. User Response: Check the configuration of the storage agent and server to ensure that communication parameters are correct ANR0479W Session session number for server server name (server platform) terminated - connection with server severed. Explanation: If server A has opened a connection with server B, server B's session is ended because the communications link has been closed by a network error or by server A's program. System Action: Server A continues operation. User Response: If server B halts operation or in some way stops communicating with server A, this message will be displayed on server A indicating that the connection was closed suddenly by server B. A network failure can also cause this message to be displayed. If a large number of these messages occur simultaneously, check the network for failure and correct any problems As you can see both error messages point to failures to communicate. It looks like the network connection between both machines is not that stable. So you are back to basics. Look if the network is configured correctly (no auto but 10/100 mb full/half duplex on the network speed), look at the switch setting and let things match. This should make live much easier. Regard, Karel p.s. It helps if the config specs (TSM Server OS, TSM Server Levels etc.) are mentioned. -Oorspronkelijk bericht- Van: Sebastian Szumczyk [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 1 juli 2003 9:39 Aan: [EMAIL PROTECTED] Onderwerp: Error logs - storage agents Hi, Plenty of times a day I receive error logs from TSM according to Storage Agents sessions. For insance : 2003-07-01 07:39:19 ANR3605E Unable to communicate with storage agent. 2003-07-01 07:39:20 ANR0479W Session 67 for server STA_ORNELLA (Windows) terminated - connection with server severed It fills up the TSM logs (100 lines a day), so it's going to be very dificult to find interested me entries. If u know what is it and how to solve the problem I will be appreciate. Regards, Sebastian
