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.
Problem:
In weblogic 11G, there are several JFR files in /tmp directory:
root@app1wsora3 tmp]# pwd; find . -name *.jfr |xargs ls -tlhr
/tmp
-rw——- 1 oracle oinstall 0 Aug 11 18:41 ./2016_06_02_13_50_22_4317/2016_08_11_18_41_43_4317.jfr
-rw——- 1 oracle oinstall 37M Aug 11 18:41 ./2016_06_02_13_50_22_4317/2016_08_01_11_22_51_4317.jfr
-rw——- 1 oracle oinstall 14M Aug 16 09:25 ./2016_06_02_13_50_15_4341/2016_08_16_03_24_12_4341.jfr
-rw——- 1 oracle oinstall 0 Aug 16 12:02 ./2016_06_02_13_50_15_4341/2016_08_16_12_02_02_4341.jfr
-rw——- 1 oracle oinstall 14M Aug 16 12:02 ./2016_06_02_13_50_15_4341/2016_08_16_09_25_39_4341.jfr
-rw——- 1 oracle oinstall 0 Aug 16 12:43 ./2016_06_02_13_50_24_4344/2016_08_16_12_43_28_4344.jfr
-rw——- 1 oracle oinstall 150M Aug 16 12:43 ./2016_06_02_13_50_24_4344/2016_08_16_12_17_36_4344.jfr
These files are from DMS (Dynamic Monitoring Service) and they are created when application server is running.
I was taking high workload with data load methods, so I decided to move out of comfort zone and fortunately discovered a excellent way to copy/move high data volume with GoldenGate Initial Load.
It’s well documented by Oracle and gavinsoorma.com (best and simple one).
# On source GoldenGate (ggsci>):
GGSCI> ADD EXTRACT load1, SOURCEISTABLE GGSCI> EDIT PARAMS load1 EXTRACT load1 userid ggate@goldengate RMTHOST target-mgr.grepora.com, MGRPORT 7809 RMTTASK replicat, GROUP load2 FORMAT LEVEL 4 ---Loading tables map CUSTOMER.TABLE1;
After migrating database to another host, port or SID, the error below started to happen when running a scenario.
“Of course” all mapped connection was right setted on Topology… But environment is complex, it’s possible something is missing…
java.sql.SQLException: Io Exception: The Network Adapter could not establish the connection at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:274) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:328) at oracle.jdbc.driver.PhysicalConnection.(PhysicalConnection.java:361) at oracle.jdbc.driver.T4CConnection.(T4CConnection.java:151) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:595) at com.sunopsis.sql.SnpsConnection.u(SnpsConnection.java) at com.sunopsis.sql.SnpsConnection.c(SnpsConnection.java) at com.sunopsis.sql.h.run(h.java)
Ok, so something really is missing… But where?
Try to check this:
More“ODI 10gR1: Connection to Repository Failed after Database Descriptor Change”
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.
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.”
According Oracle guys, Apache 2.4 its is a vanila module to Weblogic 12c and same module runs with Weblogic 11g.
Modules are available to download: https://blogs.oracle.com/WebLogicServer/entry/announcing_web_socket_proxy_and
# httpd -version Server version: Apache/2.4.6 (Red Hat Enterprise Linux) Server built: Mar 21 2016 02:33:00
On httpd.conf is necessary to load Apache 2.4 module
LoadModule weblogic_module modules/lib/mod_wl_24.so
Hello guys,
Today I’m going to introduce the Coherence Server Out-of-Process configuration.
Once this configuration has changed a lot between versions 11G to 12C, the post will be a little bit more detailed (than usual).
The table below summarize these changes:
| From | To |
| osb-coherence-cache-config.xml | Coherence Cache Config resource |
| osb-coherence-override.xml | Coherence Cluster resoruce |
| Out-Of-Process Cache Server | New WLS node/cluster |
Follow the steps:
More“Configuration Coherence Server Out-of-Process in OSB 12C”
Hi,
Today, let’s to configure weblogic services startup, when machines starts.
In some blogs, we can find a bunch of customized scripts that create and set variables to startup the adminservers, nodemanagers and managed server, but, in my case, i just need to start adminserver and nodemanger, when machines start just after an incident.
For this situation, we need that the startup of application do not interrupt the operation system startup.
*The operation system in subject is Red-Hat 6.5
Hi.
Today, let’s talk about Java Message Systems (JMS), the reason led me talk about this, is that my environment, a complex architecture of messages where we have more of two hundred queues in the same domain.
The administration of queues in the weblogic console is very simple, but, if you need to remove a million messages, in a hundred queues, you have a problem!
To turn more agile the visualization of messages, state and other queue properties, nothing better than to use WLST.
This post shows a script, which can grow up where you imagine, for while the script have just three options (the most useful to me) and nothing prevents to have more.
