version control moved different job

[poorna_76]

We Initialized job "A" and VersionControl moved job "B" (Sequencer job).
We opened a case with Ascential.
They said they could not reproduce the error and kind of quite from then.

We happend to hit the same problem again now, after few months that happened.

This time , we moved job "X" and VersionControl moved job "Y"(regular job).

Any solution for this problem, yet?

Thanks in Advance.

[kduke]

Do a search. This has happened to others.

[poorna_76]

Do a search. This has happened to others.

Hi Kim,

I did searched the Forum.
I have seen posts about the problem, but i could not find any solution.
Please let me know any solid solution, yet.



Thanks in Advance.

[poorna_76]

Hi Kim,

Is there any limit on no of versions a job can be there in VersionControl tool?

Since VersionControl is moving different job contents,
we are curious like any pointer issues internally or something else.

Thanks in Advance.

[chulett]

Please let me know any solid solution, yet.

There isn't one. It would need to be reproducible first.

[chulett]

Is there any limit on no of versions a job can be there in VersionControl tool?

I'm sure there is but can't imagine those limits ever come into play.

[fridge]

I have had this problem in our set up and I believe it can be resolved by reindexing the version control repository, using DS.TOOLS from the command line in Admin.exe often does the trick

[poorna_76]

I have had this problem in our set up and I believe it can be resolved by reindexing the version control repository, using DS.TOOLS from the command line in Admin.exe often does the trick

Thanks for all ,
for all the valuable replies.

[ray.wurlod]

While there is no documented limit on the number of versions, there may be physical factors that intervene.

At one of my client's sites they ran into the "too many subdirectories in directory" limit on Solaris. This was caused by the huge number of dynamic hashed files in the Version project. The client had very many jobs, and had been using Version Control for a number of years when the problem occurred.

Changing some (lots) of the older storage to static hashed files (which don't use directories) was a viable solution to this particular operating system restrction.