Occassionally one or more tables in the database becomes corrupt. Fixing it is usually simple. Always be sure to make periodic backups of your database, just in case these tools do not work.

To test your database for corruption, issue the following command. You can include a table name at the end to just check a specific table, if desired:

mysqlcheck -u {USERNAME} {DATABASE} [TABLE]

Example:

C:\mysql5.0.45\bin>mysqlcheck -u root bytesphere alerts
bytesphere.alerts
warning  : 19 clients are using or haven't closed the table properly
error    : Found key at page 339968 that points to record outside datafile
error    : Corrupt

To fix it, make sure the system is shut down and not connected to it, then issue the following command including the -r switch to repair:

mysqlcheck -r -u {USERNAME} {DATABASE} [TABLE]

Example:

C:\mysql5.0.45\bin>mysqlcheck -r -u root bytesphere alerts

bytesphere.alerts                                  OK

Here we see that the mysql tool has fixed the alerts table. Now you can start up your application and attend to business as usual.

How To, JaguarSX corruption, database, How To

This post is password protected. To view it please enter your password below:

Password:

How To, JaguarSX debugging, JaguarSX

OidView needs to activated to be completely licensed and work properly. To activate OidView, follow these steps:

1. Get the HARDWARE-ID

The HARDWARE-ID (also called the HARDWARE Fingerprint by the licensing system).

e.g.: ABCD-1234

It is NOT a MAC-ADDRESS. It is a unique one-way hash that is generated for your computer. It changes if you upgrade the OS, install a new disk drive, or install some major piece of hardware in your computer. Don’t worry, if it changes, you can “transfer” your OLD license and HARDWARE-ID to a new computer (or the same computer) with a different HARDWARE-ID.

The HARDWARE-ID can be obtained by:

a) In OidView, click Help -> Show HARDWARE-ID.

b) From the Command Line (in the OidView directory), type OIDVIEW REGISTER

2) Get your ORDER#

This is provided to you when you purchase the product. The ORDER# is a long number, sometimes with a dash and more numbers. Rarely is it a set of words or other characters.

e.g.: 103539845-1

3) Submit License Request

Simply go to the following URL with the HARDWARE-ID and the ORDER# and submit your request using your email address.

licenses:    http://www.oidview.com/key-request-main.html

Please note for license transfers and upgrades you will need the original HARDWARE-ID and the new HARDWARE-ID, and you will need to use a different url:

transfers:   http://www.oidview.com/key-request-txfr.html

upgrades:  http://www.oidview.com/key-request-upgrade.html

4) Check your email

There should be 2 emails arriving in your inbox within the next minute or so. One email will have the activation information on it, and the other should have both the activation information and the license keys themselves, as attachments. If you only receive ONE email, then you need to go to step 3 again, and either enter a different email address or uncheck the option “Send Key in Zip File”, as some mail servers block emails with certain attachments.

Inside the email you will have two lines specifying the USER and CODE. The USER should be your email address, the CODE should be a very long code of many characters and numbers (it may be longer than the example show here), e.g.:

USER  : webmaster@mycompany.com

CODE  : 000017-F30Q9V-XPZK44-Y3UC42-VX52UJ-KEP2C2-34WGYN-319V1K

5) Copy the license keys into the OidView directory

Usually they are named license.key and license.tms.key. These are NOT registry keys, do not try to enter them into the registry. They are encrypted binary files.

If there was a ZIP file, extract the 2 or more keys into the top-level OidView directory (usually Program Files\OidView). Otherwise, just save the attachments into this directory.

6) Activate OidView

Start OidView or type OIDVIEW REGISTER from the command line prompt. It will ask you for the USER and CODE. Here you will enter the USER and CODE you were given in the email.

Now, simply click the OK button and you should receive a message stating the key has been stored.

How To, OidView activation, hardware-id, licensing, OidView

An environment variable is a setting for the WIndows Operating system that tells it (or certain programs) to behave in certain ways. Changing these environment variables are fairly simple. There are two types of environment variables, SYSTEM, and USER. If you change a USER variable you most likely will only have to restart the application you are working with. If you change a SYSTEM variable, then the computer will need to be restarted in order for the new setting to take effect.

This varies based on the version of windows you are using.

For all versions of windows except Windows Vista

http://support.microsoft.com/kb/310519

For windows Vista

Go to: Control Panel\System and Maintenance\System. Click “Advanced System Settings”. Click Environment variables button, at bottom.

 

How To environment, variables, windows

Sometimes we will need to get a log file to determine what is going on with Trap Manager. Since this is a windows application, we will need to modify a windows environment variable in order to activate the debugging process. To learn how to create environment variables, please see the “How To” post for environment variables or http://support.microsoft.com/kb/310519

1. Create the following environment variables

In the Environment variables section, create the following SYSTEM variables with the following values:

  BS_DEBUG=ON

  BS_DEBUG_MODULES=1

Remember with Trap Manager you must create SYSTEM variables, not USER because the Trap Manager process runs as a windows service and assumes the system role.

2. Restart the Computer

Remember with Trap Manager that you must restart the computer, so when the service restarts it will be able to come up in debug mode. Only then does it take effect. Now, make the problem happen. At this point, a log should have been created in the OidView main directory, named trapmanager.debug.log.

3. Turn off debugging

To turn off debugging, simply remove the variables that you created or set the values to OFF and 0, respectively.

  BS_DEBUG=OFF

  BS_DEBUG_MODULES=0

How To, OidView, Trap Manager debugging, logging, OidView, Trap Manager