No, I was more concerned about the pagesize, than the linesize. The repeated headers made it unreadable more than anything. I don't know what his defaults are set to in the login.sql..
Ah, OK. But with large enough LINESIZE you would get quite normaly readable output (no repeating headers, each reccord in one line), while only by eliminating repeated headers the output would still be barely readable.
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
Originally posted by jmodic Ah, OK. But with large enough LINESIZE you would get quite normaly readable output (no repeating headers, each reccord in one line), while only by eliminating repeated headers the output would still be barely readable.
thanks all, i was able to find out what i was looking for with the following
Select max(prmy.sequence#)-max(stby.sequence#) into v_gap_thread_1
from V$ARCHIVED_LOG@hr stby, V$ARCHIVED_LOG@hr prmy where stby.applied='YES' and stby.thread#=prmy.thread# and stby.thread#=1 group by stby.thread#;
dbms_output.put_line('thread one has a gap of '|| v_gap_thread_1
this lets me know the gap and it from there I can do 'if gap is too big then page dba' type of thing
I'm a bit puzzled here. Obviously you are executing this code on the standby database, no? So you must open the standby database in read-only. Do you open it regulary anyway (for some kind of reporting purposes) or is it just to run this piece of code?
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?