I have 2 Databases on my Network.
One Database have More then 1 SCHEMAs.
and the 2nd one have Only One SCHEMA.
For Example.
Database 1 have 2 SCHEMA
1. PMS
2. EMS
Database 2 have 1 SCHEMA
1. PMS
I want to Access the Data from the 2nd Database While Residing in 1st Database.
I Create a Database Link in DB1 in SCHEMA <b>PMS</b>. (PMS SCHEMA is Availabe in DB2)
I can Access all the Data from DB2 While Login in DB1 SCHEMA PMS.
But the Problem is.
When i Create DBLINK in DB1 in SCHEMA <b>EMS</b> with PMS in DB2(EMS in Not available in DB2)
I'm Unable to Access the Data using that link.
When i Try to Access useing this Query
Select * from Table@dbLink;
Gives me UserName/Password Error.
Please help me what Possible Reasons is Creating the Problem.
Or Give me the Solution for Accessing the Data.
Thanks
DBLINIK Problem
Just follow the instructions on the following link and if still any issue then let us know,
http://asktom.oracle.com/pls/ask/f?p=49 ... 6820211101,
http://asktom.oracle.com/pls/ask/f?p=49 ... 6820211101,
Database Link is Created Successfully.
Working on DBSERVER.
But when I Apply any SQL Statment on Client Side to Access the Database Using DBLINK. Following things occur.
kflmis@ksm> select * from dual@ksm1.com;
D
-
X
kflmis@ksm> Desc m_main@ksm1.com;
Name Null? Type
------------------------------- -------- ----
MAIN_ID NOT NULL NUMBER(2)
TITLE NOT NULL VARCHAR2(35)
OPN_DATE NOT NULL DATE
kflmis@ksm> Select * from m_main@ksm1.com;
ERROR:
ORA-03106: fatal two-task communication protocol error
no rows selected
Working on DBSERVER.
But when I Apply any SQL Statment on Client Side to Access the Database Using DBLINK. Following things occur.
kflmis@ksm> select * from dual@ksm1.com;
D
-
X
kflmis@ksm> Desc m_main@ksm1.com;
Name Null? Type
------------------------------- -------- ----
MAIN_ID NOT NULL NUMBER(2)
TITLE NOT NULL VARCHAR2(35)
OPN_DATE NOT NULL DATE
kflmis@ksm> Select * from m_main@ksm1.com;
ERROR:
ORA-03106: fatal two-task communication protocol error
no rows selected
Hope the following metalin note will be useful.
Subject: ORA-03106 WHEN CONNECTING TO UTF8 DATABASE.
Doc ID: Note:1020408.102 Type: PROBLEM
Last Revision Date: 26-MAR-2003 Status: PUBLISHED
Problem Description
-------------------
You are trying to establish connection to Oracle 8 database.
You are either trying to connect from a client, or another database, using
either SQL*PLus or any other Oracle tool.
You run the following query to find out about database's character set:
SVRMGR> select * from nls_database_parameters;
Parameter NLS_CHARACTERSET appeared as UTF8.
No matter what you do, connection cannot be established, you get errors,
mainly ORA-03106.
ERROR: ORA-03106: fatal two-task communication protocol error.
Depending on the configuration you may get other errors accompanying this one.
You have set all NLS parameters (NLS_LANG, ORA_NLS33) correctly but still
cannot connect.
Solution Description
--------------------
Use SQL*NET version 2.3..4 or higher.
Example of unsuccessful connection with SQL*Net version 2.3.3:
==============================================================
[tcsol2]/u02/app/oracle/product/7.3.3>svrmgrl
Oracle Server Manager Release 2.3.3.0.0 - Production
Copyright (c) Oracle Corporation 1994, 1995. All rights reserved.
Oracle7 Server Release 7.3.3.5.0 - Production Release
With the distributed, replication and parallel query options
PL/SQL Release 2.3.3.5.0 - Production
SVRMGR> connect internal
Connected.
SVRMGR> select * from v$version;
BANNER
----------------------------------------------------------------
Oracle7 Server Release 7.3.3.5.0 - Production Release
PL/SQL Release 2.3.3.5.0 - Production
CORE Version 3.5.3.1.0 - Production
TNS for Solaris: Version 2.3.3.0.0 - Production
NLSRTL Version 3.2.3.0.0 - Production
5 rows selected.
[tcsol2]/u02/app/oracle/product/7.3.3> sqlplus system/manager@tiger5_V815.world
SQL*Plus: Release 3.3.3.0.0 - Production on Fri Nov 19 10:34:23 1999
Copyright (c) Oracle Corporation 1979, 1996. All rights reserved.
ERROR: ORA-03106: fatal two-task communication protocol error
Example of successful connection with SQL*Net version 2.3.4:
============================================================
[tcsol2]/u02/app/oracle/product/7.3.4> sqlplus system/manager@tiger5_V815.world
SQL*Plus: Release 3.3.4.0.1 - Production on Fri Nov 19 11:03:26 1999
Copyright (c) Oracle Corporation 1979, 1996. All rights reserved.
Connected to:
Oracle8i Enterprise Edition Release 8.1.5.0.0 - Production
With the Partitioning and Java options
PL/SQL Release 8.1.5.0.0 - Production
SQL> select * from nls_database_parameters
2 where PARAMETER = 'NLS_CHARACTERSET';
PARAMETER VALUE
------------------------ -------------------------
NLS_CHARACTERSET UTF8
SQL> select * from v$version;
BANNER
----------------------------------------------------------------
Oracle7 Server Release 7.3.4.0.1 - Production
PL/SQL Release 2.3.4.0.0 - Production
CORE Version 3.5.4.0.0 - Production
TNS for Solaris: Version 2.3.4.0.0 - Production
NLSRTL Version 3.2.4.0.0 - Production
Explanation
-----------
You are NOT using SQL*Net version 2.3.4 and higher. SQL*Net version 2.3.4
and higher is required to be able to connect to a Unicode UTF8 database.
Search Words
------------
UTF-8, Oracle8, Oracle8i
Subject: ORA-03106 WHEN CONNECTING TO UTF8 DATABASE.
Doc ID: Note:1020408.102 Type: PROBLEM
Last Revision Date: 26-MAR-2003 Status: PUBLISHED
Problem Description
-------------------
You are trying to establish connection to Oracle 8 database.
You are either trying to connect from a client, or another database, using
either SQL*PLus or any other Oracle tool.
You run the following query to find out about database's character set:
SVRMGR> select * from nls_database_parameters;
Parameter NLS_CHARACTERSET appeared as UTF8.
No matter what you do, connection cannot be established, you get errors,
mainly ORA-03106.
ERROR: ORA-03106: fatal two-task communication protocol error.
Depending on the configuration you may get other errors accompanying this one.
You have set all NLS parameters (NLS_LANG, ORA_NLS33) correctly but still
cannot connect.
Solution Description
--------------------
Use SQL*NET version 2.3..4 or higher.
Example of unsuccessful connection with SQL*Net version 2.3.3:
==============================================================
[tcsol2]/u02/app/oracle/product/7.3.3>svrmgrl
Oracle Server Manager Release 2.3.3.0.0 - Production
Copyright (c) Oracle Corporation 1994, 1995. All rights reserved.
Oracle7 Server Release 7.3.3.5.0 - Production Release
With the distributed, replication and parallel query options
PL/SQL Release 2.3.3.5.0 - Production
SVRMGR> connect internal
Connected.
SVRMGR> select * from v$version;
BANNER
----------------------------------------------------------------
Oracle7 Server Release 7.3.3.5.0 - Production Release
PL/SQL Release 2.3.3.5.0 - Production
CORE Version 3.5.3.1.0 - Production
TNS for Solaris: Version 2.3.3.0.0 - Production
NLSRTL Version 3.2.3.0.0 - Production
5 rows selected.
[tcsol2]/u02/app/oracle/product/7.3.3> sqlplus system/manager@tiger5_V815.world
SQL*Plus: Release 3.3.3.0.0 - Production on Fri Nov 19 10:34:23 1999
Copyright (c) Oracle Corporation 1979, 1996. All rights reserved.
ERROR: ORA-03106: fatal two-task communication protocol error
Example of successful connection with SQL*Net version 2.3.4:
============================================================
[tcsol2]/u02/app/oracle/product/7.3.4> sqlplus system/manager@tiger5_V815.world
SQL*Plus: Release 3.3.4.0.1 - Production on Fri Nov 19 11:03:26 1999
Copyright (c) Oracle Corporation 1979, 1996. All rights reserved.
Connected to:
Oracle8i Enterprise Edition Release 8.1.5.0.0 - Production
With the Partitioning and Java options
PL/SQL Release 8.1.5.0.0 - Production
SQL> select * from nls_database_parameters
2 where PARAMETER = 'NLS_CHARACTERSET';
PARAMETER VALUE
------------------------ -------------------------
NLS_CHARACTERSET UTF8
SQL> select * from v$version;
BANNER
----------------------------------------------------------------
Oracle7 Server Release 7.3.4.0.1 - Production
PL/SQL Release 2.3.4.0.0 - Production
CORE Version 3.5.4.0.0 - Production
TNS for Solaris: Version 2.3.4.0.0 - Production
NLSRTL Version 3.2.4.0.0 - Production
Explanation
-----------
You are NOT using SQL*Net version 2.3.4 and higher. SQL*Net version 2.3.4
and higher is required to be able to connect to a Unicode UTF8 database.
Search Words
------------
UTF-8, Oracle8, Oracle8i
I'm Using 9i Database (both).
At Client Side Using Developer 6i and its Servises.
When i Try to Query using Oracle 9i SQL PLUS. It is Return the Resulset.
When i Try to Query using Develper 6i SQL PLUS. It is Return the the error which i stated in last last reply.
then what will be its Solution. as i want to use this Link In My Forms (developer 6i).
Forms are using the SQL Net which I think is OLD (as in Metalink Explain it).
Please Give me any Solution.
At Client Side Using Developer 6i and its Servises.
When i Try to Query using Oracle 9i SQL PLUS. It is Return the Resulset.
When i Try to Query using Develper 6i SQL PLUS. It is Return the the error which i stated in last last reply.
then what will be its Solution. as i want to use this Link In My Forms (developer 6i).
Forms are using the SQL Net which I think is OLD (as in Metalink Explain it).
Please Give me any Solution.
I dont know about the release number of Developer.
I found this Information in ( About Form Builer....)
Forms [32 Bit] Version 6.0.8.8.0 (Production)
Oracle Toolkit Version 6.0.5.34.1 (Production)
PL/SQL Version 8.0.6.0.0 (Production)
Oracle Procedure Builder V6.0.7.2.1 Build #228 - Production
PL/SQL Editor (c) WinMain Software (www.winmain.com), v1.0 (Production)
Oracle Query Builder 6.0.7.0.0 - Production
Oracle Virtual Graphics System Version 6.0.5.34.0 (Production)
Oracle Tools GUI Utilities Version 6.0.5.32.0 (Production)
Oracle Multimedia Version 6.0.5.34.0 (Production)
Oracle Tools Integration Version 6.0.5.32.0 (Production)
Oracle Tools Common Area Version 6.0.5.32.1
Oracle CORE Version 4.0.6.0.0 - Production
I found this Information in ( About Form Builer....)
Forms [32 Bit] Version 6.0.8.8.0 (Production)
Oracle Toolkit Version 6.0.5.34.1 (Production)
PL/SQL Version 8.0.6.0.0 (Production)
Oracle Procedure Builder V6.0.7.2.1 Build #228 - Production
PL/SQL Editor (c) WinMain Software (www.winmain.com), v1.0 (Production)
Oracle Query Builder 6.0.7.0.0 - Production
Oracle Virtual Graphics System Version 6.0.5.34.0 (Production)
Oracle Tools GUI Utilities Version 6.0.5.32.0 (Production)
Oracle Multimedia Version 6.0.5.34.0 (Production)
Oracle Tools Integration Version 6.0.5.32.0 (Production)
Oracle Tools Common Area Version 6.0.5.32.1
Oracle CORE Version 4.0.6.0.0 - Production
Pl check,
Subject: Using SQL RETURNING Clause in Forms 6i Causes FRM-40735, ORA-00439
Doc ID: Note:187226.1 Type: PROBLEM
Last Revision Date: 04-APR-2003 Status: PUBLISHED
* fact: Oracle Forms Developer 6.0.8
* fact: SQL Expression
* fact: PLSQL - PL/SQL
* symptom: Error During Runtime
* symptom: Using RETURNING clause causes error
* symptom: ORA-03106: fatal two-task communication protocol error
* symptom: ORA-00439: feature not enabled: %s
* symptom: RETURNING clause from this client type
* symptom: FRM-40735: %s trigger raised unhandled exception %s
* cause: The underlying cause is a PL/SQL 8.0.6 bug. The problem does not reproduce with later versions of PL/SQL (This is a problem for Forms 6i as it has client side PL/SQL engine version 8.0. 6.x) Bug 1816779 Abstract: ORA-439 WHEN TRYING TO RUN A PROCEDURE WITH RETURNING CLAUSE which refers back to base bug: Bug 1119964 Abstract: ORA-3108 ERROR WHEN (INSERT INTO...RETURNING INTO...) STATMENT IS USED which in turn refers to a base PL/SQL bug: Bug 1210204 Abstract: ORA-3108 ERROR WHEN (INSERT INTO...RETURNING INTO...) STATMENT IS USED Note, Bug 1210204 is internal only and NOT published on Metalink.
fix:
The base PL/SQL Bug is still under investigation - there is currently no fix
available or patch available.
Workarounds :
1. Do not use SQL RETURNING Clause
2. Move offending SQL into a stored database procedure / function and call this
from Forms. This will mean that the SQL is executed by the server side PL/SQL
engine. Thus, if the RDBMS is version 8.1.7 or higher, the problem should not
reproduce.
Subject: Using SQL RETURNING Clause in Forms 6i Causes FRM-40735, ORA-00439
Doc ID: Note:187226.1 Type: PROBLEM
Last Revision Date: 04-APR-2003 Status: PUBLISHED
* fact: Oracle Forms Developer 6.0.8
* fact: SQL Expression
* fact: PLSQL - PL/SQL
* symptom: Error During Runtime
* symptom: Using RETURNING clause causes error
* symptom: ORA-03106: fatal two-task communication protocol error
* symptom: ORA-00439: feature not enabled: %s
* symptom: RETURNING clause from this client type
* symptom: FRM-40735: %s trigger raised unhandled exception %s
* cause: The underlying cause is a PL/SQL 8.0.6 bug. The problem does not reproduce with later versions of PL/SQL (This is a problem for Forms 6i as it has client side PL/SQL engine version 8.0. 6.x) Bug 1816779 Abstract: ORA-439 WHEN TRYING TO RUN A PROCEDURE WITH RETURNING CLAUSE which refers back to base bug: Bug 1119964 Abstract: ORA-3108 ERROR WHEN (INSERT INTO...RETURNING INTO...) STATMENT IS USED which in turn refers to a base PL/SQL bug: Bug 1210204 Abstract: ORA-3108 ERROR WHEN (INSERT INTO...RETURNING INTO...) STATMENT IS USED Note, Bug 1210204 is internal only and NOT published on Metalink.
fix:
The base PL/SQL Bug is still under investigation - there is currently no fix
available or patch available.
Workarounds :
1. Do not use SQL RETURNING Clause
2. Move offending SQL into a stored database procedure / function and call this
from Forms. This will mean that the SQL is executed by the server side PL/SQL
engine. Thus, if the RDBMS is version 8.1.7 or higher, the problem should not
reproduce.
<blockquote id="quote"><font size="1" id="quote"><b id="quote">quote:</b id="quote"></font id="quote"><table border="0" id="quote"><tr id="quote"><td class="quote" id="quote"><font size="1" id="quote">
Workarounds :
1. Do not use SQL RETURNING Clause
<b>2. Move offending SQL into a stored database procedure / function and call this
from Forms. This will mean that the SQL is executed by the server side PL/SQL
engine. Thus, if the RDBMS is version 8.1.7 or higher, the problem should not
reproduce.</b></td id="quote"></tr id="quote"></table id="quote"></blockquote id="quote"><font size="2" id="quote"></font id="quote">
Thankx Dear Admin
But how i do this via Stored Database Procedure?
Workarounds :
1. Do not use SQL RETURNING Clause
<b>2. Move offending SQL into a stored database procedure / function and call this
from Forms. This will mean that the SQL is executed by the server side PL/SQL
engine. Thus, if the RDBMS is version 8.1.7 or higher, the problem should not
reproduce.</b></td id="quote"></tr id="quote"></table id="quote"></blockquote id="quote"><font size="2" id="quote"></font id="quote">
Thankx Dear Admin
But how i do this via Stored Database Procedure?
Who is online
Users browsing this forum: No registered users and 0 guests