From: Mary E. M. <mar...@os...> - 2003-10-29 15:46:00
|
Mark, does she need to create links from /tmp/*.data to where she wants the data to go before she runs the datagen program, or does datagen create it for her to point to output_dir? > Oops, I must have forgotten to mention the step were you run the data > generator. It's in datagen/datagen. > > datagen -w <number of warehouses> -d output_dir --pgsql > > Mark > > On Tue, Oct 28, 2003 at 06:26:44PM -0800, Mingming Cao wrote: >> On Tue, 2003-10-21 at 10:18, ma...@os... wrote: >> > Hi Mingming, >> > >> > Looks like I only updated the document with the TPC deviations. >> Building the kit is more or less the same. Just make sure you do a >> 'configure --with-postgresql' and a 'make' (instead of a 'make >> standlone'). There's a README-POSTGRESQL file that points out some >> other notes. To build the database run scripts/pgsql/create_db.sh >> and scripts/pgsql/load_db.sh. The script I've been using to run >> against postgresql is >> > scripts/run_workload.sh. >> > >> Hi Mark, >> >> After run the scripts/pgsql/create_db.sh, the pgsql/load_db.sh failed >> to load the database. It seems to me that the tables were created(I >> wonder where...), but fail to load them from /tmp/*data. >> >> Are these /tmp/*data file the primiray database files for dbt2 test? >> If so,is the location configurable? ( I would like to put the dbt2 >> database somewhere else). >> >> Any clue? >> [postgres@elm3b98 pgsql]$ ./load_db.sh >> psql:create_tables.sql:1: NOTICE: CREATE TABLE / PRIMARY KEY will >> create implicit index 'pk_warehouse' for table 'warehouse' >> CREATE TABLE >> psql:create_tables.sql:3: NOTICE: CREATE TABLE / PRIMARY KEY will >> create implicit index 'pk_district' for table 'district' >> CREATE TABLE >> psql:create_tables.sql:5: NOTICE: CREATE TABLE / PRIMARY KEY will >> create implicit index 'pk_customer' for table 'customer' >> CREATE TABLE >> CREATE TABLE >> psql:create_tables.sql:9: NOTICE: CREATE TABLE / PRIMARY KEY will >> create implicit index 'pk_new_order' for table 'new_order' >> CREATE TABLE >> psql:create_tables.sql:11: NOTICE: CREATE TABLE / PRIMARY KEY will >> create implicit index 'pk_orders' for table 'orders' >> CREATE TABLE >> psql:create_tables.sql:13: NOTICE: CREATE TABLE / PRIMARY KEY will >> create implicit index 'pk_order_line' for table 'order_line' >> CREATE TABLE >> psql:create_tables.sql:15: NOTICE: CREATE TABLE / PRIMARY KEY will >> create implicit index 'pk_item' for table 'item' >> CREATE TABLE >> psql:create_tables.sql:17: NOTICE: CREATE TABLE / PRIMARY KEY will >> create implicit index 'pk_stock' for table 'stock' >> CREATE TABLE >> psql:create_tables.sql:19: WARNING: COMMIT: no transaction in >> progress COMMIT >> Loading customer table... >> ERROR: COPY command, running in backend with effective uid 505, could >> not open file '/tmp/customer.data' for reading. Errno = No such file >> or directory (2). >> Loading district table... >> ERROR: COPY command, running in backend with effective uid 505, could >> not open file '/tmp/district.data' for reading. Errno = No such file >> or directory (2). >> Loading history table... >> ERROR: COPY command, running in backend with effective uid 505, could >> not open file '/tmp/history.data' for reading. Errno = No such file >> or directory (2). >> Loading item table... >> ERROR: COPY command, running in backend with effective uid 505, could >> not open file '/tmp/item.data' for reading. Errno = No such file or >> directory (2). >> Loading new_order table... >> ERROR: COPY command, running in backend with effective uid 505, could >> not open file '/tmp/new_order.data' for reading. Errno = No such file >> or directory (2). >> Loading order_line table... >> ERROR: COPY command, running in backend with effective uid 505, could >> not open file '/tmp/order_line.data' for reading. Errno = No such >> file or directory (2). >> Loading orders table... >> ERROR: COPY command, running in backend with effective uid 505, could >> not open file '/tmp/order.data' for reading. Errno = No such file or >> directory (2). >> Loading stock table... >> ERROR: COPY command, running in backend with effective uid 505, could >> not open file '/tmp/stock.data' for reading. Errno = No such file or >> directory (2). >> Loading warehouse table... >> ERROR: COPY command, running in backend with effective uid 505, could >> not open file '/tmp/warehouse.data' for reading. Errno = No such file >> or directory (2). >> CREATE INDEX >> CREATE INDEX >> CREATE FUNCTION >> psql:/mnt/mnt100/dbt2/storedproc/pgsql/c/new_order.sql:7: ERROR: >> functions cannot have more than 32 arguments >> CREATE FUNCTION >> CREATE FUNCTION >> CREATE FUNCTION >> VACUUM >> ANALYZE >> >> >> > Let me know if that helps. >> > >> > Mark >> > >> > On 21 Oct, Mingming Cao wrote: >> > > Hi Mark, >> > > >> > > I am looking for the document about how to set up the dbt2 tests >> on PostgreSQL. The documents included in the docs directory in >> the kit seem to cover SAP DB only. Same as the documents on the >> project website. What should I know for the PostgreSQL >> installation and configuration? Is there any document for dbt2 on >> PostgreSQL? >> > > >> > > >> > > Thanks! >> > > >> > > Mingming > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > osdldbt-general mailing list > osd...@li... > https://lists.sourceforge.net/lists/listinfo/osdldbt-general |