Jeremy,
I didn't personally experience the problem so I can't offer exact steps to reproduce it, but when I was trying to troubleshoot it, I checked the software versions they were using. They got AOLserver code using the following, not sure what the exact date would have been, but some time in the last month for sure:
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/aolserver login
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/aolserver co -r aolserver_v40_r2 aolserver
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/aolserver co nspostgres
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/aolserver co nscache
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/aolserver co nssha1
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/aolserver co nsoracle
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/aolserver co nsxml
And were running Oracle Client: 8.1.7.0,
Oracle Server: 8.1.7.4.1, tcl: 8.4.6. The failure occurs trying to insert data into a table with spec below:
SQL> desc apm_package_db_types;
Name Null? Type
----------------------------------------- -------- ----------------------------
DB_TYPE_KEY NOT NULL VARCHAR2(50)
PRETTY_DB_NAME NOT NULL VARCHAR2(200)
And the actual data in the table when installed successfully is:
SQL> select * from apm_package_db_types;
DB_TYPE_KEY
--------------------------------------------------
PRETTY_DB_NAME
--------------------------------------------------------------------------------
oracle
Oracle8
postgresql
PostgreSQL
Hopefully the stack trace above should give you other information you need to reproduce it.
HTH,
Tom