I have the following job design:
In the main sequencer:
I have a routine activity stage that determines the current date followed by a sub-sequencer. A job parameter in the sub-sequencer gets the current date from the routine activity stage as returnvalue. I also have other job parameters including DSN, ID, and password for Oracle connectivity.
In the sub-sequencer:
I have three jobs. The first one needs the database connection parameters.
The Problem:
When I run the sub-sequencer on its own, the process runs fine. When I run the main sequencer without any job parameters, it again runs successfully. However, when I put the job parameters in the main sequencer and then run it, the first job in the sub-sequencer aborts with "ORA-12541:TNS no listener" error.
Is there something that I am doing wrong here? Please help me.
Thanks.
Parameter passing from outer sequencer to inner sequencer
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
The error message you receive is because an Oracle SID value is not being propagated properly to the job. Please verify whether you have any such value passed as parameter and check the value passed from the master sequence.
Please note that when you change any parameter property in a sequence, it automatically blanks the places where that property is used or passed to sub-jobs.
Please note that when you change any parameter property in a sequence, it automatically blanks the places where that property is used or passed to sub-jobs.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
This error can also mean that all of the Oracle listeners that the DBA has set up are already in use, so no more listeners can be allocated. Check with your DBA, who should be monitoring such things.
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.