Today I will show you how to handle ORA-16053 error--Check maximum sequence number of archive loghttp://2.bp.blogspot.com/_z5ltvMQPaa8/SjJXr_U2YBI/AAAAAAAAAAM/46OqEP32CJ...) rgb(240, 240, 240); border: 1px dashed rgb(204, 204, 204); font-family: arial; font-size: 12px; height: auto; line-height: 20px; overflow: auto; padding: 0px; width: 450.828px;">
SQL> select max(sequence#) from v$archived_log; MAX(SEQUENCE#) --------------
This was a question asked over Twitter by @DanBarker to TalkTalk, the major British telco after they managed to lose a significant portion of its customers’ details, apparently through an SQL Injection attack by a 15 year old.
The question wasn’t answered, but the sooner companies realise that a security incident can wipe out a significant part of the brand’s goodwill, the more this ratio will adjust.
Here are three top tips to ensure you’re investing wisely in cyber security, and protecting your brand’s good name:
Yes, I know what you’re thinking.
“Here we go again. Another database dude about to get stuck into us telling us about the importance of foreign keys for data integrity”
and yes, I could easily do that. But you’ve seen that before (and by the way, it’s of course still totally valid – you should have all those integrity constraints defined!)
I wanted to add an append hint to some code but realised that there are known restrictions when either triggers or referential integrity are involved.
That does make sense as potentially rows would be inserted that either did not fire a trigger or broke RI constraints.
I decided to produce a test case to prove that the restrictions did work and were still in place.
Test append with trigger created
Thanks to the many attendees that came to my presentation "Oracle 12c Parallel Execution New Features" at the DOAG conference 2015.
SQL> select count(*) from all_objects_many_list;
SQL> select min(created) from all_objects_many_list;
I’m speaking at the Sydney leg on the OTN APAC tour on November 30th, 394 Lane Cove Rd, North Ryde
This is a great event with local and international speakers all giving their time and knowledge for free to help you with your Oracle technology.
If you’re in Sydney, then come along for some great education. Even if you cannot attend the conference, if you are in the area, come along and say Hi. Part of my job focus is helping developers succeed with Oracle, so we might be able to organise something in the future in terms of (free) education for your development teams.
This Log Buffer Editions picks few blog posts from Oracle, SQL Server and MySQL.
For one of my clients, I experienced several issues with applying PSU 220.127.116.11.5 with opatch 18.104.22.168.9.
There were some code changes in opatchauto, which are not yet production-ready. I am looking forward to seeing a new opatch release (maybe 22.214.171.124 or 11) which has these issues fixed.