FTP Throttling limit

If you have not implemented the TimeStamp (3) data type (see Oracle databases), when Bidding files are processed, AEMO Australian Energy Market Operator‘s systems throttle processing to one Submission A Bid/Offer submission can have: 1. Multiple Trading Days 2. Multiple DUIDs/LinkIDs 3. All Service Types in the same Submission per second per Participant ID Registered participant identifier; A company can have more than one Participant ID.. This restriction is due to an existing legacy limit in the Data Model The definition of the interface to participants of data published by AEMO for gas or electricity. A database conforming to the Data Model can contain a local copy of all current participant-specific data recorded in the main database. The Data Model includes database tables, indexes, and primary keys. bidding tables, relying on the field OfferDate in the primary key. So if you submit multiple JSON JavaScript Object Notification files via the FTP File transfer protocol interface you might observe queued files clearing slowly, this is the consequence of the FTP throttling limit.

Oracle databases

For Oracle databases, the OfferDate field is a DATE data type not supporting fractional seconds. The DATE restriction originates from the original delivery of the Data Model that assumed an Oracle implementation because it was near universal at the time.

The Five Minute Settlement (5MS) Data Model (v5.00) upgraded the OfferDate column, DATE data type to Timestamp (3) to support fractional seconds (to three decimal places).

Once the change is implemented for all Oracle participant systems AEMO can lift the restriction. To ensure global compliance, this is expected about a year from the 5MS implementation.

This change impacts the following tables and fields:

  1. BIDOFFERFILETRK.OFFERDATE
  2. BIDDAYOFFER.OFFERDATE
  3. BIDOFFERPERIOD.OFFERDATETIME (new 5MS table)
  4. MNSP_DAYOFFER.OFFERDATE
  5. MNSP_BIDOFFERPERIOD.OFFERDATETIME (new 5MS table)
  6. DISPATCHOFFERTRK.BIDOFFERDATE
  7. DISPATCH_MNSPBIDTRK.OFFEREFFECTIVEDATE
  8. PREDISPATCHOFFERTRK.BIDOFFERDATE
  9. PREDISPATCH_MNSPBIDTRK.OFFERDATE

Microsoft SQL Server databases

The field definition for SQL Server databases does not suffer this restriction.

Oracle PDR loader properties file changes

For participants running Oracle databases with pdrLoader Software responsible for loading files to and from participant's local Data Interchange folders to the participant's DBMS. It can be installed in any environment supporting Java. v7.4.1 or earlier, to accommodate the new Timestamp data type you must add the following statement to the pdrLoader properties file (see Figure 53).

db_conn_init_sql=ALTER SESSION SET NLS_TIMESTAMP_FORMAT='YYYY/MM/DD HH24:MI:SS.FF3'

This is not required for participants running SQL databases or pdrLoader v7.4.2 or above.

Figure 53 pdrLoader properties file