Parameterized password in Stored Procedure stage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 75
- Joined: Mon Jul 12, 2010 4:11 am
- Location: Chennai
Parameterized password in Stored Procedure stage
Hi,
I'm using Stored Procedure stage to call Oracle SP. In the data connection,
I'm able to pass the parameter for Data source and Username. However, I'm unable to pass the parameter for password as it accepts encrypted format.
Can you suggest the way to accept the parameter?
I'm using Stored Procedure stage to call Oracle SP. In the data connection,
I'm able to pass the parameter for Data source and Username. However, I'm unable to pass the parameter for password as it accepts encrypted format.
Can you suggest the way to accept the parameter?
Ajitha S
-
- Participant
- Posts: 75
- Joined: Mon Jul 12, 2010 4:11 am
- Location: Chennai
-
- Participant
- Posts: 75
- Joined: Mon Jul 12, 2010 4:11 am
- Location: Chennai
It could be as simple as a syntax error.
How are you typing in the Data source and user name? Do you just name the parameter -- parmDataSource -- or are you using the escape # -- #parmDataSource#?
I know that in other stages, you must use #, and in other stages you must not. Usually the difference is if you have an edit button for the text box.
How are you typing in the Data source and user name? Do you just name the parameter -- parmDataSource -- or are you using the escape # -- #parmDataSource#?
I know that in other stages, you must use #, and in other stages you must not. Usually the difference is if you have an edit button for the text box.
Franklin Evans
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
-
- Participant
- Posts: 75
- Joined: Mon Jul 12, 2010 4:11 am
- Location: Chennai
I believe it's that the password is encrypted, and not being converted back to text by the runtime engine. I defer to others who use the SP stage to comment further, because I've hit the extent of my experience with this.
Good luck.
Good luck.
Franklin Evans
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
this could be TOTALLY unrelated and off the wall, but let me describe a recent issue I was having...
I was having my password constantly rejected for a teradata system. My password was rather lengthy and about 50% special characters (standard USA keyboard punctuation, math, and similar stuff like !@#$%^&*() etc). What seems to have been happening is that I stumbled across some password that, when encrypted, generates datastage control characters, maybe #junk#, or something, I do not know exactly what, but it just would not work.
I changed my password on that database and the exact same code and such worked perfectly since.
So, all that to say, maybe change your password, if you think you are doing everything correctly?
I was having my password constantly rejected for a teradata system. My password was rather lengthy and about 50% special characters (standard USA keyboard punctuation, math, and similar stuff like !@#$%^&*() etc). What seems to have been happening is that I stumbled across some password that, when encrypted, generates datastage control characters, maybe #junk#, or something, I do not know exactly what, but it just would not work.
I changed my password on that database and the exact same code and such worked perfectly since.
So, all that to say, maybe change your password, if you think you are doing everything correctly?
I've experienced that as well. The software restricts a lot of special characters. There are documented here:
Naming restrictions for user IDs and passwords
Naming restrictions for user IDs and passwords
Choose a job you love, and you will never have to work a day in your life. - Confucius
We have also worked cases where the password that contains prohibited special characters works just fine when you click "View Data" on a Connector stage but the same password aborts the same job at run time. The password-handling code behind the "View Data" service provided by the services tier is different code than the run-time code in the engine tier. I have not worked with the Stored Procedure stage much but would, perhaps riskily, assume it would behave in a similar way.
Choose a job you love, and you will never have to work a day in your life. - Confucius
-
- Premium Member
- Posts: 145
- Joined: Thu Oct 26, 2017 10:43 am