AR System Server 9.x service is not starting while connecting to a Read-Only database instance. However in older versions, AR Servers are starting up and are accessible. Errors observed: ........................ Error initializing AR Server: ERROR (552): Message not in catalog; Message number = 552; Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.4.2.v20130514-5956486): org.eclipse.persistence.exceptions.DatabaseException Internal Exception: com.microsoft.sqlserver.jdbc.SQLServerException: Failed to update database "ARSystem" because the database is read-only. Error Code: 3906 Call: UPDATE servgrp_board SET intervalCount = ? WHERE (serverName = ?) bind => [2 parameters bound] Query: UpdateObjectQuery(com.bmc.arsys.server.persistence.ServerGroupBoardEntity@4ad69c2c); nested exception is javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.4.2.v20130514-5956486): org.eclipse.persistence.exceptions.DatabaseException Internal Exception: com.microsoft.sqlserver.jdbc.SQLServerException: Failed to update database "ARSystem" because the database is read-only. Error Code: 3906 Call: UPDATE servgrp_board SET intervalCount = ? WHERE (serverName = ?) bind => [2 parameters bound] Query: UpdateObjectQuery(com.bmc.arsys.server.persistence.ServerGroupBoardEntity@4ad69c2c) ........................ |
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers. Note: Read-Only Databases are supported from AR system 9.1.02 onwards. But be aware that if the AR Server does not have a valid server license, the AR System will not start up with a read-only database. You must apply a valid AR Server license in order to connect with a read-only database. (Which means that you will need to put the database in read/write mode temporarily while you apply the license). Please check the following article: Remedy - Server - Is Read-Only Database supported with ARS 9.1.02 or higher having Smart Reporting? For AR System 9.x where it will not start with Read-Only databases, even if they are not part of a Server Group. For previous 9 versions to SP2 AR Server did work with Read-Only databases. In version 9.x (prior to 9.1 SP2) the AR Server architecture has changed from being a C/C++ application to a Java application (serverj) and the new architecture and design prevents it from working with Read-Only databases. For versions pre-9.x of the AR Server, a Read-Only Database is not recommended because of the following restrictions: - It cannot be part of Server Group due to the required periodic updates to the Server Group tables used to keep the servers in sync - FTS should be disabled since it causes temporary tables to be created and populated - Vendor form searches will not work since they cause temporary tables to be created and populated - Any reporting which requires temp tables to be created need to be disabled - Archiving should disabled since it causes database updates - Escalations should be disabled since many of them attempt to create or modify data - Server Events and Server Statistics should be disabled It needs to understand the impact of using a Read-Only database and to be sure whether or is an actual must for a customer. Workaround: In version 9.x (prior to SP2) even with the above restrictions AR Server will still not start since it always needs to be able to update Server Group tables, even when not in a Server Group. This is a designed behavior. The workaround for this is to ensure that the following tables have write permissions: servgrp_resources servgrp_op_mstr servgrp_config servgrp_board servgrp_applic servgrp_userlic Also note that configuration changes made via the Centralized Configuration forms will not work since they need to store data. In order to make configuration changes, it is recommended to take the database out of Read Only mode. |