The installation of the Sun Web console Version 2.0.3 fails with the follow error message:
# ./inst_reporting ... Register the N1 SGE reporting module in the webconsole Registering com.sun.grid.arco_6u3. Starting Sun(TM) Web Console Version 2.0.3... Ambiguous output redirect. |
. This Sun Web Console Version can only be installed by the user noacces who has /bin/sh as their login shell. The user must be added with the following command:
# useradd -u 60002 -g 60002 -d /tmp -s /bin/sh -c "No Access User" noaccess |
The table/view dropdown menu of a simple query definition does not contain any entry, but the tables are defined in the database.
Solution:The problem normally occurs if Oracle is used as the database. During the installation of the reporting module the wrong database schema name has been specified. For Oracle, the database schema name is equal to the name of the database user which is used by dbwriter (the default name is arco_write). For Postgres, the database schema name should be public.
Problem:Connection refused.
Solution:The smcwebserver might be down. Start or restart the smcwebserver.
Problem:The list of queries or the list of results is empty.
Solution:The cause can be any of the following:
The database is down. Start or restart the database.
No more database connections are available. Increase the number of allowable connections to the database.
An error exists in the configuration file of the application. Check the configuration for wrong database users, wrong user passwords, or wrong type of database, and then restart the application.
No queries are available. If the query directory /var/spool/arco/queries is not empty, the following errors might have occurred:
Queries in the XML files are syntactically incorrect. Check the log file for error messages from the XML parser.
User noaccess has no read or write permissions on the query directory.
The list of available database tables is empty.
Solution:The cause can be any of the following:
The database is down. Start or restart the database.
No more database connections are available. Increase the number of allowable connections to the database.
An error exists in the configuration file of the application. Check the configuration for wrong database users, wrong user passwords, or wrong type of database, and then restart the application.
The list of selectable fields is empty.
Solution:No table is selected. Select a table from the list.
Problem:The list of filters is empty.
Solution:No fields are selected. Define at least one field.
Problem:The sort list is empty.
Solution:No fields are selected. Define at least one field.
Problem:A defined filter is not used.
Solution:The filter may be inactive. Modify the unused filter and make it active.
Problem:The late binding in the advanced query is ignored, but the execution runs into an error.
Solution:The late binding macro has a syntactical error. The correct syntax for the late binding macro in the advanced query is as follows:
latebinding{attribute;operator} latebinding{attribute;operator;defaultvalue} |
The breadcrumb is used to move back, but the login screen is shown.
Solution:The session timed out. Log in again, or raise the session time in the app.xml.
Problem:The view configuration is defined, but the default configuration is shown.
Solution:The defined view configuration is not set to be visible. Open the view configuration and define the view configuration to be used.
Problem:The view configuration is defined, but the last configuration is shown.
Solution:The defined view configuration is not set to be visible. Open the view configuration and define the view configuration to be used.
Problem:The execution of a query takes a very long time.
Solution:The results coming from the database are very large. Set a limit for the results, or extend the filter conditions.