Thanks guyprzytula, I already have updated the license of DB2 last October 2006, as shown below, but I'm quite curiuos with the result of License type: which is "Unwarranted", is this a big deal? because as stated in my first post, the JDBC driver Expired last December 30, 2006(after two months). My main concern really is, does the JDBC driver expires? or is it because I did not fire the db2iupdt <instancename> after i updated the license?
[root@ccs bin]# db2licm -l
Product name: "DB2 Express Edition"
License type: "Unwarranted"
Expiry date: "Permanent"
Product identifier: "db2exp"
Version information: "9.1"
Max number of CPUs: "2"
Max amount of memory (GB): "4"
Annotation: "6;
But anyway, I fired the db2iupdt command and the result is shown below.
[root@ccs instance]# ./db2iupdt db2inst1
DBI1766W Cannot change the secondary group list of
db2inst1.
Explanation:
A code, 127, is returned when attempting to change the
secondary group list of the given user ID. One of the following
situations has occurred:
o NIS is running.
o One or more processes are currently being executed under the
given user ID.
User Response:
You must add the group ID, dasadm1, to the secondary group
list of the user ID, db2inst1, so that the Adminstration Server
can function properly.
o If there happens to be any process run under the given user
ID, terminate all of these processes and follow the
instructions above to setup the secondary group list of this
user ID.
o If you are running this command on an NIS client, try the
above instructions to setup the secondary group list of this
user ID on your NIS server.
DBI1070I Program db2iupdt completed successfully.
I tried to log-in in my application again and still the error:Expired JDBC driver appeared in the logfile.
dBforums
>
Expired JDBC driver
01-21-07, 23:36
Linear Mode
