Docbase service is not running

I am trying to install 2 content servers and apply the load balance model.

I installed the first content server, created the DB and referred to a local folder as the data folder. The 3 Documentum services started successfully.

I then installed the second content server, referring to the same DB, and to another local folder as the data folder, but we ensure a continuous sync between the 2 data folders on the 2 content servers. The 3 services are created but when I try to run the docbase servce I get the following error:
DM_SERVER_F_CANT_CREATE_TICKET_MANAGER fatal unable to create ticket manager on server startup. likely reason is corrupted aek.key file or docbase config object. the server will shutdown.

Please advise.

Find more posts tagged with

Comments

Hicham Bahi

Did you copy the aek.key file from the first to the second server?

You cannot use two different local stores with such a setup. You need shared storage such as a NAS or NFS share. But this has probably nothing to do with your current problem.

Hosam Salem

bacham3 said:

Did you copy the aek.key file from the first to the second server?

You cannot use two different local stores with such a setup. You need shared storage such as a NAS or NFS share. But this has probably nothing to do with your current problem.

Thanks bacham3 for your reply.

I will try now copying the original aek.key file and feedback to you.

Meanwhile, I am wondering why the proposed implementation cannot work, we are using the "Distributed File System (DFS)" technique to ensure that both data folders of the 2 content servers are always synchronized, along with referring to the same DB.

Is there a chance that this model can work?

Hosam Salem

LimoMan said:

bacham3 said:

Did you copy the aek.key file from the first to the second server?

You cannot use two different local stores with such a setup. You need shared storage such as a NAS or NFS share. But this has probably nothing to do with your current problem.

Thanks bacham3 for your reply.
I will try now copying the original aek.key file and feedback to you.
Meanwhile, I am wondering why the proposed implementation cannot work, we are using the "Distributed File System (DFS)" technique to ensure that both data folders of the 2 content servers are always synchronized, along with referring to the same DB.
Is there a chance that this model can work?

Kindly note that after I copied both CSaek.key and dbpassword files from content server 1 to content server 2, all Documetum services on the second content servers started successfully.

Will be glad to get your assistance/advise concerning the proposed implementation. Do you prefer to contact you by mail concerning this matter as the issue of this thread is not resolved?

Hicham Bahi

Good news! About the storage, you want to setup a high-availability docbase with two Documentum Servers on different hosts, if I understand correctly. So the storage must be shared. I don't know exactly how you want to synchronize your two local stores, and what the latency will be. If it's too high, someone may request a document from server B, but the content which was created on server B has not yet been replicated. You also need to take into account jobs such as DMClean which will delete orphaned objects. Assuming your setup works, you will need to make sure this job only works on one server (and then your sync mechanism should take care of removing the files on the other system.

In any case, I'm not sure if it will work and I'm not sure this is supported. You may want to check with OT Support.

Hosam Salem

bacham3 said:

Good news! About the storage, you want to setup a high-availability docbase with two Documentum Servers on different hosts, if I understand correctly. So the storage must be shared. I don't know exactly how you want to synchronize your two local stores, and what the latency will be. If it's too high, someone may request a document from server B, but the content which was created on server B has not yet been replicated. You also need to take into account jobs such as DMClean which will delete orphaned objects. Assuming your setup works, you will need to make sure this job only works on one server (and then your sync mechanism should take care of removing the files on the other system.

In any case, I'm not sure if it will work and I'm not sure this is supported. You may want to check with OT Support.

Yes, my plan is to setup a high-availability docbase with 2 Documentum servers on 2 different hosts.

Concerning the Distributed File System (DFS) technique, and as per our System Administrators, the latency is very small.

Anyways, we will proceed with this model and check if it works or not.

Hope I can be able to reach you later in case I have further inquiries.