Professional Documents
Culture Documents
En TN 2000-10-0001 Oracle Notes OAS50 Rev-B
En TN 2000-10-0001 Oracle Notes OAS50 Rev-B
Date: Product(s): Number: Subject: October 2000 (last revised: 11/14/2000) Open AdStream 5.0 2000/10-0001 Oracle Database Setup Notes This Tech Note expands upon the Oracle Appendix that appears in the Installation Guide.
2000-11-14 REV B
T E C H
N O T E :
2 0 0 0 / 1 0 - 0 0 1 5
Oracle
Setup
TABLESPACE
The database user(s) you create must have enough space to import the report data every night. You do this by setting the appropriate tablespace quotas. When you assign tablespace to the database user (ex: oasadmin), assign the users corresponding tablespace quotas according the volume of data your site accumulates. If your site accumulates a large volume of data on a daily basis, then you must assign the database user a large tablespace. If your database user does not have a sufficient tablespace, then you will experience problems when you import the data nightly. For example, the system will give you an error message saying that it cannot create or expand a particular Index or Table. If this error occurs, you must increase the users tablespace and re-run the nightly import. If your sites traffic is relatively small, a single tablespace is fine. If you are expecting a large number of ad deliveries (> 1,000,000 ad views per day), it would be wise to set up multiple tablespaces. If it is a large site, send them the fort.realmedia.com:/tmp/Create_Tables.sql and /tmp/create_Index.sql files, which assume the creation of four tablespaces for speed: RMDATA, RMRPT, RMDATA_INDX, and RMRPT_INDX.
1 1 / 2 0 0 0
R E A L
M E D I A ,
I N C .
P A G E
T E C H
N O T E :
2 0 0 0 / 1 0 - 0 0 1 5
Oracle
Setup
If you are using one tablespace for everything, continue on and execute ./preload.sh >preload.out (assuming that dbTool works). If you have four tablespaces, as described above, the two sql files will have created the tables already and we do not want preload.sh to destroy them, hence the second command, ./dbTool -b, is the only possible switch. The other method is, ./dbTool -bR, which would obliterate the structure you already created. [The -R has since been removed in Patch*c, and after.] For dbTool connectivity: $ORACLE_HOME should be set for the user environment. Hence, if you are trying to connect as nobody you will need to edit the .profile as such: ORACLE_HOME=/opt/oracle/products/816_2 (or whatever the ORACLE_HOME is on that box) export ORACLE_HOME For webserver connectivity: You will need to make the above changes to the root profile also since the webserver will have to grab these values off the environment when it starts up if it has to be able to connect to the DB (to run the front interface). To do that, in httpd.conf (for Apache) you will have to add the following line: PassEnv ORACLE_HOME (anywhere in the configuration file would do, if they are running virtual servers then set it so that it is globally available)
Please note that at this time, we have no information on how to Pass this environment variable in Netscape.
1 1 / 2 0 0 0
R E A L
M E D I A ,
I N C .
P A G E