Process of creating new Repository

AbhiWM

Dear Team,

We want to create new Repository from Existing Docbase.While creating the Repository we have the option to provide Database System Administrator and password.Can you please let us know what values we need to enter for this.

Regards,
Suresh.M

wetcat

Hi,
That is bad idea. From my experience it should not work using repository configuration program as it requires empty schema/database to create new tables/views/indexes...
If you need new repository (with new repository, docbase owner, install owner names, docbase id, new crypto objects), I would suggest create new repository from scratch and try migrating required data (metadata and content) from old to new repository using dump and load operations.

DCTM_Guru

What is your purpose of creating a new repo from existing docbase? Do you want to clone it to another environment?

The option to provide SA password allows the set up script to create/grant all the required permissions to create Documentum database schema. Alternatively, your dba can create a username/pwd and grant all the appropriate privileges in lieu of SA password step.

Xyril1993

Hello Experts,
I know this forum/topic has been a long time now but we are planning to perform this cloning repository from Production to another working lower environment. Do you have specific step-by-step guide on how to do that? as well as creating a new repository?

I really appreciate the help!
Thank you in advance!

Hari_Gadhamsetty

Hi Xyril1993,

The steps for copying repository from Prod to Test is available at page no: 81-83 in Documentum Upgrade and Migration Guide. Here is the URL, https://knowledge.opentext.com/knowledge/llisapi.dll/fetch/2001/3551166/27085930/69125280/66215269/72073920/Documentum_System_16.4_Upgrade_and_Migration_Guide.pdf?nodeid=72193100&vernum=-2

Hope this helps:)
Hari.

Xyril1993

Thanks for responding Hari.

We followed that and right now we're getting filestore_01 is not accessible after logging in to the application of lower environment.

@Hari_Gadhamsetty said:
Hi Xyril1993,

The steps for copying repository from Prod to Test is available at page no: 81-83 in Documentum Upgrade and Migration Guide. Here is the URL, https://knowledge.opentext.com/knowledge/llisapi.dll/fetch/2001/3551166/27085930/69125280/66215269/72073920/Documentum_System_16.4_Upgrade_and_Migration_Guide.pdf?nodeid=72193100&vernum=-2

Hope this helps:)
Hari.

DCTM_Guru

Do you grant full rights (including delete) to the install owner for that filestore directory?

Xyril1993

The filestore directory is currently resides in a NAS drives. Is there a way we can check that? or we need some from the storage team to confirm it for us? also, is the filestore_01 has its own folder? and where exactly it is located. Thanks DCTM_Guru!

@DCTM_Guru said:
Do you grant full rights (including delete) to the install owner for that filestore directory?

DCTM_Guru

You dont want to share the same filestore between two different environment; otherwise, you will end up overwriting PROD data with TEST data. If you want TEST to be identical to PROD, then you would need to set up a different filestore directory and copy everything over to the new filestore. If your NAS is mounted to your TEST content server, you should be able to see the permissions yourself (as admin).

Xyril1993

We are not actually sharing same filestore between two environment. What we did is create a backup of the Prod and from that backup that's the one we are using in lower environment. Does that make sense?

@DCTM_Guru said:
You dont want to share the same filestore between two different environment; otherwise, you will end up overwriting PROD data with TEST data. If you want TEST to be identical to PROD, then you would need to set up a different filestore directory and copy everything over to the new filestore. If your NAS is mounted to your TEST content server, you should be able to see the permissions yourself (as admin).

Xyril1993

okay, sorry, so we copied every data folder (same with our Prod) and those folders (such as content_storage_01, etc.) are empty for now... and that's what we are using.

DCTM_Guru

Make sure you change location on your NAS for filestore01 to point to this new data folder.

Xyril1993

Yes, they are now, but we are still getting the not accessible message in the application.

@DCTM_Guru said:
Make sure you change location on your NAS for filestore01 to point to this new data folder.

DCTM_Guru

Try changing the data folder owner to the install owner.