Problem with DataGuard

Hello.
Please help me with problem. I install OEM with DataGuard on one computer and install database and agent on other. When I install this programs I can manage from OEM other computer on what install database. After I try create standby database for my database from OEM but it answered me "Cannot determine primary host architecture". What I need do for fix this problem? I can create standby database for base on one computer but I can't create standby for database on other computer.

Can you be more specific ?
-- Where is the Primary DB installed on ? Which version of DB ? What version of agent is installed on it ?
-- Where is the OEM Grid installed on ? Version ?
-- Where are you trying to create the Standby DB on ? If it is on a different server what version of the agent is installed on it ?
-- Have you enabled the parameters for Data Broker ?

Similar Messages

Problem with dataguard on 10g peace of !"·$%&/

Hello everyone
I have problems with the dataguard, when i switchover to physical standby the error ora-16775 the dmgrl log says:
0 2 0 ORA-16775 Error: the target standby database has some redo log(s) missing. Cannot proceed with the switchover operation
I have made i think all the solutions around here to send or activate the redo log transport, this happend to me because disable the log_archive_dest_state on physical standby, so y make a cold backup of the primary database and set this to standby with the commands:
SQL> STARTUP NOMOUNT;
SQL> ALTER DATABASE MOUNT STANDBY DATABASE;
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
I attach the orcla.ora and orclb.ora to this question:
ORCLA: (primary)
orcla.__db_cache_size=868220928
orcla.__java_pool_size=16777216
orcla.__large_pool_size=16777216
orcla.__shared_pool_size=163577856
orcla.__streams_pool_size=0
*.archive_lag_target=0
*.audit_file_dest='c:\oracle\product\10.2.0/admin/orcla/adump'
*.background_dump_dest='c:\oracle\product\10.2.0/admin/orcla/bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCLA\CONTROL01.CTL','C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCLA\CONTROL02.CTL','C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCLA\CONTROL03.CTL'#Restore Controlfile
*.core_dump_dest='c:\oracle\product\10.2.0/admin/orcla/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='ORCLA'
*.db_recovery_file_dest='c:\oracle\product\10.2.0/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.DB_UNIQUE_NAME='ORCLA'
*.dg_broker_start=TRUE
*.dispatchers='(PROTOCOL=TCP) (SERVICE=orclaXDB)'
*.fal_client='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-001)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLA_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))'
*.fal_server='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(SERVER=dedicated)))'
*.instance_name='ORCLSID'
*.job_queue_processes=10
*.log_archive_config='dg_config=(ORCLB)'
*.log_archive_dest_1='LOCATION=D:\oradata\archivelogs\orcla VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ORCLA'
orcla.log_archive_dest_1='location="D:\oradata\archivelogs\orcla"','valid_for=(ONLINE_LOGFILE,ALL_ROLES)'
*.log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))"',' LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="ORCLB" register net_timeout=180 valid_for=(online_logfile,primary_role)'
*.log_archive_dest_state_1='ENABLE'
orcla.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_format='DBSID_%t_%s_%r.arc'
orcla.log_archive_format='DBSID_%t_%s_%r.arc'
*.log_archive_max_processes=2
*.log_archive_min_succeed_dest=1
orcla.log_archive_trace=0
*.log_checkpoint_interval=10000
*.log_checkpoint_timeout=1800
*.open_cursors=3000
*.optimizer_mode='RULE'
*.pga_aggregate_target=16777216
*.processes=400
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_max_size=1073741824
*.sga_target=1073741824
orcla.standby_archive_dest=''
*.standby_file_management='auto'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='c:\oracle\product\10.2.0/admin/orcla/udump'
ORCLB: (standby)
orclb.__db_cache_size=868220928
orclb.__java_pool_size=16777216
orclb.__large_pool_size=16777216
orclb.__shared_pool_size=163577856
orclb.__streams_pool_size=0
*.aq_tm_processes=0
*.archive_lag_target=0
*.audit_file_dest='c:\oracle\product\10.2.0/admin/orclb/adump'
*.background_dump_dest='c:\oracle\product\10.2.0/admin/orclb/bdump'
*.compatible='10.2.0.1.0'
*.control_files='c:\oracle\product\10.2.0/oradata/orclb/\stand.ctl'
*.core_dump_dest='c:\oracle\product\10.2.0/admin/orclb/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='ORCLA'
*.db_recovery_file_dest='c:\oracle\product\10.2.0/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.DB_UNIQUE_NAME='ORCLB'
*.dg_broker_start=TRUE
*.dispatchers='(PROTOCOL=TCP) (SERVICE=orclaXDB)'
*.fal_client='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))'
*.fal_server='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-001)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLA_XPT)(SERVER=dedicated)))'
*.instance_name='ORCLSID'
*.job_queue_processes=10
*.log_archive_config='dg_config=(ORCLA)'
*.log_archive_dest_1='LOCATION=C:\oracle\product\10.2.0\oradata\orclb VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ORCLB'
orclb.log_archive_dest_1='location="C:\oracle\product\10.2.0\oradata\orclb"','valid_for=(ALL_LOGFILES,ALL_ROLES)'
*.log_archive_dest_2=''
orclb.log_archive_dest_2='location="D:\oradata\archivelogs\orclb"','valid_for=(STANDBY_LOGFILE,STANDBY_ROLE)'
*.log_archive_dest_state_1='ENABLE'
orclb.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
orclb.log_archive_dest_state_2='ENABLE'
*.log_archive_format='DBSID_%t_%s_%r.arc'
orclb.log_archive_format='DBSID_%t_%s_%r.arc'
*.log_archive_max_processes=2
*.log_archive_min_succeed_dest=1
*.log_archive_trace=0
orclb.log_archive_trace=0
*.log_checkpoint_interval=10000
*.log_checkpoint_timeout=1800
*.open_cursors=3000
*.optimizer_mode='RULE'
*.pga_aggregate_target=16777216
*.processes=400
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_max_size=1073741824
*.sga_target=1073741824
orclb.standby_archive_dest='D:\oradata\archivelogs\orclb'
*.standby_file_management='auto'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='c:\oracle\product\10.2.0/admin/orclb/udump'
DGMGRL (primary)
DG 2009-11-11-22:05:17 0 2 702684180 DMON: CTL_ENABLE of ORCLB
DG 2009-11-11-22:05:17 0 2 702684180 requires reset of LOG XPT Engine
DG 2009-11-11-22:05:17 0 2 702684180 on Site ORCLA
DG 2009-11-11-22:05:17 0 2 0 Reset Log Transport Resource: SetState ONLINE, phase BUILD-UP, External Cond ENABLE
DG 2009-11-11-22:05:17 0 2 0 Set log transport destination: SetState ONLINE, phase BUILD-UP, External Cond ENABLE
DG 2009-11-11-22:05:17 0 2 0 Executing SQL [alter system set log_archive_dest_2 = 'service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))"', '   LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="ORCLB" register net_timeout=180 valid_for=(online_logfile,primary_role)']
DG 2009-11-11-22:05:17 0 2 0 SQL [alter system set log_archive_dest_2 = 'service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))"', '   LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="ORCLB" register net_timeout=180 valid_for=(online_logfile,primary_role)'] Executed successfully
DG 2009-11-11-22:05:17 0 2 0 Executing SQL [alter system set log_archive_dest_state_2 = 'ENABLE']
DG 2009-11-11-22:05:17 0 2 0 SQL [alter system set log_archive_dest_state_2 = 'ENABLE'] Executed successfully
DG 2009-11-11-22:05:17 0 2 0 Executing SQL [ALTER SYSTEM SWITCH ALL LOGFILE]
DG 2009-11-11-22:05:22 0 2 0 SQL [ALTER SYSTEM SWITCH ALL LOGFILE] Executed successfully
DG 2009-11-11-22:05:22 0 2 0 DMON: site 01001000, instance 00000001 queuing healthcheck lock request
DG 2009-11-11-22:05:22 0 2 0 DMON: Releasing healthcheck master lock
DG 2009-11-11-22:05:22 0 2 0 DMON: Health check master lock conversion successful
DG 2009-11-11-22:05:22 0 2 0 DMON: a process acquired the healthcheck master lock
DG 2009-11-11-22:05:22 0 2 702684180 DMON: status from rfi_post_instances() for ENABLE = ORA-00000
DG 2009-11-11-22:05:22 0 2 0 INSV: Received message for inter-instance publication
DG 2009-11-11-22:05:22 0 2 702684180 DMON: ENABLE Complete, Object ORCLB
DG 2009-11-11-22:05:22 0 2 0 req_id 2.1.702684180, opcode CTL_ENABLE, phase END, flags 5
DG 2009-11-11-22:05:22 0 2 702684180      enabled in State STANDBY
DG 2009-11-11-22:05:22 0 2 702684180 rfm_inst_phase_dispatch 16 END phase processing
DG 2009-11-11-22:05:22 0 2 0 INSV: All instances have replied for message
DG 2009-11-11-22:05:22 0 2 0 req_id 2.1.702684180, opcode CTL_ENABLE, phase END
DG 2009-11-11-22:05:22 0 2 702684180 DMON: CTL_ENABLE operation completed
DG 2009-11-11-22:05:22 0 2 702684180 DMON: Entered rfm_release_chief_lock for CTL_ENABLE
DGMGRL (standby)
SCOPE=SPFILE sid='orclb']
DG 2009-11-11-22:04:06 0 2 0 SQL [ALTER SYSTEM SET log_archive_format='DBSID_%t_%s_%r.arc' SCOPE=SPFILE sid='orclb'] Executed successfully
DG 2009-11-11-22:04:07 0 2 0 Setting init.ora parameter with SQL [ALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 Executing SQL [ALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 SQL [ALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH sid='*'] Executed successfully
DG 2009-11-11-22:04:07 0 2 0 Setting init.ora parameter with SQL [ALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 Executing SQL [ALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 SQL [ALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH sid='*'] Executed successfully
DG 2009-11-11-22:04:07 0 2 0 Setting init.ora parameter with SQL [ALTER SYSTEM SET log_archive_max_processes=2 SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 Executing SQL [ALTER SYSTEM SET log_archive_max_processes=2 SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 SQL [ALTER SYSTEM SET log_archive_max_processes=2 SCOPE=BOTH sid='*'] Executed successfully
DG 2009-11-11-22:04:07 0 2 0 Setting init.ora parameter with SQL [ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 Executing SQL [ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 SQL [ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH sid='*'] Executed successfully
DG 2009-11-11-22:04:07 0 2 0 Executing SQL [ALTER SYSTEM SET fal_server='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-001)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLA_XPT)(SERVER=dedicated)))']
DG 2009-11-11-22:04:07 0 2 0 SQL [ALTER SYSTEM SET fal_server='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-001)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLA_XPT)(SERVER=dedicated)))'] Executed successfully
DG 2009-11-11-22:04:07 0 2 0 Executing SQL [ALTER SYSTEM SET fal_client='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))']
DG 2009-11-11-22:04:07 0 2 0 SQL [ALTER SYSTEM SET fal_client='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))'] Executed successfully
DG 2009-11-11-22:04:07 0 2 0 Database Resource SetState succeeded
DG 2009-11-11-22:04:07 0 2 0 RSM 0 received SETSTATE request: rid=0x02031000, sid=1, phid=2, econd=7, sitehndl=0x7fffffff
DG 2009-11-11-22:04:07 0 2 0 Physical Apply Resource: SetState ONLINE, phase BUILD-UP, External Cond ENABLE
DG 2009-11-11-22:04:07 0 2 0 Executing SQL [ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL]
DG 2009-11-11-22:04:13 0 2 0 SQL [ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL] Executed successfully
DG 2009-11-11-22:05:11 0 2 0 Executing SQL [ALTER DATABASE RECOVER MANAGED STANDBY DATABASE THROUGH ALL SWITCHOVER DISCONNECT USING CURRENT LOGFILE]
DG 2009-11-11-22:05:17 0 2 0 SQL [ALTER DATABASE RECOVER MANAGED STANDBY DATABASE THROUGH ALL SWITCHOVER DISCONNECT USING CURRENT LOGFILE] Executed successfully
DG 2009-11-11-22:05:17 0 2 0 INSV: All instances have replied for message
DG 2009-11-11-22:05:17 0 2 0 req_id 2.1.702684180, opcode CTL_ENABLE, phase BUILDUP
DG 2009-11-11-22:05:17 0 2 702684180 DMON: Entered rfm_release_chief_lock for CTL_ENABLE
DG 2009-11-11-22:05:22 0 2 702684180 DMON: Entered rfm_get_chief_lock() for CTL_ENABLE, reason 0
DG 2009-11-11-22:05:22 0 2 702684180 DMON: chief lock convert for write op CTL_ENABLE
DG 2009-11-11-22:05:22 0 2 702684180 DMON: chief lock convert for enable
DG 2009-11-11-22:05:22 0 2 702684180 DMON: CLSR being notified to enable services and startup standby instances as appropriate during ENABLE.
DG 2009-11-11-22:05:22 0 2 702684180 DMON: status from rfi_post_instances() for ENABLE = ORA-00000
DG 2009-11-11-22:05:22 0 2 0 INSV: Received message for inter-instance publication
DG 2009-11-11-22:05:22 0 2 0 req_id 2.1.702684180, opcode CTL_ENABLE, phase END, flags 5
DG 2009-11-11-22:05:22 0 2 702684180 rfm_inst_phase_dispatch 16 END phase processing
DG 2009-11-11-22:05:22 0 2 0 INSV: All instances have replied for message
DG 2009-11-11-22:05:22 0 2 0 req_id 2.1.702684180, opcode CTL_ENABLE, phase END
DG 2009-11-11-22:05:22 0 2 702684180 DMON: Entered rfm_release_chief_lock for CTL_ENABLE
DG 2009-11-11-22:05:22 0 2 702684180 DMON: Data Guard Broker initiated operation complete
DG 2009-11-11-22:05:22 0 2 702684180 DMON: CTL_ENABLE operation completed
Alert oracle primary:
FAL[server]: Fail to queue the whole FAL gap
GAP - thread 1 sequence 731-731
DBID 2809078314 branch 696087148
Wed Nov 11 22:05:17 2009
ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))"',' LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="ORCLB" register net_timeout=180 valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
Wed Nov 11 22:05:17 2009
ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
Wed Nov 11 22:05:17 2009
Thread 1 cannot allocate new log, sequence 805
Private strand flush not complete
Current log# 2 seq# 804 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCLA\REDO02.LOG
Thread 1 advanced to log sequence 805
Current log# 3 seq# 805 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCLA\REDO03.LOG
Wed Nov 11 22:05:22 2009
LNS: Failed to archive log 2 thread 1 sequence 804 (3113)
LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2
LNS: Standby redo logfile selected for thread 1 sequence 805 for destination LOG_ARCHIVE_DEST_2
Alter oracle standby
Primary database is in MAXIMUM PERFORMANCE mode
Wed Nov 11 22:05:22 2009
RFS LogMiner: Client disabled from further notification
Primary database is in MAXIMUM PERFORMANCE mode
RFS[1]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCLA\ONLINELOG\O1_MF_4_59HJ9T8L_.LOG'
Wed Nov 11 22:05:46 2009
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 731-731
DBID 2809078314 branch 696087148
FAL[client]: All defined FAL servers have been attempted.
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
Wed Nov 11 22:06:01 2009
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 5848
RFS[2]: Identified database type as 'physical standby'
Wed Nov 11 22:17:54 2009
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Can anyone see what !"·$%& is wrong whit this? maybe is the gap? this is a exact copy of the primary but set to standby.

SQL> recover database using backup controlfile;
ORA-00279: el cambio 25608871 generado en 09/24/2009 23:08:11 es necesario para
el thread 1
ORA-00289: sugerencia: D:\ORADATA\ARCHIVELOGS\ORCLB\DBSID_1_731_696087148.ARC
ORA-00280: el cambio 25608871 para el thread 1 estß en la secuencia n·mero 731
Especificar log: {<RET>=sugerido | nombre_archivo | AUTO | CANCEL}
ORA-00308: no se puede abrir el archive log
'D:\ORADATA\ARCHIVELOGS\ORCLB\DBSID_1_731_696087148.ARC'
ORA-27041: no se ha podido abrir el archivo
OSD-04002: no se ha podido abrir el archivo
O/S-Error: (OS 2) El sistema no puede hallar el archivo especificado.
So how i can recreate this file if i dont have it? anyone can help, please!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Problem with Dataguard Wizzard in OEM 10

Hi,
I've tried to create a physical standby database of a 10gR2 instance on the same host (windows 2003 64 bits) through OEM 10, and I get an error message at the first step.
I select "create a physical standby database" and I get this in french :
"Impossible de déterminer l'architecture de l'hôte principal."
which means something like :
"Unable to detect (or to find) main host architecture"
I didn't find anything related to this in alert.log or in OMS log files.
Does anyone know about this ?
I'll try to do it manually, but I'd like to understand why the wizzard is not working.
Thanks for your help

Hi :
"The /usr/bin/ldapsearch is an old version that does not support the "-Z" and "-P" flags to test SSL connection on port 636, use the ldapsearch command from SUN DS5.0/5.1 that comes bundled with Solaris9 and usually installed at /usr/iplanet/ds5 (DS5.0/5.1) or /var/Sun/mps (DS5.1/5.2) or /var/opt/mps/serverroot (DS5.2)"
Source : http://forums.sun.com/thread.jspa?threadID=5089467
Hope this can help,
Regards,
Groucho_fr

Does RMAN Work With DataGuard And Restore Points?

I only have a basic experience of RMAN on a training course and no experience of Data Guard.
We have an 11g set up where DataGuard is keeping production and DR in sync.
On a release weekend we want a rollback strategy in case any of the config goes wrong.
When the database was small and before we were using DataGuard this just consisted of datapump.
Now the database is 120GB that isn't an option in our timescale.
Can I set a restore point and use archive logs to keep track so that if there is a problem and we need to roll back we can just rollback to the restore point?
Would this work or would it cause problems with DataGuard?
Is rolling back to a restore point a relatively fast operation?

DataGuard works with Restore Points. The use case is when
a. You created a Restore Point for the Primary and Standby
b. You upgraded the Primary
c. You find a fault with the Primary
d. You revert both the Primary and the Standby to the Restore Point and resume DataGuard.
Hemant K Chitale

Problem with logminer in Data Guard configuration

Hi all,
I experience strange problem with applying of the logs in DataGuard configuration on the logical standby database side.
I've set up the configuration step by step as it is described in documentation (Oracle Data Guard Concepts and Administration, chapter 4).
Everything went fine until I issued
ALTER DATABASE START LOGICAL STANDBY APPLY;
I saw that log applying process was started by checking the output of
SELECT NAME, VALUE FROM V$LOGSTDBY_STATS WHERE NAME = 'coordinator state';
and
SELECT TYPE, HIGH_SCN, STATUS FROM V$LOGSTDBY;
but in few minutes it stoped and quering DBA_LOGSTDBY_EVENTS I saw the following records:
ORA-16111: log mining and apply setting up
ORA-01332: internal Logminer Dictionary error
Alert log says the following:
LOGSTDBY event: ORA-01332: internal Logminer Dictionary error
Wed Jan 21 16:57:57 2004
Errors in file /opt/oracle/admin/whouse/bdump/whouse_lsp0_5817.trc:
ORA-01332: internal Logminer Dictionary error
Here is the end of the whouse_lsp0_5817.trc
error 1332 detected in background process
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-01332: internal Logminer Dictionary error
But the most useful info I found in one more trace file (whouse_p001_5821.trc):
krvxmrs: Leaving by exception: 604
ORA-00604: error occurred at recursive SQL level 1
ORA-01031: insufficient privileges
ORA-06512: at "SYS.LOGMNR_KRVRDREPDICT3", line 68
ORA-06512: at line 1
Seems that somewhere the correct privileges were not given or smth like this. By the way I was doing all the operations under SYS account (as SYSDBA).
Could smb give me a clue where could be my mistake or what was done in the wrong way?
Thank you in advance.

Which is your SSIS version?
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

RAC Archivelogs not Switching on Closed Threads with Dataguard.

I have a 4 node Cluster with each database running 1 instance.
My experience is when RMAN backs up the Archivelogs it rolls the Closed threads over ie switchs Archivelogs and backs them up.
After I put one of my production databases ( 10.2.0.2 ) in Dataguard it changed, and only the Open thread switches logs.
It has caused problems with duplicating the database to test.
I went through support and Oracle said its a bug fixed in a higher version so Upgrade. ( Management not excited to do so )
The work around is to open the idle instances and immediately close them before an application thread tries to connect.
I just put a second database in dataguard ... a related application ... which is using the same Oracle home and it is switching all threads on the ArchiveLog backup.
The only difference is that the original has been open recovered ( flashbacked) and closed and the second has not but the Standby was recreated after wards ( I have put the standby in flashback now )
Has anyone else observed this behaviour.

If the Standby is in Maximum Availability and the primary has one or more Closed Threads, the Standby doesn't need the closed threads.
If you are doing Backups to create another duplicate, I suggest that you add a forced Switch or Archive Log for the closed threads in your backup script.
Hemant K Chitale

Problems with second standby database

Hello All,
I have oracle 10gr1. 1 primary db and 2 physical standby and 1 is in the same network with the primary and the other is on a remote network. The primary and the standby on the same network is working perfectly well. My problem is with the remote standby. Some log are not being archived. See output below
SEQUENCE# ARC APP
1755 YES NO
1761 YES NO
1772 YES NO
1774 YES NO
1782 YES NO
1789 YES NO
I get this error RFS[10]: "Possible network disconnect with primary database". I think it has something to do with the network connectivity of my second standby and the master db. What parameters should I tweak to avoid this?
Another thing is arhived logs from seq 1728 were not being applied. I tried manually recovering the archive log from 1728 but it says there is an error in the log. I tried getting the specified archive log from the master db and tried recovering it manually but still the same. How would I solve tjhis problem? Would rebuilding the second standby do the trick? Help needed badly.
Thanks in advanced.

Hi,
About seq 1728, if the archive has been lost or alterred, you'll have to rebuild the standby. At least take a backup of the first standby and restore the datafiles at the second standby.
About network connectivity, are you using DataGuard? If so, did you setup the FAL (Failed Archive Logs) server/client parameters on your standby? You can even set your fal_server as being both the primary and first standby..
You should investigate the network connectivity problem with your network administrator. Check alert log and trace files plus sqlnet logs to see when/where/why the communication with distant site fails sometimes.
HTH,
Yoann.

Streams with DataGuard design advice

I have two 10gR2 RAC installs with DataGuard physical copy mode. We will call the main system A and the standby system B. I have a third 10gR2 RAC install with two-way Streams Replication to system A. We will call this RAC system C.
When I have a failure scenario with system A, planned or unplanned, I need for system C's Streams Replication to start replicating with system B. When the system A is available again I need for system C to start replicating with system A again.
I am sure this is possible, and I am not the only one that wants to do something like this, but how? What are the pitfals?
Any advice on personal experience with this would be greatly appreciated!

Nice concept and I can only applaud to its ambitions.
+"I am sure this is possible, and I am not the only one that wants to do something like this".+
I would like to share your confidence, but i am afraid there are so many pitfalls than success will depends on how much pain you and you hierarchy can cope with.
Some thoughts:
Unless your dataguard is Synchronous, at the very moment where A fails, there will be missing TXN in C,
which may have been applied in B as Streams is quite fast. This alone tells us that a forced switch cannot
be guarantee consistent : You will have errors and some nasty one such as sequence numbers consumed
on A (or B) just before the crash, already replicated to B (or A)but never shipped to C. Upon awake C will
re-emit values already known on B (dup key on index?)
I hope you don't sell airplane ticket for in such a case you can sell some seats twice.
Does C have to appear as another A or is it allowed to have a different DB_NAME? (How will you set C in B?
is C another A which retakes A name or is C a distinct source).if C must have the same DB_NAME, the global
name must be the same. Your TNS construction will be have to cope with 2 identical TNS entry in your network
referring to 2 different hosts and DB. Possible with cascade lines at (ADDRESSES= ... , but to be tested.
If C is another A then C must have the same DB_name as LCR do have their origin DB name into them.
If C has a distinct name from A it must have its on apply process, not a problem it will be idle while A is alive,
but also a capture that capture nothing while A is alive, for it is Capture site who is supposed to send the ticks
to advance counters on B. Since C will be down in normal time, you will have to emulate this feature periodically
reseting the first_scn manually for this standby capture - you can jump archives providing you jump to another
archive with built in data dictionary - or accept to create a capture on B only when C wakes up. The best would
be to consider C as a copy of B (multi-master DML+DDL?) and re-instantiate tables without transferring any data
the apply and capture on C and B to whatever SCN is found to be max on both sites when C wakes up.
All this is possible, with lot of fun and hard work.
As of the return of the Jedi, I mean A after its recovered from its crash you did not tell us if the re-sync C-->A
is hot or cold. Cold is trivial but If it is hot, it can be done configuring a downstream capture from C to A with
the init SCN set to around the crash and re-load all archives produced on C. But then C and A must have a different
DB_name or maybe setting a different TAG will be enough, to be tested. Also there will be the critical switch
the multi-master replication C<-->B to A<-->B. This alone is a master piece of re-sync tables.
In all cases, I wish you a happy and great project and eager to hear about it.
Last, there was a PDF describing how to deal with dataguard switch with a DB using streams, but it is of little help,
for it assumes that the switch is gentle : no SCN missing. did not found it but maybe somebody can point a link to it.
Regards,
Bernard Polarski

A problem with threads

I am trying to implement some kind of a server listening for requests. The listener part of the app, is a daemon thread that listens for connections and instantiates a handling daemon thread once it gets some. However, my problem is that i must be able to kill the listening thread at the user's will (say via a sto button). I have done this via the Sun's proposed way, by testing a boolean flag in the loop, which is set to false when i wish to kill the thread. The problem with this thing is the following...
Once the thread starts excecuting, it will test the flag, find it true and enter the loop. At some point it will LOCK on the server socket waiting for connection. Unless some client actually connects, it will keep on listening indefinatelly whithought ever bothering to check for the flag again (no matter how many times you set the damn thing to false).
My question is this: Is there any real, non-theoretical, applied way to stop thread in java safely?
Thank you in advance,
Lefty

This was one solution from the socket programming forum, have you tried this??
public Thread MyThread extends Thread{
     boolean active = true;
     public void run(){
          ss.setSoTimeout(90);
          while (active){
               try{
                    serverSocket = ss.accept();
               catch (SocketTimeoutException ste){
               // do nothing
     // interrupt thread
     public void deactivate(){
          active = false;
          // you gotta sleep for a time longer than the
          // accept() timeout to make sure that timeout is finished.
          try{
               sleep(91);
          }catch (InterruptedException ie){
          interrupt();
}

Problem with Threads and a static variable

I have a problem with the code below. I am yet to make sure that I understand the problem. Correct me if I am wrong please.
Code functionality:
A timer calls SetState every second. It sets the state and sets boolean variable "changed" to true. Then notifies a main process thread to check if the state changed to send a message.
The problem as far I understand is:
Assume the timer Thread calls SetState twice before the main process Thread runs. As a result, "changed" is set to true twice. However, since the main process is blocked twice during the two calls to SetState, when it runs it would have the two SetState timer threads blocked on its synchronized body. It will pass the first one, send the message and set "changed" to false since it was true. Now, it will pass the second thread, but here is the problem, "changed" is already set to false. As a result, it won't send the message even though it is supposed to.
Would you please let me know if my understanding is correct? If so, what would you propose to resolve the problem? Should I call wait some other or should I notify in a different way?
Thanks,
B.D.
Code:
private static volatile boolean bChanged = false;
private static Thread objMainProcess;
   protected static void Init(){
        objMainProcess = new Thread() {
            public void run() {
                while( objMainProcess == Thread.currentThread() ) {
                   GetState();
        objMainProcess.setDaemon( true );
        objMainProcess.start();
    public static void initStatusTimer(){
        if(objTimer == null)
             objTimer = new javax.swing.Timer( 1000, new java.awt.event.ActionListener(){
                public void actionPerformed( java.awt.event.ActionEvent evt){
                          SetState();
    private static void SetState(){
        if( objMainProcess == null ) return;
        synchronized( objMainProcess ) {
            bChanged = true;
            try{
                objMainProcess.notify();
            }catch( IllegalMonitorStateException e ) {}
    private static boolean GetState() {
        if( objMainProcess == null ) return false;
        synchronized( objMainProcess ) {
            if( bChanged) {
                SendMessage();
                bChanged = false;
                return true;
            try {
                objMainProcess.wait();
            }catch( InterruptedException e ) {}
            return false;
    }

Thanks DrClap for your reply. Everything you said is right. It is not easy to make them alternate since SetState() could be called from different places where the state could be anything else but a status message. Like a GREETING message for example. It is a handshaking message but not a status message.
Again as you said, There is a reason I can't call sendMessage() inside setState().
The only way I was able to do it is by having a counter of the number of notifies that have been called. Every time notify() is called a counter is incremented. Now instead of just checking if "changed" flag is true, I also check if notify counter is greater than zero. If both true, I send the message. If "changed" flag is false, I check again if the notify counter is greater than zero, I send the message. This way it works, but it is kind of a patch than a good design fix. I am yet to find a good solution.
Thanks,
B.D.

Problem with threads running javaw

Hi,
Having a problem with multi thread programming using client server sockets. The program works find when starting the the application in a console using java muti.java , but when using javaw multi.java the program doesnt die and have to kill it in the task manager. The program doesnt display any of my gui error messages either when the server disconnect the client. all works find in a console. any advice on this as I havent been able to understand why this is happening? any comment would be appreciated.
troy.

troy,
Try and post a minimum code sample of your app which
does not work.
When using javaw, make sure you redirect the standard
error and standard output streams to file.
Graeme.Hi Graeme,
I dont understand what you mean by redirection to file? some of my code below.
The code works fine under a console, code is supposed to exit when the client (the other server )disconnects. the problem is that but the clientworker side of the code still works. which under console it doesnt.
public class Server{
ServerSocket aServerSocket;
Socket dianosticsSocket;
Socket nPortExpress;
ClientListener aClientListener;
LinkedList queue = new LinkedList();
int port = 0;
int clientPort = 0;
String clientName = null;
boolean serverAlive = true;
* Server constructor generates a server
* Socket and then starts a client threads.
* @param aPort      socket port of local machine.
public Server(int aPort, String aClientName, int aClientPort){
port = aPort;
clientName = aClientName;
clientPort = aClientPort;
try{
// create a new thread
aServerSocket = new ServerSocket(port) ;
// connect to the nPortExpress
aClientListener = new ClientListener(InetAddress.getByName(clientName), clientPort, queue,this);
// aClientListener.setDaemon(true);
aClientListener.start();
// start a dianostic port
DiagnosticsServer aDiagnosticsServer = new DiagnosticsServer(port,queue,aClientListener);
// System.out.println("Server is running on port " + port + "...");
// System.out.println("Connect to nPort");
catch(Exception e)
// System.out.println("ERROR: Server port " + port + " not available");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Server port " + port + " not available", JOptionPane.ERROR_MESSAGE);
serverAlive = false;
System.exit(1);
while(serverAlive&&aClientListener.hostSocket.isConnected()){
try{
// connect the client
Socket aClient = aServerSocket.accept();
//System.out.println("open client connection");
//System.out.println("client local: "+ aClient.getLocalAddress().toString());
// System.out.println("client localport: "+ aClient.getLocalPort());
// System.out.println("client : "+ aClient.getInetAddress().toString());
// System.out.println("client port: "+ aClient.getLocalPort());
// make a new client thread
ClientWorker clientThread = new ClientWorker(aClient, queue, aClientListener, false);
// start thread
clientThread.start();
catch(Exception e)
//System.out.println("ERROR: Client connection failure");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client connection failure", JOptionPane.ERROR_MESSAGE);
}// end while
} // end constructor Server
void serverExit(){
     JOptionPane.showMessageDialog(null, "Server ","ERROR: nPort Failure", JOptionPane.ERROR_MESSAGE);
     System.exit(1);
}// end class Server
*** connect to another server
public class ClientListener extends Thread{
InetAddress hostName;
int hostPort;
Socket hostSocket;
BufferedReader in;
PrintWriter out;
boolean loggedIn;
LinkedList queue;      // reference to Server queue
Server serverRef; // reference to main server
* ClientListener connects to the host server.
* @param aHostName is the name of the host eg server name or IP address.
* @param aHostPort is a port number of the host.
* @param aLoginName is the users login name.
public ClientListener(InetAddress aHostName, int aHostPort,LinkedList aQueue,Server aServer)      // reference to Server queue)
hostName = aHostName;
hostPort = aHostPort;
queue = aQueue;
serverRef = aServer;
// connect to the server
try{
hostSocket = new Socket(hostName, hostPort);
catch(IOException e){
//System.out.println("ERROR: Connection Host Failed");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort Failed", JOptionPane.ERROR_MESSAGE);
System.exit(0);
} // end constructor ClientListener
** multi client connection server
ClientWorker(Socket aSocket,LinkedList aQueue, ClientListener aClientListener, boolean diagnostics){
queue = aQueue;
addToQueue(this);
client = aSocket;
clientRef = aClientListener;
aDiagnostic = diagnostics;
} // end constructor ClientWorker
* run method is the main loop of the server program
* in change of handle new client connection as well
* as handle all messages and errors.
public void run(){
boolean alive = true;
String aSubString = "";
in = null;
out = null;
loginName = "";
loggedIn = false;
while (alive && client.isConnected()&& clientRef.hostSocket.isConnected()){
try{
in = new BufferedReader(new InputStreamReader(client.getInputStream()));
out = new PrintWriter(new OutputStreamWriter(client.getOutputStream()));
if(aDiagnostic){
out.println("WELCOME to diagnostics");
broadCastDia("Connect : diagnostics "+client.getInetAddress().toString());
out.flush();
else {
out.println("WELCOME to Troy's Server");
broadCastDia("Connect : client "+client.getInetAddress().toString());
     out.flush();
String line;
while(((line = in.readLine())!= null)){
StringTokenizer aStringToken = new StringTokenizer(line, " ");
if(!aDiagnostic){
broadCastDia(line);
clientRef.sendMessage(line); // send mesage out to netExpress
out.println(line);
out.flush();
else{
if(line.equals("GETIPS"))
getIPs();
else{
clientRef.sendMessage(line); // send mesage out to netExpress
out.println(line);
out.flush();
} // end while
catch(Exception e){
// System.out.println("ERROR:Client Connection reset");
                         JOptionPane.showMessageDialog(null, (e.toString()),"ERROR:Client Connection reset", JOptionPane.ERROR_MESSAGE);
try{
if(aDiagnostic){
broadCastDia("Disconnect : diagnostics "+client.getInetAddress().toString());
out.flush();
else {
broadCastDia("Disconnect : client "+client.getInetAddress().toString());
     out.flush();
// close the buffers and connection;
in.close();
out.close();
client.close();
// System.out.println("out");
// remove from list
removeThreadQueue(this);
alive = false;
catch(Exception e){
// System.out.println("ERROR: Client Connection reset failure");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client Connection reset failure", JOptionPane.ERROR_MESSAGE);
}// end while
} // end method run
* method run - Generates io stream for communicating with the server and
* starts the client gui. Run also parses the input commands from the server.
public void run(){
boolean alive = true;
try{
// begin to life the gui
// aGuiClient = new ClientGui(hostName.getHostName(), hostPort, loginName, this);
// aGuiClient.show();
in = new BufferedReader(new InputStreamReader(hostSocket.getInputStream()));
out = new PrintWriter(new OutputStreamWriter(hostSocket.getOutputStream()));
while (alive && hostSocket.isConnected()){
String line;
while(((line = in.readLine())!= null)){
System.out.println(line);
broadCast(line);
} // end while
} // end while
catch(Exception e){
//     System.out.println("ERRORa Connection to host reset");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort reset", JOptionPane.ERROR_MESSAGE);
try{
hostSocket.close();
     }catch(Exception a){
     JOptionPane.showMessageDialog(null, (a.toString()),"ERROR: Exception", JOptionPane.ERROR_MESSAGE);
alive = false;
System.exit(1);
} // end method run

Problem with threads and camera.

Hi everybody!
I've a problem with taking snapshot.
I would like to display a loading screen after it take snapshot ( sometimes i
have to wait few seconds after i took snapshot. Propably photo is being taken in time where i have to wait).
I was trying to use threads but i didn't succeed.
I made this code:
display.setCurrent(perform);
        new Thread(new Runnable(){
            public void run() {
                while((!performing.isShown()) && (backgroundCamera.isShown())){
                    Thread.yield();
                notifyAll();
        }).start();
        new Thread(new Runnable(){
            public void run() {
                try {
                    this.wait();
                } catch(Exception e) {
                    exceptionHandler(e);
                photo = camera.snapshot();
                display.setCurrent(displayPhoto);
        }).start();This code is sometimes showing performing screen but sometimes no.
I don't know why. In my opinion performing.isShown() method isn't working correctly.
Does anyone have some idea how to use threads here?

Hi,
I've finally managed to work this fine.
The code:
       Object o = new Object();
       display.setCurrent(perform);
        new Thread(new Runnable(){
            public void run() {
                while(!performing.isShown()){
                    Thread.yield();
               synchronized(o) {
                  o.notify();
        }).start();
        new Thread(new Runnable(){
            public void run() {
                try {
                    synchronized(o) {
                       o.wait(1);
                } catch(Exception e) {
                    exceptionHandler(e);
                photo = camera.snapshot();
                display.setCurrent(displayPhoto);
        }).start();

Problem with threads hanging

We have a problem where our application stops responding after a few days of usage. Things will for fine for a day or two, and then pretty quickly threads will start getting hung up, usually in places where they are allocating memory
We are running WebLogic 8.1 SP2 on Sun JDK 1.4.2_04 on Solaris 8 using the alternate threading model and the -server hotspot vm. We are running pretty much the same code that we had no problems with under WebLogic 6.1 SP4 and Sun JDK 1.3.1.
A thread dump usually shows that some or all of our execute threads are in the state "waiting for monitor entry" even though they are not currently waiting on any java locks. Here is a sample thread from the thread dump (we have ~120 threads so I don't want to post the full dump).
=============================================================================================
"ExecuteThread: '8' for queue: 'itgCrmWarExecutionQueue'" daemon prio=5 tid=0x005941d0 nid=0x2c waiting for monitor entry [c807f000..c807fc28]
at java.lang.String.substring(String.java:1446)
at java.lang.String.substring(String.java:1411)
at weblogic.servlet.internal.ServletRequestImpl.getRelativeUri(ServletRequestImpl.java:1872)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3492)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
=============================================================================================
String.java line 1446 for this jdk allocates a new String object, and all the other threads in this state also are creating new objects or arrays, etc.
We've done a pstack on this process when it's in this state, and the threads that are in the "waiting for monitor entry" that look like they're allocating memory are all waiting on the same lwp_mutex_lock with some allocation method that's calling into the native TwoGenerationCollectorPolicy.mem_allocate_work (see pstack output below for the same thread as in the thread dump above)
=============================================================================================
----------------- lwp# 44 / thread# 44 --------------------
ff31f364 lwp_mutex_lock (e3d70)
fee92384 __1cNObjectMonitorGenter26MpnGThread__v_ (5000, 525c, 5000, 50dc, 4800, 4af0) + 2d8
fee324d4 __1cSObjectSynchronizerKfast_enter6FnGHandle_pnJBasicLock_pnGThread__v_ (c807f65c, c807f7d4, 5941d0, 0, 35d654, fee328ec) + 68
fee32954 __1cQinstanceRefKlassZacquire_pending_list_lock6FpnJBasicLock__v_ (c807f7d4, ff170000, d4680000, 4491d4, fee1bc2c,
0) + 78
fee3167c __1cPVM_GC_OperationNdoit_prologue6M_i_ (c807f7bc, 4400, ff170000, 2d2b8, 4a6268, c807fa18) + 38
fee2e0b0 __1cIVMThreadHexecute6FpnMVM_Operation__v_ (c807f7bc, 963a8, 0, 0, 1, 0) + 90
fed2c2a4 __1cbCTwoGenerationCollectorPolicyRmem_allocate_work6MIii_pnIHeapWord__ (962c0, ff1c29ec, ff1c297c, ff131a26, 4800, 4998) + 160
fed22940 __1cNinstanceKlassRallocate_instance6MpnGThread__pnPinstanceOopDesc__ (ee009020, 5941d0, 15ca581, 3647f0, 4a6268, c807f8c8) + 180
fed34928 __1cLOptoRuntimeFnew_C6FpnMklassOopDesc_pnKJavaThread__v_ (ee009018, 5941d0, 0, 0, 0, 0) + 28
fa435a58 ???????? (ee009018, e86de, 15ca4de, 50dc, 5941d0, c807f9c8)
fb36f9a4 ???????? (0, d412ccd8, ee046c28, ff170000, 0, 0)
fad8b278 ???????? (ee046c28, d6000c90, ee046530, 8, db8e8450, c807f9e8)
fad62abc ???????? (d412ccd8, ee046530, d6000c90, ee3bfa38, 8, c807fa18)
fa4b3c38 ???????? (c807fb9c, 0, f2134700, fa415e50, 8, c807faa8)
fa40010c ???????? (c807fc28, c807fe90, a, ee9e1e20, 4, c807fb40)
fed5d48c __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (c807fe88, c807fcf0, c807fda8, 5941d0, 5941d0, c807fd00) + 27c
fee4b784 __1cJJavaCallsMcall_virtual6FpnJJavaValue_nLKlassHandle_nMsymbolHandle_4pnRJavaCallArguments_pnGThread__v_ (ff170000, 594778, c807fd9c, c807fd98, c807fda8, 5941d0) + 164
fee5e8dc __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (c807fe88, c807fe84, c807fe7c, c807fe74, c807fe6c, 5941d0) + 6c
fee6fc74 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (5941d0, 5941d0, 838588, 594778, 306d10, fee69254) + 128
fee6927c __1cKJavaThreadDrun6M_v_ (5941d0, 2c, 40, 0, 40, 0) + 284
fee6575c _start   (5941d0, fa1a1600, 0, 0, 0, 0) + 134
ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
=============================================================================================
Also when it's having this problem, the "VM Thread" is always using a lot of processor time. We did a couple of pstacks today while it was having this problem, and this thread was stuck in the ONMethodSweeper.sweep for over 15 minutes when we finally killed the server.
From the thread dump:
"VM Thread" prio=5 tid=0x000e2d20 nid=0x2 runnable
From the first pstack:
=============================================================================================
----------------- lwp# 2 / thread# 2 --------------------
fed40c04 __1cXvirtual_call_RelocationIparse_ic6FrpnICodeBlob_rpC5rppnHoopDesc_pi_nNRelocIterator__ (42a2f4, fa5fa46d, ffffffff, fc4ffcb8, 42a2f4, 42a324) + 124
fed46318 __1cKCompiledIC2t5B6MpnKRelocation__v_ (42a2f0, fc4ffd24, fc4ffd4c, e802, 0, 6) + 38
fed90c38 __1cHnmethodVcleanup_inline_caches6M_v_ (fa5f7f88, fa608940, 1, 0, fa400000, 6) + 1ac
fede18b4 __1cONMethodSweeperFsweep6F_v_ (2cf38, 0, ffffffff, ff1cf1fc, ff1c66e8, fede1d44) + 1b0
fede1e6c __1cUSafepointSynchronizeFbegin6F_v_ (2cf38, ff1ba138, 5000, 50dc, 5000, 525c) + 248
feef1fd4 __1cIVMThreadEloop6M_v_ (4400, 4000, 4324, 4000, 42b0, 3800) + 3d4
feef1ae4 __1cIVMThreadDrun6M_v_ (e2d20, 2, 40, 0, 40, 0) + 8c
fee6575c _start   (e2d20, ff270200, 0, 0, 0, 0) + 134
ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
=============================================================================================
Second pstack
=============================================================================================
----------------- lwp# 2 / thread# 2 --------------------
fed41180 __1cXvirtual_call_RelocationIparse_ic6FrpnICodeBlob_rpC5rppnHoopDesc_pi_nNRelocIterator__ (0, ff1b9664, ffffffff, fc4ffcb8, a6f2cc, fc4ffbd0) + 6a0
fed46318 __1cKCompiledIC2t5B6MpnKRelocation__v_ (a6f2c8, fc4ffd24, fc4ffd4c, e802, 0, 6) + 38
fed90c38 __1cHnmethodVcleanup_inline_caches6M_v_ (faded4c8, fadf2c80, 1, 0, fa400000, 6) + 1ac
fede18b4 __1cONMethodSweeperFsweep6F_v_ (2cf38, 0, ffffffff, ff1cf1fc, ff1c66e8, fede1d44) + 1b0
fede1e6c __1cUSafepointSynchronizeFbegin6F_v_ (2cf38, ff1ba138, 5000, 50dc, 5000, 525c) + 248
feef1fd4 __1cIVMThreadEloop6M_v_ (4400, 4000, 4324, 4000, 42b0, 3800) + 3d4
feef1ae4 __1cIVMThreadDrun6M_v_ (e2d20, 2, 40, 0, 40, 0) + 8c
fee6575c _start   (e2d20, ff270200, 0, 0, 0, 0) + 134
ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
=============================================================================================
Has anyone ever seen anything like this? I'm trying to figure out if this is caused by something we're doing, or something relating to our environment and jvm options. Any ideas?

Thanks for the reply - I'm testing our app with the +UseConcMarkSweepGC now in our test environment to make sure it doesn't cause any problems there. Unfortunately the only place we've had this problem is on the production server, so it's extra difficult debugging this.
We're using the following memory options:
-ms512m -mx512m -XX:NewSize=128m -XX:PermSize=192m -XX:MaxNewSize=128m -XX:MaxPermSize=192m -XX:SurvivorRatio=8and the following debugging options, as we've also been seeing OutOfMemoryErrors ( see http://forum.java.sun.com/thread.jsp?forum=37&thread=522354&tstart=45&trange=15 )
-verbosegc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGCBTW, which c++filt version and options are you using? Our Solaris boxes only seem to have the GNU version installed. I was trying to run that on some of the other stack traces and wasn't getting anywhere, and didn't know if because it was GNU version wouldn't work on something compiled with the Sun compiler.
Thanks!
--Andy

Problem with threads and ProgressMonitor

Dear Friends:
I have a little problem with a thread and a ProgressMonitor. I have a long time process that runs in a thread (the thread is in an separate class). The thread has a ProgressMonitor that works fine and shows the tasks progress.
But I need deactivate the main class(the main class is the user interface) until the thread ends.
I use something like this:
LongTask myTask=new LongTask();
myTask.start();
myTask.join();
Now, the main class waits for the task to end, but the progress monitor don`t works fine: it shows only the dialog but not the progress bar.
What's wrong?

Is the dialog a modal dialog? This can block other UI updates.
In general, you should make sure that it isn't modal, and that your workThread has a fairly low priority so that the UI can do its updating

Problem with threads and/or memory

I'm developing an application where there are 3 threads. One of them sends a request to the other, and if the 2nd can't answer it, it sends it to the 3rd (similar to CPU -> CACHE -> MEMORY). When i run the program with 1000-10.000 requests, no problem occurs. When i run it with 300.000-1.000.000 requests, it sometimes hangs. Is this a problem with the garbage collector, or should it be related to the threads mecanism.
(note: eache thread is in execution using a finite state machine)

i had been running the program inside Netbeans.
Running the jar using the command line outside
Netbeans i have no more problems... Does Netbeans use
it's own JVM?Depends how you set it up, but look under the options. There are settings for the compiler and jvm that it uses.

Problem with DataGuard

Similar Messages

Maybe you are looking for