Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I have 2 questions:
1) Does ASM Log Reader alter redo log files or only reads them?
2) Confirmation of whether Qlik Replicate alters state of ASM and its files or not
3) Why it is needed to grant SYSASM privileges? Is it possible to work with ASMOPER privilege?
4) List of commands/calls that are executed by Replicate while working with ASM (including which of the procedures from DBMS_DISKGROUP package are used and in what modes)?
Hello @Tamerboy ,
Qlik Replicate does not modify the redo log files or any other data in ASM. It only reads the required redo log information.
No write operations are performed by Qlik Replicate.
Qlik Replicate reads files from ASM through the Oracle API by calling the DBMS_DISKGROUP packages. These calls require at least SYSASM or SYSDBA privileges. Without SYSASM/SYSDBA, the required API calls cannot be executed.
This is an Oracle privilege requirement rather than a Qlik Replicate restriction.
Regarding ASMOPER, this is intentionally a limited operational privilege. It is primarily intended for operations such as starting and stopping ASM instances, mounting and dismounting disk groups, and similar administrative tasks. Oracle specifically describes the ASM SYSOPER role as providing operational privileges rather than access to the data stored in ASM.
Hope this helps.
John.
Hi,
1. and 2. No. Redo logs are read and parsed on the Replicate server.
3. and 4. There is no other role available in Oracle that grants all of the permissions Replicate needs, so you have to give it super privilege. You can get a list of operations that Replicate performs from Qlik Support.
Cheers!
Hello @Tamerboy ,
Qlik Replicate does not modify the redo log files or any other data in ASM. It only reads the required redo log information.
No write operations are performed by Qlik Replicate.
Qlik Replicate reads files from ASM through the Oracle API by calling the DBMS_DISKGROUP packages. These calls require at least SYSASM or SYSDBA privileges. Without SYSASM/SYSDBA, the required API calls cannot be executed.
This is an Oracle privilege requirement rather than a Qlik Replicate restriction.
Regarding ASMOPER, this is intentionally a limited operational privilege. It is primarily intended for operations such as starting and stopping ASM instances, mounting and dismounting disk groups, and similar administrative tasks. Oracle specifically describes the ASM SYSOPER role as providing operational privileges rather than access to the data stored in ASM.
Hope this helps.
John.