Erreur Oracle-12154: COBOL unix + Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production

Bonjour,

Suite au problème abordé dans la discussion suivante :
http://www.developpez.net/forums/d16...curseur-cobol/

J'ai ajouté ce code à un sous programme COBOL qui fait du SQL :

Code:

---

1 2 3 4 5 6

EXEC SQL CONNECT :ORAUSER IDENTIFIED BY :ORAPASS USING :ORASERV END-EXEC. END-EXEC

---

Lorsque j'exécute l'écran utilisant le programme appelant mon sous programme sous mon profile, ça fonctionne.

Mais si j'essaie par un autre profil, j'obtiens un SQLCODE -12154.
Or les ORAUSER, ORAPASS et ORASERV sont utilisés pour tous les profiles par d'autres programmes qui, eux fonctionnent.

Pouvez-vous m'aider ?

L'erreur est documentée elle dépende de la méthode de connexion, vous devez voir avec votre DBA.

Citation:

---

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.

---