Help Request: ORA-01950: no privileges on tablespace

I am a fairly new Oracle DBA. I have a developer who has his own tablespace, and he is getting the error message above when he tries to execute the following script to create a table:
CREATE TABLE SOA_FWK_VALUE_TRANSLATION
CONTEXT_ID VARCHAR2(10) NOT NULL,
TRANSLATION_ID VARCHAR2(10) NOT NULL,
FROM_QUALIFIER VARCHAR2(30) NOT NULL,
FROM_VALUE VARCHAR2(250) NOT NULL,
TO_VALUE VARCHAR2(250)
, CONSTRAINT SOA_FWK_VALUE_TRANSLATION_PK PRIMARY KEY
CONTEXT_ID,
TRANSLATION_ID,
FROM_QUALIFIER,
FROM_VALUE
He has CONNECT as well as CREATE TABLE and CREATE SEQUENCE privledges. What other privledges do I need to grant to him so that he can create his tables and indexes?
Thank you!

ORA-01950

Similar Messages

Import error IMP-00017 and ORA-01950 no privileges on tablespace

Hi,
I am trying to do a full import into a 10.2.0.4 database from a 9.2.0.6 export dumpfile. The tablespaces have already been pre-created. I got this error on one tablespace, and I can't figure out why because I was using SYS to do import, how come SYS doesn`t have this privilege. All objects in other tablespaces were created without this problem.
- IMP-00017: following statement failed with ORACLE error 1950:
"CREATE TABLE "FYAERLG" ...
- ORA-01950: no privileges on tablespace 'INFOTABLES'
Please help.
Thanks
-lixidon

Who is the owner of "FYAERLG" ?
Try granting the owner of the table, quota on INFOTABLES tablespace.
**Added**
Note [95554.1|https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=95554.1] explains a scenario,which could be the reason for this failure.
Edited by: Bobcatalog on Jan 8, 2009 12:49 PM

ORA-01950: no privileges on tablespace

I am trying to move 'test' users table as system to a new tablespace 'tbs2'.
I am getting the above error, however both system and test users have either resource role or unlimited tablespace privilege ?

Hey,
ORA-01950: no privileges on tablespace 'string'
Cause: User does not have privileges to allocate an extent in the specified tablespace.
Action: Grant the user the appropriate system privileges or grant the user space resource on the tablespace.
I believe you can find helpful help in URLs below -
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:1063989617206
( this one regarding : ORA-01950: NO PRVILIGES ON TABLESPACE...)
and
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:47812348053
( this one regarding : move tables from one
tablespace to another tablespace)
Best regards,
Marcello

ORA-01950: no privileges on tablespace 'USERS' - bug?

(1)you(SYSTEM) create a XE(APEX)-User with DBA privilege and "create table..."
(2) later SYSTEM revoke the dba (only uncheck the dba)
he should have even connect, resource, "create table..." ?
(3) but he can connect, but not create a table:
ORA-01950: no privileges on tablespace 'USERS'
=> bug?

granting of `unlimited tablespace' systemprivilege
when granting DBA or RESOURCE (and may be someother
roles too?). could you please point me any?Did you know that it has UNLIMITED TABLESPACE system
privilege, making it able to create any table
anywhere in the database – including the SYSTEM
tablespace? "it" - who is "it"? DBA (or RESOURCE) role? but UNLIMITED TABLESPACE can't be granted to a role.
Obviously, this is not what you want. You
would want to restrict the tablespaces to specific
users only...?i want to find where this issue (or feature) is documented.
PS ouch. in my previous post i ment implicit granting of that system privilege.

ORA 01950 no privileges to tablespace 'system'

Please help,
I need to create a table as XX user.
First, I log in as system/manager
Second, I grant create table privilege to XX
Third, I log in as UPS and create a table... (X)
At this point I get an error 'ORA-01950' no privileges to table space 'SYSTEM'. What should I do next? Should I grant assess to tablespace 'System' for UPS?
Thanks in advance,
Sonya

Change the default and temporary tablespaces of the user to something other than SYSTEM, and grant them an unlimited quota on those tablespaces.

Exchange Partition and ORA-01950 no privileges on tablespace

I am getting an ORA-01950 error on exchanging a partition. The user that is being used has been granted 'Unlimited Tablespace' privilege. I can create tables with the user in question in the tablespace in question but the exchange fails with the 1950 error.
Anyone have any thoughts?

No it is not. However the user has select, insert,update and delete on all tables in the schema. Not even SYSTEM can perform this without the same error

Help! ORA-01031: insufficient privileges during "startup migrate" 8i to 9i

Hello there,
I am following the Oracle 9i upgrade checklist Doc ID: 159657.1 to upgrade from 8.1.7.3 to 9.2.0.4.
In step 31, after setting the environment to new ORACLE_HOME, I am trying to start the 9.2.0.4 instance in migrate mode. This is the sequence of errors that I get.
Any help is greatly appreciated.
Thanks,
Rao
oracle>sqlplus /nolog
SQL*Plus: Release 9.2.0.4.0 - Production on Mon Aug 25 09:55:29 2003
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> connect / as sysdba;
Connected to an idle instance.
SQL> shutdown immediate
ORA-24324: service handle not initialized
ORA-24323: value not allowed
ORA-01092: ORACLE instance terminated. Disconnection forced
SQL> startup migrate
ORA-01031: insufficient privileges
SQL> quit
Disconnected
oracle>

bash-2.03$ env | sort
HOME=/home/oraclei
HOSTNAME=orafinprdrodb01
HOSTTYPE=sparc
HZ=
LD_LIBRARY_PATH=/usr/lib:/usr/local/lib:/ysm_finapps_legacy/ysm_data/d00/app/oraclei/prodidb/8.1.7/lib:/usr/dt/lib:/usr/openwin/lib
LOGNAME=oraclei
MACHTYPE=sparc-sun-solaris
MAIL=/var/mail/oraclei
NLS_DATE_FORMAT=DD-MON-RR
NLS_LANG=American_America.UTF8
NLS_NUMERIC_CHARACTERS=.,
NLS_SORT=binary
OLDPWD=/ysm_finapps_legacy/ysm_data/d00/app/oraclei/prodidb/8.1.7/rdbms
ORACLE_HOME=/ysm_finapps_legacy/ysm_data/d00/app/oraclei/prodidb/8.1.7
ORACLE_SID=PRODI
OSTYPE=solaris
PATH=/ysm_finapps_legacy/ysm_data/d00/app/oraclei/prodidb/8.1.7/bin:/usr/ccs/bin:/usr/sbin:/usr/bin:
PWD=/ysm_finapps_legacy/ysm_data/d00/app/oraclei/prodidb/8.1.7/rdbms/lib
SHELL=/bin/sh
SHLVL=1
TERM=xterm
TNS_ADMIN=/ysm_finapps_legacy/ysm_data/d00/app/oraclei/prodidb/8.1.7/network/admin
TZ=US/Pacific
_=/usr/bin/env

Privileges on tablespace

Hi all,
A real beginner's question:
I created a tablespace ts_name, and when I try and create my table using the tablespace, I get:
ORA-01950: no privileges on tablespace 'TS_NAME'
Which privileges do I need to setup?
Thanks
Philippe

Please do NOT hijack a thread to ask your own, unrelated questions.
PLEASE, PLEASE, PLEASE, PLEASE learn to check the documentation. The full set of official Oracle documents, including SQL Reference manuals, can be found at tahiti.oracle.com.

No privileges on tablespace

i exported a table from database test to other database through logical backup.
while importing i am getting error ora-01950-no privileges on table space 'mchtbs'
the user from which i exported the table default table space is mchtbs.
i am getting my table imported to the user who has default table space mchtbs
why this is happening.can any one suggest me
thanks in advance

So?
Isn't this just a quota issue?
Did you look up the error message?
Your initial post is so vague, one would need an interpreter to understand it.
If you would have set up the target user with the correct default tablespace, quota on the default tablespace, and no quota on the original tablespace, it would have worked.
And obviously, the resolution to ora-1950 has been posted all over the Internet.
But why would one use a search engine, when you can post the question again?
Sybrand Bakker
Senior Oracle DBA

ORA-01031: insufficient privileges in oracle 10.2 in windows 2008r2

Dear All,
We have install SAP ecc6 EHP4 on oracle 10.2.0.5 on windows 2008R2
whenever we schedule any activity in db13 we are getting below error .
=================================
Job started
Step 001 started (program RSDBAJOB, variant &0000000000059, user ID PARESH)
Execute logical command BRBACKUP On host IRDAECCDEV
Parameters:-u / -jid FLL__20110922104226 -c force -t online -m full -p initieq_online.sap
BR0051I BRBACKUP 7.20 (3)
BR0055I Start of database backup: begvgwgh.fnf 2011-09-22 10.42.27
BR0484I BRBACKUP log file: K:\oracle\IEQ\sapbackup\begvgwgh.fnf
BR0280I BRBACKUP time stamp: 2011-09-22 10.42.28
BR0301E SQL error -1031 at location BrInitOraCreate-2, SQL statement:
'CONNECT / AT PROF_CONN IN SYSOPER MODE'
ORA-01031: insufficient privileges
BR0303E Determination of Oracle version failed
=================================
As per sap note 400421 i have carry out all the check and all are perfect.
Also i have check below notes and every thing are fine
Note 834917 - Oracle Database 10g: New database role SAPCONN
Note 1028220 - ORA-01031: Insufficient privileges despite SAPCONN role
Note 700548 - FAQ: Oracle authorizations
Also i have check the note which suggest to run the sapdba_role.sql script
But still i am getting the same error.
Also SAPSID services is running with user id sapserviceSID and i change it to SIDadm but no lock.
Request you please help me in this regard.
Sincerely
Paresh

As expected
This is really a very small problem but very weird we suffered so many times. May be we should confirm the authorizations for SAPServiceSID and sidadm users on that windows host, sometimes we miss this part in Windows to check.
Kernel folders should be proper accessible by both of the users. Also, please keep SAP instance service via SAPServiceSID itself.
Just to reconfirm - you restarted SAP and restarted SAP/Oracle services as well, right ?
Thanks

ORA-01031: insufficient privileges when connecting by SQL PLUS 8.0 with sys

From client, I use SQL PLUS 8.0 to connect to server: sys/password@MYDB1 as sysdba
The error always raises “ORA-01031: insufficient privileges”
I have done:
- Set: remote_login_passwordfile=exclusive in tnsname.ora file
- Uncomment: SQLNET.AUTHENTICATION_SERVICES in “sqlnet.ora” file
Also on this client:
to use SQL PLUS 8.0 to connect to server: manager/password@MYDB1. To connect normally
to use PLSQL Deverloper (it is the same oracle_home with SQL PLUS 8.0) to connect to database normally with user sys.
To use Enterprise manager console (it is other oracle_home with SQL PLUS 8.0) to connect to database normally with user sys
Please, help me to solve this trouble

THIS IS CONTENT OF SQLNET.ora CLIENT
# copyright (c) 1996 by the Oracle Corporation
# NAME
# sqlnet.ora
# FUNCTION
# Oracle Network Client startup parameter file example
# NOTES
# This file contains examples and instructions for defining all
# Oracle Network Client parameters. It should be possible to read
# this file and setup a Client by uncommenting parameter definitions
# and substituting values. The comments should provide enough
# explanation to enable a reasonable user to manage his TNS connections
# without having to resort to 'real' documentation.
# SECTIONS
# ONames Client
# Namesctl
# Native Naming Adpaters
# MODIFIED
# skanjila 06/06/97 - Correct default for Automatic_IPC
# eminer 05/15/97 - Add the relevant onrsd parameters.
# asriniva 04/23/97 - Merge with version from doc
# ggilchri 03/31/97 - mods
# bvasudev 02/07/97 - Change sqlnet.authentication_services documentation
# bvasudev 11/25/96 - Merge sqlnet.ora transport related parameters
# asriniva 11/12/96 - Revise with new OSS parameters.
# asriniva 11/05/96 - Add ANO parameters.
# - ONames Client ----------------------------------------------------
#names.default_domain = world
#Syntax: domain-name
#Default: NULL
# Indicates the domain from which the client most often requests names. When
# this parameter is set the default domain name (for example, US.ACME), the
# domain name will be automatically appended to any unqualified name in an
# ONAmes request (query, register, deregister, etc). Any name which contains
# an unescaped dot ('.') will not have the default domain appended. Simple
# names may be qualified with a trailing dot (for example 'rootserver.').
#names.initial_retry_timeout = 30
#Syntax: 1-600 seconds
#Default: 15 (OSD)
# Determines how long a client will wait for a response from a Names Server
# before reiterating the request to the next server in the preferred_servers
# list.
#names.max_open_connections = 3
#Syntax: 3-64
#Default: ADDRS in preferred_servers
# Determines how many connections an ONames client may have open at one time.
# Clients will ordinarily keep connections to servers open once they are
# established until the operation (or session in namesctl) is complete. A
# connection will be opened whenever needed, and if the maximum would be
# exceeded the least recently used connection will be closed.
#names.message_pool_start_size = 10
#Syntax: 3-256
#Default: 10
# Determines the initial number of messages allocated in the client's message
# pool. This pool provides the client with pre-allocated messages to be used
# for requests to ONames servers. Messages which are in the pool and unused
# may be reused. If a message is needed and no free messages are available in
# the pool more will be allocated.
#names.preferred_servers = (address_list =
# (address=(protocol=ipc)(key=n23))
# (address=(protocol=tcp)(host=nineva)(port=1383))
# (address=(protocol=tcp)(host=cicada)(port=1575))
#Syntax: ADDR_LIST
#Default: Well-Known (OSD)
# Specifies a list of ONames servers in the client's region; requests will be
# sent to each ADDRESS in the list until a response is recieved, or the list
# (and number of retries) is exhausted.
# Addresses of the following form specify that messages to the ONames server
# should use Oracle Remote Operations (RPC):
# (description =
# (address=(protocol=tcp)(host=nineva)(port=1383))
# (connect_data=(rpc=on))
#names.request_retries = 2
#Syntax: 1-5
#Default: 1
# Specifies the number of times the client should try each server in the list
# of preferred_servers before allowing the operation to fail.
#names.directory_path
#Syntax: <adapter-name>
#Default: TNSNAMES,ONAMES,HOSTNAME
# Sets the (ordered) list of naming adaptors to use in resolving a name.
# The default is as shown for 3.0.2 of sqlnet onwards. The default was
# (TNSNAMES, ONAMES) before that. The value can be presented without
# parentheses if only a single entry is being specified. The parameter is
# recognized from version 2.3.2 of sqlnet onward. Acceptable values include:
# TNSNAMES -- tnsnames.ora lookup
# ONAMES -- Oracle Names
# HOSTNAME -- use the hostname (or an alias of the hostname)
# NIS -- NIS (also known as "yp")
# CDS -- OSF DCE's Cell Directory Service
# NDS -- Novell's Netware Directory Service
# - Client Cache (ONRSD) ---------------------------------------------
names.addresses = (ADDRESS=(PROTOCOL=IPC)(KEY=ONAMES))
Syntax: ADDR
Default: (ADDRESS=(PROTOCOL=IPC)(KEY=ONAMES))
Address on which the client cache listens (is available to clients).
Any valid TNS address is allowed. The default should be used if at
all possible; clients have this entry hardwired as the first line
of their server-list file (sdns.ora). If the address is set to a
non-default value the client's preferred_servers parameter should
be set to include the client-cache address first.
names.authority_required = False
Syntax: T/F
Default: False
Determines whether system querys (for the root etc) require Authoritative
answers.
names.auto_refresh_expire = 259200
Syntax: Number of seconds, 60-1209600
Default: 259200
This is the amount of time (in seconds) the server will cache the addresses
of servers listed in server-list file (sdns.ora). When this time expires the
server will issue another query to the servers in those regions to refresh
the data.
names.auto_refresh_retry = 180
Syntax: Number of seconds, 60-3600
Default: sec.     180
This set how often the server will retry when the auto_refresh query fails.
names.cache_checkpoint_file = cache.ckp
Syntax: filename
Default: $ORACLE_HOME/network/names/ckpcch.ora
Specifies the name of the operating system file to which the Names Server
writes its foreign data cache.
names.cache_checkpoint_interval = 7200
Syntax: Number of seconds, 10-259200
Default: 0 (off)
Indicates the interval at which a Names Server writes a checkpoint of its
data cache to the checkpoint file.
names.default_forwarders=
(FORWARDER_LIST=
(FORWARDER=
(NAME= rootserv1.world)
(ADDRESS=(PROTOCOL=tcp)(PORT=42100)(HOST=roothost))))
Syntax: Name-Value/address_list
Default: NULL
A list (in NV form) of the addresses of other servers which should be used to
forward querys while in default_forwarder (slave) mode. NAME is the global
names for the server to which forwards whould be directed, and ADDRESS is its
address.
names.default_forwarders_only = True
Syntax: T/F
Default: False
When set to true this server will use the servers listed in default_forwarders
to forward all operations which involve data in foreign regions. Otherwise it
will use the servers defined in the server-list file (sdns.ora) in addition
to any defined in the default_forwarders parameter.
names.log_directory = /oracle/network/log
Syntax: directory
Default: $ORACLE_HOME/network/log
Indicates the name of the directory where the log file for Names Server
operational events are written.
names.log_file = names.log
Syntax: filename
Default: names.log
The name of the output file to which Names Server operational events are
written.
names.log_stats_interval = 3600
Syntax: Number of seconds, 10-ub4max
Default: sec.     0 (off)
Specifies the number of seconds between statistical entries in log file.
names.log_unique = False
Syntax: T/F
Default: False
If set to true the server will guarantee that the log file will have a unique
name which will not overwrite any existing files (note that log files are
appended to, so log information will not be lost if log_unique is not true).
names.max_open_connections = 10
Syntax: 3-64
Default: 10
Specifies the number of connections that the Names Server can have open at any
given time. The value is generated as the value 10 or the sum of one
connection for listening, five for clients, plus one for each foreign domain
defined in the local administrative region, whichever is greater. Any
operation which requires the server to open a network connection will use
an already open connection if it is available, or will open a connection
if not. Higher settings will save time and cost network resources; lower
settings save network resources, cost time.
names.max_reforwards = 2
Syntax: 1-15
Default: 2
The maximum number of times the server will attempt to forward a certain
operation.
names.message_pool_start_size = 24
Syntax: 3-256
Default: 10
Determines the initial number of messages allocated in the server's message
pool. This pool provides the server with pre-allocated messages to be used
for incoming or outgoing messages (forwards). Messages which are in the pool
and unused may be reused. If a message is needed and no free messages are
available in the pool more will be allocated.
names.no_modify_requests = False
Syntax: T/F
Default: False
If set to true, the server will refuse any operations which modify the
data in its region (it will still save foreign info in the cache which is
returned from foreign querys).
names.password = 625926683431AA55
Syntax: encrypted string
Default: NULL
If set the server will require that the user provide a password in his
namesctl session (either with sqlnet.ora:namesctl.server_password or 'set
password') in order to do 'sensitive' operations, like stop, restart, reload.
This parameter is generally set in encrypted form, so it can not be set
manually.
names.reset_stats_interval = 3600
Syntax: 10-ub4max
Default: 0 (off)
Specifies the number of seconds during which the statistics collected by the
Names Servers should accumulate. At the frequency specified, they are reset
to zero. The default value of 0 means never reset statistics.
names.trace_directory = /oracle/network/trace
Syntax: directory
Default: $ORACLE_HOME/network/trace
Indicates the name of the directory to which trace files from a Names Server
trace session are written.
names.trace_file = names.trc
Syntax: filename
Default: names.trc
Indicates the name of the output file from a Names Server trace session.
names.trace_func # NA
Syntax: T/F
Default: False
Internal mechanism to control tracing by function name.
names.trace_level = ADMIN
Syntax: T/F
Default: False
Syntax: {OFF,USER,ADMIN,0-16}
Default: OFF (0)
Indicates the level at which the Names Server is to be traced.
Available Values:
     0 or OFF - No trace output
     4 or USER - User trace information
     10 or ADMIN - Administration trace information
     16 or SUPPORT - WorldWide Customer Support trace information
names.trace_mask = (200,201,202,203,205,206,207)
Syntax: list of numbers
Default: NULL
Internal mechanism to control trace behavior.
names.trace_unique = True
Syntax: T/F
Default: False
Indicates whether each trace file has a unique name, allowing multiple trace
files to coexist. If the value is set to ON, a process identifier is appended
to the name of each trace file generated.
# - Namesctl ---------------------------------------------------------
#namesctl.trace_directory = /oracle/network/trace
#Syntax: directory
#Default: $ON/trace
# Indicates the name of the directory to which trace files from a namesctl
# trace session are written.
#namesctl.trace_file = namesctl.trc
#Syntax: filename
#Default: namesctl.trc
# Indicates the name of the output file from a namesctl trace session.
#namesctl.trace_func # NA
#Syntax: word list
#Default: NULL
# Internal mechanism to control tracing by function name.
#namesctl.trace_level = ADMIN
#Syntax: {OFF,USER,ADMIN,0-16}
#Default: OFF (0)
# Indicates the level at which the namesctl is to be traced.
# Available Values:
#     0 or OFF - No trace output
#     4 or USER - User trace information
#     10 or ADMIN - Administration trace information
#     16 or SUPPORT - WorldWide Customer Support trace information
#namesctl.trace_mask # NA
#Syntax: number list
#Default: NULL
# Internal mechanism to control trace behavior.
#namesctl.trace_unique = True
#Syntax: T/F
#Default: False
# Indicates whether each trace file has a unique name, allowing multiple trace
# files to coexist. If the value is set to ON, a process identifier is appended
# to the name of each trace file generated.
#namesctl.no_initial_server = False
#Syntax: T/F
#Default: False
# If set to TRUE namesctl will suppress any error messages when namesctl is
# unable to connect to a default names server.
#namesctl.internal_use = True
#Syntax: T/F
#Default: False
# If set to true namesctl will enable a set of internal undocumented commands.
# All internal commands are preceded by an underscore ('_') in order to
# distinguish them as internal. Without going into details, the commands
# enabled are:
# adddata createname deletename
# fullstatus ireplacedata newttlname
# pause                 remove_data renamename
# replacedata start                 walk*
# There are also a set of names server variables which may be set when
# namesctl is in internal mode:
# authorityrequired autorefresh*
# cachecheckpoint_interval cachedump
# defaultautorefresh_expire defaultautorefresh_retry
# defaultforwarders_only forwardingdesired
# maxreforwards modifyops_enabled
# nextcache_checkpoint nextcache_flush
# nextstat_log nextstat_reset
# reload                         request_delay
# restart                        shutdown
#namesctl.noconfirm = True
#Syntax: T/F
#Default: False
# When set to TRUE namesctl will suppress the confirmation prompt when
# sensitive operations (stop, restart, reload) are requested. This is
# quite helpful when using namesctl scripts.
#namesctl.server_password = mangler
#Syntax: string
#Default: NULL
# Automatically sets the password for the names server in order to perform
# sensitive operations (stop, restart, reload). The password may also be
# set manually during a namesctl session using 'set password'.
#namesctl.internal_encrypt_password = False
#Syntax: T/F
#Default: True
# When set to TRUE namesctl will not encrypt the password when it is sent to
# the names server. This would enable an unencrypted password to be set in
# names.ora:names.server_password
# - Native Naming Adpaters -------------------------------------------
#names.dce.prefix = /.:/subsys/oracle/names
#Syntax: DCE cell name
#Default: /.:/subsys/oracle/names
#Specifies the DCE cell (prefix) to use for name lookup.
#names.nds.name_context = personnel.acme
#Syntax: NDS name
#Default: (OSD?)
# Specifies the default NDS name context in which to look for the name to
# be resolved.
#names.nis.meta_map # NA
# Syntax: filename
# Default: sqlnet.maps
# Specifies the file to be used to map NIS attributes to an NIS mapname.
# Currently unused.
# - Advanced Networking Option Authentication Adapters ----------------
#sqlnet.authentication_services
# Syntax: A single value or a list from {beq, none, all, kerberos5,
#       cybersafe, securid, identitx}
# Default: NONE
# Enables one or more authentication services. To enable
# authentication via the Oracle Security Server, use (beq, oss). If
# the Advanced Networking Option has been installed with Kerberos5
# support, using (beq, kerberos5) would enable authentication via
# Kerberos.
sqlnet.authentication_services=(beq, oss)
## Parmeters used with Kerberos adapter.
#sqlnet.kerberos5_cc_name
# Syntax: Any valid pathname.
# Default: /tmp/krb5cc_<uid>
# The Kerberos credential cache pathname.
#sqlnet.kerberos5_cc_name=/tmp/mycc
#sqlnet.kerberos5_clockskew
# Syntax: Any positive integer.
# Default: 300
# The acceptable difference in the number of seconds between when a
# credential was sent and when it was received.
#sqlnet.kerberos5_clockskew=600
#sqlnet.kerberos5_conf
# Syntax: Any valid pathname.
# Default: /krb5/krb.conf
# The Kerberos configuration pathname.
#sqlnet.kerberos5_conf=/tmp/mykrb.conf
#sqlnet.kerberos5_realms
# Syntax: Any valid pathname
# Default: /krb5/krb.realms
# The Kerberos host name to realm translation file.
#sqlnet.kerberos5_realms=/tmp/mykrb.realms
#sqlnet.kerberos5_keytab
# Syntax: Any valid pathname.
# Default: /etc/v5srvtab
# The Kerberos secret key file.
#sqlnet.kerberos5_keytab=/tmp/myv5srvtab
#sqlnet.authentication_kerberos5_service
# Syntax: Any string.
# Default: A default is not provided.
# The Kerberos service name.
#sqlnet.authentication_kerberos5_service=acme
## Parmeters used with CyberSAFE adapter.
#sqlnet.authentication_gssapi_service
# Syntax: A correctly formatted service principal string.
# Default: A default is not provided.
# The CyberSAFE service principal
#sqlnet.authentication_gssapi_service=acme/[email protected]
## Parmeters used with Identix adapter.
#sqlnet.identix_fingerprint_method
# Syntax: Must be oracle.
# Default: A default is not provided.
# The Identix authentication server method
#sqlnet.identix_fingerprint_method=oracle
#sqlnet.identix_fingerprint_database
# Syntax: Any string.
# Default: A default is not provided.
# The Identix authentication server TNS alias
#sqlnet.identix_fingerprint_database=ofm
#sqlnet.identix_fingerprint_database_user
# Syntax: Any string
# Default: A default is not provided.
# The Identix authentication service well known username.
#sqlnet.identix_fingerprint_database_user=ofm_client
#sqlnet.identix_fingerprint_database_password
# Syntax: Any string
# Default: A default is not provided.
# The Identix authentication service well known password.
#sqlnet.identix_fingerprint_database_password=ofm_client
# - Advanced Networking Option Network Security -------------------------
#sqlnet.crypto_checksum_client
#sqlnet.crypto_checksum_server
#sqlnet.encryption_client
#sqlnet.encryption_server
# These four parameters are used to specify whether a service (e.g.
# crypto-checksumming or encryption) should be active:
# Each of the above parameters defaults to ACCEPTED.
# Each of the above parameters can have one of four possible values:
# value          meaning
# ACCEPTED     The service will be active if the other side of the
#          connection specifies "REQUESTED" or REQUIRED" and
#          there is a compatible algorithm available on the other
#          side; it will be inactive otherwise.
# REJECTED     The service must not be active, and the connection
#          will fail if the other side specifies "REQUIRED".
# REQUESTED     The service will be active if the other side specifies
#          "ACCEPTED", "REQUESTED", or "REQUIRED" and there is a
#          compatible algorithm available on the other side; it
#          will be inactive otherwise.
# REQUIRED     The service must be active, and the connection will
#          fail if the other side specifies "REJECTED" or if there
#          is no compatible algorithm on the other side.
#sqlnet.crypto_checksum_types_client
#sqlnet.crypto_checksum_types_server
#sqlnet.encryption_types_client
#sqlnet.encryption_types_server
# These parameters control which algorithms will be made available for
# each service on each end of a connection:
# The value of each of these parameters can be either a parenthesized
# list of algorithm names separated by commas or a single algorithm
# name.
# Encryption types can be: RC4_40, RC4_56, RC4_128, DES, DES40
# Encryption defaults to all the algorithms.
# Crypto checksum types can be: MD5
# Crypto checksum defaults to MD5.
#sqlnet.crypto_seed ="4fhfguweotcadsfdsafjkdsfqp5f201p45mxskdlfdasf"
#sqlnet.crypto_checksum_server = required
#sqlnet.encryption_server = required
# - Oracle Security Server ---------------------------------------------
#oss.source.my_wallet
# Syntax: A properly formatted NLNV list.
# Default: Platform specific. Unix: $HOME/oracle/oss
# The method for retrieving and storing my identity.
#oss.source.my_wallet
# =(source
# =(method=file)
# (method_data=/dve/asriniva/oss/wallet)
#oss.source.location
# Syntax: A properly formatted NLNV list.
# Default: Oracle method, oracle_security_service/oracle_security_service@oss
# The method for retrieving encrypted private keys.
#oss.source.location
# =(source
# =(method=oracle)
# (method_data=
# (sqlnet_address=andreoss)
# - Sqlnet(v2.x) and Net3.0 Client ------------------------------------------
# In the following descriptions, the term "client program" could mean
# either sqlplus, svrmgrl or any other OCI programs written by users
#trace_level_client = ADMIN
#Possible values: {OFF,USER,ADMIN,0-16}
#Default: OFF (0)
#Purpose: Indicates the level at which the client program
# is to be traced.
# Available Values:
# 0 or OFF - No Trace output
#     4 or USER - User trace information
#      10 or ADMIN - Administration trace information
#     16 or SUPPORT - Worldwide Customer Support trace information
#Supported since: v2.0
#trace_directory_client = /oracle/network/trace
#Possible values: Any valid directory path with write permission
#Default: $ORACLE_HOME/network/trace ($ORACLE_HOME=/oracle at customer
# site)
#Purpose: Indicates the name of the directory to which trace files from
# the client execution are written.
#Supported since: v2.0
#trace_file_client = /oracle/network/trace/cli.trc
#Possible values: Any valid file name
#Default:     $ORACLE_HOME/network/trace/cli.trc ($ORACLE_HOME =
#          /oracle at customer site)
#Purpose: Indicates the name of the file to which the execution trace
# of the client is written to.
#Supported since: v2.0
#trace_unique_client = ON
#Possible values: {ON, OFF}
#Default: OFF
#Purpose: Used to make each client trace file have a unique name to
#     prevent each trace file from being overwritten by successive
#     runs of the client program
#Supported since: v2.0
#log_directory_client = /oracle/network/log
#Possible values: Any valid directory pathname
#Default: $ORACLE_HOME/network/log ($ORACLE_HOME = /oracle at customer
#     site)
#Purpose: Indicates the name of the directory to which the client log file
#     is written to.
#Supported since: v2.0
#log_file_client = /oracle/network/log/sqlnet.log
#Possible values: This is a default value, u cannot change this
#Default: $ORACLE_HOME/network/log/sqlnet.log ($ORACLE_HOME=/oracle in
# customer site)
#Purpose: Indicates the name of the log file from a client program
#Supported since: v2.0
#log_directory_server = /oracle/network/trace
#Possible values: Any valid diretcory path with write permission
#Default: $ORACLE_HOME/network/trace ( $ORACLE_HOME=/oracle at customer
#     site)
#Purpose: Indicates the name of the directory to which log files from the
#      server are written
#Supported since: v2.0
#trace_directory_server = /oracle/network/trace
#Possible values: Any valid directory path with write permission
#Default: $ORACLE_HOME/network_trace ( $ORACLE_HOME=/oracle at customer
#     site)
#Purpose: Indicates the name of the directory to which trace files from
# the server are written
#Supported since: v2.0
#trace_file_server = /orace/network/trace/svr_<pid>.trc
#Possible values: Any valid filename
#Default: $ORACLE_HOME/network/trace/svr_<pid>.trc where <pid? stands for
# the process id of the server on UNIX systems
#Purpose: Indicates the name of the file to which the execution trace of
# the server program is written to.
#Supported since: v2.0
#trace_level_server = ADMIN
#Possible values: {OFF,USER,ADMIN,0-16}
#Default: OFF (0)
#Purpose: Indicates the level at which the server program
# is to be traced.
# Available Values:
# 0 or OFF - No Trace output
# 4 or USER - User trace information
# 10 or ADMIN - Administration trace information
# 16 or SUPPORT - Worldwide Customer Support trace information
#Supported since: v2.0
#use_dedicated_server = ON
#Possible values: {OFF,ON}
#Default:      OFF
#Purpose: Forces the listener to spawn a dedicated server process for
#     sessions from this client program.
#Supported since: v2.0
#use_cman = TRUE
#Possible values: {TRUE, FALSE}
#Default:     FALSE
#Purpose:
#Supported since: v3.0
#tnsping.trace_directory = /oracle/network/trace
#Possible values: Any valid directory pathname
#Default: $ORACLE_HOME/network/trace ($ORACLE_HOME=/oracle at customer
#     site)
#Purpose: Indicates the directory to which the execution trace from
#     the tnsping program is to be written to.
#Supported since: v2.0
#tnsping.trace_level = ADMIN
#Possible values: {OFF,USER,ADMIN,0-16}
#Default: OFF (0)
#Purpose: Indicates the level at which the server program
# is to be traced.
# Available Values:
# 0 or OFF - No Trace output
# 4 or USER - User trace information
# 10 or ADMIN - Administration trace information
# 16 or SUPPORT - Worldwide Customer Support trace information
#Supported since: v2.0
#sqlnet.expire_time = 10
#Possible values: 0-any valid positive integer! (in minutes)
#Default: 0 minutes
#Recommended value: 10 minutes
#Purpose: Indicates the time interval to send a probe to verify the
#     client session is alive (this is used to reclaim watseful
#     resources on a dead client)
#Supported since: v2.1
#sqlnet.client_registration = <unique_id>
#Possible values:
#Default: OFF
#Purpose: Sets a unique identifier for the client machine. This
#     identifier is then passed to the listener with any connection
#     request and will be included in the Audit Trail. The identifier
#     can be any alphanumeric string up to 128 characters long.
#Supported since: v2.3.2
#bequeath_detach = YES
#Possible values: {YES,NO}
#Default: NO
#Purpose: Turns off signal handling on UNIX systems. If signal handling
#     were not turned off and if client programs written by users make
#     use of signal handling they could interfere with Sqlnet/Net3.
#Supported since: v2.3.3
#automatic_ipc = OFF
#Possible values: {ON,OFF}
#Default: OFF
#Purpose: Force a session to use or not to use IPC addresses on the
#     client's node.
#Supported since: v2.0
#disable_oob = ON
#Possible values: {ON,OFF}
#Default: OFF
#Purpose: If the underlying transport protocol (TCP, DECnet,...) does
# not support Out-of-band breaks, then disable out-of-band
#     breaks
#Supported since: v2.0
#

ORA-01950

Hi All,
My DB Version: 10.2.0
OS: Solaris 5
Hi while one of my user trying to create a table he is getting below error:
create table emp
2 (ename varchar2(10));
create table emp
ERROR at line 1:
ORA-01950: Message 1950 not found; No message file for product=RDBMS,
facility=ORA; arguments: [TSI]
Can anyone tell me the reason for the same

Hi,
Check the user's privilege on the particular tablespace which he is trying to create the table.
Regards,
Mahesh.

Please Help with ORA-01031 - try to connect as sysdba

The log of the error is as follows:
D:\oracle\product\10.1.0\Db_ra>set oracle_sid
Environment variable oracle_sid not defined
D:\oracle\product\10.1.0\Db_ra>set oracle_sid=ra
D:\oracle\product\10.1.0\Db_ra>connect "/ as sysdba"
'connect' is not recognized as an internal or external command,
operable program or batch file.
D:\oracle\product\10.1.0\Db_ra>sqlplus "/ as sysdba"
SQL*Plus: Release 9.0.1.4.0 - Production on Mon Aug 29 12:31:17 2005
(c) Copyright 2001 Oracle Corporation. All rights reserved.
ERROR:
ORA-01031: insufficient privileges
Enter user-name: sys@ra as sysdba
Enter password:
Connected to an idle instance.
SQL> shutdown immediate;
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SQL> startup;
ORACLE instance started.
Total System Global Area 612368384 bytes
Fixed Size 790096 bytes
Variable Size 170127792 bytes
Database Buffers 440401920 bytes
Redo Buffers 1048576 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forced
I have been trying to work this out, but no success, Thanks in advance for your help.
JA

some part of the alert.log:
Instance terminated by USER, pid = 1212
ORA-1092 signalled during: ALTER DATABASE open ...
Dump file d:\oracle\product\10.1.0\admin\ra\bdump\alert_ra.log
Mon Aug 29 16:40:06 2005
ORACLE V10.1.0.2.0 - Production vsnsta=0
vsnsql=13 vsnxtr=3
Windows Server 2003 Version V5.2 Service Pack 1
CPU : 4 - type 586, 2 Physical Cores
Process Affinity: 0x00000000
Memory (A/P) : PH:3794M/4094M, PG:5823M/5973M, VA:1960M/2047M
Mon Aug 29 16:40:06 2005
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
KCCDEBUG_LEVEL = 0
Autotune of undo retention is turned on.
Dynamic strands is set to TRUE
Running with 2 shared and 18 private strand(s). Zero-copy redo is FALSE
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 10.1.0.2.0.
System parameters with non-default values:
processes = 150
__shared_pool_size = 159383552
__large_pool_size = 4194304
__java_pool_size = 4194304
sga_target = 612368384
control_files = D:\ORACLE\PRODUCT\10.1.0\RA\U02\ORADATA\RA\CONTROLFILE\O1_MF_1GHVSHLJ_.CTL, D:\ORACLE\PRODUCT\10.1.0\RA\U03\ORADATA\RA\CONTROLFILE\O1_MF_1GHVSHNZ_.CTL
db_block_size = 8192
__db_cache_size = 440401920
compatible = 10.1.0.2.0
log_archive_dest_1 = LOCATION=D:\oracle\product\10.1.0\ra\flash_recovery_area
log_archive_format = ARC%S_%R.%T
db_file_multiblock_read_count= 8
db_create_file_dest = D:\oracle\product\10.1.0\ra\u01\oradata
db_create_online_log_dest_1= D:\oracle\product\10.1.0\ra\u02\oradata
db_create_online_log_dest_2= D:\oracle\product\10.1.0\ra\u03\oradata
db_recovery_file_dest = D:\oracle\product\10.1.0\ra\flash_recovery_area
db_recovery_file_dest_size= 10485760000
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain = megatel.hn
dispatchers = (protocol=TCP)
shared_servers = 1
job_queue_processes = 10
background_dump_dest = D:\ORACLE\PRODUCT\10.1.0\ADMIN\RA\BDUMP
user_dump_dest = D:\ORACLE\PRODUCT\10.1.0\ADMIN\RA\UDUMP
core_dump_dest = D:\ORACLE\PRODUCT\10.1.0\ADMIN\RA\CDUMP
sort_area_size = 65536
db_name = ra
open_cursors = 300
pga_aggregate_target = 203423744
MMAN started with pid=3, OS id=1236
RECO started with pid=8, OS id=768
CJQ0 started with pid=9, OS id=1260
Mon Aug 29 16:40:08 2005
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
SMON started with pid=7, OS id=1256
CKPT started with pid=6, OS id=1252
Mon Aug 29 16:40:10 2005
alter database mount exclusive
PMON started with pid=2, OS id=1232
LGWR started with pid=5, OS id=1248
DBW0 started with pid=4, OS id=1244
Mon Aug 29 16:40:13 2005
Controlfile identified with block size 16384
Mon Aug 29 16:40:17 2005
Setting recovery target incarnation to 2
Mon Aug 29 16:40:17 2005
Successful mount of redo thread 1, with mount id 2665279661
Mon Aug 29 16:40:17 2005
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Mon Aug 29 16:40:18 2005
alter database open
Mon Aug 29 16:40:18 2005
Beginning crash recovery of 1 threads
attempting to start a parallel recovery with 3 processes
parallel recovery started with 3 processes
Mon Aug 29 16:40:19 2005
Started first pass scan
Log resilvered from block #210 to block #212
Mon Aug 29 16:40:19 2005
Completed first pass scan
210 redo blocks read, 131 data blocks need recovery
Mon Aug 29 16:40:19 2005
Started redo application at
Thread 1: logseq 2213, block 3, scn 0.0
Recovery of Online Redo Log: Thread 1 Group 1 Seq 2213 Reading mem 0
Mem# 0 errs 0: D:\ORACLE\PRODUCT\10.1.0\RA\U02\ORADATA\RA\ONLINELOG\O1_MF_1_1GHVSJOX_.LOG
Mem# 1 errs 0: D:\ORACLE\PRODUCT\10.1.0\RA\U03\ORADATA\RA\ONLINELOG\O1_MF_1_1GHVSJW8_.LOG
Mon Aug 29 16:40:20 2005
Completed redo application
Mon Aug 29 16:40:20 2005
Completed crash recovery at
Thread 1: logseq 2213, block 213, scn 0.8340211
131 data blocks read, 131 data blocks written, 210 redo blocks read
Mon Aug 29 16:40:21 2005
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=15, OS id=2064
ARC0: Archival started
Mon Aug 29 16:40:21 2005
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=16, OS id=2076
ARC1: Archival started
Mon Aug 29 16:40:21 2005
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Mon Aug 29 16:40:21 2005
ARC1: Becoming the heartbeat ARCH
Mon Aug 29 16:40:21 2005
LGWR: Primary database is in CLUSTER CONSISTENT mode
Thread 1 advanced to log sequence 2214
Maximum redo generation record size = 120832 bytes
Maximum redo generation change vector size = 116476 bytes
Private_strands 7 at log switch
Thread 1 opened at log sequence 2214
Current log# 2 seq# 2214 mem# 0: D:\ORACLE\PRODUCT\10.1.0\RA\U02\ORADATA\RA\ONLINELOG\O1_MF_2_1GHVSK69_.LOG
Current log# 2 seq# 2214 mem# 1: D:\ORACLE\PRODUCT\10.1.0\RA\U03\ORADATA\RA\ONLINELOG\O1_MF_2_1GHVSKF3_.LOG
Successful open of redo thread 1
Mon Aug 29 16:40:21 2005
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Aug 29 16:40:21 2005
ARC0: Evaluating archive log 1 thread 1 sequence 2213
Mon Aug 29 16:40:21 2005
ARC1: Evaluating archive log 1 thread 1 sequence 2213
ARC1: Unable to archive log 1 thread 1 sequence 2213
Log actively being archived by another process
ARC1: Evaluating archive log 1 thread 1 sequence 2213
Mon Aug 29 16:40:22 2005
SMON: enabling cache recovery
Mon Aug 29 16:40:22 2005
ARC1: Unable to archive log 1 thread 1 sequence 2213
Log actively being archived by another process
ARC1: Evaluating archive log 1 thread 1 sequence 2213
ARC1: Unable to archive log 1 thread 1 sequence 2213
Log actively being archived by another process
Mon Aug 29 16:40:22 2005
Committing creation of archivelog 'D:\ORACLE\PRODUCT\10.1.0\RA\FLASH_RECOVERY_AREA\ARC02213_0564762704.001'
Mon Aug 29 16:40:23 2005
Successfully onlined Undo Tablespace 1.
Mon Aug 29 16:40:23 2005
SMON: enabling tx recovery
Mon Aug 29 16:40:23 2005
Database Characterset is WE8MSWIN1252
Mon Aug 29 16:40:23 2005
Published database character set on system events channel
Mon Aug 29 16:40:23 2005
All processes have switched to database character set
Mon Aug 29 16:40:25 2005
Starting background process QMNC
QMNC started with pid=17, OS id=2152
Mon Aug 29 16:40:27 2005
replication_dependency_tracking turned off (no async multimaster replication found)
Mon Aug 29 16:40:28 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\udump\ra_ora_1304.trc:
ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [], [], [], [], [], [], []
Mon Aug 29 16:40:30 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\udump\ra_ora_1304.trc:
ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [], [], [], [], [], [], []
Mon Aug 29 16:40:31 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\udump\ra_ora_1304.trc:
ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [], [], [], [], [], [], []
Mon Aug 29 16:40:32 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\udump\ra_ora_1304.trc:
ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [], [], [], [], [], [], []
Error 600 happened during db open, shutting down database
USER: terminating instance due to error 600
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_mman_1236.trc:
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_p002_1984.trc:
ORA-00600: internal error code, arguments: [15784], [600], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_p001_1980.trc:
ORA-00600: internal error code, arguments: [15784], [600], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_p000_1568.trc:
ORA-00600: internal error code, arguments: [15784], [600], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_reco_768.trc:
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_smon_1256.trc:
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_ckpt_1252.trc:
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_lgwr_1248.trc:
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:34 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_dbw0_1244.trc:
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Instance terminated by USER, pid = 1304
ORA-1092 signalled during: alter database open...

ORA-01031: insufficient privileges in PL/SQL but not in SQL

I have problem with following situation.
I switched current schema to another one "ban", and selected 4 rows from "ed"
alter session set current_schema=ban;
SELECT * FROM ed.PS WHERE ROWNUM < 5;
the output is OK, and I get 4 rows like
ID_S ID_Z
1000152 1
1000153 1
1000154 1
1000155 1
but following procedure is compiled with warning
create or replace
procedure proc1
as
rowcnt int;
begin
select count(*) into rowcnt from ed.PS where rownum < 5;
end;
"Create procedure, executed in 0.031 sec."
5,29,PL/SQL: ORA-01031: insufficient privileges
5,2,PL/SQL: SQL Statement ignored
,,Total execution time 0.047 sec.
Could you help me why SELECT does work in SQL but not in PL/SQL procedure?
Thanks.
Message was edited by:
MattSk

Privs granted via a role are only valid from SQL - and not from/within stored PL/SQL code.
Quoting Tom's (from http://asktom.oracle.com) response to this:I did address this role thing in my book Expert one on one Oracle:
<quote>
What happens when we compile a Definer rights procedure
When we compile the procedure into the database, a couple of things happen with regards to
privileges. We will list them here briefly and then go into more detail:
q    All of the objects the procedure statically accesses (anything not accessed via dynamic SQL)
are verified for existence. Names are resolved via the standard scoping rules as they apply to the
definer of the procedure.
q    All of the objects it accesses are verified to ensure that the required access mode will be
available. That is, if an attempt to UPDATE T is made - Oracle will verify the definer or PUBLIC
has the ability to UPDATE T without use of any ROLES.
q    A dependency between this procedure and the referenced objects is setup and maintained. If
this procedure SELECTS FROM T, then a dependency between T and this procedure is recorded
If, for example, I have a procedure P that attempted to 'SELECT * FROM T', the compiler will first
resolve T into a fully qualified referenced. T is an ambiguous name in the database - there may be
many T's to choose from. Oracle will follow its scoping rules to figure out what T really is, any
synonyms will be resolved to their base objects and the schema name will be associated with the
object as well. It does this name resolution using the rules for the currently logged in user (the
definer). That is, it will look for an object owned by this user called T and use that first (this
includes private synonyms), then it will look at public synonyms and try to find T and so on.
Once it determines exactly what T refers to - Oracle will determine if the mode in which we are
attempting to access T is permitted.   In this case, if we as the definer of the procedure either
owns the object T or has been granted SELECT on T directly or PUBLIC was granted SELECT, the
procedure will compile. If we do not have access to an object called T by a direct grant - the
procedure P will fail compilation. So, when the object (the stored procedure that references T) is
compiled into the database, Oracle will do these checks - and if they "pass", Oracle will compile
the procedure, store the binary code for the procedure and set up a dependency between this
procedure and this object T. This dependency is used to invalidate the procedure later - in the
event something happens to T that necessitates the stored procedures recompilation. For example,
if at a later date - we REVOKE SELECT ON T from the owner of this stored procedure - Oracle will
mark all stored procedures this user has that are dependent on T, that refer to T, as INVALID. If
we ALTER T ADD some column, Oracle can invalidate all of the dependent procedures. This will cause
them to be recompiled automatically upon their next execution.
What is interesting to note is not only what is stored but what is not stored when we compile the
object. Oracle does not store the exact privilege that was used to get access to T. We only know
that procedure P is dependent on T. We do not know if the reason we were allowed to see T was due
to:
q    A grant given to the definer of the procedure (grant select on T to user)
q    A grant to public on T (grant select on T to public)
q    The user having the SELECT ANY TABLE privilege
The reason it is interesting to note what is not stored is that a REVOKE of any of the above will
cause the procedure P to become invalid. If all three privileges were in place when the procedure
was compiled, a revoke of ANY of them will invalidate the procedure - forcing it to be recompiled
before it is executed again. Since all three privileges were in place when we created the procedure
- it will compile successfully (until we revoke all three that is). This recompilation will happen
automatically the next time that the procedure is executed.
Now that the procedure is compiled into the database and the dependencies are all setup, we can
execute the procedure and be assured that it knows what T is and that T is accessible. If something
happens to either the table T or to the set of base privileges available to the definer of this
procedure that might affect our ability to access T -- our procedure will become invalid and will
need to be recompiled.
This leads into why ROLES are not enabled during the compilation and execution of a stored
procedure in Definer rights mode. Oracle is not storing exactly WHY you are allowed to access T -
only that you are. Any change to your privileges that might cause access to T to go away will cause
the procedure to become invalid and necessitate its recompilation. Without roles - that means only
'REVOKE SELECT ANY TABLE' or 'REVOKE SELECT ON T' from the Definer account or from PUBLIC. With
roles - it greatly expands the number of times we would invalidate this procedure. If some role
that was granted to some role that was granted to this user was modified, this procedure might go
invalid, even if we did not rely on that privilege from that role. ROLES are designed to be very
fluid when compared to GRANTS given to users as far as privilege sets go. For a minute, let's say
that roles did give us privileges in stored objects. Now, most any time anything was revoked from
ANY ROLE we had, or any role any role we have has (and so on -- roles can and are granted to roles)
-- many of our objects would become invalid. Think about that, REVOKE some privilege from a ROLE
and suddenly your entire database must be recompiled! Consider the impact of revoking some system
privilege from a ROLE, it would be like doing that to PUBLIC is now, don't do it, just think about
it (if you do revoke some powerful system privilege from PUBLIC, do it on a test database). If
PUBLIC had been granted SELECT ANY TABLE, revoking that privilege would cause virtually every
procedure in the database to go invalid. If procedures relied on roles, virtually every procedure
in the database would constantly become invalid due to small changes in permissions. Since one of
the major benefits of procedures is the 'compile once, run many' model - this would be disastrous
for performance.
Also consider that roles may be
q    Non-default: If I have a non-default role and I enable it and I compile a procedure that
relies on those privileges, when I log out I no longer have that role -- should my procedure become
invalid -- why? Why not? I could easily argue both sides.
q    Password Protected: if someone changes the password on a ROLE, should everything that might
need that role be recompiled? I might be granted that role but not knowing the new password - I
can no longer enable it. Should the privileges still be available? Why or Why not? Again, arguing
either side of this is easy. There are cases for and against each.
The bottom line with respect to roles in procedures with Definer rights are:
q    You have thousands or tens of thousands of end users. They don't create stored objects (they
should not). We need roles to manage these people. Roles are designed for these people (end users).
q    You have far fewer application schema's (things that hold stored objects). For these we want
to be explicit as to exactly what privileges we need and why. In security terms this is called the
concept of 'least privileges', you want to specifically say what privilege you need and why you
need it. If you inherit lots of privileges from roles you cannot do that effectively. We can manage
to be explicit since the number of development schemas is SMALL (but the number of end users is
large)...
q    Having the direct relationship between the definer and the procedure makes for a much more
efficient database. We recompile objects only when we need to, not when we might need to. It is a
large efficiency enhancement.
</quote>

ORA-00604 error occured at recursive level1,ORA-20123 Insufficient privileges: you cannot drop table cls_lrn_tab_unique TABLE,ORA-06512

Dear All,
I created one table like
create table cls_lrn_tab_unique (F_no number unique UK_F_NO );
after performing some operations I want to delete the same.
At that time i got following error. Please help me and tell what is the reason for the error.
ORA-00604 error occured at recursive level1
ORA-20123 Insufficient privileges: you cannot drop table cls_lrn_tab_unique TABLE,
ORA-06512 at line no 2
Thanks and Regards
Prasad

26bffcad-f9a2-4dcf-afa0-e1e33d0281bf wrote:
Dear All,
I created one table like
create table cls_lrn_tab_unique (F_no number unique UK_F_NO );
after performing some operations I want to delete the same.
At that time i got following error. Please help me and tell what is the reason for the error.
ORA-00604 error occured at recursive level1
ORA-20123 Insufficient privileges: you cannot drop table cls_lrn_tab_unique TABLE,
ORA-06512 at line no 2
Thanks and Regards
Prasad
ORA-20123 is a localized/customized error code & message; therefore any solution depends upon what is unique inside your DB now.
I suspect that some sort of TRIGGER exists, which throws posted error, but this is just idle speculation on my part.
How do I ask a question on the forums?
https://forums.oracle.com/message/9362002#9362002

Help Request: ORA-01950: no privileges on tablespace

Similar Messages

Maybe you are looking for