Newbie in Learning Oracle Failed to connect

Hi everybody,
Just bought a book titled "Oracle 10g: SQL" by Joan Casteel, installed the Oracle 10g software that comes with the book, I was looking for a database using the Administration Assistant for windows, unable to find it, I search the internet, figured out need to create them manually, so used Database Configuration Assistant to create a General Purpose database (locally-IPC), now problem is unable to connect to this database either through the Administration Assistant for windows or SqlPlus, I created a couple of service name and listener using Net Manager, and use this service name to connect in the Administration assistant, but tells no Listener, what does it mean? How to solve this? In the SqlPlus, I use SYS, System, to logon, leaving Host string blank (as I read by it connects default), it tells me something like "ORA-01033: Oracle initialization or shutdown in progress","ORA-12541: TNS:no listener" and others??
Please provide details steps to check/to do...
Thanks in advanced.

Hi,
http://<computername>:5560/isqlplus in browser, nothing happens..Page cannot be displayed..
You are on windows.Check that the service of isqlplus is running ornot ? Also try replacing computer name with just localhost so that its read as http://localhost:5560/isqlplus
I learned that there is no utoincrement in Oracle right? It is used to autoincrement a column usually applied to rpimary key columns..Need to create a sequence and a trigger to accomplish this?
I am sorry but I didnt understand this part. For what you are trying autoincrement? Can you please rephrase your question ?
If I like to a saved a backup copy of actual database data, is it found in <oracle directory>\product\<version>\<Db home>\database folder?? files with .ora extensions? are those the data files?
No the files in the datbase folder are the software files used by Oracle software to run smoothly.Well smoothly or not but they are must for the software to run :).
There will be another folder in the path eg c:\oracle\product\10.2.0\admin\your_db_name\oradata
In the oradata folder, you will find couple of *.dbf files.As the name suggests , these are the database files. They actualy contain the data that you are going to store in your db.In addition to these, there will be few *.ctl and *.log files too. They represent control files and redo log files. It will be a long reply if I shall start telling about what these files do and contain.So I suggest that you shoudl read oracle Admin guide which explains all of these things very nicely.You can read about it here,
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/toc.htm
For the backup concepts I suggest you should read backup guide which is here,
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/toc.htm
This will explain the concepts which are must for anyone to start with Oracle db.
Sorry for lots of questions...:D
Absolutely no issues with lots of questions.Some one said this to me and I am repeating. No questio is stupid ever, there are always stupid answers. So if you are asking, it means you are keen to know and that's what the right path is. I ask alot and one can only learn by asking , sharing his knowledge.
Aman....

Similar Messages

Oracle 11G DG ,ERROR"PING[ARC2]: Heartbeat failed to connect to standby 'wnadsdy'. Error is 1033."

主库一直报错，提示如下： Error 1033 received logging on to the standby FAL[server, ARC0]: Error 1033 creating remote archivelog file 'wnadsdy' FAL[server, ARC0]: FAL archive failed, see trace file. Error 1033 received logging on to the standby PING[ARC2]: Heartbeat failed to connect to standby 'wnadsdy'. Error is 1033. tnsping 可以Ping 到备库 wnadsdy primary ip 172.31.0.41 standby ip 1721.31.0.112 primary db initwnad.ora wnad.__db_cache_size=687865856 wnad.__java_pool_size=16777216 wnad.__large_pool_size=33554432 wnad.__oracle_base='/opr/oracle'#ORACLE_BASE set from environment wnad.__pga_aggregate_target=671088640 wnad.__sga_target=989855744 wnad.__shared_io_pool_size=0 wnad.__shared_pool_size=234881024 wnad.__streams_pool_size=0 *.audit_file_dest='/opr/oracle/admin/wnad/adump' *.audit_trail='db' *.compatible='11.2.0.4.0' *.control_files='/opr/oracle/wnad/control01.ctl','/opr/oracle/fast_recovery_area/wnad/control02.ctl' *.db_block_size=8192 *.db_domain='' *.db_name='wnad' *.db_recovery_file_dest='/opr/oracle/fast_recovery_area' *.db_recovery_file_dest_size=10737418240 *.diagnostic_dest='/opr/oracle' *.dispatchers='(PROTOCOL=TCP) (SERVICE=wnadXDB)' *.log_archive_dest_1='location=/opr/oracle/wnad/archive' *.log_archive_dest_2='SERVICE=wnadsdy' *.memory_target=1656750080 *.open_cursors=300 *.processes=150 *.remote_login_passwordfile='EXCLUSIVE' *.standby_file_management='AUTO' *.undo_tablespace='UNDOTBS1' listener.ora LISTENER= (DESCRIPTION= (ADDRESS_LIST= (ADDRESS=(PROTOCOL=TCP)(HOST=oracle-test)(PORT=1521)) ) ) SID_LIST_LISTENER= (SID_LIST= (SID_DESC= (SID_NAME=wnad) (ORACLE_HOME=/opr/oracle/product/11.2.0/db_1) (GLOBAL_DBNAME=wnad) ) ) tnsnames.ora WNAD= (DESCRIPTION= (ADDRESS_LIST= (ADDRESS=(PROTOCOL=TCP)(HOST=oracle-test)(PORT=1521)) ) (CONNECT_DATA= (SERVER = DEDICATED) (SERVICE_NAME=wnad) ) ) wnadsdy= (DESCRIPTION= (ADDRESS_LIST= (ADDRESS=(PROTOCOL=TCP)(HOST=oracle-test2)(PORT=1521)) ) (CONNECT_DATA= (SERVER = DEDICATED) (SERVICE_NAME=wnad) ) ) standby db initwnad.ora wnad.__db_cache_size=687865856 wnad.__java_pool_size=16777216 wnad.__large_pool_size=33554432 wnad.__oracle_base='/opr/oracle'#ORACLE_BASE set from environment wnad.__pga_aggregate_target=671088640 wnad.__sga_target=989855744 wnad.__shared_io_pool_size=0 wnad.__shared_pool_size=234881024 wnad.__streams_pool_size=0 *.audit_file_dest='/opr/oracle/admin/wnad/adump' *.audit_trail='db' *.compatible='11.2.0.4.0' *.control_files='/opr/oracle/wnad/control01.ctl','/opr/oracle/fast_recovery_area/wnad/control02.ctl' *.db_block_size=8192 *.db_domain='' *.db_name='wnad' *.diagnostic_dest='/opr/oracle' *.dispatchers='(PROTOCOL=TCP) (SERVICE=wnadXDB)' *.log_archive_dest_1='location=/opr/oracle/wnad/archive' *.memory_target=1656750080 *.open_cursors=300 *.processes=150 *.remote_login_passwordfile='EXCLUSIVE' *.standby_file_management='AUTO' *.undo_tablespace='UNDOTBS1' listener.ora LISTENER= (DESCRIPTION= (ADDRESS_LIST= (ADDRESS=(PROTOCOL=TCP)(HOST=oracle-test2)(PORT=1521)) ) ) SID_LIST_LISTENER= (SID_LIST= (SID_DESC= (SID_NAME=wnad) (ORACLE_HOME=/opr/oracle/product/11.2.0/db_1) (GLOBAL_DBNAME=wnad) ) ) tnsnames.ora wnad= (DESCRIPTION= (ADDRESS_LIST= (ADDRESS=(PROTOCOL=TCP)(HOST=oracle-test)(PORT=1521)) ) (CONNECT_DATA= (SERVER = DEDICATED) (SERVICE_NAME=wnad) ) ) wnadsdy= (DESCRIPTION= (ADDRESS_LIST= (ADDRESS=(PROTOCOL=TCP)(HOST=oracle-test2)(PORT=1521)) ) (CONNECT_DATA= (SERVER = DEDICATED) (SERVICE_NAME=wnad) ) )

Hello;
Very difficult to read your post.
If your standby is in "recovery - mount" a 1033 is normal assuming you are trying to shut down the standby.
Otherwise try this query on the standby:
select process, client_process, sequence#, status from V$managed_standby;
If there is a MRP or a MRP0 process, the database is performing managed recovery. Otherwise It's not ready and you may have found your cause.
Best Regards
mseberg

REP-56110: Failed to connect to security repository Oracle Portal.

Dear All,
I need your help on the error REP-56110: Failed to connect to security repository Oracle Portal.
I have installed Oracle Application Server 10g R2.
I have enabled SSO for form Sevice and Report Service.
I created OID user login and map it to my database user (on which my Application Run).
When i run my application, SSO page apear. I login it with user id and Password and My application Runing Succesfully. But when i call Reports from my Application through Run_Repor_Object or Web.Show document. I get the error REP-56110: Failed to connect to security repository Oracle Portal.
my oid user id and passwor is as follow
username = ssotest
password = ssotest1
IF i run rwservlet command. It is showing the Server page with Secure mode.
http://server:7778/reports/rwservlet/showjobs?
What is the reasong behind this? Help me out.
http://server/reports/rwservlet?destype=cache&desformat=pdf&report=sr_master.rdf&FromDate='01-JAN-12'&ToDate='31-DEC-12'&SSOConn=test/OracleDB/ssotest
where -- test is my Resoruce Name define in OID
oracleDB Resource Type
ssotest my sso user name
Edited by: Meherban Khan on Mar 27, 2012 6:21 AM

I changed %PORTAL_DB_USERNAME%/%PORTAL_DB_PASSWORD%@%PORTAL_DB_TNSNAME%
with the actual username/password of the portal schema. Now i get the following Error.
REP-56071: Security check failed with error message: Error code30004 - Cannot access the output type:cache
In package:wwv_rw_usr function:security_check
Command line is: server=rep_portal_form_report_services report=KPIx/Churn Analysis/ChurnByAgeGroup.jsp destype=cache desformat=html rundate="27-DEC-05 12:12:20"
Executed on:12/27/05 12:12:29

Can anyone help me with this-"network adaptor failed to connect"

hi,
i just starting to learn oracle..so installed oracle 11g R2 and sql developer on my laptop..when i tried to connect to the database i get this error
"network adaptor failed to connect"..
help will be thankful..

Welcome to the forums !
What is the OS ? 11gR2 is only supported on Win 7 - http://download.oracle.com/docs/cd/E11882_01/install.112/e10843/reqs.htm#CHDHGGFE
HTH
Srini

OBIEE 11g agents are failed to connect to Essbase

OBIEE 11g agents are failed to connect to Essbase. We are using :USER & :PASSWORD (SSO) in connection pool setting to connect to Essbase.
User account exists in both OBIEE and Essbase. OBIEE dashboards which are based on Essbase are working fine. Essbase variables in RPD are upto date.
Only agents are failing and error says invalid credentials, but dashboard pages are running without any issue.
OBIEE: 11.1.1.5 (BP4)
Essbase: 11.1.2.1
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 96002] Essbase Error: Login fails due to invalid login credentials (HY000)
Essbase and OBIEE services are up and running.
Any help will be appreciated.

We finally implemented CSS Token option and ended up with this error. We are unable to connect to essbase with CSS Token option.
We followed the Oracle document to implement this.
[nQSError: 43119] Query Failed: EPMCSS-00301: Failed to authenticate user. Invalid credentials. Enter valid credentials. (HY000)
We did update this property:
JAVA_PROPERTIES="-Dplatform.home=${WL_HOME} -Dwls.home=${WLS_HOME} -Dweblogic.home=${WLS_HOME} -Didstore.identityAttribute=objectguid"
Any help will be appreciated!

Error in Creating the Oracle Fail Safe Group during installation on MSCS

Hi All,
I am installing ECC 6 dual stack on MSCS.
I have done steps till CI installation as per installation guide.
I am gettig the following error in the step "Creating the Oracle fail safe group" while changing physical hostname into the virtual databse hostname using configtool in secure store parameter jdbc/pool/<SAPSID>Url as per the installation guide.
"Error occurred while working with configuration(scanning)
MSG:Error while connecting to the database"
I think it is not accepting the virtual hostname.
In our scenario CI is running CI node and DB instance is running on DB node.
I have followed the steps as per the installation guide.
Please let me know how to resolve this issue.
Database - Oracle 10g,OS is Windows server 2008 enterprse edition.
Regards,
Dinakar
Edited by: mutnuru dinakar on Jun 1, 2011 1:39 PM
Edited by: mutnuru dinakar on Jun 1, 2011 1:40 PM

Hi,
Thanks for your reply.
1) did you stop the CI before making the modifications as stated in the installation guide?
     Yes
2) is your database currently running on the same physical cluster node as your CI?
    No.Database instance is running on DB node and CI is on CI node.
3) is your database online?
     Yes,it is up and running
Please let me know if there is anyway to resolve this issue.
Regards,
Dinakar

Apex fails to connect after rebooting XE

Hi:
My environment is Apex 4.0.0, Oracle XE 10.2.0, Apex default Gateway, Windows 2008 32 bit.
After I reboot the database, Apex fails to connect.
If I check the Apex port number, it lists 8080, as expected. (SELECT DBMS_XDB.GETHTTPPORT FROM DUAL;)
Look at the Oracle Listener status below after the reboot, notice the host value in line
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=8080))(Presentation=HTTP)(Session=RAW))
When I reset the Apex port number to 8080, I can then connect OK (EXEC DBMS_XDB.SETHTTPPORT(8080); )
Look at value of HOST in the Oracle Listener status below after the reset, the HOST lists the Server Name.
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=galapp13.bsci.bossci.com)(PORT=8080))(Presentation=HTTP)(Session=RAW))
This is a major problem, because if the Server is rebooted, nobody can connect to Apex.
I assume this is an Oracle Listener problem.
I have made no changes to the LISTENER.ora file, see values below.
Any suggestions on how to overcome this problem will be helpful.
Status of Oracle Listener after a reboot.
LSNRCTL> status
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 - Production
Start Date 02-JUN-2011 09:03:47
Uptime 42 days 22 hr. 31 min. 5 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Default Service XE
Listener Parameter File D:\oraclexe\app\oracle\product\10.2.0\server\network\admin\listener.ora
Listener Log File D:\oraclexe\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=galapp13.bsci.bossci.com)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=8080))(Presentation=HTTP)(Session=RAW))
Status of Listener after resetting the Port number to 8080, notice the HOST = a ServerName in line:
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=galapp13.bsci.bossci.com)(PORT=8080))(Presentation=HTTP)(Session=RAW))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production
Start Date 02-JUN-2011 09:03:47
Uptime 42 days 22 hr. 34 min. 40 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Default Service XE
Listener Parameter File D:\oraclexe\app\oracle\product\10.2.0\server\network\admin\listener.ora
Listener Log File D:\oraclexe\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=galapp13.bsci.bossci.com)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=galapp13.bsci.bossci.com)(PORT=8080))(Presentation=HTTP)(Session=RAW))
The parameters in LISTENER.ora
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = D:\oraclexe\app\oracle\product\10.2.0\server)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = CLRExtProc)
(ORACLE_HOME = D:\oraclexe\app\oracle\product\10.2.0\server)
(PROGRAM = extproc)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
(ADDRESS = (PROTOCOL = TCP)(HOST = galapp13.bsci.bossci.com)(PORT = 1521))
DEFAULT_SERVICE_LISTENER = (XE)

Hi
Where did you find the latest WLan driver?
Here on this Toshiba driver page you can find the latest Wlan driver:
http://aps2.toshiba-tro.de/wlan/
I recommend uninstalling firstly the old driver and then to install the newer version.
Furthermore its necessary to update the BIOS. I read in the forum that similar issues could be solved by BIOS update.
Greets

New install of sqldeveloper 3.0.04.34 fails to connect

I exited the running sqldeveloper 3.0.03.45, and started the sqldeveloper exe for 3.0.04.34 which I have just downloaded and unzipped.
It asked to import settings.
When I try to open the imported connection to scott/tiger@//lambda/ora10 (where lambda is my local db server), I get this error text in a dialog box.
+-----------------------------------------------------------------------
|
| An error was encountered performing the requested
| operation:
|
| oracle.jdbc.driver.T2Connection.getLibraryVersionNumber()
| I
|
| Vendor code 0
|
+-----------------------------------------------------------------------
I'm sure that means something to a java developer, or perhaps even a jdbc developer, but it is meaningless, and absolutely useless to me.
My connection properties are
user: scott; password: tiger; save password: checked; connection type: TNS; role: default; connection identifier: //lambda/ora10
I am running Win7 on a AMD 64, using the 32 bit instant client and 32 bit sql developer
When I start sql plus:
..>which sqlplus.exe
E:\Oracle\x86\instantclient_11_1_0_7_0\sqlplus.exe
..>sqlplus scott/tiger@//lambda/ora10
SQL*Plus: Release 11.1.0.7.0 - Production on Mon May 9 18:36:51 2011
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL>
I have never installed a thick client on this machine.
I think I have the latest JRE (as automatically updated) installed.
..>which java.exe
C:\Windows\System32\java.exe
..>java -version
java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode)
and
D:\Program Files (x86)\Java\jre6\bin>.\java.exe -version
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode, sharing)
I think I have a very recent version of the JDK
D:\Program Files (x86)\Java\jdk1.6.0_23\bin>.\javac.exe -version
javac 1.6.0_23
How do I make this version of sqldeveloper work? What can I try next to help diagnose this problem?

I downloaded and installed a fresh copy of Instant Client 11.2.0.2.0 and added it to my path in place of the 11.1 client.
sql_developer 3.0.04.34 now works. However, sql_developer 2.1.1.64.45 now fails to connect with this error dialog:
+--------------------------------------------------------------
|
| An error was encountered performing the
| requested operation:
|
| oracle.jdbc.driver.T2Connection.t2cCreateState([BI
| [BI[BI[BI[BISI[S[B[BZ)I
|
| Vender code 0
|
+--------------------------------------------------------------
I suspect this is the reason I continued to use the 11.1 instant client. I could not easily evaluate the two versions of sql_developer when I also had to switch the instant client. My perception of the early adapter label is that it was another name for public beta. And that means: have a fall back option.
What do you mean by a regular simple connect? The scott/tiger@//lambda/ora10 connect string works when i run .\sqlplus.exe from all four of the instant clients I have here (10.2.0.4.0, 11.1.0.7.0, 11.2.0.1.0 and 11.2.0.2.0). My db server is on a linux box, but I run the client on a windows box.
Sorry about the duplicate thread.

SUNW.gds for jboss + Load Balancing Group = Failed to connect to host ...

Hi all!
In a simple two node cluster (Solaris cluster 3.2) with quorum server I've created a resource for jboss 5.1.0 using SUNW.gds. It is supposed to be load-balanced. To achieve that I've followed instructions from [http://download.oracle.com/docs/cd/E18728_01/html/821-1258/gds-25.html]
The command I've used to create the resource was:
clresource create -g scalable-rg -t SUNW.gds -p resource_dependencies=vip -p Scalable=TRUE -p Start_timeout=400 -p Stop_timeout=400 -p Probe_timeout=30 -p Port_list=8080/tcp -p Start_command="/opt/jboss-5.1.0.GA/bin/run.sh -b 0.0.0.0" -p Child_mon_level=0 -p Failover_enabled=TRUE -p Stop_signal=15 -p Load_balancing_policy=LB_STICKY_WILD jboss-rs
The whole configuration seems to work, but when the second node joins cluster, resource with jboss can't bind to shared ip address. There are many entries in /var/adm/messages like:
Jan 19 13:46:35 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 141062 daemon.error] Failed to connect to host vip and port 8080: Connection refused.
Jan 19 13:46:35 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 805735 daemon.error] Failed to connect to the host <vip> and port <8080>.
Jan 19 13:46:37 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 141062 daemon.error] Failed to connect to host vip and port 8080: Connection refused.
Jan 19 13:46:37 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 805735 daemon.error] Failed to connect to the host <vip> and port <8080>.
Jan 19 13:46:39 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 141062 daemon.error] Failed to connect to host vip and port 8080: Connection refused.
Jan 19 13:46:39 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 805735 daemon.error] Failed to connect to the host <vip> and port <8080>.
Jan 19 13:46:41 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 141062 daemon.error] Failed to connect to host vip and port 8080: Connection refused.
Jan 19 13:46:41 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 805735 daemon.error] Failed to connect to the host <vip> and port <8080>.
Jan 19 13:46:43 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 141062 daemon.error] Failed to connect to host vip and port 8080: Connection refused.
Jan 19 13:46:43 play SC[,SUNW.gds:6,scalable-rg,jboss-rs,gds_svc_start]: [ID 805735 daemon.error] Failed to connect to the host <vip> and port <8080>.
However, after some time, it finally somehow binds to shared ip and port 8080.
Is this something I should be worried about? Or it is a normal thing, since e.g. it takes some time to bring the interface with shared ip up? I've never had to install such configuration, and I don't have neither intuiton, nor the experience. Any help would be very appreciated.
Thanks a bunch,
Bart

Hi, a couple of things to check:
- did you check that both JBOSS instances were up and running?
- can you check in the logs (on both nodes) when a message saying something like "service .... registered..." showed up. This should show up for both JBOSS instances. From the time of the second "registered" message, the load balancer should sending incoming requests to both instances using its distribution mechanism
- did you check the vip address on one of the nodes on an external interface and on lo0 on the other
- connection refused looks like a server problem; can you connect to the JBOSS instance locally?
Hth
Hartmut

Failed to connect to database ONLY at the first time

Hi all, I installed Discoverer 10g version and I'm using an Application User to connect to the server where's the Db is installed.
Every time I try to connect to the server with Discoverer Viewer or Desktop I have a curious behavior....
ALWAYS but ONLY the first time I try to connect I have the following error :
- Failed to connect to database - Unable to connect to Oracle Applications database: invalid username/password.
If I try to re-connect again the second time it works perfectly !!....so, I think, there's nothing related with my .dbc file.
I tried also to write the ':' at the end of the user name....but it didn't work.
Into the pref.txt file doesn't exist a parameter like DefaultUserTypeIsApps to set....
Anybody have had the same "strange" behavior and found a solution or workaround ?
Thanks in advance
Alex

Thanks for your answers first of all !
At the end I found the solution looking at the Note:307167.1 on Metalink:
Discoverer Plus 10.1.2 Fails with ORA-1017 Error On First Login Attempt Then Works On Second Attempt
This note is very useful but into the solution the point 3 is not correct !
3. Modify the servername parameter to indicate the fully qualified servername.domain
Example:
An httpd.conf setting of: ServerName my_servername.mydomain.com should match a Discoverer Plus URL like http://my_servername.mydomain.com:7778/discoverer/plus
I had this problem both with Viewer and Plus...so instead to change the server name parameter (into the Apache/Apache/conf/httpd.conf file) with my complete URL (http://gnvdev.ote.gr:7779/discoverer/plus), I just write my right server name:
Example
After the installation of the Discoverer 1og server, into the httpd.conf file it was written automatyically: ServerName gnvdev
I just modified in ServerName gnvdev.ote.gr and both Viewer and Plus started to work perfectly at the first time.
I hope that this hint will be useful for you and others in the Discoverer forum !!!
Best Regards
Alex

JDBC fails to connect to 8.1.7.0.1 on Linux

Hi,
I compile and run the sample JDBCVersion program on a Win98 client PC. It works ok connecting to a Sparc 8.1.7.0.1. However, when it connects to 8.1.7.0.1 on Redhat 7.3, it gives the following error.
D:\Programs>java JDBCVersion
Exception in thread "main" java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:169)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:211)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:324)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:266)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:365)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at JDBCVersion.main(jdbcversion.java:10)
The strange thing is if the same program is run on the local Redhat 7.3 machine, it works fine!
I checked the listener.log file. The log message for the successful and unsuccessful cases are the same (of course except the HOST= field).
Is it a bug?
Regards,
John Lee

Hi Rahul,
Thanks for your response. I'm using Oracle Java Thin client. Environment is J2SE SDK 1.4.1_01 (uses classes12.zip from Oracle).
Successful cases
- Win98 can use ODBC and SQL*PLUS to connect to the remote Oracle8i
- Win98 can use JDBCVersion program to connect to a remote Oracle8i on Sparc and another Oracle9i on RedHat 7.3
- JDBCVersion can successfully connects to Oracle8i on Redhat 7.3 if it is run locally on the database server
Failed cases
- When JDBCVersion runs on Win98, it fails to connect to remote Oracle8i on Redhat 7.3
The log from listener.log shows that nothing special happens when JDBCVersion runs on Win98 to connect.
Any clues?
Regards,
John

RMAN Automatic backup/recovery with oracle fail safe, windows cluster

Hello,
I have question,
1) Whether it is possible to do "RMAN Automatic Backup and recovery" in environment as ?
Environment: -
a. Windows clustering with windows server 2003 Enterprise Edition R2 (Two Node Clustering)
b. Shared disk ( RAID )
c. Oracle 10g standard edition one
d. Oracle fail safe v3.3.3 (for redundancy)
Here we have single oracle instance operating on single database whose files are located on shared disk.
2) If answer to above question is yes please specify if there is some good documentation to it.
Any help regarding this will be greatly appreciated.
Thanks in advance,
Rahul

You just need to make sure that the RMAN scripts are always able to connect to the target database instance whether instance runs on cluster node 1 or cluster node 2
here, If oracle services(resources) will shift from Node1 to Node2 (due to media or any failure) during RMAN Backup then there will be break in connection, will it destroy my backup or will it get started automatically without any harm?
and also I want to know,
Do we need to setup another server which will have RMAN backup script running?

Database control in a two node oracle fail safe cluster

os windows server 2003 r2
db 10.2.0.4
ofs 3.4.1
i've configured db control in the following
D:\oracle\product\10.2.0\db_1\BIN>emca -config dbcontrol db -repos recreate -cluster_name name_of_the_cluster
is this right?
next question
the -cluster flag and the -EM_NODE / -EM_SID_LIST parameters in the emca are only for rac?
with my configuration i can't login to my database over dbcontrol
Listener refused the connection with the following error: ORA-12514, TNS:listener does not currently know of service requested in connect descriptor The Connection descriptor used by the client was: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1.blah)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ABBA)))

How to Configure the 10.2 DB Control in a Failsafe Environment
ID: 452305.1
HOWTO: PUBLISHED 17-OCT-2008
In this Document
   Goal
   Solution
   References
Applies to:
Enterprise Manager Grid Control - Version: 10.2.0.1 to 10.2.0.3
Information in this document applies to any platform.
Goal
The goal of the document is to provide the steps to configure the DB Console in an Oracle Failsafe environment.
Please note that the solution offered in this document is not certified by Oracle. It's only provided as a workaround for customers who wish to use this setup for the Database Control Console in a failsafe environment. Support for the procedure outlined in this document will be provided on a 'best efforts' approach.
As an alternative to this approach you can use Grid Control Agents to monitor a database in a failsafe environment. For more details please see:
Note 396659.1 How To Setup Grid Control Central Agent Manually in Oracle Failsafe Environment
We assume the following:
- the database binaries are installed on each node on the local disk
- you already have a failsafe group with the database, the listener, disk resource, and virtual
ip/hostname
Note: This is specific for Windows environments using Oracle Failsafe. For setting up the DB Console in Active/Passive clusters on UNIX please use the following note instead:
Note 362524.1 Configure DB Control 10.2 for use in Active/Passive High Availability Environments
Solution
1. Drop the DB Control repository and configuration files on the active node:
<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop
2. Recreate the DB Control using the virtual hostname:
- in a command window do the following:
set oracle_sid=<your_sid>
set oracle_home=<your_oracle_home>
set oracle_hostname=<virtual_hostname>
cd %oracle_home%\bin
emca -config dbcontrol db -repos create
-- make sure that the virtual host name was picked up by emca (it will display a summary screen
before continuing)
3. Verify that the DB Console works fine and can be accessed using the virtual host name in the URL
4. Stop the DB Console
5. Create a directory path on the group disk resource similar to your oracle home path on the local disk.
For example:
If the oracle home on the local disk is C:\oracle\product\10.2.0\db_1 and the shared disk is D:
then create the following path: D:\oracle\product\10.2.0\db_1
Copy C:\oracle\product\10.2.0\db_1\<hostname_sid> and
C:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
to D:\oracle\product\10.2.0\db_1\<hostname_sid> and respectively
D:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
Remember to change the values enclosed in <> with those in your environment.
6. Delete the following directories from the local disk
C:\oracle\product\10.2.0\db_1\<hostname_sid>
C:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
7. Create NTFS junction points from the local disk to the shared disk (these work like symbolic
links on UNIX) . It is your responsibility to create these.
You can find a brief guide as well as some tools that will help you create them at:
http://en.wikipedia.org/wiki/NTFS_junction_point
http://www.microsoft.com/technet ... dDisk/Junction.mspx
Important: Please note that this functionality is not certified nor supported by Oracle. Make sure you understand the
implications. Especially don't delete the junction points from Windows Explorer !!
In the end you should have the junction points on the local disk (with the same names as the
original directories) that would point to the directories you copied on the shared disk.
8. Start the DB Console service and verify that everything is still working fine.
9. Stop the DB Console service.
10. Move the Fail Safe group to the 2nd node.
11. Once the database is started, create the DB Console configuration files on the 2nd node:
<ORACLE_HOME>/bin/emca -config dbcontrol db
12. Stop the DB Console
13. Delete the created configuration files from the local disk:
C:\oracle\product\10.2.0\db_1\<hostname_sid>
C:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
14. Create junction points from the local disk to the directories already located on the shared
disk.
15. Start the DB Console service and verify that is working fine.
16. Add the DB Console service as a resource to the fail safe group and put dependencies on the
database and listener services.
17. Perform a fail over and see if everything works fine.
References
Note 298238.1 - Oracle10g Grid Control with Oracle Fail Safe
Note 362524.1 - Configure DB Control 10.2, 11g for use in Active/Passive High Availability Environments
Note 396659.1 - How To Setup Grid Control Central Agent Manually in Oracle Failsafe Environment
Keywords
EMCA ; DB~CONTROL ; FAILSAFE ; DBCONTROL ; ENTERPRISE~MANAGER ;

Suggested books/video series for learning oracle sql?

What are some good books/ videos for a beginner to learn oracle sql?
I learn best by being able to go through exercises.
I am using Oracle 11g express edition and sql developer. In sql developer I have only one connection to the HR schema.
Also, can I connect to the SCOTT schema in oracle 11g?

Hi,
The SQL Language reference is a great book, but its a bit dry for a beginner.
How about starting with the Getting Started and 2 Day guides here
http://docs.oracle.com/cd/E17781_01/index.htm
There are a lot of tutorials here as well
https://apex.oracle.com/pls/apex/f?p=44785:1:0::NO
google will also bring up lots of hits as well
Regards
Andre

ARC1: Heartbeat failed to connect to standby 'TEST10'. Error is 1031.

Hi Every one,
I m getting this error in alert log.
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'xxxx'
ORA-01031: insufficient privileges
*** 2003-11-30 18:55:30.984 49871 kcrr.c
ARC1: Heartbeat failed to connect to standby 'xxxx'. Error is 1031.
We tried to setup on same machine as well as on separate machine, but in both cases getting the same error.
Please guide me what should i do.
Thanks
Nadeem

If you are running oracle 10g, then, the following would be helpful.
Cause
The parameter DB_ALLOWED_LOGON_VERSION has not been set in the remote database.
DB_ALLOWED_LOGON_VERSION is a new parameter introduced in 10g that allows the DBA to explicitly determine which authentication protocols are allowed by the client or database.
The value specified is the earliest client version level supported by this database.
When clients earlier than the specified version attempt to connect, authentication will fail.
Solution
In the init.ora of the remote (Downstream capture) database, set the following : db_allowed_logon_version=10
Note: Bug 2981553, which is implemented in 10.1.0.2, removes the parameter db_allowed_logon_version. This is replaced by the sqlnet.ora parameter called sqlnet_allowed_logon_version.
Jaffar

Newbie in Learning Oracle Failed to connect

Similar Messages

Maybe you are looking for