Bequeath connection 8i - 9i

I have Oracle Server9i and Oracle Client 8i on the same machine (HP TRU64-UNIX).
For compatibility reason with another product, I have to use Oracle 8i client to connect to Oracle 9i database.
If I set the environment variable ORACLE_HOME (9i) and ORACLE_SID, I can get a bequeath session without using net service name.
Is it possible to get a bequeath session to a 9i database setting the environment variable ORACLE_HOME to the path of Oracle Client 8i?
Tank you,
Fabio

Try this (from Metalink), where forms is your client side:
Note:253099.1
Subject: Setup Forms to Connect to Database with no Database Listener
Type: HOWTO
Status: PUBLISHED
Content Type: TEXT/X-HTML
Creation Date: 01-MAY-2002
Last Revision Date: 01-APR-2004
goal: How To Setup Developer Forms or Reports to Connect to the Database
without a Database Listener.
fact: HP 9000 Series HP-UX (64-bit)
fact: Oracle Reports Developer 6.0.8
fix:
Normally Forms and Reports in a separate oracle home requires the database
listener to be up and running. Separate oracle homes are mandatory with the
modern product - old versions of forms could live in the same oracle home as
very specific versions of older databases, and connect without the listener,
but this is no longer the case.
However you can get round this by setting the environment variable TWO_TASK
to a custom tnsnames.ora entry called 'bequeath'. To enable this, the following
code has to be entered into the tnsnames.ora file:
bequeath =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=BEQ)
(PROG=<database_oracle_home>/bin/oracle)
(ARGV0=oracle<oracle_sid>)
(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))')
(ENVS='ORACLE_HOME=<database_oracle_home>,ORACLE_SID=<
database_oracle_sid>')
(DETACH=NO)
(CONNECT_DATA=(SID=<oracle_sid>))
To work out what you should enter for ARGV0, do a
ps -eaf | grep oracle
- one of the processes should show as oracle<SID> where SID is your
database SID. For example, if your SID is fred, the process name
should be 'oraclefred' - this is the string you enter in the ARGV0= line.
Come out of forms, stop the database listener in a separate database session
with
lsnrctl stop
start forms up again and now you should be able to connect using :
scott
tiger
bequeath
ciao,
Orlando

Similar Messages

Impdp network mode can use bequeath connection?

Hi, I'm going to import a single database using FS to a RAC on ASM both are in same server running oracle 11.2.0.3. So I was wondering if can I use network link mode of impdp without setting up a listener using 10gb Ethernet interface ?
I don’t want to incur the overhead of the tcp network layer because both DB single and Rac are on the same server.
Thanks in advance

Hi, thanks for you time
here I am with bad results.
more tnsnames.ora
BOSS_DB =
(DESCRIPTION =
    (ADDRESS =
      (PROTOCOL = BEQ)
      (PROGRAM = /oracle/REMP/oradb/11.2.0.3/bin/oracle)
      (argv0 = oracleQA3)
      (args = '(DESCRIPTION = (LOCAL=YES) (ADDRESS=(PROTOCOL=BEQ)))')
      (envs = 'ORACLE_HOME=/oracle/REMP/oradb/11.2.0.3,ORACLE_SID=QA3')
    (CONNECT_DATA = (SID = QA3))
rmdy01:/oracle/REMP/oradb/11.2.0.3/network/admin>sqlplus system@BOSS_DB
SQL*Plus: Release 11.2.0.3.0 Production on Wed Feb 13 14:53:44 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
SQL> select instance_name from v$instance;
INSTANCE_NAME
QA3
SQL> select network_service_banner from v$session_connect_info where sid=sys_context('userenv','sid');
NETWORK_SERVICE_BANNER
Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.2.0.3.0 - Production
Oracle Advanced Security: authentication service for HPUX: Version 11.2.0.3.0 -
Production
Oracle Advanced Security: encryption service for HPUX: Version 11.2.0.3.0 - Prod
uction
Oracle Advanced Security: crypto-checksumming service for HPUX: Version 11.2.0.3
.0 - Production
SQL>As you can see I can connect from sqlplus using Bequeath Protocol.
Now from the other database, I Can Not create db_link, here's
SQL> select instance_name from v$instance;
INSTANCE_NAME
RMDY1
SQL> create public database link BOSS connect to system identified by thepass using 'BOSS_DB';
create public database link BOSS connect to system identified by nosystem using 'BOSS_DB'
ERROR at line 1:
ORA-09276: All bequeath database links must be loopback database linksIs There something wrong with Bequeath connection from dblink or Do I use IPC instead?
Best regards
Edited by: Law on Feb 13, 2013 12:59 PM
Edited by: Law on Feb 14, 2013 7:56 PM

What means "bequeathed connection" ??

Hi,
I'm making different tests with sqlnet.expire_time parameter you configure in sqlnet.ora file.
I have read in different sites that this parameter can't be used in "bequeathed connections", for example, you find this in http://www.oracle-training.cc/10g_299.htm.
Someone can tell me what bequeathed connection means or where I will find documentation about it?
Thanks,
Juan Moratilla Peón
from Telefonica I+D

user10202447 wrote:
Someone can tell me what bequeathed connection means Simply an Oracle client-server connection that uses IPC (Inter Process Communication) and not TCP (network connection established via the Listener).
In other words, the client and server process communicates directly (via IPC) with one another. There's no network layer in between that serves as the communication layer.
Obviously, this also means that both client process and server process run on the same kernel - as IPC is a communication method that the kernel provides for processes it is executing, to communicate with one another.

Log of bequeath connection

Hello All,
We are known for that listener will no longer be used for oracle database connection
if the connection is being requested from the server itself, it's called "Bequeath" connection.
I am searching such a log(something like listener log) which is maintained for "Bequeath" connection.
Can anybody suggest me how can I get the log of each "Bequeath" connection in a particular oracle database server.
Thanks in advance and Best Regards,
Suresh Gautam

Suresh,
If it is for an auditing purpose, you could look into Fine Grained Auditing.
With auditing from the database level it would be possible to log session connects.
And with fine grained auditing you could write a procedure which would read the userenv context and you will notice that the IP is null for an bequeath connection.
I do not have an example at hand for this.
but look on otn for the FGA documentation for your oracle release.
for oracle 10.2.0.4 you could start by reading [Fine grained auditing (Security Guide)|http://www.oracle.com/pls/db102/to_URL?remark=ranked&urlname=http:%2F%2Fdownload.oracle.com%2Fdocs%2Fcd%2FB19306_01%2Fnetwork.102%2Fb14266%2Fauditing.htm%23DBSEG525]
SELECT sys_context('USERENV', 'IP_ADDRESS') FROM dual;[syscontext (SQL Reference)|http://www.oracle.com/pls/db102/to_URL?remark=ranked&urlname=http:%2F%2Fdownload.oracle.com%2Fdocs%2Fcd%2FB19306_01%2Fserver.102%2Fb14200%2Ffunctions165.htm%23SQLRF06117]
If you do not need this for auditing then i have no idea ;)

Enterprise Manager is not able to connect to the database instance. Open??

Hello there,
After I installed oracle database and tried to start Enterprise Manager, I got the message:
Enterprise Manager is not able to connect to the database instance.
All statuses are OK (green and up) except database instance. It is also green and up but open. (Details: The instance is open.)
Can anyone help me about it?
I use Windows XP x64 with all patches installed. Oracle database R11g x64.
I tried with different database versions and different machines and different OS and loopback adapter and... my EM still want to log in.
I can log in with sqlplus. It accepts any pass for sys (as sysdba). Why?
My log files are available here: http://195.66.185.187/log.zip

You are using a bequeath connection when logging in with SQL*Plus on the server so the password is not validated.
Log in using SQL*Plus this way:
sqlplus /nolog
followed by
conn sys@<service_name> AS SYSDBA
and provide the correct password
My guess it it will fail.
If so then you need to use the correct password and if you don't know what it is set it when logged on as SYS.

Very slow queries when connecting through the listener in Oracle 10.2.0.4

Hi,
I have a 10g database with a little table (2 columns, 9 rows).
When i connect to the db through the listener (sqlplus system/manager@SID) and run this query : select * from table, the execution time is about 500ms
When i connect to the db by setting the ORACLE_SID to SID (export ORACLE_SID=SID; sqlplus system/manager) and run the same query, it's 10x faster ...
The listener is : TNSLSNR for Solaris: Version 10.2.0.4.0 - Production
The database is : Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
Any ideas ?
Thanks ... (i'm a newbie in oracle and in english ... so excuse me in advance)
Edited by: user1248176 on 12 avr. 2010 22:50

steve80lyon wrote:
i didn't activate wait tracing ... that's done : now i get this when running through TCP/IP connection
PARSING IN CURSOR #5 len=70 dep=0 uid=5 oct=3 lid=5 tim=1038452661888 hv=3805331552 ad='8fa8e228'
SELECT ID, DESCRIPTION FROM AGARIC.PROFILS ORDER BY LOWER(DESCRIPTION)
END OF STMT
PARSE #5:c=260000,e=300749,p=10,cr=1047,cu=0,mis=1,r=0,dep=0,og=4,tim=1038452661879
EXEC #5:c=0,e=84,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=4,tim=1038452662120
WAIT #5: nam='SQL*Net message to client' ela= 5 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1038452662202
WAIT #5: nam='SQL*Net message from client' ela= 50324 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1038452712705
WAIT #5: nam='SQL*Net message to client' ela= 2 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1038452713043
FETCH #5:c=0,e=359,p=0,cr=7,cu=0,mis=0,r=9,dep=0,og=4,tim=1038452713153
WAIT #5: nam='SQL*Net message from client' ela= 1750 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1038452715077
PARSE #3:c=0,e=23,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=0,tim=1038452715199And there we see the difference. Notice the WAIT lines, above? They aren't in your previous post, with the bequeath connection.
I'm re-reading some docs on exactly how to "walk the clock" in reading the above. If you are interested, see if you can find a copy of "Optimizing Oracle Performance" by Cary Milsap. It goes into great detail about how to interpret these traces.
The "ela" value is the elapsed time of the wait, in micro-seconds (1 ms = 0.000 001 second). Unless I've slipped a decimal position, you have 0.52081 sec (a whisker more than one-half second) in network wait time, that doesn't exist on the bequeath connection. That is your "about 500 milliseconds".
Edited by: EdStevens on Apr 13, 2010 9:56 AM
Edited by: EdStevens on Apr 13, 2010 10:00 AM

Oracle/ SQL Developer connection problem.

I have installed Oracle 11 g and SQL Developer, When I open SQL Developer and try to make a new connection ( I name the connection, put a user name in, put my password in), I click on "Test" and I get this error:
Status: Failure - Test failed: Listener refused the connection with the followong error:ORA-12505, TNS: listener does not currently know of SID given in connect descriptor The connection descroptor used by the client was:localhost:1521:ex
Can anyone explain this to me and help me resolve this issue I am having?
Thank you in advance for your help
-steve
p.s. I have also tried the user name: Scott and Password: Tiger

Windows 7 Home ... will have challenges at some point, as Oracle may not be completely compatible with Windows 7.
Aside from that, you may find firewall issues even if you are on the same machine, since the default connection from SQLDeveloper is to use the network (even loopback).
First step is to verify that the database and listener are running and that the database is registered to the listener. TO do that, drop into command line and issue:
1) Listener
lsnrctl statuswhich will give one of two results, if properly installed. First - listener is down
C:\temp>lsnrctl status
LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 07-FEB-2010 20:48
:13
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE)))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
   32-bit Windows Error: 2: No such file or directory
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=FCC003L)(PORT=1521)))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
   32-bit Windows Error: 61: Unknown errorIf the above is displayed, check the Service applet (Control Panel -> Admin Tools > Service) to ensure serivce is up, or enter "lsnrctl start", in which case the status shoud show
C:\temp>lsnrctl status
LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 07-FEB-2010 20:46
:40
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE)))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Produ
ction
Start Date                05-FEB-2010 14:42:10
Uptime                    2 days 6 hr. 4 min. 30 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Default Service           XE
Listener Parameter File   C:\oracle\app\oracle\product\10.2.0\server\network\adm
in\listener.ora
Listener Log File         C:\oracle\app\oracle\product\10.2.0\server\network\log
\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC_FOR_XEipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=FCC003L)(PORT=1521)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
C:\temp>2) After the service is verified up, make sure the database is up
sqlplus / as sysdbawhich should respond with something like
C:\temp>sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Sun Feb 7 20:43:12 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL>if it gives something like
C:\temp>sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Sun Feb 7 20:44:49 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
ERROR:
ORA-12560: TNS:protocol adapter errorthe pull up the Control Panel, Admnistration Tools, Services and start the database. Then recheck the listener and it shoudl show some additional services such as
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "TEST" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Service "XEXDB" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Service "XE_XPT" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Service "xe" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
The command completed successfullyIn the above, remember the "xe" from 'Service "xe" has 1 instance(s).'. I expect to see something about that in the TNSNAMES.ORA file in your ORACLE_HOME\network\admin directory. That file should have an entry like
XE =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = FCC003L)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = XE)
)and you will note the XE on the left side of the equal sign (which is a network alias), and one XE in the (SERVICE_NAME = XE) line. On YOUR system, the XE should be replaced by whatever you called your database (often 'orcl'). REMEMBER THIS ALIAS;-) and also make note of the host that your entry uses. If your host name changes because of DHCP, you're hooped (for a while).
If the database is registered (shows up in the list), the next step is to make sure a userid is available. You could use 'system' (try to avoid using SYS since it is the master userid and if you mess that up, you mess up all your homework. In a production encvironment, every access to SYS will be audited.
So, let's create a userid called me with (in 11g case sensitive) password 'myself'. Make sure that user is allow to log in (create session) and create a table.
C:\temp>sqlplus system/oracle
SQL*Plus: Release 10.2.0.1.0 - Production on Sun Feb 7 20:54:38 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL> create user me identified by myself;
User created.
SQL> rem to show you how to change password ...
SQL> alter user me identified by myself account unlock;
User altered.
SQL> grant create session, create table to me;
Grant succeeded.
SQL> exit
Disconnected from Oracle Database 10g Express Edition Release 10.2.0.1.0 - Productionand now see whether we can log in using the same 'network' technique we will later use with SQLDeveloper.
Do you remember the XE discussion above? Replace XE with the one on the left of the equal sign - the system looks that up to find which service it wants to access.
C:\temp>sqlplus me/myself@XE
SQL*Plus: Release 10.2.0.1.0 - Production on Sun Feb 7 20:58:26 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL> select * from dual;
D
X
SQL> exit
Disconnected from Oracle Database 10g Express Edition Release 10.2.0.1.0 - ProductionIf the above worked, you should have no problem accessing the system using SQLDeveloper. You simply use the HOST, the PORT and the SID (alias) or service from the "lsnrctl status" output in the SQLDeveloper fields.
If it did not work, try dropping the "@XE" to see whether you can get in (using the bequeath connection) which is useful for troubleshooting but will not help with the traditional SQLDeveloper connection. If you get in without the @XE (or whatever your alias is) but not with it, most likely either your listener is not up or your firewall is blocking the access to the listener.

Shell script connection issues

I'm after some advice.
In our development enviroment we pull data from a content database using a shell script by setting the ORACLE_SID within the script and
we then check we can connect. Like our production environment our content and 'normal' database reside on the same server and under these conditions
everything works OK.
ORACLE_SID=$TARGET_DB
DB_CONNECT=`sqlplus -s $USER/$PASS <<EOF
whenever sqlerror exit failure
whenever oserror exit failure
select 1 from dual;
EOF`
However I now have access to a test content database with full production data but it resides on a different server. I can tnsping the other database and connect form the unix prompt with sqlplus user/pwd@newdb. However my shell script now gives
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory
The same also occurs if I do the same manually at the UNIX prompt.
Unfortunately I don't currently have access to a DBA so I am on my own (although I do have full access to both database and operating system on the development box).
Thanks in advance,
Steve

Steve,
Everything is normal. Using ORACLE_SID is limited to local -IPC/Bequeath- connections on the same server.
Assuming you don't want two different methods to connect, you'd best set up an IPC connection in your tnsnames.ora to connect to the local database ,
using ((PROTOCOL=IPC)(KEY=<whatever you used in listener.ora>)), and use the normal tns connection for the remote database.
In that case you can use the @<servicename in tnsnames.ora> all the time.
Alternatively you can replace @<servicename> by
set TWO_TASK=<servicename>
sqlplus ... <without @...>
Hth
Sybrand Bakker
Senior Oracle DBA

Connect Oracle 10G XE and Oracle 9.2i Simultaneously from same machine

Hello,
How to Connect Oracle 10G XE and Oracle 9.2i Simultaneously from same machine using .Net Application.
I have one application which is in .net, i want to connect it with oracle 10g XE and oracle 9.2i Simultaneously.
it always connect only one database which is first in environment variable (path).
please reply.

Use SQL*Net or JDBC Connections. Looks like you are connecting using the Bequeathed connections
Christopher Soza
Oracle BI DBA

Initial Access to Portal 3.0 failing

I have IAS installed, Apache is running but I can't get into the Portal S/W.
I've successfully connected to the DB from sql+ from that Oracle home, so connectivity works.
I did run the Portal config assistant as part of the installation with no obvious errors.
Now I get this when I try to bring up the Portal.
I've tried the Portal DAD, Login server and gateway addresses with much the same result.
THe only odditity I can see is a line later on that says "HTTP_COOKIE=test_dad....." This was the name I used for an earlier failed attempt. I can't find this cookie anywhere or I'd delete it.
Ideas ?
No DAD configuration Found
DAD name:
PROCEDURE : portal30_sso.wwsso_app_admin.ls_login
URL : http://ian:80/pls/sso_dad/portal30_sso.wwsso_app_admin.ls_login

In working on this I think it isn't using the correct tnsnames address.
It appears to be attempting a bequeath connect with SID=orcl.
I have no idea where it is getting this from. THe config utility runs fine and gets to the database ?
This is very confusing

ORA-12535: TNS:operation timed out on a win2000 Oracle instance

Hi,
i have a Oracle 8.1.5 instance on a WIN2000 PC.
I can connect me to this database with sqlplus
as long i stay on the PC (means i started the sqlplus
on the same machine).
When i try to connect from an other (unix-)system
i get after a while (ca. 90 sec.) the error:
ORA-12535: TNS:operation timed out
tnsping works fine (answer comes back in one second)
There are no firewalls or other "strange" things between
the database and the failing client (on an other PC,
also win2000, Oracle 8.1.5 everything works fine).
Below you see the log with debug of the listener.
I have also a trace on level SUPPORT but this is more
than 1000 lines for just 1 or 2 TNSPINGs and one SQLPLUS
connect. Due to this volume i decided not to attach it to
this initial mail.
Does any one have some advice or experiences ?
Please advice.
Best regards,
[email protected]
======================================================================
TNSLSNR for 32-bit Windows: Version 8.1.5.0.0 - Production on 19-APR-01 09:07:26
(c) Copyright 1998 Oracle Corporation. All rights reserved.
Die System-Parameterdatei ist D:\Oracle81\network\admin\listener.ora
Log-Meldungen wurden geschrieben in: D:\Oracle81\network\log\listener.log
Listen auf: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=driller-nb)(PORT=1521))(PROTOCOL_STACK=(PRESENTATION=TTC)(SESSION=NS)))
TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
19-APR-01 09:07:28 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=mdriller))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=135286784)) * status * 0
19-APR-01 09:08:04 * service_register * MDR50 * 0
19-APR-01 09:08:11 * trc_level * 0
19-APR-01 09:08:16 * trc_level * 0
---------------- BEGIN TNSLSNR DEBUG ---------------------
*** ENDPOINT #1 **
Name:
Address: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=driller-nb)(PORT=1521))(PROTOCOL_STACK=(PRESENTATION=TTC)(SESSION=NS)))
Presentation: ttc
Session: NS
Info = <none>
Display: <none>
Load: 0
Handler ID = 80FFE377148D-41F8-AAC2-09A8BD4BE682
Oracle SID = <none>
Flags:
** INSTANCE #1 **
INSTANCE_NAME: MDR50
SERVICE_NAMEs: MDR50
INSTANCE LOAD: 0
INSTANCE ID: 4CC2FCDA6819-40D2-839D-F1628CC0BCA2
FLAGS: LOCAL
VERSION: 81500
NUM. HANDLERS: 2
Handler Matrix: (NS):
tcp nmp spx raw ipc beq lu62 tcps ANY
ttc 0 0 0 0 0 0 0 0 0
giop 0 0 0 0 0 0 0 0 0
http 0 0 0 0 0 0 0 0 0
ro 0 0 0 0 0 0 0 0 0
ANY 0 0 0 0 0 0 0 0 2
Handler Matrix: (RAW):
tcp nmp spx raw ipc beq lu62 tcps ANY
ttc 0 0 0 0 0 0 0 0 0
giop 0 0 0 0 0 0 0 0 0
http 0 0 0 0 0 0 0 0 0
ro 0 0 0 0 0 0 0 0 0
ANY 0 0 0 0 0 0 0 0 0
SERVICE HANDLERS:
Name: DEDICATED
Address: (ADDRESS=(PROTOCOL=beq)(PROGRAM=oracle)(ENVS=)(ARGV0=oracleMDR50)(ARGS='(LOCAL=NO)'))
Presentation: <none>
Session: <none>
Info = LOCAL SERVER
Display: DEDICATED SERVER
Load: 0
Handler ID = 83CB008C17A3-4E48-94DA-2765A62AAD7E
Oracle SID = <none>
Flags: BEQUEATH
Name: DEDICATED
Address: (ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleMDR50)(ARGS='(DESCRIPTION=(LOCAL=no)(ADDRESS=(PROTOCOL=BEQ)))'))
Presentation: <none>
Session: NS
Info = LOCAL SERVER
Display: DEDICATED SERVER
Load: 0
Handler ID = D9E0EC298D16-40FA-935F-7B989D139666
Oracle SID = MDR50
Flags: BEQUEATH CONNECTED DYNAMIC
** INSTANCE #2 **
INSTANCE_NAME: PLSExtProc
SERVICE_NAMEs: PLSExtProc
INSTANCE LOAD: 0
INSTANCE ID: 000000000000-0000-0000-000000000000
FLAGS: LOCAL
NUM. HANDLERS: 1
Handler Matrix: (NS):
tcp nmp spx raw ipc beq lu62 tcps ANY
ttc 0 0 0 0 0 0 0 0 0
giop 0 0 0 0 0 0 0 0 0
http 0 0 0 0 0 0 0 0 0
ro 0 0 0 0 0 0 0 0 0
ANY 0 0 0 0 0 0 0 0 1
Handler Matrix: (RAW):
tcp nmp spx raw ipc beq lu62 tcps ANY
ttc 0 0 0 0 0 0 0 0 0
giop 0 0 0 0 0 0 0 0 0
http 0 0 0 0 0 0 0 0 0
ro 0 0 0 0 0 0 0 0 0
ANY 0 0 0 0 0 0 0 0 0
SERVICE HANDLERS:
Name: DEDICATED
Address: (ADDRESS=(PROTOCOL=beq)(PROGRAM=extproc)(ENVS=)(ARGV0=extprocPLSExtProc)(ARGS='(LOCAL=NO)'))
Presentation: <none>
Session: <none>
Info = LOCAL SERVER
Display: DEDICATED SERVER
Load: 0
Handler ID = 56D4DAD11082-4097-992C-AF7F8067D858
Oracle SID = <none>
Flags: BEQUEATH
---------------- END TNSLSNR DEBUG ---------------------
19-APR-01 09:08:28 * debug * 0
19-APR-01 09:08:41 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=mdriller))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=135286784)) * status * 0
19-APR-01 09:09:57 * ping * 0
19-APR-01 09:10:16 * (CONNECT_DATA=(SID=MDR50)(CID=(PROGRAM=)(HOST=slarti)(USER=mdriller))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.10.34)(PORT=55678)) * establish * MDR50 * 0
19-APR-01 09:14:39 * trc_level * 0
19-APR-01 09:14:58 * trc_level * 0
19-APR-01 09:15:06 * trc_level * 0
19-APR-01 09:16:16 * trc_level * 0
19-APR-01 09:16:20 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=mdriller))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=135286784)) * status * 0
19-APR-01 09:16:33 * trc_level * 0
19-APR-01 09:17:09 * ping * 0
19-APR-01 09:17:51 * (CONNECT_DATA=(SID=MDR50)(CID=(PROGRAM=)(HOST=slarti)(USER=mdriller))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.10.34)(PORT=55695)) * establish * MDR50 * 0
19-APR-01 09:18:06 * MDR50 * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.10.34)(PORT=55695)) * service_update * MDR50 * 0
19-APR-01 09:23:33 * (CONNECT_DATA=(SID=MDR50)(CID=(PROGRAM=)(HOST=deep-thought)(USER=mdriller))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.10.22)(PORT=42006)) * establish * MDR50 * 0
19-APR-01 09:28:09 * MDR50 * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.10.22)(PORT=42006)) * service_update * MDR50 * 0
19-APR-01 09:28:25 * ping * 0
null

Rather than
MyDB.10gXE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = MYSERVER)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = XE)
why not go with the bulk standard tnsnames entry as follows:-
XE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = MYSERVER)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = XE)
I don't think the qualified MyDB.10gXE name is adding any value and may well confuse things.
Although setting it for my environment does work
C:\Documents and Settings\mtownsen.ST-USERS>tnsping myDB.10gXE
TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 09-NOV-2
005 18:06:48
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Used parameter files:
C:\oraclexe\app\oracle\product\10.2.0\server\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = mtownsen
-lap.us.oracle.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_
NAME = XE)))
OK (40 msec)
OK - when I use your entry pasted directly from the above, with my server name, I get the following problem:-
C:\Documents and Settings\mtownsen.ST-USERS>tnsping myDB.10gXE
TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 09-NOV-2
005 18:07:43
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Used parameter files:
C:\oraclexe\app\oracle\product\10.2.0\server\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION =
TNS-12533: TNS:illegal ADDRESS parameters
I added back some spaces, as indicated by the . below, and it works fine
MyDB.10gXE =
(DESCRIPTION =
.(ADDRESS = (PROTOCOL = TCP)(HOST = mtownsen-lap.us.oracle.com)(PORT = 1521))
.(CONNECT_DATA =
.(SERVER = DEDICATED)
.(SERVICE_NAME = XE)
.)

Why do we create externally identfied users ?

RDBMS version: 11.2.0.2
Platform : Solaris 10
I work in a Retail Banking/financial applications environment. All our applications are in Java running from Websphere/Tibco. Our DB servers only host DBs. ie Applications are run from dedicated Linux servers.
But, in our DB server (solaris) several Unix users are created for application. Then we create DB schemas with EXT$ prefixed
If unix user is xpsapp, then we'll create a schema named EXT$xpsapp
os_authent_prefix parameter set to EXT$Why do applications need this externally identified schemas ? Can't they just use a normal schema?

Traditionally, externally authenticated accounts are used for application batch jobs and DBA utility jobs run from "cron." The shell scripts executed by "cron" invoke Oracle tools (usually sqlplus) connecting to the database "as slash" and not hardcoding a password on the command line. This has the following benefits:
* The O/S-level password can be changed on a regular basis without any associated code (or preference file) changes
* No hard-coded passwords are used on the command line (which can be seen with the "ps -ef" utility)
* The batch jobs are not affected by network outages due to the bequeath connection type

TRACING IN SQL*NET V2

제품 : SQL*NET
작성날짜 : 1997-10-10
Introduction
~~~~~~~~~~~~
For most problems you need to identify the relevant parts of a
connection to trace. To do this consider which scenario you are
having problems with and where tracing needs to be enabled.
Note that tracing produces a lot of output , especially at higher
trace levels.
There are 3 main areas of SQL*Net that can produce trace output:
1 = the SQL*Net 'client'
2 = the 'listener' process
3 = the SQL*Net 'server'.
a) Establishing a connection:
Client ----> Listener ----> Server
1 2 3
b) An established connection:
Client --------> Server
1 3
c) Opening a database link:
Client ----> Server ----> Listener -----> Server2
1 3 1 2 3
Note here that the Oracle server process is also a SQL*Net
client when it makes an outgoing call to a listener to
open a database link. Database links are OPENED when first
used. They should then remain open until closed.
d) An established database link:
Client ----> Server -----> Server2
1 3 1 3
In each case here there are several potential sampling points. You
should be able to identify quickly which of these scenarios matches
your setup. As these scenarios are likely to involve connections
between different machines you should remember that tracing for any
process is controlled by the configuration details that the process
reads WHEN IT IS STARTED. This is especially important when looking
at MTS connections as the SQL*Net server is the 'dispatcher' process.
Some dispatchers are started when the database instance is started
and others may start at a later time (on demand). Each dispatcher will
read their SQL*Net configuration WHEN THEY START.
7.2 Client Tracing
~~~~~~~~~~~~~~
For client TOOLS edit or create the file $HOME/.sqlnet.ora and add
the lines:
trace_level_client=16
trace_file_client=cli
trace_directory_client=/tmp # Or a known directory
trace_unique_client=true # Add '_pid' to trace filename
This will turn on FULL tracing for your user account only producing
output in a file called /tmp/cli_<PID>.trc .
(For some SQL*Net versions the file will be just /tmp/cli.trc)
For client 'ORACLE' process (as in the case of database links) put this
same information into $TNS_ADMIN/sqlnet.ora file.
On versions up to and including Oracle 7.0.16 client trace may not
add a process ID to the name of the trace file. This means two
processes may end up writing to the same trace file unless you
take care to control which processes write trace output to each file.
7.3 Listener Tracing
~~~~~~~~~~~~~~~~
Listener tracing can ONLY be configured in the listener.ora file.
Add the lines below to the listener.ora file:
trace_level_listener=16
trace_file_listener=listener
trace_directory_listener=/tmp # Or a known directory
This will define FULL listener tracing to the file /tmp/listener.trc.
You can enable this tracing by either:
lsnrctl reload
OR
lsnrctl stop;
lsnrctl start;
TCP/IP
~~~~~~
It is often useful to confirm that a listener is listening on a
specified address. Most Unix machines include a command called
'netstat' (Often in /etc or in /usr/etc). The command netstat -a
should list all TCP/IP end points on which a listener is listening.
Eg:
For a listener listening on HOST=... PORT=1580 there should be a
netstat entry of the form:
RecvQ SendQ Local Address Foreign Address TCP state
0 0 *.1580 *.* LISTEN
Note: Some versions of netstat will only list established connections
and not listen end points. See the man page on your machine.
7.4 Server Tracing
~~~~~~~~~~~~~~
Server side trace is not required as often as the other two traces
mainly because most problems are related to establishing a connection.
Once a connection has been established the client and server processes
are communicating. It is sometimes useful to see exactly what SQL
commands have been received by the server, and what data it has sent
back out.
The file $TNS_ADMIN/sqlnet.ora controls the server side tracing. Add
the lines below to this file:
trace_level_server=16
trace_file_server=server
trace_directory_server=/tmp # Or a known directory
Output should be sent to the file /tmp/server_<PID>.trc
Note: Server side tracing acts on the SQL*Net server side.
For dedicated connections this is the Oracle process on the
server machine.
For MTS connections this is the DISPATCHER and NOT the shared
server. Data is passed between the dispatcher and the shared
servers via the SGA and this does NOT involve SQL*Net.
It is also important to note that as a dispatcher handles
several client processes the dispatcher trace output can be a
mix of trace from many client processes making it VERY difficult
to follow. The general advice for such problems is:
a) See if the problem reproduces WITHOUT using MTS - if
so the trace is much cleaner
b) If a problem ONLY reproduces under MTS ensure the machine
is in a controlled environment so you can be sure that only
YOUR process is using the dispatcher.
7.5 Trace Summary
~~~~~~~~~~~~~
1) Identify where you need to trace.
2) Identify which files on which machines control tracing at these
points. Tracing is controlled in the following files:
Client Server Listener
~~~~~~ ~~~~~~ ~~~~~~~~
Files: $HOME/.sqlnet.ora sqlnet.ora listener.ora
sqlnet.ora
3) Add in the relevant trace parameters (See Below)
4) Restart any processes that need to read the new trace values.
Reload the listener as required.
5) Reproduce your problem
6) Save all your trace output immediately
7) Disable the tracing
7.6 Main Trace Parameters
~~~~~~~~~~~~~~~~~~~~~
trace_level_listener = off
trace_file_listener = Filename *1
trace_directory_listener = Directory *2
*1 Unquoted (") filenames will be translated into lower case.
*2 You CANNOT use environment variables in the Filename or Directory
name.
7.7 Diagnosing Trace output
~~~~~~~~~~~~~~~~~~~~~~~
Trace output can be very difficult to follow. Before looking at a
trace file make sure:
a) You are familiar with the sequence of events in setting up
a connection. SQL*Net connections follow a sequence of
events - you will need to determin where in the sequence
the problem occurs.
b) Do not be misled by error reports in the trace files. You
must follow the context of the errors - an error may be
quite valid at that point in a sequence. Eg: For client
connections a list of addresses to call is built - if the
first address yeilds no response the next address is tried.
This next address may yeild a response and the 'true' error
occurs at this point in the sequence.
c) Do not be misled by unusual 'Bequeath' connections in the
trace. If an error is received over SQL*Net the client
may use a "Bequeath" operation to spawn an oracle process
which it then uses to get the TEXT of the error. A very short
exchange of packets occurs and the bequethed process exits.
The 'TRUE' problem is likely to be before this bequeath
operation.
Useful trace 'tags':
The following are useful items to follow in trace files - these
are not guaranteed to be valid across all SQL*Net releases and
are for guidance only. Entries are assumed to be taken at trace
level 16 to allow data packets to be seen. This will produce a
LOT of trace output.
-<ERROR>-
Error information follows. Remember the error may be acceptable
osntns: Calling address
Shows address list constructed for a call OUT to a listener
nricall: Making call with following address information: ...
Shows the ACTUAL address being called from the above list
nsopen: entry
We are about to try and open a connection.
nsopen: transport is open
nsopen: error exit
A connection to the called address has been made / failed.
nsclose: ...
An established connection is being closed - check nearby
for errors.
nscall: redirected
The client has been redirected to a differenct address.
The next step should be to call the new address. The address
should appear in an earlier data packet.
nspsend / nsprecv
Outgoung / Incoming data

This forum is for Oracle Migration Workbench issues, i.e. migration using the workbench from a non Oracle database to an Oracle database.
Here are some pointers that may be useful, but you may need to get more information elsewhere, for example Oracle Customer Support.
a Oracle 7.1 client (including your example) will connect to an Oracle 8.1.5 server.
Is the server correctly configured (can a client connect from another machine)?
Tracing can be turned on in the client, server and/or listener to get further information.
Turloch

Remove the datafile not belong to database

ASM disk +data filled with datafile and onlinelogs not belong to the database.
I have created the standby datbase from primary using copy datafiles . first time it failed.
but files were copied into disk. without removeing the old datafile gain created the standby database
standby datbase working fine. no problem
but disk with filled with old file and online logs
I would like to know how to remove the files from ASM (+data)
how to identify the files not belong to the database.

export ORACLE_SID=+ASM
asmcmd
you will see disckgroups name on the top level. Run help command
oracle@dw5: ~$ asmcmd
ASMCMD> ls
DAG_01/
IXG_01/
ASMCMD> help
asmcmd [-v] [-a <sysasm|sysdba>] [-p] [command]
The environment variables ORACLE_HOME and ORACLE_SID determine the
instance to which the program connects, and ASMCMD establishes a
bequeath connection to it, in the same manner as a SQLPLUS / AS
SYSDBA. The user must be a member of the SYSDBA group.
Specifying the -v option prints the asmcmd version number and
exits immediately.
Specify the -a option to choose the type of connection. There are
only two possibilities: connecting as "sysasm" or as "sysdba".
The default value if this option is unspecified is "sysasm".
Specifying the -p option allows the current directory to be displayed
in the command prompt, like so:
ASMCMD [+DATAFILE/ORCL/CONTROLFILE] >
[command] specifies one of the following commands, along with its
parameters.
Type "help [command]" to get help on a specific ASMCMD command.
commands:
help
cd
cp
du
find
ls
lsct
lsdg
mkalias
mkdir
pwd
rm
rmalias
md_backup
md_restore
lsdsk
remap
ASMCMD> cd DAG_01/
ASMCMD> ls
DB_UNKNOWN/
IDTDW/
ASMCMD>
....

Some other PLSXML compile problems (7.3.4.2.0 on NT)

Hello XML team,
I also get errors when trying to compile the PLSXML packages and
bodies using 7.3.4.2.0 on Win NT with PL/SQL 2.3.4.2.0 and
PL/SQL 3.3.4.0.0.
Connected to:
Oracle7 Workgroup Server Release 7.3.4.2.0 - Production
With the distributed option
PL/SQL Release 2.3.4.2.0 - Production
SQL> @..\dbdom\dbdom
CREATE OR REPLACE PACKAGE DBDOM IS
ERROR at line 1:
ORA-01010: invalid OCI operation
Thanks in advance for any help,
Andreas Loew
[email protected] (my OTN member address)
[email protected] (current address at customer project)
!!! Please answer to [email protected], as I can only
!!! read my mail at CSC Ploenzke once a week... :-(
null

: Connected to:
: Oracle7 Workgroup Server Release 7.3.4.2.0 - Production
: With the distributed option
: PL/SQL Release 2.3.4.2.0 - Production
: SQL> @..\dbdom\dbdom
: CREATE OR REPLACE PACKAGE DBDOM IS
: ERROR at line 1:
: ORA-01010: invalid OCI operation
: Thanks in advance for any help,
: Andreas Loew
: [email protected] (my OTN member address)
: [email protected] (current address at customer project)
: !!! Please answer to [email protected], as I can only
: !!! read my mail at CSC Ploenzke once a week... :-(
I found Oracle Bug 691590 for this, "Windows Version
of SQLPlus causes ORA-1010 with Large Package Bodies"
This occurs on Version 7.3.4 of Oracle on NT
The bug only occurs if you use a BEQ (bequeath)
connection to the database. The workaround is to
use a loopback TCPIP sqlnet connection to your
database to connect and create the package.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

Bequeath connection 8i - 9i

Similar Messages

Maybe you are looking for