Surrogate Key Generator Stage
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 306
- Joined: Wed Jun 21, 2006 11:41 am
Surrogate Key Generator Stage
Hi,
We have a job that looks like this....When we execute we error out on the link from the Surrogate Key generator to the ODBC stage with the errors below.
ODBC stage
|
|
Sequential File---->> Look Up Stage-->transformer stage-->> ODBC stg
|
|
Surrogate Key Gen stg ----> ODBC stage
Warning # 1:
main_program: Operator "parallel APT_KeyGenerator in skNewPlan" is not wave aware; the operator will be reset and rerun on each wave if multiple waves present. This may lead to incorrect results and memory issues. Update the operator to make it wave aware and calls setWaveAware() in describeOperator() to inform the framework that the operator knows how to handle waves. [sc\sc.C:4252]
Fatal Error # 1:
node_node0: Player 7 terminated unexpectedly. [processmgr\player.C:157]
Fatal Error # 2:
main_program: Step execution finished with status = FAILED. [sc\sc_api.C:242]
Any suggestions or ideas would be appreciated.
Thanks - - John
We have a job that looks like this....When we execute we error out on the link from the Surrogate Key generator to the ODBC stage with the errors below.
ODBC stage
|
|
Sequential File---->> Look Up Stage-->transformer stage-->> ODBC stg
|
|
Surrogate Key Gen stg ----> ODBC stage
Warning # 1:
main_program: Operator "parallel APT_KeyGenerator in skNewPlan" is not wave aware; the operator will be reset and rerun on each wave if multiple waves present. This may lead to incorrect results and memory issues. Update the operator to make it wave aware and calls setWaveAware() in describeOperator() to inform the framework that the operator knows how to handle waves. [sc\sc.C:4252]
Fatal Error # 1:
node_node0: Player 7 terminated unexpectedly. [processmgr\player.C:157]
Fatal Error # 2:
main_program: Step execution finished with status = FAILED. [sc\sc_api.C:242]
Any suggestions or ideas would be appreciated.
Thanks - - John
-
- Premium Member
- Posts: 306
- Joined: Wed Jun 21, 2006 11:41 am
Since you aren't doing wave processing you can ignore the warning; but the failure message(s) in the logs do contain additional information on the actual cause, could you post the complete and unabridged error messages please?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Premium Member
- Posts: 306
- Joined: Wed Jun 21, 2006 11:41 am
-
- Premium Member
- Posts: 306
- Joined: Wed Jun 21, 2006 11:41 am
Hi ArndW,
Is this what you were looking for?
Server:NJROS1BBLA0602
Project:CLR_NQRPT
Job No:2
Job name:jb_ld_dim_metrix_plan
Invocation:
Event Number:753
Event type:Fatal
User:NJROS1BBLA0602\DSADM
Timestamp:6/15/2009 8:11:32 AM
Message Id:IIS-DSEE-TFPM-00192
Message:
node_node0: Player 7 terminated unexpectedly. [processmgr\player.C:157]
Server:NJROS1BBLA0602
Project:CLR_NQRPT
Job No:2
Job name:jb_ld_dim_metrix_plan
Invocation:
Event Number:754
Event type:Fatal
User:NJROS1BBLA0602\DSADM
Timestamp:6/15/2009 8:11:32 AM
Message Id:IIS-DSEE-TFSC-00011
Message:
main_program: Step execution finished with status = FAILED. [sc\sc_api.C:242]
If not please let me know how to get teh more detailed messages. These are copied from director.
Thanks - - John
Is this what you were looking for?
Server:NJROS1BBLA0602
Project:CLR_NQRPT
Job No:2
Job name:jb_ld_dim_metrix_plan
Invocation:
Event Number:753
Event type:Fatal
User:NJROS1BBLA0602\DSADM
Timestamp:6/15/2009 8:11:32 AM
Message Id:IIS-DSEE-TFPM-00192
Message:
node_node0: Player 7 terminated unexpectedly. [processmgr\player.C:157]
Server:NJROS1BBLA0602
Project:CLR_NQRPT
Job No:2
Job name:jb_ld_dim_metrix_plan
Invocation:
Event Number:754
Event type:Fatal
User:NJROS1BBLA0602\DSADM
Timestamp:6/15/2009 8:11:32 AM
Message Id:IIS-DSEE-TFSC-00011
Message:
main_program: Step execution finished with status = FAILED. [sc\sc_api.C:242]
If not please let me know how to get teh more detailed messages. These are copied from director.
Thanks - - John
-
- Premium Member
- Posts: 306
- Joined: Wed Jun 21, 2006 11:41 am
Hi,
I opened a PMR with IBM and just recieved the following:
Hello John,
Engineering has provided the following:
This is known issue with surrogate key in 8.0.1
We are working on a fix for 8.5. The usual workaround for this is to use the key generator in the database (Oracle, DB2 etc).
Please try the workaround and let me know the results.
Thank you.
I opened a PMR with IBM and just recieved the following:
Hello John,
Engineering has provided the following:
This is known issue with surrogate key in 8.0.1
We are working on a fix for 8.5. The usual workaround for this is to use the key generator in the database (Oracle, DB2 etc).
Please try the workaround and let me know the results.
Thank you.
-
- Premium Member
- Posts: 306
- Joined: Wed Jun 21, 2006 11:41 am
And they ask me to respond to....
AmI staisfied? Sure we spend all this money and there going to ask us to do the ETL in the database or withing shell scripts!!!
Hello John,
Since the job is working with the workaround and there is nothing additional I can assist with for this PMR, may I close it?
Are you satisfied with the resolution?
Please let me know.
Thank you.
AmI staisfied? Sure we spend all this money and there going to ask us to do the ETL in the database or withing shell scripts!!!
Hello John,
Since the job is working with the workaround and there is nothing additional I can assist with for this PMR, may I close it?
Are you satisfied with the resolution?
Please let me know.
Thank you.
-
- Premium Member
- Posts: 892
- Joined: Thu Oct 16, 2003 5:18 am
Re: Surrogate Key Generator Stage
Wave is new feature in 8.00 and hence all josb need to be wave aware
Regards
Sreeni
Regards
Sreeni
JPalatianos wrote:Hi,
We have a job that looks like this....When we execute we error out on the link from the Surrogate Key generator to the ODBC stage with the errors below.
ODBC stage
|
|
Sequential File---->> Look Up Stage-->transformer stage-->> ODBC stg
|
|
Surrogate Key Gen stg ----> ODBC stage
Warning # 1:
main_program: Operator "parallel APT_KeyGenerator in skNewPlan" is not wave aware; the operator will be reset and rerun on each wave if multiple waves present. This may lead to incorrect results and memory issues. Update the operator to make it wave aware and calls setWaveAware() in describeOperator() to inform the framework that the operator knows how to handle waves. [sc\sc.C:4252]
Fatal Error # 1:
node_node0: Player 7 terminated unexpectedly. [processmgr\player.C:157]
Fatal Error # 2:
main_program: Step execution finished with status = FAILED. [sc\sc_api.C:242]
Any suggestions or ideas would be appreciated.
Thanks - - John
-
- Premium Member
- Posts: 892
- Joined: Thu Oct 16, 2003 5:18 am
Re: Surrogate Key Generator Stage
Wave is new feature in 8.00 and hence all josb need to be wave aware
Regards
Sreeni
Regards
Sreeni
JPalatianos wrote:Hi,
We have a job that looks like this....When we execute we error out on the link from the Surrogate Key generator to the ODBC stage with the errors below.
ODBC stage
|
|
Sequential File---->> Look Up Stage-->transformer stage-->> ODBC stg
|
|
Surrogate Key Gen stg ----> ODBC stage
Warning # 1:
main_program: Operator "parallel APT_KeyGenerator in skNewPlan" is not wave aware; the operator will be reset and rerun on each wave if multiple waves present. This may lead to incorrect results and memory issues. Update the operator to make it wave aware and calls setWaveAware() in describeOperator() to inform the framework that the operator knows how to handle waves. [sc\sc.C:4252]
Fatal Error # 1:
node_node0: Player 7 terminated unexpectedly. [processmgr\player.C:157]
Fatal Error # 2:
main_program: Step execution finished with status = FAILED. [sc\sc_api.C:242]
Any suggestions or ideas would be appreciated.
Thanks - - John
Re: Surrogate Key Generator Stage
You do realize how singularly unhelpful posting something like this without any explanation is, yes? The only way posted this would help would be if you also included a description of what a "wave" is and some clue how to make a job "wave aware". If there even is such a thing.Sreenivasulu wrote:Wave is new feature in 8.00 and hence all jobs need to be wave aware
If you read the warning logged, you'll see that it is the operator that needs to be "wave aware" and properly communicate that to the parallel framework, something we as users have absolutely no control over.
ps. Forgot to add that waves are not a new feature, AFAIK they've always been in the product.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
DID you let them know?JPalatianos wrote:And they ask me to respond to....
AmI staisfied? Sure we spend all this money and there going to ask us to do the ETL in the database or withing shell scripts!!!
Hello John,
Since the job is working with the workaround and there is nothing additional I can assist with for this PMR, may I close it?
Are you satisfied with the resolution?
Please let me know.
Thank you.
If so, did they respond your no doubt constructive criticism?
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.
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI