Special Characters in Oracle password

[roblew]

Hello,

I'm getting this error when using the Oracle Enterprise Stage and using an Oracle password with special characters.

Oracle_Enterprise_1: Incorrect dboption list; it failed on Expected "," or "}", got: "$", line 1.


We're on DS EE 7.5.1A on RHEL AS 3.0. We're connecting to multiple Oracle sources, but I tested with v9205.

The error comes up when doing "view data" and also when running the job. It does not matter if we use job parameter or not. The special character is part of a security profile requirement. Has anyone experienced this same issue?

note: I just tested the same method in Server job, and it works successfully.

Thanks,
Rob

[roy]

Hi,
Doy you have the $DS_ENABLE_RESERVED_CHAR_CONVERT variable set to True in your job?

[roblew]

Doy you have the $DS_ENABLE_RESERVED_CHAR_CONVERT variable set to True in your job?

I did not have it set initially, but I just tested the job with the variable set in project and in job, and it returned the same error.

I received the following from IBM support. I'm waiting to hear back from them.

"I found Ecase 84857 that has fixed the password with the special characters.
But the patch is build for AIX platform, I will need to request the patch for Linux OS."

[djoni]

Try enclosing your Oracle password with single quotes, such as 'pass$word'

Hello,

I'm getting this error when using the Oracle Enterprise Stage and using an Oracle password with special characters.

Oracle_Enterprise_1: Incorrect dboption list; it failed on Expected "," or "}", got: "$", line 1.


We're on DS EE 7.5.1A on RHEL AS 3.0. We're connecting to multiple Oracle sources, but I tested with v9205.

The error comes up when doing "view data" and also when running the job. It does not matter if we use job parameter or not. The special character is part of a security profile requirement. Has anyone experienced this same issue?

note: I just tested the same method in Server job, and it works successfully.

Thanks,
Rob

[roblew]

Try enclosing your Oracle password with single quotes, such as 'pass$word'

nope. No luck with that either.

[roblew]

FYI, we received a patch for this some time ago. Here's the info.


PATCH REPORT FOR ECASE: 84857
PRODUCT: DSEE
VERSION: 751A

PROBLEM REPORTED:
Cannot use '#' or '$' in Oracle passwords
CAUSE OF PROBLEM:

FIX SUMMARY:
Fixed so that oraupsert, oraread, and orchdbutil will work with '#' or '$' in password.

USER INTERFACE FIX:

PRE-REQUISITE PATCHES REQUIRED
None

COMPETING PATCHES:

EXPECTED RESULTS OF PATCH:
Jobs created using the DS Client will have to have user specified database options for
oraread, orawrite, and oraupsert to work correctly with this fix. The password must
be enclosed in "" if it contains a '$' or '#' byte when it is specified in the client GUI.
When orchdbutil is run from the command line the password on the command line must also
be enclosed in "". This fix will only work for jobs run with command files, such as:

osh -f OshCommandFile

It will not work for osh commands run from the command line:

osh "operator arguments, etc., etc."

SYSTEM REQUIREMENTS (OS LEVEL, COMPILER VERSION):
This patch is supported on LINUX platforms currently supported
by DataStage 751A

PATCH APPLICATION PROCEDURE
Apply the patch by executing the following instructions.

PATCHED FILES:
The following files contain the fixes for this ecase:
db2esql.bnd liborchi686.so liborchsasop8i686.so
liborchbuildopi686.so liborchmonitori686.so liborchsasop9i686.so
liborchcommondbi686.so liborchoracle10gi686.so liborchsorti686.so
liborchcorei686.so liborchoracle9ii686.so liborchstatsi686.so
liborchdb2op8i686.so liborchosli686.so
liborchgenerali686.so liborchsasop612i686.so osh

TARGET DIRECTORY:
The following directories are where the patched files will
be copied:
<unixhost>:$APT_ORCHHOME/PXEngine/lib
<unixhost>:$APT_ORCHHOME/PXEngine/bin

INSTALLATION:

PX INSTALL:
1. Ensure that no jobs utilizing the PX Engine are running.
These are any jobs developed utilizing the parallel canvas.

2. Make sure that your $APT_ORCHHOME is set properly.

3. Uncompress and un-tar the patch file provided.

4. cd into the patch directory (patch_84857) and
run the patch_install.sh script:
patch_install.sh .
This script will backup the old libraries and install the
new ones.

5. If for any reason, the script does not run to the end
successfully, do not rerun it again before you manually
make a copy of the backed up original libraries, for example:
mv $DSHOME/../../patches/patch_84857
$DSHOME/../../patches/patch_84857.bak

PATCH DELETION PROCEDURE

TO REMOVE THE PATCH, REPLACE THE PATCHED FILES WITH THE
ORIGINAL FILES. IF YOU USED THE PATCH INSTALL SCRIPT
TO INSTALL THE PATCH, THESE FILES WERE BACKED UP BEFORE
THE PATCH WAS APPLIED.

1. Ensure that no jobs utilizing the PX Engine are running.
These are any jobs developed utilizing the parallel canvas.

2. Replace original files. Backup files should have been
made before installing the initial patch.

FOR EXAMPLE:
* cd $APT_ORCHHOME/PXEngine/lib
* Remove the patched files:
rm liborchcorei686.so (patched file)
* Restore the original file:
cp $DSHOME/../../patches/patch_83370/files_backup/DataStage/
PXEngine/lib/liborchcorei686.so .

[roblew]

By the way, you will still need to enclose the password in double quotes after the patch is applied! Also, the patch required both server and client side patches.

[kumar_s]

Its always good to update the post with resolution. And so don't you wish to mark the post as resolved?

[roblew]

Its always good to update the post with resolution. And so don't you wish to mark the post as resolved?

ah, gotcha. I actually didn't know we could do that.

[prasad111]

Just updating.......

Version 7.5 - Need to install patches
Version 8.0 - Need to pass it with escape characters [For example: sea$$wgyc has to be passed as "sea\$\$wgyc" (double quotes has to be present)]