Known Issues for Sybase Control Center

Descriptions of known issues for Sybase Control Center.

Sybase Control Center Issues
CR# Description
735135
  • Failure to create temp DB file when adding a secondary node – When adding a secondary node, the process fails when attempting to create the local temp DB file with the messages:
    Login timed out.  Check that your database server is running on the host and port number you specified. Also, check the database server for other conditions (such as a full tempdb) that might be causing it to hang.
    
    Failed to create local temp DB file <filename on node <nodename>.  
    
    Failed to add n nodes.
  • Workaround
    1. Ensure the MPX is running.
    2. Connect to the failed secondary node (not the Coordinator node) using Interactive SQL.
    3. Execute:
      ALTER DBSPACE IQ_SYSTEM_TEMP 
      ADD FILE temp_db_filename 'path\temp_db_filename.iqtmp' 
      SIZE file_size
    4. Repeat steps 2 and 3 once for each failed secondary node. For more details on the ALTER DBSPACE statement, in the SAP Sybase IQ documentation, see Reference: Statements and Options.
    5. In Sybase Control Center, use Resource Explorer to unregister the MPX resource; the associated nodes are automatically unregistered.
    6. Use Resource Explorer to re-register the MPX resource; the associated nodes are automatically re-registered.
732628
  • When you create a dbfile with the Create DB File wizard, all secondary nodes shut down, fail to synchronize, and fail to restart – You might also see a java.io.IOException in the SCC console or in agent.log. This problem might be specific to Red Hat Enterprise Linux 6.
  • Workaround – None.
731973
  • You cannot create an external procedure – For a 15.3 or 15.4 database, DBA authority is required to create a new external procedure. However, even with DBA authority, an error message appears indicating you do not have privilege/authority to create the object.
  • Workaround – Use Interactive SQL to create the external procedure in SAP Sybase IQ 15.3 or 15.4.
731455
  • Unexpected behavior when starting or synchronizing a multiplex node – When starting or synchronizing a node, if any directory name in the node's path or the database name of the node begins with the letter "n" (for example, c:\database\iq\mpx\node1 or node1.db), the commands fail.
  • Workaround – Start the node outside of SCC and use Interactive SQL to synchronize the node.
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 MPX node and restart it using the appropriate flags to bring the node online as the coordinator. Please 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 Sybase Control Center.
  • 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.
729408
  • You cannot move a partition although you have correct permissions (ALTER permission on the table and CREATE ANY OBJECT system privileges) – The Move option in Table Properties > Partition is unavailable.
  • Workaround – Use Interactive SQL to move the partition.
727450
  • You cannot truncate data although you have the correct permissions (TRUNCATE permission on the materialized view) – The Truncate Data option is unavailable.
  • Workaround – Use Interactive SQL 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.
724117
  • When you manage a large multiplex, changing authentication in SCC can take a long time – Wait times may exceed three minutes.
  • Workaround – None.
721981
  • When you use a 64-bit version of Internet Explorer 9 to read SCC online help, graphics may fail to load – Each missing graphic is replaced with a red X. The problem is most noticeable on the landing page when you first open the online help.
  • Workaround – Use an earlier or a 32-bit version of IE, or use another browser.
721119
  • Script execution is not logged as expected on UNIX-like operating systems – Alert-triggered script executions are not being recorded in SCC-3_2\log\alert-server.log as they are supposed to be. Information about the execution from the RemoteShell Service’s ProcessRunner is appearing in SCC-3_2\log\agent.log, but this is not the alert script execution code that we expect to see logged in alert-server.log.
  • Workaround: – None.
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. This functionality is not implemented in Sybase Control Center.
  • Workaround – Use interactive SQL to change the user's password.
697145
  • You cannot use incremental backups of the Sybase Control Center repository to recover the database
  • Workaround:
    1. Shut down SCC.
    2. Open this file in a text editor: SCC-3_2/services/SccSADataserver/service-config.xml.
    3. Delete this line:
      <set-property property="com.sybase.asa.database.options" value="-m" />
    4. Save the changes and start SCC.
    You can restore the repository database using incremental backups taken after this change.
696767
  • Cannot set timeout and row count options in SCC Properties – 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:
    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.
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: – None.
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
  • Conversion to multiplex disregarded – 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, 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
  • Prolonged authentication – 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.
587717
  • Datatips in monitoring views and the statistics chart appear in fixed locations on the browser screen regardless of where the chart is located. If you move the chart on the screen, the datatips do not move with the chart – (A datatip is a tooltip that displays the data value for a particular spot on a graph or chart when you mouse over that spot.) This occurs in all product module plug-ins.
  • Workaround: – None. This is an Adobe Flex SDK issue.
576129
  • Pressing F5 to refresh your browser logs you out of Sybase Control Center – Browser refresh does not refresh data inside Sybase Control Center, but refreshes the loaded application or pages in the browser—in this case, the Adobe Flash on which Sybase Control Center is built. Consequently, pressing F5 logs you out of any servers you are currently logged in to, including Sybase Control Center.
  • Workaround: – Do not use F5 when you are logged in to Sybase Control Center.
560601
  • Cannot log in because the Sybase Control Center HTTP redirect fails when you use IPv6 format – If you use an IPv6 HTTP URL for Sybase Control Center, it does not redirect to HTTPS as it should. For example, this URL does not work:
    http://myscc64.v6:8282/scc
  • Workaround: – Use a URL with the HTTPS format and port to connect to SCC in IPv6 networks. For example:
    https://myscc64.v6:8283/scc
Related concepts
Known Issues for SAP Sybase IQ Operations
Known Issues for Interactive SQL
Known Issues for Multiplex Environment
Related reference
Restrictions