Amazon books

Monday, October 28, 2013

Using log dump to find operations in a table between interval time - GoldenGate

1-Open the trace file

Logdump 2 >open eb000025
Current LogTrail is /ggshop/bwdhdbpr025/gghome/dirdat/eb000025

2-Set time interval
Logdump 4 >filter starttime 2013-10-28 11:30
Logdump 5 >filter endtime 2013-10-28 11:59

3-Match all tables and show
Logdump 6 >filter match all
Logdump 7 >filter show
Logdump 8 >count

4-Or check for only one table
Logdump 11 >filter filename TABLE_NAME

####################################################
###### Output example ######
####################################################
SCHEMA.TABLE1                       Partition 4
Total Data Bytes             70524
  Avg Bytes/Record            1410
Insert                          16
LargeObject                     34
After Images                    50
####################################################



Best Regards,
Paulo Portugal

Friday, October 25, 2013

Enable all DDL Commands to be Logged in Alert.log file - Oracle Database 12c

With this simple command below you can enable all DDL commands to be logged in alert.log

ALTER SYSTEM SET enable_ddl_logging = TRUE ;


Best Regards,
Paulo Portugal

Thursday, October 24, 2013

Veridata Agent problem. Job Hang in one table.

If your veridata job is running forever , check if you are in 11.2.0.0 version.

I got this error on my veridata agent log:

ERROR:2013-10-24 16:03:50,524 (Session: 1098) - An unexpected exception has occurred: null [RowHashQuery:getCompletion, line 315]
java.lang.ArrayIndexOutOfBoundsException
        at com.goldengate.veridata.db.OracleDatabase$OracleRawTimestampColumnMapper.getBytes(OracleDatabase.java:841)
        at com.goldengate.veridata.db.BaseQuery.packRow(BaseQuery.java:134)
        at com.goldengate.veridata.db.RowHashQuery.call(RowHashQuery.java:112)
        at com.goldengate.veridata.db.RowHashQuery.call(RowHashQuery.java:34)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
        at java.util.concurrent.FutureTask.run(FutureTask.java:149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
        at java.lang.Thread.run(Thread.java:738)


--Solution
Apply patch 11.2.0.1  on all your veridata agents.


Best Regards,
Paulo Portugal

Wednesday, October 23, 2013

GoldenGate JAgent not starting - FIXED!

Trying to start jagent got this error below:

[hostname]/ggshop/bwdhdbpr052/gghome>  java -jar -Xms64m -Xmx512m dirjar/jagent.jar
0    [main] INFO  com.goldengate.monitor.jagent.JAgentWSMain  - About to call initialize on the WebService
997  [main] INFO  com.goldengate.monitor.jagent.config.impl.AgentInfoImpl  - Using IP address 10.3.0.33 to connect to the Manager Web Service
1002 [main] ERROR com.goldengate.monitor.jagent.JAgentWSMain  - Error Initializing JAgent. JAgent will not be initialized and about to return. Exception: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'agentBootstrapper': Injection of resource dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'agentInfo': Invocation of init method failed; nested exception is java.lang.NumberFormatException: For input string: "number"
1002 [main] INFO  com.goldengate.monitor.jagent.JAgentWSMain  - JAgentWSMain is about to terminate its operation
1003 [Shutdown Thread.] INFO  com.goldengate.monitor.jagent.JAgentWSMain  - JAgent is about to shutdown.
1004 [Shutdown Thread.] INFO  com.goldengate.monitor.jagent.JAgentWSMain  - JAgent shutdown process is completed successfully.

--Solution
1-Edit mgr.prm file and remove all comments before the line that specify the Manager port:
--Port of Manager -------REMOVE THIS LINE
"port 7809"


Best Regards,
Paulo Portugal