Need to configure first GoldenGate data replication?
Should be hard to configure?
Which strategies should I check?
What step may I do?
Need to configure first GoldenGate data replication?
Should be hard to configure?
Which strategies should I check?
What step may I do?
Hello all,
Yeah, these days I got some errors and when validating the server found the fllowing error:
su: cannot set user id: Resource temporarily unavailable
As you can imagine, in order to fix the issue, I adjusted the /etc/security/limits.conf increasing oracle nprocs to:
oracle soft nproc 4047 oracle hard nproc 20384
Ok, turns out that after a while I got the same errors again…
After some investigating I find that the EM Agent process was with 5020 threads!
Take a look:
Have you read last ‘Failure unregister integrated extract’ and still impossible to unregister Integrated Extract on Oracle Database?
Is it’s ‘Impossible mission’ to unregister extract?

Struggling with that, right?
As you know, in Oracle Database 9i the view V$SESSION doesn’t have SQL_ID column…
So how to map SQLs in my database? And, for example, how to get the SQLs causing a lock?
In the end of the day, the SQL_ID is only a representation of the hash_value of an SQL. You can even make the translation from SQL_ID to Hash Value as you can check on this post by Tanel Poder.
Ok, but I have to map which sql is causing the lock in my 9i database, how can I do that?
Here it goes:
If session status is ACTIVE:
SELECT s1.sql_text from v$sqlarea s1,v$session s2 where s2.SID=&sid and s2.SQL_ADDRESS = s1.ADDRESS
If session status is INACTIVE:
SELECT s1.sql_text from v$sqlarea s1,v$session s2 where s2.SID=&sid and s2.prev_sql_addr = s1.ADDRESS
You’re welcome! 😉
See you next week!
Hi.
If you search solutions to this Error, you will perceived only one documented root cause:
Error:
OGG-01411 Cannot convert input file ./dirdat/xx000549 with format RELEASE 9.0/9.5 to output file ./dirdat/zz000034 with format RELEASE 12.1.
Cause:
“The output trail of the data pump has a different format (version) than the input trail of the data pump”
If you are using GG 12.1 version, and all trails (rmttrail and exttrail) are correctly set with “format release”, you fell into a bug.
Oracle recommend to do upgrade to GG 12.2.
To work around this issue and start process, you need write a new trail, perform etrollover and reposition pump process.
On the Target System, process works fine, but not receive new trails, because pump process are abended.
GGSCI (lab2.grepora.net) 001> info rep01
REPLICAT rep01 Last Started 2017-03-20 12:08 Status RUNNING
Checkpoint Lag 00:00:00 (updated 00:00:09 ago)
Process ID 13563
Log Read Checkpoint File ./dirdat/zz000034
2017-03-22 09:53:31.004144 RBA 30683971
After deploy GoldenGate with downstream database option archives from downstream database not cleaning ? All database transaction are gracefull, but archives (from downstream) are not cleaning?
Are no log transactions registered on GG Extract?
check this:
GGSCI (dbcloud) 3> send ETL01 showtrans Sending SHOWTRANS request to EXTRACT ETL01 ... Oldest redo log files necessary to restart Extract are: ------------------------------------------------------------ XID: 14.6.3931092 Items: 1 Extract: ETL01 Redo Thread: 1 Start Time: 2017-00-00:00:00:00 SCN: 1682.4049305132 (7228184297004) Redo Seq: 8612 Redo RBA: 20965491728 Status: Running ------------------------------------------------------------
If you on same case, make this:
It should reach (and delete) JUST archived log that have already read by GoldenGate.
set serveroutput on size unlimited set line 1000 set trimsp on set feed off set pages 5000 set pagesize 0 spool [[ some_dir ]]/delete_archives__dowstream_goldengate.sh -- SR 3-14409179111 - Golden Gate Configuration, How To Delete Archive Logs From Downstream Database (Doc ID 2011174.1) SELECT 'rm ' || r.NAME -- case when (r.next_scn > c.required_checkpoint_scn) then 'NO' else 'YES' end purgable FROM DBA_REGISTERED_ARCHIVED_LOG r, DBA_CAPTURE c WHERE r.CONSUMER_NAME = c.CAPTURE_NAME and r.source_database = c.source_database and r.next_scn < ( select min(required_checkpoint_scn) from dba_capture where captur e_type='DOWNSTREAM') and purgeable='YES' order by modified_time; spool off
Schedule the output in automation tool (crontab / dba_job / windows job scheduler, (whatever)):
Quick one today!
Having message below in your 11.2.0.3 on AIX like this?
WARNING: Heavy swapping observed on system in last 5 mins. pct of memory swapped in [31.28%] pct of memory swapped out [3.81%]. Please make sure there is no memory pressure and the SGA and PGA are configured correctly. Look at DBRM trace file for more details.
Stand down, this issue is caused by unpublished Bug 11801934, mentioned in MOS False Swap Warning Messages Printed To Alert.log On AIX (Doc ID 1508575.1).
Basically happens because the v$osstat does not reflect proper stats for the swap space paging.
So, stay calm and see you next week!
GoldenGate Extract / Replicat abend with bellow error:
Source Context : SourceModule : [ggdb.ora.sess] SourceID : [/scratch/aime/adestore/views/aime_stuya22/oggcore/OpenSys/src/gglib/ggdbora/ocisess.c] SourceFunction : [OCISESS_context_def::oci_try(int, const char *, ...)] SourceLine : [832] 2017-04-19 07:52:07 ERROR OGG-00665 OCI Error executing single row select (status = 3113-ORA-03113: end-of-file on communication channel)
It’s is a common stuff in Oracle Database not stable or it’s taking some 00600.
Review items:
Suggest you to review ‘Master Note: Troubleshooting ORA-03113 (Doc ID 1506805.1)‘ on Oracle support services and keep database away from ORA-03113.
🙂
Hi all,
Getting this error? OMS 12.1.0.3?
Ok… After an investigation on MOS and also a SR opened with Oracle is was pointed to relation with Bug 17575631 CLUSTER DB HOME PAGE ERRORS- REGIONS FETCH REAL TIME DATA WILL NOT BE DISPLAYED on Database Plugin.
It’s solved in OMS 12.1.0.4 and also in 12.1.0.5.1 EM Database Plugin Bundle patch.
I’ll show you how to workaround it. 🙂
Hi all!
This days I faced some ORA-600 as per below in a database:
ORA-00600: internal error code, arguments: [13030], [20], [], [], [], [], [], [], [], [], []
Checking for error in Database I find it was related to a pretty complex UPDATE, as per:
More“ORA-00600: internal error code, arguments: [13030], [20]”