Hi Guys!
Don’t forget to confirm your presence in GUOB Tech Day 2016 Today! Why? Because the subscribing price is very low just until midnight (GMT -3)!
Take a look:
More about GUOB Tech Day 2016
Register now!
Take a look in our first call here!
See you there!
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 Folks!
As I told you here, last 28, 29 and 30th I was at Oracle OpenWorld LA 2016, in São Paulo/SP – Brazil.
Before my considerations, I’d like to remember that some presentation materials used by speakers are available at here.
There was a lot of sessions, so the review for is as short as possible for each one of them:
Hi all!
Just a curiosity: Have you ever noticed in a database alert log the occourance of the following message for every logfile switch:
Thread 1 cannot allocate new log, sequence 9281 Private strand flush not complete Current log# 5 seq# 9280 mem# 0: /db/u5001/oradata/GREPORADB/redo05a.log Thread 1 advanced to log sequence 9281 (LGWR switch) Current log# 6 seq# 9281 mem# 0: /db/u5001/oradata/GREPORADB/redo06a.log
More“Alert Log: “Private Strand Flush Not Complete” on Logfile Switch”
Hi all,
If you have missed the previous Flashback posts, please go through these links to find it and read them if you feel like!
Flashback – Part 1 (Flashback Drop)
Flashback – Part 2 (Flashback Query)
Flashback – Part 3 (Flashback Versions Query)
Flashback – Part 5 (Flashback Table)
Flashback – Part 6 (Flashback Database)
Flashback – Part 7 (Flashback Data Archive)
And now, we are half way there to the end of the Flashback posts, let’s see a little more about FLASHBACK TRANSACTION QUERY.
Hey Dudes and Dudettes!
Just to remmember you about 1º Oracle Technology Users Meeting of 2016 by GUORS, next week!
If you not subscribed yet, please access here!
Will be there: Cassiano, Maiquel, Matheus and Rafael!
See you!
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”
Hi.
Today, let’s talk about Java Message Systems (JMS), the reason led me talk about this, is that my environment, a complex architecture of messages where we have more of two hundred queues in the same domain.
The administration of queues in the weblogic console is very simple, but, if you need to remove a million messages, in a hundred queues, you have a problem!
To turn more agile the visualization of messages, state and other queue properties, nothing better than to use WLST.
This post shows a script, which can grow up where you imagine, for while the script have just three options (the most useful to me) and nothing prevents to have more.
Hi Everyone,
Here we are to continue our Flashback Saga! If you lost our first 2 posts about that and are in the mood for a good reading, please go through the links below:
Flashback – Part 1 (Flashback Drop)
Flashback – Part 2 (Flashback Query)
Flashback – Part 4 (Flashback Transaction Query)
Flashback – Part 5 (Flashback Table)
Flashback – Part 6 (Flashback Database)
Flashback – Part 7 (Flashback Data Archive)
Today we are going to discuss Flashback Versions Query, which has a strong link with the previous post, the Flashback Query (AS OF). With this feature, we are able to verify all changes made between 2 points in time in the past, using SCN or a Timestamp. Of course, the Flashback Versions Query will retrieve only the committed data. Just like Flashback Query, the Flashback Versions Query is undo-based, so make sure your undo Tablespace and undo retention period is good enough for you.