file lvm recorded with time stamp graphic display

Similar Questions

• Check out when a last accessed table (select, insert, update) with time stamp. Auditing enabled

  Hello world

  IM pretty new to audit the database. Auditing is enabled in the database. I would like to retrieve the news all of the objects belonged to a certain pattern when it was last accessed (select, insert, update) with time stamp. Is there any script for this? Your time and your reply is greatly appreciated. Thank you.

  Database version: 11.2.0.4

  Enable audit is not quite enough to get the details when the table is updated/inserted/selected.

  You must activate audting on the object level, then you may only be able to see your report of your choice.

  SELECT OBJ_NAME, ACTION_NAME, to_char (timestamp, ' dd/mm/yyyy, hh') of sys.dba_audit_object.

• Group records with time

  Hi all
  
  This is our requirement.
  
  We must combine records with time.
  
  for example: period = 3
  TABLE: XX_SALES
  ---------------------------------------------
  XDATE XQTY
  ---------------------------------------------
  10 5/1/2012
  20 2/5/2012
  3/5/2012 30
  4/5/2012 60
  12 2012/5/7
  8/5/2012 23
  45 8/5/2012
  100 12/5 / 2012
  5/2012/13 55
  5/2012/15 99
  
  == >
  ---------------------------------------------
  XDATE XQTY
  ---------------------------------------------
  1/5/2012 10-> 5/1/2012 Group (5/1/2012 ~ 3/5/2012)
  2/5/2012 20-> 5/1/2012 Group (5/1/2012 ~ 3/5/2012)
  3/5/2012 30-> 5/1/2012 Group (5/1/2012 ~ 3/5/2012)
  4/5/2012 60-> Group 5/2012/4 (4/5/2012 ~ 2012/5/6) *.
  7/5/2012 12-> Group 5/2012/7 (5/7/2012 ~ 9/5/2012) *.
  8/5/2012 23-> Group 5/2012/7 (5/7/2012 ~ 9/5/2012) *.
  8/5/2012 45-> Group 5/2012/7 (5/7/2012 ~ 9/5/2012) *.
  5/2012/12 100-> Group 5/12/2012 (2012/5/12 ~ 14/5/2012) *.
  13/5/2012 55-> Group 5/12/2012 (2012/5/12 ~ 14/5/2012) *.
  5/15/2012 99-> Group 5/15/2012 (15/5/2012 ~ 5/17/2012) *.
  
  After amount to combine with period = 3, the result will be
  ---------------------------------------------
  XDATE_G XQTY_G
  ---------------------------------------------
  60 1/5/2012
  4/5/2012 60
  2012/5/7 80
  12/5/2012 155
  5/2012/15 99
  
  
  Here's the example script

   
  create table XX_SALES(XDATE DATE, XQTY Number);
  insert into XX_SALES VALUES(to_date('20120501','YYYYMMDD'),10);
  insert into XX_SALES VALUES(to_date('20120502','YYYYMMDD'),20);
  insert into XX_SALES VALUES(to_date('20120503','YYYYMMDD'),30);
  insert into XX_SALES VALUES(to_date('20120504','YYYYMMDD'),60);
  insert into XX_SALES VALUES(to_date('20120507','YYYYMMDD'),12);
  insert into XX_SALES VALUES(to_date('20120508','YYYYMMDD'),23);
  insert into XX_SALES VALUES(to_date('20120508','YYYYMMDD'),45);
  insert into XX_SALES VALUES(to_date('20120512','YYYYMMDD'),100);
  insert into XX_SALES VALUES(to_date('20120513','YYYYMMDD'),55);
  insert into XX_SALES VALUES(to_date('20120515','YYYYMMDD'),99);
   

  We can solve this problem by using the loop now:
  to find the XDATE_G and it's rank in the loop and the XQTY in the range of the sum.
  

  DECLARE
    V_DATE_FROM DATE := NULL;
    V_DATE_TO   DATE := NULL;
    V_QTY_SUM   NUMBER := 0;
    CURSOR CUR_DATE IS
      SELECT DISTINCT XDATE FROM XX_SALES ORDER BY XDATE;
  BEGIN
    FOR REC IN CUR_DATE LOOP
      IF V_DATE_TO IS NULL OR REC.XDATE > V_DATE_TO THEN
        V_DATE_FROM := REC.XDATE;
        V_DATE_TO   := REC.XDATE + 3 - 1;
        SELECT SUM(XQTY)
          INTO V_QTY_SUM
          FROM XX_SALES
         WHERE XDATE >= V_DATE_FROM
           AND XDATE <= V_DATE_TO;
        DBMS_OUTPUT.PUT_LINE(TO_CHAR(V_DATE_FROM, 'YYYYMMDD') ||
                             '-----qty: ' || TO_CHAR(V_QTY_SUM));
      END IF;
    END LOOP;
  END;

  Is it possible to solve this problem by using analyze sql?
  
  
  Thanks in advance,
  Best regards
  Zhxiang
  
  Published by: zhxiangxie on April 26, 2012 14:41 fixed the grouping expected data

  There was an article about a similar problem in Oracle Magazine recently:

  http://www.Oracle.com/technetwork/issue-archive/2012/12-Mar/o22asktom-1518271.html

  See the section on the 'grouping beaches '. They needed a total cumulative who started once the total reaches a certain amount.

  You need a total cumulative which starts again when the date changes to group and the dates of beginning and end of each group must be determined dynamically.

  This can be done with the analytical functions.

  Here is a solution-based 'code listing 5', the solution MODEL, which is recommended in the article.

  SELECT FIRST_DATE, SUM(XQTY) SUM_XQTY FROM (
    SELECT * FROM xx_sales
    MODEL DIMENSION BY(ROW_NUMBER() OVER(ORDER BY XDATE) RN)
    MEASURES(XDATE, XDATE FIRST_DATE, XQTY)
    RULES(
      FIRST_DATE[RN > 1] =
        CASE WHEN XDATE[CV()] - FIRST_DATE[CV() - 1] >= 3
        THEN xdate[cv()]
        ELSE FIRST_DATE[CV() - 1]
        END
    )
  )
  GROUP BY first_date ORDER BY first_date;
  
  FIRST_DATE            SUM_XQTY
  --------------------- --------
  2012/05/01 00:00:00         60
  2012/05/04 00:00:00         60
  2012/05/07 00:00:00         80
  2012/05/12 00:00:00        155
  2012/05/15 00:00:00         99
  

  If you 9i, there is no function model. In this case, I can give you a solution using START WITH / CONNECT BY that does not work as well.

• PDM Viewer do not display data with time stamp

  Need help with the timestamp of the data in a PDM file generated by the DAQ Assistant.

  When I use the PDM Viewer, with x the value absolute time scale, the date starts in 1903. If I use Excel to look at the file that the start time is correct (i.e. 2013).

  Bo_Xie, I simplified my VI and now able to display the correct time stamp. Thanks for your time!

• record in the table with time stamp

  Hello
  I use Forms6i and db 10g
  I have a datablock in my form, which is based on a table hlp_user_master.
  The table has fields crt_on, upd_on. who is date type.
  Now I'm set sysdate to these areas, before saving it to the database.
  He is now in the database, just.
  But I want it to be like date with the time.
  My Manager said to set the data type of the fields in the form.
  I did the DateTime data type, in the form
  but still in the database, just when saving
  
  Help, please

  Hello
  If you have changed in the form of the datetime data type and the mask format as I said in my previous post. Then, the database will have time also after saving it. I guess that you are checking in via SQL * more. If so, try the following query.

  SELECT TO_CHAR(DATE_COLUMN,'DD-MON-YY HH24:MI:SS');
  FROM TABLE_NAME;
  

  If the form is stalling as it will display then with time.

  -Clément

• Acquisition of data high-speed with time stamp

  I am acquiring data at a fairly fast speed (5 to 25 kHz) for a few seconds and then writing in a spreadsheet file. Is there a way to set up so that it displays the time stamp for each data point instead of just the data point number?

  

  Of course. Change the type of data returned by DBL 2D to 1 D wave form. This is doen by clicking on the polymorphic selector or right-click and choose 'select the Type '.

• Rough terrain when the data is plotted with time stamp of AM / PM or to the right!

  Hi to all programmers.

  I'm attached Datafile. Can someone tell me how to draw this line! I need all of the data plotted on the right and the x - axis with the date and time stamp.

  I understand that the chart cannot understand that after the time: 12:59:59.999, it's 01:00:00.000 afternoon.

  Thanks to Labview 7.1

  Concerning

  HFZ

  Apart from a code that can be simplified by the use of other functions, what I see, it's that the file you provided does not match the format that expects the VI.

  Other comments:

  • I don't understand why you're going to all the trouble of the evolution of the time string when all what you need to do is:

    

  • All the way at the beginning, use the function of path of the band to get the file name rather than the gymnastics that you're doing.
  • Your time loop must be indexed for auto-loop.
  • I can't quite understand what you're trying to do with all these sliders.

• BEFORE the UPDATE of relaxation with time stamp does not work as expected

  We have a scenario where I check update operations on a table.

  I created a before update TRIGGER, so that every time he goes an update on the main table statement, one before the image of the lines is captured in the table of audit with timestamp.

  Since it is before updating, ideally the audit table timestamp (TRG_INS_TMST) should be less main table timestamp (IBMSNAP_LOGMARKER) VALUE, I mean TRIGGER should happen before the update.

  (I could understand in a way that the UPDATE statement is formulated with SYSTIMESTAMP earlier before the TRIGGER is evaluated and so UPDATE is to have a time stamp prior to TRIGGER, but this isn't what we wanted. We want PRIOR update)

  'Table' IBM_SNAPOPERATION IBM_SNAPLOGMARKER            
  ---- ----------------- -------------------------------
  T1   U                 13-OCT-15 03.07.01.775236 AM   <<---------- This is the main table, This should have the latest timestamp
  T2   I                 13-OCT-15 03.07.01.775953 AM
  

  Here is my test case.

  DELETE FROM TEST_TRIGGER_1;
  
  DELETE FROM TEST_TRIGGER_2;
  
  SELECT 'T1', ibm_snapoperation, ibm_snaplogmarker FROM TEST_TRIGGER_1
  UNION
  SELECT 'T2', ibm_snapoperation, TRG_INS_TMST FROM TEST_TRIGGER_2;
  
  INSERT INTO TEST_TRIGGER_1 (ID,ibm_snapoperation, ibm_snaplogmarker)
       VALUES (1, 'I', SYSTIMESTAMP);
  
  COMMIT;
  
  SELECT 'T1', ibm_snapoperation, ibm_snaplogmarker FROM TEST_TRIGGER_1
  UNION
  SELECT 'T2', ibm_snapoperation, TRG_INS_TMST FROM TEST_TRIGGER_2;
  
  UPDATE TEST_TRIGGER_1
     SET IBM_SNAPOPERATION = 'U', ibm_snaplogmarker = SYSTIMESTAMP;
  
  COMMIT;
  
  SELECT 'T1', ibm_snapoperation, ibm_snaplogmarker FROM TEST_TRIGGER_1
  UNION
  SELECT 'T2', ibm_snapoperation, TRG_INS_TMST FROM TEST_TRIGGER_2;
  

  Def trigger:

  CREATE OR REPLACE TRIGGER etl_dbo.TEST_TRIGGER_1_TRG BEFORE UPDATE OF IBM_SNAPOPERATION
  ON TEST_TRIGGER_1 REFERENCING OLD AS OLD NEW AS NEW
  FOR EACH ROW
  WHEN (
  NEW.IBM_SNAPOPERATION= 'U'
        )
  DECLARE
  V_SQLCODE  VARCHAR2(3000);
  --PRAGMA AUTONOMOUS_TRANSACTION;
  BEGIN
  INSERT INTO etl_dbo.TEST_TRIGGER_2
  (ID,
  IBM_SNAPOPERATION,
  IBM_SNAPLOGMARKER,
  TRG_INS_TMST
  )
  VALUES (:OLD.ID,:OLD.IBM_SNAPOPERATION,:OLD.IBM_SNAPLOGMARKER,SYSTIMESTAMP)
  ;
  --COMMIT;
  END;
  /
  

  Output is something like this

  1 row deleted.
  1 row deleted.
  no rows selected.
  1 row created.
  Commit complete.
  
  'T1' IBM_SNAPOPERATION IBM_SNAPLOGMARKER            
  ---- ----------------- -------------------------------
  T1   I                 13-OCT-15 03.07.00.927546 AM 
  1 row selected.
  1 row updated.
  Commit complete.
  
  'T1' IBM_SNAPOPERATION IBM_SNAPLOGMARKER            
  ---- ----------------- -------------------------------
  T1   U                 13-OCT-15 03.07.01.775236 AM   <<---------- This is the main table, This should have the latest timestamp
  T2   I                 13-OCT-15 03.07.01.775953 AM 
  
  2 rows selected.
  

  But for some reason, even after the creation of the 'AFTER' trigger for update, it works as expected. Sense - the main table is not having the last timestamp given

  It's OKAY - I told you in my reply earlier. Reread my answer.

  could understand somehow that the UPDATE statement is made with earlier

  SYSTIMESTAMP until the TRIGGER is assessed and updated so is to have

  time stamp prior to the trigger, but this isn't what we wanted. We want to

  BEFORE the update)

  As I told you before that your UPDATE statement occurs BEFORE the trigger is activated.

  Despite what the other speakers have said, it makes NO DIFFERENCE if you use a BEFORE UPDATE or an AFTER UPDATE trigger. Your UPDATE statement runs ALWAYS BEFORE the trigger.

  HE has TO - it's your update processing statement that causes the trigger to fire.

  Your update statement includes SYSTIMESTAMP. If during the processing of your return to update the value of SYSTIMESTAMP "at this exact time" is captured.

  Then your trigger is activated and starts to run. ANY reference to SYSTIMESTAMP that you use in your trigger cannot be earlier than the value of until the trigger was executed. It's IMPOSSIBLE.

  The trigger can use the SAME value by referencing: NEW and the column name you store the value. Or the trigger can get its own value that your code is doing.

  But the SYSTIMESTAMP value in the trigger will NEVER earlier than the value in your query.

  And none of these values can actually be used to tell when the changes are really ENGAGED since the trigger does not work and CAN NOT, to know when, or if, a validation occurs.

  Reread my first answer - he explains all this.

• overloading a DATE with time STAMP function to avoid the "too many declarations.

  CREATE OR REPLACE PACKAGE util
  AS
    FUNCTION yn (bool IN BOOLEAN)
      RETURN CHAR;
  
    FUNCTION is_same(a varchar2, b varchar2)
      RETURN BOOLEAN;
  
    FUNCTION is_same(a date, b date)
      RETURN BOOLEAN;
  
    /* Oracle's documentation says that you cannot overload subprograms
     * that have the same type family for the arguments.  But, 
     * apparently timestamp and date are in different type families,
     * even though Oracle's documentation says they are in the same one.
     * If we don't create a specific overloaded function for timestamp,
     * and for timestamp with time zone, we get "too many declarations 
     * of is_same match" when we try to call is_same for timestamps.
     */
    FUNCTION is_same(a timestamp, b timestamp)
      RETURN BOOLEAN;
  
    FUNCTION is_same(a timestamp with time zone, b timestamp with time zone)
      RETURN BOOLEAN;
  
    /* These two do indeed cause problems, although there are no errors when we compile the package.  Why no errors here? */
    FUNCTION is_same(a integer, b integer) return boolean;
  
    FUNCTION is_same(a real, b real) return boolean;
  
  END util;
  /
  
  CREATE OR REPLACE PACKAGE BODY util
  AS
    /********************************************************************************
       NAME: yn
       PURPOSE: pass in a boolean, get back a Y or N
    ********************************************************************************/
    FUNCTION yn (bool IN BOOLEAN)
      RETURN CHAR
    IS
    BEGIN
      IF bool
      THEN
        RETURN 'Y';
      END IF;
  
      RETURN 'N';
    END yn;
  
    /********************************************************************************
       NAME: is_same
       PURPOSE: pass in two values, get back a boolean indicating whether they are
                the same.  Two nulls = true with this function.
    ********************************************************************************/
    FUNCTION is_same(a in varchar2, b in varchar2)
      RETURN BOOLEAN
    IS
      bool boolean := false;
    BEGIN
      IF a IS NULL and b IS NULL THEN bool := true;
      -- explicitly set this to false if exactly one arg is null
      ELSIF a is NULL or b IS NULL then bool := false;
      ELSE bool := a = b;
      END IF;
      RETURN bool;
    END is_same;
  
    FUNCTION is_same(a in date, b in date)
      RETURN BOOLEAN
    IS
      bool boolean := false;
    BEGIN
      IF a IS NULL and b IS NULL THEN bool := true;
      -- explicitly set this to false if exactly one arg is null
      ELSIF a is NULL or b IS NULL then bool := false;
      ELSE bool := a = b;
      END IF;
      RETURN bool;
    END is_same;
    
    FUNCTION is_same(a in timestamp, b in timestamp)
      RETURN BOOLEAN
    IS
      bool boolean := false;
    BEGIN
      IF a IS NULL and b IS NULL THEN bool := true;
      -- explicitly set this to false if exactly one arg is null
      ELSIF a is NULL or b IS NULL then bool := false;
      ELSE bool := a = b;
      END IF;
      RETURN bool;
    END is_same;
  
    FUNCTION is_same(a in timestamp with time zone, b in timestamp with time zone)
      RETURN BOOLEAN
    IS
      bool boolean := false;
    BEGIN
      IF a IS NULL and b IS NULL THEN bool := true;
      -- explicitly set this to false if exactly one arg is null
      ELSIF a is NULL or b IS NULL then bool := false;
      ELSE bool := a = b;
      END IF;
      RETURN bool;
    END is_same;
  
    /* Don't bother to fully implement these two, as they'll just cause errors at run time anyway */
    FUNCTION is_same(a integer, b integer) return boolean is begin return false; end;
    FUNCTION is_same(a real, b real) return boolean is begin return false; end;
    
  END util;
  /
  
  declare
   d1 date := timestamp '2011-02-15 13:14:15';
   d2 date;
   t timestamp := timestamp '2011-02-15 13:14:15';
   t2 timestamp;
   a varchar2(10);
   n real := 1;
   n2 real;
  begin
   dbms_output.put_line('dates');
   dbms_output.put_line(util.yn(util.is_same(d2,d2) ));
   dbms_output.put_line(util.yn(util.is_same(d1,d2) ));
   dbms_output.put_line('timestamps'); -- why don't these throw exception?
   dbms_output.put_line(util.yn(util.is_same(t2,t2) ));
   dbms_output.put_line(util.yn(util.is_same(t,t2) ));
   dbms_output.put_line('varchars');
   dbms_output.put_line(util.yn(util.is_same(a,a)));
   dbms_output.put_line(util.yn(util.is_same(a,'a')));
   dbms_output.put_line('numbers');
   -- dbms_output.put_line(util.yn(util.is_same(n,n2))); -- this would throw an exception
  end;
  /

  Originally, I had just the a function with the arguments of VARCHAR2. It worked not correctly because when the dates were gone, the automatic conversion into VARCHAR2 lowered the timestamp. So, I added a 2nd function with the arguments to DATE. Then I started to get "too many declarations of is_same exist" error during the passage of time stamps. This made no sense to me, so, although documentation Oracle says you can't do this, I created a 3rd version of the function, to manage the TIMESTAMPS explicitly. Surprisingly, it works fine. But then I noticed that he did not work with TIMESTAMP with time zones. Therefore, the fourth version of the function. Docs of the Oracle say that if your arguments are of the same family, you can't create an overloaded function, but in the example above shows, it's very bad.
  
  Finally, just for grins, I created the functions of number two, one number, the other with REAL and even these are allowed - they are compiled. But then, at runtime, it fails. I'm really confused.
  
  Here's the apparently erroneous Oracle documentation on this subject: http://docs.oracle.com/cd/B12037_01/appdev.101/b10807/08_subs.htm (see overload subprogram names) and here are the different types and their families: http://docs.oracle.com/cd/E11882_01/appdev.112/e17126/predefined.htm.
  
  Published by: hot water on 9 January 2013 15:38
  
  Published by: hot water on 9 January 2013 15:46

  >
  So, I added a 2nd function with the arguments to DATE. Then I started to get "too many declarations of is_same exist" error during the passage of time stamps. It makes no sense for me
  >
  This is because when you pass a TIMESTAMP Oracle cannot determine whether to implicitly convert to VARCHAR2 and use your first function or implicitly convert to DATE and use your second function. Where the "too many declarations" error exist.
  >
  , even if said Oracle documentation you can not do, so I created a 3rd version of the function to manage the TIMESTAMPS explicitly. Surprisingly, it works fine. But then I noticed that he did not work with TIMESTAMP with time zones.
  >
  Perhaps due to another error "too many declarations? Because now, there will be THREE possible implicit conversions that might be made.
  >
  Therefore, the fourth version of the function. Docs of the Oracle say that if your arguments are of the same family, you can't create an overloaded function, but in the example above shows, it's very bad.
  >
  I think that the documentation, of the family of 'date', is wrong as you suggest. For WHOLE and REAL, the problem is that those are the ANSI data types and are really the same Oracle data type; they are more like "alias" that different data types.

  See the doc of SQL language
  >
  ANSI SQL/DS and DB2 data types

  The SQL statements that create tables and clusters allows also ANSI data types and products IBM SQL/DS and DB2 data types. Oracle recognizes the ANSI or IBM data type name that differs from the Oracle database data type name. It converts the data type for the equivalent Oracle data type, stores the Oracle data type under the name of the column data type and stores the data in the column in the data type Oracle based on the conversions listed in the following tables.

  INTEGER NUMBER

  INT

  SMALLINT
  NUMBER (38)

  FLOAT (Note b)

  DOUBLE-PRECISION (Note c)

  REAL (Note d)
  FLOAT (126)

  FLOAT (126)

  FLOAT (63)

• Time series graphics display data inappropriate for a continuous analysis

  Hi all
  I've marked in months as chronological key in my MDB layer, but I still cannot display data correctly in my chart of time series, because it shows data for analyses continuously when you create the chart. Can someone help me with the same.
  
  
  Thank you

  What type of data is your key? The chronological key is required for time series formulas (there etc.).

  The time series graph requires a date or datetime data type work - maybe a new column with the first of the month / help? Kind regards

  Robret

• -Command FTP put with time stamp

  Hello
  I need to send a file to a 3rd party (Bank) and include a timestamp in the file. The Bank suggests that I include the timestamp in the command 'put '. I know only to do with the unix commands. Here is an example of the code I have so far:
  

  ftp ftp.bank.com
  <username entered here>
  <password entered here>
  cd inbound
  binary
  put <timestamp - what syntax goes here?>.myfile.txt
  quit

  The timestamp format must be - HHMMSS (hour, minutes, seconds)
  
  Thanks for your time and your input!

  Interplay says:
  Hello
  I need to send a file to a 3rd party (Bank) and include a timestamp in the file. The Bank suggests that I include the timestamp in the command 'put '. I know only to do with the unix commands. Here is an example of the code I have so far:

  ftp ftp.bank.com
  
  
  cd inbound
  binary
  put .myfile.txt
  quit
  

  The timestamp format must be - HHMMSS (hour, minutes, seconds)

  Thanks for your time and your input!

  I see no where that has nothing to do with oracle, so try to use oracle functions as TO_CHAR is doomed to failure.

  I've never seen ftp actually rename a file on the fly (named "MyFile" on the sender system and "votre_fichier" on the receiving system

  steven'sgonna > touch myfile
  steven'sgonna > he's
  Total 0
  -rw-rw-rw-1 steven'sgonna dpi 0 Nov 13 12:29 myfile
  steven'sgonna > mv myfile ' date + %m _myfile %se hour
  steven'sgonna > he's
  Total 0
  -rw-rw-rw-1 steven'sgonna dpi 0 Nov 13 12:29 123124_myfile

  so, you could do something like this:

  NEWFILE ='date + %m _myfile %se hour
  CP myfile $NEWFILE Pei

  FTP<>
  Incoming CD
  put $NEWFILE
  ! EXPRESSIONS OF FOLKLORE!

• help please with time STAMP

  Hello gurus

  Just a little annoyingly Yes, problem here that has pulling me on my eyebrows...

  ALTER session set nls_date_format = "FM MONTH DD YYYY HH24:mi:SS";

  Select username, timestamp, userhost, action_name to_char logoff_time in dba_audit_trail;

  APPS

  ***********

  May 4, 2014 0:3:5

  CLOSURE OF SESSION

  MAY 4, 2014 0:3:5

  As you can see, the timestamp 24HH indicates 0:3:5, instead of the planned 00:03:05

  Did anyone see my mistake in this? I could have been watching this for too long!

  Thanks in advance,

  11.2.04

  RHEL 5.5

  Or, if you need FM for the MONTH, disable it before the portion of time (note that NOVEMBER is still left stuffed and you get your zeros for the part time):

  ORA1@XE > alter session set nls_date_format = "FM MONTH DD YYYY FMHH24:mi:SS";

  Modified session.

  ORA1@XE > select sysdate double

  2.

  SYSDATE

  ---------------------------

  NOVEMBER 6, 2015 09:36:56

• Creating the table with time stamp

  I need to create the table with the data inside buffer
  
  Can you help me pls
  
  If it works today,
  
  create the table test_04NOV2010 in select * from product where product_code = '101'
  
  If executed tmrw,
  
  create the table test_05NOV2010 in select * from product where product_code = '101'
  

  declare
  
  v_date varchar2(25);
  v_sql  varchar2(20);
  
  begin
  
  select to_char(sysdate,'DDMONYYYY') into v_date from dual;
  
   v_sql := ' create table ' ||TEST||'_'||'v_date'|| 
               ' as '
               ' select * from Product where product_code = '101'
            
   EXECUTE IMMEDIATE v_sql;
  
  end;

  can is it you pls let me know how to use it in PL SQL
  
  Can you help me pls
  
  Thank you very much

  declare
  
  v_date varchar2(25);
  v_sql  varchar2(2000); --Noted this. this was also small.
  
  begin
  
  select to_char(sysdate,'DDMONYYYY') into v_date from dual;
  
   v_sql := ' create table TEST_'||v_date||
               ' as select * from Product where product_code = ''101''';
  
   EXECUTE IMMEDIATE v_sql;
  
  end;
  

  You can use the Q operator also.

  DECLARE
  
  v_date varchar2(25);
  v_sql  varchar2(2000);
  
  BEGIN
  
  select to_char(sysdate,'DDMONYYYY') into v_date from dual;
  
   v_sql := ' create table TEST_'||v_date||
              Q'[ as select * from Product where product_code = '101']';
  
   EXECUTE IMMEDIATE v_sql;
  
  END;
  

  Published by: mohamed on November 4, 2010 05:32

• Types with time stamp

  Hi all I'm trying to frind the max of the timestamp when the folllowing gives me an error while storing itself, please share your thoughts
  
  DECLARE
  TYPE type_timestamp IS TABLE OF timestamp;
  list_timestamp type_timestamp;
  BEGIN
  -Set up some test values:
  BECAUSE me in 1... 9 LOOP
  list_timestamp.extend;
  list_timestamp (i): = TO_DATE (TRUNC (DBMS_RANDOM. VALUE (2452641,
  2452641 + 364)).
  'J');
  DBMS_OUTPUT. Put_line(i ||) ': ' || list_timestamp (i));
  END LOOP;
  
  END;
  /

  Says error "refers to an uninitialized collection" so, of course, you must initialize the collection before you use...

  How to initialize?

  DECLARE
    TYPE type_timestamp IS TABLE OF timestamp;
    list_timestamp type_timestamp := type_timestamp(); --- just use the default constructor
  BEGIN
  ...
  

  HTH

  Published by: Roger on January 19, 2012 02:53

• Time-stamped comments adding in a DDHN file during logging

  I'm trying to find the best way to add comments in a DDHN file during logging.  I know that the fragmentation occurs when the properties are written for TDMS logging.  Should I write comments in the level in the logging file (maybe a case of Structure fires when a new comment occurs) or is there another way to incorporate comments into a DDHN file during logging that I'm missing?  Any help would be appreciated.

  Nathan, do you really care about fragmentation? If this isn't the case, you could do it just like that. If you really care fragmantation, you could write Time-Stamped comments in a separate file, PDM, or any, Time-Stamped cache and write cached put comments in the PDM file after cutting.