Can I just check a few things with you.
You are performing offline capture of your Sybase database.
You have "chosen to migrate only Table and Constraints". How did you go about this ? Did you modify the offline capture scripts or the dat files they generated?
SQL Developer Team.
When we start the Migration workflow, there is an option to choose objects to be migrated. We choose "All Constraints and All Indexes".
If you have time we could have a quick zoom conference just to gather some information about the issue.
You can email direct
I'll setup a meeting
We work out of a restricted customer environment and it would be difficult to do a zoom conference. I am taking screenshots of every step that I perform and will mask the sensitive parts. Will share one by Monday morning IST.
I am also working with Customer DBA teams so see if something changed on the Sybase & oracle DB permissions etc.
1 person found this helpful
I am in Ireland so not too many hours difference.
In the mean time here are the steps for offline capture of a Sybase database
I would make sure the offline capture files you are using are all there and the directory structure is present as created by SQL Developer.
Problems can occur if files/directories are removed or modified.
If the files are being moved from linux to windows they may required end of line conversion.
Ohhhh .. This clearly shows we were doing it wrong. We were choosing Tools -> Migration -> Migrate. There In Capture phase we chose All Constraints, All indexes and then for Data we chose Offline and hence were calling this Offline Migration. Your blog has helped.
Will try this and let you know how we progress. Thanks a ton
The following information may help.
You can think of the migration in two parts.
- Metadata Migration (table definitions, index, constraints, procedures, ...)
There are two ways to capture the metadata information. Online and Offline.
Online Metada Migration
If you can make a connection to Sybase from SQL Developer then the preferred way of performing a migration is online.
You use the connection to capture the Sybase metadata over JDBC.
Offline Metadata Migration
If you cannot make a direct connection form SQL Developer to Sybase then the offline capture can be used,
SQL Developer can create some script which execute Sybase BCP commands to dump out metadata information to dat files.
These scripts are copied to your Sybase machine first to be run. Once run and the dat files are created, all the files can be moved back to the SQL Developer machine.
SQL Developer can then perform the capture from these files instead of a Sybase connection.
The data can be migrated in a similar way.
Obviously if you performed the metadata migration using offline method (because you could not directly connect to Sybase) you will have to perform the data move offline.
But its important to note that if you performed the metadata migration online it may be preferable to perform the data migration offline.
Offline Data Move has some advantages over online data move.
Offline Data Move involves SQL Developer generating two sets of scripts
- Unload the Sybase table data into dat files using Sybase BCP . (These can be copied an run on the Sybase machine)
- Load the Dat files into Oracle using SQL*Loader (You move the output of the Sybase unload scripts to your Oracle machine)
Using Sybase BCP and Oracle SQL*Loader scripts gives you far move control and are a lot more robust when moving large amounts of data.
The scripts can also be customised for your project and allow you to reproduce a data move easily.
Heres a video to get you started
Apologies for the late feedback.
But, we were able to migrate using the Offline method for Metadata and Data.