After Installation configuration steps for Oracle

10g/ Developer 6i
Step1
Open Database Folder with name d:\ Oracle Product 10.2.0 db_1Network
Admin Tnsname.ora

Open this file with Notepad and copy the following text:
==================================================
===
ORCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = ora5-PC)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl)
)
)
==================================================
========
And paste into

D:\orant\NET80\ADMIN\tnname.ora

(If you are using Developer6i with Oracle10g)

And open another file sqlnet.ora and the statement should like that:

SQLNET.AUTHENTICATION_SERVICES= (None)

IMP-00013: only a DBA can import a file exported by

another DBA
Import:

Release

11.1.0.6.0

Production

on

Wed

Sep

04:26:06

2013

Copyright (c) 1982, 2007, Oracle. All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export
IMP-00013:

file

created
only

DBA

by
can

EXPORT:V11.02.00
import

file

via
exported

conventional
by

another

IMP-00000: Import terminated unsuccessfully

Solution:
It will work only if both import schema and export schema must have below credentials
grant IMP_FULL_DATABASE to <schema>
grant EXP_FULL_DATABASE to <schema>
syntax:
imp test/test file=xyz.dmp fromuser=<schema> touser=test
or
imp test/test file=xyz.dmp tables=<tables>

path
DBA

How to grant all privileges in Oracle

This is a short paper showing how to grant "all privileges" to a user in Oracle and more importantly
what privileges are needed to do this. This was a posting I made to one of the newsgroups/mailing lists
recently. This is for information only as it is useful to know BUT one important fact that should be
highlighted here is that i cannot think of any circumstances or when ALL PRIVILEGES should be granted
to anyone. It is simply unnecessary. Do the job correctly and find out the exact privileges needed for
the job in hand and grant those. Granting all privileges is a security risk as it means the user having
those privileges can do just about anything in your database.
Remember use least privilege principle at all times and grant what is needed. Do not
grant everything just to get the job done quickly. Here is the example code!
Connected to:
Personal Oracle9i Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL>
SQL>
USER
SQL>
2

sho user
is "SYSTEM"
select * from system_privilege_map
where name like '%PRIV%';

PRIVILEGE
----------167
-244

grant

NAME
PROPERTY
---------------------------------------- ---------GRANT ANY PRIVILEGE
0
GRANT ANY OBJECT PRIVILEGE
0

SQL>
SQL> -- Create a new user with just create session (to log on) and
SQL> -- any privilege to, well grant all privileges.
SQL> create user emil identified by emil;
User created.
SQL> grant create session, grant any privilege to emil;
Grant succeeded.
SQL> -- because we want to test this privilege create a second user to
SQL> -- test it with
SQL> create user zulia identified by zulia;
User created.
SQL> -- connect as emil and grant all privileges to Zulia
SQL> connect emil/emil@sans
Connected.
SQL> grant all privileges to zulia;
Grant succeeded.

SQL> -- connect as system and find out if it worked.

SQL> connect system/manager@sans
Connected.
SQL>
2
3
4*
SQL>

select count(*),grantee
from dba_sys_privs
where grantee in ('MDSYS','EMIL','ZULIA')
group by grantee
/

COUNT(*)
---------2
139
139

GRANTEE
-----------------------------EMIL
MDSYS
ZULIA

SQL>
it

We used MDSYS as a checkpoint as MDSYS has all privileges granted to

by default in a default installation of Oracle. The privilege you need
therefore is GRANT ANY PRIVILEGE.