Is possible to connect db with sys/sys as sysdba in SQLPLUS utility

Hi all,
I'm using windows 2000 with oracle 10.1.0
I have to connect server through SQLPLUS utility. I can able to connect system/manager@instance_name
From system user, i cant able to query >archive log list; .Im getting error as permission denaid.
is any possbilities there to login as super user(sys/sys as sysdba) in SQLLUS utility.
Thanks

connect sys/sys@instance_name as sysdbaUses password file in $ORACLE_HOME/dbs, connecting through SQL*NET
connect sys/sys as sysdbaUses the BEQ protocol to connect to the database process directly and uses OS authentication, meaning your can use whatever username or password, it does not matter, same as connect / as sysdba - It will always connect to the SYS schema regardless. For this to work, your account needs to be in the SYSDBA group. (DBA - Linux, OSDBA - Windows).
See the oracle standard documentation for creating a password file under Windows.
When you have created the passwd file, you can reset the password using
sqlplus / as sysdba
alter user sys identified by 'password' ;

Similar Messages

Is it possible to connect indesign with database/OOD...

Hello fellow Indesign user,
Not sure if this question belongs here or in scripting...
I'm just a moderate user in ID CS4 and I got this daunting task to find/invest a way to use Indesign (our existing layout software) to create "brochures/instruction manuals" using databases or OOD. Meanings, use a template, add a code that corresponds to a similar code with pre-defined data-entity in a database/OOD, and automatically add the text/pictures from the database/OOD.
We are not talking about addresses or simple things like that, but brochures and instruction manuals in different languages with different or similar operation for each machine. Some instructions are the same and some are not. Get my drift?
We are using ID Cs4 in the company right now, not the smartest tool to use when producing 25 different brochures/technical manuals with different languages. Changing one content in one manual, meaning we have to change all 25 brochures/manuals.... manually...
Many of you may think -"why did you start ID in the first place". The answer: I don't know, I wasn't here then... It is not until now they discovered -"Oh, we need a new system… " and guess who got the task to evaluate it…
I need to know if it is possible and to what extent we can use ID with database or an OOD-system to retrieve data (mostly custom data with bulletin, font, size, pictures, etc).
Articles, links and other information would be very helpful….
Thanks!
//Vincent

What kind TM exist out there and is it possible to integrate it with ID? (I can probably check Wikipedia, but it feels correct to ask the right question to ask to the right person here. How does your firm manage multilingual contents in ID? You gotto have the same problem as I do, at least to some extent…
How is it even possible to have an automated system and still have that flexible design freedom in ID..? Many questions here…
To invest a complete new system is not an option anymore. I made some calculation and plenty of phone calls. The figures does not look good at all… it’s simply not worth the time and money. So what are the options, if we keep ID in the firm?
Well, I should have had lots of time to answer your questions this evening, but it turns out that we're both out of luck. I'll cover a few things quickly to give you some Google-fodder:
1) Okay, I won't suggest expensive commercial solutions.
2) Read up about how to flow XML content into and out of ID
2b) Store your content in the DB of your choice, spit out XML, and then update your INDDs with it.
3) Think about an open-source TM app like OmegaT
4) Do you do all of your translations in-house? If not, ask your suppliers how they work.
5) But really, if you don't have a completely obsessive person in charge of making sure everything is up to date, you're asking for trouble. I'm reminded of a quote by Edward Tufte who was talking about project management; I can't remember the quote, but the idea boiled down to the fact that you can do just as good a job with whiteboards as you can with databases. At least right now you know that you haven't kept all versions up to date... if you were housing all your content in a database, then the update process is somewhat hidden from you, and you wouldn't know if something broke unlesss you caught it in QA. If you're not doing all the updates... then you can't do good QA.This is a recipe for disaster.
5b) Establish a good workflow with whatever tools you have (database, whiteboards, little strings with knots tied in 'em, notches carved in the thighbones of extinct birds of prey, etc.) and give someone the power to sanction/punish/fire people who disobey workflow rules. I am not kidding.
I will make more useful suggestions (suggestions more useful than 5b, at any rate) in the near future.

Is it possible to connect iphone5 with ipad3 via bluetooth( if yes tell me how)

Im asking this again as its not connecting via bluetooth but gets connected with personal hotspot using my expensive internet pack...

Personal Hotspot is, in fact, the only way to pair your phone & iPad by Bluetooth. File transfer, by Bluetooth, has never been supported on any iPhone.

Is it possible to connect labview with opc server without using NI dsc Module ?

Hellow sir,
I want to get data over labview using OPC server and i am not using any dsc module vi (Alams, print, GUI, security).I am using share variable to get data from OPC server to labview. Now i want to deploy that application to third party computer. (where there is no NI software is installed)
i am using labview 8.6 and 2009.
Many ? like....
1) what is the procedure to install that application in third party computer.
2) Do i need to use my dsc run time licence..?
waiting for your valuable feed back.
Thank you.
CLAD
Labiew programmer

Hi, When you connect to NI OPC Server by creating New I/O Server > OPC Client. You will see all registered OPC Servers running on local machine or remote machine. I used KepServerEx from Kepware and LSIS OPC Server from LG with no problems. Just make sure that the OPC server is running.
Hope it helps
Waleed El-Badry MSc.,MCPD, ISTQB Certified Tester
Assistant Lecturer
Mechatronics Department
Faculty of Engineering
Misr University for Science & Technology
Attachments:
LG.png ‏57 KB

Is it possible to connect MBPR with Cinema HD Display 30" 's Firewire Port for iSight

I want to buy a external iSight for my old Cinema HD Display 30" ,as i don't have enough space to open my notebook to use the built-in iSight camera.
I know they are very old item, but i think they have very beautiful design and great quality, i want to use them
I have already using the 30" Display by Dual Link-DVI converter, i don't have any firewire device, i don't know is it still work for using Thunderbolt (MacBook) -> Firewire800 (Adapter)-> Firewire400(converter) -> Cinema HD Display FW port -> external iSight
or is there any other solution for me?
or should i give up this setting
As i don't want to use other brand USB camera, other brand no need to consider.
Thanks for attention

mluk6328 wrote: I want to buy a external iSight ... I know they are very old item, but ...
Test BEFORE you buy. More discussion in this old thread: http://discussions.apple.com/thread/2450744 .

Cannot connect with "SYS@MYDB AS SYSDBA"

Hello,
I logged in as os user oracle and do:
sqlplus "SYS@MYDB AS SYSDBA"
After entering the right password I get this error:
This returns a ORA-01031: insufficient privileges
MYDB is a local database.
sqlplus "SYS AS SYSDBA"
and
sqlplus "/ AS SYSDBA"
both work.
I don't use password files (and I don't want to).
Doing the first statement on a remote database (Win2K) works also. If the remote database is a Linux
machine I receive again a ORA-01031.
Any ideas whats wrong here?
Kai

ensure:
a. The listener is running.Is running.
b. there is a definition for MYDB in the local tnsnames file.Is done. There is also oracle names running. sqlplus scott/tiger@MYDB works. So no problem here.
c. There is an entry like: remote_login_passwordfile=EXCLUSIVE or SHARED in your init file.I don't want to use a password file.
More ideas?
Kai

Unable to connect to sqlplus .. sys as sysdba .. No listener in Oracle 11G

Hi ,
I have installed Oracle 11.2.0 . When connecting to sqlplus with sys as sysdba . Getting error as NO listener .
I started listener . But finally getting the message as
The listener supports no services
The command completed successfully
Kindly help

I am getting the same message
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/product/11.2.0/dbhome_1/log/diag/tnslsnr/oracledb/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracledb.example.com)(PORT=1521)))
The listener supports no services
The command completed successfully
I don't find the services entry here .

Audigy SE: Possibility to connect with front panel audio in/

I have a case which has an audio in and out jack on the frontcase. Is it possible to connect these with an connector on the Audigy SE?

Quote from: msiAMD6400 on 25-December-07, 21:57:43
My "disable front panel detection" is unchecked.
It is not clear to me if you were able to check (enable) the box. The setting you need is "disable front panel detection" checked; that means the motherboard delivers the output to front panel, irrespective of there is a headphone connected or not.
If you are unable to check that box, i am not sure where is the problem. If you can, i expect you see a pop up window asking you what you have connected to the front panel, by default it should be an audio output option like headphone. Make sure, as I mentioned already, that you can see inside the audio software window the status of all the audio input/output sockets in different colours. The 2 icons representing the frontpanel should be highlighted and you should be able to designate what output/input you want from each of them. If this doesn't happen there is no point in connecting the audio out cable to the header (unless you have the appropriate MSI frontpanel cable which provides jack detection)
If you have successfully disabled the detection, you just need 3 wires to get output (things work when they are simple). Forget about the looping; you don't need them if jack detection is disabled.
I suggest you connect the 3 wires to the pins as shown in the manual.
Note the pin configuration diagram for the "JAUD1" header. I think the common/ground wire from your headphone socket should be to pin 2, Right out to pin 5 and left out to pin 9.
Let us know of your results.
Siby

Connect Problems with Oracle Database Express Edition 11g Release 2

Hello,
I am a student trying to install Oracle Database Express Edition 11g Release 2 and SQL Developer on my home system, Win7 64Bit, in order to practice some things I've learned from me DBA class and Developer classes.
Anyway, I have everything installed, but I am having difficulty connecting as SYS or SYSDBA in the 'Run SQL Command Line', I keep getting the ORA-01017: invalid username/password: logon denied.
However, If i select the 'Start Database' I get this:
C:\oraclexe\app\oracle\product\11.2.0\server\bin>
and I can type sqlplus / as sysdba and it starts up just fine and show user lists me as "SYS".
but if I go back to 'Run SQL Command Line' I still cannot connect as SYS or SYSDBA...I find this both confusing and frustrating. I don't know if I am in different instances or something like that, but I seem to be limited to connecting only as "SYSTEM". I need SYS because I want to practice creating datafiles, instances and things like that, but I seem to be lost.
Also, I am trying to create a new DB connection with SQL Developer and I can only us SYSTEM for my login which, if I understand correctly, will limit my privileges. Again When I try to sign in with SYS or SYSDBA I get error'd out. When I installed Ora11gDBExpress I was prompted in input a single password that was supposed to grant me access as SYS or SYSTEM, but I am limited to only SYSTEM for some reason.
So, I am looking for help/guidance as to what to do.
Thanks in advance for any and all help,
Warren

General rule of thumb, don't use sysdba unless you want to shut down the database, or grant a database user privileges on a sys object.
A SYSTEM connection is not "limiting", it has the DBA role which means a user with a system connection can do most anything needed, including select/update/delete/drop any user's objects as well as change parameters in the instance.
The system user can indeed add datafiles, tablespaces, etc. The instance and database should already be created as long as the installer completed all its chores correctly. For XE, per the license agreement only one instance can run on one host. If you want to try creating a database, it will require shutting down the XE instance and creating a new database service, creating the database, and installing the system catalog and any other optional components desired. Good practice indeed, but a bit advanced for the new user.
Do create users for schemas ... connect system; create user <username> identified by <password> and connect <username> for the schemas (a collection of objects) within the database. Grant the resource and create session privilege to <username> to allow the database user the ability to create tables, indexes, stored procedures, etc.
There is no "or" in a sys as sysdba connection, from 10g onwards a sys connection requires using the sysdba privilege. To enable a sysdba connection, add your host user to the ORA_DBA group on the host. To verify the OS users in the ORA_DBA group, this might work for win7, in a cmd box ...
$ net localgroup ora_dba
...If your OS user is in the ora_dba group the sys as sysdba password is not relevant, you can in fact type anything for a password. If you wish to connect with the sysdba privilege from a remote client, that is a bit different and requires knowing the password set in the instance password file. Which should be set the same as the system password defined in the installer, but you can change that by creating a new password file. Another slightly advanced topic.
In Windows IMHO its better to leave the listener and database set to Manual start (in the services applet, Start/Run/services.msc) and start the listener, then the database, when its needed. At least for an XE instance, as its intended for practice and learning RDBMS management.
Edited by: clcarter on Mar 2, 2012 6:19 PM
fix typos

Possible to connect to wlan via PC trough n95?

Hi there!
Is it possible to connect wlan with my computer using my n95? I can connect to our wlan with my phone but I can't find such a option on pc suite.
Thank you.

The only option on pcsuite is to connect to your providers 3g/gsm network and use your device as modem. Using your device as an WIFI usb dongle is not possible.

Officejet 5610 - can I connect it with the usb to a router home network, instead to connect to the c

Hi, Is it possible to connect Offcejet5610 with usb to a router home network, instead to a computer?

Yes, if the router supports USB printers (not just hard drives). Also, the only function that will be supported will be printing, nothing else.
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

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
#

Connection Problem to sys with @ TNSNAMES ?

Hi oracle gurus,
OS: Solaris 10
DB: Oracle Database Release 10.2.0.3.0
I have problem to connect to sys as SYSDBA throw @<TNSNAMES>
I did the follow test below:
TEST 1: OK
SQL> connect sys/xxx as sysdba
Connected.
TEST 2: OK
SQL> connect sysman/xxx@OEMREP
Connected.
TEST 3: FAIL?
SQL> connect sys/xxx@OEMREP as sysdba
ERROR:
ORA-01017: invalid username/password; logon denied
Does anyone now why test 3 fail?
Its NOT because of wrong password.
Best Regards - Tommy
Message was edited by:
T.Rönnholm

Hi,
>>I have problem to connect to sys as SYSDBA throw @<TNSNAMES>
Certainly you are typing a wrong password. As Werner said, in server side, doesn't matter what you typed id you are using OS authentication:
oracle@icaro:~> sqlplus blablabla/blablabla... as sysdba
SQL*Plus: Release 10.1.0.2.0 - Production on Fri Dec 7 15:07:07 2007
Copyright (c) 1982, 2004, Oracle. All rights reserved.
Conected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SYS@BD1> show user
USER e "SYS"In resume, when you connect to the database by using the SYSDBA privilege, you are connected to the SYS schema.
Cheers
Legatti

Problem in login with sys

hi,
i have a problem in login with sys, the situation as follows:
1- when i try to connect using : sqlplus "/as sysdba" or "sys/password as sysdba" it connect me to the DB.
2- when i try to connect : sqlplus "sys/password@MYDB as sysdba" it gives me "ORA-01017: invalid username/password; logon denied".
3- when i try to connect with another user i.e : sqlplus "system/password@MYDB" it connect me to the DB.
DB version : 9.2.0.8
OS version : Solaris 10
please advice...

1- when i try to connect using : sqlplus "/as sysdba"
or "sys/password as sysdba" it connect me to
the DB.This works anyway, because you're authenticated by OS. Example :
SQL> conn sys/aaaa as sysdba
Connected.
SQL> conn sys/bbbb as sysdba
Connected.
SQL>
2- when i try to connect : sqlplus "sys/password@MYDB
as sysdba" it gives me "ORA-01017: invalid
username/password; logon denied".Here you need the real password, so make sure you're using the correct one.

Fail to logon with SYS user: ORA-01031: insufficient privileges

Hello,
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
OS: CentOS 5.5
I fail to log on with SYS user through PL/SQL Developer. I receive the error: ORA-01031: insufficient privileges. PL/SQL Developer is installed on Windows 7 Professional. Oracle Client Version is 11.2.0.1.0. However I logon successfully with SYSMAN and SYSTEM.
For those who might ask whether I try to connect "as sysdba" when I use SYS user, the answer is YES, I do.
Besides I think the name of the tool (PL/SQL Developer) doesn't matter because I think I'll face the same error with any other tool (but I mentioned it just in case).
On server side I have no issues with SYS user. I can connect through SQLPlus with connect / as sysdba or connect "/as sysdba" faultlessly.
The initialization parameter sec_case_sensitive_logon is set to FALSE
SQL> show parameter sensi
NAME TYPE VALUE
sec_case_sensitive_logon boolean FALSE
I'm using local naming to connect and on client side I've a tnanames.ora file. The sqlnet.ora file looks like this:
SQLNET.AUTHENTICATION_SERVICES= (NTS)
NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)I read in this forum (another thread) about using a password file. I created a password file using orapwd this way:
orapwd file=orapwDB11G2 entries=100 ignorecase=y password=a_passwordwhere I replaced "a_password" with the SYS password.
Actually I'm not sure the client is influenced by the password file anyway because I tell it to use local naming.
Any clues?
Thank you very much!

Verdi wrote:
Hello, Chinar, AlexeyDev,
ORACLE_SID variable is:
[oracle@localhost bin]$ echo $ORACLE_SID
planetThe directory $ORACLE_HOME/dbs:
[oracle@localhost ~]$ ls -l $ORACLE_HOME/dbs
total 28020
-rw-rw---- 1 oracle oinstall    1544 Apr 10 12:43 hc_DBUA0.dat
-rw-rw---- 1 oracle oinstall    1544 Apr 27 18:02 hc_planet.dat
-rw-r--r-- 1 oracle oinstall    2851 May 15 2009 init.ora
-rw-r--r-- 1 oracle oinstall    2966 Apr 26 16:33 initplanet.ora
-rw-r----- 1 oracle oinstall      24 Apr 1 18:22 lkPLANET
-rw-r----- 1 oracle oinstall 9519104 Apr 27 18:43 ora_control1
-rw-r----- 1 oracle oinstall 9519104 Apr 27 18:43 ora_control2
drwx------ 2 oracle oinstall    4096 Apr 10 12:43 peshm_DBUA0_0
drwx------ 2 oracle oinstall    4096 Apr 1 18:19 peshm_planet_0
-rw-r----- 1 oracle oinstall 9519104 Apr 8 11:25 snapcf_planet.f
-rw-r----- 1 oracle oinstall    2560 Apr 27 18:41 spfileplanet.oraThe value of the parameter remote_login_passwordfile is:
*.remote_login_passwordfile='EXCLUSIVE'
I start up the instance using the spfile.As a side observation, it appears you have two control files also in this directory. That is risky, and goes against the intent of having multiplexed the control file. Ideally they would be on separate disk devices - including separate controllers, but at the very least they should be in directories that are separate all the way back to the root directory. If you can't protect against hardware failure, at least protect against human failure.

Is possible to connect db with sys/sys as sysdba in SQLPLUS utility

Similar Messages

Maybe you are looking for