Re: select on events table question

Yes, what you describe is documented in IC34609, which is related to IC28825. The workaround is to include a hard-coded date as the first filtering criteria in your WHERE clause. Picking a hard-coded date will force the EVENTS table to include all events from that date, after which additional filt

Re: Determining which side of an optical platter a file is on?

Yes, TSM keeps track of where files are on media, but that info is not exposed to customers. In any case, you should not consider attempting physical retrieval of TSM-stored data without TSM due to factors such as any specialized methods by which TSM may have stored the data (which are proprietary

Re: Group collocation

I'm scheduling the following scripts to automatically assign new nodes to a copy group. Utilities available with TSM 5.3 server when dealing with collocation groups. http://www-1.ibm.com/support/docview.wss?rs=100&q1=collocate+group&uid=swg21205433&loc=en_US&cs=utf-8&lang=en john underdown [EMA

Re: Determining which side of an optical platter a file is on?

Thanks for the reply Richard... I'm not considering doing anything unsavvy to get this data back -- I'm using TSM Clients, and the platters must remain in the jukebox so that the data is accessible by end users at the same time this extraction is going on. My goal is to select all data from a si

Re: Determining which side of an optical platter a file is on?

==> On Sat, 15 Oct 2005 12:57:51 -0400, Justin Derrick <[EMAIL PROTECTED]> said: > I'm figuring that doing a query that simply tells me which side of > the platter the data is on, or which offset from the beginning of the > disk (and determining which side it's on by saying a number is > greater t

Error "There is insufficient recovery log space to complete the database transaction"

Good Morning I have an old TSM server running 4.1.1 on a AIX 4.3 server. When I tried to logon this morning I'm receiving an error "Insufficient recovery log spaceThere is insufficient recovery log space to complete the database transaction" What's the best way to recovery from this? Is the

Re: Group collocation

I tried that, but I found I needed to change the collocation group name in the script every 2-3 days. For the time being, it's easier to run the script manually before leaving every afternoon. Original message >Date: Sat, 15 Oct 2005 12:23:58 -0400 >From: John Underdown <[EMAIL PROTECTE

Re: Error "There is insufficient recovery log space to complete the database transaction"

Yes. If you have not hit the max size for version 4, then format and allo9cate a new chunkk of log. If you are at the max, then it's time to RESTORE DB from your last backup. Original message >Date: Sat, 15 Oct 2005 18:31:18 -0400 >From: "Jones, Eric J" <[EMAIL PROTECTED]> >Subject:

Re: Backup error ----Email OK.

...and if that doesn't do it, you may have a funky date/time stamp on a backup of one of the system state or system service files. One way to fix it, per Tivoli support, is to completely remove the filesystems containing those files followed by an immediate backup of same. That seems to fix the pro

Re: Error "There is insufficient recovery log space to complete the database transaction"

Do I just need to allocate additional log space and stop and start TSM or is there additional steps? I don't think I'm close to the max size, the log space was not that large when the system was setup. Thanks for the help, Eric -Original Message- From: ADSM: Dist Stor Manager [mailto:[EM

Re: Error "There is insufficient recovery log space to complete the database transaction"

Follow the Admin Guide manual to perform an Extend Log operation, as a command within a TSM server session, if you can get in, else as a stand-alone operation. You need to to through the usual formatting procedure if the log volume is an OS file, but not if it is a raw logical volume. Richard