Give me hints how to re-create this table for best performance

Question

Dear Friends,
I do not have any experience in good database desiginig practices. please advise me on this issue.
i have this table here, it gets only data inserts mostly 99%, no deletes, and very very few updates that is neglizable, please suggest me best storage parmteres,physical attributes. how much PCT FREE, PCT USED,INIT TRANS, MAX TRANS etc, all the i didnt use this storage clauses when i design tables. just a plain table design only. please give me idea, so that i can undesratand with this example and i can use for other tables in my application, our database is Oracle 8i.
this is OLTP application this table is importnat for all transactions.
this table gets 3000 records per day, but the number will increase in future.
CREATE TABLE ticket_master(ticket_no VARCHAR2(20) CONSTRAINT tick_mas_pkey PRIMARY KEY,
name_of_the_passenger     VARCHAR2(50), /* 10 to 15 characters max */
nationality          VARCHAR2(50), /* 10 to 15 max */
passport_id_no          VARCHAR2(50), /* 10 max */
place_of_issue          VARCHAR2(50), /* 12 max */
issued_by          VARCHAR2(50), /* 12 max */
date_of_issue          DATE,
trip_id               VARCHAR2(20) CONSTRAINT tick_mas_trip_rkey REFERENCES trip_master(trip_id),
seat_no               VARCHAR2(5), /* 2 only */
class               VARCHAR2(50), /* 3 to 5 max */
fare               NUMBER(10,2),
payment_instrument_no     VARCHAR2(20),
boarding_from           VARCHAR2(50), /* 10 to 15 max */
dropping_point          VARCHAR2(50), /* 10 to 15 max */
journey_from           VARCHAR2(50), /* 10 to 15 max */
journey_to          VARCHAR2(50), /* 10 to 15 max */
paid_at               VARCHAR2(50), /* 10 to 15 max */
gender               CHAR(1));
and do you want me keep only this table into a seperate table space if so, give me a CREATE command for creating table space with best paramaters as a example.
thanks in advance.

Answer 1

My $0.02
1) Since there are no deletes from the table, PCTUSED isn't going to be much of a factor.
2) The default PCTFREE of 10% will probably work just fine.
3) The table design doesn't have any not null constraints. Certainly the primary key and your FK trip_id should be not null. Things like date_of_issue and gender are probably mandatory columns also. The existance of not-null constraints help the CBO in optimizing queries.
4) It sure looks like the table could be normalized. Particurlarly the nationality column could be brought out into a nation_master table. The resultant FK could then be a number(5,0) which would make the table quite smaller (thus faster to query)...
5) Keep the table stats up-to-date as the table grows. Let the CBO take care of the rest...