Log transport failing to standby host , target using ASM.
Hi,
Please help me in the following scenario. I have two nodes ASM1 & ASM2 with RHEL4 U5 OS. On node ASM1 there is database ORCL using ASM diskgroups DATA & RECOVER and archive location is on '+RECOVER/orcl/'. On ASM2 node, I have to configure STDBYORCL (standby) database without ASM (i.e. on FS). I have taken the copy of database ORCL via RMAN, using following command:
run{
copy datafile 1 to '/opt/oracle/admin/df1.dbf';
copy datafile 2 to '/opt/oracle/admin/df2.dbf';
copy datafile 3 to '/opt/oracle/admin/df3.dbf';
copy datafile 4 to '/opt/oracle/admin/df4.dbf';
copy current controlfile for standby to '/opt/oracle/admin/stdbyorcl_control01.ctl'
Then I have ftp'd all to ASM2 and put them on FS /u01/oradata. Have made all necessary changes in primary and standby database pfile and then mount the standby database and put it in managed recovery mode. Unfortunately, log transport service is not working and archives are not getting shipped to standby host.
Here are all configuration details.
Primary database ORCL pfile:
[oracle@asm dbs]$ more initorcl.ora
stdbyorcl.__db_cache_size=251658240
orcl.__db_cache_size=226492416
stdbyorcl.__java_pool_size=4194304
orcl.__java_pool_size=4194304
stdbyorcl.__large_pool_size=4194304
orcl.__large_pool_size=4194304
stdbyorcl.__shared_pool_size=100663296
orcl.__shared_pool_size=125829120
stdbyorcl.__streams_pool_size=0
orcl.__streams_pool_size=0
*.audit_file_dest='/opt/oracle/admin/orcl/adump'
*.background_dump_dest='/opt/oracle/admin/orcl/bdump'
*.compatible='10.2.0.1.0'
*.control_files='+DATA/orcl/controlfile/current.270.665007729','+RECOVER/orcl/controlfile/current.262.665007731'
*.core_dump_dest='/opt/oracle/admin/orcl/cdump'
*.db_block_size=8192
*.db_create_file_dest='+DATA'
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='orcl'
*.db_recovery_file_dest='+RECOVER'
*.db_recovery_file_dest_size=3163553792
*.db_unique_name='ORCL'
*.fal_client='ORCL'
*.fal_server='STDBYORCL'
*.instance_name='orcl'
*.job_queue_processes=10
*.log_archive_config='dg_config=(orcl,stdbyorcl)'
*.log_archive_dest_1='LOCATION=+RECOVER/orcl/'
*.log_archive_dest_2='SERVICE=stdbyorcl'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_format='%t_%s_%r.dbf'
*.open_cursors=300
*.pga_aggregate_target=121634816
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=364904448
*.standby_file_management='AUTO'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS'
*.user_dump_dest='/opt/oracle/admin/orcl/udump'
Standby database STDBYORCL pfile:
[oracle@asm2 dbs]$ more initstdbyorcl.ora
stdbyorcl.__db_cache_size=251658240
stdbyorcl.__java_pool_size=4194304
stdbyorcl.__large_pool_size=4194304
stdbyorcl.__shared_pool_size=100663296
stdbyorcl.__streams_pool_size=0
*.audit_file_dest='/opt/oracle/admin/stdbyorcl/adump'
*.background_dump_dest='/opt/oracle/admin/stdbyorcl/bdump'
*.compatible='10.2.0.1.0'
*.control_files='u01/oradata/stdbyorcl_control01.ctl'#Restore Controlfile
*.core_dump_dest='/opt/oracle/admin/stdbyorcl/cdump'
*.db_block_size=8192
*.db_create_file_dest='/u01/oradata'
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='orcl'
*.db_recovery_file_dest='/u01/oradata/backup'
*.db_recovery_file_dest_size=3163553792
*.db_unique_name='STDBYORCL'
*.fal_client='STDBYORCL'
*.fal_server='ORCL'
*.instance_name='stdbyorcl'
*.job_queue_processes=10
*.log_archive_config='dg_config=(orcl,stdbyorcl)'
*.log_archive_dest_1='LOCATION=/u01/oradata/archive'
*.log_archive_dest_2='SERVICE=orcl'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_format='%t_%s_%r.dbf'
*.log_archive_start=TRUE
*.open_cursors=300
*.pga_aggregate_target=121634816
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=364904448
*.standby_archive_dest='LOCATION=/u01/oradata/archive'
*.standby_file_management='AUTO'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS'
*.user_dump_dest='/opt/oracle/admin/stdbyorcl/udump'
db_file_name_convert=('+DATA/ORCL/DATAFILE','/u01/oradata','+RECOVER/ORCL/DATAFILE','/u01/oradata')
log_file_name_convert=('+DATA/ORCL/ONLINELOG','/u01/oradata','+RECOVER/ORCL/ONLINELOG','/u01/oradata')
Have configured the tns service on both the hosts and its working absolutely fine.
ASM1
=====
[oracle@asm dbs]$ tnsping stdbyorcl
TNS Ping Utility for Linux: Version 10.2.0.1.0 - Production on 19-SEP-2008 18:49:00
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.20)(PORT = 1521))) (CONNECT_DATA = (SID = stdbyorcl) (SERVER = DEDICATED)))
OK (30 msec)
ASM2
=====
[oracle@asm2 archive]$ tnsping orcl
TNS Ping Utility for Linux: Version 10.2.0.1.0 - Production on 19-SEP-2008 18:48:39
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.10)(PORT = 1521))) (CONNECT_DATA = (SID = orcl) (SERVER = DEDICATED)))
OK (30 msec)
Please guide where I am missing. Thanking you in anticipation.
Regards,
Ravish Garg
(Oracle DBA)
As Anvar said, check your primary db's alert log what error message you get...
I am wondering you need this in your standby parameter file?..
*.log_archive_dest_2='SERVICE=orcl'
*.log_archive_dest_state_2='ENABLE'
Similar Messages
-
Hi Guys,
Good Day! Im receving this type of log on my 4507 switch. Appreciate if someone could give us an explanation on this and how to resolve this item. I cant find also the MAC address owner in ieee either
Jun 16 09:59:56 EDT: %C4K_EBM-4-HOSTFLAPPING: Host 0C:07:AC:00:00:1B in vlan 29 is moving from port Gi5/13 to port Gi5/20
.Jun 16 10:00:03 EDT: %C4K_EBM-4-HOSTFLAPPING: STANDBY:Host 0C:07:AC:00:00:1B in vlan 29 is moving from port Gi5/2 to port Gi5/20Years have gone by, so sure you have figured this out. But since I stumbled on it, I figure someone who needs help may too. This is typically caused by a LAN loop.
- If those are both ports go to 'user' devices: there may be a misconnection such as PC port and switch port of a VoIP phone connected to the wall plate, thus bridging (LAN looping). It could also be a dual uplinked hub or 'dumb' switch not running STP. I would make sure that any Cisco switch userports that have 'spanning-tree portfast' enabled are also running 'spanning-tree bpduguard enable' to ensure that frames only expected from switches (BPDUs) can trigger a port shut if seen. If you cannot run bpduguard, you should not run portfast! Small unmanaged switches often do not run STP, do be careful that they do not become dual uplinked.
- Wireless Roaming (ports go to APs or switches feeding APs): When layer two wireless bridges connected users directly to the LAN (not CAPWAP tunneled to a controller) either because they are autonomous more or 'FlexConnect' is enabled (users for select WLANs/SSIDs locally bridged), MACs may 'flap' if rapidly hopping beween two APs.
- Trunking Misconfguration: Verify "ALL" trunking in your network does NOT have PortFast enabled. Flaps on one switch may not indicate it is the miconfgured switch, only that it is seeing flappping. The entire LAN most be looked at. Portfast disables loop avoidance, STP. -
New Non-ASM Standby Trying to use ASM during recovery
Oracle 11.2.0.3 on RH6 x86_64. Cross-posting from oracle-l.
We have a database on ASM. We want to migrate to filesystem storage on same host (Oracle ZFS). Recommended path from Oracle is to create a standby and then do a failover when ready. Simple enough you'd think.
Standby has all reference to ASM diskgroups removed, and convert parameters set appropriately. Take a new backup including archivelogs and also a backup standby controlfile. The "duplicate target database for standby" performs the restore phase perfectly fine. When the media recovery phase starts, I see it tries to mount the diskgroup that the primary uses for ASM. However it fails to do so (plenty of errors to alert log), then recovery fails and the instance is left in mount mode. Subsequent attempt to run "recover database" or even "crosscheck archivelog all" run into the same ASM errors.
The one odd thing I see is the reference to the srvctl resource name for that diskgroup:
Mon Aug 19 10:41:35 2013
ERROR: failed to establish dependency between database prod_zfs and diskgroup resource ora.FRA.dg
However I never registered prod_zfs in srvctl, and it still isn't listed when I run "srvctl config database".
There are no references to ASM paths in the standby v$logfile, v$datafie, v$tempfile or v$archived_log. Created a trace controlfile and the ASM paths it uses are for logfiles and datafiles which are successfully restored on disk and renamed in the controlfile.
Wondering if any of you have seen this.Here's an example of what I can reproduce 100%of the time:
RMAN> backup database plus archivelog;
Starting implicit crosscheck backup at 08/19/2013 16:28:53
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=487 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=498 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=509 device type=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: SID=564 device type=DISK
ORA-03113: end-of-file on communication channel
ORA-01403: no data found
ORA-01403: no data found
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
... (repeated many times)
Crosschecked 63 objects
ORA-03113: end-of-file on communication channel
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
... (repeated many times)
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03113: end-of-file on communication channel
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
ORA-03114: not connected to ORACLE
... (repeated many times)
ORA-03114: not connected to ORACLE
ORA-03113: end-of-file on communication channel
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 08/19/2013 16:28:58
ORA-03114: not connected to ORACLE -
Can Grid Control 10gR2 create a standby database when primary db uses ASM?
Does anyone know if Grid Control 10gR2 will be able to create a standby database when the primary database uses ASM for data files, redo log files, and archive log files but the standby database will use mounted disks? If it can, would it matter that the primary db will be a RAC cluster and the standby will be a single instance db?
I appreciate your reply and hope you are correct. Have you had a look at the 10gR2 Grid Control to confirm this or are you only going on published statements? The reason I ask is because previous versions of Grid Control claimed to support ASM but they would only allow you to work with them AFTER you had created a standby database manually but you couldn't actually use Grid Control to create a standby database from a primary database that had its log files on ASM disks.
-
Solaris 10 SCSI transport failed reason 'tran err' on host level
Hello,
we are frequently getting below errors on host, can any one please help to solve this issue?
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 1 20:41:09 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 1 20:41:09 host SCSI transport failed: reason 'tran_err': retrying command
Mar 2 00:30:14 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::GPN_ID for D_ID=2e1400 failed
Mar 2 00:30:14 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::N_x Port with D_ID=2e1400, PWWN=50060e80164ed673 disappeared from fabric
Mar 2 00:30:16 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::N_x Port with D_ID=2e1400, PWWN=50060e80164ed673 reappeared in fabric
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 2 00:30:18 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 2 00:30:18 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Requested Block: 367501 Error Block: 367501
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B0
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 00:30:36 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,5 (ssd112):
Mar 2 00:30:36 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Requested Block: 201152 Error Block: 201152
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B5
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 00:31:40 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,2 (ssd115):
Mar 2 00:31:40 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Requested Block: 10063136 Error Block: 10063136
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B2
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 00:32:31 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,4 (ssd113):
Mar 2 00:32:31 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Requested Block: 71274 Error Block: 71274
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B4
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 03:41:29 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,3 (ssd114):
Mar 2 03:41:29 host Error for Command: read(10) Error Level: Retryable
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Requested Block: 88112 Error Block: 88112
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B3
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 06:00:00 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,1 (ssd116):
Mar 2 06:00:00 host Error for Command: read(10) Error Level: Retryable
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Requested Block: 202608 Error Block: 202608
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B1
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 17:02:01 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 2 17:02:01 host SCSI transport failed: reason 'timeout': retrying command
Mar 4 02:07:11 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130304020711-1
Mar 4 02:07:21 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130304020711-2
Mar 5 02:06:47 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130305020647-1
Mar 5 02:06:57 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130305020647-2
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 5 10:02:55 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,2 (ssd115):
Mar 5 10:02:55 host SCSI transport failed: reason 'timeout': retrying command
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 6 02:06:38 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130306020638-1
Mar 6 02:06:48 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130306020638-2
Mar 6 05:00:00 host explorer: [ID 702911 daemon.notice] Explorer started
Mar 6 05:02:49 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18043] core dumped: /ecmp/ecm/log/cores/luxadm.host.18043.core
Mar 6 05:02:50 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18046] core dumped: /ecmp/ecm/log/cores/luxadm.host.18046.core
Mar 6 05:02:54 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18331] core dumped: /ecmp/ecm/log/cores/luxadm.host.18331.core
Mar 6 05:03:46 host explorer: [ID 702911 daemon.notice] Explorer finished
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 6 12:27:02 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[28834] core dumped: /ecmp/ecm/log/cores/luxadm.host.28834.core
Mar 6 12:27:33 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[28839] core dumped: /ecmp/ecm/log/cores/luxadm.host.28839.core
Mar 6 15:24:11 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5006] core dumped: /ecmp/ecm/log/cores/luxadm.host.5006.core
Mar 6 15:30:52 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5699] core dumped: /ecmp/ecm/log/cores/luxadm.host.5699.core
Mar 6 15:31:57 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5975] core dumped: /ecmp/ecm/log/cores/luxadm.host.5975.core
Mar 6 15:32:39 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5987] core dumped: /ecmp/ecm/log/cores/luxadm.host.5987.core
Mar 6 15:36:16 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[6274] core dumped: /ecmp/ecm/log/cores/luxadm.host.6274.core
Mar 6 15:36:38 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[6286] core dumped: /ecmp/ecm/log/cores/luxadm.host.6286.core
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 6 18:23:44 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 6 18:23:44 host SCSI transport failed: reason 'tran_err': retrying command
Mar 7 01:43:47 host xntpd[735]: [ID 774427 daemon.notice] time reset (step) 0.139069 s
Mar 7 02:07:10 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130307020710-1
Mar 7 02:07:20 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130307020710-2
Mar 7 02:07:58 host xntpd[735]: [ID 774427 daemon.notice] time reset (step) 0.152342 s
Mar 7 07:23:29 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[24350] core dumped: /ecmp/ecm/log/cores/luxadm.host.24350.coreHello,
we are frequently getting below errors on host, can any one please help to solve this issue?
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 1 20:41:09 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 1 20:41:09 host SCSI transport failed: reason 'tran_err': retrying command
Mar 2 00:30:14 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::GPN_ID for D_ID=2e1400 failed
Mar 2 00:30:14 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::N_x Port with D_ID=2e1400, PWWN=50060e80164ed673 disappeared from fabric
Mar 2 00:30:16 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::N_x Port with D_ID=2e1400, PWWN=50060e80164ed673 reappeared in fabric
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 2 00:30:18 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 2 00:30:18 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Requested Block: 367501 Error Block: 367501
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B0
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 00:30:36 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,5 (ssd112):
Mar 2 00:30:36 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Requested Block: 201152 Error Block: 201152
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B5
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 00:31:40 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,2 (ssd115):
Mar 2 00:31:40 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Requested Block: 10063136 Error Block: 10063136
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B2
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 00:32:31 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,4 (ssd113):
Mar 2 00:32:31 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Requested Block: 71274 Error Block: 71274
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B4
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 03:41:29 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,3 (ssd114):
Mar 2 03:41:29 host Error for Command: read(10) Error Level: Retryable
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Requested Block: 88112 Error Block: 88112
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B3
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 06:00:00 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,1 (ssd116):
Mar 2 06:00:00 host Error for Command: read(10) Error Level: Retryable
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Requested Block: 202608 Error Block: 202608
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B1
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 17:02:01 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 2 17:02:01 host SCSI transport failed: reason 'timeout': retrying command
Mar 4 02:07:11 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130304020711-1
Mar 4 02:07:21 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130304020711-2
Mar 5 02:06:47 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130305020647-1
Mar 5 02:06:57 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130305020647-2
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 5 10:02:55 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,2 (ssd115):
Mar 5 10:02:55 host SCSI transport failed: reason 'timeout': retrying command
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 6 02:06:38 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130306020638-1
Mar 6 02:06:48 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130306020638-2
Mar 6 05:00:00 host explorer: [ID 702911 daemon.notice] Explorer started
Mar 6 05:02:49 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18043] core dumped: /ecmp/ecm/log/cores/luxadm.host.18043.core
Mar 6 05:02:50 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18046] core dumped: /ecmp/ecm/log/cores/luxadm.host.18046.core
Mar 6 05:02:54 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18331] core dumped: /ecmp/ecm/log/cores/luxadm.host.18331.core
Mar 6 05:03:46 host explorer: [ID 702911 daemon.notice] Explorer finished
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 6 12:27:02 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[28834] core dumped: /ecmp/ecm/log/cores/luxadm.host.28834.core
Mar 6 12:27:33 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[28839] core dumped: /ecmp/ecm/log/cores/luxadm.host.28839.core
Mar 6 15:24:11 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5006] core dumped: /ecmp/ecm/log/cores/luxadm.host.5006.core
Mar 6 15:30:52 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5699] core dumped: /ecmp/ecm/log/cores/luxadm.host.5699.core
Mar 6 15:31:57 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5975] core dumped: /ecmp/ecm/log/cores/luxadm.host.5975.core
Mar 6 15:32:39 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5987] core dumped: /ecmp/ecm/log/cores/luxadm.host.5987.core
Mar 6 15:36:16 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[6274] core dumped: /ecmp/ecm/log/cores/luxadm.host.6274.core
Mar 6 15:36:38 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[6286] core dumped: /ecmp/ecm/log/cores/luxadm.host.6286.core
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 6 18:23:44 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 6 18:23:44 host SCSI transport failed: reason 'tran_err': retrying command
Mar 7 01:43:47 host xntpd[735]: [ID 774427 daemon.notice] time reset (step) 0.139069 s
Mar 7 02:07:10 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130307020710-1
Mar 7 02:07:20 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130307020710-2
Mar 7 02:07:58 host xntpd[735]: [ID 774427 daemon.notice] time reset (step) 0.152342 s
Mar 7 07:23:29 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[24350] core dumped: /ecmp/ecm/log/cores/luxadm.host.24350.core -
Concurrent manager log CONC-SM TNS FAIL ICM failed to start for target MSOA
Hi all,
We are doing cloning from two node PCP with loadbalancer to single node application tier.
I did preclone in database and one of the node of application,
Run adcfgclone.pl in dbTier and AppsTier everything went smooth, But the Three managers are not coming up,
1. Internel manager
2.Standar manager
3.standard manager
Thease three managers are pointing to node" Prymary node of PCP
We followed the note: 555081.1 still the issue is same
The manager logfile shows:
"Check that your system has enough resources to start a concurrent manager process : 15-NOV-2008 21:20:22
Starting STANDARD Concurrent Manager : 15-NOV-2008 21:20:22
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /ebiz/u01/appltest/TEST/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /ebiz/u01/appltest/TEST/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process : 15-NOV-2008 21:20:23
Starting Internal Concurrent Manager Concurrent Manager : 15-NOV-2008 21:20:23
CONC-SM TNS FAIL
: ICM failed to start for target MSOAAPPL2. Review ICM log files for additional information.
Process monitor session ended : 15-NOV-2008 21:20:23"
Please help me out in resolving this
many thanks in advance..Hi all,
Sorted out by changing the Primary node as thhe corect node and run cmclean.sql..
Now the managers are working file..
Thanks and Regards
Vasu -
I operate an Amway Business and use the switch share duplicate APP. Initial log in was successful but now it reads " Log in failed ( GW900751 ). This is constant upon log in attempts. Is there a way to rectify this?
Hi Tracy,
I don't suspect Malware yet, Id guess Disk corruption or failing Hard Drive with Files not found.
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
If perchance you can't find your install Disc, at least try it from the Safe Boot part onward. -
Archive logs not applied on standby!!
Hi Guys,
I am trying to set up physical standby on windows 2003 server. I am using oracle 10.2.0.4.0. I get the following error in my alert file on standby
Failed to request gap sequence
Following is the results of some queries :
SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
MR(fg) WAIT_FOR_GAP 1 10004 0 0
SQL> select * from v$archive_gap;
no rows selected
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
ARC0: Becoming the 'no FAL' ARCH
MESSAGE
ARC0: Becoming the 'no SRL' ARCH
ARC1: Becoming the heartbeat ARCH
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply
Media Recovery Waiting for thread 1 sequence 10004
Fetching gap sequence in thread 1, gap sequence 10004-10017
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 10004-10017
DBID 2422302575 branch 670594799
FAL[client]: All defined FAL servers have been attempted.
MESSAGE
MRP0: Background Media Recovery cancelled with status 16037
MRP0: Background Media Recovery process shutdown
Managed Standby Recovery Canceled
Media Recovery Start: Managed Standby Recovery
Managed Standby Recovery not using Real Time Apply
Media Recovery Waiting for thread 1 sequence 10004
Fetching gap sequence in thread 1, gap sequence 10004-10017
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 10004-10017
DBID 2422302575 branch 670594799
FAL[client]: All defined FAL servers have been attempted.
SQL>SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG
where applied= 'YES'
no rows selected
##Modification to primary##
*.log_archive_dest_2='SERVICE=STANDBY'
*.fal_client='STUTEST'
*.fal_server='STUSTANDBY'
*.log_archive_config='DG_CONFIG=(STUTEST,STUSTANDBY)'
##Modification to standby##
*.db_unique_name='STANDBY'
*.log_archive_dest_2='SERVICE=STANDBY'
*.log_archive_dest_state_2='ENABLE'
*.Fal_server=STUTEST
*.Fal_client=STUSTANDBY
*.db_file_name_convert='H:\ORACLE\ORADATA\STUTEST\','I:\ORACLE\ORADATA\STUTEST\s_'
*.log_file_name_convert='D:\oracle\oradata\STUTEST\','D:\oracle\oradata\STUTEST\s_'
Nore: I used RMAN to create the standby database. The following are brief steps
Below are the steps to accomplish the task :
Step 1: Backup the database that includes backup of datafiles, archivelogs and controlfile for standby
backup current controlfile for standby;
Step 2: Move the backups to the standby server and restore control file from backup
Step 3: Make changes in the parameter files of both primary and standby database
Step 4: Do the restore and recover on standby database
Step 5: Put the standby database in recover managed mode
Thanks for help guys!!!!!Hi sb92075
Alert log on standby
alter database mount standby database
Mon Jul 26 14:10:40 2010
Setting recovery target incarnation to 1
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=21, OS id=6708
ARC1 started with pid=22, OS id=3892
ARC2 started with pid=23, OS id=4380
ARC3 started with pid=24, OS id=4896
ARC4 started with pid=25, OS id=6348
ARC5 started with pid=26, OS id=5868
ARC6 started with pid=27, OS id=6904
ARC7 started with pid=28, OS id=4428
ARC8 started with pid=29, OS id=5008
Mon Jul 26 14:10:40 2010
ARC0: Archival started
ARC9 started with pid=30, OS id=5804
Mon Jul 26 14:10:41 2010
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
ARCH: STARTING ARCH PROCESSES COMPLETE
Mon Jul 26 14:10:41 2010
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC0: Thread not mounted
Mon Jul 26 14:10:41 2010
Successful mount of redo thread 1, with mount id 2477113436
Mon Jul 26 14:10:41 2010
Physical Standby Database mounted.
Mon Jul 26 14:10:42 2010
ARC1: Becoming the heartbeat ARCH
Completed: alter database mount standby database
Mon Jul 26 14:10:42 2010
Errors in file c:\oracle\admin\stustandby\udump\stustandby_ora_6604.trc:
Mon Jul 26 14:11:41 2010
alter database recover managed standby database disconnect from session
MRP0 started with pid=19, OS id=3696
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 7 processes
Mon Jul 26 14:11:46 2010
Waiting for all non-current ORLs to be archived...
Media Recovery Waiting for thread 1 sequence 10004
Fetching gap sequence in thread 1, gap sequence 10004-10017
Mon Jul 26 14:11:47 2010
Completed: alter database recover managed standby database disconnect from session
Mon Jul 26 14:12:16 2010
*FAL[client]: Failed to request gap sequence*
GAP - thread 1 sequence 10004-10017
DBID 2422302575 branch 670594799
*FAL[client]: All defined FAL servers have been attempted.*
Alert log on primary
Mon Jul 26 13:50:11 2010
db_recovery_file_dest_size of 40960 MB is 49.73% 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.
Mon Jul 26 13:50:12 2010
Successfully onlined Undo Tablespace 19.
Mon Jul 26 13:50:12 2010
SMON: enabling tx recovery
Mon Jul 26 13:50:12 2010
Database Characterset is WE8ISO8859P1
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 8
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=38, OS id=3776
Mon Jul 26 13:50:14 2010
Completed: ALTER DATABASE OPEN
Mon Jul 26 13:51:10 2010
Shutting down archive processes
Mon Jul 26 13:51:15 2010
ARCH shutting down
ARCa: Archival stopped
Mon Jul 26 14:11:47 2010
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
*FAL[server]: DGID from FAL client not in Data Guard configuration*
*FAL[server]: FAL request for destination STUSTANDBY was:*
GAP - thread 1 sequence 10004-10017
DBID 2422302575 branch 670594799
Mon Jul 26 15:04:10 2010
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
*FAL[server]: DGID from FAL client not in Data Guard configuration*
*FAL[server]: FAL request for destination STUSTANDBY was:*
GAP - thread 1 sequence 10004-10017 DBID 2422302575 branch 670594799 -
Logs not applying on Standby Database
I am afraid I am back.
I now have a primary database and a standby database and logs are being shipped but not applied. Done some research and I have got to the point where in my alert log I find the following when I try to start MRP:
Fri Jun 29 15:03:40 2012
alter database recover managed standby database disconnect from session
Attempt to start background Managed Standby Recovery process (SAPDS)
Fri Jun 29 15:03:40 2012
MRP0 started with pid=29, OS id=23272
MRP0: Background Managed Standby Recovery process started (SAPDS)
started logmerger process
Fri Jun 29 15:03:45 2012
Managed Standby Recovery not using Real Time Apply
Read of datafile '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf' (fno 2) header failed with ORA-01206
Rereading datafile 2 header failed with ORA-01206
MRP0: Background Media Recovery terminated with error 1110
Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_pr00_23308.trc:
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01122: database file 2 failed verification check
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01206: file is not part of this database - wrong database id
Recovery Slave PR00 previously exited with exception 1110
Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_mrp0_23272.trc:
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01122: database file 2 failed verification check
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01206: file is not part of this database - wrong database id
MRP0: Background Media Recovery process shutdown (SAPDS)
Completed: alter database recover managed standby database disconnect from session
My question therefore is how can I get out of this and get my logs to apply on standby?Hello again;
Do you think if I tried to repeat the duplicate?
Yes I think you should do this.
Give me a few minutes and I will review my Word document and provide a step by step overview here as insurance.
I always cleanup the standby before trying another dup
OVERVIEW
Step 1 - Password file fro standby - Copy from primary and rename
Step 2 - Directory Structure on the remote server - Make sure noting is missing
Step 3 - Oracle Net Setup - entry for the CLONE in your TNSNAMES.ORA on both servers
Step 4 - SID_LIST_LISTENER addition ( assumes listener named LISTENER )
Step 5 - Timeouts set in listener.ora and sqlnet.ora Both Servers
Step 6 - Initialization Parameter File for the Auxiliary Instance
Step 7 - Set SID for Auxiliary Instance
Step 8 - Create an SPFILE for the new database by using a pfile with the INIT settings
Step 9 - Shutdown and startup nomount on new Spfile ( Auxiliary Instance )
Step 10 - Start RMAN and run the DUPLICATE Command
SID_LIST_LISTENER Example from mine
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
(PROGRAM = extproc)
(SID_DESC =
(global_dbname = CLONE.hostname)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
(sid_name = CLONE)
Prevent Timeouts
Add these to both servers
To listener.ora
INBOUND_CONNECT_TIMEOUT_ = 120
To sqlnet.ora
SQLNET.INBOUND_CONNECT_TIMEOUT = 120
Then stop and start the listener.
RMAN
$ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
Connect should return something like this
connected to target database: RECOVER9 (DBID=3806912436)
connected to auxiliary database: CLONE (not mounted)RMAN>duplicate target database for standby from active database NOFILENAMECHECK;
INIT Extras
To avoid ORA-09925 make sure the PFILE has audit_file_dest and core_dump_dest set
Best Regards
mseberg
Edited by: mseberg on Jun 29, 2012 11:12 AM -
When transporting multiproviders and cubes transport failed.
HI Experts,
When transporting cubes and multiproviders in a request the transport failed with return code 8.
The described below as:
Start of the after-import method RS_CUBE_AFTER_IMPORT for obje
Error/warning in dict. activator, detailed log > Detail
/BIC/L101078 (specify a primary key)
Table /BIC/L101078 could not be activated
Return code..............: 8
DDIC Object TABL /BIC/L101078 has not been activated
Error when activating InfoCube 101078
Error/warning in dict. activator, detailed log > Detail
/BIC/L101077 (specify a primary key)
Table /BIC/L101077 could not be activated
Return code..............: 8
DDIC Object TABL /BIC/L101077 has not been activated
Error when activating InfoCube 101077
Error/warning in dict. activator, detailed log > Detail
/BIC/L101078 (specify a primary key)
Table /BIC/L101078 could not be activated
Return code..............: 8
DDIC Object TABL /BIC/L101078 has not been activated
Error when activating InfoCube 101078
Error/warning in dict. activator, detailed log > Detail
/BIC/L101077 (specify a primary key)
Table /BIC/L101077 could not be activated
Return code..............: 8
DDIC Object TABL /BIC/L101077 has not been activated
Error when activating InfoCube 101077
Error/warning in dict. activator, detailed log > Detail
/BIC/L101078 (specify a primary key)
Table /BIC/L101078 could not be activated
Please let us know if anyone has come across similar kind of issue.
Regards,
Monalisa MohantyIssue seems to be with the aggregates maintained in the cube.
Is your aggregates were properly maintained in your Dev system when you have collected it in your transport?
Check the same and also use overwrite option when you are trying to import the transport in the target systems.
If the aggregates are properly maintained then check the import once again and see if that works fine with the overwrite mode. If not then you need to collect your objects again in a new transport.
Hope this helps.
Murali -
Hello Guys, I'm trying to figure out if my harddrive is going bad in my system. I'm seeing a lot of SCSI transport error messages in the /var/adm/messages file. This only happens when our backups are running at night. We back up all our servers through the firewall using veritas's netbackup. Can someone help me sift thought this information in the messages file and let me know what all this means. Thanks
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 Cmd (0x2d37890) dump for Target 0 Lun 0:
Dec 6 18:53:22 cp-hqc2 Cmd (0x2d37890) dump for Target 0 Lun 0:
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 cdb=[ 0x2a 0x0 0x0 0x60 0xba 0x74 0x0 0x0 0x2 0x0 ]
Dec 6 18:53:22 cp-hqc2 cdb=[ 0x2a 0x0 0x0 0x60 0xba 0x74 0x0 0x0 0x2 0x0 ]
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 pkt_flags=0x4000 pkt_statistics=0x60 pkt_state=0x7
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 pkt_scbp=0x0 cmd_flags=0x1860
Dec 6 18:53:22 cp-hqc2 pkt_flags=0x4000 pkt_statistics=0x60 pkt_state=0x7
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 Disconnected tagged cmd(s) (1) timeout for Target 0.0
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 genunix: [ID 408822 kern.info] NOTICE: glm0: fault detected in device; service still available
Dec 6 18:53:22 cp-hqc2 pkt_scbp=0x0 cmd_flags=0x1860
Dec 6 18:53:22 cp-hqc2 genunix: [ID 611667 kern.info] NOTICE: glm0: Disconnected tagged cmd(s) (1) timeout for Target 0.0
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 Disconnected tagged cmd(s) (1) timeout for Target 0.0
Dec 6 18:53:22 cp-hqc2 glm: [ID 401478 kern.warning] WARNING: ID[SUNWpd.glm.cmd_timeout.6018]
Dec 6 18:53:22 cp-hqc2 genunix: [ID 408822 kern.info] NOTICE: glm0: fault detected in device; service still available
Dec 6 18:53:22 cp-hqc2 genunix: [ID 611667 kern.info] NOTICE: glm0: Disconnected tagged cmd(s) (1) timeout for Target 0.0
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 glm: [ID 401478 kern.warning] WARNING: ID[SUNWpd.glm.cmd_timeout.6018]
Dec 6 18:53:22 cp-hqc2 got SCSI bus reset
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 genunix: [ID 408822 kern.info] NOTICE: glm0: fault detected in device; service still available
Dec 6 18:53:22 cp-hqc2 genunix: [ID 611667 kern.info] NOTICE: glm0: got SCSI bus reset
Dec 6 18:53:22 cp-hqc2 got SCSI bus reset
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3/sd@0,0 (sd0):
Dec 6 18:53:22 cp-hqc2 genunix: [ID 408822 kern.info] NOTICE: glm0: fault detected in device; service still available
Dec 6 18:53:22 cp-hqc2 genunix: [ID 611667 kern.info] NOTICE: glm0: got SCSI bus reset
Dec 6 18:53:22 cp-hqc2 SCSI transport failed: reason 'reset': retrying command
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3/sd@0,0 (sd0):
Dec 6 18:53:22 cp-hqc2 SCSI transport failed: reason 'reset': retrying command
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3/sd@0,0 (sd0):
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3/sd@0,0 (sd0):
Dec 6 18:53:22 cp-hqc2 SCSI transport failed: reason 'timeout': retrying command
Dec 6 18:53:22 cp-hqc2 SCSI transport failed: reason 'timeout': retrying commandHello, data is not being backed up locally. This server is our firewall. We have multiple dmz zones on our firewall. One of our dmz's host's the veritas master server which backs up other web servers in other dmz zones. When the backups kick off at night, these messages appear in the /var/adm/messages file. Does this mean the firewall cannot handle the load of traffic??
-
Failed to send email report ,The transport failed to connect to the server
HI i have to automate my report using sub
1.I have configured SMTP server in the configuration settings
2. I have created subscitption using my report,But i here i will found one error.
Please find the
failed to send email report ,The transport failed to connect to the server
and can u please help me out for this
when i check in the loge files it will show this error below
No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;I have change the settings as u suggested but still not able to send the mail .
its shows me the same error mesg
<Header>
<Product>Microsoft SQL Server Reporting Services Version 2009.0100.1600.01 ((KJ_RTM).100402-1539 )</Product>
<Locale>English (United States)</Locale>
<TimeZone>W. Europe Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVEREPORT\Reporting Services\Logfiles\ReportServerService__02_10_2015_03_44_06.log</Path>
<SystemName>WEGDACM1</SystemName>
<OSName>Microsoft Windows NT 6.1.7601 Service Pack 1</OSName>
<OSVersion>6.1.7601</OSVersion>
<ProcessID>10420</ProcessID>
<Virtualization>Hypervisor</Virtualization>
</Header>
rshost!rshost!28d0!02/10/2015-03:44:06:: i INFO: Currently registered url http://+:80/ReportServer_MSSQLSERVEREPORT/ on endpoint 2
rshost!rshost!28d0!02/10/2015-03:44:06:: e ERROR: Failed to register url=http://+:80/Reports/ for endpoint 3, error=b7.
rshost!rshost!28d0!02/10/2015-03:44:06:: w WARN: Endpoint 3 is enabled but no url is registered for vdir=/Reports, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVEREPORT\Reporting Services\ReportManager.
servicecontroller!DefaultDomain!28f4!02/10/2015-03:44:06:: e ERROR: Error creating HTTP endpoint. System.Runtime.InteropServices.COMException (0x800700B7): Cannot create a file when that file already exists. (Exception from HRESULT: 0x800700B7)
at Microsoft.ReportingServices.HostingInterfaces.IRsUnmanagedCallback.CreateHttpEndpoint(RsAppDomainType application, String[] urlPrefixes, Int32 cPrefixes, String[] hosts, Int32 cHosts, Boolean wildCardPresent, String virtualDirectory, String
filePath, Int32 authType, Int32 logonMethod, String authDomain, String authRealm, Boolean authPersist, Int32 extendedProtectionLevel, Int32 extendedProtectionScenario, Boolean enabled)
at Microsoft.ReportingServices.Library.ServiceAppDomainController.SetWebConfiguration(RunningApplication rsApplication, Boolean enabled, String folder)
rshost!rshost!28d0!02/10/2015-03:44:06:: i INFO: Endpoint 4 is disabled and no url is registered vdir=/ReportServer_MSSQLSERVEREPORT/ReportBuilder, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVEREPORT\Reporting Services\ReportServer\ReportBuilder.
rshost!rshost!28f4!02/10/2015-03:44:06:: i INFO: Derived memory configuration based on physical memory as 16776696 KB
servicecontroller!DefaultDomain!28f4!02/10/2015-03:44:06:: i INFO: Recycling the service from the default domain
rshost!rshost!28f4!02/10/2015-03:44:17:: i INFO: Application domain type WindowsService statistics: created: 10, unloaded: 10, failed: 0, timed out: 0.
appdomainmanager!DefaultDomain!28f4!02/10/2015-03:44:17:: i INFO: Appdomain:12 WindowsService_10 started.
library!WindowsService_10!28f4!02/10/2015-03:44:17:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. ;
servicecontroller!WindowsService_10!28f4!02/10/2015-03:44:17:: e ERROR: Error initializing configuration from the database: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration
error.
resourceutilities!WindowsService_10!28f4!02/10/2015-03:44:18:: i INFO: Reporting Services starting SKU: Enterprise
servicecontroller!WindowsService_9!28f4!02/10/2015-03:44:18:: i INFO: Service controller exiting.
appdomainmanager!DefaultDomain!28f4!02/10/2015-03:44:18:: i INFO: Appdomain:11 unregistered.
appdomainmanager!DefaultDomain!28f4!02/10/2015-03:44:18:: i INFO: Appdomain:11 WindowsService_9 unloading.
appdomainmanager!DefaultDomain!e24!02/10/2015-03:44:18:: i INFO: AppDomain:11 0 pending unload(s)
library!WindowsService_10!19f0!02/10/2015-03:44:18:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. ;
library!WindowsService_10!19f0!02/10/2015-03:44:18:: e ERROR: ServiceStartThread: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration
error.
library!WindowsService_10!19f0!02/10/2015-03:44:18:: e ERROR: ServiceStartThread: Attempting to start service again...
library!DefaultDomain!1ca8!02/10/2015-10:55:23:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. ;
This is my Logfile can u pls go through it and resolve my issue. -
Problem discovering host targets - Routing error
Hi,
I am trying to discover targets using the auto discovery, and I get an error related to the nmap command.
I tried with a privileged user as well as the root user, but both ways it fails with the error below:
<?xml version="1.0"?>
<?xml-stylesheet href="file:///scratch/agentHome/agent_inst/discovery/nmap/share/nmap/nmap.xsl" type="text/xsl"?>
<!-- Nmap 6.00 scan initiated Mon May 6 16:30:40 2013 as: /scratch/agentHome/agent_inst/discovery/nmap/bin/nmap -sV --max-os-tries 1 --min-hostgroup 64 --open -p 80,443,389,636,1433,1434,3389,3306,4443,7443,7777,3938,1158,1521,8080,66,400,54321,54322,8899,7001,7003,5155,1156,22,23 -O -oX - --exclude 10.240.218.10 --datadir /scratch/agentHome/agent_inst/discovery/nmap/share/nmap -T5 10.240.218.11-24 -->
<nmaprun scanner="nmap" args="/scratch/agentHome/agent_inst/discovery/nmap/bin/nmap -sV --max-os-tries 1 --min-hostgroup 64 --open -p 80,443,389,636,1433,1434,3389,3306,4443,7443,7777,3938,1158,1521,8080,66,400,54321,54322,8899,7001,7003,5155,1156,22,23 -O -oX - --exclude 10.240.218.10 --datadir /scratch/agentHome/agent_inst/discovery/nmap/share/nmap -T5 10.240.218.11-24" start="1367872240" startstr="Mon May 6 16:30:40 2013" version="6.00" xmloutputversion="1.03">
<scaninfo type="syn" protocol="tcp" numservices="26" services="22-23,66,80,389,400,443,636,1156,1158,1433-1434,1521,3306,3389,3938,4443,5155,7001,7003,7443,7777,8080,8899,54321-54322"/>
<verbose level="0"/>
<debugging level="0"/>
route_dst_generic: Failed to obtain system routes: getsysroutes_dnet: sysroutes_dnet_find_interfaces() failed
Any idea, what may be wrong?Ok. Just confirming this is a vanilla linux install and hardware.
Network discover (Nmap) must be run as root user. And in EM that means you must configure privilege delegation and sudo/pbrun on the host running nmap. You mentioned you tried privilege delegation before so I assume you have this configured correctly and tested.
If you still have issue, then please open an SR as we will need the logs and more details of the host to troubleshoot.
Dave -
Proxy Log On failed(Error Code 12154)
Hello There!
Can someone P'se help on this
Installation
WIN2K-Pro
Oracle8iEE-1.7..
Oracle9iAS
Two different Oracle homes
Problem
I am trying to test for the first time my portal but i am receiving the following error messages
1)when I type in <http://mysever/pls/dad> this is the result:
Proxy log On failed.
Please verify that you have specified correct connectivity information i.e.username, password & connect-string in the Database Access Descriptor
Error-Code:12640
Error TimeStamp:Mon, 06 Aug 2001 04:25:15 GMT
Database Log In Failed
TNS is unable to connect to destination. Invalid TNS address supplied or destination is not listening. This error can also occur because of underlying network transport problems.
Verify that the TNS name in the connectstring entry of the DAD for this URL is valid and the database listener is running.
2)Also when I try this <http://myserver/pls/admin/gateway.htm>the result is as follows:
Mon, 06 Aug 2001 20:01:28 GMT
No DAD configuration Found
DAD name:
PROCEDURE : gateway.htm
URL : http://nt2kserver.learning.local:80/pls/admin/gateway.htm
PARAMETERS :
===========
ENVIRONMENT:
============
PLSQL_GATEWAY=WebDb
GATEWAY_IVERSION=2
SERVER_SOFTWARE=Oracle HTTP Server Powered by Apache/1.3.12 (Win32) ApacheJServ/1.1 mod_ssl/2.6.4 OpenSSL/0.9.5a mod_perl/1.24
GATEWAY_INTERFACE=CGI/1.1
SERVER_PORT=80
SERVER_NAME=nt2kserver.learning.local
REQUEST_METHOD=GET
QUERY_STRING=
PATH_INFO=/admin/gateway.htm
SCRIPT_NAME=/pls
REMOTE_HOST=
REMOTE_ADDR=127.0.0.1
SERVER_PROTOCOL=HTTP/1.1
REQUEST_PROTOCOL=HTTP
REMOTE_USER=
HTTP_CONTENT_LENGTH=
HTTP_CONTENT_TYPE=
HTTP_USER_AGENT=Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
HTTP_HOST=nt2kserver.learning.local
HTTP_ACCEPT=*/*
HTTP_ACCEPT_ENCODING=gzip, deflate
HTTP_ACCEPT_LANGUAGE=en-us
HTTP_ACCEPT_CHARSET=
HTTP_COOKIE=
Authorization=
HTTP_IF_MODIFIED_SINCE=
HTTP_REFERER=Hello Teijo
sorry about this, but I have checked on both of my two standalone servers(Running similar softwares and settings(host name...etc) independently) I can't see any service registerd by APACHE LISTENER.The only listener service available is for ORACLE8i under the oracle8iHome.
The only running service under the 9iASHome is HTTPServer.During both installations I didn't encounter any problems,everything ended succefully.Can you p'se let me know if this sounds Ok to you?
Hashim
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Teijo Lallukka ([email protected]):
This looks like a tnsnames.ora issue. I copied a reply from a similar post:
Since you have multiple Oracle homes, you are probably looking at the wrong tnsnames.ora. The reason why SQL*Plus is working is because it is being picked up from an Oracle Home where the correct tnsnames.ora resides. Here is a quick way to confirm this
- Stop the Apache Listener service
- Open a "Console prompt window"
- Go to $IAS_HOME/Apache/Apache
- Set TNS_ADMIN=Directory_with_correct_tnsnames.ora
- Issue "tnsping your_dbalias_name" to verify that you can ping the database. If this does not work, then your tnsnames.ora is incorrect
- If it works, startup Apache by issuing "start Apache -k start"
- Try connecting to Portal thru your browser
- This should work.
- Post a reply if this does not work<HR></BLOCKQUOTE>
null -
Will RMAN delete archive log files on a Standby server?
Environment:
Oracle 11.2.0.3 EE on Solaris 10.5
I am currently NOT using an RMAN repository (coming soon).
I have a Primary database sending log files to a Standby.
My Retention Policy is set to 'RECOVERY WINDOW OF 8 DAYS'.
Question: Will RMAN delete the archive log files on the Standby server after they become obsolete based on the Retention Policy or do I need to remove them manually via O/S command?
Does the fact that I'm NOT using an RMAN Repository at the moment make a difference?
Couldn't find the answer in the docs.
Thanks very much!!
-garyHello again Gary;
Sorry for the delay.
Why is what you suggested better?
No, its not better, but I prefer to manage the archive. This method works, period.
Does that fact (running a backup every 4 hours) make my archivelog deletion policy irrelevant?
No. The policy is important.
Having the Primary set to :
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBYBut set to "NONE" on the Standby.
Means the worst thing that can happen is RMAN will bark when you try to delete something. ( this is a good thing )
How do I prevent the archive backup process from backing up an archive log file before it gets shipped to the standby?
Should be a non-issue, the archive does not move, the REDO is transported and applied. There's SQL to monitor both ( Transport and Apply )
For Data Guard I would consider getting a copy of
"Oracle Data Guard 11g Handbook" - Larry Carpenter (AKA Dr. Paranoid ) ISBN 978-0-07-162111-2
Best Oracle book I've read in 10 years. Covers a ton of ground clearly.
Also Data Guard forum here :
Data Guard
Best Regards
mseberg
Edited by: mseberg on Apr 10, 2012 4:39 PM
Maybe you are looking for
-
Error in Running REPORT in JSP format
Dear Fellows, I have created a report in JSP format and deployed on the local web server. I try to run the report through this URL. "http://dw_hit4:7778/emprev_Zeeshan.jsp?server=repsrv&userid=hr/hr@sbpdw" When i access this URL i get this error "Err
-
I just bought an IPhone 4s and plugged it into my Toshiba Windows 7 (64 bit) OS and it failed to recognize the phone. I checked in the tech community and discovered that I need to remove all the software assoicated with the phone and start over....I
-
Photo Merge not working in CS4
I use Lightroom 2.3 on a MacBook Pro. When I go to "edit in" and choose "merge to panorama in photoshop", photoshop opens and the "photomerge window" comes up. I select auto merge for the 3 selected photos and click ok. Then, nothing happens. No n
-
1. Does anybody know who is sysdba and sysdba's name and password? I only know you can login this way: sqlplus system/pwd as sysdba, does sysdba is a seperate user from system, sys or internal? they are required in Table 2-2 of Installation guide. 2.
-
Windows 7 Pro 64 Bit 16GB Ram 500GB Hard Drive Intel Quad Core CPU When I click the install for InDesign CC the software is slowly downloaded, much slower than any of the other apps. It goes all the way through to Extracting and then it says "Waiti