nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Standalone DataDeploy fails after upgrade to OpenDeploy 7.1

tanguyr

Hello,

We recently upgraded our OpenDeploy servers from 6.2 to 7.1

Since then a standalone datadeploy job that we were using to insert xml files into a number of oracle db tables has stopped working. When i look at the logs for the deployment, i see the error message:


*******************************************************
DBD: SQLException occured in JdbcCheckup:MakeConnection()
DBD: Exception Message: Null user or password not supported in THIN driver
DBD: Vendor Error Code: 17443
DBD: SQL state: null
DBD: *******************************************************

I've checked the following:
1) The hostname, username, password, etc info in the $OD_HOME/etc/database.xml file is correct. I can use them in a little standalone java class to connect to the database from the same host where OD is running
2) Datadeploy is reading this file: if i change the path to this file in the deployment configuration, i get a different error basically saying "can't find the file". Likewise if i change the name of the database in this file i get an error saying that the deployment can't find the specified database
3) I tried regenerating a new OD license, it doesn't make any difference.
4) I checked the odbase.xml file (it hasn't changed since 6.2) - the databaseDeployment element is uncommented, the daemon port is correct, and it has a standalone enabled="yes" subelement

I still have access to an environment where everything is the same EXCEPT it still has OD 6.2 installed, and there the same datadeploy deployment works as expected, so i'm fairly confident that the problem is 7.1 related.

Has anyone here seen this kind of error when performing a standalone datadeployment before?

Thanks,
/t

Find more posts tagged with

Comments

srosewall

Don't know, but JDBC Drivers perhaps?

tanguyr

Don't know, but JDBC Drivers perhaps?

Hey there Stuart, how are things?

As far as I can see, drivers are unmodified by the OD7.1 upgrade (the jars are in the same place with the same md5 and there are no new ones). Furthermore, the error seems to be reported by the driver (complaining that it was passed a null username or password) so I'm guessing this is more likely to be a configuration issue.

/t

srosewall

Hey there Stuart, how are things?

Pretty good thanks; apart from being in Belgium at the moment! Smiley Wink

You keeping busy?

As far as I can see, drivers are unmodified by the OD7.1 upgrade (the jars are in the same place with the same md5 and there are no new ones). Furthermore, the error seems to be reported by the driver (complaining that it was passed a null username or password) so I'm guessing this is more likely to be a configuration issue.

How about the format of the name / password - any special characters?
(probably not, but just in case as I've seen authentication fail because of that before...)

tanguyr

Pretty good thanks; apart from being in Belgium at the moment!
You keeping busy?

Just in time for the winter rain and darkness... I'm actually moving away from WCMS tasks for a while after i finish this one last thing, and it looks like OD knows it too Smiley Wink

How about the format of the name / password - any special characters?
(probably not, but just in case as I've seen authentication fail because of that before...)

Without getting into too many details Smiley Wink

, nope... all standard stuff, and again the very same info works on the QA server which is still in 6.2...

Even worse is that, if this were the issue, i'd be screwed as production generates passwords that look like snoopy swearing

tanguyr

Just to say that IWOV support's first idea is tha same as yours: it's a driver issue. I've tried using fresh ojdbc5 and ojdbc6 drivers from oracle, along with the matching orai18n.jar (replaces nls_charset12.zip) - all it does is change the error message from

DBD: Exception Message: Null user or password not supported in THIN driver
to
DBD: Exception Message: ORA-01005: null password given; logon denied

RonaldV

See this thread for a "undocumented" feature that will solve your problem:

http://devnet.interwoven.com/forums_vb/showthread.php?t=32014&forumid=12

mart2001

Is your db password encrypted? Starting in OD 7.1, your db password need to be encrypted in order for DataDeploy to work.

Adam Stoller

Is your db password encrypted? Starting in OD 7.1, your db password need to be encrypted in order for DataDeploy to work.

needs to be - or can be?
I believe there is a directive in the database.xml that indicates whether or not the password is encrypted - I believe the default is "no". So you can either use encrypted password and specify that they are such, or use un-encrypted passwords and either specify them as such or not make any specification - which should be the same thing.

tanguyr

RonaldV, Thanks **sooooo** much, this (in database.xml: adding password-encoded="yes" and then encoding the password with iwodpasscoder) has indeed fixed my problem!