Explanation
S2SS0002: The following SQL statement cannot be converted:
/*
* ROLLBACK TRIGGER WITH
* RAISERROR 130506 @var
*/
Suggest you to convert these statements manually. Actually, rollback trigger statements are supported in sybase but not supported in sql server so it requires some changes.
You can refer to this article:
http://www.devarticles.com/c/a/SQL-Server/Migrating-from-Sybase-to-SQL-Server/1/
More Information
Error
Applies to
• SSMA 2005 for Sybase
• SSMA 2008 for Sybase
Tuesday, August 4, 2009
O2SS0259: CURSOR type was converted to varchar(8000).
Explanation
SQL Server returns cursors in different way than Oracle. SSMA converts cursor parameter to a VARCHAR parameter to keep procedure parameter count, but converts OPEN FOR statement inside stored procedure into a SELECT statement. This works in most cases when procedure is called from outside (client application).
In general, you can safely ignore this warning, because all places which require attention because of this migration issue (passing a cursor as a parameter) are marked with other errors with proper “migration hours” assigned.
More Information
Warning
Applies to
• SSMA 2005 for Oracle
• SSMA 2008 for Oracle
SQL Server returns cursors in different way than Oracle. SSMA converts cursor parameter to a VARCHAR parameter to keep procedure parameter count, but converts OPEN FOR statement inside stored procedure into a SELECT statement. This works in most cases when procedure is called from outside (client application).
In general, you can safely ignore this warning, because all places which require attention because of this migration issue (passing a cursor as a parameter) are marked with other errors with proper “migration hours” assigned.
More Information
Warning
Applies to
• SSMA 2005 for Oracle
• SSMA 2008 for Oracle
Not able to convert Parameterized Queries
Symptom
SSMA Access is not able to convert parameterized queries.
Eg: “>=[forms]![Date_Range]![BeginDate]
Cause
The current version of SSMA doesn’t support parameterized queries.
Resolution
The current version of SSMA doesn’t support parameterized queries. Need to manually convert the queries.
Applies to
• SSMA 2008 for Access
SSMA Access is not able to convert parameterized queries.
Eg: “>=[forms]![Date_Range]![BeginDate]
Cause
The current version of SSMA doesn’t support parameterized queries.
Resolution
The current version of SSMA doesn’t support parameterized queries. Need to manually convert the queries.
Applies to
• SSMA 2008 for Access
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
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
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
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
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
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
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
Monday, August 3, 2009
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
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
Subscribe to:
Posts (Atom)