Following is the call that can be made to refresh your materialized view in Oracle manually: 1 EXECUTE DBMS_SNAPSHOT.REFRESH('[MV_NAME]’,'[refresh_option]’);execute DBMS_SNAPSHOT.REFRESH(‘[MV_NAME]’,'[refresh_option]’); Refresh Options: ? – Uses default F or f – Fast C or c – Complete A – Always complete
Are you a TOAD fanatic when it comes to “anything-Oracle”? If so, you probably realized that TOAD will not show you the DDL for a materialized view in any of the tabs in the schema browser. The “Scripts” tab will look similar to a table’s script. Following is an SQL statement you can run to find out the SQL used by the materialized view: 1 SELECT query FROM user_mviews WHERE mview_name='[MV_NAME]’;select query from user_mviews where mview_name='[MV_NAME]’; Enjoy!
This will run only the SQL that your cursor is on. You do not need to highlight the line or the entire SQL statement; simply place your cursor anywhere inside the SQL statement and click SHIFT-F9.
This will verify (parse) the statement without executing it.
This will execute an explain plan on the current statement.
This will bring up your previous SQL statement. If you use SHIFT-F9 and are disciplined about keeping all iterations of executed statements in the screen…
Unlike Oracle, other less expensive and less robust databases make autoincrementing a simple task…typically a couple of clicks in some easy to understand UI. Some examples are with SQL Server, MySQL, and Access. As we know, with Oracle’s additional “flexibility” can come additional work (but this is sometimes for a legitimate reason). Approach 1 Following are the steps on how you can mimic an autoincrement in Oracle: 1) create a table 2) create a sequence 3) create a trigger 4) insert record(s) CREATE TABLE test_table ( test_id INT PRIMARY KEY, test_col varchar2(100)); CREATE SEQUENCE test_seq; CREATE TRIGGER test_trigger … Read More