DB Version: 10.2.0.4
Users: TESTUSR (Table Owner)
TESTUSR_PKG (Package Onwer)
TESTUSR_APP (Application Owner)
create table test_tbl(a number);
CREATE OR REPLACE PACKAGE test_pkg AS -- spec
PROCEDURE insert_test_tbl (
PROCEDURE delete_test_tbl (
CREATE OR REPLACE PACKAGE BODY test_pkg AS -- body
PROCEDURE insert_test_tbl (
I have tried the GoldenGate Software for data replication. I would like to share the steps to one who is really looking for Goldengate replication steps.
I feel its a simple if we think it is simple, If we think its complicated, it is really a complicated. Start with a mindset that you can achieve it.
I have seen articles that misrepresent a Flex Cluster, even this book Expert Oracle RAC 12c which is written by people who should know better (Oracle ACE directors, an OCM, an Oak Table member) gets it fundamentally wrong.
In earlier releases, running a shell script from the Scheduler was awkward. Oracle has realized this, and introduced a new job type in 12c that makes it simple.
Vi is an everyday tool for an Oracle DBA. Commands are many, here's a PDF cheatsheet if you want to become an expert: http://www.math.ntu.edu.tw/~wwang/mtxcomp2010/cssd2011/download/vi_cheat%20sheet.pdf
At the end you get handle yourself with the same commands. I specifically use:
/ -> Lookahead
One often sees requests for test cases, typically when a user has a SQL performance issue. So many users appear to have problems with producing a suitable test case that Uncle Oracle provides routine to automate this. There are no longer any excuses for not providing a test case. Here is an intro to how to do it (code tested on 220.127.116.11 and 18.104.22.168).
The inverted table format can deliver fast and flexible query capabilities, but is not widely used. ADABAS is probably the most successful implementation, but how often do you see that nowadays? Following is a description of how to implement inverted structures within a relational database. All code run on Oracle Database 12c, release 22.214.171.124.
There are three restrictions on indexing and partitioning: a unique index cannot be local non-prefixed; a global non-prefixed index is not possible; a bitmap index cannot be global. Why these limitations? I suspect that they are there to prevent us from doing something idiotic.
I see posts on Oracle related forums about various releases (anything that isn't 11.x or 12.x) being "unsupported". This is wrong. Of course you should upgrade any 9i or 10g databases, but you don't have to.
In this post, I will demonstrate a new feature introduced in 12c : In database archiving. It enables you to archive rows within a table by marking them as invisible. This is accomplshed by means of a hidden column ORA_ARCHIVE_STATE. These invisible rows are not visible to the queries but if needed, can be viewed , by setting a session parameter ROW ARCHIVAL VISIBILITY.
-- Create test user uilm, tablespace ilmtbs
-- Connect as user uilm
-- create and populate test table (5 rows) ilmtab with row archival clause