Axton, By the way....
On the other topic in your message, definition of a primary key. We found that a number of the replication technologies require a table to have a primary key in order to replicate successfully. Since every one of our tables has a primary key -- the entry ID -- and we can define combinations of fields for other forms -- like status history -- that are unique, we have added a primary key to every metadata table and all the data tables for things we install or create going forward. I don't think we retrofit the DB to add them to existing installations. This work was done in the 7.5 or so timeframe (before, at, or after I am not sure, but in the range of the three releases just before, at, or after 7.5). No issue if you want to create something else as your primary key, but just be aware of the fact that the environment does create a primary key for all tables now so that it is present and defined for any environment where DB replication requires this capability. So, you may want to check to see if there is already a primary key defined and maintained for you. Then, you can decide whether this is sufficient or do you need to do something different for your situation. Just be clear that you may need to undo the primary key specification in your work as we should already be doing one. This was added in that range of just before, at, or just after the 7.5 release. If before or at, you have already seen/addressed this situation. If after, just be aware that this is coming and may have some impact on you in the future. Doug Mueller -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Axton Sent: Monday, February 27, 2012 7:53 AM To: arslist@ARSLIST.ORG Subject: Remedy Table Recreation First, some background information: It used to be the case that certain operations would trigger Remedy to recreate a database table: - rename existing table - create new table with the original name - copy the data from the renamed table to the new table - drop the renamed table I remember altering the precision on a decimal field would trigger this, and I seem to also remember something with currency fields. Now for the issue: We have applied changes to every table in the Remedy database to define a primary key. This primary key is used for Oracle Streams replication to a target database. If the table is recreated, the primary key is dropped, which can cause Streams to choke if the table contains a large volume of data. Now for the question: Does anyone know of an action that a user can perform through the Remedy clients that will cause a table to be recreated in this manner? When I say "Remedy Clients" I am referring to Dev Studio, User Tool, ITSM applications, mid-tier, or the Remedy API. Relevant Environment Information: - Oracle 11g - ARServer 7.5 - Apps 7.5 (ITSM, CMDB, etc.) Thanks, Axton Grams _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
