Restore BASDBTEST

vinsnash

Can BASDBTEST be deleted and replaced with a renamed copy of BASDB? Starting test mode with no initial data does not help. I can import the CSV file to BASDB but after starting test mode with no initial data and importing the same CSV file BASDBTEST is still corrupted.

Vins Nash

tford

Not sure, but one other possible solution is to narrow down which part of the CSV file is causing the issue. For example

1) Can you import 1 record from the CSV and it works OK?

2) If you have 1,000 records being imported, try imported 1/2 of them.

3) Using this "cutting the difference in half" logic, you can rather quickly narrow down which record is the issue.

Are you sure your logs are not throwing off any errors during the import process?

vinsnash

There is nothing in the log other than a number of "data exceeds" warnings which is giving me truncated "notes" in some instances which is expected and OK.

I imported the 1st 6 records only and they all show in the "admin" user "Search Objects" query. Clicking he "Edit" icon on each produces the "Conglomeration" error. I don't think it's going to narrow down to one record of 17K +.

The error message is pretty specific.

"Internal error. The conglomerate (8,769) requested does not exist"

That number doesn't change no matter the instance. This is the supplied AwareIM default data base. I've even seen support replies stating there is no advantage to switching to MYSQL. Someone in support must know or be able to find out just what the error is about and how to correct it.

I've imported the exact same .csv into the BASDB without any problems.

I've started the test mode with no initial data and imported several times without resolving the error.

I've tried using a backup from a month ago, but now that I've installed 5.1 with a new product key the backups all report "Expired or Invalid Product Key".

Isn't there someway to just "kill" BASDBTEST and reestablish it or are they both intertwined somehow?

Once we roll this application out I'm going to want to use the current live data in the test mode data base. Is that going to involve export/import on all the objects? I'm sure the powers that be here won't accept QA on a sample data base.

Vins Nash

aware_support

Try this:

Create a backup of your DATA directory just in case
Delete the file DATA/derby.log
If this doesn't help install the evaluation version of Aware IM in a separate directory and copy DATA/BASDBTEST folder from that installation into the corresponding folder of your production version

vinsnash

Support,

Steps 1 & 2 had no affect.

I proceeded with step 3. Initiated test mode with no initial data. Now there is no way to log on to the test mod. "admin"'/"password" does not work nor does my previous ID/Password.

Vins Nash

tford

Are you able to log into AwareIM in test mode in the separate directory created in #3?

vinsnash

In a word, no. The original "admin" ID and "password" password don't work and neither dose the log on ID and password I created for the "admin" access level.

I would've thought that BASDBTEST from the evaluation versions would honor "admin" and "password". Evidently those must be stored elsewhere.

Vins Nash

vinsnash

Additionally, since there was an AwareIM evaluation installed previously, a year or more ago, the newest evaluation won't start the server because of expired time.

I believe I would be able to log on to the evaluation but I'd have to delete all references of the previous evaluation installation including those in the registry and reinstall it.

Still, I'm puzzled. Is it Derby throwing that error, the server, what? I can't believe there's a "whoops! There's something wrong. We don't know what or what caused it or even where the error message comes from or what the error message means" situation. My best guess is that there is some fatal malfunction in the Derby AwareIM interface.

Not very encouraging. BASDBTEST sat unused for approximately 30 days while we did a beta test on the production BASDB. The test was very successful and we were presented with several very useful end user suggestions. I created a new Major Version, put it in test mode, imported some data and was just testing the imported data when the error occurred.

Vins

tford

If you Google the error message you are receiving, you will find it's a Derby message.

I'm guessing you will have to purchase a support ticket to sort this out.