Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

First Time Installation.

Status
Not open for further replies.

salimwng

IS-IT--Management
Mar 11, 2002
134
MU
Hello,

I have installed Oracle 9i on a Win2000 Pro PC. I have been given an assignment that i need to work on. I successfully installed the 3 CD's on my PC by using the following prompts when asked during installation. They are;

Destination Name is --> OraHome90
Destination Path is --> c:\oracle\ora90
Product installed is --> Oracle9i DataBase 9.0.1.1.1
Installation type is --> Personal Edition (1.72 Gb)
Database configuration is --> General Purpose

I need to work on the SQL plus as per what we have been asked in the assignment. But everytime i launch the SQL PLus, i am being asked for;

User Name:
Password:
Host String;

I have no idea what to put in here. At the University, we were given already these info to log in and overthere they are on a Network. How should i proceed on a Stand Alone PC ? I have been searching on this forum for 2 hours already, but didn't get any clue for a stand alone installation.

Can anybody please help me step by step how must i proceed. I am completely new at Oracle

Many thanks
Salim
 
Salim,

To become connected to a database/instance about which you do not yet know any information, you can do the following. From your Windows2000 command prompt, issue the following commands while connected to Windows2000 as the same privileged user with which you installed the Oracle database/instance:
Code:
c:
cd\oracle\ora90\bin
sqlplus /nolog
You can copy and paste the above commands at your command prompt to connect you to SQL*Plus.

Once you have connected to SQL*Plus, issue these commands:
Code:
connect / as sysdba
(This command should result in one of the two following responses:
“connected.”
Or
“connected to an idle instance.”
If you see the latter message, then issue this command:

Startup

This command starts the Oracle instance, issuing several confirmatory commands ending with “database opened.”

At this point, you are connected to a running Oracle instance as its most privileged/powerful user, “SYS”. To discover other important information about your Oracle instance, issue this command:
Code:
select * from v$instance;
This results in several columns of output that will be so wide that they do not fit on one line of output on your screen. If you can visually line up the headings with their respective data, you will see (among other columns) these pieces of information:
INSTANCE_NAME
HOST_NAME
VERSION
STARTUP_TIME

Also, you can discover the names of USERS that reside on the database with this command:
Code:
select username, default_tablespace, temporary_tablespace from dba_users;
Incidentally, the only users that should have “SYSTEM” as their default tablespace are users “SYS” and “SYSTEM”. No users (even “SYS” or “SYSTEM”) should have “SYSTEM” as their temporary tablespace. To correct any issues with tablespace assignments, you can issue these commands:
Code:
ALTER USER <username> DEFAULT TABLESPACE <non-SYSTEM tablespace name>;
-- or --
ALTER USER <username> TEMPORARY TABLESPACE <temporary tablespace name>;
-- or –
ALTER USER <username> DEFAULT TABLESPACE <non-SYSTEM tablespace name> TEMPORARY TABLESPACE <temporary tablespace name>;

You may confirm/assign passwords to users with the following commands:
Code:
ALTER USER <username> IDENTIFIED BY <password that you choose>;
-- or, you can combine the previous commands with the above command:
ALTER USER <username> IDENTIFIED BY <password that you choose>
DEFAULT TABLESPACE <non-SYSTEM tablespace name>
TEMPORARY TABLESPACE <temporary tablespace name>;

Also, to confirm that a user is able to connect to the database and to create objects, you can GRANT the following privileges, as needed:
Code:
GRANT CONNECT TO <username>; -- This allows logins
GRANT RESOURCE TO <username>; -- This allows CREATE-ing objects
GRANT CONNECT, RESOURCE TO <username>; -- This combinses the above.

Now that you know the passwords for your users, you can now reattempt connects from the GUI SQL*Plus application that you originally tried. Since you are not connecting to a remote database, the HOST entry is optional:
Code:
USERNAME: <enter a username of your choice>
PASSWORD: <enter the appropriate password for this user>
HOST STRING: <leave it without an entry>
[OK]
If all goes well, you should be able to successfully connect to your database with this user.

Let us know your findings, on-going obstacles, or follow-on questions.

[santa]Mufasa
(aka Dave of Sandy, Utah, USA)
@ 02:11 (30Jan05) UTC (aka "GMT" and "Zulu"),
@ 19:11 (29Jan05) Mountain Time

Click here to Donate to Tsunami Relief. 100% of your contributions here go to the victims...0% to administration.
They were "The First-Responder" to the disaster, with relief deliveries arriving before Red Cross and U.S. aid.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top