I was also facing the same problem when i create the DB Link as
CREATE PUBLIC DATABASE LINK TestService USING 'TestService';
TNS COULD NOT RESOLVE SERVICE NAME.
This is basically the problem with the TNSNAME.ora file, the 'Using' clause not able to find the service name in the TNSNAMES.ora
This is how i solved: I just copy paste the TestService`s Description part as
CODE
alter system set global_names=false
/
CREATE PUBLIC DATABASE LINK TestService
using
'(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = TestHost)(PORT = 1521))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = TestService)
)
)
'
/
here my destination server host is TestHost & service name is TestService .
NOTE: If I had set the "GLOBAL_NAME" parameter to "TRUE", then the DBLink name need to be same as that of DBName .
Link Unit
Tuesday, October 23, 2007
Unrecongnised Section ConnectionStrings
When one of my client was deploying the web application he faced this issue. The following Steps helped me. Hope they help you too.
By default, when you create a website in IIS, the framework is 1.1
ASP.NET has introduced the new section in the web.config which will not be recognized in the .NET 1.1 framework.
1) Open IIS and browse to the website under computer_name > Web Sites > Default Web Site > website_name.
Where website_name is the actual name of the website, in this case the MySite website.
2) Right click website_name.
3) Click Properties.
4) Click the ASP.NET Tab
5) From the ASP.NET Version dropdown, select 2.0... version and Click OK.
Now, if you visit your application main page, it should work !
By default, when you create a website in IIS, the framework is 1.1
ASP.NET has introduced the new
1) Open IIS and browse to the website under computer_name > Web Sites > Default Web Site > website_name.
Where website_name is the actual name of the website, in this case the MySite website.
2) Right click website_name.
3) Click Properties.
4) Click the ASP.NET Tab
5) From the ASP.NET Version dropdown, select 2.0... version and Click OK.
Now, if you visit your application main page, it should work !
Subscribe to:
Posts (Atom)