Skip to main content

Run Unit tests using DBTest library

Sybase IQ columnar analytics database uses DBTest as Unit test library.
Following are the steps to use it:
$ cds
$ cd testlib
$ vi xyz.tst #Write the dbtest.
$ dbtest -y xyz.tst #Checks for syntax errors in the tst file.
$ vi my.bch #Enter in the first line "xyz.tst"
$ vi xyz.op #This is the output file whose contents are compared with the actual run-time output of the test.
$ cd ..
$ cmake debug64
$ cdp (test directory)
$ setup current debug64
$ run_saint_testlib.sh -port xxxx -newdbonerror my.bch #This run the tests

If test fails then
$ vi xyz.ot #Check out the errors.
$ vi xyz.tst #Correct the errors and rerun the test.

Use dbtest command to run your tests:
  1. On terminal 1, run commands:
    $ setenv IQTMP `pwd`
    $ setenv IQTMP15 `pwd`
    $ setenv ASTMP `pwd`
    $ runsrv abc abcd.db, OR $iqsrv15 -n abc abcd.db -zr all -gd all -gl all -c 32m -ch 200m -x "tcpip(port=xxxx)"
  2. On terminal 2, run commands:
    $ setenv IQTMP `pwd`
    $ setenv IQTMP15 `pwd`
    $ setenv ASTMP `pwd`
    dbtest -ds -m1 xyz.tst > xyz.ot
  3. To connect to an IQ database server, either set environmental variables or specify following command in .tst file:
    stringconnect "uid=dba;pwd=sql;eng=abc;links=tcpip{host=m/cName;port=xxxx}"

Comments

Popular posts from this blog

MPlayer subtitle font problem in Windows

While playing a video with subtitles in mplayer, I was getting the following problem: New_Face failed. Maybe the font path is wrong. Please supply the text font file (~/.mplayer/subfont.ttf). Solution is as follows: Right click on "My Computer". Select "Properties". Go to "Advanced" tab. Click on "Environment Variables". Delete "HOME" variable from User / System variables.

Kafka performance tuning

Performance Tuning of Kafka is critical when your cluster grow in size. Below are few points to consider to improve Kafka performance: Consumer group ID : Never use same exact consumer group ID for dozens of machines consuming from different topics. All of those commits will end up on the same exact partition of __consumer_offsets , hence the same broker, and this might in turn cause performance problems. Choose the consumer group ID to group_id+topic_name . Skewed : A broker is skewed if its number of partitions is greater that the average of partitions per broker on the given topic. Example: 2 brokers share 4 partitions, if one of them has 3 partitions, it is skewed (3 > 2). Try to make sure that none of the brokers is skewed. Spread : Brokers spread is the percentage of brokers in the cluster that has partitions for the given topic. Example: 3 brokers share a topic that has 2 partitions, so 66% of the brokers have partitions for this topic. Try to achieve 100% broker spread

wget and curl behind corporate proxy throws certificate is not trusted or certificate doesn't have a known issuer

If you try to run wget or curl in Ununtu/Debian behind corporate proxy, you might receive errors like: ERROR: The certificate of 'apertium.projectjj.com' is not trusted. ERROR: The certificate of 'apertium.projectjj.com' doesn't have a known issuer. wget https://apertium.projectjj.com/apt/apertium-packaging.public.gpg ERROR: cannot verify apertium.projectjj.com's certificate, issued by 'emailAddress=proxyteam@corporate.proxy.com,CN=diassl.corporate.proxy.com,OU=Division UK,O=Group name,L=Company,ST=GB,C=UK': Unable to locally verify the issuer's authority. To connect to apertium.projectjj.com insecurely, use `--no-check-certificate'. To solution is to install your company's CA certificate in Ubuntu. In Windows, open the first part of URL in your web browser. e.g. open https://apertium.projectjj.com in web browser. If you inspect the certifcate, you will see the same CN (diassl.corporate.proxy.com), as reported by the error above