My password was something like
athens#3
in the Oracle Enterprise stage. I used:
"athens#3" in the parameter set to prevent the error in my subject line above. This works but the job which was taking 15 seconds is taking 6 minutes. Any ideas?
Incorrect dboption list error
Moderators: chulett, rschirm, roy
Re: Incorrect dboption list error
Are you saying after using Parameterset the job is taking more time?
Thanks
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
No, this is an existing job. The parameter set was being used before as well. The problem is when the # sign was introduced in the password, the password had to be double quoted. The job works fine but the time taken is almost 25 times.
The parameter set is something like this:
ABC_PARM.DBUserID=my123
ABC_PARM.DBPassword="athens#3"
....
....
where ABC_PARM is the parameter set name. In the Oracle EE stage, the password is being set as: #ABC_PARM.DBPassword#
The parameter set is something like this:
ABC_PARM.DBUserID=my123
ABC_PARM.DBPassword="athens#3"
....
....
where ABC_PARM is the parameter set name. In the Oracle EE stage, the password is being set as: #ABC_PARM.DBPassword#
I really have a problem envisioning how the quoting password change can affect runtimes, since the password is passed only once to instantiate the connection. Is it possible to change the password back again to confirm that the job immediately runs faster?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>