Failed to establish datasource connection
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 106
- Joined: Thu Jun 08, 2006 8:51 am
Failed to establish datasource connection
Hi,
I post this after seached the word "Failed to establish datasource connection" in this forum. In all the forums, it has been mentioned that "Failed to establish datasource connection" might be happened due to connection string or userid or password or DB or server name wrong.
But Here is different. the job has only two stages - OLEDB and Hash.
|-------|------------------>|-----------|
|-------|------------------>|-----------|
|-------|------------------>|-----------|
OLEDB|------------------>|Hash------|
|-------|------------------>|------------|
|-------|------------------>|------------|
OLEDB stage has settings all default. and the same to Hash stage (Dynamic - 30). It has 17 links that are connecting different tables and some of them (3) are connecting to the same table.
When job is running, most of links are establishing a connection, but few (1 or 2) dont establish a connection. At different times, different link(s) dont establish connection. Finally job aborts by throwing the error "Failed to establish datasource connection and OLE DB provider error". I could not identify the issue.
I appreicate if any one gives input on this.
Is there a problem with OLEDB stage or SQL server or Network issue or any other?
Regards,
Venkat
I post this after seached the word "Failed to establish datasource connection" in this forum. In all the forums, it has been mentioned that "Failed to establish datasource connection" might be happened due to connection string or userid or password or DB or server name wrong.
But Here is different. the job has only two stages - OLEDB and Hash.
|-------|------------------>|-----------|
|-------|------------------>|-----------|
|-------|------------------>|-----------|
OLEDB|------------------>|Hash------|
|-------|------------------>|------------|
|-------|------------------>|------------|
OLEDB stage has settings all default. and the same to Hash stage (Dynamic - 30). It has 17 links that are connecting different tables and some of them (3) are connecting to the same table.
When job is running, most of links are establishing a connection, but few (1 or 2) dont establish a connection. At different times, different link(s) dont establish connection. Finally job aborts by throwing the error "Failed to establish datasource connection and OLE DB provider error". I could not identify the issue.
I appreicate if any one gives input on this.
Is there a problem with OLEDB stage or SQL server or Network issue or any other?
Regards,
Venkat
-
- Participant
- Posts: 106
- Joined: Thu Jun 08, 2006 8:51 am
Basically asking if the problem is consistent or not. In other words, do the exact same connections fail each time or do the failed ones change with each run? If it is the latter, then I'd be checking with your DBA and/or SysAdmin to see if you are having resource issues.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 106
- Joined: Thu Jun 08, 2006 8:51 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Is there a limit on the number of simultaneous connections to the database server? For example Oracle is limited by the number of listeners that have been configured.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 106
- Joined: Thu Jun 08, 2006 8:51 am
Hi Ray,ray.wurlod wrote:Is there a limit on the number of simultaneous connections to the database server? For example Oracle is limited by the number of listeners that have been configured. ...
Thanks for your response.
But there is no limitation on simultaneous connections on SQL server. Is there any limitations on Datastage side?
Regards,
They do have a per-cpu with no concurrent limit licensing option, but in this case they probably do not have that license.
SQL Server Licensing
SQL Server Licensing
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 106
- Joined: Thu Jun 08, 2006 8:51 am
Hi ArndW,ArndW wrote:They do have a per-cpu with no concurrent limit licensing option, but in this case they probably do not have that license.
[url=http://www.microsoft.com/sqlserver/2005 ... nsing.aspx]SQL Serv ...
We have a license on SQL server 2000 Developer edition. There seems no limit on concurrent in this.
Regards,
-
- Participant
- Posts: 106
- Joined: Thu Jun 08, 2006 8:51 am
Hi all,
thanks for your valuable response and support.
this problem got resolved. Due to some incorrect settings in the DB config, this issue happened. After corrected the config file, this problem is gone.
In the DB config, the "set working set size" was set to 1. This should be set to 1, when the value of "Max and Min server memory" is user defined and both has same value.
But at our environment, this was 1, when "Max and Min server memory" is automatic. Actually in this case, "set working set size" should be 0.
After changed to 0, it is working fine.
Regards,
Venkat
thanks for your valuable response and support.
this problem got resolved. Due to some incorrect settings in the DB config, this issue happened. After corrected the config file, this problem is gone.
In the DB config, the "set working set size" was set to 1. This should be set to 1, when the value of "Max and Min server memory" is user defined and both has same value.
But at our environment, this was 1, when "Max and Min server memory" is automatic. Actually in this case, "set working set size" should be 0.
After changed to 0, it is working fine.
Regards,
Venkat