Hi everyone,
Sometimes we need to connect to the database using an unusual schema that we don’t even know the password, maybe because it was created through a script in a release or the latest DBA never stored it somewhere public or maybe due to any other reason (whatever, right? you just need to connect there and end of the story), but anyhow, you need to login using this schema specifically (to create/delete synonyms, dblinks, jobs etc…). How would you do that without the password?
Hi all!
As the oldest readers know, someday I had to found some entries in the alertlog and I had a really big log. So I jerrry-ringed some scripts for grepping alert with auxiliar files and etc.
I can see the posts here: Grepping Alert by Day and Grepping Entries from Alert.log.
So… They are functional, but probably the worst ways to get it. I didn’t know and was innocent to not search by the view x$dbgalertext.
There is also possible to write on alert through the procedure SYS.DBMS_SYSTEM.KSDWRT.
Ok, so let me fix this situation with theese two good guys: @write_alert and @find_alert
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.
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.
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).
More“ADRCI Retention Policy and Ad-Hoc Purge Script for all Bases”
Hi all!
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:
#!/bin/bash
# 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.touch /var/lock/subsys/local
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) CGroup: /system.slice/rc-local.service ├─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 .
Maiquel.
Sounds weird creating table does not raise any error, but inserting a correct tuple in this table raise a permission error, right? Just take a look:
SQL> create table matheusdba.table_test(a number) tablespace TEST_TABLESPACE; Table created. SQL> insert into matheusdba.table_test values (1); insert into matheusdba.table_test values (1) * ERROR at line 1: ORA-01950: no privileges on tablespace 'TEST_TABLESPACE'
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 all!
The post Purge SYSAUX Tablespace, made on Fabruary 8this, is yet being high accessed. So, if you’re interested, here it goes another post about:
Last week I supported a database was not purging statistics through MMON job, because is timeouting. Worst than simply that, the database is not purging statistics since 2012 and SYSAUX was huge!
To understand: By default, the MMON performs the automatic purge that removes all history older than:
1) current time – statistics history retention (by default 31 days)
2) time of recent analyze in the system – 1
MMON performs the purge of the optimizer stats history automatically, but it has an internal limit of 5 minutes to perform this job. If the operation takes more than 5 minutes, then it is aborted and stats not purged.
The problem was very clear in alert.log, through the entry:
Unexpected error from flashback database MMON timeout action Errors in file /oracle/diag/rdbms/oracle/trace/oracle_mmon_1234567.trc: ORA-12751: cpu time or run time policy violation
But it’s happening since 2012! How to address that?
More“Statistics not Being Auto Purged – Splitting Purge”
