No UWL Logs are writing
Hi,
have anybody an idea how I could change the configuration for the uwl logs.
Normally the logs should be in the directory /usr/sap/<SID> JCXX/j2ee/cluster/server0/log/applications/sap.pom/uwl
But in both server directories (2 have server0 und server1) are the uwl logs old.
ls -tlr
total 46344
-rw-rr 1 pepadm sapsys 10000391 Aug 6 2007 uwl_defaultLog.0.log
-rw-rr 1 pepadm sapsys 10000417 Sep 5 2007 uwl_defaultLog.1.log
-rw-rr 1 pepadm sapsys 3697415 Sep 1 11:51 uwl_defaultLog.2.log
I change the loglevel in der Visualadmin from error to all but nothings happens.
The following steps will lead you to activate UWL log.
1) Open the services tree in Visual Administrator.
2) Go to u201CLog Configuratoru201D service.
3) On the u201CRuntimeu201D tab, in the right-hand pane, select the u201CLocationsu201D sub-tab. Look at the u201CLog Controllersu201D tree.
4) Expand to: ROOT LOCATION/com/sap/netweaver/bc/uwl.
5) Click u201Cuwlu201D.
6) Change the severity to level u201CAllu201D.
7) Click the u201CCopy severity to subtreeu201D button to update the change to all subcomponents.
8 ) Click the u201CApplyu201D button to save changes.
The UWL log files are located in the following directory: /usr/sap//JC/j2ee/cluster/server/log/applications/sap.com/uwl
Did anybody has an idea?
Greeting
Thomas
Hi,
It is advisable to reset the severity level back to default after reproducing the issue as the increased information been logged in the default trace files will fill them up and may lead to performance issues. You should check the following wiki which contains helpful information on logging levels etc
http://wiki.scn.sap.com/wiki/display/ASJAVA/Log+and+Trace+configuration+on+NW+7.1
Regards,
Lorraine
Similar Messages
-
Why is the Log Area size much smaller than the log volume
I have been following up on an Early Watch report that has been generated for our production SCM 5.0 system running liveCache 7.6.02 Build 14. The alert says "The LOG volumes size in your system is too small. Recommendation: Configure LOG Volumes to at least 2 GB". There are two interesting things about this.
1) I have spent the last couple of days reading all the OSS Notes, and MaxDB documentation I could find, and this does not seem to be documented as a recommendation anywhere. Does this seem like a realistic recommendation without taking into account the level of change actifity?
2) There is a single log volume allocated with size 2,097,160 KB. In production LC10 and DBMGUI report this to be correct size under volume details, but only list the total log area size as 1,706,328 (81% of the volume size). We have a non-production environment with exactly the same size log volume, but it reports that the log area size is 2,032,008 KB (97% of the volume). What leads to these different amounts of wasted space, and is there any way of getting the database to start using it?
Thanks,
MarkHi Natalia,
I did read 869267, several times. It does not answer my questions which is why I posted here.
DBMGUI version = 7.6.00.25
DBMCLI commands for PL1 (Production)
> xinstinfo PL1
IndepData : /sapdb/data
IndepPrograms : /sapdb/programs
InstallationPath : /sapdb/PL1/db
Kernelversion : KERNEL 7.6.02 BUILD 014-123-152-175
Rundirectory : /sapdb/data/wrk/PL1
> dbmcli -d PL1 -u control,control
dbmcli on PL1>db_state
OK
State
ONLINE
dbmcli on PL1>info log
OK
END
Name | Value
Log Mirrored = NO
Log Writing = ON
Log Automatic Overwrite = OFF
Max. Size (KB) = 1706328
Backup Segment Size (KB) = 699048
Used Size (KB) = 104640
Used Size (%) = 6
Not Saved (KB) = 104640
Not Saved (%) = 6
Log Since Last Data Backup (KB) = 0
Savepoints = 5210
Checkpoints = 0
Physical Reads = 2469115
Physical Writes = 15655616
Queue Size (KB) = 48000
Queue Overflows = 646
Group Commits = 98205
Waits for Logwriter = 10957511
Max. Waits = 10
Average Waits = 0
OMS Log Used Pages = 0
OMS Min. Free Pages = 0
dbmcli on PL1>param_getvolsall
OK
LOG_MIRRORED NO
MAXLOGVOLUMES 2
MAXDATAVOLUMES 14
LOG_VOLUME_NAME_001 262145 F /sapdb/PL1/saplog/DISKL001
DATA_VOLUME_NAME_0001 524289 F /sapdb/PL1/sapdata/DISKD0001
DATA_VOLUME_NAME_0002 524289 F /sapdb/PL1/sapdata/DISKD0002
DATA_VOLUME_NAME_0003 524289 F /sapdb/PL1/sapdata/DISKD0003
DATA_VOLUME_NAME_0004 524289 F /sapdb/PL1/sapdata/DISKD0004
DATA_VOLUME_NAME_0005 524289 F /sapdb/PL1/sapdata/DISKD0005
DATA_VOLUME_NAME_0006 524289 F /sapdb/PL1/sapdata/DISKD0006
DATA_VOLUME_NAME_0007 524289 F /sapdb/PL1/sapdata/DISKD0007
DATA_VOLUME_NAME_0008 524289 F /sapdb/PL1/sapdata/DISKD0008
DATA_VOLUME_NAME_0009 1048577 F /sapdb/PL1/sapdata/DISKD0009
DATA_VOLUME_NAME_0010 1048577 F /sapdb/PL1/sapdata/DISKD0010
DATA_VOLUME_NAME_0011 1048577 F /sapdb/PL1/sapdata/DISKD0011
DATA_VOLUME_NAME_0012 1048577 F /sapdb/PL1/sapdata/DISKD0012
dbmcli on PL1>param_directget MAXCPU
OK
MAXCPU 12
dbmcli on PL1>param_directget MAX_LOG_QUEUE_COUNT
OK
MAX_LOG_QUEUE_COUNT 0
dbmcli on PL1>param_directget LOG_IO_QUEUE
OK
LOG_IO_QUEUE 6000
> xinstinfo SL1
IndepData : /sapdb/data
IndepPrograms : /sapdb/programs
InstallationPath : /sapdb/SL1/db
Kernelversion : KERNEL 7.6.02 BUILD 014-123-152-175
Rundirectory : /sapdb/data/wrk/SL1
dbmcli on SL1>db_state
OK
State
ONLINE
dbmcli on SL1>info log
OK
END
Name | Value
Log Mirrored = NO
Log Writing = ON
Log Automatic Overwrite = OFF
Max. Size (KB) = 2032008
Backup Segment Size (KB) = 699048
Used Size (KB) = 3824
Used Size (%) = 0
Not Saved (KB) = 3824
Not Saved (%) = 0
Log Since Last Data Backup (KB) = 0
Savepoints = 1256
Checkpoints = 0
Physical Reads = 2178269
Physical Writes = 4969914
Queue Size (KB) = 16000
Queue Overflows = 21201
Group Commits = 643
Waits for Logwriter = 751336
Max. Waits = 4
Average Waits = 0
OMS Log Used Pages = 0
OMS Min. Free Pages = 0
dbmcli on SL1>param_getvolsall
OK
LOG_MIRRORED NO
MAXLOGVOLUMES 2
MAXDATAVOLUMES 10
LOG_VOLUME_NAME_001 262145 F /sapdb/SL1/saplog/DISKL001
DATA_VOLUME_NAME_0001 262145 F /sapdb/SL1/sapdata1/DISKD0001
DATA_VOLUME_NAME_0002 262145 F /sapdb/SL1/sapdata2/DISKD0002
DATA_VOLUME_NAME_0003 1048577 F /sapdb/SL1/sapdata3/DISKD0003
DATA_VOLUME_NAME_0004 1048577 F /sapdb/SL1/sapdata4/DISKD0004
DATA_VOLUME_NAME_0005 783501 F /sapdb/SL1/sapdata1/DISKD0005
DATA_VOLUME_NAME_0006 783501 F /sapdb/SL1/sapdata2/DISKD0006
dbmcli on SL1>param_directget MAXCPU
OK
MAXCPU 4
dbmcli on SL1>param_directget MAX_LOG_QUEUE_COUNT
OK
MAX_LOG_QUEUE_COUNT 0
dbmcli on SL1>param_directget LOG_IO_QUEUE
OK
LOG_IO_QUEUE 2000
Thanks for the explaination of the reserved space for the Log Queue pages. This does explain why there is the difference between the two. I think we probably have our log segment size too large. As you can see we do get occasional log queue overflows. Do you suggest we increase the size of our log IO queue higher, and allocate more log volume space to compensate?
select * from SYSINFO.LOGSTATISTICS (on PL1)
1706328;334176;19;334176;19;1879;20305192;64109066;7806480;182151514;12;48000
DBMGUI Log Area Usage
Total Size: 2048.01 MB
Free Log Area: 1330.38 MB
Used Log Area: 335.96 MB
Unsaved Log Area: 335.96
Log since Last Data Backup: 0.00 MB
Thanks,
Mark -
Logs are not getting applied in the standby database
Hello,
I have created a physical standby database and in it the logs are not getting applied..
following is an extract of the standby alert log
Wed Sep 05 07:53:59 2012
Media Recovery Log /u01/oracle/oradata/ABC/archives/1_37638_765704228.arc
Error opening /u01/oracle/oradata/ABC/archives/1_37638_765704228.arc
Attempting refetch
Media Recovery Waiting for thread 1 sequence 37638
Fetching gap sequence in thread 1, gap sequence 37638-37643
Wed Sep 05 07:53:59 2012
RFS[46]: Assigned to RFS process 3081
RFS[46]: Allowing overwrite of partial archivelog for thread 1 sequence 37638
RFS[46]: Opened log for thread 1 sequence *37638* dbid 1723205832 branch 765704228
Wed Sep 05 07:55:34 2012
RFS[42]: Possible network disconnect with primary database
However, the archived files are getting copied to the standby server.
I tried registering and recovering the logs but it also failed..
Follows some of the information,
Primary
Oralce 11R2 EE
SQL> select max(sequence#) from v$log where archived='YES';
MAX(SEQUENCE#)
37668
SQL> select DEST_NAME, RECOVERY_MODE,DESTINATION,ARCHIVED_SEQ#,APPLIED_SEQ#, SYNCHRONIZATION_STATUS,SYNCHRONIZED,GAP_STATUS from v$archive_dest_status where DEST_NAME = 'LOG_ARCHIVE_DEST_3';
DEST_NAME RECOVERY_MODE DESTINATION ARCHIVED_SEQ# APPLIED_SEQ# SYNCHRONIZATION_STATUS SYNCHRONIZED GAP_STATUS
LOG_ARCHIVE_DEST_3 MANAGED REAL TIME APPLY ABC 37356 0 CHECK CONFIGURATION NO RESOLVABLE GAP
Standby
Oralce 11R2 EE
SQL> select max(sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
37637
SQL> select * from v$archive_gap;
no rows selected
SQL> select open_mode, database_role from v$database;
OPEN_MODE DATABASE_ROLE
READ ONLY WITH APPLY PHYSICAL STANDBY
Please help me to troubleshoot this and get the standby in sync..
Thanks a lot..the results are as follows..
SQL> select process, status, group#, thread#, sequence# from v$managed_standby order by process, group#, thread#, sequence#;
PROCESS STATUS GROUP# THREAD# SEQUENCE#
ARCH CLOSING 1 1 37644
ARCH CLOSING 1 1 37659
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
MRP0 WAIT_FOR_GAP N/A 1 37638
RFS IDLE N/A 0 0
RFS IDLE N/A 0 0
RFS IDLE N/A 0 0
RFS RECEIVING N/A 1 37638
RFS RECEIVING N/A 1 37639
RFS RECEIVING N/A 1 37640
RFS RECEIVING N/A 1 37641
RFS RECEIVING N/A 1 37642
RFS RECEIVING N/A 1 37655
RFS RECEIVING N/A 1 37673
RFS RECEIVING N/A 1 37675
42 rows selected.
SQL>
SQL> select name,value, time_computed from v$dataguard_stats;
NAME VALUE TIME_COMPUTED
transport lag +00 02:44:33 09/05/2012 09:25:58
apply lag +00 03:14:30 09/05/2012 09:25:58
apply finish time +00 00:01:09.974 09/05/2012 09:25:58
estimated startup time 12 09/05/2012 09:25:58
SQL> select timestamp , facility, dest_id, message_num, error_code, message from v$dataguard_status order by timestamp
TIMESTAMP FACILITY DEST_ID MESSAGE_NUM ERROR_CODE MESSAGE
05-SEP-12 Remote File Server 0 60 0 RFS[13]: Assigned to RFS process 2792
05-SEP-12 Remote File Server 0 59 0 RFS[12]: Assigned to RFS process 2790
05-SEP-12 Log Apply Services 0 61 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 62 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 63 0 Managed Standby Recovery Canceled
05-SEP-12 Log Apply Services 0 64 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 65 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 66 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 67 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 68 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 69 0 RFS[5]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 70 0 RFS[6]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 71 0 RFS[14]: Assigned to RFS process 2829
05-SEP-12 Remote File Server 0 72 0 RFS[15]: Assigned to RFS process 2831
05-SEP-12 Network Services 0 73 0 RFS[9]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 74 0 RFS[16]: Assigned to RFS process 2833
05-SEP-12 Network Services 0 75 0 RFS[1]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 76 0 RFS[17]: Assigned to RFS process 2837
05-SEP-12 Network Services 0 77 0 RFS[3]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 78 0 RFS[2]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 79 0 RFS[7]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 80 0 RFS[18]: Assigned to RFS process 2848
05-SEP-12 Network Services 0 81 0 RFS[16]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 82 0 RFS[19]: Assigned to RFS process 2886
05-SEP-12 Network Services 0 83 0 RFS[19]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 84 0 RFS[20]: Assigned to RFS process 2894
05-SEP-12 Log Apply Services 0 85 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 86 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 87 0 Managed Standby Recovery Canceled
05-SEP-12 Remote File Server 0 89 0 RFS[22]: Assigned to RFS process 2900
05-SEP-12 Remote File Server 0 88 0 RFS[21]: Assigned to RFS process 2898
05-SEP-12 Remote File Server 0 90 0 RFS[23]: Assigned to RFS process 2902
05-SEP-12 Remote File Server 0 91 0 Primary database is in MAXIMUM PERFORMANCE mode
05-SEP-12 Remote File Server 0 92 0 RFS[24]: Assigned to RFS process 2904
05-SEP-12 Remote File Server 0 93 0 RFS[25]: Assigned to RFS process 2906
05-SEP-12 Log Apply Services 0 94 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 95 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 96 0 Managed Standby Recovery starting Real Time Apply
05-SEP-12 Log Apply Services 0 97 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Log Transport Services 0 98 0 ARCa: Beginning to archive thread 1 sequence 37644 (7911979302-7912040568)
05-SEP-12 Log Transport Services 0 99 0 ARCa: Completed archiving thread 1 sequence 37644 (0-0)
05-SEP-12 Network Services 0 100 0 RFS[8]: Possible network disconnect with primary database
05-SEP-12 Log Apply Services 0 101 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 102 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 103 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 104 0 Managed Standby Recovery Canceled
05-SEP-12 Network Services 0 105 0 RFS[20]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 106 0 RFS[26]: Assigned to RFS process 2930
05-SEP-12 Network Services 0 107 0 RFS[24]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 108 0 RFS[27]: Assigned to RFS process 2938
05-SEP-12 Network Services 0 109 0 RFS[14]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 110 0 RFS[28]: Assigned to RFS process 2942
05-SEP-12 Network Services 0 111 0 RFS[15]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 112 0 RFS[29]: Assigned to RFS process 2986
05-SEP-12 Network Services 0 113 0 RFS[17]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 114 0 RFS[30]: Assigned to RFS process 2988
05-SEP-12 Log Apply Services 0 115 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 116 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 117 0 Managed Standby Recovery starting Real Time Apply
05-SEP-12 Log Apply Services 0 118 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 119 0 RFS[18]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 120 0 RFS[31]: Assigned to RFS process 3003
05-SEP-12 Network Services 0 121 0 RFS[26]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 122 0 RFS[32]: Assigned to RFS process 3005
05-SEP-12 Network Services 0 123 0 RFS[27]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 124 0 RFS[33]: Assigned to RFS process 3009
05-SEP-12 Remote File Server 0 125 0 RFS[34]: Assigned to RFS process 3012
05-SEP-12 Log Apply Services 0 127 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 126 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 128 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 129 0 Managed Standby Recovery Canceled
05-SEP-12 Network Services 0 130 0 RFS[32]: Possible network disconnect with primary database
05-SEP-12 Log Apply Services 0 131 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 132 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 133 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 134 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 135 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 136 0 RFS[33]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 137 0 RFS[35]: Assigned to RFS process 3033
05-SEP-12 Log Apply Services 0 138 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 139 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 140 0 Managed Standby Recovery Canceled
05-SEP-12 Remote File Server 0 141 0 RFS[36]: Assigned to RFS process 3047
05-SEP-12 Log Apply Services 0 142 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 143 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 144 0 Managed Standby Recovery starting Real Time Apply
05-SEP-12 Log Apply Services 0 145 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 146 0 RFS[35]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 147 0 RFS[37]: Assigned to RFS process 3061
05-SEP-12 Network Services 0 148 0 RFS[36]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 149 0 RFS[38]: Assigned to RFS process 3063
05-SEP-12 Remote File Server 0 150 0 RFS[39]: Assigned to RFS process 3065
05-SEP-12 Network Services 0 151 0 RFS[25]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 152 0 RFS[21]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 153 0 Archivelog record exists, but no file is found
05-SEP-12 Remote File Server 0 154 0 RFS[40]: Assigned to RFS process 3067
05-SEP-12 Network Services 0 155 0 RFS[37]: Possible network disconnect with primary database -
Restored standby database from primary; now no logs are shipped
Hi
We recently had a major network/SAN issue and had to restore our standby database from a backup of the primary. To do this, we restored the database to the standby, created a standby controlfile on the primary, copied this across to the control file locations and started in standby recover and applied the logs manually/registered to get it back up to speed.
However, no new logs are being shipped across from the primary.
Have we missed a step somewhere?
One thing we've noticed is that there is no RFS process running on the standby:
SQL> SELECT PROCESS, CLIENT_PROCESS, SEQUENCE#, STATUS FROM V$MANAGED_STANDBY;
PROCESS CLIENT_P SEQUENCE# STATUS
ARCH ARCH 0 CONNECTED
ARCH ARCH 0 CONNECTED
MRP0 N/A 100057 WAIT_FOR_LOG
How do we start this? Or will it only show if the arc1 process on the primary is sending files?
The arc1 process is showing at OS level on the primary but I'm wondering if its faulty somehow?
There are NO errors in the alert logs in the primary or the standby. There's not even the normal FAL gap sequence type error - in the standby it's just saying 'waiting for log' and a number from ages ago. It's like the primary isn't even talking to the standby. The listener is up and running ok though...
What else can we check/do?
If we manually copy across files and do an 'alter database register' then they are applied to the standby without issue; there's just no automatic log shipping going on...
Thanks
RossHi all
Many thanks for all the responses.
The database is 10.2.0.2.0, on AIX 6.
I believe the password files are ok; we've had issues previously and this is always flagged in the alert log on the primary - not the case here.
Not set to DEFER on primary; log_archive_dest_2 is set to service="STBY_PHP" optional delay=720 reopen=30 and log_archive_dest_state_2 is set to ENABLE.
I ran those troubleshooting scripts, info from standby:
SQL> @troubleshoot
NAME DISPLAY_VALUE
db_file_name_convert
db_name PHP
db_unique_name PHP
dg_broker_config_file1 /oracle/PHP/102_64/dbs/dr1PHP.dat
dg_broker_config_file2 /oracle/PHP/102_64/dbs/dr2PHP.dat
dg_broker_start FALSE
fal_client STBY_PHP
fal_server PHP
local_listener
log_archive_config
log_archive_dest_2 service=STBY_PHP optional delay=30 reopen=30
log_archive_dest_state_2 DEFER
log_archive_max_processes 2
log_file_name_convert
remote_login_passwordfile EXCLUSIVE
standby_archive_dest /oracle/PHP/oraarch/PHParch
standby_file_management AUTO
NAME DB_UNIQUE_NAME PROTECTION_MODE DATABASE_R OPEN_MODE
PHP PHP MAXIMUM PERFORM PHYSICAL S MOUNTED
ANCE TANDBY
THREAD# MAX(SEQUENCE#)
1 100149
PROCESS STATUS THREAD# SEQUENCE#
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
MRP0 WAIT_FOR_LOG 1 100150
NAME VALUE UNIT TIME_COMPUTED
apply finish time day(2) to second(1) interval
apply lag day(2) to second(0) interval
estimated startup time 8 second
standby has been open N
transport lag day(2) to second(0) interval
NAME Size MB Used MB
0 0
On the primary, the script has froze!! How long should it take? Got as far as this:
SQL> @troubleshoot
NAME DISPLAY_VALUE
db_file_name_convert
db_name PHP
db_unique_name PHP
dg_broker_config_file1 /oracle/PHP/102_64/dbs/dr1PHP.dat
dg_broker_config_file2 /oracle/PHP/102_64/dbs/dr2PHP.dat
dg_broker_start FALSE
fal_client STBY_R1P
fal_server R1P
local_listener
log_archive_config
log_archive_dest_2 service="STBY_PHP" optional delay=720 reopen=30
log_archive_dest_state_2 ENABLE
log_archive_max_processes 2
log_file_name_convert
remote_login_passwordfile EXCLUSIVE
standby_archive_dest /oracle/PHP/oraarch/PHParch
standby_file_management AUTO
NAME DB_UNIQUE_NAME PROTECTION_MODE DATABASE_R OPEN_MODE SWITCHOVER_STATUS
PHP PHP MAXIMUM PERFORMANCE PRIMARY READ WRITE SESSIONS ACTIVE
THREAD# MAX(SEQUENCE#)
1 100206
NOW - before you say it - :) - yes, I'm aware that fal_client as STBY_R1P and fal_server as R1P are incorrect - should be PHP - but it looks like it's always been this way! Well, as least for the last 4 years where it's worked fine, as I found an old SP file and it still has R1P set in there...?!?
Any ideas?
Ross -
LiveCach problem with log Area
In LiveCache monitoring I can see the message: "Log area full - back up log!"
I use the RSLVCBACKUP interactively with the parameter "Complete Data Backup". After running an error is displayed:
"Failed to determine media (Database connection: LCA)
Message no. LVC505 ".
Is it true I'm doing taking such measures for Log Area Backup. And if all true, how can I avoid mistakes LVC505?Sounds like you did not configure a backup medium for your liveCache.
To get rid of the log-full situation you may just use DBMGUI now and take a full backup and activate autolog backup afterwards.
Once this is done you may check what's wrong with your report usage.
regards,
Lars -
Archive logs are missing in hot backup
Hi All,
We are using the following commands to take hot backup of our database. Hot backup is fired by "backup" user on Linux system.
=======================
rman target / nocatalog <<EOF
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '$backup_dir/$date/%F';
run {
allocate channel oem_backup_disk1 type disk format '$backup_dir/$date/%U';
#--Switch archive logs for all threads
sql 'alter system archive log current';
backup as COMPRESSED BACKUPSET database include current controlfile;
#--Switch archive logs for all threads
sql 'alter system archive log current';
#--Backup Archive logs and delete what we've backedup
backup as COMPRESSED BACKUPSET archivelog all not backed up delete all input;
release channel oem_backup_disk1;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
exit
EOF
=======================
Due to which after command (used 2 times) "sql 'alter system archive log current';" I see the following lines in alert log 2 times. Because of this all the online logs are not getting archived (Missing 2 logs per day), the backup taken is unusable when restoring. I am worried about this. I there any to avoid this situation.
=======================
Errors in file /u01/oracle/admin/rac/udump/rac1_ora_3546.trc:
ORA-19504: failed to create file "+DATA/rac/1_32309_632680691.dbf"
ORA-17502: ksfdcre:4 Failed to create file +DATA/rac/1_32309_632680691.dbf
ORA-15055: unable to connect to ASM instance
ORA-01031: insufficient privileges
=======================
Regards,
Kunal.All thanks you for help, pleas find additional information. I goth the following error as log sequence was missing. Everyday during hotbackup, there are 2 missing archive logs, which makes our backup inconsistent and useless.
archive log filename=/mnt/xtra-backup/ora_archivelogs/1_32531_632680691.dbf thread=1 sequence=32531
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28768_632680691.dbf thread=2 sequence=28768
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28769_632680691.dbf thread=2 sequence=28769
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28770_632680691.dbf thread=2 sequence=28770
archive log filename=/mnt/xtra-backup/ora_archivelogs/1_32532_632680691.dbf thread=1 sequence=32532
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28771_632680691.dbf thread=2 sequence=28771
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf thread=2 sequence=28772
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf thread=2 sequence=28773
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/13/2012 04:22:56
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf'
ORA-00310: archived log contains sequence 28772; sequence 28773 required
ORA-00334: archived log: '/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf'
Let me try the susggestions provided above. -
Anyone have any idea why some logs are not produced even though all jobs are set to the default class with logging ?
I have not given any details so far, this is just a general enquiry to see if any one else has experienced this.Are you talking about missing entries in USER_SCHEDULER_JOB_RUN_DETAILS after jobs have run?
I had a problem with that after upgrading to 11g, but can't remember how I fixed it. May have been something to do with the LOGGING_LEVEL or LOG_HISTORY on the Job or Job Class... -
Our production server logs are creating frequently and system is down simultaneously.
Any suggestionsHi,
you could also consider using infinite logging, (as of DB2 v 8). This means is possible to support environments with large jobs that require more log space than you would normally allocate to the primary logs. For this, the database configuration parameter LOGSECOND must be set to -1
Please refer to SAP note 1493587
regards, Javier -
How to determine which archive logs are needed in flashback.
Hi,
Let's assume I have archive logs 1,2,3,4, then a "backup database plus archivelogs" in RMAN, and then archive logs 5+6. If I want to flashback my database to a point immediately after the backup, how do I determine which archive logs are needed?
I would assume I'd only need archive logs 5 and/or 6 since I did a full backup plus archivelogs and the database would have been checkpointed at that time. I'd also assume archive logs 1,2,3,4 would be obsolete as they would have been flushed to the datafiles in the checkpoint.
Are my assumptions correct? If not what queries can I run to determine what files are needed for a flashback using the latest checkpointed datafiles?
Thanks.Thanks for the explanation, let me be more specific with my problem.
I am trying to do a flashback on a failed primary database, the only reason why I want to do a flashback is because dataguard uses the flashback command to try and synchronize the failed database. Specifically dataguard is trying to run:
FLASHBACK DATABASE TO SCN 865984
But it fails, if I run it manually then I get:
SQL> FLASHBACK DATABASE TO SCN 865984;
FLASHBACK DATABASE TO SCN 865984
ERROR at line 1:
ORA-38754: FLASHBACK DATABASE not started; required redo log is not available
ORA-38761: redo log sequence 5 in thread 1, incarnation 3 could not be accessed
Looking at the last checkpoint I see:
CHECKPOINT_CHANGE#
865857
Also looking at the archive logs:
RECID STAMP THREAD# SEQUENCE# FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# RESETLOGS_CHANGE# RESETLOGS
25 766838550 1 1 863888 10-NOV-11 863892 863888 10-NOV-11
26 766838867 1 2 863892 10-NOV-11 864133 863888 10-NOV-11
27 766839225 1 3 864133 10-NOV-11 864289 863888 10-NOV-11
28 766839340 1 4 864289 10-NOV-11 864336 863888 10-NOV-11
29 766840698 1 5 864336 10-NOV-11 865640 863888 10-NOV-11
30 766841128 1 6 865640 10-NOV-11 865833 863888 10-NOV-11
31 766841168 1 7 865833 10-NOV-11 865857 863888 10-NOV-11
How can I determine what archive logs are needed by a flashback command? I deleted any archive logs with a SCN less than the checkpoint #, I can restore them from backup but I am trying to figure out how to query what is required for a flashback. Maybe this coincides with the point that flashbacks have nothing to do with the backups of datafiles or the checkpoints? -
How the Payload Message and Logs are stored in the B1i Database Table: BZSTDOC
I would appreciate it if someone could provide any documentation regarding B1i database further maintenance.
for example:
I want to know how the payload message and logs are stored in the table BZSTDOC, and how can we retrieve the payload message directly from the column DOCDATA.
As described in the B1iSNGuide05 3.2 LogGarbageCollection:
to avoid the overload of the B1i Database, I set the Backup Buffer to 90 days : so this means Message Logs from the last 90 days will always be available, but is there some way we can save those old messages to a disk so that I can retrieve the payload message anytime?
in addition, let’s assume the worst, the B1iSN server or the B1i database damaged, Can we just simply restore the B1i database from a latest backup DB then it can work automatically after the B1iSN server is up and running again?
BR/JimDear SAP,
Two weeks passed, I still haven't received any feedback from you guys.
Could you please have a look at my question?
How is this Question going? Is it Untouched/Solving/Reassigned ? -
Archive logs are being shipped, but are not applied
Hi everyone,
Some strange things are happening when I try to configure an Oracle Data Guard setup. Currently I am at the point where the configuration has been completed, and I just need to sync the standby database to the primary one. I can see in the log files that the archive logs are being shipped, but they are not applied on the standby system.
If I run "recover standby database;" manually in sqlplus I can see that it is trying to apply an archive log which is way too old (ORA-00279: change 9656498443 generated at 04/29/2008 08:45:08 needed for thread 1).
In the alert log I can also see this error: Warning: Recovery target destination is in a sibling branch of the controlfile checkpoint. Recovery will only recover changes to datafiles.
At this point I was thinking that the standby database might be on a different incarnation compared to the primary, but this is not the case, they are both in incarnation 6:
6 6 MVF 4023175798 CURRENT 48493546257 13-06-21
Does anyone have an idea how this could happen, and how I could fix this issue?
Thanks, JM.The restore did not cause any errors to be displayed, so I assumed everything was ok.
That's fair enough.
One thing I think might cause this behaviour is that the backup on the primary database is incremental,
Yes...that may be an issue. Best bet is to re-run your standby creation.....as you are doing.
With version 11gR2 you also have the option of duplicate from active database which negates the need to copy your backupsets over to do the restore: I find it a much simpler process than the rman backup, copy files over, restore and then recover process.
http://www.oracle-base.com/articles/11g/data-guard-setup-11gr2.php
Something worth considering. -
Whether t-logs are truncated in DB's particpating in High Availability. SQLAlways On 2012
Hi,
How the transaction logs are cleared for DB's participating in SQL AlwaysOn.I have a DB participating in HA.Now in order to use alwaysON DB recovery model should be set to full. NOw with this recovery model my transaction logs will grow continuously.
How t-logs can be cleared for the DB's participating in AG. Is there any recommendation?
Thanks
ManishHello,
Have you scheduled log backup on primary.Secondary replica might be applying transaction log records of this database to a corresponding secondary database.
Whats does below query returns
select name,log_resuse_wait_desc from sys.databases where name='db_name'
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
I enabled Soft Delete on one of my Azure Mobile Services tables, and ever since then, the logs are flooded with tons of warnings that say something like this:
The table 'Section' does not support the 'deleted' system property.
Is there a way to suppress these warnings, or is it advisable to enable soft delete for all of my tables?
As a follow on, is there a way to export the logs so that it's easier to peruse through them and search?
Thanks :)Hi
You can set your logging level in Azure Admin portal to be Error only, so it only logs errors and warnings will be ignored.
Regards
Aram -
As of version 31, why is there still no Thunderbird option to QUICKLY insert current date and time in message that you are writing?
Literally have seen this very-much-needed -- and used -- option "promised" for three years now, and even if there's only one or two formats that could be used, at least the option is there.
It seems only way is to link a Macro and tool to Thunderbird and do it that way.
Joe Rotello
[email protected]
Skype: joerotelloWhere was it promised? A quick search of Bugzilla didn't find a functionality request bug report for it.
I assume you're aware that Mozilla stopped development about 2 years ago (just adds security/stability fixes and provides infrastructure) and all new features and bug fixes are now added by the community. They seem pretty tied up with bug fixes and reworking some hard to maintain components such as the MIME support.
Have you tried the Timestamp add-on at https://addons.mozilla.org/en-us/thunderbird/addon/timestamp/ ? The version at AMO doesn't support versions later than 2.0 so you'd need to do something like install the disable add-on compatibility checks add-on at https://addons.mozilla.org/en-us/thunderbird/addon/checkcompatibility/?src=ss, and ignore the warning message about Timestamp not being compatible. However, the author has a version at http://extensions.sanjer.nl/?page=tb_ts that supposedly supports up to Thunderbird 11.9.x so it should be "compatible by default as it supports version 5 or later and is not a binary add-on like Lightning or Enigmail.
"For Thunderbird use the context menu (right click popup) in the compose window, Ctrl+Shift+T or "Options | Insert timestamp" to inserts the date/time into a message" -
Firefighter Config change logs / SOD logs are not displayed..
We are on GRC 5.3, SP8. I have configured the SUP and firefighter id's are working fine. However, I am getting the message " No match nor conflict found " when I execute the 'Configuration Change Log report' and 'SOD Violations Report' even though the we changed the configuration and FF id's executed conflicting transactions defined in RAR. ' Log data changes ' box is already activated in the following tables:
1. Configuration (/VIRSA/ZFFCONFIG)
2. Controllers (/VIRSA/ZFFCNTRL)
3. Critical Tcodes (/VIRSA/ZVIRTCODE)
4. Firefighters (/VIRSA/ZFFUSERS)
5. Owners (/VIRSA/ZVIRFFIDS)
6. Reason Codes (/VIRSA/ZFFRCD)
7. Security (/VIRSA/ZVIRFFPWD)
Still the logs are not displayed. Thanks for your help.
Regards,
RajHi Raj,
Can you check the SM37 background job../VIRSA/ZVFATBAK is running or NOT???
Regards'
Gangadhar
Maybe you are looking for
-
How to delete string or line from unix file(dataset) of application server
Hi All, After transfer workarea information or all records into dataset(unix file). When I see the file in application server automatically the last line is shown a blank line. I am not passing any blank line. I have tried for single record than als
-
Sharing iTunes Library - Can see but cannot play movies
I have a Mac with iTunes and a connected external hard drive. In my Movies library, I point to movie files on my external hard drive. I have shared my entire iTunes library including my music and movie selections under iTunes Sharing settings. From i
-
What happened to the attachment icon in Mail?
I just upgraded to Lion, and I noticed that there wasn't an icon for mail attachments. I looked into preferences and no option there. I have to go into the menu to attach a file. What happened? That seems to be a pretty basic function.
-
HT201363 i forgot my password when i have to back up my phone, what do i do?
i forgot my password when i have to back up my phone, what do i do?
-
MIRO / - Can it match on item number instead of line number?
Hello, I am bringing in INVOICE01 iDocs and posting them (same as manual MIRO) against 2 Way Purchase Orders with function module IDOC_INPUT_INVOIC_MRM. Since the PO's are 2 Way PO's we don't do receipts against them. My Issue: This vendor does not