Installing and configuring IBM® Rational® Insight.
- IBM WebSphere® Application
Server does
not get installed
- A previous installation of WebSphere Application Server might not
have been uninstalled successfully. You can:
- I get an error about file manageprofiles.bat or manageprofiles.sh
not found during installation
- A previous installation of WebSphere Application Server might not
have been uninstalled successfully. You can:
- The installation failed while creating the WebSphere Application Server service. What
should I do?
- The WebSphere Application Server service
is likely still registered from a previous installation. You can check
the installed services on Windows® by
opening . If a WebSphere Application Server service
is registered for Rational Insight,
you can remove it by running the following command at the command
prompt:
sc delete SERVICE_NAME
- The installation failed to copy bcprov-jdk14-134.jar because the
file already exists.
- Delete the [rational_insight_installation_directory]/AppServer/java/jre/lib/ext/bcprov-jdk14-134.jar file
or the [websphere_installation_directory]/AppServer/java/jre/lib/ext/bcprov-jdk14-134.jar and
run the installation program again.
- After we start the Rational Insight service,
the application server starts up but the Rational Insight does not
start. If we try to access the BI server at the time, the [rational_insight_installation_directory]/cognos/logs/pogo_DATE.log file
shows the following message: An error has occurred. DPR-ERR-2109
The dispatcher cannot service the request at this time. The dispatcher
is still initializing. Contact your administrator if this problem
persists. Please try again or contact your administrator.
- It may take several minutes for the Cognos® Web application to initialize. The Cognos content store must start
before the Cognos Web application
can initialize. By default, you can view the status of the content
store at http://localhost:9080/insight/servlet/
- There was an error while creating the databases.
- If existing databases have the same names, the creation of the
databases will fail. Either drop the existing databases or specify
new names for the Rational Insight databases.
For
information about the database installation, see the database installation
log files (http://publib.boulder.ibm.com/infocenter/rentrpt/v1r0m0/topic/com.ibm.rational.raer.troubleshooting.doc/topics/ts_locatinglog_container.html.
- Uninstalling Rational Insight does
not remove the rptuser user
- If you do not need the rptuser user for any
other purpose, remove it using the standard system method for removing
users.
- The data warehouse, data warehouse with sample data, and content
store are not removed when Rational Insight is uninstalled.
- If these data warehouses are no longer needed, drop them using
the tools specific for the type of database (DB2®, Microsoft® SQL
Server, Oracle) in use.
- When I enter my DB2 administrator
user name and password, I get a message that they are not valid even
though I know the user name and password are correct.
- Make sure the DB2 service
is started.
- The installation fails with an error while running issetup.exe.
You might be reinstalling IBM Cognos on the system. Before
reinstalling Cognos, you
must reboot the system
Make sure you have the
required packages installed before installing Rational Insight. For details,
see http://publib.boulder.ibm.com/infocenter/rentrpt/v1r0m0/topic/com.ibm.rational.raer.install.doc/topics/t_prereq_rhel5.html
- The reporting server fails to connect to the live ODBC data source.
with Oracle Server: Restart the system.
:
Restart theWebSphere Application Server service.
The data warehouses are not installed correctly on Oracle
11g on Windows 2008 Server
- Make sure at least 6 GB of memory is available.
After a system restart, the reporting server cannot connect
to the Cognos content store.
The /cogserver.log file at [rational_insight_installation_directrory]/cognos/logs/ shows
the following message:CM-CFG-5063 A Content Manager configuration
error was detected while connecting to the content store.CM-SYS-5003
Content Manager is unable to access the content store.
- By default, DB2 is not registered
to be started after a system restart in a Linux® environment. The reporting server requires DB2 to be started first before WebSphere Application Server is started.
To work around the problem:
- After a system restart, start the DB2 database
and restart the reporting server.
- Register your DB2 instances
to be automatically started during a system restart. To do so:
- Run the following command:
db2iauto -on b2iauto -on instance name
- Open the /etc/inittab file in an editor.
- Move the following command from the bottom of the file to just
after the id:5:initdefault: command:
fmc:2345:respawn:/opt/ibm/db2/V9.1/bin/db2fmcd #DB2 Fault Monitor Coordinator
For information on the db2iauto command, at
the (http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp) information center, search for the db2iauto keyword.
Starting the Cognos Configuration
failed.
- This usually happens when you are installing Data Manager or Framework
Manager on a developer machine without installing the reporting server
component. You need to set up the missing environment variables and
libraries. Follow the steps listed in http://publib.boulder.ibm.com/infocenter/rentrpt/v1r0m0/topic/com.ibm.rational.raer.install.doc/topics/t_install_devmachine_container.html.