Hi,
Out B2B application running on Sterling 5.2.6.3_10 with Oracle 11g. DB and working on project to migrate On-Premise to Oracle Private Cloud.
While migrating to Cloud, we have proposed to keep same DB version, so that we don't have change drivers and other associated configurations.
Overall Plan goes like :
1. DBA team clone DB instances over Cloud & Share new URL & port configuration
2. validate connectivity by performing telnet to new DB URL
3. Replicate changes in customer override or jdbc group property files
4. Bring up application and perform validation.
Has anyone experienced this situation or foresees any problem with approach?
I though of executing db_verify.sh script from bin directory, however while reading through IBM forum came across below
Running dbverify.cmd/sh using an Oracle 12g or 11g database can cause table modification SQL to be unnecessarily created even though the tables are already defined correctly.
Ibm |
remove preview |
|
Running dbverify.cmd/sh using an Oracle 12g or 11g database can cause table modification SQL to be unnecessarily created even though the tables are already defined correctly. |
When running dbverify.cmd/sh in IBM Sterling B2B Integrator (B2Bi), it was found that the script would try to change certain tables which had NUMBER or INT data type columns. |
View this on Ibm > |
|
|
Any direction or suggestion will be helpful.
------------------------------
Atul Pawar
------------------------------
#SupplyChain#B2BIntegration