You can identify when component failover occurs by noting the symptoms that a failure causes in the application. There can be an interruption to service or an error can occur during a web browser session. If you experience a symptom of failover, you can use one of the solutions that are listed to continue your web browser session.
The symptoms can vary, depending on the components that are in use at the time of failover.
The following symptoms indicate that failover might have occurred during processing of the database.
Symptom | Indicator | Solution |
---|---|---|
An error occurs when you select a record from the list in an application. | You see the following error message: Error BMXAA6712E: The database connection failed and the record was not retrieved. Try the operation again. If you experience repeated failures, check the log files in the home directory or contact your system administrator. | Close the error message and reselect the record from the list. |
An error occurs when you search for a record in an application. | You see one of the following error messages:
|
Close the error message and search for the record again. |
The portlets in the Start Center show an error or the KPI graphs are not available. | You see the following error message in the portlets: There was a problem loading the portlet. | After a moment, click on the Start Center link. |
You cannot open a new application from the Go To menu. | The screen is blank and no error message is shown. | Refresh the page in the web browser and select the application from the Go To menu again. |
Business Intelligence and Reporting Tools (BIRT) report viewer returns a report that contains no data or an error message is shown. | You see the following error message: Unauthorized to run the report, or Error 500: Failed to Process the request If database failover occurs when the BIRT report viewer is processing the report, you do not see all of your records in the report. |
Resubmit the report to resolve the error. |
An error occurs when report request pages are generated. | You see the following error message: Error BMXAA7118E: The request pages could not be generated. | Close the error message and resubmit the request. |
You cannot change the status of all of the records that you selected. | You see the following message, Please Wait, but when you are returned to the Change Status window, some record statuses are changed and some are unchanged. | Reselect all of the records and change the status. |
When you generate multiple work orders from preventive maintenance (PM) records, not all work order records are created. | The System Message window shows the work orders that were created and the work orders that were not created. | Regenerate the multiple work orders from the PM record. |
An error occurs when you try to log in to Maximo® Asset Management. | You see the following error message: Login Error: Username and password combination are not valid. Try again. | Close the error message and log in to Maximo Asset Management again. |
The following symptoms indicate that failover might have occurred during processing in Tivoli® Directory Server:
Symptom | Indicator | Solution |
---|---|---|
An error occurs when you try to log in to Maximo Asset Management. | You see the following error message: Login Error User name and password combination are not valid. Try again. | Close the error message and log in to Maximo Asset Management again. When the failover is complete, you can log in successfully. |
The following symptoms indicate that failover might have occurred during processing of the application server. Due to the internal design and implementation of Tivoli's process automation engine, the HTTP session state cannot be replicated across multiple servers. Because of this replication restriction, Tivoli's process automation engine does not support the session failover mechanism that is provided by the application server. As a result, users might lose some work when failure occurs.
Symptom | Indicator | Solution |
---|---|---|
The application server fails and you must log in again. | Your session is interrupted and you are either redirected to the login screen, or you are redirected to the Start Center. | When failure occurs and single sign-on is not in use, you must log in again. When single sign-on is in use, you can continue to work without logging in again. |
The following symptoms indicate that failover might have occurred during processing in IBM® HTTP Server. You can also opt to show a warning message when the server connection is lost.
Symptom | Indicator | Solution |
---|---|---|
An error occurs when you open the product login page or when you enter your login details and select Sign in. | The page is not displayed in the web browser. | Refresh the page in the web browser and sign in again. |
An error occurs when you select any of the user interface elements. | You see the following error message: System Message: There was a communication problem with the server which will result in the loss of some of your changes. You must reload the application and enter the information again. | Select Reload to refresh the user interface. |
An error occurs when you run a report in your product. | You see the following error message: Connection was reset. | Refresh the page in the web browser and resubmit the report. |
You cannot change the status of all of the records that you select. | You see the following message: Please Wait. In the background, you see the following error message: System Message: There was a communication problem with the server which will result in the loss of some of your changes. You must reload the application and enter the information again. |
Refresh the page in the web browser, reselect all of the records, and change the status. |
When you generate multiple work orders from preventive maintenance (PM) records, the process takes a long time to complete. | You see the message, Please Wait, which remains on the screen indefinitely. | Refresh the page in the web browser and regenerate the multiple work orders from the PM record. |