Database Test Suite

On Sat, Mar 13, 2010 at 6:01 PM, Megha <megha1983us@...> wrote:
> Hi
>
> I have installed Postgresql in /usr/local/pgsql.
> DBT2 is installed in /home/megha/dbt2 directory.
> And source code of the DBT2 is in /home/megha/tmp/dbt2-0.40/ directory.
>
> Now I use this command to start postgresql
> "$ /usr/local/pgsql/bin/pg_ctl -h localhost -D /home/megha/dbt2/pgdata -l
> logfile start"
>
> Then I use "$ scripts/run_workload.sh -d 300 -w 1 -c 1 " to work with
> database.
> I get this error:
>  "server starting
> database did not start correctly, check database log ":
>
>
> Log
>
> LOG:  could not bind IPv4 socket: Address already in use
> HINT:  Is another postmaster already running on port 5432? If not, wait a
> few seconds and retry.
> WARNING:  could not create listen socket for "localhost"
> FATAL:  could not create any TCP/IP sockets
> LOG:  could not bind IPv4 socket: Address already in use
> HINT:  Is another postmaster already running on port 5432? If not, wait a
> few seconds and retry.
> WARNING:  could not create listen socket for "localhost"
>
> ..Can some one help me with this??

Hi Megha,

The dbt2 scripts should take care of starting and stopping the
database for you.  This looks like a setup error though.  What the
dbt2 scripts is trying to stop/start is not the same PGDATA as what
you started by hand.  I don't recall exactly how v0.40 of the kit sets
the PGDATA directory.  I believe it's set in the
sripts/pgsql/pgsql_profile file.  There should be a note of that in
the README-POSTGRESQL file.

Regards,
Mark

On Tue, Mar 16, 2010 at 6:52 PM, Megha <megha1983us@...> wrote:
> Hi Mark,
>
>  I build the database according to README. "build_db.sh -g -w 1"
> then I run the workload "run_workload.sh -d 300 -w 1"
>
> I check the error.log in output/9/Client folder. I am getting these errors.
> I run 9 test . I am getting same kind of error in all of them.
>
> Is this installation error?
> Which other error.log should I need to check?
> Please Help..
>
>
> Tue Mar 16 21:12:36 2010
> tid:-1216784704 client.c:129
> 2 DB worker threads have started
> Tue Mar 16 21:12:39 2010
> tid:-1229374608 libpq/dbc_stock_level.c:36
> ERROR:  function stock_level(integer, integer, integer) does not exist
> LINE 1: SELECT stock_level(1, 1, 20)
>                ^
> HINT:  No function matches the given name and argument types. You might need
> to add explicit type casts.
>
> Tue Mar 16 21:12:43 2010
> tid:-1227277456 libpq/dbc_payment.c:37
> SELECT payment(1, 10, 0, 1, 10, 'OUGHTESEPRI', 1036.870000)
> ERROR:  function payment(integer, integer, integer, integer, integer,
> unknown, numeric) does not exist
> LINE 1: SELECT payment(1, 10, 0, 1, 10, 'OUGHTESEPRI', 1036.870000)
>                ^
> HINT:  No function matches the given name and argument types. You might need
> to add explicit type casts.
>
> Tue Mar 16 21:12:47 2010
> tid:-1229374608 libpq/dbc_payment.c:37
> "error.log" 499L, 25450C
>
>
>
> Thanks,
>
<snip>
>
>
>
> --
> Megha
>

My guess is that that stored functions weren't built before running
the load_db.sh script because they weren't found.  That script should
have loaded them.  Can you confirm?

Regards,
Mark

On Sat, Mar 20, 2010 at 12:43 PM, Megha <megha1983us@...> wrote:
> Hi Mark,
>
> I checked the dbt2-0.40/src folder. It contains all these .o files.
>
> [megha@... src]$ ls
> client                         driver-_semaphore.o
> client.c                       driver-_socket.o
> client-client_interface.o      driver-transaction_data.o
> client-client.o                include
> client-common.o                input_data_generator.c
> client-dbc_common.o            libpq
> client-dbc_delivery.o          listener.c
> client-dbc_integrity.o         logging.c
> client-dbc_new_order.o         Makefile
> client-dbc_order_status.o      Makefile.am
> client-dbc_payment.o           Makefile.in
> client-dbc_stock_level.o       mysql
> client-db.o                    nonsp
> client-db_threadpool.o         odbc
> client_interface.c             _semaphore.c
> client-listener.o              _socket.c
> client-logging.o               transaction_data.c
> client-_semaphore.o            transaction_queue.c
> client-_socket.o               transaction_test
> client-transaction_data.o      transaction_test.c
> client-transaction_queue.o     transaction_test-client_interface.o
> common.c                       transaction_test-common.o
> common.o                       transaction_test-dbc_common.o
> datagen                        transaction_test-dbc_delivery.o
> datagen.c                      transaction_test-dbc_integrity.o
> datagen.o                      transaction_test-dbc_new_order.o
> db.c                           transaction_test-dbc_order_status.o
> db_threadpool.c                transaction_test-dbc_payment.o
> driver                         transaction_test-dbc_stock_level.o
> driver.c                       transaction_test-db.o
> driver-client_interface.o      transaction_test-input_data_generator.o
> driver-common.o                transaction_test-logging.o
> driver-driver_main.o           transaction_test-_semaphore.o
> driver-driver.o                transaction_test-_socket.o
> driver-input_data_generator.o  transaction_test-transaction_data.o
> driver-logging.o               transaction_test-transaction_test.o
> driver_main.c
>
> odbc: folder contains .c function
>
> $ cd odbc
> [megha@... odbc]$ ls
> dbc_common.c    dbc_integrity.c  dbc_order_status.c  dbc_stock_level.c
> dbc_delivery.c  dbc_new_order.c  dbc_payment.c
>
>
> is this what you wanted to confirm?
<snip>
>
>
>
> --
> Megha
>

Not quite.  What I meant specifically if asking the database if what
stored functions are loaded.  There is a shortcut command using psql:
\df

Also, the code for the stored functions are in the storedprocs directory.

Regards,
Mark