configuring_oracle_net

each tnsnames.ora file should have a network service name and therefore access to the participation of other databases

Which is exactly the same thing that what I said then, "each database must have entered his $ORACLE_HOME/network/admin/tnsnames.ora tns for other databases"

Scroll through the thread and notice that you had posted tnsnames.ora entries that point to exactly the same combination of HOST + PORT + SERVICE_NAME. Thus, the two entries are linking to that same base.
Now, you have posted entries that show that the two databases on two servers different 192.168.1.10 and 192.168.1.11

Please do not use the terms "database of the customer" or "client site. A client is the software - SQL * Plus, T.O.A.D., PLSQL developer, Developer SQL, Oracle Enterprise Manager Console etc. - that you use to connect to the database and the issue of administrative orders using the language SQL, PLSQL and APIs procedures.

Oracle database console is a client to the databases.
hbfm and hbfp are identifiers for the two databases, who both have the same name of "orcl", on two different servers.
You will later have problems with the installation of multimaster, because the names of two databases must be different and the GLOBAL_NAMES parameter must be set to TRUE so that Oracle can identify them as two different databases. In the real world, two different databases have two different global names.

ORA-12170 research in documentation of Error Messages.
12170 error is:

ORA-12170: 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).

Your OEMConsole is not able to connect to this IP address + combination PortNumber. You have an active firewall? Is the VM database, a server that is not configured to allow connections from a client that has a different IP address?

As to your question about replication of clues... what EXACTLY are you trying to do? You started off saying that you are "replication via the materialized views. Where are the clues in the image? A materialized view is a local representation data retrieved through a query. (Or search the documentation for a formal definition, better it is of a MV). You generate clues on a MV if necessary.
The MV is different from the source table. Source one or more tables may have clues. The MV may have clues. There is no "replication" to do.

If you speak of MultiMaster replication, Tables and indexes are replicated as objects via some DDL statements.

I suggest that you understand:
1. that the servers, data bases are on.
2. If the SQLNet connectivity is enabled.
3. the question whether the two databases have different names.
4. the question of if you are replicating tables or create materialized views.

If you configure a production environment in the near future, do not use 10.2.0.1. Use 11.2.0.2 or 10.2.0.5
Consider learning Oracle Streams or Golden Gate as long as other options.

Getting back to the basics. I don't know what 'book' you follow. How about you read the documentation?

It is 10.2 on Advanced Replication documentation:
http://download.Oracle.com/docs/CD/B19306_01/server.102/b14226/TOC.htm
It's literature 11.2 on Advanced Replication:
http://download.Oracle.com/docs/CD/E11882_01/server.112/e10706/TOC.htm

(You can also find documentation on water courses in Oracle database documentation set from the 'List of books' link. Golden Gate is a separate product).

Hemant K Collette
http://hemantoracledba.blogspot.com

more

Tags: Database