Specifications

Red Hat Enterprise Linux to Oracle Solaris Porting Guide
15
POPULAR PROPRIETARY DATABASES
Oracle 11gR2 √ √
DB2 9.7.x √ √
Sybase 15.7.x √ √
Informix 11.7.x √ √
Though it is challenging to move data between proprietary databases, most of the database vendors
ship tools to aid this type of data migration.
For information about migrating from various proprietary databases to Oracle Database, please refer
to http://www.oracle.com/technetwork/products/migration/index-084442.html
.
Application Verification
Code Coverage
Functional testing is the most critical phase in the migration process. Many of the system calls and
features on both platforms look similar, but there are subtle behavioral differences that can be
uncovered only during testing. Even if the code compiles on the new platform, it might behave
significantly different during actual test runs. Hence, it is very important to ensure that the applications
are thoroughly tested on the target platform.
Oracle provides powerful tools to help track code coverage during testing as well as to unearth difficult
to detect code issues, such as memory leaks. One such tool is Uncover, which is a code-coverage tool
bundled with Oracle Solaris Studio software.
To use Uncover on Oracle Solaris 11, the following steps must be performed:
• The code must be compiled with Oracle Solaris Studio optimization flags -xO[n]. For example, a
typical compilation command line looks like the following:
cc -g -xO2 test.c
•
Instrumentation codes should be added to the binary using the following command:
uncover a.out
•
When the instrumented binary is run and regular functional testing is performed, the code-coverage
data will be stored in the following directory:
/tmp/project/a.out.uc
•
Then this Oracle Solaris Studio tool can be used to generate the report: