Suppose there is  database migration planned from Solaris to Linux. This is going to be a new project work and some billing is involved

and client approval is required .

So if the migration plan is designed by Architect team , before we go to customer approval , internal checker process should be done from every department

like

a) architect team

b)_project Management team

c) Finance team

d) DBA team

e) Platform team (Unix / Windows)

f) Monitoring team

g) Mail and messaging team

h) Security team

Let us verify how a DBA team SPOC should review the document/process.

If the SPOC from DBA team is doing this first time ,there is a chance of missing things and later there will be communication

gap and issues in allocating additional resources if required.

1) Verify all existing source server resources like CPU, Memory, Storage and Versions, and DB options used in the the server.

1) Storage value in the Source and Target

2) CPU capacity in the source and target.

3) Source software version and target software version.

4) compatibility of OS and RDBMS/Grid in the target server.

          If there is no official version compatibility we can not not raise Oracle Service requests for any setup.

          For example Oracle 19.18 version on RHEL 9.x, there is no official compatibility between these as of Apr 27-2023.

          If there is installation issue or Database migration issue ,we can not move forward to do the next steps.

5) Sufficient storage space for transporting data between Source and target.

       For example Data migration from Solaris(Big endian)  to Linux(Little Endian).

       here we should do  transporting tablespaces .so need sufficient space in the source target to transfer ASM files.

6) Licensing requirements.

          For example Partitioning, TDE option are going to be used , then need to verify the Licensing details entered or not.

          For example the no.of CPUs should be enabled after procuring the server.