When having an Oracle RAC environment setup in place and running the AR System installer/Configuration Checker as documented here: Remedy - Server - Is Oracle RAC configuration supported with Remedy 9.x For an Oracle RAC setup the Service Name needs to be provided, not the SID. When selecting the Service Name, as required, the following message is displayed when the configuration checker goes through: ................. TNS:Listener error code is SID specific not service specific ORA-12505 TNS:Listener does not know of SID given in the connect descriptor. ................. This forces us to use the SID instead. When using the SID the installer may then display the following check error: ........................... .......CONFIG,com.bmc.install.task.InstallationPropertiesHelper, LOG EVENT {Description=[SET PROPERTY VALIDATION_ERROR_RESULT],Detail=[INVALID_DATABASE_SID_LENGTH]} .......INFO,com.bmc.install.product.arsuitekit.platforms.arsystemservers.arserver.ARServerDatabaseInformationValidationTask, LOG EVENT {Description=[Validation error],Detail=[INVALID_DATABASE_SID_LENGTH]} ........................... |
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. The behavior within the installer using the SID instead of the Oracle Service Name required when using Oracle RAC has been reported as a defect: ................. SW00546819 - configchecker91_build002 uses SID instead of Service Name ................. Note: The defect is addressed in version 18.08 installer. Remedy - ARS 18.08 Corrected and Known issues/defects (AR System Suite) The second behavior observed when using SID instead is: ........................... LOG EVENT {Description=[Validation error],Detail=[INVALID_DATABASE_SID_LENGTH]} ........................... This is due to the fact that for an ORACLE RAC setup, the SID can be up to 12 characters long, but for a single Oracle database it is usually 8 characters long. By default, the installer, when selecting the SID, assumes the Oracle type being used is a single database and expects the SID not to be more than 8 characters long. In the Oracle documentation for Oracle RAC the following is mentioned: ……………… For an Oracle RAC database, each instance has a unique identifier, ORACLE_SID, which consists of the SID prefix and an instance number. The ORACLE_SID prefix can contain up to 12 characters. The ORACLE_SID for Oracle RAC database instances is generated differently, depending on how you choose to manage the database. If you select a policy-managed database, then Oracle generates the SID in the format name_#, where name is the first eight alphanumeric characters of DB_UNIQUE_NAME, and # is the instance number. If you select an administator-managed database, then Oracle Database Configuration Assistant generates the default SID for the instance names, using the format name#, where name is the first eight alphanumeric characters of DB_UNIQUE_NAME, and # is the instance number. However, during installation or database creation you can specify a nondefault value for the SID. The instance number is automatically added to the end of this string for each instance. ……………… And this is how SIDs are generated:
https://docs.oracle.com/en/database/oracle/oracle-database/12.2/rilin/selecting-a-database-name.html#GUID-3C954866-8375-4319-9184-CAA5F3B299D4 - SIDs for a single Database will by default be 8 characters long. - SIDs for Oracle RAC will have by default more than 8 characters long. However, the behavior observed when using the SID as mentioned above is an additional behavior due the fact that the Oracle Service Name cannot be used in the AR System installer as per the reported defect. If facing this issue the workaround is: 1- Configure an Oracle SID to have no more than 8 characters long. 2- Configure the Oracle listener.ora file to have this parameter present: USE_SID_AS_SERVICE_listener=on (information about this parameter can be checked here: https://docs.oracle.com/database/121/NETRF/listener.htm#NETRF2090) 3- Run the AR System installer, select and enter the Oracle SID. Note: The current defect SW00546819 is being under investigation and it will be addressed on a future release not yet specified. Related articles: Remedy - Server - Is Oracle RAC configuration supported with Remedy 9.x Remedy - Server - v9.x Error (ORA-12505) starting Remedy after configuring the TNSNAME.ORA of a copied Remedy Oracle database located on a different server |