[go: up one dir, main page]

File: newconnection.html

package info (click to toggle)
tora 1.3.21-3
  • links: PTS
  • area: main
  • in suites: etch, etch-m68k
  • size: 14,252 kB
  • ctags: 10,397
  • sloc: cpp: 108,822; sh: 10,861; makefile: 766; xml: 69; perl: 6
file content (55 lines) | stat: -rw-r--r-- 3,285 bytes parent folder | download | duplicates (2)
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
<HTML><HEAD><TITLE>Connecting to a database</TITLE></HEAD><BODY>
<H1>Connecting to a database</H1>
You can connect to a database by selecting the <B>File|New Connection</B> menu entry or
the toolbar button. For more information about the menu and toolbar see
<A HREF=window.html>this page</A>.<P>
After selecting the menu you will be presented with the following dialog.<P>
<IMG SRC=images/newconnection.png><P>
The filling out of this dialog is pretty straight forward.
<TABLE>
<TR><TD VALIGN=top><B>Previous connections</B></TD>
<TD VALIGN=top>This list contains the previous connection made, selecting an entry from
this list will set all the values to the right to the correct values to connect to
this database again.</TD></TR>
<TR><TD VALIGN=top><B>Connection provider</B></TD>
<TD VALIGN=top>The type of connection to create. Usually Oracle,
but MySQL is also supported on some platforms.</TD></TR>
<TR><TD VALIGN=top><B>Username</B></TD>
<TD VALIGN=top>The username with which to connect to the database</TD></TR>
<TR><TD VALIGN=top><B>Password</B></TD>
<TD VALIGN=top>The password to use for the connection, this defaults to
manager. You can also configure TOra to remember your last used password in
the <A HREF=preferences.html#global>options dialog</A>.</TD></TR>
<TR><TD VALIGN=top><B>Use SQL*Net</B></TD>
<TD VALIGN=top>This is perhaps the most difficult setting. This indicates whether
to connect locally to the database or use SQL*Net. If you check this box the
connection is made through the Oracle listener, otherwise a local connection
usually using shared memory or named pipes is made. This is only available for
Oracle connections.
</TD></TR>
<TR><TD VALIGN=top><B>Hostname</B></TD>
<TD VALIGN=top>The host on which the database resides. This is only available for
non Oracle connections.
</TD></TR>
<TR><TD VALIGN=top><B>Database</B></TD>
<TD VALIGN=top>What database to connect to, the listbox is filled with the
values available in your tnsnames.ora file.</TD></TR>
<TR><TD VALIGN=top><B>Connection Mode</B></TD>
<TD VALIGN=top>The type of connection to make, usually <B>normal</B> always suffices here.
But sometimes during database administration <B>SYS_DBA</B> or <B>SYS_OPER</B> is needed. If you
don't know what these mean you probably shouldn't be using them.</TD></TR>
</TABLE>
Upon establishing a successful connection all the settings of the dialog will be saved
and remembered when the next connection is made with the exception of the password.
<A NAME=priv><H2>What privileges do you need to run TOra</H2>
TOra should be able to run as any user, although off course you can never do anything
in TOra that aren't allowed from that Oracle account. You will be able to use pretty much
any tool in TOra for read only purposes if you are granted the <B>SELECT_CATALOG_ROLE</B>,
also some parts of TOra will have limited functionality if you do not have the
<B>ALTER SESSION</B> privilege.<P>
Also you need to be able to create the plan table if that is not done for you. The plan
table (See <A HREF=database.html>options</A> for how to select plan table name) must
also be available with <B>INSERT</B> and <B>SELECT</B> access. TOra will function without
the plan table but off course you will not be able to display any execution plans.
</body>
</html>