GSM-40148: Database task failed with ORA-12170

How to resolve GSM-40148: Database task failed with ORA-12170 TNS connect timeout occurred when adding a broker in GSM.

The error message "GSM-40148: Database task failed with ORA-12170" with ORA-12170 TNS connect timeout typically occurs due to a configuration issue with the GDS/GSM instance (Global Service Manager)).

Ensure that the GSM host is available from the database host. To do this, run the following on each new database from the database host:
```
SQL> show parameter "_gsm"
```
For each of the GSM TNS addrssses in that list, run:
```
$ tnsping tns_address
```
where tns_address is the TNS connect address.

If any address does not respond, then peform the following checks:
- Ensure that the GSM hostname is known to the database host (ping the host)
- Ensure that the firewall from the database to the GSM host has been opened for the GSM listener port (usually that port is 1572, but check the port number in the TNS address).
If either of these checks turn up issues, then address that problem with your networking team.
Check that all of the database hosts are available from the GSM host. To do this, select the connect string for each standby database. On the primary database, enter the following:
```
SQL> select connect_identifier from v$dg_broker_config;
```
Next, on each GSM host, run the following checks:
- Run tnsping on the primary database TNS that you used to add the broker.
- Run tnsping on each of the addresses from v$dg_broker_config.

Note:

Be aware that you may have used a TNS alias in any of these addresses. If you used a TNS alias, then you must use that same TNS alias in the TNS ping.

Be aware that all TNS aliases must be in the tnsnames.ora file on all of the GSM hosts.

Parent topic: Troubleshooting GSM Issues