DSR_RECORD (Action=2); check DataStage is set up correctly i
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 107
- Joined: Wed Sep 29, 2004 10:15 am
DSR_RECORD (Action=2); check DataStage is set up correctly i
Hi,
Initially created a JOBsequence with a few sequence, these are independent with no dependencies, but When adding more jobsequences(with no dependencies) to the exsisting one i'am seeing this error message
==============================================
Error calling subroutine: DSR_RECORD (Action=2); check DataStage is set up correctly in project Dhl_Flat_Oracle
(Internal Error (81021))
===============================================
Very urgent any advice is appreciated.
Thanks.
Initially created a JOBsequence with a few sequence, these are independent with no dependencies, but When adding more jobsequences(with no dependencies) to the exsisting one i'am seeing this error message
==============================================
Error calling subroutine: DSR_RECORD (Action=2); check DataStage is set up correctly in project Dhl_Flat_Oracle
(Internal Error (81021))
===============================================
Very urgent any advice is appreciated.
Thanks.
Where (designer/director) and when (runtime,save,open,add) are you seeing the error message? If you save-as another name does the new one have the same error?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The 81xxx messages relate to the dsrpc daemon. Specifically, 81021 decodes as Error writing to pipe.
Something (possibly intermittent) has gone awry between processes, dsrpcd, dsapi_server, dsapi_slave. Exactly where is not reported.
Establishing a new connection is likely to fix this problem.
Code: Select all
SELECT * FROM SYS.MESSAGE WHERE @ID = 081021;
Establishing a new connection is likely to fix this problem.
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: 107
- Joined: Wed Sep 29, 2004 10:15 am
Hi
Thanks for sharing your ideas
Actually i had placed 10 job activitys on the sequence canvas and ran the sequence . every thing is fine and data has been populated to the subsequent target tables. on the same canvas then i added another 8 job activitys , when i try to run it then it is throughing this error. all my 18 jobs are compiled and they are working fine when i ran each job individually.
I am not aware that why this error has happened, Kindly through me a light on it that what are the area's that had a problem which is throughing me this kind of error
thanks
RK
Thanks for sharing your ideas
Actually i had placed 10 job activitys on the sequence canvas and ran the sequence . every thing is fine and data has been populated to the subsequent target tables. on the same canvas then i added another 8 job activitys , when i try to run it then it is throughing this error. all my 18 jobs are compiled and they are working fine when i ran each job individually.
I am not aware that why this error has happened, Kindly through me a light on it that what are the area's that had a problem which is throughing me this kind of error
thanks
RK
-
- Participant
- Posts: 107
- Joined: Wed Sep 29, 2004 10:15 am
Where (designer/director) and when (runtime,save,open,add) are you seeing the error message? If you save-as another name does the new one have the same error?
I had done this on designer , while saving the sequence i am getting this problem, i tried to save the same sequence with another name , it is throughing the same error.
Thanks
RK
I had done this on designer , while saving the sequence i am getting this problem, i tried to save the same sequence with another name , it is throughing the same error.
Thanks
RK
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Are you running on multiple machines (MPP)? The conductor, section leader and player processes communicate via TCP, and with 16 jobs x N stages chances are you have overloaded the capacity of the processes all to communicate simultaneously. For example all processes must relay warnings and errors to the conductor process, which is the only process that writes to the log.
However, since the error is being reported from DSR_RECORD, which is a helper subroutine that accesses records in the DataStage Repository, I don't believe that is the appropriate diagnosis. It may be that one of your Repository tables is in need of verification and/or reindexing.
However, since the error is being reported from DSR_RECORD, which is a helper subroutine that accesses records in the DataStage Repository, I don't believe that is the appropriate diagnosis. It may be that one of your Repository tables is in need of verification and/or reindexing.
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: 107
- Joined: Wed Sep 29, 2004 10:15 am
I am relatively new to the admin side of DataStage, and have not been able to take an admin class yet either. I am researching an issue that is similar to this and found Ray's SQL query above.ray.wurlod wrote:The 81xxx messages relate to the dsrpc daemon. Specifically, 81021 decodes as Error writing to pipe.Something (possibly intermittent) has gone awry between processes, dsrpcd, dsapi_server, dsapi_slave. Exactly where is not reported.Code: Select all
SELECT * FROM SYS.MESSAGE WHERE @ID = 081021;
Establishing a new connection is likely to fix this problem.
How do I run this? I tried running with dssh and got the following error message:
Code: Select all
myserver:/u001/Ascential/DataStage/DSEngine> bin/dssh
DataStage Command Language 7.5
Copyright (c) 1997 - 2004 Ascential Software Corporation. All Rights Reserved
DSEngine logged on: Wed Apr 25 07:48:38 2007
>select * from sys.message where @id = 081021;
DataStage/SQL: Table "sys.message" does not exist.
Thanks!
Brad.