dbacockpit error

[Former Member]

Hi Experts,

with the help of note 1261329 - DBA Cockpit: Oracle as a remote database, I have configured dbacockpit for one of my managed system.

I have added the entry in tnsnames.ora file as per note 1261329. After that i have created a database connection. while testing this database connection, I am getting following error

-- ERROR Database connection %_ED5_CDEVECC01: SQL error 12170 ORA-12170: TNS:Connect timeout occurred.

I have checked, database, listerner is up in settelite system.

Kinldy help in resolving this issue.

Regards,

Akhilesh.

[Paul_Babier · Accepted solution]

Hello Ahilesh,

You can check if the listener is running i.e "lsnrctl status"

Also check the listener.log for any errors.

If listener is running, check if the database can be/is started.

Check in sqlnet.ora if SQLNET.INBOUND_CONNECT_TIMEOUT parameter is set.

Depending on what has been done, a server restart might be necessary for some setting to take effect?

Regards,

Paul

[Former Member · Accepted solution]

Hi Paul,

Thanks for your respone. I have checked "listener" is running fine. I also checked in sqlnet.ora file, in that SQLNET.INBOUND_CONNECT_TIMEOUT parameter is not set.

Can you please tell me why is the need to set this parameter and with what value we should set it ?

Regards,

Akhilesh.

[Paul_Babier · Accepted solution]

Hello Akhilesh,

The following is the error description of the ora-12170.

12170, 00000, "TNS:Connect timeout occurred"

// *Cause: The server shut down because connection establishment or

communication with a client failed to complete within the

allotted time interval. This may be a result of network or

system delays; or this may indicate that a malicious client

is trying to cause a Denial of Service attack on the server.

// *Action: If the error occurred because of a slow network or system,

reconfigure one or all of the parameters

SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT,

SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values.

If a malicious client is suspected, use the address in

sqlnet.log to identify the source and restrict access. Note

that logged addresses may not be reliable as they can be

forged (e.g. in TCP/IP).

Unfortunately, I am not a DBA, so I am not sure what values are defaulted when not set, so I am not sure what values would be suitable. I know a corrective action for this error can be to increase the values.

Regards,

Paul

[Former Member]

issue was with ports. Now working fine.

[nirmal_konchada]

Hi,

Also make sure that the hostfiles entries are present on both, the satellite and the central system.

Regards,

Nirmal.K