Hey folks! As a database administrator, one of the questions I often get is, "How can I tell if my extract is a classic extract or an integrated extract?" It's a great question, and I'm here to make it easy and fun to understand.To figure out whether your extract is classic or integrated, you simply need to look at the output of a specific command.
Here’s how you can do it:
Step 1: Check the Extract Info
Run the following command in GGSCI:
Run the following command in GGSCI:
GGSCI (localhost.oracledbahelpblog.com as gguser@prodsng1) 78> info extract extint
If your output looks like this, with "Oracle Integrated Redo Logs" under the Log Read Checkpoint, it means you have an integrated extract :
EXTRACT EXTINT Last Started 2024-05-19 23:39 Status STOPPED
Checkpoint Lag 00:00:04 (updated 00:02:13 ago)
Log Read Checkpoint Oracle Integrated Redo Logs
2024-05-19 23:36:32
SCN 0.1065738 (1065738)
Step 2: Compare with any other Extract Output
Alternatively, if you see "Oracle Redo Logs" under the Log Read Checkpoint, then it’s a classic extract:
GGSCI (localhost.oracledbahelpblog.com as gguser@prodsng1) 79> info extcls
EXTRACT EXTCLS Last Started 2024-05-20 00:50 Status RUNNING
Checkpoint Lag 00:00:00 (updated 00:00:03 ago)
Process ID 16352
Log Read Checkpoint Oracle Redo Logs
2024-05-20 00:52:12 Seqno 25, RBA 19285645
SCN 0.1385764 (1385764)
Summary
So, next time you're scratching your head wondering whether you’re dealing with a classic or integrated extract, just remember to check the "Log Read Checkpoint" section in your extract info. It's that simple! Keep those databases running smoothly and happy replicating ! 😉😊
So, next time you're scratching your head wondering whether you’re dealing with a classic or integrated extract, just remember to check the "Log Read Checkpoint" section in your extract info. It's that simple! Keep those databases running smoothly and happy replicating ! 😉😊
No comments:
Post a Comment