Due to ease in which we can go to the future or return to the past using Goldengate, it becomes increasingly necessary recover archives from backup, sometimes it is necessary to recover a several days.
To do it, generally we need large disk space, at this time, starts a searching for storage disks.
After finding a disk, is need to mount it, i performed with simply mount options in AIX.
ORA-06512 ORA-48168 ORA-12012 for ADR Job Raising Errors
A database is raising stack below on alertlog:
Errors in file /db/u7011/oracle/admin/MYDB/trace/MYDB_j002_22935.trc: ORA-12012: error on auto execute of job "SYS"."DRA_REEVALUATE_OPEN_FAILURES" ORA-48168: the ADR sub-system is not initialized ORA-06512: at "SYS.DBMS_IR", line 522
More“ORA-06512 ORA-48168 ORA-12012 for ADR Job Raising Errors”
Hi all!
After add a datafile in PRIMARY database, the STANDBY MRP stopped. An “ALTER DATABASE RECOVER MANAGED STANDBY DATABASE” does not solved te problem, as you see:
SQL> SELECT SEQUENCE#, Name, APPLIED FROM V$ARCHIVED_LOG where APPLIED 'YES' and SEQUENCE# ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION; Database altered. SQL> SELECT SEQUENCE#, Name, APPLIED FROM V$ARCHIVED_LOG where APPLIED 'YES' and SEQUENCE# < (select max(SEQUENCE#) -1 from V$ARCHIVED_LOG); SEQUENCE# NAME APPLIED ---------- -------------------------------------------------------------------------------- --------- 15075 /db/u1004/oracle/admin/MYDB/arch/arch_1_823102978_15075.arc NO
More“After adding Datafile in Primary the MRP Stopped in Physical Standby (Dataguard)”
Hey everyone,
Finally, the last part of our flashback posts, FLASHBACK DATA ARCHIVE! If you didn’t have a chance to check the previous posts, please do not hesitate to take a look if you need or if you just get curious.
Flashback – Part 1 (Flashback Drop)
Flashback – Part 2 (Flashback Query)
Flashback – Part 3 (Flashback Versions Query)
Flashback – Part 4 (Flashback Transaction Query)
Flashback – Part 5 (Flashback Table)
Flashback – Part 6 (Flashback Database)
Well, there we go then 🙂
Hi,
Today, as in another normal days, I found a problem with ODI schedule in the newly created enviroment. While creating a schedule to scenario execution, then clicked in update schedule in Topology > Agents > OracleDIAgent, I received an exception:
ODI-1274: Agent Exception Caused by: Could not find the AgentScheduler instance in order to process 'OdiComputePlanning' request
Oracle support has a solution for this exception, but only for ODI 12c, it happens that my enviroment is ODI 11.1.1.6, in community oracle, has the same question, but, without answer.
As you know, since 11g we have a Automatic Diagnostic Repository (ADR). To better manage it, we also have a Command-line Interface, called ADRCI.
ADR contains all diagnostic information for database (logs, traces, incidents, problems, etc).
More“ADRCI Retention Policy and Ad-Hoc Purge Script for all Bases”
Hi people,
We’re almost there to finish this Flashback Tutorial 🙂
To check the previous posts, please go through:
Flashback – Part 1 (Flashback Drop)
Flashback – Part 2 (Flashback Query)
Flashback – Part 3 (Flashback Versions Query)
Flashback – Part 4 (Flashback Transaction Query)
Flashback – Part 5 (Flashback Table)
Flashback – Part 7 (Flashback Data Archive)
Today’s post is gonna be about Flashback Database, a pretty good feature for non-production levels of your structure, I would say.
It’s very unlikely that you are going to rollback your entire production database to a point-in-time in the past, right? But if you need to, this facility is there.
Why do I say that it is great for non-production environments?
More“Flashback – Part 6 (Flashback Database)”
A few months ago, i had a problem in Persistence Store of JMS queues, soon after perform server restart, I get error from persistence store to recover message:
weblogic.store.PersistentStoreFatalException: [Store:280064]invalid handle 55981 (server="EVENTS01" store="JDBCStore_3022" table="JDBCStore_3022WLStore"),
To resolve this problem, just add this parameter on server startup arguments:
-Dweblogic.store.StoreBootOnError = true
With this parameter, the server starts with OK status in WebLogic 11g and with FAILED status in Weblogic 12c, but in both the processing of the messages continues when active,
to remove FAILED status in Weblogic 12c, just need to truncate persistence table in database and restart server (This solution can be found in Oracle Docs).
This solution did not solved my problem, because I can’t lost or delete messages.
Let’s go analyse the problem:
More“Avoiding lost messages in JDBC Persistent Store, when processing Global Transactions with JMS.”
Hi all,
What if your arch processes hangs or get killed? How to keep archive going without restart database?
Take a look…
Hi everybody,
Today we are going to discuss about FLASHBACK TABLE. As usual, first, I am tagging here the previous posts about Flashback Technology, so feel free to check it out if you want:
Flashback – Part 1 (Flashback Drop)
Flashback – Part 2 (Flashback Query)
Flashback – Part 3 (Flashback Versions Query)
Flashback – Part 4 (Flashback Transaction Query)
Flashback – Part 6 (Flashback Database)
Flashback – Part 7 (Flashback Data Archive)
So let’s do it people.
