Author Topic: Error running ARSXML export.  (Read 5468 times)

Alessandro Perucchi

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1002
    • View Profile
Re: Error running ARSXML export.
« Reply #15 on: February 16, 2019, 03:19:07 AM »
When we migrated from an 8.5 system (windows) to a 9.5 system(z/OS) I used ARSXML with a lot of manual manipulation of the xml export, including storage, to get the items to be defined correctly.  Seemed no way around it at the time.

I think that's my only option at this point sadly. Instead of trying to figure out why arsxml keeps crashing, on an old version, on servers that are going away. Thanks for the feedback

I have found that sometimes, old servers have not nice configuration of AG/APP/Folders for some reasons... that the admin was tolerating at one time, and then no more, but the db was "corrupted" slightly that you don't see the problem in the day to day production, but only when you do export such quirks appears.
And doing what you need to do is a wonderful way to clean up things.
BUT between XML from V8.5 and V9+... you have a lot work manual work to do, or script to do in order to convert from one format to another.

And don't worry, you could upgrade from CMOD V8 -> V10 in one shot without problems. The upgrade process is quite perfect in that area.
The only moment you might need to go to V9 is only if you use ODF/RDF.

Regards,
Alessandro
Alessandro Perucchi

#Install #Migrations #Conversion #Educate #Repair #Upgrade #Migrate #Enhance #Optimize #AIX #Linux #Multiplatforms #DB2 #Windows #Oracle #TSM #Tivoli #Performance #Audits #Customizing #Availability #HA #DR #JavaApi #ContentNavigator #ICN #WEBi #ODWEK #Services #PDF #AFP #XML

jsquizz

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 576
    • View Profile
Re: Error running ARSXML export.
« Reply #16 on: February 16, 2019, 11:43:00 AM »
When we migrated from an 8.5 system (windows) to a 9.5 system(z/OS) I used ARSXML with a lot of manual manipulation of the xml export, including storage, to get the items to be defined correctly.  Seemed no way around it at the time.

I think that's my only option at this point sadly. Instead of trying to figure out why arsxml keeps crashing, on an old version, on servers that are going away. Thanks for the feedback

I have found that sometimes, old servers have not nice configuration of AG/APP/Folders for some reasons... that the admin was tolerating at one time, and then no more, but the db was "corrupted" slightly that you don't see the problem in the day to day production, but only when you do export such quirks appears.
And doing what you need to do is a wonderful way to clean up things.
BUT between XML from V8.5 and V9+... you have a lot work manual work to do, or script to do in order to convert from one format to another.

And don't worry, you could upgrade from CMOD V8 -> V10 in one shot without problems. The upgrade process is quite perfect in that area.
The only moment you might need to go to V9 is only if you use ODF/RDF.

Regards,
Alessandro

I tried this yesterday. I exported one of the heaviest used AG's from our system, and tried exporting it directly to 10.1 with a newly created storage set. It looks like everything worked, except there is the one field depricated and ARSXML doesnt like it, it's logDBqueries or something. So I'm going to have to tinker with that a bit. I was going to change that logging anyway.
#CMOD #DB2 #AFP2PDF #TSM #AIX #RHEL #AWS #AZURE #GCP #EVERYTHING