Yurttas/PL/DBL/oracle/F/R/01.txt
Jump to navigation
Jump to search
1From: ORACLE Admin Account <oracle@cs.BitsOfCode Software Systems, Inc..edu>
2To: yurttas@zcubes.com
3
4Subject: POLICIES of ORACLE
5
6
7DON'T DELETE THIS MAIL
8
9BitsOfCode Software Systems, Inc. CS DEPT Oracle Database -
10Using ORACLE and General Policies 01 Sep 00
11=====================================================================
12* Send any system problem reports or questions to oracle@cs.BitsOfCode Software Systems, Inc..edu
13 or dbadmin@cs.BitsOfCode Software Systems, Inc..edu.
14
15* Although all manuals and documentation are available "online", any
16 reproduction, printing, or transmission to a third party is in
17 violation of our licensing agreement with Oracle Corporation and
18 is forbidden. Any user that attempts to produce printed copies of
19 the Oracle online documentation is subject to sanctions imposed by
20 the CSG director that include, but are not limited to, the loss of
21 access to the Oracle database server.
22
23* Each user is allowed a maximum of 4Mb of tablespace for their
24 coursework. If additional space is required for a research
25 project, special provisions must be made through the Database
26 Administrator. User tables for standard courses are deleted at
27 the close of each semester. Faculty should consult with the
28 Database Administrator to acquire permanent space for example
29 tables and other long-term, course-related storage.
30
31 Long-term tablespace for 689/489 projects, theses, and
32 dissertations should be prearranged with the Database
33 Administrator and the CSG Director.
34
35*************
36************* The following stuff is very important
37*************
38
39* Backup and restore services are only provided in the event
40 of a system failure. Please note that if you delete a table
41 it is not considered a system failure. We recommend that you
42 ensure the integrity of your table by using the rollback and
43 recovery services provided by the Oracle database server,
44 especially when long term projects are involved. If you
45 have any questions concerning the protection afforded for a
46 research project, please contact the Database Administrator
47 BEFORE implementation.
48
49* Also, you can use export and import statements to save your
50 system data every time you make a major change in your
51 tablespace. You can do a help on export and import to find
52 out more about them.
53
54
55Oracle Overview
56===============
57Users with an Oracle database account can access the system
58from any Solaris 2.7 machine, without having to logon to the
59Oracle database server. The following are a few of the commands
60available:
61
62 * sqlplus interactive SQL environment
63 * orac_ppc embedded SQL/C compiler
64
65
66Accessing interactive SQL
67=========================
68From any Solaris 2.7 machine, enter the following command:
69
70 > sqlplus username@oracledatabase
71
72where 'username' is your Oracle database account username.
73Oracle will then ask you for your database account password.
74If successful, Oracle will display the following prompt:
75
76 SQL>
77
78If your logon attempt was unsuccessfull you will receive the
79following message:
80
81 ERROR: ORA-01017: invalid username/password; logon denied
82
83 Enter user-name:
84
85Enter your Oracle user-name as: username@oracledatabase.
86Follow this with your database account password.
87
88If this still does not work you may be using the wrong
89password. See the section on changing Oracle database
90passwords.
91
92
93Using Interactive SQL
94=====================
95Once at the "SQL>" prompt, SQL commands can then be entered
96directly. For example,
97
98 SQL> SELECT * FROM Employee WHERE salary=40000;
99
100For more information on using SQL please refer to the
101"SQL*Plus User's Guide and References" using the oradocm
102command or see your instructor.
103
104
105Creating embedded SQL/C programs
106================================
1071) Build your program with any text editor. The program file
108 must have a '.pc' extension.
1092) From any Solaris 2.7 machine, compile and link your program
110 by using the 'orac_ppc filename' command. If there are no
111 errors, an executable file will be created; the executable
112 has the same name as the original .pc file, but without any
113 extension.
114
115For example:
116
117 > emacs sample.pc /* build the program */
118 .
119 .
120 > orac_ppc sample /* create the executable */
121 > sample /* run the program */
122
123* See the online documentation for details concerning
124 embedding SQL in other high-level languages
125 (example: Programmer's Guide to the Pro*C Precompiler) or
126 your instructor for more information.
127
128
129Changing Your Oracle Database Password
130======================================
131If your Oracle account is the same as your UNIX account name,
132then you can generate a new Oracle database password on any
133Solaris 2.7 using the orapasswd command. The orapasswd command is
134used as follows:
135
136 > orapasswd
137 The new password for username@oracledatabase is WUz3fRvX
138
139THE PASSWORD SHOWN IS NOT YOUR PASSWORD, YOU MUST USE 'orapasswd'.
140
141If you are already in SQL, you can change your password using the
142following command:
143
144 SQL> ALTER USER username IDENTIFIED BY new-password;
145
146where username is your Oracle database account name and
147new-password is the new password that you desire.