Nothing to Process error when creating Assessment report

Symptom
When user tries to create Assessment Report by click “Create Report” they may get error “There is Nothing to process”

Cause
We get this message if there are no objects in the node selected.

Resolution









As there are no objects in any of the schemas(as shown above) you are getting that message ”There is nothing to process”. You can create report only when you have objects(tables,Procedures etc) in the node selected.
In the above the user guest does not have access to any database objects. So there are no objects under guest schema. If the above user is given permission to those objects, then those objects will be visible in Metadeta explorer. Then you won’t get this error message.

More Information
Article Id: KBS2SS1010

Applies to
• SSMA 2005 for Sybase
• SSMA 2008 for Sybase

UDF not converted by SSMA

Symptom
When using ASE 15.0.2 version SSMA is not able to convert the User Defined functions.

Cause
SSMA does not support this Sybase version

Resolution
User defined functions have to be converted manually.
UDF were introduced in Sybase ASE 15.0.2and SSMA for Sybase v4.0 doesn’t support this version.

More Information
Article Id: KBS2SS1009

Applies to
• SSMA 2005 for Sybase
• SSMA 2008 for Sybase

Text columns get truncated to a size of 32K

Symptom
When using SSMA 2008 for Sybase for Data migration “text” columns may get truncated to a maximum of 32K

Cause
Text columns can get truncated because of default value of textsize property.

Resolution
Text columns can get truncated because of default value of textsize property. The default size of TextSize attribute of Oledb provider is 32K so if the data is more than 32K , its getting truncated in your case.
As a workaround, you can set the connection string in advanced mode to connect to Sybase.

In the connection string include a parameter ‘textsize’ as shown and assign it the maximum number of characters you have in all your text columns ,so that it won’t truncate data.
Sample connection string:
User ID=myID;PWD=abc;Provider=ASEOLEDB.1;Server=myserver;Port=5000;Database=master;
textsize=;
(Note: Change Provider according to your version)

More Information
Article Id: KBS2SS1008

Applies to
• SSMA 2005 for Sybase
• SSMA 2008 for Sybase

Preventing regeneration of Identity columns

Symptom
When doing data migration SSMA may regenerate the identity columns.

Cause
Keep Identity property in Project settings is set to false

Resolution
Setting the “Keep Identity” in the Migration tab of the Project settings to true.
Keep identity Specifies whether SSMA will preserve identity values when it inserts data into SQL Server. If this value is false, SQL Server will assign identity values. The default is true.
When Keep Identity is set to true, the data of the identity column resembles the data in the source database.
When Keep Identity is set to false, Identity columns are regenerated when inserting data in the SQL Server table and it will assign identity values taking seed and increment as 1


More Information
Article Id: KBS2SS1007

Applies to
• SSMA 2005 for Sybase
• SSMA 2008 for Sybase

SSMA Extension pack not found on database server

Symptom
When doing Data migration using SSMA user may encounter the following pop-up message:
Failed prerequisites list:
Common requirement: SSMA extension pack was not found on the database server. Install the SSMA extension pack to use the data migration.

Cause
This error message usually occur when
a) Extension pack is not installed on SQL Server instance
b) The Sysdb and ssma_syb databases doesn’t exist on the sql server instance which you are trying to connect or is not accessible because of lack of permissions.

Resolution
a) Install the extension pack on SQL server instance.
b) Ensure that the Sysdb and ssma_syb databases exists on the sql server machine which you are trying to connect and is accessible.

More Information
Article Id: KBS2SS1006


Applies to
• SSMA 2005 for Sybase
• SSMA 2008 for Sybase

Timeout error when migrating data in a large table

Symptom
Data Migration times-out for a particular table that contains around 100000 rows (the error message is ‘The command has timed out.’). Sybase OLEDB provider was used to connect to ASE 15.0.2 (on Windows 2003 32bit)

Cause
This is caused when using OLEDB provider to connect to Sybase, which fails when trying to read large tables using cursors.

Resolution
If you are using Oledb provider and facing the same issue, this can be resolved in two ways:
1) It’s failing when oledb provider is trying to read large tables using cursors.
You can give the connection string in Advance mode by setting property UseCursor=0 . Please see the below image for more details.

Sample Connection string:
User ID=sa;PWD=abc;Provider=ASEOLEDB.1;Server=myserver;Port=5000;Database=master;UseCursor=0;
(Please remember provider should be changed as per your sybase version)

2) You can consider changing the provider to ADO.Net provider. Please follow the following process to change the provider:Tools menu => Click on ProjectSettings=> Migration Tab and use the Provider dropdown to change the provider.


More Information
Article Id: KBS2SS1005

Applies to
• SSMA 2005 for Sybase
• SSMA 2008 for Sybase

The table does not exist in SQL Server

Symptom
When trying to migrate data using SSMA user may get the above error. When clicked on "Migrate Data", after entering the user name and password, it pops up "The table 'xxxxxx' does not exist in SQL Server. You must first convert the table and then load it into the database."

Cause
This error occurs when user tries to migrate the data before doing the ‘synchronize with the database’ operation.

Resolution
This error message generally occurs when the target table doesn’t exist on sql server database. After converting schema, you need to synchronize the table with the database before migrating the data. To do this you right click on the SQL Server database in Metadata explorer and click “Synchronize with database” menu. The table structure will not be created in the sql server database until you synchronize.

More Information
Article Id: KBS2SS1004

Applies to
• SSMA 2005 for Sybase
• SSMA 2008 for Sybase

Data Migration reports migration for each row in table

Symptom
During data migration of even very big tables, SSMA reports migration of each single data row. This slows down data migration.

Cause
ADO.NET Data Provider for Sybase has a bug in some versions, when AseCommand.ExecuteReader(CommandBehavior.SingleRow) returns AseDataReader which returns false from Read() method when called even though SQL statement returns one single row.

See http://search.sybase.com/kbx/changerequests?bug_id=485824 for details.

This bug is proved to be in the following Sybase provider version: 1.15.152.0.

Resolution
Use OleDb Sybase provider or install ADO.NET Data Provider of version 1.15.50.

More Information
Article Id: KBS2SS1003

Applies to
• SSMA 2005 for Sybase
• SSMA 2008 for Sybase

Extension Pack is corrupted error

Symptom
When SSMA is used the user can get an error message saying: Failed prerequisites list:
Common requirement: Extension Pack is corrupted or You do not have permission to use it.

Cause
Incorrect privileges of the user. User doesn’t have the privilege to run the following query: SELECT * FROM sysdb.sys.schemas where name = 'ssma_syb'

Resolution
Give the sufficient privileges to the user.
Depending on the operation user performing, following permissions are required:

• For most operations it is enough to give a user an access to the database and grant a role ssma_syb.
• If a user needs to perform a data migration, rights to create and start job will be needed (including CmdExec).
• If a user needs to work with tester, we highly recommend giving the user full rights on ssmatesterdb_syb database.

More Information
Article Id: KBS2SS1002

Applies to
• SSMA 2005 for Sybase
• SSMA 2008 for Sybase

SQL Server cannot access the source table

Symptom
When Migration Assistant is used to move a table from Sybase ASE 12.5 into MS Sql Server 2005 when they the data migration, they get this in the results pane:
Migrating data...
Analyzing metadata...
Preparing table dbo.table1...
Preparing data migration package...
Starting data migration agent...
Starting data migration...
The data migration agent is migrating table 'dbo.table1': >
dbo.table1, 0 rows total
SQL Server cannot access the source table.
Data migration complete.
0 table(s) successfully migrated.
0 table(s) partially migrated.
1 table(s) failed to migrate.

Cause
This issue may occur due to following:
• User credentials used for data migration may not have SELECT permission on this table.
• There are lots of issues with different versions of Sybase providers so need to check the type and version of the driver you are using.

Resolution
The users usually get this error when they use OleDb provider for Sybase for data migration. To resolve this try using ADO.NET provider of version 1.15.50. You can set it up in Project Settings dialog using "Provider" dropdown.

More Information
Article Id: KBS2SS1001

Applies to
• SSMA 2005 for Sybase