There is a standard way of trapping any SQL or database errors in Pro*C.This is done using EXEC SQL WHENEVER SQLERROR DO ; just ensure that the above statement goes before any sql statements whenever an error is encountered , the control goes to the function function_name in the body of the function_name , just…
1. EXEC SQL COMMIT WORK RELEASE; (When you want to commit transactions and disconnect;similar to EXIT in SQL*PLUS) 2. EXEC SQL ROLLBACK WORK RELEASE; (When you want to rollback transactions and disconnect;similar to QUIT in SQL*PLUS)
ou can remove the ^M by doing the following: Bring the datafile into the Unix editor vi. In command mode you would type in: :1,$s/^V^M// Make sure you are entering ‘control V’ and ‘control M’. The ‘control V’ says to accept the next character exactly as I type it. Adding the two slashes at the…
To replace the ^M ‘s on the screen in vi type :1, $ s/r/
select * from v$session_longops where sid=100;
exec dbms_output.enable(10000); set lines 130 pages 1000 set serveroutput on size 1000000 declare cursor c1 is select substr(name,1,61) complete_filename, bytes/(1024) KB, substr(name, instr(name, ‘/’, -1)+1) only_filename from v$datafile order by file#; threshold_kb number(10) := 94000000 ; size_counter number := 0; mountpoint_counter number := 1; mountpoint_prefix varchar2(10) := ‘/800t’; common_mountpoint_prefix varchar2(15) := ‘/oradata/800T/’; target_filename varchar2(61); begin…
ALTER SEQUENCE CS.SESSION_ACTIVE_SEQ_ID CACHE 2000; exec sys.DBMS_SHARED_POOL.KEEP(‘CS.SESSION_ACTIVE_SEQ_ID ‘, ‘Q’) =>> To pin the sequence using the DMBS_SHARED_POOL.KEEP procedure (IF NEEDED) Potential drawbacks Setting a cache size larger then 0 can result in the loss of sequence values if the system is shutdown abruptly. When the system fails, the values that were preserved in memory are…
Remove DOS style CR/LF characters (^M) from UNIX files using: sed -e ‘s/^M$//’ filename > tempfile The newly created tempfile should have the ^M character removed
Subject: RMAN : Consistent Backup, Restore and Recovery using RMAN Doc ID: 162855.1 Oracle9i Lab 1 Consistent Backup, Restore and Recovery using RMAN In Oracle9i, Recovery Manager still works the same as in 8 and 8i with enhancements for ease of use and manageability. Using the updateable persistent configuration options, backing up the database is…
Read More “RMAN : Consistent Backup, Restore and Recovery using RMAN” »
Backup and Recovery Scenarios Doc ID: 94114.1 In this Document Purpose Last Review Date Instructions for the Reader Troubleshooting Details BACKUP SCENARIOS a) Consistent backups b) Inconsistent backups c) Database Archive mode d) Backup Methods e) Incremental backups f) Support scenarios RECOVERY SCENARIOS 1. Online Block Recovery. 2. Thread Recovery. 3. Media Recovery. Media Failure…
