1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
|
set doc off;
set sqlblanklines on;
/**
Oracle Table Creation Scripts.
$Horde: horde/scripts/sql/create.oci8.sql,v 1.4.8.4 2005/03/16 11:59:10 jan Exp $
@author Miguel Ward <mward@aluar.com.ar>
This sql creates the Horde SQL tables in an Oracle 8.x
database. Should work with Oracle 9.x (and Oracle7 using varchar2).
Once the tables are created you have to complete following steps:
1) Edit /usr/local/horde/config/horde.php and modify/include:
// Preference System Settings
// What preferences driver should we use? Valid values are 'none'
// (meaning use system defaults and don't save any user preferences),
// 'session' (preferences only persist during the login), 'ldap',
// and 'sql'.
$conf['prefs']['driver'] = 'sql';
// Any parameters that the preferences driver needs. This includes
// database or ldap server, username/password to connect with, etc.
$conf['prefs']['params']['phptype'] = 'oci8';
$conf['prefs']['params']['hostspec'] = 'database_name';
$conf['prefs']['params']['username'] = 'horde';
$conf['prefs']['params']['password'] = '*******';
$conf['prefs']['params']['database'] = '';
$conf['prefs']['params']['table'] = 'horde_prefs';
Where 'database_name' is the database name as defined in tnsnames.ora
that you wish to connect to.
2) Make sure that the user that starts up Apache (usually nobody or
www-data) has the following environment variables defined:
ORACLE_HOME=/home/oracle/OraHome1 ; export ORACLE_HOME
ORA_NLS=/home/oracle/OraHome1/ocommon/nls/admin/data ; export ORA_NLS
ORA_NLS33=/home/oracle/OraHome1/ocommon/nls/admin/data ; export ORA_NLS33
LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH ; export LD_LIBRARY_PATH
YOU MUST CUSTOMIZE THESE VALUES TO BE APPROPRIATE TO YOUR INSTALLATION
You can include these variables in the user's local .profile or in
/etc/profile, etc.
Obviously you must have Oracle installed on this machine AND you must
have compiled Apache/PHP with Oracle (you included --with-oci8 in the
build arguments for PHP, or uncommented the oci8 extension in
php.ini).
3) Make sure you have latest PEAR instalation inside your PHP library.
Specifically the file /usr/local/lib/php/DB.php and the directory
associated with it must be dated after April 2002 (PHP 4.2.1 is ok).
If you have an older version of PHP OR you overwrote the PHP
installation with the PEAR version 4.1.0 found at the IMP website
everything will seem to work ok but the 'Options' you save in IMP will
not appear next time you connect.
4) No grants are necessary since we connect as the owner of the
tables. If you wish you can adapt the creation of tables to include
tablespace and storage information. Since we include none it will use
the default tablespace values for the user creating these tables. Same
with the indexes (in theory these should use a different tablespace).
There is no need to shut down and start up the database!
*/
rem conn horde/&horde_password@database
/**
This is the Horde users table, needed only if you are using SQL
authentication. Note that passowrds in this table need to be
md5-encoded.
*/
CREATE TABLE horde_users (
user_uid VARCHAR2(255) NOT NULL,
user_pass VARCHAR2(32) NOT NULL,
PRIMARY KEY (user_uid)
);
/**
This is the Horde preferences table, holding all of the user-specific
options for every Horde user.
pref_uid is the username (appended with @realm if specified in servers.php)
pref_scope is the application the pref belongs to
pref_name is the name of the variable to save
pref_value is the value saved (can be very long)
We use a CLOB column so that longer column values are supported.
If still using Oracle 7 this should work but you have to use
VARCHAR2(2000) which is the limit imposed by said version.
*/
CREATE TABLE horde_prefs (
pref_uid CHAR(255) NOT NULL,
pref_scope CHAR(16) NOT NULL,
pref_name CHAR(32) NOT NULL,
-- See above notes on CLOBs.
pref_value CLOB,
PRIMARY KEY (pref_uid, pref_scope, pref_name)
);
/*
The DataTree tables are used for holding hierarchical data such as
Groups, Permissions, and data for some Horde applications.
*/
CREATE TABLE horde_datatree (
datatree_id NUMBER(16) NOT NULL,
group_uid VARCHAR2(255) NOT NULL,
user_uid VARCHAR2(255),
datatree_name VARCHAR2(255) NOT NULL,
datatree_parents VARCHAR2(255),
datatree_order NUMBER(16),
datatree_data CLOB,
datatree_serialized NUMBER(8) DEFAULT 0 NOT NULL,
datatree_updated DATE,
PRIMARY KEY (datatree_id)
);
CREATE INDEX datatree_datatree_name_idx ON horde_datatree (datatree_name);
CREATE INDEX datatree_group_idx ON horde_datatree (group_uid);
CREATE INDEX datatree_user_idx ON horde_datatree (user_uid);
CREATE INDEX datatree_order_idx ON horde_datatree (datatree_order);
CREATE INDEX datatree_serialized_idx ON horde_datatree (datatree_serialized);
CREATE TABLE horde_datatree_attributes (
datatree_id NUMBER(16) NOT NULL,
attribute_name VARCHAR2(255) NOT NULL,
attribute_key VARCHAR2(255),
attribute_value VARCHAR2(4000)
);
CREATE INDEX datatree_attribute_idx ON horde_datatree_attributes (datatree_id);
CREATE INDEX datatree_attribute_name_idx ON horde_datatree_attributes (attribute_name);
CREATE INDEX datatree_attribute_key_idx ON horde_datatree_attributes (attribute_key);
CREATE TABLE horde_tokens (
token_address VARCHAR2(100) NOT NULL,
token_id VARCHAR2(32) NOT NULL,
token_timestamp NUMBER(16) NOT NULL,
PRIMARY KEY (token_address, token_id)
);
CREATE TABLE horde_vfs (
vfs_id NUMBER(16) NOT NULL,
vfs_type NUMBER(8) NOT NULL,
vfs_path VARCHAR2(255),
vfs_name VARCHAR2(255) NOT NULL,
vfs_modified NUMBER(16) NOT NULL,
vfs_owner VARCHAR2(255),
vfs_data CLOB,
PRIMARY KEY (vfs_id)
);
CREATE INDEX vfs_path_idx ON horde_vfs (vfs_path);
CREATE INDEX vfs_name_idx ON horde_vfs (vfs_name);
exit
|
