Introduction
To connect to Identity Management Oracle database (IDTP) after 0700 ET 10 December 2022, please follow the instructions below. At that time, per CHG0145570 Identity Management Oracle Database (IDTP) migration, IDTP will be migrated from Gold to Platinum Infrastructure to comply with Michigan Medicine standards for Platinum services.
Instructions
Use Case 1: Using the central TNSNAME file. If you connect to IDTP.WORLD via a core image computer's Oracle client and the central TNSNAMES file, you do not have to take any action; the central TNSNAME has already been updated, and your service will connect to IDTP.WORLD after the outage--a regression test after the outage is always recommended.
Use Case 2: Using a local TNSNAME file. If you connect to IDTP.WORLD via a local copy of the TNSNAMES names, you must update your local TNSNAMES with the following string during the outage, then perform a regression test after the outage.
IDTP.WORLD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = idtp_a.mcit.med.umich.edu)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = idtp_b.mcit.med.umich.edu)(PORT = 1521))
(ENABLE=BROKEN)
(LOAD_BALANCE=OFF)
(FAILOVER=ON)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = idtpfan.world)
(FAILOVER_MODE =
(TYPE = SELECT)
(METHOD = BASIC)
(RETRIES = 10)
(DELAY = 15))))
Use Case 3: Using a JDBC connection string in applications and/or drivers to connect to IDTP.WORLD. If you use a JDBC connection string in applications and/or drivers to connect to IDTP.WORLD, then you will have to update the connection string(s) as follows during the outage, then perform a regression test after the outage:
Existing string:
jdbc:oracle:thin:@idtp.mcit.med.umich.edu:1521:idtp
New String:
jdbc:oracle:thin:@(DESCRIPTION = (CONNECT_TIMEOUT=10)(RETRY_COUNT=10)(ADDRESS_LIST = (ADDRESS =(PROTOCOL = TCP) (HOST = idtp_a.mcit.med.umich.edu) (PORT = 1521)) (ADDRESS
=(PROTOCOL = TCP) (HOST =idtp_b.mcit.med.umich.edu) (PORT = 1521)))(CONNECT_DATA = (SERVICE_NAME = idtpfan.world)))