From: Evgeniy Z. <eig...@nm...> - 2003-07-11 12:17:04
|
Hello Jenny, Tuesday, July 8, 2003, 12:20:32 AM, you wrote: Thanx, test successfully has maked. I do not know, in what there was a mistake as "export ..FLAGS " I did up before configure. But I did not start autoconf as it it was not specified in the documentation. Nevertheless, after installation RedHat Linux 9.0 with default kernel (2.4.20), sapdb 7.3.0.25-1 from rpm's. dbt1 from dbt1-v1.2.tar.gz complite the steps described by you, dbt1 successfully has maked. But I have another problem. I first need to start test on machine with 2x 2.4 Ghz Xeon (with HT), 2Gb RAM and 70Gb raid5 hdd space. After studying the documentation, I have established amount of item=10000 and amount of user=1000 (these are values by default, if all correctly I understand). I enter export SID1=DBT1 export SID=DBT1 export PATH=$PATH':/opt/sapdb/depend/bin:/opt/sapdb/indep_prog/bin' in system environment. and also added "/opt/sapdb/interfaces/odbc/lib" in /etc/ld.so.conf I put .odbc.ini [dbt1] ServerDB = DBT1 ServerNode = 10.0.0.5 Driver = /opt/sapdb/interfaces/odbc/lib/libsqlod.so into home dir of sapdb user (with this user all scripts executed) Also I edited create_db.sh param_adddevspace 1 SYS /home/sapdb/dbt1/tmp2/DBT1_SYS_001 F param_adddevspace 1 DATA /home/sapdb/dbt1/tmp2/DBT1_DATA_001 F 524228 param_adddevspace 1 LOG /home/sapdb/dbt1/tmp2/DBT1_LOG_001 F 8192 set_param.sh: param_rmfile param_startsession param_init param_put LOG_MODE DEMO param_put DATA_CACHE 262144 param_put MAXDATADEVSPACES 14 param_put MAXUSERTASKS 32 param_put MAXCPU 4 param_put _IDXFILE_LIST_SIZE 8192 param_put _PACKET_SIZE 131072 param_put CAT_CACHE_SUPPLY 6464 param_put _USE_IOPROCS_ONLY YES (I do not undestand what is "MAXUSERTASKS" and how to calculate that). sapdb:sapdb is owner of all files in /home/sapdb dir. Next, executed ./build_db.sh -g -i 10000 -u 1000 -p /home/sapdb/dbt1/tmp/ in script output has following errors (full output) (log attached at end of the letter and also put to http://www.ixbt.com/comm/temp/osdl/log_build_db.txt ) In a script output contain mistakes. Where are log files, on which link "---> See log file (s) for more information. "? "I have not found any files on /.*log.*/ How to start REPLICATION SERVER? If it is used, why will not startup automatically? Further I have edited dbt1.config ---------------------------------------------------------------- [database] #hostname instance username password localhost:DBT1:dbt:dbt [cache] #hostname port dbconnections items appCache_executable_directory localhost:9992:5:1000:/home/sapdb/dbt1/cache [appServer] #hostname localhost:localhost #port 9999:9999 #dbconnection 40:40 #transaction_queue_szie 400:400 #transaction_array_szie 400:400 #items 10000:10000 #appServer executable directory /home/sapdb/dbt1/appServer:/home/sapdb/dbt1/appServer [dbdriver] #hostname localhost:localhost #items 10000:10000 #customers 2880000:2880000 #eu 400:400 ---------------------------------------------------------------- and file dbdriver.config ---------------------------------------------------------------- [dbdriver] #hostname localhost:localhost #dbdriver executable directory /home/sapdb/dbt1/dbdriver:/home/sapdb/dbt1/dbdriver ---------------------------------------------------------------- Also edited run_dbt1.sh and removed ssh from it becouse all scripts started at local machine. And corrected cmd-line parameters of appCache startup: cd $cache_dir; ./appCache -d $db_host:$db_instance -u $db_user -p $db_password -l $cache_port -c $cache_dbconnection -i $cache_items > /tmp/cache.log Next I executed ./run_dbt1.sh /home/sapdb/dbt1/tmp/res output is ------------------------------------------- reading from dbt1.config db: localhost DBT1 dbt dbt cache: localhost 9992 5 1000 /home/sapdb/dbt1/cache appServer 0 localhost 9999 40 400 400 1000 /home/sapdb/dbt1/appServer appServer 1 localhost 9999 40 400 400 1000 /home/sapdb/dbt1/appServer dbdriver 0 localhost 1000 8640 3 3 7.2 4100 /home/sapdb/dbt1/dbdriver dbdriver 1 localhost 1000 8640 3 3 7.2 4100 /home/sapdb/dbt1/dbdriver Starting appCache User defined signal 2 ------------------------------------------- Message "User defined signal 2" are after 2-3 seconds after "Starting appCache". In cache/error.log is ------------------------------------------- Fri Jul 11 12:22:24 2003 1094437952 /home/sapdb/dbt1/interfaces/odbc/odbc_interaction_search_results.c:80 [1] sqlstate HY000 : [SAP AG][LIBSQLOD SO][SAP DB] General error;-4016 POS(1) Unknown procedure name:SEARCH_RESULTS_AUTHOR. Fri Jul 11 12:22:24 2003 1094437952 cache.c:389 execute_search_results returned error Fri Jul 11 12:22:24 2003 ------------------------------------------- If to start appCache from a command line, ./appCache -d localhost:DBT1 -u dbt -p dbt -l 9992 -c 5 -i 10000 the conclusion will be precisely same mistake. Probably a mistake what the test needs to be started by different machines? But in the documentation (excluding Advanced Topics) about it it is not told. I all over again wanted to understand with start by one machine and is more best to understand the test, and then to use some machines and others of a server. p.s. sorry for my bad english. ==================================================================================================== ./build_db.sh output ==================================================================================================== Generating data... 10000 item and 1000 eu Thu Jul 10 20:42:53 MSD 2003 /home/sapdb/dbt1/datagen item scale factor 10000 user scale factor 1000 data files are in /home/sapdb/dbt1/tmp/ generating sequence creation file: ../scripts/sapdb/create_sequence.sql generating data files... Generating item table data... Finished item table data. Generating customer table data... Finished customer table data. Generating author table data... Finished author table data. Generating address table data... Finished address table data. Generating order, order_line, and cc_xacts table data... Finished order, order_line, and cc_xacts table data. data file is generated Thu Jul 10 21:06:55 MSD 2003 Thu Jul 10 21:06:55 MSD 2003 drop db OK OK OK Thu Jul 10 21:06:55 MSD 2003 create db start communication server... stop and drop existing DBT1... create database DBT1... set parameters for DBT1... set parameters for DBT1... start DBT1... initializing DBT1... load system tables... create database demo user... Thu Jul 10 21:12:58 MSD 2003 create tables >sql_execute create table author ( a_id fixed(10), a_fname varchar(20), a_lname varchar(20), a_mname varchar(20), a_dob date, a_bio varchar(500), primary key (a_id) ) OK --- > >sql_execute create table country ( co_id fixed(4), co_name varchar(50), co_exchange fixed(12, 6), co_currency varchar(18), primary key (co_id) ) OK --- > >sql_execute create table address ( addr_id fixed(10), addr_street1 varchar(40), addr_street2 varchar(40), addr_city varchar(30), addr_state varchar(20), addr_zip varchar(10), addr_co_id fixed(4), primary key (addr_id)) OK --- > >sql_execute create table customer ( c_id fixed(10), c_uname varchar(20), c_passwd varchar(20), c_fname varchar(15), c_lname varchar(15), c_addr_id fixed(10), c_phone varchar(16), c_email varchar(50), c_since date, c_last_visit date, c_login timestamp, c_expiration timestamp, c_discount fixed(5, 2), c_balance fixed(17, 2), c_ytd_pmt fixed(17, 2), c_birthdate date, c_data varchar(500), primary key (c_id)) OK --- > >sql_execute create table item ( i_id fixed(10), i_title varchar(60), i_a_id fixed(10), i_pub_date date, i_publisher varchar(60), i_subject varchar(60), i_desc varchar(500), i_related1 fixed(10), i_related2 fixed(10), i_related3 fixed(10), i_related4 fixed(10), i_related5 fixed(10), i_thumbnail fixed(8), i_image fixed(8), i_srp fixed(17, 2), i_cost fixed(17, 2), i_avail date, i_stock fixed(4), i_isbn char(13), i_page fixed(4), i_backing varchar(15), i_dimensions varchar(25), primary key (i_id)) OK --- > >sql_execute create table orders ( o_id fixed(10), o_c_id fixed(10), o_date timestamp, o_sub_total fixed(17, 2), o_tax fixed(17, 2), o_total fixed(17, 2), o_ship_type varchar(10), o_ship_date timestamp, o_bill_addr_id fixed(10), o_ship_addr_id fixed(10), o_status varchar(15), primary key (o_id)) OK --- > >sql_execute create table order_line ( ol_id fixed(3), ol_o_id fixed(10), ol_i_id fixed(10), ol_qty fixed(3), ol_discount fixed(5, 2), ol_comments varchar(100), primary key(ol_o_id, ol_id)) OK --- > >sql_execute create table cc_xacts ( cx_o_id fixed(10), cx_type varchar(10), cx_num fixed(16), cx_name varchar(31), cx_expiry date, cx_auth_id char(15), cx_xact_amt fixed(17, 2), cx_xact_date timestamp, cx_co_id fixed(4), primary key (cx_o_id)) OK --- > >sql_execute create table shopping_cart ( sc_id fixed(10), sc_c_id fixed(10), sc_date timestamp, sc_sub_total fixed(17, 2), sc_tax fixed(17, 2), sc_ship_cost fixed(17, 2), sc_total fixed(17, 2), sc_c_fname varchar(15), sc_c_lname varchar(15), sc_c_discount fixed(5, 2), primary key(sc_id) ) OK --- > >sql_execute create table shopping_cart_line ( scl_sc_id fixed(10), scl_i_id fixed(10), scl_qty fixed(3), scl_cost fixed(17, 2), scl_srp fixed(17, 2), scl_title varchar(60), scl_backing varchar(15), primary key(scl_sc_id, scl_i_id) ) OK --- Thu Jul 10 21:12:58 MSD 2003 load db Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. backup so that we can add foreign key changing data_cache to 10000 Thu Jul 10 21:13:04 MSD 2003 start backup define backup medium Thu Jul 10 21:13:09 MSD 2003 changing data_cache back to 262144 set parameters for DBT1... Thu Jul 10 21:13:19 MSD 2003 create foreign key Thu Jul 10 21:13:19 MSD 2003 >sql_execute alter table address add foreign key fk_addr_co_id ( addr_co_id) references country ( co_id ) OK --- >sql_execute commit OK --- > >sql_execute alter table customer add foreign key fk_c_addr_id ( c_addr_id ) references address ( addr_id ) OK --- >sql_execute commit OK --- > >sql_execute alter table item add foreign key fk_i_a_id ( i_a_id ) references author ( a_id ) OK --- >sql_execute commit OK --- > >sql_execute alter table orders add foreign key fk_o_c_id ( o_c_id ) references customer ( c_id ) OK --- >sql_execute commit OK --- > >sql_execute alter table orders add foreign key fk_o_bill_addr_id ( o_bill_addr_id ) references address ( addr_id ) OK --- >sql_execute commit OK --- > >sql_execute alter table orders add foreign key fk_o_ship_addr_id ( o_ship_addr_id ) references address ( addr_id ) OK --- >sql_execute commit OK --- > >sql_execute alter table order_line add foreign key fk_line_ol_i_id ( ol_i_id ) references item ( i_id ) OK --- >sql_execute commit OK --- > >sql_execute alter table order_line add foreign key fk_line_ol_o_id ( ol_o_id ) references orders ( o_id ) OK --- >sql_execute commit OK --- > >sql_execute alter table cc_xacts add foreign key fk_cx_o_id ( cx_o_id ) references orders ( o_id ) OK --- >sql_execute commit OK --- > >sql_execute alter table cc_xacts add foreign key fk_cx_co_id ( cx_co_id ) references country ( co_id ) OK --- >sql_execute commit OK --- Thu Jul 10 21:13:19 MSD 2003 Thu Jul 10 21:13:19 MSD 2003 create indexes >sql_execute create index i_i_subject on item (i_subject asc) OK --- >sql_execute commit OK --- >sql_execute create index i_i_a_id on item (i_a_id asc) OK --- >sql_execute commit OK --- >sql_execute create index i_address_table on address (addr_street1, addr_street2, addr_city, addr_state, addr_zip, addr_co_id) OK --- >sql_execute commit OK --- >sql_execute create index i_c_uname on customer (c_uname asc) OK --- >sql_execute commit OK --- >sql_execute create index i_o_c_id on orders (o_c_id asc) OK --- >sql_execute commit OK --- >sql_execute create index i_i_title on item (i_title asc) OK --- >sql_execute commit OK --- >sql_execute create index i_a_lname on author (a_lname asc) OK --- >sql_execute commit OK --- Thu Jul 10 21:13:19 MSD 2003 create prejoined tables for large database >sql_execute create table new_products (i_id fixed(10), i_title varchar(60), i_subject varchar(60), i_pub_date date, a_fname varchar(20), a_lname varchar(20), primary key (i_id)) OK --- > >sql_execute create table best_sellers (i_id fixed(10), i_title varchar(60), i_subject varchar(60), i_pub_date date, a_fname varchar(20), a_lname varchar(20), primary key (i_id)) OK --- > >sql_execute create table search_results_subject (i_id fixed(10), i_title varchar(60), i_subject varchar(60), i_pub_date date, a_fname varchar(20), a_lname varchar(20), primary key (i_id)) OK --- > >sql_execute create table i_related (i_id fixed(10), i_related1 fixed(10), i_related2 fixed(10), i_related3 fixed(10), i_related4 fixed(10), i_related5 fixed(10), primary key (i_id)) OK --- > >sql_execute commit OK --- > >sql_execute insert into new_products (select i_id, i_title, i_subject, i_pub_date, a_fname, a_lname from item, author where i_a_id=a_id) ERR -24988,ERR_SQL: sql error 100,Row not found --- Thu Jul 10 21:13:20 MSD 2003 update statistics >sql_execute update statistics item OK --- >sql_execute update statistics country OK --- >sql_execute update statistics author OK --- >sql_execute update statistics customer OK --- >sql_execute update statistics orders OK --- >sql_execute update statistics order_line OK --- >sql_execute update statistics cc_xacts OK --- >sql_execute update statistics address OK --- >sql_execute update statistics shopping_cart OK --- >sql_execute update statistics shopping_cart_line OK --- Thu Jul 10 21:13:20 MSD 2003 load dbproc >sql_connect dbt,dbt OK --- >sql_execute CREATE SEQUENCE custid INCREMENT BY 1 START WITH 2880001 OK --- >sql_execute CREATE SEQUENCE addrid INCREMENT BY 1 START WITH 5760001 OK --- >sql_execute CREATE SEQUENCE scid INCREMENT BY 1 START WITH 2592001 OK --- Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. Opened connection to REPLICATION SERVER at node local host. Replication server error (-4 : 'wrong connection state') Some error(s) occurred running command. ---> See log file(s) for more information. opened ../storedproc/sapdb/new_products.sql read ../storedproc/sapdb/new_products.sql load failed opened ../storedproc/sapdb/best_sellers.sql read ../storedproc/sapdb/best_sellers.sql load failed opened ../storedproc/sapdb/search_results_author.sql read ../storedproc/sapdb/search_results_author.sql load failed opened ../storedproc/sapdb/search_results_subject.sql read ../storedproc/sapdb/search_results_subject.sql load failed opened ../storedproc/sapdb/search_results_title.sql read ../storedproc/sapdb/search_results_title.sql load failed start to backup Thu Jul 10 21:13:21 MSD 2003 backup changing data_cache to 10000 Thu Jul 10 21:13:27 MSD 2003 start backup define backup medium Thu Jul 10 21:13:33 MSD 2003 changing data_cache back to 262144 set parameters for DBT1... Thu Jul 10 21:13:42 MSD 2003 ==================================================================================================== ==================================================================================================== end of ./build_db.sh output ==================================================================================================== JZ> I reproduced your problem on my machine. I think what happened is JZ> you did (at least I did) JZ> autoconf JZ> ./configure JZ> before >>#export CFLAGS=-I/opt/sapdb/interfaces/odbc/incl >> #export LDFLAGS=-L/opt/sapdb/interfaces/odbc/lib JZ> so autoconf did not detect sqlod library. JZ> Suggestion: JZ> make clean JZ> rm config.* JZ> autoconf JZ> ./configure JZ> make JZ> Also, with those release, sapdb 7.3.0.25 is recommended. Higher JZ> versions require the stored procedures to be changed due to SAPDB bug. JZ> Let me know if you have any questions. -- Best regards, Evgeniy mailto:eig...@nm... |