Oracle database naming convention

[SAPSupport]

We are in processing of having below setup for ECC, with two physical standby databases. This is part of migration effort.

Database Name (DB_NAME) A

Primary Database Instance (ORACLE_SID) B
Primary Database Unique Name (db_unique_name) B

First Standby Instance (ORACLE_SID) C
First Standby Database Unique Name (db_unique_name) C

Second Standby Instance (ORACLE_SID) D
Second Standby Database Unique Name (db_unique_name) D


A service will be created with name A, which can handle Data Guard connection as below:

A=
(DESCRIPTION =
(ADDRESS_LIST =
(FAILOVER = on)
(CONNECT_TIMEOUT = 5)
(TRANSPORT_CONNECT_TIMEOUT = 3)
(RETRY_COUNT = 3)
(LOAD_BALANCE = OFF)
)
(CONNECT_DATA =
(SERVICE_NAME = A)
)
)


Questions:
==================

1. Does SAP application support this naming convention?
2. Do we have any restrictions/limitations on naming? Our Basis/application team pointed few SAP notes about three character limitations on ORACLE_SID/DB_NAME/Instance Name?
3. Update us with SAP Notes on naming convention if anything as pointed in #2

------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.

[SAPSupport · Accepted solution]

SAP has no name limit, as long as SAP can connect correct database, based on tnsnames.ora.

SAP is using dbs_ora_tnsname environment variable value, to match tnsnames.ora to reach database.

For ORACLE_SID/DB_NAME/Instance Name, this is more oracle relevant.
According to SAP&Oracle dataguard guide: https://www.sap.com/documents/2016/12/a67bac51-9a7c-0010-82c7-eda71af511fa.html
They (ORACLE_SID/DB_NAME/Instance Name) should be the same, and DB_Unique_name is different for each primary and standby database.

For details, strongly suggest to check https://www.sap.com/documents/2016/12/a67bac51-9a7c-0010-82c7-eda71af511fa.html
section "Example application for an SQL*Net configuration"