Hi Pavan, Please find my responses inline. Thanks!
Bottomline: 1) Compile all the 65 INVALID objects, in fact they are the reason for longer run of your ITSM upgrade installer. They should have been identified before running installer and must have been re-compiled. Keep checking for them when installer is running and compile them. 2) You have trouble importing one join form. Take backup of base forms in your environment. Import OOTB 8.1.02 version of the form directly. Regards, Aditya Shrivastava On Tue, Mar 17, 2015 at 6:50 PM, Nagidi Pavan <pavan....@gmail.com> wrote: > ** > Hi Aditya, > > Thank you very much for your reply. Please find my answers below. > > 1) Which database you have? If you have Oracle, did you check for INVALID > objects while installing/upgrading? > ANS: Oracle, How do we checked INVALID objects by the below query and it > fetched almost 65 entries > select object_name,object_type,status from user_objects where > status='INVALID'; > > [APS]: Yes, this query gives you count of INVALID objects. You can > re-compile these objects using "Compile" option from whatever software you > are using. or run query to compile those objects. > Any suggestions to correct them is highly appreciated, also I would like to > know why they are INVALID. How to troubleshoot that? > There are INVALID objects because of the fact that there are some structural differences between how Remedy and Oracle creates tables and views. But this is not a big problem as those INVALID objects can be "Compiled" and then everything would be in sync. > > 2) Hope you must have seen ITSM install log files, but would again suggest > you to look through logs and find out which .def failed to import. For ex > chg_deplapp.def etc > ANS: Fixed all most all the issues that we could see in the logs. The > issues which we are seeing now is while importing > CHG:ChangeRelationshipinterface form, which does not exist in 7.6.03 but > seems like newly added in 8.1.02 > > [APS]: I believe you have already followed recommended upgrade path 7.6.03 to 7.6.04 to 8.1.02. Since this form doesn't exist in 7.6.03, I would like to try out following: 1. Identify the def to which it belong like chg_deplapp**.def and try to import this form alone from 8.1.02_install folder. 2. If unable to find the def, you can try importing def of this form alone obtained from an OOTB environment. Please note this is a join form so you should have the base forms inn your environment CHG:ChangeRelationshipinterface -> CHG:Associations + CHG:ChangeInterface > 3) Go through all INC/PBM/CHG and import all the failed def files. > ANS: imported all the def files related to INC and PBM only facing issues > while importing chg_deplapp.def and especially with > CHG:ChangeRelationshipinterface form. > [APS]: You can try importing def of this form alone obtained from an OOTB environment. > > 4) If you are facing issues with specific form import also - suggest you > to modify them, save changes and again try to import them. > ANS: Since we are only facing issues with CHG:ChangeRelationshipinterface > form, is that fine modifying that form? > My only concern is the above mentioned form does not exist in 7.603. We > are upgrading ITSM from 7.6.03 to 8.1.02. > [APS]: As you said, this form doesn't exist in old environment and might be newly added one. Would suggest take backup of base forms and import the newly added join form obtained from an OOTB environement. > > Please let me now your thoughts and any suggestions to move forward!! > > Thanks once again. > > > On Tue, Mar 17, 2015 at 9:07 AM, Aditya Shrivastava <iadity...@gmail.com> > wrote: > >> ** >> Hi Pavan, >> >> 1) Which database you have? If you have Oracle, did you check for INVALID >> objects while installing/upgrading? >> 2) Hope you must have seen ITSM install log files, but would again >> suggest you to look through logs and find out which .def failed to import. >> For ex chg_deplapp.def etc >> 3) Go through all INC/PBM/CHG and import all the failed def files. >> 4) If you are facing issues with specific form import also - suggest you >> to modify them, save changes and again try to import them. >> >> Let us know how it goes. Thanks! >> >> Regards, >> Aditya >> >> On Tue, Mar 17, 2015 at 5:59 AM, Nagidi Pavan <pavan....@gmail.com> >> wrote: >> >>> ** >>> Hello Experts, >>> >>> Do anyone has any suggestions for me!! >>> >>> On Fri, Mar 13, 2015 at 8:04 PM, Nagidi Pavan <pavan....@gmail.com> >>> wrote: >>> >>>> Hi Ken, >>>> >>>> Thanks for your response. >>>> >>>> For the form which we are facing the issue, in the Base devleopment >>>> mode it shows its "overlaid", in the Best Practice Customization mode it >>>> shows "unmodified". >>>> >>>> Is this the issue? If so, how to overcome this? >>>> >>>> On Fri, Mar 13, 2015 at 2:52 AM, Ken Pritchard <pri...@ptd.net> wrote: >>>> >>>>> ** >>>>> >>>>> I’ve seen the unique index error occur when there is a form with and >>>>> without the __c designation. Seems like the system thinks they are two >>>>> different forms, but the same form. >>>>> >>>>> >>>>> >>>>> *From:* Action Request System discussion list(ARSList) [mailto: >>>>> arslist@ARSLIST.ORG] *On Behalf Of *Grooms, Frederick W >>>>> *Sent:* Thursday, March 12, 2015 2:03 PM >>>>> >>>>> *To:* arslist@ARSLIST.ORG >>>>> *Subject:* Re: ITSM Upgrade completed with warnings - In fact failed >>>>> to upgrade >>>>> >>>>> >>>>> >>>>> ** >>>>> >>>>> The SQL database operation failed.; Error - OCI_INVALID_HANDLE, 552 >>>>> >>>>> >>>>> >>>>> Sounds like your database had an error with connecting to it. I >>>>> believe there is an SQL log made during the upgrade. See if it has any >>>>> more information >>>>> >>>>> >>>>> >>>>> Look to see what the SQL was doing when you got the >>>>> >>>>> The value(s) for this entry violate a unique index that has been >>>>> defined for this form; , 382 >>>>> >>>>> >>>>> >>>>> That will tell you which forms tried to create duplicate records >>>>> >>>>> >>>>> >>>>> Fred >>>>> >>>>> >>>>> >>>>> *From:* Action Request System discussion list(ARSList) [ >>>>> mailto:arslist@ARSLIST.ORG <arslist@ARSLIST.ORG>] *On Behalf Of *Nagidi >>>>> Pavan >>>>> *Sent:* Thursday, March 12, 2015 12:52 PM >>>>> *To:* arslist@ARSLIST.ORG >>>>> *Subject:* Re: ITSM Upgrade completed with warnings - In fact failed >>>>> to upgrade >>>>> >>>>> >>>>> >>>>> ** >>>>> >>>>> Hi William, >>>>> >>>>> Firstly, thanks for your response. >>>>> >>>>> Below was done prior to ITSM upgrade. >>>>> >>>>> >>>>> 1) We have upgraded AR Server from 7.6.04 to 8.1.02 without any issues. >>>>> 2) Ran BPCU in overlay mode to preserve our customizations >>>>> 3) Upgraded Atrium Core successfully from 7.6.03 to 8.1.02 >>>>> 4) Upgraded ITSM from 7.6.03 to 8.1.02 successfully after fixing >>>>> issues with field mappings using the option "Only copy CI attributes from >>>>> CDM to ITSM Foundation". >>>>> 5) Restarted upgrade once again with the option "Upgrade to 8.1.02 but >>>>> don not remove CI attributes from CDM". After 13 hours we got the results >>>>> as "BMC Remedy ITSM Suite 8.1.02 install completed with warnings." >>>>> >>>>> I believe I am going in the correct direction. Please advise. >>>>> >>>>> Thanks >>>>> >>>>> Pavan >>>>> >>>>> >>>>> >>>>> *From:* Action Request System discussion list(ARSList) [mailto: >>>>> arslist@ARSLIST.ORG] *On Behalf Of *Nagidi Pavan >>>>> *Sent:* Thursday, March 12, 2015 12:14 PM >>>>> *To:* arslist@ARSLIST.ORG >>>>> *Subject:* ITSM Upgrade completed with warnings - In fact failed to >>>>> upgrade >>>>> >>>>> >>>>> >>>>> ** >>>>> >>>>> Hello Experts, >>>>> >>>>> We tried to upgraded ITSM from 7.603 to 8.1.02, but it says completed >>>>> with warnings. From the logs we could find many def files failed to >>>>> import. >>>>> We have sorted out issues related to Asset, incident and Problem >>>>> Management. But facing issues while importing the def files related to >>>>> Change Module. >>>>> >>>>> We could see the below error messages while importing the file. >>>>> >>>>> The SQL database operation failed.; Error - OCI_INVALID_HANDLE, 552, >>>>> The following item was not imported; >>>>> CHG:ChangeImpactedAreaCIAssociation_Join, 55, >>>>> The following item was not imported; >>>>> CHG:Change-ImpactedAreasCIAssociation_outer_ApproverLookup, 55, >>>>> The following item was not imported; CHG:ChangeRelationshipInterface, >>>>> 55 >>>>> >>>>> We have restarted Remedy services and tried importing that again. This >>>>> time we could find the below messages. >>>>> >>>>> The value(s) for this entry violate a unique index that has been >>>>> defined for this form; , 382, >>>>> The following item was not imported; >>>>> CHG:ChangeImpactedAreaCIAssociation_Join, 55, >>>>> The following item was not imported; >>>>> CHG:Change-ImpactedAreasCIAssociation_outer_ApproverLookup, 55, >>>>> The following item was not imported; CHG:ChangeRelationshipInterface, >>>>> 55, >>>>> >>>>> >>>>> >>>>> I have opened a ticket with BMC but as as usual very poor response in >>>>> this week. Any suggestions are highly appreciated. >>>>> >>>>> Thanks >>>>> >>>>> Pavan >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >>>>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >>>>> >>>> >>>> >>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >>> >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
