Does anyone know which part of the repository assigns the magic_id to a univ, document, etc? Is it the security domain? Will I get rid of the unique constraint errors we are experiencing (it happens when we try to export a univ or send a doc to a user) if we have 1 security domain, with only the univ and doc domains pointing to different Oracle databases (instead of 3 complete repos like we do now)?
Thanks,
Sandy Brotje
Roadway Express
Listserv Archives (BOB member since 2002-06-25)
There’s a table OBJ_M_MAGICID in the security domain that gives the magic ids. If you have 3 security domains, you will have clashes if you exchange definitions between them.
1 security domain will solve your problems. Or you could update M_MAGIC_N_ID in OBJ_M_MAGICID so that all three domains have disjunct numberspaces.
There’s a HTML document that explains the repository in the freeware directory on the BO cd.
Stijn Nuyts
Sandy Brotje wrote:
Does anyone know which part of the repository assigns the magic_id to a univ, document, etc? Is it the security domain? Will I get rid of the unique constraint errors we are experiencing (it happens when we try to export a univ or send a doc to a user) if we have 1 security domain, with only the univ and doc domains pointing to different Oracle databases (instead of 3 complete repos like we do now)?
Thanks,
Sandy Brotje
Roadway Express
Listserv Archives (BOB member since 2002-06-25)
Sandy,
We have 1 security domain with 3 universe/document domains (Dev, Test, Prod). We are also having the “unique constraint” errors. Would like to hear from some people with similar setups to know if they are also having the same problem.
Does anyone know which part of the repository assigns the magic_id to a
univ, document, etc? Is it the security domain? Will I get rid of the
unique constraint errors we are experiencing (it happens when we try to
export a univ or send a doc to a user) if we have 1 security domain, with
only the univ and doc domains pointing to different Oracle databases (instead of 3 complete repos like we do now)?
Steve Money
Southwestern Bell
Listserv Archives (BOB member since 2002-06-25)
MONEY, STEVEN C wrote:
Sandy,
We have 1 security domain with 3 universe/document domains (Dev, Test, Prod). We are also having the “unique constraint” errors. Would like to hear from some people with similar setups to know if they are also having the same problem.
Steven,
We have a similar setup ( 1 security domain with many universe and document domains ). We get unique constraint errors whenever there is some problem in the updation of the magic id. In such a situation we run the “Scan and Repair” option available in the Supervisor module. This will correct the anomaly in the Magic Id and from then onwards we won’t get this error. The error has usually occurred when the user terminates a task submitted to DAS abnormally i.e. by rebooting his PC etc… The same happens when the task is abnormally terminated by DAS also. There might be many other reasons also but these two are quite frequent in our setup.
I hope this info helps you.
Chandrashekar.S
Listserv Archives (BOB member since 2002-06-25)
Chandrashekar,
We are already doing scan and repairs to correct the magic_id. Unfortunately we are having to do them more and more frequently. If this keeps up we will be running scan and repair every day. There has to be a better way.
We have a similar setup ( 1 security domain with many universe and document domains ). We get unique constraint errors whenever there is some problem in the updation of the magic id. In such a situation we run the “Scan and Repair” option available in the Supervisor module. This will correct the anomaly in the Magic Id and from then onwards we won’t get this error. The error has usually occurred when the user terminates a task submitted to DAS abnormally i.e. by rebooting his PC etc… The same happens when the task is abnormally terminated by DAS also. There might be many other reasons also but these two are quite frequent in our setup.
Steve Money
Southwestern Bell
SM5064@SBC.COM
Listserv Archives (BOB member since 2002-06-25)
Steve,
If you are already doing scan and repairs and it works for a period of time, you may have people attempting to do the same thing at the same time. If possible, I would ask groups to only export at certain periods throughout the day to prevent this from happening as often.
We are already doing scan and repairs to correct the magic_id. Unfortunately we are having to do them more and more frequently. If this keeps up we will be running scan and repair every day. There has to be a better way.
The problem only happens when:
a) A task is interrupted and the MagicID table doesn’t get properly updated. (Exporting a Universe, Document, Sending to user, etc…). Scan and repair will repair this. I believe that ‘retrying’ the task in later versions also fixes this.
b) More than one user is trying to do the same thing. (Two users sending a document to the same user at the same time). I’d resolve this by setting a period of time that each group can do this, or by controlling who can do these actions. Perhaps you can set a group that they can expor to and then having a Supervisor relink this to others?
-rm
Listserv Archives (BOB member since 2002-06-25)
Steven,
Yes, I agree with you. For us also it is becoming very difficult day by day as the number of BO users are increasing and utilising BO to publish almost all of their reports. Sometimes there are situations when I have to run the scan and repair function 3-4 times a day.
Is BO hearing this ??? If any other better method exists, can you point out the same. Also could you list out the precautions that we can take in order to avoid this situation or minimize it ???
Thanks in Advance for any help,
Chandrashekar.S
Listserv Archives (BOB member since 2002-06-25)
I would ask groups to only export at certain periods throughout the day to prevent this from happening as often.
Due to the fact that we have 1200+ users spread out over 5 states this is not really feasible. Also, I would prefer to not burden the user with a workaround solution. What I want is for the software to behave as well developed software should. We are paying a premium price and maintenance for what reason?
Steve Money
Southwestern Bell
SM5064@SBC.COM
Listserv Archives (BOB member since 2002-06-25)