Automic Workload Automation

  • Private Community
Back to discussions
Expand all | Collapse all

[Quick question] - AWA v12 and performance indicator

Keld Mollnitz

Keld MollnitzJun 15, 2018 04:05 AM

I fully support what eric.felker says.

  • 1.  [Quick question] - AWA v12 and performance indicator

    Posted Mar 30, 2017 05:57 AM
    20160403/110844.008 - U00003533 UCUDB: Check of data source finished: No errors. Performance CPU/DB: '44358458'/'826 (1000/1.209291 s)'

    What does 1000/1.209291 s mean ?

    From the version 12 of AWA, a new performance indicator is available. First values ('44358458'/'826 ) are known  (CF : https://community.automic.com/discussion/7395/database-performance)

    • CPU
    44358458 : is the result of the addition 1+1+1+1+1+… the WP is able to do in 1 second. This is more or less a CPU speed  indicator.

    • DB
    826 : is the amount of DB sequence BDD ‘insert + select + rollback’ in DIVDB table the WP is able to do in 1 second. This number illustrates the quality of the DB access.

    (1000/1.209291 s) : can be read as “the WP is able to to run 1000 DB sequence in 1,20 seconds”. This is finally the same indicator but with another point of view.


    To be more explicit and illustrate my words differently we could find in log :
    20160403/110844.008 - U00003533 UCUDB: Check of data source finished: No errors. Performance CPU/DB: '(44358458/1 s)'/'(826/1 s) (1000/1.209291 s)'


  • 2.  [Quick question] - AWA v12 and performance indicator

    Posted Mar 30, 2017 07:04 PM
    This is great information and can be very confusing for those looking at it for the first time. Great post!


  • 3.  Re: [Quick question] - AWA v12 and performance indicator

    Posted Jun 14, 2018 03:46 PM

    I agree with Andrew--it's great to see this more clearly spelled out. I'm hoping we can take it even further. Can someone from Automic side provide the exact query that are being executed for the DB performance check? It would be very helpful for use in performance tuning the DB, rather than being forced to start up a piece of the application and looking at the log output to get that information.



  • 4.  Re: [Quick question] - AWA v12 and performance indicator

    Posted Jun 15, 2018 04:05 AM

    I fully support what eric.felker says.



  • 5.  Re: [Quick question] - AWA v12 and performance indicator

    Posted Jun 15, 2018 06:41 PM

    Disclaimer I'm not from the Automic side but I was curious so decided to run a DB4 trace on a start up of a WP and here is what I saw.

     

    SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    INSERT INTO DIVDB (DIVDB_PK,DIVDB_Memo,DIVDB_String,DIVDB_Date) VALUES(1, ?, ?, ?)
    SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1

     

    The INSERT shows in the startup 1000 times and the SELECT shows up 2000 times.

     

    Bind parameters however is just Umlauts for every field: öäüÖÄÜß{}[] (that exact string from trace >öäüÖÄÜß{}[].....<)

     

    EDIT: Another thing I found interesting is that it looks like it runs 1000 insert statements regardless of how long it takes. For example here is the results from my startup

     

    CPU/DB: '28209746'/'221 (1000/4.506597 s)

     

    So it took 4.5 seconds to run all 1000 inserts. Its not done by going lets see how many we can do in 1 second

     

    Regards,

     

    Michael



  • 6.  Re: [Quick question] - AWA v12 and performance indicator

    Posted Jun 18, 2018 01:30 PM

    Thanks Michael for that detailed information. It helps quite a lot. I can also confirm that the DB performance check does the same number of steps regardless of how long it may take, even though documentation states that these checks only sample a 2 second window. I have DB systems that literally take minutes because the DB performance value is in the single digits. Not production thankfully! I am taking this back to our DBAs



  • 7.  Re: [Quick question] - AWA v12 and performance indicator

    Posted Jun 19, 2018 08:03 AM

    I played with these statements a bit yesterday, but putting them into a loop isn't as straightforward in Oracle PLSQL as I was hoping.

     

    It's also worth noting, if a record is left in the DIVDB table, the AE will not be able to start up normally if attempted. It will fail with an "EXISTS" message several times in the log. By happenstance we needed to restart the system I had been playing with later in the day, so it took some lengthy troubleshooting to figure out the issue. So while the trace provided by Michael on this thread may show a select > insert > select, I feel there must be a statement that clears the table, too. Grupe01 on this other thread notes that the sequence is select > insert > rollback, which makes more sense. This is all a good step in the right direction.



  • 8.  Re: [Quick question] - AWA v12 and performance indicator

    Posted Jun 19, 2018 11:34 AM

    Thanks for testing that out. It would make sense that it would want a clear table on every start up. I do not see anything in my trace file for rollback or commit so I'm not sure how it handles the transaction when it is finished with the 1000 inserts. In the trace it goes directly from the last select to printing the performance metric:

     

    20180615/151111.506 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20180615/151111.506 - U00003533 UCUDB: Check of data source finished: No errors. Performance CPU/DB: '28209746'/'221 (1000/4.506597 s)'
    20180615/151111.506 - U00003544 UCUDB: Reference values tested with Windows 2003 on XEON 1500 MHz: CPU 813865, DB 470



  • 9.  RE: Re: [Quick question] - AWA v12 and performance indicator

    Posted May 11, 2020 08:14 AM
    Hi @Michael Pirson,

    In the Trace file, did you notice the same strange behavior regarding the timestamps as I do:

    Many updates within the same ms:
    20200511/111216.009 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/111216.009 - Length string :11
    20200511/111216.009 - U00009909 TRACE: (DB-DATA: string) 0000000000E29CE0 000255
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 000000 >...............<
    20200511/111216.009 - Length date :16
    20200511/111216.009 - U00009909 TRACE: (DB-DATA: date) 0000000000E29DE0 000016
    00000000 6B070C00 1E001700 2D003A00 00000000 >k.......-.:.....<
    20200511/111216.009 - Length memo :11
    20200511/111216.009 - U00009909 TRACE: (DB-DATA: memo) 0000000000E297C0 000256
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 00000000 >................<
    20200511/111216.009 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1

    Then a 16 ms pause, before it continues:
    20200511/111216.025 - INSERT INTO DIVDB (DIVDB_PK,DIVDB_Memo,DIVDB_String,DIVDB_Date) VALUES(1, ?, ?, ?)
    20200511/111216.025 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/111216.025 - Length string :11
    20200511/111216.025 - U00009909 TRACE: (DB-DATA: string) 0000000000E29CE0 000255
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 000000 >...............<
    20200511/111216.025 - Length date :16
    20200511/111216.025 - U00009909 TRACE: (DB-DATA: date) 0000000000E29DE0 000016
    00000000 6B070C00 1E001700 2D003A00 00000000 >k.......-.:.....<
    20200511/111216.025 - Length memo :11
    20200511/111216.025 - U00009909 TRACE: (DB-DATA: memo) 0000000000E297C0 000256
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 00000000 >................<
    20200511/111216.025 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/111216.025 - INSERT INTO DIVDB (DIVDB_PK,DIVDB_Memo,DIVDB_String,DIVDB_Date) VALUES(1, ?, ?, ?)

    /Keld.
    Original Message


  • 10.  RE: Re: [Quick question] - AWA v12 and performance indicator

    Posted May 11, 2020 08:36 AM
    thats really funny - I am also on this issue right now.
    We are analyzing the behaviour. According to our HealthCheck this value should be round about 1 seconds for this 1000 statements.
    we are on about 3 second
    And we got the same behaviour. A lot of inserts in one milleseconds  then about 15 milliseconds nothing - then again a lot of inserts in one millisecond.

    We suspect the vm. maybe the vm doesnt permanently release CPU time. 
    But it is not because of that.
    Do you use a physically or virtuell machine?
    the next maybe-reason I will observe is our network
    Original Message


  • 11.  RE: Re: [Quick question] - AWA v12 and performance indicator

    Posted May 11, 2020 08:53 AM
    Hi @Markus,

    Which OS is your AE on and which database are you using? We are using Windows for the AE and Oracle DB is on Unix.

    The following is taken from our Sandbox env. but we see the same low numbers across all our environments:
    20200511/111222.353 - U00003533 UCUDB: Check of data source finished: No errors. Performance CPU/DB: '73678682'/'157 (1000/6.346456 s)'

    We are using VMware today, but I have also installed the AE on a physical server (44 CPUs and 780 GB Mem). It does not make any difference.

    /Keld.
    Original Message


  • 12.  RE: Re: [Quick question] - AWA v12 and performance indicator

    Posted May 11, 2020 10:48 AM
    we too
    AE ist running an windows and database is oracle on Unix.
    could it be the reason for that?

    anybody here whose enviroment arent win-ae-server and unix-oracle-server?
    Original Message


  • 13.  RE: Re: [Quick question] - AWA v12 and performance indicator

    Posted May 11, 2020 11:03 AM
    Hi @Markus,
    I'm curious to see your trace file, would you be able to share it with me ?

    /Keld.​
    Original Message


  • 14.  RE: Re: [Quick question] - AWA v12 and performance indicator

    Posted May 11, 2020 11:43 AM
    here you are:
    20200511/095936.231 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.231 - INSERT INTO DIVDB (DIVDB_PK,DIVDB_Memo,DIVDB_String,DIVDB_Date) VALUES(1, ?, ?, ?)
    20200511/095936.231 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.231 - Length string :11
    20200511/095936.231 - U00009909 TRACE: (DB-DATA: string) 00000000022BDF60 000255
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 000000 >...............<
    20200511/095936.231 - Length date :16
    20200511/095936.231 - U00009909 TRACE: (DB-DATA: date) 00000000022BE060 000016
    00000000 6B070C00 1E001700 2D003A00 00000000 >k.......-.:.....<
    20200511/095936.231 - Length memo :11
    20200511/095936.231 - U00009909 TRACE: (DB-DATA: memo) 00000000022BDA40 000256
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 00000000 >................<
    20200511/095936.231 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.231 - INSERT INTO DIVDB (DIVDB_PK,DIVDB_Memo,DIVDB_String,DIVDB_Date) VALUES(1, ?, ?, ?)
    20200511/095936.231 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.231 - Length string :11
    20200511/095936.231 - U00009909 TRACE: (DB-DATA: string) 00000000022BDF60 000255
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 000000 >...............<
    20200511/095936.231 - Length date :16
    20200511/095936.231 - U00009909 TRACE: (DB-DATA: date) 00000000022BE060 000016
    00000000 6B070C00 1E001700 2D003A00 00000000 >k.......-.:.....<
    20200511/095936.231 - Length memo :11
    20200511/095936.231 - U00009909 TRACE: (DB-DATA: memo) 00000000022BDA40 000256
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 00000000 >................<
    20200511/095936.231 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.231 - INSERT INTO DIVDB (DIVDB_PK,DIVDB_Memo,DIVDB_String,DIVDB_Date) VALUES(1, ?, ?, ?)
    20200511/095936.231 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.231 - Length string :11
    20200511/095936.231 - U00009909 TRACE: (DB-DATA: string) 00000000022BDF60 000255
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 000000 >...............<
    20200511/095936.231 - Length date :16
    20200511/095936.231 - U00009909 TRACE: (DB-DATA: date) 00000000022BE060 000016
    00000000 6B070C00 1E001700 2D003A00 00000000 >k.......-.:.....<
    20200511/095936.231 - Length memo :11
    20200511/095936.231 - U00009909 TRACE: (DB-DATA: memo) 00000000022BDA40 000256
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 00000000 >................<
    20200511/095936.231 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.231 - INSERT INTO DIVDB (DIVDB_PK,DIVDB_Memo,DIVDB_String,DIVDB_Date) VALUES(1, ?, ?, ?)
    20200511/095936.231 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.231 - Length string :11
    20200511/095936.231 - U00009909 TRACE: (DB-DATA: string) 00000000022BDF60 000255
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 000000 >...............<
    20200511/095936.231 - Length date :16
    20200511/095936.231 - U00009909 TRACE: (DB-DATA: date) 00000000022BE060 000016
    00000000 6B070C00 1E001700 2D003A00 00000000 >k.......-.:.....<
    20200511/095936.231 - Length memo :11
    20200511/095936.231 - U00009909 TRACE: (DB-DATA: memo) 00000000022BDA40 000256
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 00000000 >................<
    20200511/095936.231 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.231 - INSERT INTO DIVDB (DIVDB_PK,DIVDB_Memo,DIVDB_String,DIVDB_Date) VALUES(1, ?, ?, ?)
    20200511/095936.246 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.246 - Length string :11
    20200511/095936.246 - U00009909 TRACE: (DB-DATA: string) 00000000022BDF60 000255
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 000000 >...............<
    20200511/095936.246 - Length date :16
    20200511/095936.246 - U00009909 TRACE: (DB-DATA: date) 00000000022BE060 000016
    00000000 6B070C00 1E001700 2D003A00 00000000 >k.......-.:.....<
    20200511/095936.246 - Length memo :11
    20200511/095936.246 - U00009909 TRACE: (DB-DATA: memo) 00000000022BDA40 000256
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 00000000 >................<
    20200511/095936.246 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.246 - INSERT INTO DIVDB (DIVDB_PK,DIVDB_Memo,DIVDB_String,DIVDB_Date) VALUES(1, ?, ?, ?)
    20200511/095936.246 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.246 - Length string :11
    20200511/095936.246 - U00009909 TRACE: (DB-DATA: string) 00000000022BDF60 000255
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 000000 >...............<
    20200511/095936.246 - Length date :16
    20200511/095936.246 - U00009909 TRACE: (DB-DATA: date) 00000000022BE060 000016
    00000000 6B070C00 1E001700 2D003A00 00000000 >k.......-.:.....<
    20200511/095936.246 - Length memo :11
    20200511/095936.246 - U00009909 TRACE: (DB-DATA: memo) 00000000022BDA40 000256
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 00000000 >................<
    20200511/095936.246 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.246 - INSERT INTO DIVDB (DIVDB_PK,DIVDB_Memo,DIVDB_String,DIVDB_Date) VALUES(1, ?, ?, ?)
    20200511/095936.246 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.246 - Length string :11
    20200511/095936.246 - U00009909 TRACE: (DB-DATA: string) 00000000022BDF60 000255
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 000000 >...............<
    20200511/095936.246 - Length date :16
    20200511/095936.246 - U00009909 TRACE: (DB-DATA: date) 00000000022BE060 000016
    00000000 6B070C00 1E001700 2D003A00 00000000 >k.......-.:.....<
    20200511/095936.246 - Length memo :11
    20200511/095936.246 - U00009909 TRACE: (DB-DATA: memo) 00000000022BDA40 000256
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 00000000 >................<
    20200511/095936.246 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.246 - INSERT INTO DIVDB (DIVDB_PK,DIVDB_Memo,DIVDB_String,DIVDB_Date) VALUES(1, ?, ?, ?)
    20200511/095936.246 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.246 - Length string :11
    20200511/095936.246 - U00009909 TRACE: (DB-DATA: string) 00000000022BDF60 000255
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 000000 >...............<
    20200511/095936.246 - Length date :16
    20200511/095936.246 - U00009909 TRACE: (DB-DATA: date) 00000000022BE060 000016
    00000000 6B070C00 1E001700 2D003A00 00000000 >k.......-.:.....<
    20200511/095936.246 - Length memo :11
    20200511/095936.246 - U00009909 TRACE: (DB-DATA: memo) 00000000022BDA40 000256
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 00000000 >................<
    20200511/095936.246 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.246 - INSERT INTO DIVDB (DIVDB_PK,DIVDB_Memo,DIVDB_String,DIVDB_Date) VALUES(1, ?, ?, ?)
    20200511/095936.246 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.246 - Length string :11
    20200511/095936.246 - U00009909 TRACE: (DB-DATA: string) 00000000022BDF60 000255
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 000000 >...............<
    20200511/095936.246 - Length date :16
    20200511/095936.246 - U00009909 TRACE: (DB-DATA: date) 00000000022BE060 000016
    00000000 6B070C00 1E001700 2D003A00 00000000 >k.......-.:.....<
    20200511/095936.246 - Length memo :11
    20200511/095936.246 - U00009909 TRACE: (DB-DATA: memo) 00000000022BDA40 000256
    00000000 F6E4FCD6 C4DCDF7B 7D5B5D00 00000000 >öäüÖÄÜß{}[].....<
    00000010= 00000000 00000000 00000000 00000000 >................<
    000000F0 00000000 00000000 00000000 00000000 >................<
    20200511/095936.262 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.262 - INSERT INTO DIVDB (DIVDB_PK,DIVDB_Memo,DIVDB_String,DIVDB_Date) VALUES(1, ?, ?, ?)
    20200511/095936.262 - SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
    20200511/095936.262 - Length string :11
    Original Message


  • 15.  RE: Re: [Quick question] - AWA v12 and performance indicator

    Posted May 12, 2020 02:24 AM
    Hi @Markus,
    I have send you a private message​..
    Original Message