TNS:could not resolve the connect identifier specified
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54
- Joined: Mon Dec 24, 2007 9:27 am
TNS:could not resolve the connect identifier specified
Hello Gurus,
I am moving from one DB to another DB and I am using environment variables for server,user,password and schema.
Admin updated the tnsnames.ora with the new connection. Updated the environment variables with new DB details.
When I open a job and do View Data, the connector is able to connect to the new DB and is giving the desired results.
But, when I compile the job and re-run the job in its entirety, I am getting the error: ConfigLvl_Ora_Load,1: [IIS-CONN-ORA-001004] The connector could not establish connection to Oracle server TEBDB01. Method: OCIServerAttach, Error code: 12,154, Error message ORA-12154: TNS:could not resolve the connect identifier specified. (CC_OraConnection::verifyConnection, file CC_OraConnection.cpp, line 4,404)
Please assist.
I am moving from one DB to another DB and I am using environment variables for server,user,password and schema.
Admin updated the tnsnames.ora with the new connection. Updated the environment variables with new DB details.
When I open a job and do View Data, the connector is able to connect to the new DB and is giving the desired results.
But, when I compile the job and re-run the job in its entirety, I am getting the error: ConfigLvl_Ora_Load,1: [IIS-CONN-ORA-001004] The connector could not establish connection to Oracle server TEBDB01. Method: OCIServerAttach, Error code: 12,154, Error message ORA-12154: TNS:could not resolve the connect identifier specified. (CC_OraConnection::verifyConnection, file CC_OraConnection.cpp, line 4,404)
Please assist.
-
- Participant
- Posts: 54
- Joined: Mon Dec 24, 2007 9:27 am
-
- Participant
- Posts: 54
- Joined: Mon Dec 24, 2007 9:27 am
When I am saying "View Data", I am not changing any credentials. The parameters are defined as $PROJDEF so it should be getting from whatever we defined in the administrator.
In short, it is using the same credentials to connect to the database.
As far as the user, who is running the job from the designer is myself.
Sorry, if I am not answering your question to assist me.
In short, it is using the same credentials to connect to the database.
As far as the user, who is running the job from the designer is myself.
Sorry, if I am not answering your question to assist me.
-
- Participant
- Posts: 342
- Joined: Tue Nov 04, 2008 10:38 am
- Location: Chennai, India
-
- Participant
- Posts: 54
- Joined: Mon Dec 24, 2007 9:27 am
So... you ARE on a grid? If so, does this error happen on a specific node?
For the record, I am not talking about the credentials you are using. I'm talking about the environment in both cases, the collection of values like $ORACLE_HOME, path, shared library (etc) that exist when the job runs or when you are logged in. And you still haven't confirmed one way or the other what user your job runs under... yours or a common one like "dsadm".
For the record, I am not talking about the credentials you are using. I'm talking about the environment in both cases, the collection of values like $ORACLE_HOME, path, shared library (etc) that exist when the job runs or when you are logged in. And you still haven't confirmed one way or the other what user your job runs under... yours or a common one like "dsadm".
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54
- Joined: Mon Dec 24, 2007 9:27 am