In our process of getting ready for a 9.4 to 10.1 migration we would like to perform a run-through of the scan_rep / migration process. We are leary of performing this process on our live web server OI installation as we just don't know if it will affect that installation at all. We need to keep it running as-is for a couple of months until our network is ready for the migration.
What we have planned for this test is to run the scan_rep utility, select OI entities that we do not want included in the migration then import the 9.4 application to an evaluation installation of OI 10.1. If the scan_rep process does not affect the 9.4 installation we can feel better about taking a snapshot of it and proceeding. Otherwise we would like to know if we can copy the live installation to a new location and use the new location as a source for the test 10.1 migration.
Thanks for you input.
Hi Michael
Lets start by commenting on the 'purpose' of Scan_Rep and why it is such a good idea to do prior to upgrade/migration.
When we create say a form, there will be a record created containing info on the form controls (SYSREPOSWINS table) + possibly associated events (a record for each in SYSREPOEVENTS) and when we compile the form to execute - we generate corresponding object code (a record in SYSREPOSWINSEXE etc) PLUS for each and every 'component', an entity record in table SYSREPOS. And if we create a Stored Procedure, we will end up with the source code record in SYSPROCS table, the compiled code as a $ record and likewise debug code as @ record in SYSOBJ, PLUS, again, am entity record for each item in SYREPOS.
Now if - in our development journey, we say modified a form - removed a control and or associated event, or we perhaps copied/deleted a stored procedure - there is possibility that not everything is left tidy - we may get events without the parent form, we might somehow have removed some of the entities but not the entity reference in SYSREPOS. Over time we might accumulate a lot of debris - garbage and clutter.
Scan_Rep is a tool to remove clutter - sift thru the system to pick out possible inconsistencies - and provide a way of organized the information so we can investigate and - as appropriately - eliminate the bad stuff. I had an experience running Scan_Rep at one development site where - on first run - it took 3 days to complete. Many multiple scans and careful decisions later, I was able to get the scan time down to about 40 min. Think of all the rubbish that got eliminated from the system before an upgrade!
The golden rule would be NOT to touch anything in the SYPROG App - because we probably don't know enough about context etc - just focus on our own applications, and then only delete stuff that we are absolutely sure is bad. In other words, this is not really the tool to slim down an application prior to migration but rather clean out the rubbish and thus improve the 'health' of the system and any application in the system.
Unless you are familiar and confident about the process - it might be a good idea to clone your system and the do some testing on the clone so that you are clear as to the process and consequences of any delete action.
Richard Bright
Wow Richard .. :) really sorry I never replied to your helpful reply. We have been pretty busy with the multiple issues that have appeared during our migration journey but I did read your article and took it to heart. We are currently working on why our forms are not being displayed in OI 10 as they are in our 9.4 installation and came across this previous article.
So, thanks again for your input, it was seen and used.
Hi Michael,
Thanks. Just the other day - as I was fossicking thru my archives for some other material, I came across a PowerPoint presentation touching on this topic and other matters related to RDK Extract that I titled "Outing the Application". While the stuff is ancient, and perhaps what happens in Vegas should stay in Vegas, you might find the content of interest.
Richard Bright