SRV - Limitations

French menus visible prior to connection

After launching CAST Server Manager and before connecting to a database server, CAST Server Manager displays its menus in French: (Fichier, Edition, Affichage) instead of in English (File, Edit, View). After connecting, all menus change correctly to the English language as expected.

Separate tablespaces/devices for tables and indexes

When a CAST database (Analysis/Dashboard/Management Service) has been installed using the option to install tables and indexes on separate tablespaces/devices, the following restrictions apply:

Import/Export of a CAST database using native RDBMS tools

When exporting a CAST database using and then importing it on a different server using native RDBMS tools, the new server must have tablespaces/devices with the same name as the tablespaces/devices used on the original server for the installation. Otherwise, loading the exported dump will produce SQL errors.

Indexes on tablespace/device for tables

The following two indexes are stored in the tablespace/device dedicated for tables rather than in the tablespace/device dedicated for indexes:

  • VWER_USR_OBJ_IDX
  • VWER_USR_ACC_IDX

The two indexes need to be considered as technical tables used by CAST’s own internal processes and therefore need to reside in the tablespace/device for tables.

SQL errors when connecting to Microsoft SQL Server

Situation:

  • Using CAST Server Manager to connect to Microsoft SQL Server and using a login that does not have access to some of the databases on the server (a login does not have access to a database if the login cannot perform the “use ” statement).

Symptoms:

An error message is displayed in CAST Server Manager for each database the login cannot access: ‘‘The server principal ‘xxx’ is not able to access database ‘yyy’. This indicates that CAST Server Manager cannot determine if the database is a CAST database or not, as such, the database will not be taken into account by CAST Server Manager, even if it is a CAST database.

Component Uninstall on Oracle 10g

If your CAST database (Analysis/Dashboard/Management Service) are installed on an Oracle 10g (or later) database server, please note that using the Component Uninstall option in CAST Server Manager to uninstall the CAST schema will not remove all objects.

You may find that certain triggers remain visible in the schema even after the uninstallation process has terminated. This issue is related to the use of the RECYCLEBIN on Oracle 10g. To remove any remaining objects, please use the PURGE RECYCLEBIN command with login credentials for the owner of the CAST database in question.