Hello everyone!
I already wrote a post about it but I think I was not clear and easy to find enough. So let me make another post about and add some information…
Ok, are you facing a “java.sql.SQLException: ORA-28040: No matching authentication protocol” after upgrade your database to 12c?
It’s related to old jdbc driver version in your application. Please review matrix available in this post and check your application. The MOS noted below have good information about it…
Hello!
Have you ever killed a session in database and the session doesn’t disappear? Or yet, you killed the SPID of the session in OS and the session still running in database, but now you cannot see the SPID?
Very weird, but it happens. First of all, let us point some interesting items:
Hello!
Having this error from cell alerthistory.log? Don’t panic!
Take a look in MOS: Exadata Storage Cell reports error RS-7445 [Serv MS Leaking Memory] (Doc ID 1954357.1). It’s related to Bug – RS-7445 [SERV MS LEAKING MEMORY].
The issue is a memory leak in the Java executable and affects systems running with JDK 7u51 or later versions. This is relevant for all versions in Release 11.2 to 12.1.
What happens is that MS process is consuming high memory (up to 2GB). Normally MS use around 1GB but because of the bug the memory allocated can grow upt to 2GB. You can check it as per example below:
[root@exaserver ~]# ps -feal|grep java 0 S root 16493 14737 0 80 0 - 15317 pipe_w 18:34 pts/0 00:00:00 grep java 0 S root 22310 27043 2 80 0 - 267080 futex_ 18:15 ? 00:00:27 /usr/java/default/bin/java -Xms256m -Xmx512m -XX:-UseLargePages -Djava.library.path=/opt/oracle/cell/cellsrv/lib -Ddisable.checkForUpdate=true -jar /opt/oracle/cell/oc4j/ms/j2ee/home/oc4j.jar -out /opt/oracle/cell/cellsrv/deploy/log/ms.lst -err /opt/oracle/cell/cellsrv/deploy/log/ms.err
Note that: 267080 * 4096 = 1143MB (1GB). If your number is higher than this, it indicates the presence of the bug.
More“RS-7445 [Serv MS leaking memory] [It will be restarted] [] [] [] [] [] [] [] [] [] []”
Are you bored with GoldenGate objects with no supplemental log on Oracle Database?
This script will check ALL tables in GG PRM, after check on database supplemental log information.
PRM, dblogin should be changed.
Try this script on crontab:
vi gg_trandata_checkup.sh
cd $GGATE
echo > gg.out
echo "dblogin USERID @ PASSWORD > template_check.tmp
echo "" >> template_check.tmp
cat dirprm/ext_1.prm|grep -i TABLE|awk {' print $1" "$2 '}|awk -F"," {' print $1 '}|sed 's/TABLE/INFO TRANDATA/g' >> template_check.tmp
./ggsci -s gg.out
obey template_check.tmp
EOF
cat gg.out|sed '/^$/d'|grep -v ": ALL."|grep -v -i "info trandata"|grep -v "data is enabled for table"|grep -v "ERROR OGG-01784"
Mail this to GGAdmins.
Maiquel.
Hi all!
I was asked to make a conversion from T-SQL (MSSQL) Procedure to PL/PGSQL. Regarding how boring is this task, the follow link helped me:
http://www.sqlines.com/online
I highly recommend it. The site has a commercial solution to convert all database, but some code can be converted online for free. 🙂
The conversion not fixed at all, but make a good part of the work… And all help is helpful…
More“Converting Between SQLServer, Oracle, PostgreSQL, MySQL, Sybase and others…”
When we use extraction process with certain macro filters, and send the trails to a goldengate with JAVA adapter, the java extract process fails with the following error: OGG-00354 Invalid BEFORE column:(column_name).
EXTRACT PROCESS
EXT01 exttrail ./dirdat/e1, FORMAT RELEASE 11.1 GETUPDATEBEFORES include ./dirmac/filter.mac TABLE OWNER01.TABLE01, #filter01();
PUMP PROCESS
PUMP01 rmthost ggjava.net rmttrail ./dirdat/j1 , format release 11.1 GETUPDATEBEFORES TABLE OWNER01.TABLE01;
EXTRACT GG JAVA
EXTRACT JAVA01 GETUPDATEBEFORES TABLE OWNER01.TABLE01;
In some cases, this issue can be resolved just removing the clause “GETUPDATEBEFORES”, as reported in the Oracle note (Doc ID 2151605.1). But in some environments this procedure not resolve, because it is an undocumented bug in goldengate JAVA 11.1, which is caused by the use of format release 11.1.
This same process has been testing in goldengate 12.1, with format release 12.1, and the problem not occurs.
The solution is the upgrade! \o/
Dieison.
Hi guys!
I already posted about Hang Analyze (part1, part2) and ASHDUMP. Now, in the same ‘package’, let me show you about SYSTEMSTATE DUMP.
Systemstate is basically made by the process state for all process in instance (or instances) at the time the systemstate is called.
Through a systemstate it’s possible to identify enqeues, rowcache locks, mutexes, library cache pins and locks, latch free situations, and other kind of chains.
It’s a good tool to add in a SR, but it’s quite hard to habituate on reading/interpreting the file. To undertand exactly how to read a systemstate I’d recommend you the best: Read the manual!
The doc Reading and Understanding Systemstate Dumps (Doc ID 423153.1) has a very good explanation with examples, I’m not able to to it better. 🙂
What I can do is share about the SYSTEMSTATE levels. I had some difficult to find it…
But before I show how you can do it, it’s important to mention that Oracle does not recommend you to use ‘numeric events’ without a SR (MOS), according to Note: 75713.1.
Hi guys!
In the last weeks I talked about ASHDUMP in the post HANGANALYZE Part 1. Let’s think about it now…
Imagine the situation: The database is hanging, you cannot find what is going on and decided to restart the database OR your leader/boss yelled to you do it so, OR you know the database is going do get down, anyway…
Everyone has passed by this kind of situation at least once. After restart everything become OK and the ‘problem’ was solved. But now you are being asked about RCA (what caused this situation?). The database was hanging, so no snap was closed and you lost the ASH info…
For this cases I think is very useful to take 1 minute before database get down to generate an ASHDUMP. It’s very simple:
More“ASHDUMP for Instance Crash/Hang ‘Post Mortem’ Analysis”
How to check which ODI repository component/version is created?
HOT SQL:
SELECT COMP_ID,COMP_NAME,OWNER,VERSION FROM SCHEMA_VERSION_REGISTRY;
Maiquel.
This steps should still be performed in SQLserver Host:
The pump process configuration is very simple, its only function is to transport the trail files to destination.
ADD extract P_MSQL, exttrailsource ./dirdat/tr
C:\goldengate> edit param P_MSQL
extract P_MSQL SOURCEDB db0sql1, USERID ggate, PASSWORD ?????? CACHEMGR CACHESIZE 2GB rmthost teradata1.net, mgrport 8809 rmttrail ./dirdat/td --TABLE MAP TABLE dbo.DLOG_ERRORS; TABLE dbo.SAC_DATA; TABLE dbo.SAC_LIST; TABLE dbo.SAC_TITLE;
Still in the SQLserver Host, is need to create a definition file, wich will be used in gg-teradata.
First, create a “tables.def” file that should contain a dblogin and tables that will be replicated.
defsfile tables_sqlserver.sql purge SOURCEDB db0sql1, USERID ggate, PASSWORD ?????? TABLE dbo.DLOG_ERRORS; TABLE dbo.SAC_DATA; TABLE dbo.SAC_LIST; TABLE dbo.SAC_TITLE;
More“GoldenGate: Replicate data from SQLServer to TERADATA – Part 2”