Archiving/Deleting(Physical) Source Control in RTC
RTC is used in our team for multiple projects, and source code in RTC is growing everyday. Is there a way to archive a single project source control artifacts from a given date to a different server(disk).
Example: Archive Project A source code artifacts before Dec 2009.
Everyday source code for a specific project increases to 2GB, We are using oracle 10g, instructions to archive through the oracle database vendor would be of help or any other alternate way to resolve this issue. But project is not ready to increase the disk space as this is POC environment
I tried in infocenter, jazznet not enough information regarding this is available.
Thanks in Advance
Example: Archive Project A source code artifacts before Dec 2009.
Everyday source code for a specific project increases to 2GB, We are using oracle 10g, instructions to archive through the oracle database vendor would be of help or any other alternate way to resolve this issue. But project is not ready to increase the disk space as this is POC environment
I tried in infocenter, jazznet not enough information regarding this is available.
Thanks in Advance
4 answers
You cannot currently do this in RTC, but there is ongoing work to
support "project move" (currently, no target release date), which would
allow you to move components from one repository to another.
I don't see that a generic DB archive operation would be of use here,
since the information is distributed through a variety of tables, but
I'll let the RTC-SCM team comment definitively on that.
Cheers,
Geoff
On 6/18/2010 9:53 AM, rajahv wrote:
support "project move" (currently, no target release date), which would
allow you to move components from one repository to another.
I don't see that a generic DB archive operation would be of use here,
since the information is distributed through a variety of tables, but
I'll let the RTC-SCM team comment definitively on that.
Cheers,
Geoff
On 6/18/2010 9:53 AM, rajahv wrote:
RTC is used in our team for multiple projects, and source code in RTC
is growing everyday. Is there a way to archive a single project
source control artifacts from a given date to a different
server(disk).
Example: Archive Project A source code artifacts before Dec 2009.
Everyday source code for a specific project increases to 2GB, We are
using oracle 10g, instructions to archive through the oracle database
vendor would be of help or any other alternate way to resolve this
issue. But project is not ready to increase the disk space as this is
POC environment
I tried in infocenter, jazznet not enough information regarding this
is available.
Thanks in Advance
Thanks Geoff.
But if there is a way through DB Vendor, Please let me know.
We are interested in archiving or deleting through DB vendor, if RTC is not really built with this feature.
Thanks Again.
But if there is a way through DB Vendor, Please let me know.
We are interested in archiving or deleting through DB vendor, if RTC is not really built with this feature.
Thanks Again.
You cannot currently do this in RTC, but there is ongoing work to
support "project move" (currently, no target release date), which would
allow you to move components from one repository to another.
I don't see that a generic DB archive operation would be of use here,
since the information is distributed through a variety of tables, but
I'll let the RTC-SCM team comment definitively on that.
Cheers,
Geoff
On 6/18/2010 9:53 AM, rajahv wrote:
RTC is used in our team for multiple projects, and source code in RTC
is growing everyday. Is there a way to archive a single project
source control artifacts from a given date to a different
server(disk).
Example: Archive Project A source code artifacts before Dec 2009.
Everyday source code for a specific project increases to 2GB, We are
using oracle 10g, instructions to archive through the oracle database
vendor would be of help or any other alternate way to resolve this
issue. But project is not ready to increase the disk space as this is
POC environment
I tried in infocenter, jazznet not enough information regarding this
is available.
Thanks in Advance
The jazz repository contains numerous schemas and tables, with linkages between them ... you will not be able to reclaim tablespace in the database without understanding how it all fits together. Even then, it would be error prone and troublesome to do as an administrator.
I would raise a specific feature request for this type of repository "scrubbing".
Regards,
JohnC
SCM Server
I would raise a specific feature request for this type of repository "scrubbing".
Regards,
JohnC
SCM Server
The jazz repository contains numerous schemas and tables, with linkages between them ... you will not be able to reclaim tablespace in the database without understanding how it all fits together. Even then, it would be error prone and troublesome to do as an administrator.
I would raise a specific feature request for this type of repository "scrubbing".
Regards,
JohnC
SCM Server
Thanks John for the response.