Naming Method Use

Hi,
TNSNAMES.ORA
MASTER=(DESCRIPTION=
(ADDRESS=
(PROTOCOL=tcp)
(HOST=TELSTAR)
(PORT=1521))
(CONNECT_DATA=
(SERVICE_NAME=LOC)))
SQLNET.ORA
NAMES.DEFAULT_DOMAIN=US.TELSTAR.COM
NAMES.DIRECTORY_PATH=(LDAP, TNSNAMES, HOSTNAME)
In here why it uses LDAP?.... Whts the purpose of using LDAP here!
What is the naming method using here....
ThankX
Edited by: Ushman on Sep 15, 2008 4:06 PM

names.directory_path:- Specifies the order of naming methods that are used when a client tries to connect to a database.
If you are not using LDAP then simply delete it. LDAP here, refers to Oracle internet Directory a component or Oracle Application Server.
Regards
Christopher Soza
Orix Consultancy Services Ltd

Similar Messages

Connecting oracle using Directory Naming Method

Hi,
I am just checking the possibilities of implementing Directory Naming Method in our organization. currently we are using Local Naming method (using tnsnames.ora).
I did google to find the pre-requsites to use directory naming method and I couldnt' find the right document.
could somebody who has implemented and using directory naming method (via centralized LDAP-compliant directory server) could help me in finding the pre-requistes and what kind of infrastucture we should be having to implement the same in our organization.
Thanks in advace for your help.
Krishna.

I'm trying to figure these things out myself.
I have some questions for you:
1. What operating systems does your server and workstations use?
If they're all Windows and you're on a Windows Domain, consider Active Directory as the directory service.
2. If it is all unix-like operating systems, consider using Oracle Internet Directory as the directory service.
3. Mixed Windows and Unix-like operating systems - use whatever you are currently using as the directory service.
At http://tahiti.oracle.com/ you may want to read some of the following books from oracle:
- Platform Guide for Microsoft Windows (if you're using Windows)
- Advanced Security Administrator's Guide
- Enterprise User Security Administrator's Guide
- Net Services Administrator's Guide
- Net Services Reference
- Oracle Internet Directory Administrator's Guide
- Oracle Database 2 Day DBA
Options to consider: Kerberos or Active Directory
If using Windows and you already using Active Directory, consider this:
Microsoft Environment: Configuring Oracle Advanced Security Option (ASO) Kerberos Adapter with Windows 2003 Active Directory
See Metalink doc-id: 368321.1

Oci_connect using easy connect naming method needs listener??

Hi,
I was thinking that using the easy connect naming method in oci_connect does not require a running local tnslsnr!? Am I wrong?
I tried:
$db = '(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = my-ora-host.example.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = my-service.example.com)))';
// $db = '//my-ora-host.example.com:1521/my-service.example.com';
$ora_conn = oci_connect('test', 'test', $db);
Using both versions of the 'db' I receive the error:
mod_fcgid: stderr: PHP Warning: oci_connect(): ORA-12541: TNS:no listener in ....
I am using a self compiled PHP 5.3.8 using Oracles instantclient 11.2.0.3.0 (on Linux, 32bit).
There are NO special environment variables ( like ORACLE_HOME or TNS_ADMIN), because I was thinking that I don't need them...
Am I wrong? Is a running tnslsnr always required? Or am I doing wrong in specifying the connection string?
Any help is appreciated!
chuan

The connection strings are fine. They only control how PHP attempts to connect to the DB. The DB will need a listener started so that those incoming requests are handled. Use: 'lsnrctl start' on the DB machine.

Multiple Data Source (for FAILOVER) in Easy Connect Naming method

Hi All,
I was wondering if there is a way to specify multiple addresses as part of data source property in the connection string when trying to connect to Oracle with Easy Connect Naming method? this is basically for failover scenario.
I know its straight forward, if i use Connect Descriptor. But not sure how to do it with EZConnect
For ex. this is what I want to achieve with EZConnect
sales.us.example.com=
(DESCRIPTION=
(ADDRESS_LIST=
(LOAD_BALANCE=off)
(FAILOVER=ON)
*(ADDRESS=(PROTOCOL=tcp)(HOST=sales1-server)(PORT=1521))*
*(ADDRESS=(PROTOCOL=tcp)(HOST=sales2-server)(PORT=1521)))*
(CONNECT_DATA=(SERVICE_NAME=sales.us.example.com)))
I appreciate your suggestions...
Thanks

You might get better answers in one of the DB forums from a generic fail-over perspective as EZconnect isn't specific to ODP.NET.
I don't know if there's a way to do it or not with EZConnect version of the connect string, but you can certainly provide the fully qualified connect string without using tnsnames.ora..
constring = "data source=(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=off)(FAILOVER=ON)(ADDRESS=(PROTOCOL=tcp)(HOST=sales1-server)(PORT=1521))(ADDRESS=(PROTOCOL=tcp)(HOST=sales2-server)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=sales.us.example.com))); user id=scott;password=tiger"
Hope it helps,
Gres

NET8의 LOCAL NAMING METHODS 이용관련 CHECK POINTS & TROUBLESHOOTING

제품 : SQL*NET
작성날짜 : 2000-12-15
===================================================================
Net8의 Local Naming Methods 이용관련 Check Points & Troubleshooting
====================================================================
Net8 관련 내용중 Local Naming Methods(sqlnet.ora와 tnsnames.ora
를 이용해서 DB에 Connect하는 방법)에 관한 일반적인 Check Points 및
Troubleshooing 사항을 정리해보도록 하겠다.
[Client Connection : Local Naming Methods]
1. Local Naming method resolves service names by using the local configuration files tnsnames.ora and sqlnet.ora.
2. One of the benefits of the Local Naming method is that it provides a simple method for resolving service name addresses. It is easy to configure local naming by using a GUI called the Net8 Assistant. When you configure a client machine for local naming by using the Net8 Assistant, a tnsnames.ora file is generated. To configure all the other client machines on the network that need to use the same database services, you can simply copy this file to the client machines.
3. Another benefit of using the local-naming method is that it resolves service name across networks running different protocols.
[Local Naming : Configuration]
1. The local-naming method resolves service names by using the information configured and stored on each individual client. Local naming is most appropriate for simple distributed networks with a small number of services that change infrequently.
2. Local naming requires the configuration of two local files, tnsnames.ora and sqlnet.ora. The tnsnames.ora file contains the address needed to direct a connection request to the specified listener on the specified node by using the specified database. The sqlnet.ora file stores information about the selected naming method.
3. Local naming is easy to configure by using the Net8 Assistant. The Net8 Assistant is implemented in Java and is packed with the Java Runtime Environment. You can run the Net8 Assistant on any platform on which Net8 is installed.
4. When you configure an Oracle8 server to use the local-naming method for service names resolution, the client-side configuration files tnsnames.ora and sqlnet.ora are automatically generated. After the configuration is complete, you copy these two files from the server to the client machines.
[Client Files : Parameters]
1. The tnsnames.ora and sqlnet.ora files are generated at the default location ORACLE_HOME\net80\admin.
2. The first parameter in the tnsnames.ora file specifies the service name and the domain name for the client.
3. The tnsnames.ora file contains a parameter called DESCRIPTION. This parameter contains information about the connect descriptor for the client.
4. The ADDRESS parameter in the tnsnames.ora file specifies the network address of the host to which the client is connected. If multiple addresses are specified, use the keyword ADDRESS_LIST before the ADDRESS parameter.
5. Another parameter in the tnsnames.ora file is the CONNECT_DATA parameter. This parameter specifies the SID of the database to which the client is connected.
6. The DEFAULT_DOMAIN parameter of the sqlnet.ora file specifies the domain from which the client most often requests names. When this parameter is set, the domain name is automatically appended to the service name in a connect string.
7. The DIRECTORY_PATH parameter is another key parameter of the sqlnet.ora file. This parameter specifies the names resolution method to be used for the client-server connection.
8. The sqlnet.ora file also contains a parameter called DEFAULT_ZONE.
This parameter specifies the region to which the client belongs.
[Troubleshooting the Client Side]
These are common client-side problems and the error messages associated with
each error code.
ORA-12154: "TNS: could not resolve service name"
ORA-12198: "TNS: could not find path to destination"
ORA-12203: "TNS: unable to connect to destination"
ORA-12533: "TNS: illegal ADDRESS parameters"
1. The ORA-12154 error occurs when Net8 cannot locate the connect descriptor specified in the tnsnames.ora configuration file. To solve this problem, first verify that a tnsnames.ora file exists and is accessible. Next, verify that multiple copies of the tnsnames.ora file are not present. After checking the existence of the tnsnames.ora file, verify that the service name specified in the connect string is mapped to a connect descriptor in the tnsnames.ora file. Verify also that the file does not contain any syntaz errors. The ORA-12154 error also occur if there is more than one copy of the sqlnet.ora file. Verify that duplicate copies of the sqlnet.ora file are not present.
2. The ORA-12198 and ORA-12203 errors occur when the client is unable to find the required database. To solve this problem, first verify that you have correctly entered the service name that you want to use. Next verify that the service name parameters in the ADDRESS section of the connect descriptor in the tnsnames.ora file are correctly defined. Then, verify that the tnsnames.ora file is stored in the correct directory. The ORA-12198 and ORA-12203 errors can also occur if the listener on the remote node is not running. Verify that the listener on the remote node has started and is running. If the listener is not running, start the listener by using the Listener Control(LSNRCTL) utility.
3. The ORA-12533 error occurs if the protocol-specific parameters in the ADDRESS section of the designated connect descriptor in the tnsnames.ora file are incorrect. To solve this problem, use the correct protocol-specific parameters in the ADDRESS section of the connect descriptor.
4. The ORA-12545 error occurs when the listener on the remote node cannot be contacted. This may happen if the values of the ADDRESS parameter in the tnsnames.ora file and the listener.ora file are incorrect. In this case replace the incorrect values with the correct values in both the files. The ORA-12545 error can also occur if the listener on the remote node is not
started. To verify whether or not the listener is started, determine its status with the STATUS command of the LSNRCTL utility. If necessary, start the listener on the remote node with the START command.

제품 : SQL*NET
작성날짜 : 2000-12-15
===================================================================
Net8의 Local Naming Methods 이용관련 Check Points & Troubleshooting
====================================================================
Net8 관련 내용중 Local Naming Methods(sqlnet.ora와 tnsnames.ora
를 이용해서 DB에 Connect하는 방법)에 관한 일반적인 Check Points 및
Troubleshooing 사항을 정리해보도록 하겠다.
[Client Connection : Local Naming Methods]
1. Local Naming method resolves service names by using the local configuration files tnsnames.ora and sqlnet.ora.
2. One of the benefits of the Local Naming method is that it provides a simple method for resolving service name addresses. It is easy to configure local naming by using a GUI called the Net8 Assistant. When you configure a client machine for local naming by using the Net8 Assistant, a tnsnames.ora file is generated. To configure all the other client machines on the network that need to use the same database services, you can simply copy this file to the client machines.
3. Another benefit of using the local-naming method is that it resolves service name across networks running different protocols.
[Local Naming : Configuration]
1. The local-naming method resolves service names by using the information configured and stored on each individual client. Local naming is most appropriate for simple distributed networks with a small number of services that change infrequently.
2. Local naming requires the configuration of two local files, tnsnames.ora and sqlnet.ora. The tnsnames.ora file contains the address needed to direct a connection request to the specified listener on the specified node by using the specified database. The sqlnet.ora file stores information about the selected naming method.
3. Local naming is easy to configure by using the Net8 Assistant. The Net8 Assistant is implemented in Java and is packed with the Java Runtime Environment. You can run the Net8 Assistant on any platform on which Net8 is installed.
4. When you configure an Oracle8 server to use the local-naming method for service names resolution, the client-side configuration files tnsnames.ora and sqlnet.ora are automatically generated. After the configuration is complete, you copy these two files from the server to the client machines.
[Client Files : Parameters]
1. The tnsnames.ora and sqlnet.ora files are generated at the default location ORACLE_HOME\net80\admin.
2. The first parameter in the tnsnames.ora file specifies the service name and the domain name for the client.
3. The tnsnames.ora file contains a parameter called DESCRIPTION. This parameter contains information about the connect descriptor for the client.
4. The ADDRESS parameter in the tnsnames.ora file specifies the network address of the host to which the client is connected. If multiple addresses are specified, use the keyword ADDRESS_LIST before the ADDRESS parameter.
5. Another parameter in the tnsnames.ora file is the CONNECT_DATA parameter. This parameter specifies the SID of the database to which the client is connected.
6. The DEFAULT_DOMAIN parameter of the sqlnet.ora file specifies the domain from which the client most often requests names. When this parameter is set, the domain name is automatically appended to the service name in a connect string.
7. The DIRECTORY_PATH parameter is another key parameter of the sqlnet.ora file. This parameter specifies the names resolution method to be used for the client-server connection.
8. The sqlnet.ora file also contains a parameter called DEFAULT_ZONE.
This parameter specifies the region to which the client belongs.
[Troubleshooting the Client Side]
These are common client-side problems and the error messages associated with
each error code.
ORA-12154: "TNS: could not resolve service name"
ORA-12198: "TNS: could not find path to destination"
ORA-12203: "TNS: unable to connect to destination"
ORA-12533: "TNS: illegal ADDRESS parameters"
1. The ORA-12154 error occurs when Net8 cannot locate the connect descriptor specified in the tnsnames.ora configuration file. To solve this problem, first verify that a tnsnames.ora file exists and is accessible. Next, verify that multiple copies of the tnsnames.ora file are not present. After checking the existence of the tnsnames.ora file, verify that the service name specified in the connect string is mapped to a connect descriptor in the tnsnames.ora file. Verify also that the file does not contain any syntaz errors. The ORA-12154 error also occur if there is more than one copy of the sqlnet.ora file. Verify that duplicate copies of the sqlnet.ora file are not present.
2. The ORA-12198 and ORA-12203 errors occur when the client is unable to find the required database. To solve this problem, first verify that you have correctly entered the service name that you want to use. Next verify that the service name parameters in the ADDRESS section of the connect descriptor in the tnsnames.ora file are correctly defined. Then, verify that the tnsnames.ora file is stored in the correct directory. The ORA-12198 and ORA-12203 errors can also occur if the listener on the remote node is not running. Verify that the listener on the remote node has started and is running. If the listener is not running, start the listener by using the Listener Control(LSNRCTL) utility.
3. The ORA-12533 error occurs if the protocol-specific parameters in the ADDRESS section of the designated connect descriptor in the tnsnames.ora file are incorrect. To solve this problem, use the correct protocol-specific parameters in the ADDRESS section of the connect descriptor.
4. The ORA-12545 error occurs when the listener on the remote node cannot be contacted. This may happen if the values of the ADDRESS parameter in the tnsnames.ora file and the listener.ora file are incorrect. In this case replace the incorrect values with the correct values in both the files. The ORA-12545 error can also occur if the listener on the remote node is not
started. To verify whether or not the listener is started, determine its status with the STATUS command of the LSNRCTL utility. If necessary, start the listener on the remote node with the START command.

Naming method

Hi,
we are taking into consideration the possibility to use directory or nis naming methods.
Do these types of naming methos have disadvantages when compared to local naming (TAF support, client load balancing,...)?
thanks in advance

but if I use OCI driver or OJDBC driver, will features like TAF and client load balancing be supported with NIS or Directory naming methods (we are planning to use them on client side not server side)?Certainly it will be possible. In case of DNS names you just configure your file say ldap.ora file to resolve name of oracle service with Directory. Other things will be as it is and Drivers will be there on your client machine as there will be a client installation there.
Regards.
Virendra.

Can we invoke a method using BCEL(byte code engineering library)

Hi i am new in Java bcel,So can anyone guide me in this problem.
I am searching for some techniques in BCEL to invoke a method of some class just like we use to invoke methods using Java Reflection.I have also tried a Java Assembler named "Jasmin" that used to interact with Operand Stack,Local variable array & Constant Pool etc so i guess this is the same containers with which our BCEL also interact with so then i am wondering why not then there exists a way through which we can invoke a method using BCEL IF this will happen in any case then kindly point it out some direction of help.
thanks in advance

856989 wrote:
I think i have clearly mentioned that "Tell me any way in doing this invocation in BCEL not in Reflection."
Why i not want to use reflection because it have "invocation overhead"Wrong.
If I dynamically load a class and reference it via a interface there is absolutely no difference in that and if I referenced the class statically and used it via an interface. The load and use process is exactly the same.
And the first uses "reflection".
If you use a proxy interface via something like java.lang.reflect.Method
then of course there is some overhead because there is in fact more classes involved. Just as if you had any other layer in any other code.
And even so unless you have actually profiled the application and found an actual bottleneck (and not just a measured impact) then even looking at it is a waste of time.
If it was me I would be far more concerned that inserting byte codes was correct for all cases.

Oracle client 8.1.7 and ldap naming method

Hello!
I have forms 6 and oracle net 8.0.5 but this version does not support ldap naming method.... so anyone know version of oracle client for windows support which ldap? Maybe 8.1.7? I need to find 8.1.7 client instalation maybe some links?
regards - mj

The minimum version for LDAP naming is 8.1.6, but I don't think it will be possible to direct Forms 6 to use it, I think you'll find that it's tied into the 8.0 stack.
If you want a centralised naming method for use with the 8.0 stack then it would have to be the old Oracle Names service, which was removed after version 9.2.
http://download.oracle.com/docs/cd/B10501_01/network.920/a96580/config_c.htm#485521

Cannot connect to a named instance using SSMS from a remote machine

Hi all,
SQL Server.....: 2012 EE
OS...................: Windows Server 2008 R2
I have a desktop machine, that i am using to administrer SQL Server (via SSMS) and to develop my SSIS solutions, but i can't connect to a named instance of my SQL Server. When i try to connect using SSMS to my named instance (myhost\DWSERVER)
i get a huge error message:
A network-related or instance-specific error occurred while establisinh a connection to SQL Server. The server was not found or was not accessible. Verify that the instance is correct and that SQL Server is configured to allow remote connections.
(provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
Locally, i am able to access that named instance using SSMS, just when i try to access from another machine, the above error pops-up to me.
I am using the SQL Server Authentication mode to connect to the named instance.
What am i doing wrong?
Thanks in advance.
Fabrício Pedroso Jorge Database Administrator - Belém, Pará, Brazil

Hi,
thanks for your attention.
That's correct, i can connect to my default instance both locally and remotelly. The default instance in on port 1433. I cannot find the port used by the named instance (DWSERVER).
Actually, i found this on the errorlog from the named instance:
2015-03-22 10:10:45.80 spid13s Server is listening on [ 'any' <ipv6> 49411].
2015-03-22 10:10:45.80 spid20s Server is listening on [ 'any' <ipv6> 5023].
2015-03-22 10:10:45.81 spid20s Server is listening on [ 'any' <ipv4> 5023].
2015-03-22 10:10:45.81 spid20s The Database Mirroring endpoint is now listening for connections.
2015-03-22 10:10:46.12 spid13s Server is listening on [ 'any' <ipv4> 49411].
2015-03-22 10:10:46.25 spid13s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\DWSERVER ].
2015-03-22 10:10:46.26 spid13s Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$DWSERVER\sql\query ].
2015-03-22 10:10:46.26 Server Server is listening on [ ::1 <ipv6> 49412].
2015-03-22 10:10:46.26 Server Server is listening on [ 127.0.0.1 <ipv4> 49412].
I can ping normally to the remote server.
Fabrício Pedroso Jorge Database Administrator - Belém, Pará, Brazil

Error while creating folder named "bin" using explorer view in sharepoint 2010

I am getting error when I create a folder in a library named "bin" using explorer view in sharepoint 2010.
When I create folders with other names I don't get any errors.
Please suggest.

Hi,
According to your description, my understanding is that you got an
error when you create a folder named “bin” in a SharePoint library with explorer view.
There are any Microsoft.NET Framework assemblies that have controls or parts that the SharePoint site uses, which are stored in the bin folder. You can remove “bin” from hidden segments, then you can create a folder named “bin”
in the SharePoint library with explorer view.
1.Opened IIS Manager and selected Server name -> Request Filtering -> Hidden Segments tab -> Removed "bin" from there:
2.Perform IISRESET:
Thanks,
Dean Wang

What is the method used for upload of data

Hi All,
What is the method used for upload of Data from excel spread sheets to SAP HR.
it is Bulk Data from many countries.LSMW or BDC Session Method?
what are country specific infotypes used for PA and OM.
can u plz give the list of country specific infotypes used for PA n OM Module.
Thanks
Archana

Hi Archana,
To Upload bulk data I think BDC is the best and effecient way.
Regarding Infotypes we dont have any country specific Infotypes in OM & PA. In Payroll we do have according to country wise.
I hope you had understood the point
Regards
Pavani
Remainder: Points to be given on answers

Is it possible to control the naming convention used by Aperture when importing photos? If so, how

When I import photos from my camera, I have them placed into projects based on the date the photos were taken. However, I do not like the naming convention used by Aperture as it causes the projects to sort into a non-chronologial order. The convention is MMM-DD-YYYY and I want to change it to YYYY-MM-DD. Is it possible in Aperture 3.2.4 to do this?

In the Import panel you can edit the preset for the file name format to "Image year - image month - image day - index" for example; the preset for folder names seems to be gone in Aperture 3,3 - at least I cannot find it any longer. You only seem to be able to enter the folder name manually in the Import panel.

Is it possible to call a class method using pattern in ABAP editor.

Hi,
Is it possible to call a class method using pattern in ABAP editor.
Thank U for Ur time.
Cheers,
Sam

Yes,
Click patterns.
Then choose Abap objects patterns.
Click on the Tick
It will give a new screen
Here Give the name of the class first.
Then the object (instance of the calss)
And finally the method ..
it will give you the pattern
Hope this helps.

TROUBLE WITH PAYMENT METHOD USED DIFFRENT VISA PAYMENTS STILL WONT WORK

TROUBLE WITH PAYMENT METHOD USED DIFFRENT VISA PAYMENTS STILL WONT WORK

This is a case for the iTunes Store Support:
1. Go to expresslane.apple.com
2. select 'itunes' and then 'itunes store' on the right
3. select a topic and a subject
4. click 'continue' and then 'email'
5. fill out the form and explain your situation
6. they will respond within 24 hours usually
Good luck
Stijn

How to retrieve the multiple rows data on PDF form in a web service method using WSDL DataConnection

How to retrieve the multiple rows data on PDF form in a web service method using WSDL DataConnection.
I have a multiple rows on PDF form. All rows have 4 textfields. I want to submit the multiple rows data to a method defiened in webservice.
Unable to retrieve the data in multiple rows within webservice method.

Hi Paul,
I'm now able to save the retrieved xml in a hidden text field and create dynamic table, and I'm able to fill this table from the XML, but the problem is that I could not find the correct way to loop on the xml, what I'm trying to say, the table will have number of rows with the data of the first row only, so can you tell me the right way to loop on the xml!
this is my code
TextField1.rawValue=xmlData.document.rawValue;
xfa.datasets.data.loadXML(TextField1.rawValue, true, false);
for(var i=0; i<count; i++)
xfa.form.resolveNode("form1.P1.Table1.Row1["+i+"].Num").rawValue = xfa.datasets.data.record.num.value;
xfa.form.resolveNode("form1.P1.Table1.Row1["+i+"].Name").rawValue = xfa.datasets.data.record.name.value;
Table1.Row1.instanceManager.addInstance(true);
Thanks
Hussam

Naming Method Use

Similar Messages

Maybe you are looking for