| Author |
Message
|
| vikas.bhu |
 Posted: Wed Jul 08, 2015 6:45 am Post subject: Accessing multiple DB in Same compute node in 8.0.0.3 |
 |
|
Disciple
Joined: 17 May 2009
Posts: 159
|
Hi All,
I have a flow which access 2 db in same compute node .I can see that WMB is able to access the tables residing in multiple DB's but it is not able to access the sequence residing.
following is the sequence of execution:
1-Database.{DSN1}.{Schema1}.TTABLE2 AS B WHERE -----OK
2-Database.{DSN2}.{Schema2}.TTABLE2 AS B WHERE -----OK
But while executing following is creating problem.
following is broker log
VALUES NEXTVAL FOR DSN2.Schema2.SEQUENCE2..
Execution of the database statement against data source DSN2 failed. Please refer to the system error log for more details.
Need help.. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Jul 08, 2015 6:50 am Post subject: Re: Accessing multiple DB in Same compute node in 8.0.0.3 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vikas.bhu wrote: |
| I have a flow which access 2 db in same compute node . |
Are the databases the same type, i.e. both Oracle?
| vikas.bhu wrote: |
| Execution of the database statement against data source DSN2 failed. Please refer to the system error log for more details. |
And the more details are........? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jul 08, 2015 6:55 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
You might also want to mention what the requirement is to access databases like this rather than (for example) performing the access in 2 Compute nodes and aggregating the results.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vikas.bhu |
| Posted: Wed Jul 08, 2015 7:00 am Post subject: |
|
|
Disciple
Joined: 17 May 2009
Posts: 159
|
both are DB2..and there is no further log..
 |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jul 08, 2015 7:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
And what part of the ESQL Select statement knows about NEXTVAL?
Also, what part of "AS B" is being used, properly? And are both datasources really referred to "AS B"? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jul 08, 2015 7:17 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vikas.bhu wrote: |
| both are DB2..and there is no further log.. |
There's nothing? Not in the broker log, not in the system log, not in the syserr from the EG, just one sentence:
| vikas.bhu wrote: |
| Execution of the database statement against data source DSN2 failed. Please refer to the system error log for more details |
without even a BIP number? That's the only indication of any problem? Really?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vikas.bhu |
| Posted: Wed Jul 08, 2015 7:28 am Post subject: |
|
|
Disciple
Joined: 17 May 2009
Posts: 159
|
SET Environment.sequence2 =Passthrough(VALUES NEXTVAL FOR DSN2.SCHEMA2.Sequence2);
and both are not refereed as B.(Sorry about that).. |
|
| Back to top |
|
|
| vikas.bhu |
| Posted: Wed Jul 08, 2015 8:27 am Post subject: |
|
|
Disciple
Joined: 17 May 2009
Posts: 159
|
it is received as warning ..
BIP12077W so no error in log.. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jul 08, 2015 8:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vikas.bhu wrote: |
it is received as warning ..
BIP12077W so no error in log.. |
The fact that a message is a warning doesn't mean it isn't accompanied by other messages. The fact that this warning message explicitly mentions the system log should be an indication that the author of the warning message expected there to be additional content of a helpful nature.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mgk |
| Posted: Thu Jul 09, 2015 3:25 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Can you post your actual ESQL here in full?
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| vikas.bhu |
| Posted: Thu Jul 09, 2015 3:51 am Post subject: |
|
|
Disciple
Joined: 17 May 2009
Posts: 159
|
Thanks Every one ...
Admin was not giving right permission to broker...and there were many such sequence in different DB's ..he give permission to broker to select sequence and restarted the broker.And finally it start working.Me and Admin sit in 2 different location so I could not see what exactly happening on his side which I think the main reason for this issue.
thanks Again.. |
|
| Back to top |
|
|
|
|
