Individual Job Running fine, but when run through sequence j

[chowdhury99]

Hello,
When I run my sequence in Dev Environment it's running fine. But, when I run in Test Environment sequence aborted. When I run the job individually in test, that runs successfully. Following error I am getting:

ORA-12537: TNS:connection closed
Connect failed: ORA-12537: TNS:connection closed
APT_OraUpsertOperator: connect failed. Environment: user: efpdm; password: *****; server: FPMT10; ORACLE_SID: ; ORACLE_HOME: /opt/oracle/product/102.

I searched the dsxchange, but didn't able to solve the issue.

I appreciate any kind of suggestions.

Thanks.

[swarnkar]

Hello,
When I run my sequence in Dev Environment it's running fine. But, when I run in Test Environment sequence aborted. When I run the job individually in test, that runs successfully. Following error I am getting:


Thanks.

Just check what are the values for DSN,UserName,Password you have passed through sequencer job to server job (If at all, you passing any value), or make sure you are calling the right job.

While running job through sequencer, your server job is not able to make connections to database.

Thanks,
Nitin Swarnkar

[chowdhury99]

Hi Nitin,
We are using parameter sets, so username/password is not an issue.

Thanks.

Hello,
When I run my sequence in Dev Environment it's running fine. But, when I run in Test Environment sequence aborted. When I run the job individually in test, that runs successfully. Following error I am getting:


Thanks.

Just check what are the values for DSN,UserName,Password you have passed through sequencer job to server job (If at all, you passing any value), or make sure you are calling the right job.

While running job through sequencer, your server job is not able to make connections to database.

Thanks,
Nitin Swarnkar

[priyadarshikunal]

it should be easy for your DBA to find out the difference between dev and test box. Involve him.

[chowdhury99]

it should be easy for your DBA to find out the difference between dev and test box. Involve him.

Hi Priya,
So far I am thinking it may be the limited number of connection issues from datastage to database. Currently, Dev and Test both have same number of connections. I already requested our DBA to increase the connections. Once I get the increased connections, I will run and check if there are still errors.

Thanks

[ray.wurlod]

Look in the job logs - job starting event - for the successful and failed attempts. Is the password, as encrypted, the same for both?

[chowdhury99]

Our DBA increased the number of concurrent connections from datastage to database 100 to 200. That solved the problem. So I am marking this post as resolved.

Look in the job logs - job starting event - for the successful and failed attempts. Is the password, as encrypted, the same for both? ...

[chowdhury99]

Yes, password was same for both.

Look in the job logs - job starting event - for the successful and failed attempts. Is the password, as encrypted, the same for both? ...