I have written my own IDM driver using the Skeleton as a base. The driver
has worked fine in my development lab. I have just tried to move it to my
test lab and the driver will not start and produces the following error:
Message: Code(-9005) The driver returned a "fatal" status indicating that
the driver should be shut down. Detail from driver:
<description>Single-valued, non-structured parameters should consist of at
most one element. Parameter tagName='option-1' consists of 7
elements.</description>
If anyone has any ideas what the problem is a quick response would be
appreciated.
The full output of the XML from the trace screen is below.
Many Thanks
Tom
Status: Fatal
Message: Code(-9005) The driver returned a "fatal" status indicating that
the driver should be shut down. Detail from driver:
<description>Single-valued, non-structured parameters should consist of at
most one element. Parameter tagName='option-1' consists of 7
elements.</description>
<document xml:space="preserve"><nds dtdversion="3.0" ndsversion="8.x">
<source>
<product version="3.0.10.20060630 ">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<init-params src-dn="CDSCOMPResourcesIDMDriverSetTOMS DRIVER">
<authentication-info>
<server>10.10.0.114:2099</server>
<user>Admin</user>
<password>
<!--content suppressed-->
</password>
</authentication-info>
<driver-options>
<option-1 display-name="JDBC Driver Class
Name">oracle.jdbc.driver.OracleDriver</option-1>
<option-2 display-name="JDBC
URL">jdbc:oracle:thin:@10.10.0.114:1521:TOM</option-2>
<option-3 display-name="Database Schema Name">TEST</option-3>
<option-4 display-name="Database Username">idmcode</option-4>
<option-5 display-name="Database Password">myPassword</option-5>
<option-6 display-name="SMTP IP Address">10.0.0.6</option-6>
<option-7 display-name="Helpdesk Email
Address">tom.b...@ansplc.com</option-7>
<option-8 display-name="Email Footer Text">This is an automated
email. Please do not reply.</option-8>
<option-9 display-name="SMTP Email From
Address">tom.b...@ansplc.com</option-9>
<option-10 display-name="Report
URL">http://www.ansplc.com?id=</option-10>
<option-11 display-name="LDAP IP Address">10.200.0.150</option-11>
<option-12 display-name="LDAP Port">389</option-12>
<option-13 display-name="LDAP Admin User
DN">cn=admin,ou=Resources,o=COMP</option-13>
<option-14 display-name="LDAP Admin User
Password">myPassword</option-14>
<option-15 display-name="Group DN">o=Groups</option-15>
</driver-options>
</init-params>
</input>
</nds></document>
I gave the options in the XML meaningful names then changed the code in
the DriverShim to pick up the values from the new names.
Very strange one. I haven't added any code to the base driver to only look
for the first few characters and like you say it seems strange why it
works in dev lab but not test lab.
Anyway it seems to be working now so thanks.
Shon Vella wrote:
> Just a wild guess - it may be that whatever is doing the parsing of
> options is doing some sort of starts-with kind of comparison or only
> looking at the first 8 characters. Either of those would cause
> considering option-1 to be equal to options 10 thru 15, which could then
> cause it to think that there were 7 option-1 's. It would probably be a
> good thing to give your options meaningful names anyway.
> Haven't a clue why it might work in your development lab and not in the
> test lab unless they aren't running the same code.
> --
> Shon
Haven't a clue why it might work in your development lab and not in the
test lab unless they aren't running the same code.
--
Shon