TNS redirect on 2-node RAC returns unqualified hostname, should be FQDN

Hi,
our 2-node RAC (11gR1, Linux x64) listeners return only a host name without a domain when sending TNS redirects (when doing server side load balancing). Is there any way to configure them to send FQDNs? The listener.ora files are set up with FQDNs on both nodes.
I would really like the FQDNs because clients will be connecting from multiple DNS domains.

rcc50886 wrote:
We generally use VIP's (vip_name.domain) to connect to database from the client side, as long as vip_name.domain is resolved on client side you don't find any problem.We use the FQDN of the VIP address on the client side as well, the problem is the answer from the server side.
To avoid domain issues, you can add the domain name to /etc/resolv.conf on client server, with this entry you don't even specify the domain name.Unfortunately, I can not control all the clients which connect to this database.

Similar Messages

Dbms_schduler job is not running on a 2 node rac when 1st node fails

Hi,
I want to create a dbms_scheduler job in a 2 node RAC and the job should always run on the node1 and if node1 is down then it should run on node2. This is Oracle 10gR2 (10.2.0.3 in WINDOWS) .In order to do the same I did following
-- First Step
Using DBCA- Service Managment - Created a service (BATCH_SERVICE) and given node1 as preferred and node2 as available. This created following entry in tnsnames.ora in both nodes.
BATCH_SERVICE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = node1-vip)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = node2-vip)(PORT = 1521))
(LOAD_BALANCE = yes)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = BATCH_SERVICE)
(FAILOVER_MODE =
(TYPE = SELECT)
(METHOD = BASIC)
(RETRIES = 180)
(DELAY = 5)
--- Step 2
-- Created BATCH job classes.
BEGIN
DBMS_SCHEDULER.create_job_class(
job_class_name => 'BATCH_JOB_CLASS',
service => 'BATCH_SERVICE');
END;
-- Step 3 -- created a job using job_class as BATCH_JOB_CLASS
begin
dbms_scheduler.create_job(
job_name => 'oltp_job_test'
,job_type => 'STORED_PROCEDURE'
,job_action => 'schema1.P1'
,start_date => systimestamp at time zone 'US/Central'
,repeat_interval => 'FREQ=DAILY;BYHOUR=11;BYMINUTE=30;'
,job_class => 'BATCH_JOB_CLASS'
,enabled => TRUE
,comments => 'New Job.');
end;
Now when I monitor this job it runs on node1. Now I started testing for failover. I manually shutdown 1st instance. Then as per my understanding job should run on 2nd node. But job is not picking up.
when I run the followign command
srvctl status service -d db -s BATCH_SERVICE
service BATCH_SERVICE is running on instance node2.
Any help is really appreciated.

It does not show that whether job is running or broken.

How to add a second database along with existing two node RAC environment

Hi,
I was wondering if anyone can help me with this.
My Environment:
1. Two node RAC Cluster database (11.2.0.2) with ASM running perfectly (Oracle Sid = test-1)
2. I have installed a second single instance db on node 2 (Oracle Sid = test-2) with NTFS file system for datafiles
3. Database is up and running, but I am not able to connect it from any client.
4. I am getting ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
5. Database (test2) is registered with grid LISTENER
5. TNSPING from client machine response is ok
Am I missing something here, happy to provide more info if requested.
Thanks,
PS

C:\Users\root.test_prod>lsnrctl
LSNRCTL for 64-bit Windows: Version 11.2.0.2.0 - Production on 23-FEB-2012 11:58:05
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Welcome to LSNRCTL, type "help" for information.
LSNRCTL> status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 64-bit Windows: Version 11.2.0.2.0 - Production
Start Date 18-FEB-2012 19:51:47
Uptime 4 days 16 hr. 6 min. 24 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File C:\app\11.2.0\grid\network\admin\listener.ora
Listener Log File C:\app\11.2.0\grid\log\diag\tnslsnr\IRIS11G-DB-2\listener\alert\log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\LISTENERipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.30.0.202)(PORT=1520)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.30.0.215)(PORT=1520)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+asm2", status READY, has 1 handler(s) for this service...
Service "test-11gRAC.test_prod.internal" has 1 instance(s).
Instance "test-11gr2", status READY, has 1 handler(s) for this service...
Service "test-11gRXDB.test_prod.internal" has 1 instance(s).
Instance "test-11gr2", status READY, has 1 handler(s) for this service...
Service "irisapps.test_prod.internal" has 1 instance(s).
Instance "test-11gr2", status READY, has 1 handler(s) for this service...
Service "test-2" has 1 instance(s).
Instance "test-2", status READY, has 1 handler(s) for this service...
Service "test-2XDB" has 1 instance(s).
Instance "test-2", status READY, has 1 handler(s) for this service...
The command completed successfully
LSNRCTL> service
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+asm2", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:1322 refused:0 state:ready
LOCAL SERVER
Service "test-11gRAC.test_prod.internal" has 1 instance(s).
Instance "test-11gr2", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:1829 refused:0 state:ready
LOCAL SERVER
Service "test-11gRXDB.test_prod.internal" has 1 instance(s).
Instance "test-11gr2", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: IRIS11G-DB-2, pid: 4496>
(ADDRESS=(PROTOCOL=tcp)(HOST=IRIS11G-DB-2.test_prod.internal)(PORT=57695))
Service "irisapps.test_prod.internal" has 1 instance(s).
Instance "test-11gr2", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:1829 refused:0 state:ready
LOCAL SERVER
Service "test-2" has 1 instance(s).
Instance "test-2", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
Service "test-2XDB" has 1 instance(s).
Instance "test-2", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: IRIS11G-DB-2, pid: 9340>
(ADDRESS=(PROTOCOL=tcp)(HOST=IRIS11G-DB-2.test_prod.internal)(PORT=58653))
The command completed successfully
LSNRCTL>

When we create one service as preferred on both nodes in two node RAC

How to configure listener,tnsnames.ora & listener file When we create one service as preferred on both nodes in two node RAC ... ( I don't need load balancing here but i just want to create service as preferred on both nodes)
please some one help me in this ..

Thanks alot Sebastain for your reply..
I am using 10.2.0.4 version and below tns entry is from my client side tns entry ..
M4AMPRD_TEST=
(DESCRIPTION=
(ADDRESS= (PROTOCOL=TCP) (HOST=153.88.184.228) (PORT=1521))
(ADDRESS= (PROTOCOL=TCP) (HOST=153.88.184.229) (PORT=1521))
(FAILOVER=ON)
(CONNECT_DATA=(SERVICE_NAME=M4AMPRD_TEST)
(FAILOVER_MODE=
(TYPE=SELECT)
(METHOD=BASIC)
(RETRIES=20)
(DELAY=5)
service creation: srvctl add service -d M4AMPRD -s M4AMPRD_TEST -r M4AMPRD1,M4AMPRD2
But when i connect to database usign above service from client some times its working fine and some times its failing please see below log with timings how it is behaving ..
SQL> set time on
18:39:46 SQL> CONN m4owner/iamm4amdev!@M4AMPRD_TEST
Connected.
18:39:48 SQL> CONN m4owner/iamm4amdev!@M4AMPRD_TEST
ERROR:
ORA-12545: Connect failed because target host or object does not exist
Warning: You are no longer connected to ORACLE.
18:39:52 SQL> CONN m4owner/iamm4amdev!@M4AMPRD_TEST
Connected.
18:39:53 SQL> CONN m4owner/iamm4amdev!@M4AMPRD_TEST
Connected.
18:39:55 SQL> CONN m4owner/iamm4amdev!@M4AMPRD_TEST
Connected.
18:39:57 SQL> CONN m4owner/iamm4amdev!@M4AMPRD_TEST
ERROR:
ORA-12545: Connect failed because target host or object does not exist
Warning: You are no longer connected to ORACLE.
18:39:59 SQL> CONN m4owner/iamm4amdev!@M4AMPRD_TEST
Connected.
Thanks for your help in advance
Anil Vejendla..

Single instance standby for 2-node RAC

Hi,
Oracle Version:11.2.0.1
Operating system:Linux
Here i am planing to create single instance standby for my 2-node RAC database.Here i am creating my single instance standby database on 1-node of my 2-node RAC DB.
1.) Do i need to configure any separate listener for my single instance standby in $ORACLE_HOME/network/admin in ORACLE user or need to change in Grid user login.
2.) Below is the error when i am duplicating my primary 2-Node RAC to single instance DB. And it is shutting down my auxiliary instance.
[oracle@rac1 ~]$ rman target / auxiliary sys/racdba123@stand
Recovery Manager: Release 11.2.0.1.0 - Production on Sun Aug 28 13:32:29 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: RACDB (DBID=755897741)
connected to auxiliary database: RACDB (not mounted)
RMAN> duplicate database racdba to stand
2> ;
Starting Duplicate Db at 28-AUG-11
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=6 device type=DISK
contents of Memory Script:
   sql clone "create spfile from memory";
executing Memory Script
sql statement: create spfile from memory
contents of Memory Script:
   shutdown clone immediate;
   startup clone nomount;
executing Memory Script
Oracle instance shut down
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 08/28/2011 13:33:55
RMAN-03015: error occurred in stored script Memory Script
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptorAlso find my listener services.
[oracle@rac1 ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 29-AUG-2011 10:56:24
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date                18-AUG-2011 10:35:07
Uptime                    11 days 0 hr. 21 min. 17 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/11.2.0/grid/network/admin/listener.ora
Listener Log File         /u01/app/oracle/diag/tnslsnr/rac1/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.8.123)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.8.127)(PORT=1521)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
Service "RACDB" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
Service "RACDBXDB" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
Service "stand" has 2 instance(s).
Instance "stand", status UNKNOWN, has 1 handler(s) for this service...
Instance "stand", status BLOCKED, has 1 handler(s) for this service...
Service "testdb" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
Service "testdb1" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
The command completed successfully
[oracle@rac1 ~]$ lsnrctl services
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 29-AUG-2011 10:56:35
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:0 refused:0 state:ready
         LOCAL SERVER
Service "RACDB" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:3 refused:0 state:ready
         LOCAL SERVER
Service "RACDBXDB" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
    Handler(s):
      "D000" established:0 refused:0 current:0 max:1022 state:ready
         DISPATCHER <machine: rac1.qfund.net, pid: 3975>
         (ADDRESS=(PROTOCOL=tcp)(HOST=rac1.qfund.net)(PORT=43731))
Service "stand" has 2 instance(s).
Instance "stand", status UNKNOWN, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:0 refused:0
         LOCAL SERVER
Instance "stand", status BLOCKED, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:669 refused:0 state:ready
         LOCAL SERVER
Service "testdb" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:3 refused:0 state:ready
         LOCAL SERVER
Service "testdb1" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:3 refused:0 state:ready
         LOCAL SERVER
The command completed successfully
[oracle@rac1 ~]$Tnsnames.ora file content.
RACDB =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = racdb-scan.qfund.net)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = RACDB)
#QFUNDRAC =
stand =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST= racdb-scan.qfund.net)(PORT = 1521))
    (CONNECT_DATA =
      (SERVICE_NAME = stand)
      (UR = A)
)Please help me how to solve this problem.
Thanks & Regards,
Poorna Prasad.S

Hi,
Please find the output from v$dataguard_status from primary and standby
Primary
SQL> select message from v$dataguard_status;
MESSAGE
ARC0: Archival started
ARCH: LGWR is scheduled to archive destination LOG_ARCHIVE_DEST_2 after log swit
ch
ARCH: Beginning to archive thread 1 sequence 214 (4604093-4604095)
Error 12514 received logging on to the standby
ARCH: Error 12514 Creating archive log file to 'stand'
ARCH: Completed archiving thread 1 sequence 214 (4604093-4604095)
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
MESSAGE
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
MESSAGE
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
MESSAGE
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC2: Becoming the heartbeat ARCH
ARC7: Beginning to archive thread 1 sequence 215 (4604095-4604191)
ARC7: Completed archiving thread 1 sequence 215 (4604095-4604191)
ARC5: Beginning to archive thread 1 sequence 216 (4604191-4604471)
ARC5: Completed archiving thread 1 sequence 216 (4604191-4604471)
ARCt: Archival started
MESSAGE
ARC3: Beginning to archive thread 1 sequence 217 (4604471-4605358)
ARC3: Completed archiving thread 1 sequence 217 (4604471-4605358)
LNS: Standby redo logfile selected for thread 1 sequence 217 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 217
LNS: Completed archiving log 1 thread 1 sequence 217
LNS: Standby redo logfile selected for thread 1 sequence 218 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 218
MESSAGE
LNS: Completed archiving log 2 thread 1 sequence 218
ARC4: Beginning to archive thread 1 sequence 218 (4605358-4625984)
ARC4: Completed archiving thread 1 sequence 218 (4605358-4625984)
LNS: Standby redo logfile selected for thread 1 sequence 219 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 219
LNS: Completed archiving log 1 thread 1 sequence 219
ARC5: Beginning to archive thread 1 sequence 219 (4625984-4641358)
ARC5: Completed archiving thread 1 sequence 219 (4625984-4641358)
LNS: Standby redo logfile selected for thread 1 sequence 220 for destination LOG
MESSAGE
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 220
LNS: Completed archiving log 2 thread 1 sequence 220
ARC6: Beginning to archive thread 1 sequence 220 (4641358-4644757)
ARC6: Completed archiving thread 1 sequence 220 (4641358-4644757)
LNS: Standby redo logfile selected for thread 1 sequence 221 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 221
LNS: Completed archiving log 1 thread 1 sequence 221
MESSAGE
ARC7: Beginning to archive thread 1 sequence 221 (4644757-4648306)
ARC7: Completed archiving thread 1 sequence 221 (4644757-4648306)
LNS: Standby redo logfile selected for thread 1 sequence 222 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 222
LNS: Completed archiving log 2 thread 1 sequence 222
ARC8: Beginning to archive thread 1 sequence 222 (4648306-4655287)
ARC8: Completed archiving thread 1 sequence 222 (4648306-4655287)
LNS: Standby redo logfile selected for thread 1 sequence 223 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 223
LNS: Completed archiving log 1 thread 1 sequence 223
ARC9: Beginning to archive thread 1 sequence 223 (4655287-4655307)
ARC9: Completed archiving thread 1 sequence 223 (4655287-4655307)
LNS: Standby redo logfile selected for thread 1 sequence 224 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 224
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
MESSAGE
Error 3135 for archive log file 2 to 'stand'
LNS: Failed to archive log 2 thread 1 sequence 224 (3135)
ARC3: Beginning to archive thread 1 sequence 224 (4655307-4660812)
ARC3: Completed archiving thread 1 sequence 224 (4655307-4660812)
LNS: Standby redo logfile selected for thread 1 sequence 224 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 224
LNS: Completed archiving log 2 thread 1 sequence 224
LNS: Standby redo logfile selected for thread 1 sequence 225 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 225
LNS: Completed archiving log 1 thread 1 sequence 225
ARC4: Beginning to archive thread 1 sequence 225 (4660812-4660959)
ARC4: Completed archiving thread 1 sequence 225 (4660812-4660959)
LNS: Standby redo logfile selected for thread 1 sequence 226 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 226
LNS: Completed archiving log 2 thread 1 sequence 226
ARC5: Beginning to archive thread 1 sequence 226 (4660959-4664925)
MESSAGE
LNS: Standby redo logfile selected for thread 1 sequence 227 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 227
ARC5: Completed archiving thread 1 sequence 226 (4660959-4664925)
LNS: Completed archiving log 1 thread 1 sequence 227
LGWR: Error 1089 closing archivelog file 'stand'
ARC6: Beginning to archive thread 1 sequence 227 (4664925-4668448)
ARC6: Completed archiving thread 1 sequence 227 (4664925-4668448)
ARC5: Beginning to archive thread 1 sequence 228 (4668448-4670392)
ARC5: Completed archiving thread 1 sequence 228 (4668448-4670392)
MESSAGE
LNS: Standby redo logfile selected for thread 1 sequence 228 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 228
LNS: Completed archiving log 2 thread 1 sequence 228
ARC4: Standby redo logfile selected for thread 1 sequence 227 for destination LO
G_ARCHIVE_DEST_2
LNS: Standby redo logfile selected for thread 1 sequence 229 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 229
LNS: Completed archiving log 1 thread 1 sequence 229
ARC3: Beginning to archive thread 1 sequence 229 (4670392-4670659)
ARC3: Completed archiving thread 1 sequence 229 (4670392-4670659)
LNS: Standby redo logfile selected for thread 1 sequence 230 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 230
LNS: Completed archiving log 2 thread 1 sequence 230
ARC4: Beginning to archive thread 1 sequence 230 (4670659-4670679)
ARC4: Completed archiving thread 1 sequence 230 (4670659-4670679)
MESSAGE
LNS: Standby redo logfile selected for thread 1 sequence 231 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 231
LNS: Completed archiving log 1 thread 1 sequence 231
ARC5: Beginning to archive thread 1 sequence 231 (4670679-4690371)
ARC5: Completed archiving thread 1 sequence 231 (4670679-4690371)
LNS: Standby redo logfile selected for thread 1 sequence 232 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 232
MESSAGE
LNS: Completed archiving log 2 thread 1 sequence 232
ARC6: Beginning to archive thread 1 sequence 232 (4690371-4712566)
ARC6: Completed archiving thread 1 sequence 232 (4690371-4712566)
LNS: Standby redo logfile selected for thread 1 sequence 233 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 233
LNS: Completed archiving log 1 thread 1 sequence 233
ARC7: Beginning to archive thread 1 sequence 233 (4712566-4731626)
LNS: Standby redo logfile selected for thread 1 sequence 234 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 2 thread 1 sequence 234
ARC7: Completed archiving thread 1 sequence 233 (4712566-4731626)
LNS: Completed archiving log 2 thread 1 sequence 234
ARC8: Beginning to archive thread 1 sequence 234 (4731626-4753780)
LNS: Standby redo logfile selected for thread 1 sequence 235 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 235
ARC8: Completed archiving thread 1 sequence 234 (4731626-4753780)
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
MESSAGE
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 3135 for archive log file 1 to 'stand'
LNS: Failed to archive log 1 thread 1 sequence 235 (3135)
ARC9: Beginning to archive thread 1 sequence 235 (4753780-4765626)
ARC9: Completed archiving thread 1 sequence 235 (4753780-4765626)
LNS: Standby redo logfile selected for thread 1 sequence 235 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 235
LNS: Completed archiving log 1 thread 1 sequence 235
LNS: Standby redo logfile selected for thread 1 sequence 236 for destination LOG
MESSAGE
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 236
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 3135 for archive log file 2 to 'stand'
LNS: Failed to archive log 2 thread 1 sequence 236 (3135)
ARCa: Beginning to archive thread 1 sequence 236 (4765626-4768914)
ARCa: Completed archiving thread 1 sequence 236 (4765626-4768914)
LNS: Standby redo logfile selected for thread 1 sequence 236 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 2 thread 1 sequence 236
LNS: Completed archiving log 2 thread 1 sequence 236
LNS: Standby redo logfile selected for thread 1 sequence 237 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 237
LNS: Completed archiving log 1 thread 1 sequence 237
ARCb: Beginning to archive thread 1 sequence 237 (4768914-4770603)
ARCb: Completed archiving thread 1 sequence 237 (4768914-4770603)
LNS: Standby redo logfile selected for thread 1 sequence 238 for destination LOG
MESSAGE
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 238
LNS: Completed archiving log 2 thread 1 sequence 238
ARCc: Beginning to archive thread 1 sequence 238 (4770603-4770651)
ARCc: Completed archiving thread 1 sequence 238 (4770603-4770651)
LNS: Standby redo logfile selected for thread 1 sequence 239 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 239
LNS: Completed archiving log 1 thread 1 sequence 239
MESSAGE
ARCd: Beginning to archive thread 1 sequence 239 (4770651-4773918)
ARCd: Completed archiving thread 1 sequence 239 (4770651-4773918)
LNS: Standby redo logfile selected for thread 1 sequence 240 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 240
LNS: Completed archiving log 2 thread 1 sequence 240
ARCe: Beginning to archive thread 1 sequence 240 (4773918-4773976)
ARCe: Completed archiving thread 1 sequence 240 (4773918-4773976)
LNS: Standby redo logfile selected for thread 1 sequence 241 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 241
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 3135 for archive log file 1 to 'stand'
LNS: Failed to archive log 1 thread 1 sequence 241 (3135)
ARC3: Beginning to archive thread 1 sequence 241 (4773976-4774673)
ARC3: Completed archiving thread 1 sequence 241 (4773976-4774673)
LNS: Standby redo logfile selected for thread 1 sequence 241 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 241
LNS: Completed archiving log 1 thread 1 sequence 241
LNS: Standby redo logfile selected for thread 1 sequence 242 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 242
LNS: Completed archiving log 2 thread 1 sequence 242
ARC4: Beginning to archive thread 1 sequence 242 (4774673-4776045)
ARC4: Completed archiving thread 1 sequence 242 (4774673-4776045)
LNS: Standby redo logfile selected for thread 1 sequence 243 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 243
LNS: Completed archiving log 1 thread 1 sequence 243
ARC5: Beginning to archive thread 1 sequence 243 (4776045-4776508)
ARC5: Completed archiving thread 1 sequence 243 (4776045-4776508)
LNS: Standby redo logfile selected for thread 1 sequence 244 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 244
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
MESSAGE
Error 3135 for archive log file 2 to 'stand'
LNS: Failed to archive log 2 thread 1 sequence 244 (3135)
ARC6: Beginning to archive thread 1 sequence 244 (4776508-4778741)
ARC6: Completed archiving thread 1 sequence 244 (4776508-4778741)
ARC7: Beginning to archive thread 1 sequence 245 (4778741-4778781)
ARC7: Completed archiving thread 1 sequence 245 (4778741-4778781)
ARC8: Beginning to archive thread 1 sequence 246 (4778781-4778787)
ARC8: Completed archiving thread 1 sequence 246 (4778781-4778787)
ARC9: Standby redo logfile selected for thread 1 sequence 244 for destination LO
G_ARCHIVE_DEST_2
MESSAGE
ARC3: Beginning to archive thread 1 sequence 247 (4778787-4778934)
LNS: Standby redo logfile selected for thread 1 sequence 247 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 247
ARC3: Completed archiving thread 1 sequence 247 (4778787-4778934)
LNS: Completed archiving log 1 thread 1 sequence 247
LNS: Standby redo logfile selected for thread 1 sequence 248 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 248
MESSAGE
ARC4: Beginning to archive thread 1 sequence 248 (4778934-4781018)
LNS: Completed archiving log 2 thread 1 sequence 248
ARC4: Completed archiving thread 1 sequence 248 (4778934-4781018)
LNS: Standby redo logfile selected for thread 1 sequence 249 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 249
LNS: Completed archiving log 1 thread 1 sequence 249
ARC5: Beginning to archive thread 1 sequence 249 (4781018-4781033)
ARC5: Completed archiving thread 1 sequence 249 (4781018-4781033)
LNS: Standby redo logfile selected for thread 1 sequence 250 for destination LOG
MESSAGE
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 250
233 rows selected.
SQL>Standby
SQL> select message from v$dataguard_status;
MESSAGE
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
MESSAGE
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
MESSAGE
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC2: Becoming the heartbeat ARCH
Error 1017 received logging on to the standby
FAL[client, ARC2]: Error 16191 connecting to RACDB for fetching gap sequence
MESSAGE
ARCt: Archival started
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery starting Real Time Apply
Media Recovery Log /u02/stand/archive/1_119_758280976.arc
Media Recovery Waiting for thread 2 sequence 183
RFS[1]: Assigned to RFS process 30110
RFS[1]: Identified database type as 'physical standby': Client is ARCH pid 25980
RFS[2]: Assigned to RFS process 30118
RFS[2]: Identified database type as 'physical standby': Client is ARCH pid 26008
RFS[3]: Assigned to RFS process 30124
MESSAGE
RFS[3]: Identified database type as 'physical standby': Client is ARCH pid 26029
RFS[4]: Assigned to RFS process 30130
RFS[4]: Identified database type as 'physical standby': Client is ARCH pid 26021
ARC4: Beginning to archive thread 1 sequence 244 (4776508-4778741)
ARC4: Completed archiving thread 1 sequence 244 (0-0)
RFS[5]: Assigned to RFS process 30144
RFS[5]: Identified database type as 'physical standby': Client is LGWR ASYNC pid
26128
Primary database is in MAXIMUM PERFORMANCE mode
ARC5: Beginning to archive thread 1 sequence 247 (4778787-4778934)
MESSAGE
ARC5: Completed archiving thread 1 sequence 247 (0-0)
ARC6: Beginning to archive thread 1 sequence 248 (4778934-4781018)
ARC6: Completed archiving thread 1 sequence 248 (0-0)
ARC7: Beginning to archive thread 1 sequence 249 (4781018-4781033)
ARC7: Completed archiving thread 1 sequence 249 (0-0)
58 rows selected.
SQL>also find the output for the primary alertlog file.
Tue Aug 30 10:45:41 2011
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Errors in file /u01/app/oracle/diag/rdbms/racdb/RACDB1/trace/RACDB1_nsa2_26128.trc:
ORA-03135: connection lost contact
Error 3135 for archive log file 2 to 'stand'
Errors in file /u01/app/oracle/diag/rdbms/racdb/RACDB1/trace/RACDB1_nsa2_26128.trc:
ORA-03135: connection lost contact
LNS: Failed to archive log 2 thread 1 sequence 244 (3135)
Errors in file /u01/app/oracle/diag/rdbms/racdb/RACDB1/trace/RACDB1_nsa2_26128.trc:
ORA-03135: connection lost contact
Tue Aug 30 10:50:25 2011
Thread 1 advanced to log sequence 245 (LGWR switch)
Current log# 1 seq# 245 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
Current log# 1 seq# 245 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
Tue Aug 30 10:50:25 2011
Archived Log entry 612 added for thread 1 sequence 244 ID 0x2d0e0689 dest 1:
Thread 1 cannot allocate new log, sequence 246
Checkpoint not complete
Current log# 1 seq# 245 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
Current log# 1 seq# 245 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
Thread 1 advanced to log sequence 246 (LGWR switch)
Current log# 2 seq# 246 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
Current log# 2 seq# 246 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
Tue Aug 30 10:50:27 2011
Archived Log entry 613 added for thread 1 sequence 245 ID 0x2d0e0689 dest 1:
Thread 1 cannot allocate new log, sequence 247
Checkpoint not complete
Current log# 2 seq# 246 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
Current log# 2 seq# 246 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
Thread 1 advanced to log sequence 247 (LGWR switch)
Current log# 1 seq# 247 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
Current log# 1 seq# 247 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
Tue Aug 30 10:50:30 2011
Archived Log entry 614 added for thread 1 sequence 246 ID 0x2d0e0689 dest 1:
Tue Aug 30 10:51:37 2011
ARC9: Standby redo logfile selected for thread 1 sequence 244 for destination LOG_ARCHIVE_DEST_2
Tue Aug 30 10:51:39 2011
Thread 1 advanced to log sequence 248 (LGWR switch)
Current log# 2 seq# 248 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
Current log# 2 seq# 248 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
Tue Aug 30 10:51:39 2011
Archived Log entry 620 added for thread 1 sequence 247 ID 0x2d0e0689 dest 1:
Tue Aug 30 10:51:39 2011
LNS: Standby redo logfile selected for thread 1 sequence 247 for destination LOG_ARCHIVE_DEST_2
LNS: Standby redo logfile selected for thread 1 sequence 248 for destination LOG_ARCHIVE_DEST_2
Tue Aug 30 11:08:27 2011
Thread 1 advanced to log sequence 249 (LGWR switch)
Current log# 1 seq# 249 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
Current log# 1 seq# 249 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
Tue Aug 30 11:08:27 2011
Archived Log entry 622 added for thread 1 sequence 248 ID 0x2d0e0689 dest 1:
Tue Aug 30 11:08:27 2011
LNS: Standby redo logfile selected for thread 1 sequence 249 for destination LOG_ARCHIVE_DEST_2
Thread 1 cannot allocate new log, sequence 250
Checkpoint not complete
Current log# 1 seq# 249 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
Current log# 1 seq# 249 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
Thread 1 advanced to log sequence 250 (LGWR switch)
Current log# 2 seq# 250 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
Current log# 2 seq# 250 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
Tue Aug 30 11:08:31 2011
Archived Log entry 624 added for thread 1 sequence 249 ID 0x2d0e0689 dest 1:
LNS: Standby redo logfile selected for thread 1 sequence 250 for destination LOG_ARCHIVE_DEST_2Thanks & Regards,
Poorna Prasad.S

ORA-01652 unable to extend temp segment in 11gR2 with ASM and 2 node RAC

Hi ,
I have a 11.2.0.1 system with 2 node RAC and ASM . We are hitting ORA-01652 very frequently
and I can see space is available in TEMP .
CREATE TEMPORARY TABLESPACE "TEMP" TEMPFILE
SIZE 21474836480,
SIZE 137437904896
AUTOEXTEND ON NEXT 655360 MAXSIZE 131071M ( Will the next size ignored as the extent size is 1MB ?)
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576
And during the failure
SELECT tablespace_name,
total_blocks,
used_blocks,
free_blocks,
total_blocks*32768/1024/1024 as total_MB,
used_blocks*32768/1024/1024 as used_MB,
free_blocks*32768/1024/1024 as free_MB
FROM gv$sort_segment;
TABLESPACE_NAME TOTAL_BLOCKS USED_BLOCKS FREE_BLOCKS TOTAL_MB USED_MB FREE_MB
TEMP 4849568 2385728 2463840 151549 74554 76995
TEMP 0 0 0 0 0 0
Also when I checked from v$sort_usage I see only two session consuming space
SQL> SELECT b.tablespace tablespace,
2 -- b.segfile#,
3 -- b.segblk#,
4 b.blocks,
5 b.blocks * (SELECT value FROM v$parameter WHERE name = 'db_block_size')/1024/1024 bytes,
6 a.sid,
7 a.username username,
8 a.osuser osuser,
9 a.inst_id,a.sid,a.serial#,a.module
10 FROM gv$session a, gv$sort_usage b
11 WHERE a.saddr = b.session_addr and
12 b.blocks != 16 and
13 a.inst_id = b.inst_id
14 ORDER BY b.tablespace, b.blocks, bytes desc;
BLOCKS BYTES SID USERNAME OSUSER INST_ID SID SERIAL# MODULE
1,192,864 37277 381 CN obiqb 2 381 860 nqsserver@icmqapp01cdp (TNS V1
1,192,864 37277 3952 CN obiqb 2 3952 1374 nqsserver@icmqapp01cdp (TNS V1
2,385,728 74554 (mb)
Wat is causing the 1652 ?

877394 wrote:
Thanks Srini,
But I did try all that notes with no luck .
I have a temporary tablespace with 150gb (130+20) datafiles .
TABLESPACE_NAME FILE_NAME (BYTES/1024/1024)
TEMP +DATA_01/tempfile/temp.314.743964            131071
TEMP +DATA_01/tempfile/temp.312.757303             20480
and the DDL is
CREATE TEMPORARY TABLESPACE "TEMP" TEMPFILE
SIZE 21474836480,
SIZE 137437904896
AUTOEXTEND ON NEXT 655360 MAXSIZE 131071M
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576
And on querying v$sort_usage
SQL> SELECT b.tablespace tablespace,
2 -- b.segfile#,
3 -- b.segblk#,
4 b.blocks,
5 b.blocks * (SELECT value FROM v$parameter WHERE name = 'db_block_size')/1024/1024 bytes,
6 a.sid,
7 a.username username,
8 a.osuser osuser,
9 a.inst_id,a.sid,a.serial#,a.module
10 FROM gv$session a, gv$sort_usage b
11 WHERE a.saddr = b.session_addr and
12 b.blocks != 16 and
13 a.inst_id = b.inst_id
14 ORDER BY b.tablespace, b.blocks, bytes desc;
TABLESPACE BLOCKS BYTES SID OSUSER INST_ID SID SERIAL# MODULE
TEMP 63,328 1,979 3952 CN 2 3952 1374
TEMP 84,384 2,637 381 CN 2 381 860
TEMP 433,184 13,537 381 CN 2 381 860
TEMP 1,117,728 34,929 3952 CN 2 3952 1374
sum 1,698,624 53,082 (mb)
So the space utilization was less than 150gb and on querying v$sort_Segment
SQL> SELECT tablespace_name,
total_blocks,
used_blocks,
free_blocks,
total_blocks*32768/1024/1024 as total_MB,
used_blocks*32768/1024/1024 as used_MB,
free_blocks*32768/1024/1024 as free_MB
FROM gv$sort_segment;
TABLESPACE_NAME TOTAL_BLOCKS USED_BLOCKS FREE_BLOCKS TOTAL_MB USED_MB FREE_MB inst
TEMP 4849568 2311104 2538464 151549 72222 79327 2
TEMP 0 0 0 0 0 0 1
why for inst 1 it is showing 0 (which means no sort is happening in instance 1)
But still we got the error
ORA-1652: unable to extend temp segment by 32 in tablespace TEMP
01652, 00000, "unable to extend temp segment by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
//          a temporary segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
//          files to the tablespace indicated.

How to install DG4DRA in grid infrastructure env 2 node rac

Hi All,
is there any MOS note regarding installation of Oracle Transparent Gateways for DRDA in a grid infrastructure environment (2 node rac)
other than the note below?
How to Set up DG4MSQL, DG4DRDA, DG4IFMX, DG4SYBS or DG4Tera in a RAC Environment (Doc ID 421981.1)
I mean, it seems that the note does note provide specific instructions for rac env in GI (scan listener, default listener configuration, tns connect string to drda via scan, etc...).
Thank you,
Regards.
Domenico.

Grid Infrastructure automatically uses Oracle Restart as default if you're installing Standalone. You can turn this off using crsctl ('disable has', I believe).
According to the inference in the install docs (http://download.oracle.com/docs/cd/E11882_01/install.112/e16763/oraclerestart.htm#CIHCBGCC), you can install 11gR2 without Grid Infrastructure, but you lose ASM and Restart.

How many Scan Listeners, we have to configure for 5 Node RAC?

Dear Professionals,
How many scan Listeners we need to configure for 5 Node RAC? Oracle will not allow us to create More than 3 scan's? What If i have one scan Listener per each for 1st 3 node's? what about remaining two Node's? How application user will connect to 4 or 5 Node? Can you please explain..? Forgive me, If am totally wrong?
Thanks
Sagar

Each of the 5 instances will register itself with the scan listener (using the instance parameter remote_listener). Thus, the scan listener is "aware" of the database instances on the other two nodes where it is not running. It can still redirect incoming connections to the local listeners on these nodes (registered as local_listener).
Hemant K Chitale

Removed node history returns after an unspecified interval

Hi Folks,
I'm using the simpleChatModel::clear() to remove the history node as OWNER. Everything looks fine from a web base client. I check it in the AFCS Developer console and all the history nodes are gone. Everything is working fine. I reconnect to the chat no problem, I check in the AFCS Dev console, the history is as I would expect. persistItems is checked as is allowPrivateMessages.
I come back some time afterwards and all the history nodes have returned.
As before I have a working chat deployed for a customer and it's been reasonably stable. I've gone back to the simple chat as an install as a prototype and now I'm having this problem.
Any suggestions on what I'm doing wrong?
--Doug

Hi DaddyDog,
I have some good news and some bad news.
Good news is that I could reproduce your issue many times trying from this morning from a network outside Adobe(from home). I couldn't reproduced it within Adobe Network last time. But I can now reproduce the issue many times. Moreover, I could reproduce this issue both in new rooms (created after april or ones with new domain) and also in old rooms. So, its independant of room creation timings.
Bad news is that, even after scratching from morning, I havent been able to generate a clean fix, primarily because the clean fix isn't on the client SDK. This bug happens in my opinion as a race condition when you clear chat history, the nodes are deleted and recreated immediately inside model.clear() function. But all the items may not have been deleted on the server by the time we recreate the nodes.So, this could be mostly a bug on the server side.
But I actually could create a hack with the model class and I am attaching the file for your reference. Try this file and let me know if you can still reproduce, hopefully not . The file is of SImpleChatModel.as in player 10. If you are using player 9, let me know I can provide that file for player 9. You can diff with your SimpleChatModel.as in player 10 source and can see the difference and the hack in case you are interested. I can't guarantee that it will definitely work but at least it can let you going( you need to link to the source files and not use player 10 swc in your app).
Meanwhile, we have started discussions internally on this issue and we should be able to come up with a cleaner fix in future release. I will keep you posted on that. In the meanwhile, go ahead and give it a try and let me know.
Thanks again for finding. Issues like this are almost impossible to find without active help from user community.
Regards
Hironmay Basu

Failover takes 14 minutes on 2 node rac cluster installed on virtualbox

i have 2 node rac 10gr2 installation without asm on virtualbox for learning purposes, the storage is kept on rac1 node and shared via nfs,
i connected a third machine to be used as client by creating a service
but when i shutdown the rac2 node to cause a failover, it takes almost 14-15 minutes to reconnect to the rac1 node
even though the vip of rac2 is taken up by rac1 in not more than 30 seconds
so i checked the listener log for rac1 node
the correct service update shows up after 14 minutes every time i try
tried a lot of googling but found nothing
This is the service
RAC =
(DESCRIPTION =
    (LOAD_BALANCE = ON)
    (FAILOVER = ON)
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip.localdomain)(PORT = 1521))
      (ADDRESS = (PROTOCOL = TCP)(HOST = rac2-vip.localdomain)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = RAC.WORLD)
      (FAILOVER_MODE =
        (TYPE = SELECT)
        (METHOD = BASIC)
        (RETRIES = 180)
        (DELAY = 1)
18-DEC-2013 18:34:48 * node_down * rac2 * 0
18-DEC-2013 18:34:48 * service_down * RAC2 * 0
18-DEC-2013 18:34:48 * service_update * RAC1 * 0
18-DEC-2013 18:34:48 * service_update * RAC1 * 0
18-DEC-2013 18:35:48 * service_update * RAC1 * 0
18-DEC-2013 18:35:48 * service_update * RAC1 * 0
18-DEC-2013 18:36:48 * service_update * RAC1 * 0
18-DEC-2013 18:36:48 * service_update * RAC1 * 0
18-DEC-2013 18:37:48 * service_update * RAC1 * 0
18-DEC-2013 18:37:48 * service_update * RAC1 * 0
18-DEC-2013 18:38:48 * service_update * RAC1 * 0
18-DEC-2013 18:38:48 * service_update * RAC1 * 0
18-DEC-2013 18:39:45 * service_update * RAC1 * 0
18-DEC-2013 18:39:45 * service_update * RAC1 * 0
18-DEC-2013 18:40:12 * service_update * RAC1 * 0
18-DEC-2013 18:40:12 * service_update * RAC1 * 0
18-DEC-2013 18:40:48 * service_update * RAC1 * 0
18-DEC-2013 18:40:48 * service_update * RAC1 * 0
18-DEC-2013 18:41:01 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=rac1.localdomain)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER_RAC1)(VERSION=169869568)) * status * 0
18-DEC-2013 18:41:49 * service_update * RAC1 * 0
18-DEC-2013 18:41:49 * service_update * RAC1 * 0
18-DEC-2013 18:42:31 * service_update * RAC1 * 0
18-DEC-2013 18:42:31 * service_update * RAC1 * 0
18-DEC-2013 18:43:49 * service_update * RAC1 * 0
18-DEC-2013 18:43:49 * service_update * RAC1 * 0
18-DEC-2013 18:44:49 * service_update * RAC1 * 0
18-DEC-2013 18:44:49 * service_update * RAC1 * 0
18-DEC-2013 18:45:40 * service_update * RAC1 * 0
18-DEC-2013 18:45:40 * service_update * RAC1 * 0
18-DEC-2013 18:45:49 * service_update * RAC1 * 0
18-DEC-2013 18:45:49 * service_update * RAC1 * 0
18-DEC-2013 18:46:49 * service_update * RAC1 * 0
18-DEC-2013 18:46:49 * service_update * RAC1 * 0
18-DEC-2013 18:47:49 * service_update * RAC1 * 0
18-DEC-2013 18:47:49 * service_update * RAC1 * 0
18-DEC-2013 18:47:54 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=RAC.WORLD)(FAILOVER_MODE=(TYPE=SELECT)(METHOD=BASIC)(RETRIES=180)(DELAY=1))(CID=(PROGRAM=sqlplus)(HOST=client.localdomain)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.103)(PORT=32774)) * establish * RAC.WORLD * 0
18-DEC-2013 18:47:55 * service_update * RAC1 * 0
18-DEC-2013 18:47:55 * service_update * RAC1 * 0

These entries came by when the failover state resumed
[19-DEC-2013 15:17:05:546] ntt2err: entry
[19-DEC-2013 15:17:05:547] ntt2err: soc 9 error - operation=5, ntresnt[0]=530, ntresnt[1]=113, ntresnt[2]=0
[19-DEC-2013 15:17:05:547] ntt2err: exit
[19-DEC-2013 15:17:05:547] nttrd: exit
[19-DEC-2013 15:17:05:547] nsprecv: error exit
[19-DEC-2013 15:17:05:547] nserror: entry
[19-DEC-2013 15:17:05:547] nserror: nsres: id=0, op=68, ns=12570, ns2=12560; nt[0]=530, nt[1]=113, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
[19-DEC-2013 15:17:05:547] nsrdr: error exit
[19-DEC-2013 15:17:05:547] nsdo: nsctxrnk=0
[19-DEC-2013 15:17:05:547] nsdo: error exit
[19-DEC-2013 15:17:05:547] nioqrc: recv: packet reader error -> translated to IFCR_EOF
[19-DEC-2013 15:17:05:547] nioqer: entry
[19-DEC-2013 15:17:05:547] nioqer: incoming err = 12151
[19-DEC-2013 15:17:05:547] nioqce: entry
[19-DEC-2013 15:17:05:547] nioqce: exit
[19-DEC-2013 15:17:05:547] nioqer: returning err = 3113
[19-DEC-2013 15:17:05:547] nioqer: exit
[19-DEC-2013 15:17:05:547] nioqrc: exit
[19-DEC-2013 15:17:05:547] nioqrs: entry
[19-DEC-2013 15:17:05:547] nioqrs: state = normal (0)
[19-DEC-2013 15:17:05:547] nioqrs: reset called, but connection in EOF state.
[19-DEC-2013 15:17:05:547] nioqrs: exit
[19-DEC-2013 15:17:05:547] nioqds: entry
[19-DEC-2013 15:17:05:547] nioqds: disconnecting...
[19-DEC-2013 15:17:05:547] nsclose: entry
[19-DEC-2013 15:17:05:547] nstimarmed: entry
[19-DEC-2013 15:17:05:547] nstimarmed: no timer allocated
[19-DEC-2013 15:17:05:547] nstimarmed: normal exit
[19-DEC-2013 15:17:05:547] nttctl: entry
[19-DEC-2013 15:17:05:547] nttctl: entry
[19-DEC-2013 15:17:05:547] nsdo: entry
[19-DEC-2013 15:17:05:547] nsdo: cid=0, opcode=66, *bl=0, *what=0, uflgs=0x0, cflgs=0x2
[19-DEC-2013 15:17:05:548] nsdo: rank=64, nsctxrnk=0
[19-DEC-2013 15:17:05:548] nsdo: nsctx: state=1, flg=0x1004009, mvd=0
[19-DEC-2013 15:17:05:548] nsdo: entry
there are a lot more entries
but can't really paste all of them here
still have no clue what so ever regarding what is actually happening

Install mulutple RAC databases on 2-node RAC cluster

I am installing 5 RAC databases on a 2-node RAC cluster. I have setup SCAN using 3 IP addresses.
Do I have to use SCAN listener for all databases?
When installing the 3 database, I get ORA-12537: TNS connection closed error.
ENV: 11gR2 2-node RH5.x
Thanks!

I have setup SCAN using 3 IP addresses.
Do I have to use SCAN listener for all databases?These 3 scan ip will work for youe all database running under this cluster setup.
you may also use VIP to make connection like 10g.
I get ORA-12537: TNS connection closed error.Appear some connectivity/configuration isue,please try MOS doc contain detail on this.
How to Troubleshoot Connectivity Issue with 11gR2 SCAN Name [ID 975457.1]

Multi-table INSERT with PARALLEL hint on 2 node RAC

Multi-table INSERT statement with parallelism set to 5, works fine and spawns multiple parallel
servers to execute. Its just that it sticks on to only one instance of a 2 node RAC. The code I
used is what is given below.
create table t1 ( x int );
create table t2 ( x int );
insert /*+ APPEND parallel(t1,5) parallel (t2,5) */
when (dummy='X') then into t1(x) values (y)
when (dummy='Y') then into t2(x) values (y)
select dummy, 1 y from dual;
I can see multiple sessions using the below query, but on only one instance only. This happens not
only for the above statement but also for a statement where real time table(as in table with more
than 20 million records) are used.
select p.server_name,ps.sid,ps.qcsid,ps.inst_id,ps.qcinst_id,degree,req_degree,
sql.sql_text
from Gv$px_process p, Gv$sql sql, Gv$session s , gv$px_session ps
WHERE p.sid = s.sid
and p.serial# = s.serial#
and p.sid = ps.sid
and p.serial# = ps.serial#
and s.sql_address = sql.address
and s.sql_hash_value = sql.hash_value
and qcsid=945
Won't parallel servers be spawned across instances for multi-table insert with parallelism on RAC?
Thanks,
Mahesh

Please take a look at these 2 articles below
http://christianbilien.wordpress.com/2007/09/12/strategies-for-rac-inter-instance-parallelized-queries-part-12/
http://christianbilien.wordpress.com/2007/09/14/strategies-for-parallelized-queries-across-rac-instances-part-22/
thanks
http://swervedba.wordpress.com

Multiple copies of same database on a 2 node RAC server - How to merge ?

I currently have multiple copies of the same database running on a 2 node Rac system. I am looking for a way to combine them into 1 large database but keeping the data separate.
The databases are copies of production for testing, development and a yearly "historical" databases .
All the databases are created from production, and generally have the same schema's , tables, procedures, etc however may be different versions and need to be.
Is There a way to use one large database and logically split all the different versions of the same objects into their own space in one database ? The structure cannot change as the database is for a 3rd party's Forms application the relies on the objects not changing names etc.
Ideally I am looking for a solution that will allow the forms application to connect to "test" and "historical" copies of our production database separately in the same database container.
Thanks for any direction.

I currently have multiple copies of the same database running on a 2 node Rac system. I am looking for a way to combine them into 1 large database but keeping the data separate.
The databases are copies of production for testing, development and a yearly "historical" databases .
All the databases are created from production, and generally have the same schema's , tables, procedures, etc however may be different versions and need to be.
Is There a way to use one large database and logically split all the different versions of the same objects into their own space in one database ? The structure cannot change as the database is for a 3rd party's Forms application the relies on the objects not changing names etc.
Ideally I am looking for a solution that will allow the forms application to connect to "test" and "historical" copies of our production database separately in the same database container.
Thanks for any direction.

Multiple databases/instances on 4-node RAC Cluster including Physical Stand

OS: Windows 2003 Server R2 X64
DB: 10.2.0.4
Virtualization: NONE
Node Configuration: x64 architecture - 4-Socket Quad-Core (16 CPUs)
Node Memory: 128GB RAM
We are planning the following on the above-mentioned 4-node RAC cluster:
Node 1: DB1 with instanceDB11 (Active-Active: Load-balancing & Failover)
Node 2: DB1 with instanceDB12 (Active-Active: Load-balancing & Failover)
Node 3: DB1 with instanceDB13 (Active-Passive: Failover only) + DB2 with instanceDB21 (Active-Active: Load-balancing & Failover) + DB3 with instanceDB31 (Active-Active: Load-balancing & Failover) + DB4 with instance41 (Active-Active: Load-balancing & Failover)
Node 4: DB1 with instanceDB14 (Active-Passive: Failover only) + DB2 with instanceDB22 (Active-Active: Load-balancing & Failover) + DB3 with instanceDB32 (Active-Active: Load-balancing & Failover) + DB4 with instance42 (Active-Active: Load-balancing & Failover)
Note: DB1 will be the physical primary PROD OLTP database and will be open in READ-WRITE mode 24x7x365.
Note: DB2 will be a Physical Standby of DB1 and will be open in Read-Only mode for reporting purposes during the day-time, except for 3 hours at night when it will apply the logs.
Note: DB3 will be a Physical Standby of a remote database DB4 (not part of this cluster) and will be mounted in Managed Recovery mode for automatic failover/switchover purposes.
Note: DB4 will be the physical primary Data Warehouse DB.
Note: Going to 11g is NOT an option.
Note: Data Guard broker will be used across the board.
Please answer/advise of the following:
1. Is the above configuration supported and why so? If not, what are the alternatives?
2. Is the above configuration recommended and why so? If not, what are the recommended alternatives?

Hi,
As far as i understand, there's nothing wrong in configuration except you need to consider below points while implementing final design.
1. No of CPU on each servers
2. Memory on each servers
3. If you've RAC physical standby then apply(MRP0) will run on only one instance.
4. Since you are configuring physical standby for on 3rd and 4th nodes of DB1 4 node cluster where DB13 and DB14 instances are used only for failver, if you've a disaster at data center or power failure in entire data center, you are losing both primary and secondary with an assumption that your primary and physical standby reside in same data center so it may not be highly available architecture. If you are going to use extended RAC for this configuration then it makes sense where Node 1 and Node 2 will reside in Datacenter A and Node 3 ,4 will reside in Datacenter B.
Thanks,
Keyur

How to create 11.2.0.2 physical standby database from 2 node RAC (11.2.0.2)

Hi,
Can any one please help me How to manually create 11.2.0.2 standalone physical standby database from 2 node RAC (11.2.0.2) database which is running in RHEL5 and ASM plugged in.
DB : 11.2.0.2
OS : RHEL5
RMAN duplicate is causing problem with network and we decided to go for manual creation of the same.
Thanks in Advance..

Hi;
Can any one please help me How to manually create 11.2.0.2 standalone physical standby database from 2 node RAC (11.2.0.2) database which is running in RHEL5 and ASM plugged in.
DB : 11.2.0.2
OS : RHEL5I had similar issue, what i did
1. Used source oracle_home on standby server
2. Created new asm instance and use same naming
3. I took RMAN full backup on source and move it to target
4. I edit initora file remove RAC setting and restore db(also edited listener file)
Regard
Helios

TNS redirect on 2-node RAC returns unqualified hostname, should be FQDN

Similar Messages

Maybe you are looking for