Surrogate Key Stage Error-- Unable to lock state file
Moderators: chulett, rschirm, roy
Surrogate Key Stage Error-- Unable to lock state file
Hi,
I am using Surrogate Key stage in my job to generate a unique sequence number. I am using the STAT file for creating it.
The job worked fine many times previously, but now it started throwing the following error and job getting aborted.
Error:
skg_MatchRecs,0: Unable to lock state file /path/proj1/output/101_CluserFle.txt: No locks available.
skg_MatchRecs,0: The runLocally() of the operator failed.
skg_MatchRecs,0: Output 0 produced 0 records.
main_program: APT_PMsectionLeader(3, node3), player 2 - Unexpected exit status 1.
APT_PMsectionLeader(1, node1), player 4 - Unexpected exit status 1.
main_program: Step execution finished with status = FAILED.
Any one has faced same king of problem before? Any ideas/help to resolve this issue?
--Thanks
--Swathi
I am using Surrogate Key stage in my job to generate a unique sequence number. I am using the STAT file for creating it.
The job worked fine many times previously, but now it started throwing the following error and job getting aborted.
Error:
skg_MatchRecs,0: Unable to lock state file /path/proj1/output/101_CluserFle.txt: No locks available.
skg_MatchRecs,0: The runLocally() of the operator failed.
skg_MatchRecs,0: Output 0 produced 0 records.
main_program: APT_PMsectionLeader(3, node3), player 2 - Unexpected exit status 1.
APT_PMsectionLeader(1, node1), player 4 - Unexpected exit status 1.
main_program: Step execution finished with status = FAILED.
Any one has faced same king of problem before? Any ideas/help to resolve this issue?
--Thanks
--Swathi
--
Swathi Ch
Swathi Ch
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Surrogate stage is working fine now, It is problem with the linux server.
And regarding the Datasets on multinode,
If the dataset is created with multi node and reading with a single node, then it is a probelm. It will throw error like below
has n partitions, but only 1 is accessible from the nodes in the configuration file.
But if the dataset is created with single node and reading from a multi node file, it wont be a problem. Datastage can read the multi node dataset from single node.
And regarding the Datasets on multinode,
If the dataset is created with multi node and reading with a single node, then it is a probelm. It will throw error like below
has n partitions, but only 1 is accessible from the nodes in the configuration file.
But if the dataset is created with single node and reading from a multi node file, it wont be a problem. Datastage can read the multi node dataset from single node.
--
Swathi Ch
Swathi Ch