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
Would you to clone some GoldenGate home, but you have too many extract / pump / replicats?
It will take an eternal day?
Try to use this script:
How to autostart GoldenGate services after system startup?
On Linux: /etc/rc.local
#Auto start GoldenGate
su - oracle -c "/oracle/goldengate/./ggsci paramfile startGG.obey"
On GoldenGate ggsci path, create follow file:
echo "start mgr" > startGG.obey
GGSCI 1> edit params mgr
AUTOSTART er *
AUTORESTART er *,RETRIES 5,WAITMINUTES 5,RESETMINUTES 30
It’s a recurrent subject, right? But no one is 100% sure to how figure this out… So, let me quickly show you my way:
– Physical CPUs (sockets):
[root@mysrvr ~]# grep -i "physical id" /proc/cpuinfo | sort -u | wc -l
[root@mysrvr ~]# dmidecode -t processor |grep CPU
Version: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz
Version: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz
So, 2 physical CPUs.
– Physical Cores
[root@mysrvr ~]# egrep -e "core id" -e ^physical /proc/cpuinfo|xargs -l2 echo|sort -u
physical id : 0 core id : 0
physical id : 0 core id : 1
physical id : 0 core id : 2
physical id : 0 core id : 3
physical id : 1 core id : 0
physical id : 1 core id : 1
physical id : 1 core id : 2
physical id : 1 core id : 3
Each one of Physical Processors has 4 cores.
So, there is two quad-cores. This way, we have 8 cores at all.
– Logical CPUs
[root@mysrvr ~]# grep -i "processor" /proc/cpuinfo | sort -u | wc -l
Ok, so we have cores in double.
This means we have Hyper-Threading (technology by Intel Processors).
Not so hard, right?
Those links are similar and quite cool to understand the concepts:
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.
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 126.96.36.199, 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).
Do you know the difference between “tail -f” and “tail -F”?
Ok, don’t feel bad. It’s very difficult to find someone who knows… And with a reason, I can’t find any link explaining this by Googling.
It’s possible that I don’t know how to search it too. But I searched as I’d search if I didn’t know that… And couldn’t find anything about…
Let’s take a look on –help, so:
It’s very common to automate application startup in rc.local on Linux systems.
Was testing Red Hat 7.2 (Maipo), and found that apps was’t started.
Found this on some Red Hat blog:
“Systemd is a system and service manager for Linux operating systems. It is designed to be backwards compatible with SysV init scripts, and provides a number of features such as parallel startup of system services at boot time, on-demand activation of daemons, support for system state snapshots, or dependency-based service control logic. In Red Hat Enterprise Linux 7, systemd replaces Upstart as the default init system.”
On default /etc/rc.local comes useful info:
# THIS FILE IS ADDED FOR COMPATIBILITY PURPOSES
# It is highly advisable to create own systemd services or udev rules
# to run scripts during boot instead of using this file.
# In contrast to previous versions due to parallel execution during boot
# this script will NOT be run after all other services.
# Please note that you must run ‘chmod +x /etc/rc.d/rc.local’ to ensure
# that this script will be executed during boot.
Then, this ‘chmod’ turns rc.local enable during system startup.
To familiarize this new feature:
[root@somesystem~]# systemctl status rc-local
● rc-local.service - /etc/rc.d/rc.local Compatibility
Loaded: loaded (/usr/lib/systemd/system/rc-local.service; static; vendor preset: disabled)
Active: active (running) since Mon 2016-07-11 13:16:18 BRT; 28min ago
Process: 1046 ExecStart=/etc/rc.d/rc.local start (code=exited, status=0/SUCCESS)
├─2272 /bin/sh /oracle/domains/mywl_domain/startWebLogic.sh
├─2284 /bin/sh /oracle/domains/mywl_domain/bin/startWebLogic.sh
├─2374 /bin/sh /oracle/domains/mywl_domain/bin/startNodeManager.sh
├─2377 /bin/sh /oracle/binaries/wlserver/server/bin/startNodeManager.sh
├─2428 /oracle/jdk1.7.0_25/bin/java -Dwls.home=/oracle/binaries/wlserver/server -Dweblogic.home=/oracle/binaries/wlserver/server -server -Xms1g -Xmx1g -XX:MaxPermSize=512m -Dcoherence...
└─2442 /oracle/jdk1.7.0_25/bin/java -server -Xms1g -Xmx1g -XX:MaxPermSize=512m -Dweblogic.Name=AdminServer -Djava.security.policy=/oracle/binaries/wlserver/server/lib/weblogic.policy .
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