TIP 02: Easy Connect Naming Method in 10g by Joel Pèrez

Hi OTN Readers!
Everyday I get connection on Internet and one of the first issues that
I do is to open the OTN main page to look for any new article or any
new news about the Oracle Technology. After I open the main page of
OTN Forums and I check what answers I can write to help some people
to work with the Oracle Technology and I decided to begin to write some
threads to help DBAs and Developers to learn the new features of 10g.
I hope you can take advantage of them which will be published here in
this forum. For any comment you can write to me directly to : [email protected]
Please do not replay this thread, if you have any question related to
this I recommend you to open a new post. Thanks!
The tip of this thread is: Easy Connect Naming Method
Joel Pérez
http://otn.oracle.com/experts

Let's go to test it removing the BASE1 service of the listener.ora file
# listener.ora Network Configuration File: C:\oracle\product\10.1.0\db_1\NETWORK\ADMIN\listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
  (SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME = BASE2)
      (ORACLE_HOME = C:\oracle\product\10.1.0\db_1)
      (SID_NAME = BASE2)
LISTENER =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = oracle10g)(PORT = 1521))
  )and Now, I am going to reload the listener service in order to
apply the change to the enviroment.
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
C:\>
C:\>lsnrctl stop
LSNRCTL for 32-bit Windows: Version 10.1.0.2.0 - Production on 20-APR-2004 13:20
:35
Copyright (c) 1991, 2004, Oracle.  All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oracle10g)(PORT=1521)))
The command completed successfully
C:\>lsnrctl start
LSNRCTL for 32-bit Windows: Version 10.1.0.2.0 - Production on 20-APR-2004 13:20
:39
Copyright (c) 1991, 2004, Oracle.  All rights reserved.
Starting tnslsnr: please wait...
TNSLSNR for 32-bit Windows: Version 10.1.0.2.0 - Production
System parameter file is C:\oracle\product\10.1.0\db_1\network\admin\listener.or
a
Log messages written to C:\oracle\product\10.1.0\db_1\network\log\listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oracle10g)(PORT=1521)))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for 32-bit Windows: Version 10.1.0.2.0 - Produ
ction
Start Date                20-APR-2004 13:20:41
Uptime                    0 days 0 hr. 0 min. 2 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   C:\oracle\product\10.1.0\db_1\network\admin\listener.o
ra
Listener Log File         C:\oracle\product\10.1.0\db_1\network\log\listener.log
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
Services Summary...
Service "BASE2" has 1 instance(s).
  Instance "BASE2", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
C:\>Joel Pérez
http://otn.oracle.com/experts

Similar Messages

  • Multiple Data Source (for FAILOVER) in Easy Connect Naming method

    Hi All,
    I was wondering if there is a way to specify multiple addresses as part of data source property in the connection string when trying to connect to Oracle with Easy Connect Naming method? this is basically for failover scenario.
    I know its straight forward, if i use Connect Descriptor. But not sure how to do it with EZConnect
    For ex. this is what I want to achieve with EZConnect
    sales.us.example.com=
    (DESCRIPTION=
    (ADDRESS_LIST=
    (LOAD_BALANCE=off)
    (FAILOVER=ON)
    *(ADDRESS=(PROTOCOL=tcp)(HOST=sales1-server)(PORT=1521))*
    *(ADDRESS=(PROTOCOL=tcp)(HOST=sales2-server)(PORT=1521)))*
    (CONNECT_DATA=(SERVICE_NAME=sales.us.example.com)))
    I appreciate your suggestions...
    Thanks

    You might get better answers in one of the DB forums from a generic fail-over perspective as EZconnect isn't specific to ODP.NET.
    I don't know if there's a way to do it or not with EZConnect version of the connect string, but you can certainly provide the fully qualified connect string without using tnsnames.ora..
    constring = "data source=(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=off)(FAILOVER=ON)(ADDRESS=(PROTOCOL=tcp)(HOST=sales1-server)(PORT=1521))(ADDRESS=(PROTOCOL=tcp)(HOST=sales2-server)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=sales.us.example.com))); user id=scott;password=tiger"
    Hope it helps,
    Gres

  • Oci_connect using easy connect naming method needs listener??

    Hi,
    I was thinking that using the easy connect naming method in oci_connect does not require a running local tnslsnr!? Am I wrong?
    I tried:
    $db = '(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = my-ora-host.example.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = my-service.example.com)))';
    // $db = '//my-ora-host.example.com:1521/my-service.example.com';
    $ora_conn = oci_connect('test', 'test', $db);
    Using both versions of the 'db' I receive the error:
    mod_fcgid: stderr: PHP Warning: oci_connect(): ORA-12541: TNS:no listener in ....
    I am using a self compiled PHP 5.3.8 using Oracles instantclient 11.2.0.3.0 (on Linux, 32bit).
    There are NO special environment variables ( like ORACLE_HOME or TNS_ADMIN), because I was thinking that I don't need them...
    Am I wrong? Is a running tnslsnr always required? Or am I doing wrong in specifying the connection string?
    Any help is appreciated!
    chuan

    The connection strings are fine. They only control how PHP attempts to connect to the DB. The DB will need a listener started so that those incoming requests are handled. Use: 'lsnrctl start' on the DB machine.

  • Question about "Easy Connect Naming"

    Good evening,
    My installation consists of 11gR2 where both host and client are on the same machine.
    I wanted to test the "Easy Connect Naming" functionality, to that end, I renamed tnsnames.ora and proceeded to connect using the following command:
    sqlplus sys/abc123@"Oracle2Day1.john.local/orcl.john.local:1521" as sysdbaas expected, the command was successful in connecting to the orcl instance.
    To ensure that everything was as expected, I also tried:
    sqlplus sys/abc123 as sysdbaUnexpectedly, this command also connected to the orcl instance.
    I expected it to fail since there is no tnsnames.ora and I did not specify the host and service names.
    The question is: why was the command sqlplus sys/abc123 as sysdba" successful given that there is no tnsnames.ora ?
    Thank you for your help,
    John.

    The question is: why was the command sqlplus sys/abc123 as sysdba" successful given that there is no tnsnames.ora ?Above only works when logged directly on to DB server, because this flavor of connection does not use SQL*Net; but uses BEQ protocol.

  • TIP 04: Duplicating a Database in 10g by Joel Pèrez

    Hi OTN Readers!
    Everyday I get connection on Internet and one of the first issues that
    I do is to open the OTN main page to look for any new article or any
    new news about the Oracle Technology. After I open the main page of
    OTN Forums and I check what answers I can write to help some people
    to work with the Oracle Technology and I decided to begin to write some
    threads to help DBAs and Developers to learn the new features of 10g.
    I hope you can take advantage of them which will be published here in
    this forum. For any comment you can write to me directly to : [email protected] . Apart from your comments you can suggest to me any topic to write an article like this.
    Please do not replay this thread, if you have any question related to
    this I recommend you to open a new post. Thanks!
    The tip of this thread is: Duplicating a Database in 10g
    Joel Pérez
    http://otn.oracle.com/experts

    Step 6: Editing the file generated
    The file generated is going to be like this:
    Dump file f:\ora9i\admin\copy1\udump\copy1_ora_912.trc
    Thu May 20 16:27:37 2004
    ORACLE V9.2.0.1.0 - Production vsnsta=0
    vsnsql=12 vsnxtr=3
    Windows 2000 Version 5.0 Service Pack 4, CPU type 586
    Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.1.0 - Production
    Windows 2000 Version 5.0 Service Pack 4, CPU type 586
    Instance name: copy1
    Redo thread mounted by this instance: 1
    Oracle process number: 10
    Windows thread id: 912, image: ORACLE.EXE
    *** SESSION ID:(9.38) 2004-05-20 16:27:37.000
    *** 2004-05-20 16:27:37.000
    # The following are current System-scope REDO Log Archival related
    # parameters and can be included in the database initialization file.
    # LOG_ARCHIVE_DEST=''
    # LOG_ARCHIVE_DUPLEX_DEST=''
    # LOG_ARCHIVE_FORMAT=ARC%S.%T
    # REMOTE_ARCHIVE_ENABLE=TRUE
    # LOG_ARCHIVE_MAX_PROCESSES=2
    # STANDBY_FILE_MANAGEMENT=MANUAL
    # STANDBY_ARCHIVE_DEST=%ORACLE_HOME%\RDBMS
    # FAL_CLIENT=''
    # FAL_SERVER=''
    # LOG_ARCHIVE_DEST_1='LOCATION=f:\ora9i\RDBMS'
    # LOG_ARCHIVE_DEST_1='MANDATORY NOREOPEN NODELAY'
    # LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM SYNC'
    # LOG_ARCHIVE_DEST_1='NOREGISTER NOALTERNATE NODEPENDENCY'
    # LOG_ARCHIVE_DEST_1='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED'
    # LOG_ARCHIVE_DEST_STATE_1=ENABLE
    # Below are two sets of SQL statements, each of which creates a new
    # control file and uses it to open the database. The first set opens
    # the database with the NORESETLOGS option and should be used only if
    # the current versions of all online logs are available. The second
    # set opens the database with the RESETLOGS option and should be used
    # if online logs are unavailable.
    # The appropriate set of statements can be copied from the trace into
    # a script file, edited as necessary, and executed when there is a
    # need to re-create the control file.
    #     Set #1. NORESETLOGS case
    # The following commands will create a new control file and use it
    # to open the database.
    # Data used by the recovery manager will be lost. Additional logs may
    # be required for media recovery of offline data files. Use this
    # only if the current version of all online logs are available.
    STARTUP NOMOUNT
    CREATE CONTROLFILE REUSE DATABASE "COPY1" NORESETLOGS  NOARCHIVELOG
    --  SET STANDBY TO MAXIMIZE PERFORMANCE
        MAXLOGFILES 50
        MAXLOGMEMBERS 5
        MAXDATAFILES 100
        MAXINSTANCES 1
        MAXLOGHISTORY 226
    LOGFILE
      GROUP 1 'C:\COPY1\COPY1\REDO01.LOG'  SIZE 10M,
      GROUP 2 'C:\COPY1\COPY1\REDO02.LOG'  SIZE 10M,
      GROUP 3 'C:\COPY1\COPY1\REDO03.LOG'  SIZE 10M
    -- STANDBY LOGFILE
    DATAFILE
      'C:\COPY1\COPY1\SYSTEM01.DBF',
      'C:\COPY1\COPY1\UNDOTBS01.DBF',
      'C:\COPY1\COPY1\CWMLITE01.DBF',
      'C:\COPY1\COPY1\DRSYS01.DBF',
      'C:\COPY1\COPY1\EXAMPLE01.DBF',
      'C:\COPY1\COPY1\INDX01.DBF',
      'C:\COPY1\COPY1\ODM01.DBF',
      'C:\COPY1\COPY1\TOOLS01.DBF',
      'C:\COPY1\COPY1\USERS01.DBF',
      'C:\COPY1\COPY1\XDB01.DBF'
    CHARACTER SET WE8ISO8859P1
    # Recovery is required if any of the datafiles are restored backups,
    # or if the last shutdown was not normal or immediate.
    RECOVER DATABASE
    # Database can now be opened normally.
    ALTER DATABASE OPEN;
    # Commands to add tempfiles to temporary tablespaces.
    # Online tempfiles have complete space information.
    # Other tempfiles may require adjustment.
    ALTER TABLESPACE TEMP ADD TEMPFILE 'C:\COPY1\COPY1\TEMP01.DBF'
         SIZE 41943040  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
    # End of tempfile additions.
    #     Set #2. RESETLOGS case
    # The following commands will create a new control file and use it
    # to open the database.
    # The contents of online logs will be lost and all backups will
    # be invalidated. Use this only if online logs are damaged.
    STARTUP NOMOUNT
    CREATE CONTROLFILE REUSE DATABASE "COPY1" RESETLOGS  NOARCHIVELOG
    --  SET STANDBY TO MAXIMIZE PERFORMANCE
        MAXLOGFILES 50
        MAXLOGMEMBERS 5
        MAXDATAFILES 100
        MAXINSTANCES 1
        MAXLOGHISTORY 226
    LOGFILE
      GROUP 1 'C:\COPY1\COPY1\REDO01.LOG'  SIZE 10M,
      GROUP 2 'C:\COPY1\COPY1\REDO02.LOG'  SIZE 10M,
      GROUP 3 'C:\COPY1\COPY1\REDO03.LOG'  SIZE 10M
    -- STANDBY LOGFILE
    DATAFILE
      'C:\COPY1\COPY1\SYSTEM01.DBF',
      'C:\COPY1\COPY1\UNDOTBS01.DBF',
      'C:\COPY1\COPY1\CWMLITE01.DBF',
      'C:\COPY1\COPY1\DRSYS01.DBF',
      'C:\COPY1\COPY1\EXAMPLE01.DBF',
      'C:\COPY1\COPY1\INDX01.DBF',
      'C:\COPY1\COPY1\ODM01.DBF',
      'C:\COPY1\COPY1\TOOLS01.DBF',
      'C:\COPY1\COPY1\USERS01.DBF',
      'C:\COPY1\COPY1\XDB01.DBF'
    CHARACTER SET WE8ISO8859P1
    # Recovery is required if any of the datafiles are restored backups,
    # or if the last shutdown was not normal or immediate.
    RECOVER DATABASE USING BACKUP CONTROLFILE
    # Database can now be opened zeroing the online logs.
    ALTER DATABASE OPEN RESETLOGS;
    # Commands to add tempfiles to temporary tablespaces.
    # Online tempfiles have complete space information.
    # Other tempfiles may require adjustment.
    ALTER TABLESPACE TEMP ADD TEMPFILE 'C:\COPY1\COPY1\TEMP01.DBF'
         SIZE 41943040  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
    # End of tempfile additions.
    #As you can see, you have there different ways to recreate the controlfile. In Our case, We are going to recreate the controlfiles so:
    STARTUP NOMOUNT
    CREATE CONTROLFILE SET DATABASE "COPY2" RESETLOGS NOARCHIVELOG
    -- SET STANDBY TO MAXIMIZE PERFORMANCE
    MAXLOGFILES 50
    MAXLOGMEMBERS 5
    MAXDATAFILES 100
    MAXINSTANCES 1
    MAXLOGHISTORY 226
    LOGFILE
    GROUP 1 'C:\COPY2\COPY2\REDO01.LOG' SIZE 10M,
    GROUP 2 'C:\COPY2\COPY2\REDO02.LOG' SIZE 10M,
    GROUP 3 'C:\COPY2\COPY2\REDO03.LOG' SIZE 10M
    -- STANDBY LOGFILE
    DATAFILE
    'C:\COPY2\COPY2\SYSTEM01.DBF',
    'C:\COPY2\COPY2\UNDOTBS01.DBF',
    'C:\COPY2\COPY2\CWMLITE01.DBF',
    'C:\COPY2\COPY2\DRSYS01.DBF',
    'C:\COPY2\COPY2\EXAMPLE01.DBF',
    'C:\COPY2\COPY2\INDX01.DBF',
    'C:\COPY2\COPY2\ODM01.DBF',
    'C:\COPY2\COPY2\TOOLS01.DBF',
    'C:\COPY2\COPY2\USERS01.DBF',
    'C:\COPY2\COPY2\XDB01.DBF'
    CHARACTER SET WE8ISO8859P1
    Note: two important issues to denote in the sentence above is the word "SET" instead of "REUSE" and the controlfiles must be recreated in RESETLOG mode because the database must be opened in RESETLOG mode.
    If you use the word "REUSE" instead of "SET" the opening of the database is going to request recovery of the datafile of the tablespace system.
    So, apply this to recreate the controlfiles:
    - Start the service in windows for the database COPY2
    - Get connection through SQL*Plus as system
    - Shut down the database with shutdown abort
    - Start the database up in nomount stage
    - apply the sentence to recreate the controlfile.
    C:\>SET ORACLE_SID=COPY2
    C:\>sqlplus /nolog
    SQL*Plus: Release 9.2.0.1.0 - Production on Thu May 20 16:46:49 2004
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    SQL> conn sys as sysdba
    Enter password:
    Connected.
    SQL>
    SQL> shutdown abort
    ORACLE instance shut down.
    SQL>
    SQL>
    SQL> startup nomount
    ORACLE instance started.
    Total System Global Area  135338868 bytes
    Fixed Size                   453492 bytes
    Variable Size             109051904 bytes
    Database Buffers           25165824 bytes
    Redo Buffers                 667648 bytes
    SQL>
    SQL>
    SQL> CREATE CONTROLFILE SET DATABASE "COPY2" RESETLOGS  NOARCHIVELOG
      2  --  SET STANDBY TO MAXIMIZE PERFORMANCE
      3      MAXLOGFILES 50
      4      MAXLOGMEMBERS 5
      5      MAXDATAFILES 100
      6      MAXINSTANCES 1
      7      MAXLOGHISTORY 226
      8  LOGFILE
      9    GROUP 1 'F:\COPY2\COPY2\REDO01.LOG'  SIZE 10M,
    10    GROUP 2 'F:\COPY2\COPY2\REDO02.LOG'  SIZE 10M,
    11    GROUP 3 'F:\COPY2\COPY2\REDO03.LOG'  SIZE 10M
    12  -- STANDBY LOGFILE
    13  DATAFILE
    14    'F:\COPY2\COPY2\SYSTEM01.DBF',
    15    'F:\COPY2\COPY2\UNDOTBS01.DBF',
    16    'F:\COPY2\COPY2\CWMLITE01.DBF',
    17    'F:\COPY2\COPY2\DRSYS01.DBF',
    18    'F:\COPY2\COPY2\EXAMPLE01.DBF',
    19    'F:\COPY2\COPY2\INDX01.DBF',
    20    'F:\COPY2\COPY2\ODM01.DBF',
    21    'F:\COPY2\COPY2\TOOLS01.DBF',
    22    'F:\COPY2\COPY2\USERS01.DBF',
    23    'F:\COPY2\COPY2\XDB01.DBF'
    24  CHARACTER SET WE8ISO8859P1
    25  ;
    Control file created.
    SQL>Joel Pérez
    http://otn.oracle.com/experts

  • TIP 03: Transportable Tablespaces in 10g by Joel Pèrez

    Hi OTN Readers!
    Everyday I get connection on Internet and one of the first issues that
    I do is to open the OTN main page to look for any new article or any
    new news about the Oracle Technology. After I open the main page of
    OTN Forums and I check what answers I can write to help some people
    to work with the Oracle Technology and I decided to begin to write some
    threads to help DBAs and Developers to learn the new features of 10g.
    I hope you can take advantage of them which will be published here in
    this forum. For any comment you can write to me directly to : [email protected]
    Please do not replay this thread, if you have any question related to
    this I recommend you to open a new post. Thanks!
    The tip of this thread is: Transportable Tablespaces
    Joel Pérez
    http://otn.oracle.com/experts

    Step 9: Apply this command to see all the options of the export utility
    C:\>
    C:\>EXP HELP=Y
    Export: Release 10.1.0.2.0 - Production on Fri Apr 23 19:48:30 2004
    Copyright (c) 1982, 2004, Oracle.  All rights reserved.
    You can let Export prompt you for parameters by entering the EXP
    command followed by your username/password:
         Example: EXP SCOTT/TIGER
    Or, you can control how Export runs by entering the EXP command followed
    by various arguments. To specify parameters, you use keywords:
         Format:  EXP KEYWORD=value or KEYWORD=(value1,value2,...,valueN)
         Example: EXP SCOTT/TIGER GRANTS=Y TABLES=(EMP,DEPT,MGR)
                   or TABLES=(T1:P1,T1:P2), if T1 is partitioned table
    USERID must be the first parameter on the command line.
    Keyword    Description (Default)      Keyword      Description (Default)
    USERID     username/password          FULL         export entire file (N)
    BUFFER     size of data buffer        OWNER        list of owner usernames
    FILE       output files (EXPDAT.DMP)  TABLES       list of table names
    COMPRESS   import into one extent (Y) RECORDLENGTH length of IO record
    GRANTS     export grants (Y)          INCTYPE      incremental export type
    INDEXES    export indexes (Y)         RECORD       track incr. export (Y)
    DIRECT     direct path (N)            TRIGGERS     export triggers (Y)
    LOG        log file of screen output  STATISTICS   analyze objects (ESTIMATE)
    ROWS       export data rows (Y)       PARFILE      parameter filename
    CONSISTENT cross-table consistency(N) CONSTRAINTS  export constraints (Y)
    OBJECT_CONSISTENT    transaction set to read only during object export (N)
    FEEDBACK             display progress every x rows (0)
    FILESIZE             maximum size of each dump file
    FLASHBACK_SCN        SCN used to set session snapshot back to
    FLASHBACK_TIME       time used to get the SCN closest to the specified time
    QUERY                select clause used to export a subset of a table
    RESUMABLE            suspend when a space related error is encountered(N)
    RESUMABLE_NAME       text string used to identify resumable statement
    RESUMABLE_TIMEOUT    wait time for RESUMABLE
    TTS_FULL_CHECK       perform full or partial dependency check for TTS
    TABLESPACES          list of tablespaces to export
    TRANSPORT_TABLESPACE export transportable tablespace metadata (N)
    TEMPLATE             template name which invokes iAS mode export
    Export terminated successfully without warnings.Joel Pérez
    http://otn.oracle.com/experts

  • TIP 01: Default User Tablespace in 10g by Joel Pèrez

    Hi OTN Readers!
    Everyday I get connection on Internet and one of the first issues that
    I do is to open the OTN main page to look for any new article or any
    new news about the Oracle Technology. After I open the main page of
    OTN Forums and I check what answers I can write to help some people
    to work with the Oracle Technology and I decide to begin to write some
    threads to help DBAs and Developers to learn the new features of 10g.
    I hope you can take advantage of them which will be published here in
    this forum. For any comment you can write to me directly to : [email protected]
    Please do not replay this thread, if you have any question related to
    this I recommend you to open a new post. Thanks!
    The tip of this thread is: DEFAULT USER TABLESPACE
    Joel Pérez
    http://otn.oracle.com/experts

    Step 9: At the step 5 We changed the default tablespace of the database but there is an
    important detail that We have to realize. That detail is the following : when you change
    the default tablespace of the database. The users were using it are move to store its objects
    in the new default tablespace but the objects that were stored in the original tablespace
    remain there. Let's go to look at it:
    Here We are connected to the database as system user
    SQL> show user
    USER is "SYSTEM"Let's go to get connection as new_user user in order to create a table
    SQL> conn new_user/new_user@base1
    Connected.
    Creating a table in the schema NEW_USER
    SQL> create table t1_new_user(c1 number);
    Table created.As you can see that table is stored in the default tablespace assigned to the user new_user
    SQL> select TABLE_NAME, TABLESPACE_NAME from dba_tables
      2  where owner='NEW_USER';
    TABLE_NAME                     TABLESPACE_NAME
    T1_NEW_USER                    USERS1Now, We are going to perform the change at the database level regarding the default tablespace
    SQL> alter database default tablespace TEST;
    Database altered.Now, Let's go to see where the object is stored
    SQL> select TABLE_NAME, TABLESPACE_NAME from dba_tables
      2  where owner='NEW_USER';
    TABLE_NAME                     TABLESPACE_NAME
    T1_NEW_USER                    USERS1The object remain in the original tablespace assigned to the user new_user.
    Here We can realize that the change was successful but the table still remain in the original
    tablespace. You will have to move manually the objects to a new default tablespace.
    SQL> select USERNAME, DEFAULT_TABLESPACE from dba_users
      2  where username='NEW_USER';
    USERNAME                       DEFAULT_TABLESPACE
    NEW_USER                       TESTJoel Pérez
    http://otn.oracle.com/experts

  • Try to use easy connect to connect from isqlplus but to no avail

    Using the Easy Connect Naming Method
    from http://download.oracle.com/docs/cd/B19306_01/network.102/b14212/naming.htm#sthref783
    I want to connect from isqlplus remotely.
    pardon me if I ask this stupid question,
    do I need to install oracle client to use isqlplus. if yes, then no need to answer the above question.
    I mean with browser no doubt I can reach the url, but when it prompt for the connect string, i try to substitute the
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = globalro-417667)(PORT = 1522))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = tomkyte)
    so I wonder if I'm doing the right thing or not.
    thanks!

    Hi,
    See the link care fully, the page which you reffered it self says "This chapter describes how to configure connectivity information for client connections to the database server." So Client is required.
    Clients can connect to a database server using easy connect naming if the following conditions are met:
    - Oracle Database 10g Net Services software installed on the client.
    - Oracle TCP/IP protocol support on both the client and database server
    - No features requiring a more advanced connect descriptor are required
    Every thing is there in ORACLE Document.
    - Pavan Kumar N

  • Unable to use "easy connect" method to XE database

    All,
    I have an XE database running on Oracle Enterprise Linux. If I create a tnsnames.ora entry I can connect to the server fine. However, if I try to connect via the easy connect method
    sqlplus user@host:port:sid it fails with
    Enter password:
    ERROR:
    ORA-12545: Connect failed because target host or object does not exist
    the hostname I am using is definitely correct and I've also tried with ip address and get same error message. If I change from SID to SERVICE_NAME
    sqlplus user@host:port/service
    I get the following error message
    ERROR:
    ORA-12514: TNS:listener does not currently know of service requested in connect
    descriptor
    I've used both XE and xe as service name. The service name in my tnsnames.ora entry that works uses lower case xe for service name.
    Any help out there would be appreciated.

    Maybe this is more significant for you ?
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.
    C:\Documents and Settings\User1>sqlplus test/test@xe
    SQL*Plus: Release 10.2.0.1.0 - Production on Sat Feb 3 14:05:49 2007
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    ERROR:
    ORA-12154: TNS:could not resolve the connect identifier specified
    Enter user-name: test/[email protected]/xe
    Connected to:
    Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
    SQL> select * from v$version;
    BANNER
    Oracle Database 10g Express Edition Release 10.2.0.1.0 - Product
    PL/SQL Release 10.2.0.1.0 - Production
    CORE    10.2.0.1.0      Production
    TNS for Linux: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    SQL>

  • Connecting oracle using Directory Naming Method

    Hi,
    I am just checking the possibilities of implementing Directory Naming Method in our organization. currently we are using Local Naming method (using tnsnames.ora).
    I did google to find the pre-requsites to use directory naming method and I couldnt' find the right document.
    could somebody who has implemented and using directory naming method (via centralized LDAP-compliant directory server) could help me in finding the pre-requistes and what kind of infrastucture we should be having to implement the same in our organization.
    Thanks in advace for your help.
    Krishna.

    I'm trying to figure these things out myself.
    I have some questions for you:
    1. What operating systems does your server and workstations use?
    If they're all Windows and you're on a Windows Domain, consider Active Directory as the directory service.
    2. If it is all unix-like operating systems, consider using Oracle Internet Directory as the directory service.
    3. Mixed Windows and Unix-like operating systems - use whatever you are currently using as the directory service.
    At http://tahiti.oracle.com/ you may want to read some of the following books from oracle:
    - Platform Guide for Microsoft Windows (if you're using Windows)
    - Advanced Security Administrator's Guide
    - Enterprise User Security Administrator's Guide
    - Net Services Administrator's Guide
    - Net Services Reference
    - Oracle Internet Directory Administrator's Guide
    - Oracle Database 2 Day DBA
    Options to consider: Kerberos or Active Directory
    If using Windows and you already using Active Directory, consider this:
    Microsoft Environment: Configuring Oracle Advanced Security Option (ASO) Kerberos Adapter with Windows 2003 Active Directory
    See Metalink doc-id: 368321.1

  • NET8의 LOCAL NAMING METHODS 이용관련 CHECK POINTS & TROUBLESHOOTING

    제품 : SQL*NET
    작성날짜 : 2000-12-15
    ===================================================================
    Net8의 Local Naming Methods 이용관련 Check Points & Troubleshooting
    ====================================================================
    Net8 관련 내용중 Local Naming Methods(sqlnet.ora와 tnsnames.ora
    를 이용해서 DB에 Connect하는 방법)에 관한 일반적인 Check Points 및
    Troubleshooing 사항을 정리해보도록 하겠다.
    [Client Connection : Local Naming Methods]
    1. Local Naming method resolves service names by using the local configuration files tnsnames.ora and sqlnet.ora.
    2. One of the benefits of the Local Naming method is that it provides a simple method for resolving service name addresses. It is easy to configure local naming by using a GUI called the Net8 Assistant. When you configure a client machine for local naming by using the Net8 Assistant, a tnsnames.ora file is generated. To configure all the other client machines on the network that need to use the same database services, you can simply copy this file to the client machines.
    3. Another benefit of using the local-naming method is that it resolves service name across networks running different protocols.
    [Local Naming : Configuration]
    1. The local-naming method resolves service names by using the information configured and stored on each individual client. Local naming is most appropriate for simple distributed networks with a small number of services that change infrequently.
    2. Local naming requires the configuration of two local files, tnsnames.ora and sqlnet.ora. The tnsnames.ora file contains the address needed to direct a connection request to the specified listener on the specified node by using the specified database. The sqlnet.ora file stores information about the selected naming method.
    3. Local naming is easy to configure by using the Net8 Assistant. The Net8 Assistant is implemented in Java and is packed with the Java Runtime Environment. You can run the Net8 Assistant on any platform on which Net8 is installed.
    4. When you configure an Oracle8 server to use the local-naming method for service names resolution, the client-side configuration files tnsnames.ora and sqlnet.ora are automatically generated. After the configuration is complete, you copy these two files from the server to the client machines.
    [Client Files : Parameters]
    1. The tnsnames.ora and sqlnet.ora files are generated at the default location ORACLE_HOME\net80\admin.
    2. The first parameter in the tnsnames.ora file specifies the service name and the domain name for the client.
    3. The tnsnames.ora file contains a parameter called DESCRIPTION. This parameter contains information about the connect descriptor for the client.
    4. The ADDRESS parameter in the tnsnames.ora file specifies the network address of the host to which the client is connected. If multiple addresses are specified, use the keyword ADDRESS_LIST before the ADDRESS parameter.
    5. Another parameter in the tnsnames.ora file is the CONNECT_DATA parameter. This parameter specifies the SID of the database to which the client is connected.
    6. The DEFAULT_DOMAIN parameter of the sqlnet.ora file specifies the domain from which the client most often requests names. When this parameter is set, the domain name is automatically appended to the service name in a connect string.
    7. The DIRECTORY_PATH parameter is another key parameter of the sqlnet.ora file. This parameter specifies the names resolution method to be used for the client-server connection.
    8. The sqlnet.ora file also contains a parameter called DEFAULT_ZONE.
    This parameter specifies the region to which the client belongs.
    [Troubleshooting the Client Side]
    These are common client-side problems and the error messages associated with
    each error code.
    ORA-12154: "TNS: could not resolve service name"
    ORA-12198: "TNS: could not find path to destination"
    ORA-12203: "TNS: unable to connect to destination"
    ORA-12533: "TNS: illegal ADDRESS parameters"
    1. The ORA-12154 error occurs when Net8 cannot locate the connect descriptor specified in the tnsnames.ora configuration file. To solve this problem, first verify that a tnsnames.ora file exists and is accessible. Next, verify that multiple copies of the tnsnames.ora file are not present. After checking the existence of the tnsnames.ora file, verify that the service name specified in the connect string is mapped to a connect descriptor in the tnsnames.ora file. Verify also that the file does not contain any syntaz errors. The ORA-12154 error also occur if there is more than one copy of the sqlnet.ora file. Verify that duplicate copies of the sqlnet.ora file are not present.
    2. The ORA-12198 and ORA-12203 errors occur when the client is unable to find the required database. To solve this problem, first verify that you have correctly entered the service name that you want to use. Next verify that the service name parameters in the ADDRESS section of the connect descriptor in the tnsnames.ora file are correctly defined. Then, verify that the tnsnames.ora file is stored in the correct directory. The ORA-12198 and ORA-12203 errors can also occur if the listener on the remote node is not running. Verify that the listener on the remote node has started and is running. If the listener is not running, start the listener by using the Listener Control(LSNRCTL) utility.
    3. The ORA-12533 error occurs if the protocol-specific parameters in the ADDRESS section of the designated connect descriptor in the tnsnames.ora file are incorrect. To solve this problem, use the correct protocol-specific parameters in the ADDRESS section of the connect descriptor.
    4. The ORA-12545 error occurs when the listener on the remote node cannot be contacted. This may happen if the values of the ADDRESS parameter in the tnsnames.ora file and the listener.ora file are incorrect. In this case replace the incorrect values with the correct values in both the files. The ORA-12545 error can also occur if the listener on the remote node is not
    started. To verify whether or not the listener is started, determine its status with the STATUS command of the LSNRCTL utility. If necessary, start the listener on the remote node with the START command.

    제품 : SQL*NET
    작성날짜 : 2000-12-15
    ===================================================================
    Net8의 Local Naming Methods 이용관련 Check Points & Troubleshooting
    ====================================================================
    Net8 관련 내용중 Local Naming Methods(sqlnet.ora와 tnsnames.ora
    를 이용해서 DB에 Connect하는 방법)에 관한 일반적인 Check Points 및
    Troubleshooing 사항을 정리해보도록 하겠다.
    [Client Connection : Local Naming Methods]
    1. Local Naming method resolves service names by using the local configuration files tnsnames.ora and sqlnet.ora.
    2. One of the benefits of the Local Naming method is that it provides a simple method for resolving service name addresses. It is easy to configure local naming by using a GUI called the Net8 Assistant. When you configure a client machine for local naming by using the Net8 Assistant, a tnsnames.ora file is generated. To configure all the other client machines on the network that need to use the same database services, you can simply copy this file to the client machines.
    3. Another benefit of using the local-naming method is that it resolves service name across networks running different protocols.
    [Local Naming : Configuration]
    1. The local-naming method resolves service names by using the information configured and stored on each individual client. Local naming is most appropriate for simple distributed networks with a small number of services that change infrequently.
    2. Local naming requires the configuration of two local files, tnsnames.ora and sqlnet.ora. The tnsnames.ora file contains the address needed to direct a connection request to the specified listener on the specified node by using the specified database. The sqlnet.ora file stores information about the selected naming method.
    3. Local naming is easy to configure by using the Net8 Assistant. The Net8 Assistant is implemented in Java and is packed with the Java Runtime Environment. You can run the Net8 Assistant on any platform on which Net8 is installed.
    4. When you configure an Oracle8 server to use the local-naming method for service names resolution, the client-side configuration files tnsnames.ora and sqlnet.ora are automatically generated. After the configuration is complete, you copy these two files from the server to the client machines.
    [Client Files : Parameters]
    1. The tnsnames.ora and sqlnet.ora files are generated at the default location ORACLE_HOME\net80\admin.
    2. The first parameter in the tnsnames.ora file specifies the service name and the domain name for the client.
    3. The tnsnames.ora file contains a parameter called DESCRIPTION. This parameter contains information about the connect descriptor for the client.
    4. The ADDRESS parameter in the tnsnames.ora file specifies the network address of the host to which the client is connected. If multiple addresses are specified, use the keyword ADDRESS_LIST before the ADDRESS parameter.
    5. Another parameter in the tnsnames.ora file is the CONNECT_DATA parameter. This parameter specifies the SID of the database to which the client is connected.
    6. The DEFAULT_DOMAIN parameter of the sqlnet.ora file specifies the domain from which the client most often requests names. When this parameter is set, the domain name is automatically appended to the service name in a connect string.
    7. The DIRECTORY_PATH parameter is another key parameter of the sqlnet.ora file. This parameter specifies the names resolution method to be used for the client-server connection.
    8. The sqlnet.ora file also contains a parameter called DEFAULT_ZONE.
    This parameter specifies the region to which the client belongs.
    [Troubleshooting the Client Side]
    These are common client-side problems and the error messages associated with
    each error code.
    ORA-12154: "TNS: could not resolve service name"
    ORA-12198: "TNS: could not find path to destination"
    ORA-12203: "TNS: unable to connect to destination"
    ORA-12533: "TNS: illegal ADDRESS parameters"
    1. The ORA-12154 error occurs when Net8 cannot locate the connect descriptor specified in the tnsnames.ora configuration file. To solve this problem, first verify that a tnsnames.ora file exists and is accessible. Next, verify that multiple copies of the tnsnames.ora file are not present. After checking the existence of the tnsnames.ora file, verify that the service name specified in the connect string is mapped to a connect descriptor in the tnsnames.ora file. Verify also that the file does not contain any syntaz errors. The ORA-12154 error also occur if there is more than one copy of the sqlnet.ora file. Verify that duplicate copies of the sqlnet.ora file are not present.
    2. The ORA-12198 and ORA-12203 errors occur when the client is unable to find the required database. To solve this problem, first verify that you have correctly entered the service name that you want to use. Next verify that the service name parameters in the ADDRESS section of the connect descriptor in the tnsnames.ora file are correctly defined. Then, verify that the tnsnames.ora file is stored in the correct directory. The ORA-12198 and ORA-12203 errors can also occur if the listener on the remote node is not running. Verify that the listener on the remote node has started and is running. If the listener is not running, start the listener by using the Listener Control(LSNRCTL) utility.
    3. The ORA-12533 error occurs if the protocol-specific parameters in the ADDRESS section of the designated connect descriptor in the tnsnames.ora file are incorrect. To solve this problem, use the correct protocol-specific parameters in the ADDRESS section of the connect descriptor.
    4. The ORA-12545 error occurs when the listener on the remote node cannot be contacted. This may happen if the values of the ADDRESS parameter in the tnsnames.ora file and the listener.ora file are incorrect. In this case replace the incorrect values with the correct values in both the files. The ORA-12545 error can also occur if the listener on the remote node is not
    started. To verify whether or not the listener is started, determine its status with the STATUS command of the LSNRCTL utility. If necessary, start the listener on the remote node with the START command.

  • Windows "Easy Connect" does not reply with the password / "Easy Connect is not Available"

    Hello,
    I have posted a related question some time ago, which was eventually resolved. However, after some time a problem with Easy Connect (used for MSRA) came back:
    Whenever I arrive at the point in setting up a MSRA session where Easy Connect is needed, I get the reply: "Easy Connect is not Available". Here is an example of the problem:
    Start MSRA
    --> as expected, a window with "invite someone to help you" and " Help some who has invited you" appears
    Select "invite someone to help you"
    --> as expected, a window with "Who do you want to get help from" appears 
    Select "Invite someone to help you"
    --> as expected, a windows with "How do you want to invite your trusted helper?" appears
    Select "Use Easy Connect"
    --> as expected, the temporary "Create invitation window / checking network capabilities" window appears
    Next, I would expect this windows to close a new window to provide me with the Easy Connect password. However, instead I get the window "Easy Connect is not available".
    I cannot continue. (I have screenshots so can repost with them if that would clarity my question)
    Any suggestion how to resolve would be appreciated.
    (Please do not reply with the 3 suggestions from the FAQ (both computers must run windows 7 / Access to internet is limited / your router does not support Easy Connect - doesn't help)
    More background information and things I have tried:
    The "Easy Connect is not available" window offers the "Tell me more about how to fix this problem" which I have tried, but those suggestions do not help
    If I use the other MSRA option: "Help someone who has invited you" (this would be my typical use case), followed by "help someone new" and than select "Use Easy Connect", I also get the "Easy Connect is not available"
    window instead of the expected option to enter the Easy Connect password. I believe this is that same problem.
    This happed with both the 32 as well as the 64 MSRA versions
    I'm using Window 7 Ultimate, 64 bit with all the latest updates
    This desktop PC is wired to the internet via an Edimax gigabit switch, a Dlink DIR-855 wireless router and a fiber modem in bridge mode
    The W7 desktop has a single active network connection only
    I'm using Windows Firewall and Windows Security Essentials
    Disabling the firewall on the PC did not help
    Network discovery is enabled in Control Panel\All Control Panel Items\Network and Sharing Center\Advanced sharing settings (that’s UPnP – right?)
    The Internet Connectivity Evaluation Tool does not seem to be available anymore from MSFT sites
    Restarting "Peer Name Resolution Protocol" did not help
    Restarting "Peer Networking Identity Manager Properties" did not help
    Starting up with a "Clean Boot" (disabled all non-Microsoft services using MSConfig) did not help
    I would also be interested to understand how I can check on the status of the "Easy Connect" service. Is this a service hosted somewhere, or??
    Thanks!

    Dear Andy,
    Thanks a lot for your reply. Let me answer your questions:
    Q: Could you use the other methods: save this invitation as a file and use e-mail to send invitation?
    A: yes, that way I can establish a MSRA connection
    Q: Have you disable other network connections, including disable all virtual network card?
    A: if I check with ‘Device Manager/Network Adapters’ (or Control Panel/Network and Internet/Network Connections) I see two network adapters (my Asus motherboard has two network connectors). Both are available, but only one is used. I have
    disabled one. Unfortunately, this does not solve the problem. I will leave it disable for now.
    Q: To find detailed information about this issue, please locate to event view and find the logs about remote assistance.
    A: I have to admit that the Event Viewer is unfamiliar territory for me. So, I’m not sure where and what to look for. However, as suggested, I found "Event Viewer (local)/Applications and Services Logs/Microsoft/Windows/Remote assistance/Operational".
    Each time, I attempt to use MSRA/Easy Connect, it seems two entries are added. As I cannot seem to upload files with this post, here are just the two entries:
    “Diagnosis Repro Attempt resulted in a failure.”
    “Remote Assistance troubleshooting has confirmed the problem: Remote Assistance Easy Connect isn't available.”
    If you need more details, please suggest what to forward or check. I'm eager to find a solution!
    W.

  • Naming Method Use

    Hi,
    TNSNAMES.ORA
    MASTER=(DESCRIPTION=
    (ADDRESS=
    (PROTOCOL=tcp)
    (HOST=TELSTAR)
    (PORT=1521))
    (CONNECT_DATA=
    (SERVICE_NAME=LOC)))
    SQLNET.ORA
    NAMES.DEFAULT_DOMAIN=US.TELSTAR.COM
    NAMES.DIRECTORY_PATH=(LDAP, TNSNAMES, HOSTNAME)
    In here why it uses LDAP?.... Whts the purpose of using LDAP here!
    What is the naming method using here....
    ThankX
    Edited by: Ushman on Sep 15, 2008 4:06 PM

    names.directory_path:- Specifies the order of naming methods that are used when a client tries to connect to a database.
    If you are not using LDAP then simply delete it. LDAP here, refers to Oracle internet Directory a component or Oracle Application Server.
    Regards
    Christopher Soza
    Orix Consultancy Services Ltd

  • PDO Connection to a local 10G DB

    Hello together,
    i am using Zend IDE for PHP-Development and have the following problem:
    $dbh = new PDO('oci:dbname=LOCAL.ABC.XYZ.ORG','scott','tiger');
    connects to the local database inside the IDE without a problem.
    Running this login.php script over http://.... inside the browser over an Apache 2.x doesn't connect and i get a script time out.
    The settings for the php.ini files (Zend IDE and PHP 5.1.2 installation) are the same.
    Is there a solution out ?
    Thanks for your help.
    Hans

    Other than the typo in the previous comment, the Easy Connect syntax
    is often an easier way to connect in PDO, ADOdb, or oci8. If the Oracle
    client libraries that PHP links with are 10g or 10gR2, you can use the
    connect string "[/]hostname[:port][service_name]". For example to
    connect to the HR schema on the local XE database in PDO you can use:
    <?php
      try {
        $dbh = new PDO('oci:dbname=localhost/XE', 'HR', 'HRPASSWORD');
      catch (PDOException $e) {
        echo 'Connection failed: ' . $e->getMessage();
        exit;
      $s = $dbh->prepare("select city from locations");
      $s->execute();
      while ($r = $s->fetch(PDO::FETCH_ASSOC)) {
        echo $r['CITY'] . "<br>";
    ?>

  • ORA-12514 with Easy Connect only

    Greetings,
    On linux with a recent local install of Oracle XE:
    $ echo ORACLE_SID
    XE
    $ sqlplus system...works fine with nothing output to listener.log. I can connect no problem. However if I try:
    $ sqlplus system@localhost:1521/XEI get the following in listener.log:
    08-SEP-2008 14:03:11 * (CONNECT_DATA=(SERVICE_NAME=XE)(CID=(PROGRAM=sqlplus)(HOST=my.host.local)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=42572)) * establish * XE * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptorTnsping works:
    $ tnsping XE
    *+...+*
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = XE)))
    OK (0 msec)My tnsnames.ora is:
    $ cat /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/network/admin/tnsnames.ora
    # tnsnames.ora Network Configuration File:
    XE =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = XE)
    EXTPROC_CONNECTION_DATA =
      (DESCRIPTION =
        (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
        (CONNECT_DATA =
          (SID = PLSExtProc)
          (PRESENTATION = RO)
      )I put the listener in trace at the SUPPORT level. I can post that dump as well if it would help?
    Without the Easy Connect connection identifier is it that I'm connecting via IPC? This is preventing me from remotely connecting via sqlplus or JDBC over an SSH tunnel of 1521 (the box is firewalled).
    Thanks!
    Ian
    Edited by: ibrandt on Sep 8, 2008 2:29 PM - Fixed unintended wiki markup.
    Edited by: ibrandt on Sep 8, 2008 3:19 PM - Formatting.

    Well, I've gotten it to work by changing 'localhost' to 'myhost.mydomain.local' (name changed to protect the innocent) in tnsnames.ora and listener.ora, adding myhost.mydomain.local to my local DNS server such that it resolves to eth0's external IP, and restarting oracle. After that...
    $ lsnrctl status XE
    LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 09-SEP-2008 12:08:07
    Copyright (c) 1991, 2005, Oracle.  All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myhost.mydomain.local)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=XE)))
    STATUS of the LISTENER
    Alias                     LISTENER
    Version                   TNSLSNR for Linux: Version 10.2.0.1.0 - Production
    Start Date                09-SEP-2008 12:07:29
    Uptime                    0 days 0 hr. 0 min. 37 sec
    Trace Level               support
    Security                  ON: Local OS Authentication
    SNMP                      OFF
    Default Service           XE
    Listener Parameter File   /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/network/admin/listener.ora
    Listener Log File         /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/network/log/listener.log
    Listener Trace File       /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/network/trace/listener.trc
    Listening Endpoints Summary...
      (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC_FOR_XE)))
      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=myhost.mydomain.local)(PORT=1521)))
      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=8081))(Presentation=HTTP)(Session=RAW))
    Services Summary...
    Service "PLSExtProc" has 1 instance(s).
      Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
    Service "XE" 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...
    The command completed successfully...which is notably different from before. After that I can connect with:
    sqlplus system/password@localhost/XEAlso of note, using the external IP directly in tnsnames.ora and listener.ora did not work.
    So my new question is, why does Oracle need a HOST=hostname--where hostname resolves to an external IP--to startup correctly? Though I have 1521 firewalled from the outside world it seems like an unnecessary security hole.

Maybe you are looking for