Re: Server Name references - export/import ARSystem DB - ITSM 7
Did you ever get an answer back from BMC on the SLMConfDSServerName field data in the SLM:ConfigDataSource form? I noticed that the act of recreating the filters on a different server does not change the value in this table, but the filters still use the local server reference for the new server. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ > -Original Message- > From: Action Request System discussion list(ARSList) > [mailto:arsl...@arslist.org] On Behalf Of Mary Ann > Sent: Tuesday, February 24, 2009 1:43 PM > To: arslist@ARSLIST.ORG > Subject: Server Name references - export/import ARSystem DB - ITSM 7 > > We have been struggling with the list of server name references that > need to be changed when exporting/importing an ARSystem DB from one > server to another server. > > Last week we found that one of the imbedded server references has been > causing Apache on our Mid-Tier server to crash because we had a server > reference for the CI Viewer to the original server. > > Our versions installed: > ARS 7.0.01/Patch 7 > CMDB 2.0.1/Patch 3 > ITSM IM/PM/AM/Change 7.0.02/Patch 5 > SLM 7.0.03/No Patch > RKM 7.2/Patch 1 > SQL Server 2005/SP2 > > I looked at past postings on this list and have been using that list to > update server references up to now. Based on our crashes I looked for > and found a SQL Server procedure on the internet to search for text > (old > server references) in columns in tables. > > These are the server references that we will NOW update when we move > the > > ARSystem database from one server to another server: > > FORM DATA: > - KMS:Adminstration_Integration - Server Name > - SHARE:Application_Properties - help file paths > - SYS:Attachments - survey path > - Report - Server field > - CAI:Application Registry - Server field > - BMC.CORE:CONFIG:BMC_FederatedInterface - ARServerName field [this was > the one causing the MidTier apache crash] > - AR System Searches - Server field > - CAI:EventParams - FromServer field > - CAI:Events - SourceServer, TargetServer fields > - SLM:ConfigDataSource - SLMConfDSServerName field - hidden in GUI > [have > > not changed this yet due to possibly having to rebuild all service > targets > connected to this data source, waiting for a response from BMC Support] > - SRM:AppInstanceBridge - AppInstanceServer field > > WORKFLOW: > - Active Link: CHG:CCMCalendar:PrintActionWUT - Action 1 path > > I asked BMC Support to confirm this list and they said "we currently do > not have a doc that contains this information, as migrating the > database > > is not a supported process. R&D is developing a document that will > define > how this should be done and once this document is published, we will > begin > supporting a DB migration like the one you describe. Unfortunately, > there > is currently no ETA on this document." The good news is that they are > working on this document and hopefully we will see one soon, so I will > feel more comfortable that we have caught everything. > > I hope this list helps others who have been struggling with this. > > Thanks. > > Mary Ann > > ___ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
Re: Server Name references - export/import ARSystem DB - ITSM 7
Why dont you use the old server name as an alias on migration? Won't that take care of most of such problems?? Except for application paths etc thats in configuration data such as the share application properties form which you would need to fix manually.. Joe From: Mary Ann To: arslist@ARSLIST.ORG Sent: Tuesday, February 24, 2009 2:42:32 PM Subject: Server Name references - export/import ARSystem DB - ITSM 7 We have been struggling with the list of server name references that need to be changed when exporting/importing an ARSystem DB from one server to another server. Last week we found that one of the imbedded server references has been causing Apache on our Mid-Tier server to crash because we had a server reference for the CI Viewer to the original server. Our versions installed: ARS 7.0.01/Patch 7 CMDB 2.0.1/Patch 3 ITSM IM/PM/AM/Change 7.0.02/Patch 5 SLM 7.0.03/No Patch RKM 7.2/Patch 1 SQL Server 2005/SP2 I looked at past postings on this list and have been using that list to update server references up to now. Based on our crashes I looked for and found a SQL Server procedure on the internet to search for text (old server references) in columns in tables. These are the server references that we will NOW update when we move the ARSystem database from one server to another server: FORM DATA: - KMS:Adminstration_Integration - Server Name - SHARE:Application_Properties - help file paths - SYS:Attachments - survey path - Report - Server field - CAI:Application Registry - Server field - BMC.CORE:CONFIG:BMC_FederatedInterface - ARServerName field [this was the one causing the MidTier apache crash] - AR System Searches - Server field - CAI:EventParams - FromServer field - CAI:Events - SourceServer, TargetServer fields - SLM:ConfigDataSource - SLMConfDSServerName field - hidden in GUI [have not changed this yet due to possibly having to rebuild all service targets connected to this data source, waiting for a response from BMC Support] - SRM:AppInstanceBridge - AppInstanceServer field WORKFLOW: - Active Link: CHG:CCMCalendar:PrintActionWUT - Action 1 path I asked BMC Support to confirm this list and they said "we currently do not have a doc that contains this information, as migrating the database is not a supported process. R&D is developing a document that will define how this should be done and once this document is published, we will begin supporting a DB migration like the one you describe. Unfortunately, there is currently no ETA on this document." The good news is that they are working on this document and hopefully we will see one soon, so I will feel more comfortable that we have caught everything. I hope this list helps others who have been struggling with this. Thanks. Mary Ann ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
Server Name references - export/import ARSystem DB - ITSM 7
We have been struggling with the list of server name references that need to be changed when exporting/importing an ARSystem DB from one server to another server. Last week we found that one of the imbedded server references has been causing Apache on our Mid-Tier server to crash because we had a server reference for the CI Viewer to the original server. Our versions installed: ARS 7.0.01/Patch 7 CMDB 2.0.1/Patch 3 ITSM IM/PM/AM/Change 7.0.02/Patch 5 SLM 7.0.03/No Patch RKM 7.2/Patch 1 SQL Server 2005/SP2 I looked at past postings on this list and have been using that list to update server references up to now. Based on our crashes I looked for and found a SQL Server procedure on the internet to search for text (old server references) in columns in tables. These are the server references that we will NOW update when we move the ARSystem database from one server to another server: FORM DATA: - KMS:Adminstration_Integration - Server Name - SHARE:Application_Properties - help file paths - SYS:Attachments - survey path - Report - Server field - CAI:Application Registry - Server field - BMC.CORE:CONFIG:BMC_FederatedInterface - ARServerName field [this was the one causing the MidTier apache crash] - AR System Searches - Server field - CAI:EventParams - FromServer field - CAI:Events - SourceServer, TargetServer fields - SLM:ConfigDataSource - SLMConfDSServerName field - hidden in GUI [have not changed this yet due to possibly having to rebuild all service targets connected to this data source, waiting for a response from BMC Support] - SRM:AppInstanceBridge - AppInstanceServer field WORKFLOW: - Active Link: CHG:CCMCalendar:PrintActionWUT - Action 1 path I asked BMC Support to confirm this list and they said "we currently do not have a doc that contains this information, as migrating the database is not a supported process. R&D is developing a document that will define how this should be done and once this document is published, we will begin supporting a DB migration like the one you describe. Unfortunately, there is currently no ETA on this document." The good news is that they are working on this document and hopefully we will see one soon, so I will feel more comfortable that we have caught everything. I hope this list helps others who have been struggling with this. Thanks. Mary Ann ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
