DBORCLOUD Blog

How to install APEX 4.2.3

This guide refer to APEX release 4.2.3 and installed on debian like server. First you must download the package of APEX from Oracle site and then unzip the package on your server with command (use “sudo” if you haven’t  right permission for do this and following S.O. commands): # unzip apex_4.2.3.zip   Move your apex directory, that it created from unzip command, to oracle folder with command: # mv apex <oraclefolder>/apex_app You change directory to apex_app and connect to database with SQLPlus: # sqlplus /nolog SQL> CONNECT SYS AS SYSDBA   You run the installation script of APEX SQL> @apexins.sql Read More

Create triggers on system events

System events are particular database states that can be used to fire a system trigger. Is possibile to create triggers for these events at DATABASE or SCHEMA level. When a triggering event occurs, the database will open an autonomous transaction scope, fire the trigger and commit any transaction imbedded in the trigger. The available system events are: AFTER STARTUP        Causes the DataBase to fire the trigger whenever the database is opened. This event is valid only with DATABASE, not with SCHEMA BEFORE SHUTDOWN      Causes the DataBase to fire the trigger whenever an instance of the Read More

Create Database Link

Use the CREATE DATABASE LINK statement to create a database link. A database link is a schema object in one database that enables you to access objects on another database. The other database need not be an Oracle Database system. However, to access non-Oracle systems you must use Oracle Heterogeneous Services. After you have created a database link, you can use it to refer to tables and views on the other database. In SQL statements, you can refer to a table or view on the other database by appending @dblink to the table or view name. You can query a Read More

Archive for the ‘DataGuard’ Category

DATAGUARD:Verifying synchronization between the primary and standby databases By using the following steps, you can control whether the standby database is synchronized with primary: 1. STANDBY DATABASE For the last archived sequence, use the following: SQL> SELECT MAX(SEQUENCE#) FROM V$ARCHIVED_LOG; MAX(SEQUENCE#) ————– 195 For the last applied sequence, use the following: SQL> SELECT MAX(SEQUENCE#) FROM V$ARCHIVED_LOG WHERE APPLIED=’YES’; MAX(SEQUENCE#) ————– 194 From the preceding two queries, we see that the latest sequence, 195, is being archived or written into the standby redo logfiles. There’s expected to be a lag of one sequence between archived and applied columns. 2. STATUS OF Read More