Iam scheduling 2 parallel jobs to run at sametime and both are using same surrogate key source which is already created.Iam trying with Db sequence and of type DB2 database...But when i run both of them at same time its throwing error and if i try same jobs individually they are working fine..
Plz let me whats is happending internally that both of them when scheduled for same time are throwing error...
scheduling 2parall jobs wit surogatekey 2 run at same time
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 9
- Joined: Wed Feb 06, 2008 12:13 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 9
- Joined: Wed Feb 06, 2008 12:13 am
This was the error in both jobs when run at same time
This was the warningray.wurlod wrote:What (exact) error message is logged? ...
main_program: Failed to initialize job monitoring. Monitor information will not be generated.
-------------------------------------------------------------------------------------
And ths was error:
Surrogate_Key_Generator_6,0: Error Idx = 5;
DB2Driver Embedded SQL message: SQL0553N An object cannot be created with the schema name "SYSTEM ".
SQLSTATE=42939
;
sqlcode = -553;
sqlstate = 42939
---------------------------------------------------------------------------------
Information:
Contents of phantom output file
DataStage Job 549 Phantom 1524
writeSocket() returned 4
DataStage Phantom Finished....
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 9
- Joined: Wed Feb 06, 2008 12:13 am
ray.wurlod wrote:Looks like you lack privilege to use the schema name SYSTEM. Try using a more appropriate schema (owner) name. ...
If i lack privilege then when i run only one job at once its not throwing error... It has got excuted successfully..Why is that its throwing error whn i try to run both the jobs at same time....
Thanks for help....
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
OK then, if it's not privileges, it's something in the database preventing one of the jobs from creating a new value in the sequence - get your DBA to help - this problem would probably occur if two simultaneous non-DataStage clients were also trying to use the same sequence.
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.