Time Series Data Management
For Windows Desktops and Servers.
All Dbank tables, indexes, and associated objects will be stored in an Oracle tablespace called DBANK. This tablespace, together with appropriate user rights for the creation/deletion/viewing/updating of tables with the DBANK tablespace, must be created before installing Dbank on client machines.
The following SQL statement can be issued to create the DBANK tablespace (all parameters except 'DBANK' can be varied; please consult Oracle documentation on the CREATE TABLESPACE command):
"CREATE TABLESPACE DBANK DATAFILE 'dbank.dbf' SIZE 50M AUTOEXTEND ON MAXSIZE UNLIMITED"
Notice that all Dbank databases/objects will be saved to the file dbank.dbf, simplifying backup. Dbank interacts with the Oracle using ADO and Oracles' OLEDB COM interface.
(Optional) Enabling Operating System Authentication:
For automatic login to the Dbank server to function correctly, your Oracle administrator needs to enable OS authentication explicitly and create specific user accounts. A few steps are needed:
* If the os_authent_prefix system parameter is null, from SQL+, issue the following SQL command to set the parameter to "ops$"
o Alter system set os_authent_prefix = “ops$” scope = spfile;
* For each user that you wish to enable OS authentication, from SQL+ issue the following command:
o Create user “ops$DOMAIN\USERID” IDENTIFIED EXTERNALLY;
where "DOMAIN" the name of the machine that supports the user, and userid is the user name of the user. For example, on an NT machine called MYNT, and user "bizyht", your administrator would need to issue the command
create user "ops$MYNT\bizht" IDENTIFIED EXTERNALLY;
* Provide the user with appropriate read/write rights to the tablespace DBANK, for example:
o Alter user “user” quota unlimited on Dbank
| Copyright © 1994-2013 | TSDM Pte Ltd | Time Series Data Management for Windows | Contact TSDM |