 I need to setup database replication with updatable materialized view [message #421089] |
Fri, 04 September 2009 03:43  |
abhi_shakya
Messages: 15
Registered: September 2009
Location: Nepal |
Junior Member |
|
|
|
i need to set up a central server with all the master tables and two other local database which will hold the updatable materialized view of the master table...the databases must be synchronized with central server..and user will work on the materialized view database...help me..with steps
|
|
|
|
|
|
| Re: I need to setup database replication with updatable materialized view [message #421222 is a reply to message #421115] |
Sun, 06 September 2009 04:41  |
abhi_shakya
Messages: 15
Registered: September 2009
Location: Nepal |
Junior Member |
|
|
I did what the documentation said...
but as creating
BEGIN
DBMS_REPCAT.CREATE_MVIEW_REPGROUP (
gname => 'test_repg',
master => 'NOC.NCCS.COM',
propagation_mode => 'ASYNCHRONOUS');
END;
/
ERROR at line 1:
ORA-04052: error occurred when looking up remote object
PROXY_MVIEWADMIN.SYS@NOC.NCCS.COM
ORA-00604: error occurred at recursive SQL level 2
ORA-12154: TNS:could not resolve the connect identifier specified
ORA-06512: at "SYS.DBMS_REPCAT_UTL", line 4262
ORA-06512: at "SYS.DBMS_REPCAT_SNA_UTL", line 1698
ORA-06512: at "SYS.DBMS_REPCAT_SNA", line 64
ORA-06512: at "SYS.DBMS_REPCAT", line 1262
ORA-06512: at line 2
what is this error...????I have already created necessary DB links.....what shud i do...
|
|
|
| Re: I need to setup database replication with updatable materialized view [message #421223 is a reply to message #421222] |
Sun, 06 September 2009 04:59 |
Michel Cadot
Messages: 29435
Registered: March 2007
Location: Nanterre, France, http://... |
Senior Member |
|
|
ORA-12154: TNS:could not resolve the connect identifier specified
*Cause: A connection to a database or other service was requested using
a connect identifier, and the connect identifier specified could not
be resolved into a connect descriptor using one of the naming methods
configured. For example, if the type of connect identifier used was a
net service name then the net service name could not be found in a
naming method repository, or the repository could not be
located or reached.
*Action:
- If you are using local naming (TNSNAMES.ORA file):
- Make sure that "TNSNAMES" is listed as one of the values of the
NAMES.DIRECTORY_PATH parameter in the Oracle Net profile
(SQLNET.ORA)
- Verify that a TNSNAMES.ORA file exists and is in the proper
directory and is accessible.
- Check that the net service name used as the connect identifier
exists in the TNSNAMES.ORA file.
- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA
file. Look for unmatched parentheses or stray characters. Errors
in a TNSNAMES.ORA file may make it unusable.
- If you are using directory naming:
- Verify that "LDAP" is listed as one of the values of the
NAMES.DIRETORY_PATH parameter in the Oracle Net profile
(SQLNET.ORA).
- Verify that the LDAP directory server is up and that it is
accessible.
- Verify that the net service name or database name used as the
connect identifier is configured in the directory.
- Verify that the default context being used is correct by
specifying a fully qualified net service name or a full LDAP DN
as the connect identifier
- If you are using easy connect naming:
- Verify that "EZCONNECT" is listed as one of the values of the
NAMES.DIRETORY_PATH parameter in the Oracle Net profile
(SQLNET.ORA).
- Make sure the host, port and service name specified
are correct.
- Try enclosing the connect identifier in quote marks.
See the Oracle Net Services Administrators Guide or the Oracle
operating system specific guide for more information on naming.
Regards
Michel
|
|
|
|
|
|
|
|
] 
Members
Search
Help
Register
Login
Home
