Shrikanthn
Well Known Member
Hi List
We are currently undertaking an upgrade from 8.0 to 8.12.
We have just come through a very tough data conversion exercise converting from E1 8.0 to 8.12 (unicode). We have 200GB of PD data, which took 15 hrs to export, another 15hrs to import into 8.12 TempDB, an additional 12 hrs to convert to Unicode and finally additional 12 hrs to import into 8.12 PD DB.
This is the procedure performed by our DBA in association with consultant's DBA.
1) Is this the correct procedure?
2) Assuming the procedure is correct, because of our DB size this procedure took 3-4 days. This indicates a massive downtime for the business. How can we minimize system downtime? What can we do differently?
3) The largest table we have is F0911 which has > 40mn records (5 yrs of data). Other large tables are F4211, F42199, F4111 and the other usual suspects. One suggestion is to purge some of these files to hold only 2 yrs data and move the balance to some "offline" files. Then can we split the data conversion process into two schedules. One weekend we do conversion of "Live" files leaving the "offline" files to another weekend. In this way we can speed up the data conversion process.
I could be way off the mark coz i am not a DBA. this post is to get some different possibilities to think about and to encourage my team to consider other alternatives.
Any suggestions are most welcome....
We are on Wintel Oracle 9i (blue stack) moving to Wintel Oracle 10G, 8.12 TR 8.97 (red stack)
Best regards
Shrikanth
We are currently undertaking an upgrade from 8.0 to 8.12.
We have just come through a very tough data conversion exercise converting from E1 8.0 to 8.12 (unicode). We have 200GB of PD data, which took 15 hrs to export, another 15hrs to import into 8.12 TempDB, an additional 12 hrs to convert to Unicode and finally additional 12 hrs to import into 8.12 PD DB.
This is the procedure performed by our DBA in association with consultant's DBA.
1) Is this the correct procedure?
2) Assuming the procedure is correct, because of our DB size this procedure took 3-4 days. This indicates a massive downtime for the business. How can we minimize system downtime? What can we do differently?
3) The largest table we have is F0911 which has > 40mn records (5 yrs of data). Other large tables are F4211, F42199, F4111 and the other usual suspects. One suggestion is to purge some of these files to hold only 2 yrs data and move the balance to some "offline" files. Then can we split the data conversion process into two schedules. One weekend we do conversion of "Live" files leaving the "offline" files to another weekend. In this way we can speed up the data conversion process.
I could be way off the mark coz i am not a DBA. this post is to get some different possibilities to think about and to encourage my team to consider other alternatives.
Any suggestions are most welcome....
We are on Wintel Oracle 9i (blue stack) moving to Wintel Oracle 10G, 8.12 TR 8.97 (red stack)
Best regards
Shrikanth