Known Issues for SAP Sybase IQ

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

Change Request Number Description

You cannot use SCC to install a Java class on an SAP IQ server.

When you try to install a Java class, SCC might display an error saying the external executable could not be found. Running SELECT db_property('JAVAVM') ought to return the location of java.exe or java, but it returns nothing.

Workaround: This is a configuration problem. To enable the SAP IQ server to support Java in the database, run this SQL:
  • Windows: alter external environment java location 'C:\\sap\\server\\Shared\\SAPJRE-7_1_015_64BIT\\bin\\java.exe';
  • UNIX: alter external environment java location '//opt//sap//server//shared//SAPJRE-7_1_015_64BIT//bin//java';
Note: If necessary, change the path above to match your installation directory and its shared Java directory.

The agent status for a multiplex server is unknown.

A multiplex server may display Agent Status "Unknown" in Admin Console > Multiplex Servers when the agent is running and has been previously authenticated. If you reauthenticate the agent, the status soon returns to "Unknown."

Workaround: In the Resource Explorer, unregister and reregister the multiplex resource.


You cannot change the TDS port number during installation.

TDS, or Tabular Data Stream, is a common application protocol that SCC servers and SCC agents use to exchange information. The TDS port number is set to 9998 and enabled by default during installation. Choosing an alternate TDS port number is not currently an option within the SAP Sybase IQ installer.

If the TDS port is in use by another application, SCC might fail to start or function properly.

Workaround: To identify and resolve TDS port conflicts:
  1. Shut down SCC according to the method you used to start it. For example, if you started from a command line, stop the background process or enter shutdown at the scc-console prompt. If you are running SCC as a service, stop the SAP Control Center service.

  2. To return a list of SCC ports indicating whether each port is in use, enter:

    Windows: scc --info ports

    UNIX: --info ports

    Any port in use when SCC is not running is likely to have a conflict.

  3. If you identify a port conflict, change the TDS port to a port in the range 1025 to 65535 that is not in use by another application. For example:

    Windows: scc --port tds=9997

    UNIX: --port tds=9997

  • Alert wizard - New member for logical server not shown – After you add a new member to a logical server using a method other than SCC (for example, dbisql), the Alert Wizard for that logical server does not display the new member.
  • Workaround: – Open Logical Server Properties for the logical server to the Membership page, uncheck the member added outside SCC, click Apply, then recheck the member and click Apply/OK. Now that member node displays.
  • Create Dbspace wizard - Multiplex Node drop-down list is empty – From the Perspective Resources view, if you select an IQ Server representing a multiplex node, and then open the Create Dbspace wizard from the Administration Console, clicking the drop-down arrow next to Multiplex Node displays an empty list.
  • Workaround: – From the Perspective Resources view, select the IQ Multiplex, not an IQ Server representing a multiplex node. Open the Administration Console and start the Create Dbspace wizard. Multiplex nodes display when you click the drop-down arrow next to Multiplex Node.

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.

  • 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.

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.


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 
  1. Shut down SAP Control Center.
  2. Log on as root.
  3. Execute: ln –s /usr/bin/env /bin/env
  4. Restart SAP Control Center.
  5. Log on as the original user.
  6. Retry the task.

Dual control password management does not work.

When the Change Password Dual Control option is enabled in a user login policy, an error message appears if you attempt to change the user password. Dual control password management is not currently implemented in SCC.

Workaround: Use Interactive SQL to change the user’s password.


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 SAP Control Center for SAP Sybase IQ.

Workaround: None.


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.


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:
  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.

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,, and
Note: Do not remove .iq, .iqtmp, and .log files. Doing so may prevent your server from starting.

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:
  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.

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.


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.


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.

(Sybase Central is now known as SQL Central.)

Workaround: Use Interactive SQL to configure the options.


The Administration Console 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.


If an SAP Sybase IQ simplex server that is registered with SAP 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.


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.