Data source does not support transactions.
Moderators: chulett, rschirm, roy
Data source does not support transactions.
Using the InfmxCLI stage as input into a transformation stage of a server job throws the warning "This data source does not support transactions." The job completes but the warning exists.
Any assistance is appreciated.
Brad
Any assistance is appreciated.
Brad
If you do a search of this forum, you see that there's an excellent discussion of your exact message in the Oliver mailing list archives.
Basically, your problem deals will the transaction log on the source table.
Basically, your problem deals will the transaction log on the source table.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You have created an Informix database without logging. Therefore, this database cannot support transactions. If you want to support transactions in an Informix database, you must create the database WITH logging.
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.
Hi,
as far as I remember this is a bug (can't remember exactly where)
and no fixes will be made (as of the case we opend with ascential)
you have to accept this behaviour and move on.
the only thing that made that customer accept this was the simple fact that we were migrating the DB from informix to something else.
maybe you can flex a muscle or 2 and they'll do something about it.
Good Luck
as far as I remember this is a bug (can't remember exactly where)
and no fixes will be made (as of the case we opend with ascential)
![Crying or Very sad :cry:](./images/smilies/icon_cry.gif)
you have to accept this behaviour and move on.
the only thing that made that customer accept this was the simple fact that we were migrating the DB from informix to something else.
maybe you can flex a muscle or 2 and they'll do something about it.
Good Luck
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
![Image](http://www.worldcommunitygrid.org/images/logo.gif)
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
![Image](http://www.worldcommunitygrid.org/images/logo.gif)
Thank you all for the answers.
Brad
Brad
![Smile :)](./images/smilies/icon_smile.gif)
roy wrote:Hi,
as far as I remember this is a bug (can't remember exactly where)
and no fixes will be made (as of the case we opend with ascential)![]()
you have to accept this behaviour and move on.
the only thing that made that customer accept this was the simple fact that we were migrating the DB from informix to something else.
maybe you can flex a muscle or 2 and they'll do something about it.
Good Luck
-
- Premium Member
- Posts: 385
- Joined: Tue Oct 07, 2003 4:55 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
DataStage reports all messages generated by database servers.
DataStage is not geared to work to non-transactional databases (except UniVerse and UniData), so it sends a COMMIT. Or more than one.
IDS responds to COMMIT on a non-logging database with the indicated message.
Can you suggest a generic strategy for DataStage engineers about which messages not to report? (Your answer must cover all possible stage types, including the ones not written yet.)
You can, if you hate this message so much, create a custom passive stage that emulates the functionality of the Informix stage, but which explicitly does not log this message - or, better, does not send COMMIT if connected to a non-logging database.
DataStage is not geared to work to non-transactional databases (except UniVerse and UniData), so it sends a COMMIT. Or more than one.
IDS responds to COMMIT on a non-logging database with the indicated message.
Can you suggest a generic strategy for DataStage engineers about which messages not to report? (Your answer must cover all possible stage types, including the ones not written yet.)
You can, if you hate this message so much, create a custom passive stage that emulates the functionality of the Informix stage, but which explicitly does not log this message - or, better, does not send COMMIT if connected to a non-logging database.
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.
Ray,
What about adding a new isolation level for instance ? I encountered a case with an ODBC stage (SELECT Only) using a gateway product connecting ADABAS. That ADABAS was read-only - whichever isolation level I tried the ODBC stage sent a COMMIT before closing the connection (And got a warning of course which messed up my SEQUENCERS !!!)
What about adding a new isolation level for instance ? I encountered a case with an ODBC stage (SELECT Only) using a gateway product connecting ADABAS. That ADABAS was read-only - whichever isolation level I tried the ODBC stage sent a COMMIT before closing the connection (And got a warning of course which messed up my SEQUENCERS !!!)
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
This won't help. DataStage sends a COMMIT. There is no transaction isolation level that bypasses this. Therefore an Informix database created without logging will still generate the error message when it receives the COMMIT.
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.
It doesn't have to.ariear wrote:Ray,
(And got a warning of course which messed up my SEQUENCERS !!!)
"[StageName].$JobStatus = 1 OR [StageName].$JobStatus = 2" on your custom trigger will absorb those warning messages just fine. Now if you hold the philosophy that there MUST be no warning messages...
Oh well.
-T.J.
Developer of DataStage Parallel Engine (Orchestrate).
Hi,
the only thing that might help is if your job is successfull only if no real warnings occur;
this means that you can set the warning limit to the number of DB connections your job has (that generate the warning) and check for failed/Aborted status to know it failed, otherwise treat the job as successfull.
this is good only in cases when you want to proceed when the process/job had no real warnings except for the "doesn't support transaction" warnings
IHTH (I Hope This Helps)
the only thing that might help is if your job is successfull only if no real warnings occur;
this means that you can set the warning limit to the number of DB connections your job has (that generate the warning) and check for failed/Aborted status to know it failed, otherwise treat the job as successfull.
this is good only in cases when you want to proceed when the process/job had no real warnings except for the "doesn't support transaction" warnings
IHTH (I Hope This Helps)
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
![Image](http://www.worldcommunitygrid.org/images/logo.gif)
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
![Image](http://www.worldcommunitygrid.org/images/logo.gif)