nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Teamsite Store

leoankit

Hi,

I recovered a Teamsite store from Tape backups. That Teamsite server has been de-commisioned. Its a TS 6.5 store. After getting the store directory from /iw-store, I tried activating the store using "iwstoreadm" and the store activated but after some days , store de-activated by itself. Now when I am trying to activate it again , I m getting error :"Unable to activate store: I/O error" .
In the trace log I saw this error :

Store /iw-store/wholesalebup: 1 objects found in the log file.
[Thu Feb 4 15:45:16 2010] Storage Manager: unable to create directory /iw-store/wholesalebup/d3/d4d/d57 error 13
[Thu Feb 4 15:45:16 2010] Storage Manager: Retrying to create directory /iw-store/wholesalebup/d3/d4d/d57
[Thu Feb 4 15:45:17 2010] Storage Manager: unable to create directory /iw-store/wholesalebup/d3/d4d/d57 error 13
[Thu Feb 4 15:45:17 2010] Storage Manager: Retrying to create directory /iw-store/wholesalebup/d3/d4d/d57
[Thu Feb 4 15:45:18 2010] Storage Manager: unable to create directory /iw-store/wholesalebup/d3/d4d/d57 error 13
[Thu Feb 4 15:45:18 2010] Storage Manager: Retrying to create directory /iw-store/wholesalebup/d3/d4d/d57
[Thu Feb 4 15:45:19 2010] Storage Manager: unable to create directory /iw-store/wholesalebup/d3/d4d/d57 error 13
[Thu Feb 4 15:45:19 2010] TModification::Commit: WritePoint failed: object ID = 34D5700, data size = 20
[Thu Feb 4 15:45:19 2010] Store /iw-store/wholesalebup: recovery failed, store is disabled.
[Thu Feb 4 15:45:19 2010] Failed to activate store 0x7b wholesalebup
[Thu Feb 4 15:45:19 2010] Shut down invalid store 0x7b at "/iw-store/wholesalebup"

When I check in /iw-store/wholesalebup/d3/d4d/ directory , there is no directory as "d57" .

Current TS server where I m activating the store is a 6.7.1 and the store is of 6.5. When I activated this store for the very first time, it activated but not anymore. Need help !

Regards,
Ankit

Find more posts tagged with

Comments

Adam Stoller

To put it simply: Any time you have a backing store problem - you should contact Support immediately!

You will probably have to try running iwfsck on it - but I'd do so under Support's guidance rather than relying on any [other] advice given here (regardless of the knowledge or good intentions of the individual)

Adam Stoller

On a related note (perhaps)...

I'm working at a customer site where they have 6.5SP2 on W2K3 and we're doing a fresh-install/upgrade to 6.7.2SP2P1 on new W2K3 servers.

We took a copy of the 6.5 backing store and placed it on a NAS box and mapped a drive to that NAS box on the new 672 server.

I ran [672] iwfsck -d -nofmtchk on the copy of the 65 backing store and it came back clean (the

-nofmtchk

option was needed because there was no FORMAT directory in the backing store copy - not sure about that...)

I then made the requisite entries in the 672 iw.cfg file to be able to reference the 6.5 backing store copy as "65", ran iwreset, and then tried:
iwstoreadm -a 65

and I got: Unable to activate store: I/O error

Nothing seems to have been written to any log files though.

I have a case open with Support. If I hear anything back I'll let you know.

Crsb

On a related note (perhaps)...

I'm working at a customer site where they have 6.5SP2 on W2K3 and we're doing a fresh-install/upgrade to 6.7.2SP2P1 on new W2K3 servers.

We took a copy of the 6.5 backing store and placed it on a NAS box and mapped a drive to that NAS box on the new 672 server.

I ran [672] iwfsck -d -nofmtchk on the copy of the 65 backing store and it came back clean (the
-nofmtchk
option was needed because there was no FORMAT directory in the backing store copy - not sure about that...)

I then made the requisite entries in the 672 iw.cfg file to be able to reference the 6.5 backing store copy as "65", ran iwreset, and then tried:
iwstoreadm -a 65

and I got: Unable to activate store: I/O error

Nothing seems to have been written to any log files though.

I have a case open with Support. If I hear anything back I'll let you know.

This is interesting, I thought upgrading from 6.5 SP2/3 to 6.7.2 is documented and supported.
Do you have to run iwstoreadm -a? I don't remember having to active the store in similar scenario. I just shutdown TS > point it to the store you want to use -> start TS and TS should start with active store.

Migrateduser

On a related note (perhaps)...

I'm working at a customer site where they have 6.5SP2 on W2K3 and we're doing a fresh-install/upgrade to 6.7.2SP2P1 on new W2K3 servers.

We took a copy of the 6.5 backing store and placed it on a NAS box and mapped a drive to that NAS box on the new 672 server.

I ran [672] iwfsck -d -nofmtchk on the copy of the 65 backing store and it came back clean (the
-nofmtchk
option was needed because there was no FORMAT directory in the backing store copy - not sure about that...)

I then made the requisite entries in the 672 iw.cfg file to be able to reference the 6.5 backing store copy as "65", ran iwreset, and then tried:
iwstoreadm -a 65

and I got: Unable to activate store: I/O error

Nothing seems to have been written to any log files though.

I have a case open with Support. If I hear anything back I'll let you know.

I'm assuming you've seen these articles.

https://customers.autonomy.com/support/secure/docs/FAQ/Interwoven/57880.html

https://customers.autonomy.com/support/secure/docs/FAQ/Interwoven/60617.html

Adam Stoller

This is interesting, I thought upgrading from 6.5 SP2/3 to 6.7.2 is documented and supported.
Do you have to run iwstoreadm -a? I don't remember having to active the store in similar scenario. I just shutdown TS > point it to the store you want to use -> start TS and TS should start with active store.

If I was just upgrading an existing implementation - I'd probably be okay, but we're changing servers as well as upgrading so there's a fresh installation of 6.7.2 on one server and an old installation of 6.5 on another server.

The backing store format changed [slightly?] between 6.5 and 6.7.2 such that you should do an iwmigrate.

I prefer to do my migrations from a copy of the store on the same server.
The process I've gone through (thus far) is the same one I've used to handle upgrading from 5.5.2 to a fresh installation of 6.7.2 without any [significant] problems. It should work.

Adam Stoller

I'm assuming you've seen these articles.

https://customers.autonomy.com/support/secure/docs/FAQ/Interwoven/57880.html

https://customers.autonomy.com/support/secure/docs/FAQ/Interwoven/60617.html

Yes - but both of those articles relate to Solaris - I'm on Windows.
The only aspect of it which might apply is that the 6.5 store was originally on a partition of the actual 6.5 server, whereas the copy (and the new 6.7.2 store) are on a NAS device rather than being on a partition of the actual server. As such, a domain account is used to access the 6.7.2 store (see KB 49040 I believe).

We'll see what Support has to say if/when they get back to me (hopefully by Monday)

mart2001

Do you have that copied of the backing store? You should run iwfsck on it. Plus, do it with support and send them the iwfsck output to determine what the error could be.

Hi,

I recovered a Teamsite store from Tape backups. That Teamsite server has been de-commisioned. Its a TS 6.5 store. After getting the store directory from /iw-store, I tried activating the store using "iwstoreadm" and the store activated but after some days , store de-activated by itself. Now when I am trying to activate it again , I m getting error :"Unable to activate store: I/O error" .
In the trace log I saw this error :
Store /iw-store/wholesalebup: 1 objects found in the log file.
[Thu Feb 4 15:45:16 2010] Storage Manager: unable to create directory /iw-store/wholesalebup/d3/d4d/d57 error 13
[Thu Feb 4 15:45:16 2010] Storage Manager: Retrying to create directory /iw-store/wholesalebup/d3/d4d/d57
[Thu Feb 4 15:45:17 2010] Storage Manager: unable to create directory /iw-store/wholesalebup/d3/d4d/d57 error 13
[Thu Feb 4 15:45:17 2010] Storage Manager: Retrying to create directory /iw-store/wholesalebup/d3/d4d/d57
[Thu Feb 4 15:45:18 2010] Storage Manager: unable to create directory /iw-store/wholesalebup/d3/d4d/d57 error 13
[Thu Feb 4 15:45:18 2010] Storage Manager: Retrying to create directory /iw-store/wholesalebup/d3/d4d/d57
[Thu Feb 4 15:45:19 2010] Storage Manager: unable to create directory /iw-store/wholesalebup/d3/d4d/d57 error 13
[Thu Feb 4 15:45:19 2010] TModification::Commit: WritePoint failed: object ID = 34D5700, data size = 20
[Thu Feb 4 15:45:19 2010] Store /iw-store/wholesalebup: recovery failed, store is disabled.
[Thu Feb 4 15:45:19 2010] Failed to activate store 0x7b wholesalebup
[Thu Feb 4 15:45:19 2010] Shut down invalid store 0x7b at "/iw-store/wholesalebup"
When I check in /iw-store/wholesalebup/d3/d4d/ directory , there is no directory as "d57" .

Current TS server where I m activating the store is a 6.7.1 and the store is of 6.5. When I activated this store for the very first time, it activated but not anymore. Need help !

Regards,
Ankit

paul_iwov

Hi,

I believe you are trying to create branch here in your 6.5 store, even if it'z a 6.5 store which is running on TS 6.7.1 version , we would be able to work on the contents, But when you have arrived at the below error, I would recommend you to run iwmigrate on the 6.5 store and make the store compatible to your current version of Teamsite.

-----------
[Thu Feb 4 15:45:18 2010] Storage Manager: unable to create directory /iw-store/wholesalebup/d3/d4d/d57 error 13
[Thu Feb 4 15:45:18 2010] Storage Manager: Retrying to create directory /iw-store/wholesalebup/d3/d4d/d57
----------

Adam Stoller

Hi,

I believe you are trying to create branch here in your 6.5 store, even if it'z a 6.5 store which is running on TS 6.7.1 version , we would be able to work on the contents, But when you have arrived at the below error, I would recommend you to run iwmigrate on the 6.5 store and make the store compatible to your current version of Teamsite.

-----------
[Thu Feb 4 15:45:18 2010] Storage Manager: unable to create directory /iw-store/wholesalebup/d3/d4d/d57 error 13
[Thu Feb 4 15:45:18 2010] Storage Manager: Retrying to create directory /iw-store/wholesalebup/d3/d4d/d57
----------

I'm curious as to what leads you to believe those messages are due to creating a branch?

That seems a pretty big leap from the error message provided.

Reji Varghese

Yes - but both of those articles relate to Solaris - I'm on Windows.
The only aspect of it which might apply is that the 6.5 store was originally on a partition of the actual 6.5 server, whereas the copy (and the new 6.7.2 store) are on a NAS device rather than being on a partition of the actual server. As such, a domain account is used to access the 6.7.2 store (see KB 49040 I believe).

We'll see what Support has to say if/when they get back to me (hopefully by Monday)

Hey Adam,
Was this issue fixed for you ?

i had a similar issue which was fixed by providing the absolute path of the store which resided in the NAS inside iw.cfg -
store_directory_store1=//nas_share/folder_name/store_name

Regards !!!

Adam Stoller

Hey Adam,
Was this issue fixed for you ?

i had a similar issue which was fixed by providing the absolute path of the store which resided in the NAS inside iw.cfg -
store_directory_store1=//nas_share/folder_name/store_name

Regards !!!

We ended up putting the 6.5 store on a local drive of the server and doing the migration from there - but AIWOV seemed to be able to recreate the problem we saw in-house and filed it as a bug (TS-11734) - we're done with all of our migration efforts now so I have no need to retry (I think we tried the UNC path in iw.cfg but I'm not sure anymore)