WARNING OGG-02544 Oracle GoldenGate Delivery for Oracle, reploggt.prm: Unhandled error (ORA-01031: insufficient privileges) while processing the record at SEQNO 237, RBA 266900102 in Integrated mode. REPLICAT will retry in Direct mode.

[Roshan]

Oracle Database 12.1.0.2 (source + target)
RAC 2 nodes
Downstream replication of OGG
GG 18.0

Hi Erman,

please note that I am getting error below whenever I start replicat

 WARNING OGG-02544  Oracle GoldenGate Delivery for Oracle, reploggt.prm:  Unhandled error (ORA-01031: insufficient privileges) while processing the record at SEQNO 237, RBA 266900102 in Integrated mode. REPLICAT will retry in Direct mode.

PERMISSIONDENIED.rar

Can you please advise.

Regards,

R

[ErmanArslansOracleBlog]

*Ensure that you have all the grants present for your Goldengate-related users.

The DB roles and  permissions required for the  OGG DB user can be found in the Oracle for Goldengate Oracle Installation and setup.
Also note that, Tthere are various installation / configuration steps of OGG that needs a have access to a user with DBA/SYSDBA privs but it doesn't have to be the OGG DB user.

Note 1269274.1 Why does GoldenGate require DBA/SYSDBA privileges in Extract/Replicat

*Use SHOWSYNTAX to debug the replicat and try to see the reason behind this ORA-01031 error. ->

Describes how to view the SQL statement a replicat is executing, showsyntax, nodynsql, nobinarychars (Doc ID 1138329.1)

[ErmanArslansOracleBlog]

*You can also use OGG Logdump utility to display the contents of that RBA.

[ErmanArslansOracleBlog]

*Ensure the permissions as I already mention. There ar permissions required for capture also.

exec dbms_goldengate_auth.grant_admin_privilege('OGG_USER');  --> for both
exec dbms_goldengate_auth.grant_admin_privilege('OGG_USER','capture');
exec dbms_goldengate_auth.grant_admin_privilege('OGG_USER','apply');

*You should also ensure that OS-level permissions are properly set for the directory that trail files, checkpoint and report-related files reside.

*Also ensure that there is nothing like DB vault-type blocker present in the environment.

[Roshan]

Thanks I will check

[Roshan]

Hi,

thanks Erman.

I managed to get the table error. I tried for 2 different RBAs and it the same table

ora12c@dware1:/ogg/ora12c$ ./logdump

Oracle GoldenGate Log File Dump Utility for Oracle
Version 18.1.0.0.0 OGGCORE_18.1.0.0.0_PLATFORMS_180928.0432

Copyright (C) 1995, 2018, Oracle and/or its affiliates. All rights reserved.



Logdump 18 >open /ogg/ora12c/dirdat/cd000000251
Current LogTrail is /ogg/ora12c/dirdat/cd000000251
Logdump 19 >pos 277953568
Reading forward from RBA 277953568
Logdump 20 >detail data
Logdump 21 >ggstoken detail
Logdump 22 >sfh

2019/09/27 17:29:51.000.098 GGSUnifiedUpdate     Len    32 RBA 277953568
Name: CLM_TT.WF_WORKFLOW  (TDR Index: 28)
After  Image:                                             Partition 12   G  b
 0000 000e 0000 000a 0000 0000 0000 0007 2e89 0000 | ....................
 000a 0000 0000 0000 0007 2e89                     | ............
Before Image          Len    18 (x00000012)
BeforeColumnLen     14 (x0000000e)
Column     0 (x0000), Len    10 (x000a)
 0000 0000 0000 0007 2e89                          | ..........

After Image           Len    14 (x0000000e)
Column     0 (x0000), Len    10 (x000a)
 0000 0000 0000 0007 2e89                          | ..........

GGS tokens:
TokenID x58 'X' ALTFORMAT        Info x01  Length    4
 0009 0024                                         | ...$
TokenID x52 'R' ORAROWID         Info x00  Length   20
 4141 4255 4934 4142 5541 4143 4d33 6e41 4143 0001 | AABUI4ABUAACM3nAAC..
TokenID x4c 'L' LOGCSN           Info x00  Length   12
 3236 3636 3039 3133 3838 3638                     | 266609138868
TokenID x36 '6' TRANID           Info x00  Length   13
 302e 3531 2e35 302e 3336 3539 39                  | 0.51.50.36599
TokenID x69 'i' ORATHREADID      Info x01  Length    2
 0002                                              | ..


Logdump 23 >exit
ora12c@dware1:/ogg/ora12c$ ./logdump

Oracle GoldenGate Log File Dump Utility for Oracle
Version 18.1.0.0.0 OGGCORE_18.1.0.0.0_PLATFORMS_180928.0432

Copyright (C) 1995, 2018, Oracle and/or its affiliates. All rights reserved.



Logdump 23 >open /ogg/ora12c/dirdat/cd000000251
Current LogTrail is /ogg/ora12c/dirdat/cd000000251
Logdump 24 >pos 354541248
Reading forward from RBA 354541248
Logdump 25 >detail data
Logdump 26 >ggstoken detail
Logdump 27 >sfh

2019/09/27 17:40:24.000.101 GGSUnifiedUpdate     Len    32 RBA 354541248
Name: CLM_TT.WF_WORKFLOW  (TDR Index: 28)
After  Image:                                             Partition 12   G  b
 0000 000e 0000 000a 0000 0000 0000 0007 2e4b 0000 | .................K..
 000a 0000 0000 0000 0007 2e4b                     | ...........K
Before Image          Len    18 (x00000012)
BeforeColumnLen     14 (x0000000e)
Column     0 (x0000), Len    10 (x000a)
 0000 0000 0000 0007 2e4b                          | .........K

After Image           Len    14 (x0000000e)
Column     0 (x0000), Len    10 (x000a)
 0000 0000 0000 0007 2e4b                          | .........K

GGS tokens:
TokenID x58 'X' ALTFORMAT        Info x01  Length    4
 0009 0024                                         | ...$
TokenID x52 'R' ORAROWID         Info x00  Length   20
 4141 4255 4934 4142 5541 4143 4d36 6241 4144 0001 | AABUI4ABUAACM6bAAD..
TokenID x4c 'L' LOGCSN           Info x00  Length   12
 3236 3636 3039 3432 3035 3737                     | 266609420577
TokenID x36 '6' TRANID           Info x00  Length   13
 302e 3333 2e36 302e 3330 3035 38                  | 0.33.60.30058
TokenID x69 'i' ORATHREADID      Info x01  Length    2
 0001                                              | ..

Regards,

Roshan

[Roshan]

I commented the table from replicat and error is gone. Problem is with the table after I applied patch p27396672_12102171017_SOLARIS64.zip.

[ErmanArslansOracleBlog]

Hmm.. Before the patch, that table named "CLM_TT.WF_WORKFLOW"  was perfectly being replicated using GG, right?
That patch is about "OGG: REPLICAT ABEND W/ ORA-00907 IF ATTRIBUTE VALUE UPDATED".
It changes qmudx.o
It is probably related with XDB and its associated qmu subheap. It seems to be related with the QMU/QMX code layers in the RDBMS.

Very internal and undocumented.

What do you see as a difference in this table (in terms of structure and data) when you compared it with a regular table?
Any errors that you see in the alert log of the related database? and any errors recorded as a user trace file? (this may give us a clue)

[Roshan]

No errors in the alert log/trace file.


The table contains LOB columns.

[ErmanArslansOracleBlog]

Okay lets do this;

set the following event in the related database/databases , reproduce the error and send me the trace file/files;

alter system set events '1031 trace name errorstack level 3; name library_cache level 10';

[Roshan]

What will be the trace file name?

dware11_lmhb_15675.trm?

[ErmanArslansOracleBlog]

It is with suffix .trc , not trm.
Just set the event,  reproduce the error and go to the directory where the your db-trace file exist.
In that directory, check the dates of the files and see the most relevant ones.
Analyze them, search ORA-01031 inside them.. Once you find the actual file, go deeper and analyze the file by all means. Try to see the failing action which is causing thing. And when you find the action, the scope of the problem will be narrowed down, so you can plan a solution for it.