Known Issues for Sybase IQ

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

Change Request Number Description
686989

Adding multiple users via Shift+click fails in Manage Members and Manage Parent Groups in the Group folder and in Manage Parent Groups in the Users folder.

The selected users are highlighted and moved to the right pane, but when you click OK, the dialog closes, and the users are not added. You can use Shift+click to remove users from groups and groups from parent groups.

Workaround: Use Ctrl+click to add multiple users.

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.

685761

Scripts and e-mail subscriptions are not included when you create duplicates of alerts on multiplex nodes.

Workaround: Create alerts for each node separately, or use the alerts wizard to create duplicates, exit from the wizard, and add alert-triggered scripts and e-mail subscriptions to the duplicates.

685609

Resolving an alert on a multiplex node often hangs if the same alert exists on other nodes.

Workaround:
  1. Wait a few minutes and try again.
  2. Drop the alert and create a new one.

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:
  • Use Sybase Central, which displays the value correctly, or
  • In the SCC Administration Console:
    1. In the left pane, expand IQ Servers > Multiplex Management and select Multiplex Servers.
    2. In the right pane, select a server and click the drop-down arrow that appears to the right.
    3. Select Properties.
    4. In the left pane of the properties dialog, select Server Properties.
    5. 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:
  1. In the Administration Console, select IQ Servers.
  2. Select a server in the right pane and click the drop-down arrow that appears next to the server’s name.
  3. Select Properties.
  4. 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 any other files. Take special care not to remove .iq, .iqtmp, and .log files. Doing so may prevent your server from starting.
676218

When you modify 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:
  1. Close the DB File Properties dialog.
  2. Click DB Files in the left pane of the Administration Console.
  3. In the Folder menu, select Refresh.
  4. Select the dbfile in the right pane, click the drop-down arrow, and select Properties.
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

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.

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: Configure the options in Sybase Central.

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.

667673

The Create Dbspace wizard incorrectly allows you to create a dbspace from a multiplex reader.

The dbspace created is valid.

Workaround: None.

667667

If a Sybase IQ simplex server that is registered in Sybase Control Center is converted to a multiplex server using another instance of SCC, Sybase Central, 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.

651730

If you change the name of a Sybase IQ server in Sybase Control Center or in Sybase Central while the Topology map of the IQ Multiplex Level Monitor is open, the name change does not update in the Topology map.

Workaround: Close the IQ Multiplex Level Monitor and reopen it.

640584

When you authenticate a Sybase IQ server, enter the user ID in Sybase Control Center in the same case in which it is defined in the Sybase IQ sysuser table.

When the cases do not match, SCC authenticates the server—for example, if the sysuser entry says DBA you can authenticate as dba—but you cannot make changes in the Administration Console.

Workaround: None.