| 664781 |
SQL error reported for successful execution.
After a project or job executes successfully, Sybase IQ InfoPrimer may report an error similar to: SQL error: SQL error: SQL logic error or missing database
ERROR : SQL error: SQL error: SQL logic error or missing database
The SQL statement executed was:
INSERT INTO job_history(timestamp, execid, data) values(:?, :?, :?)
ERROR : 1100: SQL error: SQL error: SQL logic error or missing database
This error occurs when Sybase IQ InfoPrimer does not have permission to read from and write to the job_log.db3 file in the database folder of the installation directory.
Note: For Windows Server 2008 and Windows Vista, job_log.db3 is in C:\Users\<login user>\AppData\Roaming\SYBASE\Sybase
IQ InfoPrimer Development\<product version>\database, where <login userid> is the user ID used during installation.
Workaround: Grant permission for Sybase IQ InfoPrimer to read from and write to the job_log.db3 file.
|
| 648941 |
Save keyboard shortcut fails to save project changes.
Sybase IQ InfoPrimer Development may fail to save your project changes if you use the Ctrl+S keyboard shortcut, even though an information dialog reports "Successfully saved the changes."
Workaround: Click the Save Project icon below the menu bar to save your project.
|
| 588669 |
Replication Server does not recognize the interfaces name.
If the SYBETL_VIR_RDBMS entry in the interfaces
files for the source database, Replication Server, and Sybase IQ InfoPrimer Server,
includes more than 20 lines, Replication Server does not recognize
the interface name.
Workaround: Make sure that the SYBETL_VIR_RDBMS
entry in the interface file contains fewer than 20 lines.
|
| 588134 |
Demo database points to the datasource of the old repository.
If you have previously installed ETL Development, and you uninstall
it to install Sybase IQ InfoPrimer Development for all users, when any user other than
the one who installed it tries to connect to the repository, the
demo database connects to the datasource of the ETL Development
repository.
Workaround: If the previously installed ETL Development was installed
for all users, before upgrading, log in as each user and use the
ODBC Data Source Administrator to delete the DEMO_Repository,
ETLDEMO_DWH, ETLDEMO_GER, and ETLDEMO_US
datasources. If you do not plan to uninstall ETL Development, you may want to rename the datasources instead
of deleting them. For example: <old name_version
number>.
See Sybase IQ InfoPrimer Installation Guide > Upgrading Sybase ETL to Sybase IQ
InfoPrimer.
If you have already installed Sybase IQ InfoPrimer Development without
renaming or deleting the old datasources, manually delete the old
datasources. Follow the steps described in Sybase IQ InfoPrimer Installation Guide > Postinstallation Tasks > Restoring ODBC Datasources.
Note: Make sure that you specify the database files in the
user data location, not in the installation location.
If you encounter errors when trying to delete the old datasources, you can overwrite the entries for each user, as follows:
Save a copy of the userdata.conf file
located in the etc folder of the installation
directory.
Edit the userdata.conf file
to replace all occurrences of “once” with “always” in
the ODBC section.
For each user:
Log in to the machine,
start Sybase IQ InfoPrimer Development, and then shut down the application.
Verify that the ODBC Data Source entries use SQL
Anywhere 11 and point to the appropriate database files in your
user data directory.
After all users have logged in to Sybase IQ InfoPrimer Development, you can
restore the original userdata.conf file.
See Sybase IQ InfoPrimer Installation Guide > Postinstallation Tasks > Checking the Sybase IQ InfoPrimer Development
Installation.
|
| 587862 |
Errors encountered if interface used for connecting to IQ is changed.
If you change the interface used for connecting to the Sybase IQ
database, an error may occur, and the component may fail to connect
to IQ.
Workaround: Restart the grid engine after
changing the interface.
|
| 587639 |
Upsert function is processed even when truncate is selected.
In spite of the Truncate option being selected, the target
tables do not get cleared before the Pre-processing SQL code executes.
Thus, the Upsert or Delete function is processed on a non-empty
table, leading to errors.
Workaround: To clear and repopulate target
table before processing Upsert or Delete functions, make sure Truncate
is unselected, and perform clearing of the table in pre-SQL script.
|
| 582762 |
Connection to Sybase IQ in Sybase Central fails if Sybase IQ InfoPrimer Development is uninstalled.
If Sybase IQ 15.3 and Sybase IQ InfoPrimer are installed on the same Windows machine
and you uninstall Sybase IQ InfoPrimer Development, you cannot then use Sybase Central™ to connect
to the IQ demo database.
Workaround: In a DOS window, register the dbodbc11.dll driver file from the IQ InfoPrimer Server or IQ installation:
regsvr32 %SYBASE%\IQIPS-15_3\dbodbc11.dll
Or, regsvr32 %SYBASE%\IQ-15_3\bin32\dbodbc11.dll
|
| 560953 |
Multiplex execution fails on Linux and UNIX machines that do not have ODBC drivers installed.
Project execution fails if you select the “Use IQ
Multiplex” option on a UNIX or Linux machine that does
not have SQL Anywhere 11 or Sybase IQ 15 ODBC drivers installed.
Workaround: Use the SQL Anywhere 11 ODBC
drivers installed with Sybase IQ InfoPrimer.
|
| 549882 |
Error messages display when you migrate tables with large number of columns.
If you migrate wide tables using the Migration wizard, you may
see this error message at the end of the migration process: An error occurred during execution of the engine.
Commit Failed: Client Library Message: severity(0)
layer(1) origin(1) number(50) Text: ct_cmd_drop(): user
api layer: external error: The connection has been
marked dead.
Cannot execute the last command.
Please refer to the Message section.
The migration failed due to the previous error. Unable to open the generated job.
Despite the error message, the table is successfully migrated
to the target database, and you can manually open the generated
job to transform the data.
Workaround: This error displays if you
are using the Sybase interface to connect to the source database
and if the OCS version being used is 15.0 ESD #13 or later.
To prevent this error: Use the ODBC interface
to connect to the source database.
If you are using Sybase interface to connect to
the source database, use OCS version 15.0 ESD #7.
|
| 546658 |
Project reports printed as XML fail to open in Windows Vista.
On Windows Vista Business 32-bit, Sybase IQ InfoPrimer may generate errors
when displaying project reports that are generated using XML output.
Workaround: Install Service Pack 1 on
Windows Vista.
|
| 531483 |
The uSetLocale JavaScript function works only on Windows platforms.
The uSetLocale javascript function only
works on Windows platforms. On UNIX platforms, setting uSetLocale to
any language will still display output in English for uMonthName, uMonthNameShort, uWeekdayName,
and uWeekdayNameShort.
Workaround: None.
|
| 496346 |
Table and column names cannot be database keywords in Migration wizard.
In the Migration wizard, you cannot use the "variable" database
keyword as the name of a table or column.
Workaround: None.
|