Home » Server Options » Data Guard » Data Guard - Advanced Compression (11.2.0.2.0 AIX 6.1)
Data Guard - Advanced Compression [message #633295] Sat, 14 February 2015 09:49 Go to next message
hexmanju
Messages: 78
Registered: September 2005
Location: MUMBAI
Member
I have a Data Guard Setup between Primary and Standby.No where i have enabled compression in LOG_ARCHIVE_DEST_1 parameter .But still when i query sys.dba_feature_usage_statistics i find it being used(Data Guard Network Compression).

1)Advanced Compression gets default installed with 11.2.0.2.0.
2)It seems to be somehow making inherent use of it.(At least that what it looks like to me-I May be wrong if some of you experts could help me why the sys.dba_feature_usage_statistics is showing Advanced Compression,Data Guard Network Compression used even though i have not made use of the COMPRESS clause in LOCATION and SERVICE ATTRIBUTE)
3)It does not allow us to turn off Advanced Compression.

Can you advise why i might be seeing its usage.?


[EDITED by LF: fixed topic title typo; was "Gaurd"]

[Updated on: Sun, 15 February 2015 05:21] by Moderator

Report message to a moderator

Re: Data Gaurd-Advanced Compression [message #633296 is a reply to message #633295] Sat, 14 February 2015 10:49 Go to previous messageGo to next message
BlackSwan
Messages: 25715
Registered: January 2009
Location: SoCal
Senior Member
post results from SQL below

SELECT name, 
       detected_usages 
FROM   dba_feature_usage_statistics 
WHERE  Upper(name) LIKE '%COMPRESS%' 
Re: Data Gaurd-Advanced Compression [message #633297 is a reply to message #633295] Sat, 14 February 2015 10:50 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10679
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
Please post the relevant content from dba_feature_usage_statistics. Verbatim.
Post the output of
show parameter log_archive_dest_2
show parameter log_archive_dest_1


>>3)It does not allow us to turn off Advanced Compression
Advance compression for database or DG?
With DG, I have used DISABLE option and it so reflects in DG.

Value of redocompression if using dataguard should be like this.

DGMGRL> show database verbose pri1 redocompression;
  RedoCompression = 'DISABLE'


Re: Data Gaurd-Advanced Compression [message #633299 is a reply to message #633297] Sat, 14 February 2015 17:57 Go to previous messageGo to next message
hexmanju
Messages: 78
Registered: September 2005
Location: MUMBAI
Member
Backup ZLIB Compression 0
Backup ZLIB Compression 0
Backup ZLIB Compression 0
Backup ZLIB Compression 0
Backup BZIP2 Compression 0
Backup BZIP2 Compression 0
Backup BZIP2 Compression 0
Backup BZIP2 Compression 0
Backup BASIC Compression 0
Backup BASIC Compression 0
Backup BASIC Compression 0
Backup BASIC Compression 0
Backup LOW Compression 0
Backup LOW Compression 0
Backup LOW Compression 0
Backup LOW Compression 0
Backup MEDIUM Compression 0
Backup MEDIUM Compression 0
Backup MEDIUM Compression 0
Backup MEDIUM Compression 0
Backup HIGH Compression 0
Backup HIGH Compression 0
Backup HIGH Compression 0
Backup HIGH Compression 0
Compression Advisor 0
Compression Advisor 0
Compression Advisor 0
Compression Advisor 0
SecureFile Compression (user) 0
SecureFile Compression (user) 0
SecureFile Compression (user) 0
SecureFile Compression (user) 0
SecureFile Compression (system) 0
SecureFile Compression (system) 0
SecureFile Compression (system) 0
SecureFile Compression (system) 0
HeapCompression 0
HeapCompression 0
HeapCompression 0
HeapCompression 0
Hybrid Columnar Compression 0
Hybrid Columnar Compression 0
Hybrid Columnar Compression 0
Hybrid Columnar Compression 0




SQL> show parameter log_archive_dest_1
log_archive_dest_1 string LOCATION=/u999/oradata/TIBP/ar
chive/ VALID_FOR=(ALL_LOGFILES
,ALL_ROLES) DB_UNIQUE_NAME=TIB
P_P
log_archive_dest_10 string
log_archive_dest_11 string
log_archive_dest_12 string
log_archive_dest_13 string
log_archive_dest_14 string
log_archive_dest_15 string
log_archive_dest_16 string
log_archive_dest_17 string
log_archive_dest_18 string
log_archive_dest_19 string



SQL> show parameter log_archive_dest_2
log_archive_dest_2 string SERVICE=TIBP_S LGWR ASYNC VALI
D_FOR=(ONLINE_LOGFILES,PRIMARY
_ROLE) DB_UNIQUE_NAME=TIBP_S
log_archive_dest_20 string
log_archive_dest_21 string
log_archive_dest_22 string
log_archive_dest_23 string
log_archive_dest_24 string
log_archive_dest_25 string
log_archive_dest_26 string
log_archive_dest_27 string
log_archive_dest_28 string
log_archive_dest_29 string





The Query i used to check usage -I got it from Support site and its
--
-- Content removed by Mahesh Rajendran
-- Source available at Doc ID 1317265.1



We dont use Data Guard BROKER.

[Updated on: Sat, 14 February 2015 18:17] by Moderator

Report message to a moderator

Re: Data Gaurd-Advanced Compression [message #633300 is a reply to message #633299] Sat, 14 February 2015 18:06 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10679
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
Quote:
f_stat.name in ('Data Guard') then 'Data Guard Network Compression'

I would ask the support what this really means.
I would not post a script provided by OSS in a public forum. It is a violation.


Please check Doc ID 1927057.1

[Updated on: Sat, 14 February 2015 18:23]

Report message to a moderator

Re: Data Gaurd-Advanced Compression [message #633301 is a reply to message #633300] Sat, 14 February 2015 20:04 Go to previous messageGo to next message
BlackSwan
Messages: 25715
Registered: January 2009
Location: SoCal
Senior Member
>sys.dba_feature_usage_statistics is showing Advanced Compression,Data Guard Network Compression used
You are free to believe whatever you want to believe, but I see DETECTED_USAGE=0 and believe it to be true.
YMMV.
Re: Data Gaurd-Advanced Compression [message #633439 is a reply to message #633300] Wed, 18 February 2015 13:40 Go to previous message
hexmanju
Messages: 78
Registered: September 2005
Location: MUMBAI
Member
Thanks for letting me know.Did not know that.

I made use of 1927057.1 and did alter system set log_archive_trace=16;

SQL> show parameter trace

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_trace integer 16
sec_protocol_error_trace_action string TRACE
sql_trace boolean FALSE
trace_enabled boolean TRUE
tracefile_identifier string



I DID NOT get a file like <ORACLE_SID>_tt00_<pid>.trc getting generated in the trace directory.
Any more parameters i need to set/check before i see a trace file which explains compression?

This is 11.2.0.2.0

[Updated on: Wed, 18 February 2015 13:41]

Report message to a moderator

Previous Topic: Data Guard in 10 minutes: demo today
Next Topic: Error when duplicate target database for standby from active database
Goto Forum:
  


Current Time: Sat Nov 18 08:03:57 CST 2017

Total time taken to generate the page: 0.01178 seconds