Are you tired to hard develop GoldenGate *.prm files.
I expended some time testing. What nice results.
Look demo video. It’s very easy to GoldenGate mappings.
Good from Oracle Library.
It’s excellent moment, it should help GoldenGate hard administration and DevOps automation.
Hello,
As a second part of last week’s post, here is a way to accomplish that without using audit. Using a simple logon trigger! 🙂
Take a look:
First step: Create a table to store the data.
CREATE TABLE SYS.TRG_LOGON (SCHEMA VARCHAR2(50), SERVER VARCHAR2(200), FAILTIME DATE, ERROR VARCHAR2(200));
More“EM Event: Number of failed login attempts exceeds threshold value [Part 2]”
Hello!
Just got this error? Very simple to check. Below the easy solution using audit:
Activating audit to failed logins:
SQL> audit session whenever not successful; Audit succeeded.
Then wait some time and check:
More“EM Event: Number of failed login attempts exceeds threshold value [Part 1]”
Ok, this is a common issue, once it’s like the default behavior of oracle for DEFAULT profile, used as DEFAULT to new users. But it’s really easy to solve. 🙂
Before expiring you should be received some:
ORA-28002: the password will expire within x days
Ok then, but what if you are facing errors to reuse the same password, don’t know the password and yet, how to never let it happen again?
This might occur in case of crash on host or database node where goldengate is running.
Goldengate maintains information about the process status in the file system, when the server crashes the file that has PID data is not released, and the process status in GGSCI shows erroneous information.
In GGSCI, process status it’s OK:
GGSCI (greporaLAB.net) 7> info mgr Manager is running (IP port greporaLAB.net.7809, Process ID 42064).
If you try to stop process, you will not be able to:
More“GOLDENGATE process show RUNNING status, when not RUNNING.”
Have this crazy in ggserr.log?
Source Context : SourceModule : [er.redo.ora] SourceID : [/scratch/aime/adestore/views/aime_stuya22/oggcore/OpenSys/src/app/er/redo/oracle/redoora.c] SourceFunction : [REDOORA_handle_read_error(errmsg_t &)] SourceLine : [11630] ERROR OGG-02077 Extract encountered a read error in the asynchronous reader thread and is abending: Error code 1683, error message: ORA-01683: unable to extend index . partition by in tablespace.
Check db alert_*.log, you should find some alert.
ORA-1688: unable to extend table SYS.WRH$_ACTIVE_SESSION_HISTORY partition WRH$_ACTIVE_1470969483_24757 by 128 in tablespace SYSAUX
ORA-1688: unable to extend table SYS.WRH$_ACTIVE_SESSION_HISTORY partition WRH$_ACTIVE_1470969483_24757 by 128 in tablespace SYSAUX
Resolving issue:
alter tablespace SYSAUX add datafile '+DG' size 1g;
Some options are:
Reduce AWR retention:
SQL> SELECT extract(day from snap_interval) *24*60+extract(hour from snap_interval) *60+extract(minute from snap_interval) snapshot_Interval, extract(day from retention) *24*60+extract(hour from retention) *60+extract(minute from retention) retention_Interval FROM dba_hist_wr_control; SQL> exec DBMS_WORKLOAD_REPOSITORY.modify_snapshot_settings(retention => 10800, interval => 10);
Reduce Statistics Level:
SQL> show parameter STATISTICS_LEVEL NAME TYPE VALUE --------------------------------------------------------- statistics_level string ALL SQL> alter system set STATISTICS_LEVEL = TYPICAL scope=both sid='*';
Type your message when beep 🙂
Hello!
Some time ago I found some ORA-00060: Deadlock detected. errors in a client OEM database… Like this:
Thu Dec 22 09:01:55 2016 ORA-00060: Deadlock detected. More info in file /oracle/oemdb/diag/rdbms/oemdb/oemdb/trace/oemdb_ora_1757.trc. Thu Dec 22 09:02:07 2016 ORA-00060: Deadlock detected. More info in file /oracle/oemdb/diag/rdbms/oemdb/oemdb/trace/oemdb_ora_1759.trc. ORA-00060: Deadlock detected. More info in file /oracle/oemdb/diag/rdbms/oemdb/oemdb/trace/oemdb_ora_1759.trc.
In summary, after investigating the trace (as per below), found that the issueis caused by the following command:
More“EM Repository: ORA-00060: Deadlock detected error in alert log”
Can’t umount Red-Hat filesystem with error “This utility only unmounts cifs filesystems” either with force?
[@Linux-redhat5 ~]$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.11 (Tikanga)
ERROR:
[@Linux-redhat5 /]# umount /cifsfilesystem/data/custom This utility only unmounts cifs filesystems. This utility only unmounts cifs filesystems. This utility only unmounts cifs filesystems.
Hey!
Strange question, right? You should know you applications and databases and how everything works, right?
Happen that some days ago a client requested me to identify from which database is a service_name. Easy? Not if the server have 46 database instances running…
Ok, now how can I can this information as quick as possible?
I know that the command below give me all distinct databases in CRS:
/u01/app/12.1.0.2/grid/bin/crsctl stat res -t -w "TYPE = ora.database.type"
Now, lets make some sed magic:
[root@nprd01dbadm01 ~]# /u01/app/12.1.0.2/grid/bin/crsctl stat res -t -w "TYPE = ora.database.type" |grep ora. |sed 's/ora./srvctl status service -d /' |sed 's/.db/ |grep \$1/' | head -1 srvctl status service -d dba |grep $1
More“Shellscript: Which database is this service_name from?”
To connection between unix machine with teradata environment is needed to install ODBC Driver and some others components (dependencies). All Items can be found in Teradata Downloads site: https://downloads.teradata.com/
Teradata OBDC Driver has 3 dependecies:
1. Shared common components for Internationalization (TDICU)
2. Teradata GSS client package (TeraGSS)
3. Teradata Tools and Utilities Base (TTU)
After download all items, run as root: rpm -ivh “component_name” –nodeps
Eg: rpm -ivh teragss1510-15.10.02.06-1.noarch.rpm --nodeps
Use “–nodeps” only to not need to install in order