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
Manish

Hello,
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

Similar Messages

MV logs getting truncated

I am trying to setup Master to Materialized view(Snapshot) replication and Materailzed view logs getting truncated when I create MV at Snapshot site. Is there any way to prevent truncating MV logs at master site while creating MV at sanpshot site?
Here are steps that I perforemd, Initally I made two copy of database one as master and other is Snpshot with unique global name.
At Master site:
1. MV logs created.
2. Some DML happned at Master site, MV logs are populated.
Snapshot(MV) site:
1. MV created using prebuilt table option.
then I checked on Maste site MV logs are truncated but DML that happened in step 2 at Master site that are missing at Snapshot site.
Is there any way to prevent truncating MV logs at master site while creating MV at sanpshot site?
Thanks.
Pravin

This is a restriction of the prebuilt table "At registration time, the table must reflect the materialization of a subquery." Even if you could prevent the snapshot log from getting truncated (i.e. by creating a second snapshot against the same master table), the snapshot you created on prebuilt still will NOT refresh those records. As far as the snapshot log is concerned, once you create the snapshot with prebuilt, it must be consistent. The trick is, you have to keep the users from updating the master table until you have issued the create snapshot command.

Transaction Log Truncate not working on Sql Server 2012 High Availability Groups

Hi Everyone
Firstly I have tried to search the forum for similar issues but can't seem to find any that match our situation.
We have a SQL Server 2012 High Availability Group with 2 Nodes
Node 1 = Primary
Node 2 = Secondary
Backup Schedule as follows
Full Database Backup @ 00:00
Transaction Log Backup every 30 minutes from 00:30:00 till 23:59:59.
These backups are run by Maintenance Jobs, but we have also tried doing direct backups in SSMS using Backup Database and Backup Log commands.
Before we configured the High Availability group the transaction log backups worked fine.
After we configured the High Availability group we performed a Full Backup and the T-Log schedule did the T-Log backup. The 1st T-log backup truncated the log (Used space Decreased) as expected.
However subsequent T-Log backups do not truncate the T-Log.
This happens both in our acceptance and Live environments. This also happens when running the backups as a Backup operator and sysadmin, this does not seem to be a permissions issue at all.
We have tried running the Backup on the Primary and Secondary Replica.
What about High Availability groups could stop Transaction Log Backups from not truncating the log?
Thanks
James

Hi Sean
Thank you for your reply, please see the output of the sys.databases query below, and some others which you may find usefull.
Query: select database_id,recovery_model_desc, log_reuse_wait, log_reuse_wait_desc from sys.databases
where database_id = 5
Result: database_id   recovery_model_desc   log_reuse_wait   log_reuse_wait_desc
                 5
FULL   0
NOTHING
I also ran the following
select database_id, truncation_lsn, last_received_lsn, last_commit_lsn, last_hardened_lsn, last_redone_lsn,*
from sys.dm_hadr_database_replica_states
go
database_id
truncation_lsn
last_received_lsn
last_commit_lsn
last_hardened_lsn
last_redone_lsn
database_id
group_id
replica_id
group_database_id
is_local
synchronization_state
synchronization_state_desc
is_commit_participant
synchronization_health
synchronization_health_desc
database_state
database_state_desc
is_suspended
suspend_reason
suspend_reason_desc
recovery_lsn
truncation_lsn
last_sent_lsn
last_sent_time
last_received_lsn
last_received_time
last_hardened_lsn
last_hardened_time
last_redone_lsn
last_redone_time
log_send_queue_size
log_send_rate
redo_queue_size
redo_rate
filestream_send_rate
end_of_log_lsn
last_commit_lsn
last_commit_time
low_water_mark_for_ghosts
5
1231833000417170000000
1231833000418880000000
1231833000418880000000
1231833000418890000000
1231833000418880000000
5
1391A499-3F9A-47D5-BCE0-70BC204E2A5B
7E8BFC2E-363F-4C48-86F0-C276D3E0C8D9
0581E17A-6B7B-4B8F-9288-BF765BFBCE77
0
2
SYNCHRONIZED
1
2
HEALTHY
NULL
NULL
0
NULL
NULL
4294967295429490000000000
1231833000417170000000
1
41863
1231833000418880000000
41863
1231833000418890000000
41863
1231833000418880000000
41863
0
25541
0
84404
75304
1231833000418880000000
1231833000418880000000
41863
441019861
5
1231833000417170000000
NULL
1231833000418880000000
1231833000418890000000
NULL
5
1391A499-3F9A-47D5-BCE0-70BC204E2A5B
83B9F00E-D63F-4AC0-98FC-35E48FFA2C6F
0581E17A-6B7B-4B8F-9288-BF765BFBCE77
1
2
SYNCHRONIZED
1
2
HEALTHY
0
ONLINE
0
NULL
NULL
4294967295429490000000000
1231833000417170000000
NULL
NULL
NULL
NULL
1231833000418890000000
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
1231833000418880000000
1231833000418880000000
41863
441019861
And
dbcc loginfo
go
RecoveryUnitId
FileId
FileSize
StartOffset
FSeqNo
Status
Parity
CreateLSN
0
2
458752
8192
1231828
0
128
0
0
2
458752
466944
1231829
0
128
0
0
2
458752
925696
1231830
0
128
0
0
2
712704
1384448
1231831
0
128
0
0
2
19398656
2097152
1231832
0
128
1229654000000040000000
0
2
10199171072
21495808
1231833
2
128
1229656000000010000000
0
2
10199171072
10220666880
0
0
64
1229656000000010000000
0
2
10199171072
20419837952
1231827
0
64
1229656000000010000000
0
2
10199171072
30619009024
0
0
128
1229656000000010000000
0
2
10199171072
40818180096
0
0
128
1229656000000010000000
0
2
10199171072
51017351168
0
0
128
1229656000000010000000
0
2
10199171072
61216522240
0
0
128
1229656000000010000000
0
2
10199171072
71415693312
0
0
128
1229656000000010000000
0
2
10199171072
81614864384
0
0
128
1229656000000010000000
0
2
536870912
91814035456
0
0
64
1229989001661260000000
0
2
536870912
92350906368
0
0
64
1229989001661260000000
0
2
536870912
92887777280
0
0
64
1229989001661260000000
0
2
536870912
93424648192
0
0
64
1229989001661260000000
0
2
536870912
93961519104
0
0
64
1229989001661260000000
0
2
536870912
94498390016
0
0
64
1229989001661260000000
0
2
536870912
95035260928
0
0
64
1229989001661260000000
0
2
536870912
95572131840
0
0
64
1229989001661260000000
0
2
536870912
96109002752
0
0
64
1229989001661260000000
0
2
536870912
96645873664
0
0
64
1229989001661260000000
0
2
536870912
97182744576
0
0
64
1229989001661260000000
0
2
536870912
97719615488
0
0
64
1229989001661260000000
0
2
536870912
98256486400
0
0
64
1229989001661260000000
0
2
536870912
98793357312
0
0
64
1229989001661260000000
0
2
536870912
99330228224
0
0
64
1229989001661260000000
0
2
536870912
99867099136
0
0
64
1229989001661260000000
0
2
536870912
100403970048
0
0
64
1229995000058520000000
0
2
536870912
100940840960
0
0
64
1229995000058520000000
0
2
536870912
101477711872
0
0
64
1229995000058520000000
0
2
536870912
102014582784
0
0
64
1229995000058520000000
0
2
536870912
102551453696
0
0
64
1229995000058520000000
0
2
536870912
103088324608
0
0
64
1229995000058520000000
0
2
536870912
103625195520
0
0
64
1229995000058520000000
0
2
536870912
104162066432
0
0
64
1229995000058520000000
0
2
536870912
104698937344
0
0
64
1229995000058520000000
0
2
536870912
105235808256
0
0
64
1229995000058520000000
0
2
536870912
105772679168
0
0
64
1229995000058520000000
0
2
536870912
106309550080
0
0
64
1229995000058520000000
0
2
536870912
106846420992
0
0
64
1229995000058520000000
0
2
536870912
107383291904
0
0
64
1229995000058520000000
0
2
536870912
107920162816
0
0
64
1229995000058520000000
0
2
536870912
108457033728
0
0
64
1229995000058520000000
0
2
536870912
108993904640
0
0
64
1230004000028400000000
0
2
536870912
109530775552
0
0
64
1230004000028400000000
0
2
536870912
110067646464
0
0
64
1230004000028400000000
0
2
536870912
110604517376
0
0
64
1230004000028400000000
0
2
536870912
111141388288
0
0
64
1230004000028400000000
0
2
536870912
111678259200
0
0
64
1230004000028400000000
0
2
536870912
112215130112
0
0
64
1230004000028400000000
0
2
536870912
112752001024
0
0
64
1230004000028400000000
0
2
536870912
113288871936
0
0
64
1230004000028400000000
0
2
536870912
113825742848
0
0
64
1230004000028400000000
0
2
536870912
114362613760
0
0
64
1230004000028400000000
0
2
536870912
114899484672
0
0
64
1230004000028400000000
0
2
536870912
115436355584
0
0
64
1230004000028400000000
0
2
536870912
115973226496
0
0
64
1230004000028400000000
0
2
536870912
116510097408
0
0
64
1230004000028400000000
0
2
536870912
117046968320
0
0
64
1230004000028400000000
0
2
536870912
117583839232
0
0
64
1230012000103140000000
0
2
536870912
118120710144
0
0
64
1230012000103140000000
0
2
536870912
118657581056
0
0
64
1230012000103140000000
0
2
536870912
119194451968
0
0
64
1230012000103140000000
0
2
536870912
119731322880
0
0
64
1230012000103140000000
0
2
536870912
120268193792
0
0
64
1230012000103140000000
0
2
536870912
120805064704
0
0
64
1230012000103140000000
0
2
536870912
121341935616
0
0
64
1230012000103140000000
0
2
536870912
121878806528
0
0
64
1230012000103140000000
0
2
536870912
122415677440
0
0
64
1230012000103140000000
0
2
536870912
122952548352
0
0
64
1230012000103140000000
0
2
536870912
123489419264
0
0
64
1230012000103140000000
0
2
536870912
124026290176
0
0
64
1230012000103140000000
0
2
536870912
124563161088
0
0
64
1230012000103140000000
0
2
536870912
125100032000
0
0
64
1230012000103140000000
0
2
536870912
125636902912
0
0
64
1230012000103140000000
0
2
536870912
126173773824
0
0
128
1230338000973820000000
0
2
536870912
126710644736
0
0
128
1230338000973820000000
0
2
536870912
127247515648
0
0
128
1230338000973820000000
0
2
536870912
127784386560
0
0
128
1230338000973820000000
0
2
536870912
128321257472
0
0
128
1230338000973820000000
0
2
536870912
128858128384
0
0
128
1230338000973820000000
0
2
536870912
129394999296
0
0
128
1230338000973820000000
0
2
536870912
129931870208
0
0
128
1230338000973820000000
0
2
536870912
130468741120
0
0
128
1230338000973820000000
0
2
536870912
131005612032
0
0
128
1230338000973820000000
0
2
536870912
131542482944
0
0
128
1230338000973820000000
0
2
536870912
132079353856
0
0
128
1230338000973820000000
0
2
536870912
132616224768
0
0
128
1230338000973820000000
0
2
536870912
133153095680
0
0
128
1230338000973820000000
0
2
536870912
133689966592
0
0
128
1230338000973820000000
0
2
536870912
134226837504
0
0
128
1230338000973820000000
0
2
536870912
134763708416
0
0
128
1230338001901440000000
0
2
536870912
135300579328
0
0
128
1230338001901440000000
0
2
536870912
135837450240
0
0
128
1230338001901440000000
0
2
536870912
136374321152
0
0
128
1230338001901440000000
0
2
536870912
136911192064
0
0
128
1230338001901440000000
0
2
536870912
137448062976
0
0
128
1230338001901440000000
0
2
536870912
137984933888
0
0
128
1230338001901440000000
0
2
536870912
138521804800
0
0
128
1230338001901440000000
0
2
536870912
139058675712
0
0
128
1230338001901440000000
0
2
536870912
139595546624
0
0
128
1230338001901440000000
0
2
536870912
140132417536
0
0
128
1230338001901440000000
0
2
536870912
140669288448
0
0
128
1230338001901440000000
0
2
536870912
141206159360
0
0
128
1230338001901440000000
0
2
536870912
141743030272
0
0
128
1230338001901440000000
0
2
536870912
142279901184
0
0
128
1230338001901440000000
0
2
536870912
142816772096
0
0
128
1230338001901440000000
0
2
536870912
143353643008
0
0
128
1230346000103040000000
0
2
536870912
143890513920
0
0
128
1230346000103040000000
0
2
536870912
144427384832
0
0
128
1230346000103040000000
0
2
536870912
144964255744
0
0
128
1230346000103040000000
0
2
536870912
145501126656
0
0
128
1230346000103040000000
0
2
536870912
146037997568
0
0
128
1230346000103040000000
0
2
536870912
146574868480
0
0
128
1230346000103040000000
0
2
536870912
147111739392
0
0
128
1230346000103040000000
0
2
536870912
147648610304
0
0
128
1230346000103040000000
0
2
536870912
148185481216
0
0
128
1230346000103040000000
0
2
536870912
148722352128
0
0
128
1230346000103040000000
0
2
536870912
149259223040
0
0
128
1230346000103040000000
0
2
536870912
149796093952
0
0
128
1230346000103040000000
0
2
536870912
150332964864
0
0
128
1230346000103040000000
0
2
536870912
150869835776
0
0
128
1230346000103040000000
0
2
536870912
151406706688
0
0
128
1230346000103040000000
0
2
536870912
151943577600
0
0
128
1230355000086930000000
0
2
536870912
152480448512
0
0
128
1230355000086930000000
0
2
536870912
153017319424
0
0
128
1230355000086930000000
0
2
536870912
153554190336
0
0
128
1230355000086930000000
0
2
536870912
154091061248
0
0
128
1230355000086930000000
0
2
536870912
154627932160
0
0
128
1230355000086930000000
0
2
536870912
155164803072
0
0
128
1230355000086930000000
0
2
536870912
155701673984
0
0
128
1230355000086930000000
0
2
536870912
156238544896
0
0
128
1230355000086930000000
0
2
536870912
156775415808
0
0
128
1230355000086930000000
0
2
536870912
157312286720
0
0
128
1230355000086930000000
0
2
536870912
157849157632
0
0
128
1230355000086930000000
0
2
536870912
158386028544
0
0
128
1230355000086930000000
0
2
536870912
158922899456
0
0
128
1230355000086930000000
0
2
536870912
159459770368
0
0
128
1230355000086930000000
0
2
536870912
159996641280
0
0
128
1230355000086930000000
0
2
536870912
160533512192
0
0
128
1230364000070870000000
0
2
536870912
161070383104
0
0
128
1230364000070870000000
0
2
536870912
161607254016
0
0
128
1230364000070870000000
0
2
536870912
162144124928
0
0
128
1230364000070870000000
0
2
536870912
162680995840
0
0
128
1230364000070870000000
0
2
536870912
163217866752
0
0
128
1230364000070870000000
0
2
536870912
163754737664
0
0
128
1230364000070870000000
0
2
536870912
164291608576
0
0
128
1230364000070870000000
0
2
536870912
164828479488
0
0
128
1230364000070870000000
0
2
536870912
165365350400
0
0
128
1230364000070870000000
0
2
536870912
165902221312
0
0
128
1230364000070870000000
0
2
536870912
166439092224
0
0
128
1230364000070870000000
0
2
536870912
166975963136
0
0
128
1230364000070870000000
0
2
536870912
167512834048
0
0
128
1230364000070870000000
0
2
536870912
168049704960
0
0
128
1230364000070870000000
0
2
536870912
168586575872
0
0
128
1230364000070870000000
0
2
536870912
169123446784
0
0
128
1230373000054750000000
0
2
536870912
169660317696
0
0
128
1230373000054750000000
0
2
536870912
170197188608
0
0
128
1230373000054750000000
0
2
536870912
170734059520
0
0
128
1230373000054750000000
0
2
536870912
171270930432
0
0
128
1230373000054750000000
0
2
536870912
171807801344
0
0
128
1230373000054750000000
0
2
536870912
172344672256
0
0
128
1230373000054750000000
0
2
536870912
172881543168
0
0
128
1230373000054750000000
0
2
536870912
173418414080
0
0
128
1230373000054750000000
0
2
536870912
173955284992
0
0
128
1230373000054750000000
0
2
536870912
174492155904
0
0
128
1230373000054750000000
0
2
536870912
175029026816
0
0
128
1230373000054750000000
0
2
536870912
175565897728
0
0
128
1230373000054750000000
0
2
536870912
176102768640
0
0
128
1230373000054750000000
0
2
536870912
176639639552
0
0
128
1230373000054750000000
0
2
536870912
177176510464
0
0
128
1230373000054750000000
0
2
536870912
177713381376
0
0
128
1230382000038660000000
0
2
536870912
178250252288
0
0
128
1230382000038660000000
0
2
536870912
178787123200
0
0
128
1230382000038660000000
0
2
536870912
179323994112
0
0
128
1230382000038660000000
0
2
536870912
179860865024
0
0
128
1230382000038660000000
0
2
536870912
180397735936
0
0
128
1230382000038660000000
0
2
536870912
180934606848
0
0
128
1230382000038660000000
0
2
536870912
181471477760
0
0
128
1230382000038660000000
0
2
536870912
182008348672
0
0
128
1230382000038660000000
0
2
536870912
182545219584
0
0
128
1230382000038660000000
0
2
536870912
183082090496
0
0
128
1230382000038660000000
0
2
536870912
183618961408
0
0
128
1230382000038660000000
0
2
536870912
184155832320
0
0
128
1230382000038660000000
0
2
536870912
184692703232
0
0
128
1230382000038660000000
0
2
536870912
185229574144
0
0
128
1230382000038660000000
0
2
536870912
185766445056
0
0
128
1230382000038660000000
The create LSN column seems to have been truncated so here is is again, sorry for the bulky reply.
CreateLSN
0
0
0
0
1229654000000041600001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
Thanks
James

Logs are lost frequently in Remote Agent Server

Hi All,
ACS 4.2 and remote agent was working properly two months before. But in past two months we are facing weird issue in RA server.For Somedays we are missing logs from both ACS and RA server. Once we notice this we use to restart the services in ACS to give workaround. But due to this we loose our daily logs intermittently and facing risk in without having logs.
This is not like communication between ACS and RA is not at all happening. It happens properly for a week or month, but again it is going bad without any config change.
CSAgent.ini file is properly configured.
Full version is 4.2.1.15 and patch is 10 in acs and ra.
ACS and Remote Agent Major and Patch version are same.
Any help would be highly appreciated.
Thanks.

Do you see the same intermittent logging issue with all services like csauth, rds, tcs etc.
Could you plz. provide the cslogagent file from the remote agent server when you see this issue happening.
C:\Program Files\Cisco\CiscoSecure ACS Agent\CSLogAgent\Logs
Steps to gather msinfo32
- Click the Start button.
- Click the Run option.
- Type "msinfo32" into the box and press Enter.
- Click "System Information."
- Choose "Save as System Information File" from the "Action" menu.
- Open an appropriate directory, or something easy like the desktop.
- Type "MSInfo32" into the Filename box and press Enter.
- Wait several minutes for the program to collect and save information
Did you check whether cisco remote agent server is excluded for being scanned by AV?
Jatin Katyal
- Do rate helpful posts -

How to display a DIV or not, based on whether a logging session cookie exists or not?

Hi everyone
I have created a logging system for a simple CMS using Dreamweaver server behaviours.
My problem :
When logged in, I would like to show on my pages a DIV saying something like "You are logged in". If not logged in, I would like a different DIV with this text saying "Please log in"
I have simplified the problem as much as I could. Basically, I would like to show something or to hide it and show another thing based on whether the logging session exists or not. Would someone have a simple answer to this problem?
Much obliged, W

Thanks HJ
Your answer helped me find more info about cookies and session which is what I actually needed.
So I can show a particular item based on whether an admin user is logged in, I proceed as follow.
First I check whethet the session exists. If he has just logged in using Dreamweaver logging system, the session will exist. So put the text above the <head> and preferably at the very top of the page.
<?php
if (!isset($_SESSION)) {
session_start();
?>
Then in the content portion of the page where I want to display, say a DIV with some content for the administrator I place the following :
<?php
$accessLevels = array('a','b');
$validLevel = $_SESSION['MM_UserGroup'];
if(array_search($validLevel, $accessLevels)>-1){
?>
<div id="amendPage" style="margin-left:0;margin-top:0;height:20px;"><a href="/admin/changePage.php">Changez le contenu de cette page</a></div>
<?php
?>
I am checking here whether the user is logged in based on his or her access level which I have previously set in the database. 'a' being an access level and 'b' an other one which might enable more things. So I can play with this array to show something to someone based on the access level.
If I were to remove 'b' from the array, the div would only be visible when a user with an 'a' access level is logged in and vice versa.
Not sure whether this is a good option, but it works for me

Forgot whether automatic updates are included when you update Flashplayer. Update was fine, just didn't see where to click to get automatic updates.

Forgot whether automatic updates are included when you update Flashplayer. Update was fine, just didn't see where to click to get automatic updates. Please advise whether I need to do anything or not. Thanks.

If you are using Windows:
You must be logged in from an Administrator account not a Standard account.
Click on START, then Click on CONTROL PANEL, then be sure the View is set to Large Icons not Category.
Click on the Flash Player Icon. The Flash Player Control Panel should come up.
Click on the UPDATES tab. Now you can verify or select automatic updating.

[svn] 4128: Fix for - Examples imported by the @ includeExample tag are truncated after the first or second XML comment

Revision: 4128
Author: [email protected]
Date: 2008-11-17 12:53:34 -0800 (Mon, 17 Nov 2008)
Log Message:
Fix for - Examples imported by the @includeExample tag are truncated after the first or second XML comment
examples-path option is now public and adding period at the end of Constructor.
QE Notes: baselines need to be updated.
Doc Notes: None
Bugs: SDK-18125, SDK-18077, SDK-18126
tests: checkintests
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18125
http://bugs.adobe.com/jira/browse/SDK-18077
http://bugs.adobe.com/jira/browse/SDK-18126
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va
flex/sdk/trunk/modules/compiler/src/java/flex2/configuration_en.properties
flex/sdk/trunk/modules/compiler/src/java/flex2/tools/ASDocConfiguration.java

I have the same problem except almost every song I bought from Itunes has this problem. Not only that, but somehow some of the music, about $125 worth has been deleted form my 3 back up discs. This is only happening with my purchases and not any songs I uploaded from cd. How on earth did this happen, and how did it wipe clean 3 different back ups? I have found some of the music where it belongs, but like I said some of them are gone, gone, gone. I run three different back ups and they are on 24/7. Where is all of this music? I still have it on my ipod, but it will not load back into itunes the way purchases used to. Some of the music is purchased straight to my ipod touch, but shouldn't i be able to reload them into itunes? I spent 3 hours going 1 song at a time reloading them from their original location. But I cannot locate about $125 worth of music that I purchased from itunes. I have 6 macs in my family and preach the good news to all who will listen about hows macs are flawless. Now I have egg all over my face and have thrown away a nice sum of money on missing music. Please help!

HANA Logs in "Truncated" status

We currently have an issue where all the HANA logs (except the current "active" log) are in "Truncated" status. This is causing new log segments to be created every time a log is filled, instead of cycling through the older logs. The backup logs indicate no failures and show that log backups are completing every few minutes. The only thing unusual that I could find was one instance of a log backup from 4 days ago that appeared to be stuck in "Running" status. All subsequent backups appear to be running normally however. Coincidentally, 4 days ago is roughly when the log segment count started increasing.
Anyone know what could have caused this, and what can be done to reset the log statuses so that they can be written again? We are approaching 85% full on the filesystem and growing.

Okay the requirement is to check a text field to be filled in a specific status with a specific priority. The only way i managed to do that is by allowing a status change only via defined actions. I implemented the badi SOCM_CHECK_CONDITION and did my checks there.
It worked perfectly, except for the fact that the system won't change the user status until the ibase component field is filled. I thought it could be a problem with the condition so i did a fresh copy of the slfn and added just the action for status change. But the problem is still there.
There is no error message and it also says that the specific action has been performed succesfully. But the status will only change if i fill the ibase component field.
I assume that the "hf_check_status" method has been coded for the change request management where you always need an ibase component in you change requests or change documents.
I can do a workaround by filling the ibsae by default and hide it, but it would be nice to know what the problem actually is
regards daniel

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
Ross

Hi 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

Win 8.1 modern calendar - all notes in a calendar meeting are truncated/removed after opening/viewing (Exchange 2010 and EAS)

All,
If this isn't the best forum to post in, please let me know.
I am having an issue when I accept calendar invites in the native/modern application for calendaring in Win 8.1. Whenever I then go back to open and view the contents of a meeting, all the notes are truncated and removed after closing that event.
We are running exchange 2010 for the email server.
The machine is not domain joined/managed (local account only).
Any assistance greatly appreciated.
Thanks,
Steve

Team,
Looking for some expert advice here - any assistance would be appreciated.

PI 7.1 Receiver file adapter - Spaces are truncated at end of each line

In Receiver file adapter, I specified file content conversion parameters. My file structure is as below:
Header
Field1 10
Field2 20
Field3 8
Filler   20
Detail
Field1 10
Field2 8
Filler    8
In both Header and Details structures I have to fill 20 and 8 spaces at end of each line. In XML (Payload) I can view the spaces. But when the text file is created all the spaces are truncated.
Could you please solve this issue.
Regards

Recordset Structure: ns1:MT_SAP,REC,Header,Detail
ns1:MT_SAP.fieldSeparator          '0'
ns1:MT_SAP_PNC_PPAY.fieldContentFormatting     nothing
REC.fieldContentFormatting          nothing
REC.fieldSeparator               '0'
REC.processConfiguration               FromConfiguration
Header.fieldFixedLengths               10,20,8,20
Header.endSeparator               'nl'
Header.fixedLengthTooShortHandling          Ignore
Header.fieldNames               Field1,Field2,Field3,Filler
Header.fieldContentFormatting          nothing
Detail.fieldFixedLengths               10,8,8
Detail.endSeparator               'nl'
Detail.fieldNames               Field1,Field2,Filler
Detail.fieldContentFormatting          nothing
Detail.fixedLengthTooShortHandling          Ignore

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,
Mark

Hi 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

Parameter labels are truncated

Hi All,
I'm using BI Publisher 11.1.1.6.
I create reports based on Excel and RTF templates in order to generate Excel or PDF reports.
In the DM I define my parameters and their labels.
When I run the report or try to see the XML output, in the parameter pane all the parameter labels are truncated.
Let say I define a parameter as that:
Name Data Type Parameter Type
P_NAME String Text
And then in the detail of this parameter:
Display Label : Enter Name (% is allowed) :
Once in the Report (or the XML output) execution window the label is truncated at 23 characters
my label become :
Enter Name (% is allowe...
Does someone ever experienced this ? and do you have a workaround to display the full label?
I've try to modify parameter properties, report properties... but nothing change, I can not have more that 23 characters...
I've searched on Metalink, communities .... but didn't find anything...
Thank you in advance for your help
Brice

post this in ITS forum.
Raja

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

Whether t-logs are truncated in DB's particpating in High Availability. SQLAlways On 2012

Similar Messages

Maybe you are looking for