37 Matching Annotations
  1. Sep 2022
    1. If your triggers depend on the "firing order", you NEED to (must) consolidate them into a single trigger (put them in separate procedures, have one trigger that calls them in order) UPDATE 15 Jan 201911g Added the precedes and follows clauses to triggers. This allows you to define which order trigger fire. https://www.oracle.com/pls/topic/lookup?ctx=dblatest&id=GUID-AF9E33F1-64D1-4382-A6A4-EC33C36F237B__CJAEJAFB
  2. Aug 2022
      • Flash loan is a type of unsecured lending that relies on the atomicity of blockchain transactions at the point of execution and adds dynamism to DeFi

      • Reentry attack " the DAO"

      • Arithmetic bug

    1. These attacks affect both the current single-collateral Dai (SCD or ‘Sai’) and the upcoming multi-collateral Dai (MCD) implementations, as well as similar systems with on-chain governance.

      51% is not neccesary to manipulate governance to steal the system's collateral.

  3. Feb 2022
    1. I'm still confused, if Oracle knows to throw an error if the timezone falls between the daylight saving time, why wouldn't Oracle adjust the time implicitly?
      • ???
        • 1 hour
    1. I got this error message for one of these two reasons: Most likely: you are trying to convert a local time that does not exist for reasons of DST switch, e.g. '28-MAR-21 02:34' does not exist in Germany (timezone Berlin/Europe), because clocks jump from 1:59 AM to 3:00 AM during night. Solution: add one hour, UTC will then reflect the correct time.
      • ORA-01878
      • DST
    1. The problem is “one hour missing” when DST starts at 2am — the time moves forward to 3am. It won’t happen when DST ends — the time moves backward 3am to 2am.
      • ORA-01878
      • DST
    2. As you can see from the above query results, any attempts to find data between 2am~3am with timezone information will trigger the error. As a comparison, without timezone info, query between 2am~3am works.
      • but timezone info of type 'region', not 'offset'
    3. ORA-1878 During DST, Timestamp or Timezone Testing (Doc ID 417105.1)
      • HERE
      • DST
    1. @WernfriedDomscheit, the double conversion is necessary to convert from a time zone region to a time zone offset. There is more information about the difference here stackoverflow.com/tags/timezone/info. With your example the output is the same as the input is an offset and the output is the same offset. What is implicit about this answer is that it uses the sessions's timezone – Hamish Carpenter Jul 12, 2018 at 1:57 Yes, the difference between a time zone and a time zone offset is important. This does not mean, that you need to go through two type conversions to achieve the result. The important thing is, that a timestamp with time zone, which uses actual time zone (not just an offset) is actually more precise, that a timestamp with time zone, where there's just offset. You can get the offset from both, you can't get the full time zone (region) when just having the offset. – Hilarion Jan 31, 2020 at 10:51
      • my case: define variable TIME_ZONE='region/capital'
      • with it, Oracle takes into account the DST
    1. Oracle recommends that you set the default_timezone attribute to a regions name instead of absolute time zone offset, in order to ensure that daylight saving adjustments are being taken into account.
      • use region name, to detect invalid range, ora error
    1. the time changes from 01:59:59 a.m. to 3:00:00 a.m. when Daylight Saving Time goes into effect. The interval between 02:00:00 and 02:59:59 a.m. does not exist
      • DST change Values in that interval are invalid.
    1. When you return TIMESTAMP WITH LOCAL TIME ZONE data, it’s returned in the current session’s time zone. The session time zone also takes effect when a TIMESTAMP value is converted to the TIMESTAMP WITH TIME ZONE or TIMESTAMP WITH LOCAL TIME ZONE data type.
      • time zone (SESSION)
    2. Note that the database time zone is relevant only for TIMESTAMP WITH LOCAL TIME ZONE columns. Also, Oracle recommends that you set the database time zone to UTC (0:00) to avoid data conversion and improve performance when data is transferred among databases.
      • oracle
      • time zone
    1. My system is using version 32, which is the default time zone file for Oracle 19c (which is what I’m using). This file is located at the following location: $ORACLE_HOME/oracore/zoneinfo/timezlrg_32.dat
      • file for time zones
    2. CETCentral Europe TimeCESTCentral Europe Summer Time
      • time zone
      • DST
  4. Jan 2021
  5. Oct 2020
  6. Jul 2020
    1. Oracle didn’t seem very interested in OpenOffice.org, and the community of volunteers developing it formed The Document Foundation back in 2010. They called on Oracle to participate and donate the OpenOffice.org name and brand to the community. Oracle never did, and the resulting forked office suite has been named LibreOffice since then.
    2. Yes, there are two big open-source office suites. Blame Oracle. Sun controlled the OpenOffice.org project, and Oracle acquired control of it when it purchased Sun back in 2010.
    3. In 2011, Oracle laid off OpenOffice’s paid developers and donated the OpenOffice software to the Apache Foundation, rather than The Document Foundation. It’s remained there since, a project in slow but steady decline.
  7. Aug 2017
    1. Oracle DBA Tutorial covers installation, database backup, restore with examples Oracle DBA Sample Resume Database or essentially DB is a sorted out and organized accumulation of data which can be to productively recovered, refreshed and investigated. A straightforward VB code, C, exceed expectations or notebook can't oversee extensive number of clients and documents. Additionally simple extraction, reinforcement and reclamation of information is unrealistic with this approach. To counter this impediment Oracle has thought of Oracle database or Oracle RDBMS

  8. Jun 2017
  9. Feb 2014
    1. So he took possession of the sovereign power and was confirmed in it by the Delphic oracle

      1.13. Gyges consults the Delphic oracle, who confirms him in his kingship but warns that retribution will come in the fifth generation.

    2. However, the Pythian priestess declared that the Heraclidae would have vengeance on Gyges' posterity in the fifth generation; an utterance to which the Lydians and their kings paid no regard until it was fulfilled

      Hdt. 1.13 The oracle told Gyges that the Heraclidae would have vengeance in the fifth generation and they ignored this until it came true.

    3. “Yes, I do command them, so that you may perish all the sooner for your impiety, and never again come to inquire of my oracle about giving up those that seek refuge with you.”

      1.159 Aristodikos the Cymean re-asks the Oracle at Branchidai about Pactyes and receives a direct response the god. This direct contact with the divine is a rarity in Herodotus's histories. In the conversation between the god and Aristodikos, the god reprimands Aristodikos for questioning the divine in a "how dare you even ask that question" fashion.

    4. The men of Cyme, then, sent to Branchidae to inquire of the shrine what they should do in the matter of Pactyes that would be most pleasing to the gods; and the oracle replied that they must surrender Pactyes to the Persians.

      1.158 the Cymeans consult the oracle at Branchidae before they decide whether or not to give up Pactyes, their prisoner and suppliant, back to Mazares and the Achaemenids.