Known Issues for SAP Sybase IQ

Known issues and workarounds for Sybase Control Center for SAP Sybase IQ.

Change Request Number	Description
737595	Adding a hash or hash-range partition to an unpartitioned table causes a server error. If you attempt to add a hash or hash-range partition to an existing unpartitioned table, an error message appears. If you unpartition a table with a hash or hash-range partition, you cannot re-add it. This behavior does not occur when adding a range partition to an existing unpartitioned table. Workaround – Create a new table with a hash or hash-range partition. Migrate the data from the original table to the new table, and then drop the original table.
736548	Behavior #1: Missing multiplex resource in the Perspective window. Only the original simplex resource appears. After you convert a simplex resource to a multiplex resource, the wizard indicates success, but the new multiplex resource does not appear in the Perspective Resources view. Only the original simplex resource appears. If you open the Administration Console and click IQ server, the error message `Object detail load failed` appears. No objects for the simplex resource appear in the folders of the Administration Console. Workaround Stop and restart the SCC server. Log in to SCC. In the Perspective Resources view, re-authenticate the simplex resource. The simplex resource becomes a functioning multiplex resource. Behavior #2: Missing objects for the coordinator IQ server resource in Administration Console folders after creating a new multiplex resource. After converting a simplex resource to a multiplex resource, no objects for the original simplex resource (now the coordinator resource) appear in the various folders in the administration console. Workaround: Stop and restart the SCC server. Log in to SCC. In the Perspective Resources view, re-authenticate the multiplex resource. Objects now appear for the coordinator resource.
735485	Behavior #1: Server error when refreshing a text index. When you click the Refresh Now button on the properties page of a text index, the process fails with the message: Index name, object name and object owner must be either all null or all non-null Workaround #1: In the left pane of the Administration Console, select IQ Servers > Schema Objects > Tables > Tables. Select the table on which the text index is based in the right pane and either: Click the arrow to the right of the name and select Properties, or From the Administration Console menu bar, select Resource > Properties. In the left pane, select Text Indexes. In the right pane, select the text index, and click Refresh. Workaround #2: In the left pane of the Administration Console, select IQ Servers > Schema Objects > Text Indexes. Select the text index from the right pane and either: Click the arrow to the right of the name and select Refresh Data, or From the Administration Console menu bar, select Resource > Refresh Data. Note: This workaround is available for all refresh types except Snapshot. Behavior #2: Server error when truncating a text index. When you click the Truncate Now button on the properties page of a text index, the process fails with the message: com.sybase.scc.jmx.ManagedObjectGateway.err_invoke_op Access Workaround #1: In the left pane of the Administration Console, select IQ Servers > Schema Objects > Text Indexes. Select the text index from the right pane and either: Click the arrow to the right of the name and select Truncate Data, or From the Administration Console menu bar, select Resource > Truncate Data. Workaround #2: In the left pane of the Administration Console, select IQ Servers > Schema Objects > Tables > Tables. Select the table on which the text index is based in the right pane and either: Click the arrow to the right of the name and select Properties, or From the Administration Console menu bar, select Resource > Properties. In the left pane, select Text Indexes. In the right pane, select the text index, and click Truncate.
732628	Some nodes in a multiplex shut down after adding a DB file to IQ_SYSTEM_MAIN. When adding a DB file to IQ_SYSTEM_MAIN, any node in the multiplex whose agent is not registered and authenticated becomes stopped. Workaround: In the left pane of the Administration Console, select IQ Servers > Multiplex Management > Multiplex Servers. Select a stopped node from the right pane and either: Click the arrow to the right of the name and select Register Agent, or From the Administration Console menu bar, select Resource > Register Agent. Accept the defaults displayed and click OK. Select the same node from the right pane and either: Click the arrow to the right of the name and select Authenticate Agent, or From the Administration Console menu bar, select Resource > Authenticate Agent. Type the SCC agent password and click OK. Select the same node from the right pane and either: Click the arrow to the right of the name and select Synchronize Server, or From the Administration Console menu bar, select Resource > Synchronize Server. Click Finish to start the synchronization. Click Close when synchronization is complete. Select the same node from the right pane and either: Click the arrow to the right of the name and select Start Server, or From the Administration Console menu bar, select Resource > Start Server. Click Finish to start the server. Click Close when the server is successfully started. Repeat these steps for each stopped node in the multiplex.
730793	In the Failover Wizard, if both the coordinator node (CN) and designated failover node (DFO) are stopped, and you select a new failover node, an error message appears, and the failover fails. This behavior occurs because the CN must be running in order to select a different failover node. Workaround: Use Interactive SQL to stop the multiplex node and restart it using the appropriate flags to bring the node online as the coordinator. Contact technical support for further assistance.
729451	You cannot grant or revoke permissions on a proxy table. The functionality to grant and revoke object-level permissions on a proxy table at the table level is not currently implemented in SCC. Workaround: Grant the object-level permissions at the user, group (15.3 and 15.4) or role (16.0) level. Use Interactive SQL to grant the object-level permissions at the table level.
727450	You cannot truncate data although you have the correct permissions (TRUNCATE permission on the materialized view)—the Truncate Data option is not available. Workaround: Use dbisql to truncate.
724206	User impersonation does not work. The functionality to configure one user to temporarily assume the roles and system privileges of another user (known as impersonation) is not currently implemented in SCC. Workaround: Use Interactive SQL.
723112	Performing a task that includes database validation on a SUSE platform causes a server error. The process fails with the message: SCC Agent <host_name>:9999 does not know Sybase IQ version string. Something is wrong with the IQ Agent plug-in Workaround: Shut down Sybase Control Center. Log on as root. Execute: ln –s /usr/bin/env /bin/env Restart Sybase Control Center. Log on as the original user. Retry task.
716431	Dual control password management does not work. When the Change Password Dual Control option is enabled in a user’s login policy, an error message appears if you attempt to change the user’s password. Dual control password management is not currently implemented in SCC. Workaround: Use Interactive SQL to change the user’s password.
696767	Administration Console options in the SCC Properties dialog (Application > Administration > General Settings > Administration Console) let you set timeout and row count thresholds for data retrieval. These settings have no effect in Sybase Control Center for SAP Sybase IQ. Workaround: None.
686963	If you use Server Properties to change the server configuration, and you also make changes at Request Logging or Options pages, the server configuration process runs but does not make the additional changes. Workaround: Make changes in Server Properties from individual pages and click OK for each page.
685207	The Liveness Timeout value for multiplex secondary servers always appears as 0 seconds in the INC Properties dialog. Even if you leave the value at the default (120 seconds) or set it in the Configuration Editor and restart, the INC Properties dialog displays a Liveness Timeout of 0 seconds. The value is correct on the server; only the display is wrong. Workaround: In the SCC Administration Console: In the left pane, expand IQ Servers > Multiplex Management and select Multiplex Servers. In the right pane, select a server and click the drop-down arrow that appears to the right. Select Properties. In the left pane of the properties dialog, select Server Properties. In the right pane, enter `liv` in the filtering field above the Name column. This filters out all the properties except Liveness Timeout.
676665	If you change the database location, restart the server, and later try to change back to the previous location, the server fails to start. The failure occurs because old database files remain in place when you change to a new location. If you change back to an old location, the server finds out-of-date files. To view or change the path to the database location: In the Administration Console, select IQ Servers. Select a server in the right pane and click the drop-down arrow that appears next to the server’s name. Select Properties. In the left pane of the properties dialog, select Configuration. Workaround: Before changing back to the old location, remove the .db, iqmsg, and .lmp files from the old location. If they exist, also remove params.cfg, start_server.sh, and stop_server.sh. Note: Do not remove .iq, .iqtmp, and .log files. Doing so may prevent your server from starting.
676218	When you modify property values in the Dbspace Properties dialog in the Administration Console, changes to dbspace properties that should propagate to the DB Files Properties dialog do not automatically do so. Workaround: If your changes to the Dbspace Properties dialog do not appear in the DB Files Properties dialog: Close the DB File Properties dialog. Click DB Files in the left pane of the Administration Console. In the Folder menu, select Refresh. Select the dbfile in the right pane, click the drop-down arrow, and select Properties.
676079	In the Configuration File Editor, the Maximum Output File Size uses kilobytes as the default. There is no way to specify MB or GB. Workaround: In the params.cfg file in the database directory, set the value with the -zs switch. Use K, M or G after the numerical value. For example: `-zs 4000K`, `-zs 240M`, or `-zs 30G`.
676076	In the Debug page of the Configuration File Editor, the following logging levels are missing from the Debug Level drop-down: "other," "procedures," "triggers," "plan," "hostvars," "replace," and "blocks." Workaround: To set the debug level to any of the missing levels, set the -zr switch in the params.cfg file in the database directory. You can include more than one level. For example: `-zr procedures,triggers,plans`.
670173	The Database Options, Group Options, and User Options dialogs do not allow these actions provided in Sybase Central: Create Options, Remove Options, and Mark Options as Permanent. Workaround: Use Interactive SQL to configure the options.
669571	The Administration Console’s Execute SQL window returns no status for successful queries that return no results. Interactive SQL users expect a message like `Execution time: 0.01 seconds`. Workaround: None.
667667	If an SAP Sybase IQ simplex server that is registered in Sybase Control Center is converted to a multiplex server using anything other than this instance of SCC (including another instance of SCC or the command line), the current SCC does not detect the conversion and continues to display the server as simplex. Workaround: Reauthenticate the simplex resource so that SCC displays it as multiplex.
666382	Authentication can take a very long time, especially when the resource is a multiplex. In some cases, the authentication dialog fails to dismiss. Workaround: You can safely click Cancel to dismiss the Authentication dialog at any time after you click OK.