Incorrect dboption list error

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
abc123
Premium Member
Premium Member
Posts: 605
Joined: Fri Aug 25, 2006 8:24 am

Incorrect dboption list error

Post by abc123 »

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?
SURA
Premium Member
Premium Member
Posts: 1229
Joined: Sat Jul 14, 2007 5:16 am
Location: Sydney

Re: Incorrect dboption list error

Post by SURA »

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.
abc123
Premium Member
Premium Member
Posts: 605
Joined: Fri Aug 25, 2006 8:24 am

Post by abc123 »

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#
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

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?
Post Reply