Initialize Derby Database?
4 answers
Thanks Christophe.
I dropped the tables, and recreated them. Your answer helped immensley, but I was tripped up a little because the command is case sensitive (createTables).
One interesting thing you might want to look at is that although I have now initialized the database and it is empty... I can still log on with my old username. The user by the way is *not* listed as a user. I didn't need to log in as ADMIN at all. Seems like a bug somewhere, but I'm not sure where. I have bounced the server, but perhaps clearing the cache could help.
If this is required, it seems to be a bug and possible a security issue.
Thanks very much again
Jon
repotools -createtables
should do it (by dropping and recreating the tables and data)
--
Christophe Elek
Jazz L3
IBM Software Group - Rational
I dropped the tables, and recreated them. Your answer helped immensley, but I was tripped up a little because the command is case sensitive (createTables).
One interesting thing you might want to look at is that although I have now initialized the database and it is empty... I can still log on with my old username. The user by the way is *not* listed as a user. I didn't need to log in as ADMIN at all. Seems like a bug somewhere, but I'm not sure where. I have bounced the server, but perhaps clearing the cache could help.
If this is required, it seems to be a bug and possible a security issue.
Thanks very much again
Jon
jonm@uk.ibm-dot-com.no-spam.invalid (jonm) wrote in news:h5knn5$okn$1
@localhost.localdomain:
How do I do this?
repotools -createtables
should do it (by dropping and recreating the tables and data)
--
Christophe Elek
Jazz L3
IBM Software Group - Rational
jonm wrote:
If you're using Tomcat as the app server, your "user database" is held
in the text file tomcat-users.xml, not in Derby. You may need to
manually edit that file and clip out the users, or just copy in an
original version.
MK
One interesting thing you might want to look at is that although I
have now initialized the database and it is empty... I can still log
on with my old username. The user by the way is *not* listed as a
user. I didn't need to log in as ADMIN at all. Seems like a bug
somewhere, but I'm not sure where. I have bounced the server, but
perhaps clearing the cache could help.
If this is required, it seems to be a bug and possible a security
issue.
If you're using Tomcat as the app server, your "user database" is held
in the text file tomcat-users.xml, not in Derby. You may need to
manually edit that file and clip out the users, or just copy in an
original version.
MK
Genius
Thanks again
If you're using Tomcat as the app server, your "user database" is held
in the text file tomcat-users.xml, not in Derby. You may need to
manually edit that file and clip out the users, or just copy in an
original version.
MK
Thanks again
jonm wrote:
One interesting thing you might want to look at is that although I
have now initialized the database and it is empty... I can still log
on with my old username. The user by the way is *not* listed as a
user. I didn't need to log in as ADMIN at all. Seems like a bug
somewhere, but I'm not sure where. I have bounced the server, but
perhaps clearing the cache could help.
If this is required, it seems to be a bug and possible a security
issue.
If you're using Tomcat as the app server, your "user database" is held
in the text file tomcat-users.xml, not in Derby. You may need to
manually edit that file and clip out the users, or just copy in an
original version.
MK