| Date: | 30-OCT-2009/00:10 |
| Activity: | Triggers added for billfish, shark, tuna legacy tables |
| Persons Involved: | JPAPPAS |
| Description: | Audit (_briu) triggers were added for the three legacy (pre-LODS) fish life history tables: billfish_legacy, shark_legacy, tuna_legacy. If data in any of these tables are changed, the date of the change and the user making the change will be written to the record in the last_mod_date and last_mod_by columns. Note that history tables have existed for these legacy tables since LODS' inception in Sept 2005, so any changes, inserts or deletes since then would have been recorded as records in the corresponding history table. As of this date, there have been no changes recorded in any of these history tables. |
| Back to Top | |
| Date: | 21-OCT-2009/11:10 |
| Activity: | Logbook page number corrections |
| Persons Involved: | EFORNEY |
| Description: | The logbook page numbers for 19 sets on 11 trips required correction as they had been entered wrong. Issues were opened on the applicable logbook page numbers, the trips were re-opened and after the issues were closed and the data corrections made they were re-approved. |
| Back to Top | |
| Date: | 24-AUG-2009/00:08 |
| Activity: | Added alias code to ref table LOP_HK_TYPE |
| Persons Involved: | JPAPPAS |
| Description: | LOP_HK_TYPE reference table: Added alias_code 7 for Offset Circle (code 07) as requested by K. Sender |
| Back to Top | |
| Date: | 16-AUG-2009/00:08 |
| Activity: | Added view of tagged turtles |
| Persons Involved: | JPAPPAS |
| Description: | View contains data about turtles tagged by observers; data includes the turtle species, date/time of capture and release, whether tags were already present on the turtle and the number of the tag(s) applied. Links to TDPS data (Hawaii). |
| Back to Top | |
| Date: | 27-APR-2009/00:04 |
| Activity: | Reference Table - Specimen Type |
| Persons Involved: | EFORNEY |
| Description: | The definition for the specimen type reference code "R" was changed from "The anterior rays of the anal fin. Used to determine the age of the individual fish." to "The anterior or all rays of a fin such as the anal or dorsal fin. Used to determine the age of the individual fish." as specimen collection requests from researchers have shown that the rays are not just collected from the anal fin but also other fins such as the dorsal fin. The code value was changed from [Anal Fin] Ray" to "[Fin} Ray". |
| Back to Top | |
| Date: | 15-OCT-2008/10:10 |
| Activity: | History triggers recreated to display time data in date fields |
| Persons Involved: | JPAPPAS |
| Description: | History triggers were recreated using Data History Creator. This update only affects ...datetime fields. History reports will now display the time portion of DATE (data_type) fields in the fields h_old_data and h_new_data. |
| Back to Top | |
| Date: | 15-OCT-2008/09:10 |
| Activity: | Research Experimental trip type code "RWG" was added to the 2 observed weighted gear trips |
| Persons Involved: | EForney |
| Description: | The experimental trip type of RWG was added to the 2 observed weighted gear research trips conducted by Mike Musyl. |
| Back to Top | |
| Date: | 15-OCT-2008/09:10 |
| Activity: | Research Experimental trip type code "RBG" added to the 6 blue colored fishing gear trips |
| Persons Involved: | EForney |
| Description: | The experimental trip type of RBG was added to the 6 blue colored fishing gear research trips conducted by Christofer Boggs. |
| Back to Top | |
| Date: | 09-OCT-2008/07:10 |
| Activity: | Soak time rounding error |
| Persons Involved: | EFORNEY |
| Description: | Soak times that are at the half hour correctly get rounded to the next full hour up until 24 hours. For example 17.5 hours gets rounded to 18 hours and 22.5 hours gets rounded to 23 hours. At 24 hours and above, however, it was discovered that every third hour that is at the half hour erroneously gets truncated. For example: 23.5 hours get rounded to 24 hours 24.5 hours gets truncated to 24 hours but should be rounded to 25 hours 25.5 hours gets rounded to 26 hours 26.5 hours get rounded to 27 hours 27.5 hours gets truncated to 27 hours but should be rounded to 28 hours 28.5 hours gets rounded to 29 hours 29.5 hours get rounded to 30 hours 30.5 hours gets truncated to 30 hours but should be rounded to 31 hours |
| Back to Top | |
| Date: | 09-OCT-2008/07:10 |
| Activity: | Soak times were updated or verified on 135 records. |
| Persons Involved: | EFORNEY |
| Description: | The soak times for 135 records showed a discrepancy between the soak time in LODS and what the soak time should have been based on the begin set and end haul dates/times and needed to be checked. For 81 records the soak times needed to be updated. 59 of these 81 records were from pre-LODS trips when observers were required to record the soak times with 57 records having erroneously calculated soak times by the observer and 2 records having incorrect soak times due to the observer recording incorrect end haul times. 5 of these 81 records were for LODS trips where the soak time was no longer collected by the observer but automatically calculated by a script after data entry. After the soak times were auto-calculated a correction was made to a date/time field and the soak time did not auto-update. For 17 of these 81 trips the incorrect soak time was due to an error with the soak time script that correctly rounded all soak times at the bottom of the hour to the next highest hour up to 24 hours but then truncated all soak times at the bottom of the hour to the next lowest hour in 3 hour intervals starting with 24 hours and above. There were also 54 pre-LODS trips where the soak time was correct but the end haul date field was incorrect. Many of these incorrect end haul dates were due to the fact that observers only collected an end haul time but not an end haul date for pre-LODS trips. When the data were transferred into LODS the script used automatically populated the end haul date field with the next logical end haul date based on what the begin haul date/time recorded by the observer. In some cases the begin haul date the observer collected was wrong. In other cases the haul took longer than 24 hours which was documented in the notes or margins by the observer. |
| Back to Top | |
| Date: | 26-SEP-2008/10:09 |
| Activity: | LODS slowdown |
| Persons Involved: | EFORNEY |
| Description: | After PIFSC completed the transition to the new MPLS circuit users in LODS started experiencing frequent slowdowns when tabbing through fields. These slowdowns were noticed by me around 7am and occurred up to 10 times per minute for about 1 -2 seconds each but an average maybe 2 - 3 times per minute for about 1 -2 seconds each throughout the morning and up to the time I am writing this activity log. Contacted John Kotsakis around 7:45am. He monitored the latency of traffic and did not found any slowdowns except for one brief one. The traffic was generally around around 16-17ms. Once he noticed that out of 1000 packets sent about 4 sequential packets had a delay at about 400ms. He passed this information on to HQ and Richard Uyeda. HQ notified him later in the day that they did not see any errors between the routers. |
| Back to Top | |
| Date: | 25-SEP-2008/00:09 |
| Activity: | ORA-12154 error message |
| Persons Involved: | EFORNEY |
| Description: | A debriefer received an ORA-12154 error message which happened after he changed his LODS password. It was determined that he used the special character @ in his new password. The @ symbol in Oracle is mistaken for a Net alias and should thus not be used in passwords. |
| Back to Top | |
| Date: | 18-AUG-2008/11:08 |
| Activity: | LODS unavailable |
| Persons Involved: | EFORNEY |
| Description: | While working on a trip in LODS the connection was lost at about 0815 hours. The hourglass appeared and remained. When going to the LODS homepage the following browser message was displayed. The connections was re-established at about 0825 hours. The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings. To attempt fixing network connectivity problems, click Tools, and then click "Diagnose Connection Problems..." Other options to try: Click the Refresh button, or try again later. If you typed the page address in the Address bar, make sure that it is spelled correctly. To check your connection settings, click the Tools menu, and then click Internet Options. On the Connections tab, click Settings. The settings should match those provided by your local area network (LAN) administrator or Internet service provider (ISP). See if your Internet connection settings are being detected. You can set Microsoft Windows to examine your network and automatically discover network connection settings (if your network administrator has enabled this setting). Click the Tools menu, and then click Internet Options. On the Connections tab, click LAN Settings. Select Automatically detect settings, and then click OK. Some sites require 128-bit connection security. Click the Help menu and then click About Internet Explorer to determine what strength security you have installed. If you are trying to reach a secure site, make sure your Security settings can support it. Click the Tools menu, and then click Internet Options. On the Advanced tab, scroll to the Security section and check settings for SSL 2.0, SSL 3.0, TLS 1.0, PCT 1.0. Click the Back button to try another link. Cannot find server or DNS Error Internet Explorer |
| Back to Top | |
| Date: | 08-AUG-2008/00:08 |
| Activity: | Possible DNS problem caused outage |
| Persons Involved: | EFORNEY |
| Description: | At about 0820 hours on August 7th, 2008 the connection to LODS was lost. When opening the LODS home page to attempt to log onto LODS again a "Bad Gateway. The proxy server received an invalid response from an upstream server." was displayed. This outage may have been caused by a DNS problem. |
| Back to Top | |
| Date: | 28-JUL-2008/18:07 |
| Activity: | Correction of incorrect CEL form version from CL.O7.03 to CL.07.03 for all CEL records. |
| Persons Involved: | EFORNEY |
| Description: | All trips with an incorrect CEL form version of CL.O7.03 [07 was accidentally entered as the letter "O"] were corrected to CL.07.03 for all CEL records. |
| Back to Top | |
| Date: | 28-JUL-2008/10:07 |
| Activity: | Research Experimental trip type code "RCH" added to the 97 circle hook trips |
| Persons Involved: | EFORNEY |
| Description: | The experimental trip type of RCH was added to the 97 research circle hook trips conducted by Dan Curran. |
| Back to Top | |
| Date: | 14-MAY-2008/00:05 |
| Activity: | Set & Haul Data Entry Problem |
| Persons Involved: | EFORNEY |
| Description: | The observer, Gavin Shea, was entering data on trip AS0020 on the Set & Hauls when he encountered an error message after finishing set 43 and trying to start entering set 44. He does not remember the wording of the error message. He tried to exit LODS by clicking on the "Exit" button but was not able to exit. He then closed out LODS through the Task Manager. After logging back in Gavin could locate his trip in the drop down box but when he selected it his trip would not come up. At that point he called me over. I closed out LODS through the Task Manager. After Gavin logged back in he was able to bring up his trip. When he went to set 43 on the Set & Haul no data showed up. We discovered that no data showed up for any of the 43 sets. Some of these sets had been entered the day before. At that point I went to the trip history and it clearly showed that data had been entered for all 43 sets. After viewing the trip history and going back to the Set & Haul the data showed up again on the Set & Haul. |
| Back to Top | |
| Date: | 13-MAY-2008/00:05 |
| Activity: | PSEL validations |
| Persons Involved: | EFORNEY |
| Description: | After the migration from Oracle 9i to Oracle 10g NULL values were suddenly being flagged for scan events (S) where behavior codes and sighting methods should be blank and end events (X) where behavior codes, sighting methods, vessel activity and weather codes should be blank. The validations in question were (PSI-BEHAV002, PSI-VESSACT002, PSI-SIGHTMETH002 and PSI-WEATH002). An interim solution to avoid these NULL values from being flagged was to add "AND behavior_type_id IS NOT NULL", AND "vess_activity_id IS NOT NULL", "AND sighting_method_id IS NOT NULL" and "AND weather_type_id IS NOT NULL" to the WHERE clauses of these respective validations until a system wide fix is implemented at a later time. |
| Back to Top | |
| Date: | 17-APR-2008/11:04 |
| Activity: | Vessels List of values (LOV) in LODS has no entries |
| Persons Involved: | JPAPPAS |
| Description: | If no list of values for vessels appears when the button is clicked in LODS, it could be that the dblink account (pifsc_intfc) to the Shark database at HQ is locked. Here's what to do: 1) Call/email HQ (Qian Li, Tina Chang or Navid Rahimi) to have them unlock the account. Once the account is unlocked, go to Toad and find the job that refreshes to materialized view (dbms_refresh.refresh('"DSC"."CGV_VESSELS_MV"'). Re-run (execute) the job to refresh the materialized view. Test LODS to ensure that the Vessel LOV displays properly. |
| Back to Top | |
| Date: | 04-APR-2008/00:04 |
| Activity: | LODS v 2.40 in production |
| Persons Involved: | JPAPPAS |
| Description: | LODS has been upgraded to version 2.40. This version has two main changes: 1) a new Marine Mammals form 2) the addition of an experimental trip type field in the Trips table 3) additional trip statuses. Four data tables and accompanying data views, history views and validation views added: ps_capture_behavior, ps_hooked_loc, ps_entangled_loc, ps_gear_attached_types. Two refcode tables added: lop_capture_behavior, lop_expr_trip_type. Two tables modified: TRIPS, MAMMALS. New trip statuses are added by the LODS Data Manager. Additionally, the LOV for filling in the Observer in data entry is now limited to those with a db_job of 'Biological Observer'. |
| Back to Top | |
| Date: | 05-MAR-2008/00:03 |
| Activity: | LODS Administrative module added |
| Persons Involved: | JPAPPAS |
| Description: | A new module for LODS administrators has been added through the LODS Admin link. Features include: adding/modifying users, locking/unlocking accounts and changing user roles. A report of open/active accounts is also added. |
| Back to Top | |
| Date: | 06-FEB-2008/00:02 |
| Activity: | Marine Mammals data collection enhancement |
| Persons Involved: | JPAPPAS |
| Description: | Added three data tables, three data_views to model for Marine Mammals enhancement: Tables: PS_HOOKED_LOC, PS_ENTANGLED_LOC,PS_GEAR_ATTACHED_TYPES Views: LOP_PS_HOOKED_LOC_V, LOP_PS_ENTANGLED_LOC_V, LOP_PS_GEAR_ATTACHED_V Objects added to lopadm_tabs table; ran grants scripts to grant necessary privileges to objects |
| Back to Top | |
| Date: | 08-MAY-2007/16:05 |
| Activity: | "Stub" records added to Turtles table |
| Persons Involved: | JPAPPAS |
| Description: | Data updated 08-MAY-2007. Fifty-three stub records were added to the Turtles table for pre-LODS turtles that had no Biological Data Form filled out when caught. This eliminates the disparity in record counts between the Turtles and Catch tables. |
| Back to Top | |
| Date: | 07-MAY-2007/07:05 |
| Activity: | LODS down - air conditioning failed in server room at PIFSC |
| Persons Involved: | JPAPPAS |
| Description: | LODS was down part of the weekend and early Monday morning (May 7) due to the air conditioner failing in the server room. Service resumed at 7:55 am Monday, May 7. |
| Back to Top | |
| Date: | 10-APR-2007/18:04 |
| Activity: | New LODS version 2.32 |
| Persons Involved: | JPAPPAS |
| Description: | LODS v. 2.32 is available to users as of 11-APR-2007. Changes and new features include: 1) Table and view changes: Added four fields to bird_mitig table and views: ds_bird_curtain_yn, ds_strateg_bait_discard_yn, ds_birds_present_yn, dh_birds_present_yn; modified validation views 2) Wording changes to several collection forms and the observer manual 3) Data Entry: Allows entry of up to forty sets per trip; users with lop_read_role may create an issue using the Issue button; can now select vessel length from USCG Vessel view; added item image_caption on Images screen; leader diameter entry (Gear Config screen) restricted to tenths; 4) Data Changes: Changed all PSI Event Type A (Approach) records to Event Type B (Behavior); changed gear_removal_type code 07 to code 05 and code 08 was changed to code 06; 5) Database changes: Deleted PSI Event Type A from lop_psi_event_type refcode table; deleted Gear Removal Types 07, 08, 10 and 11 from lop_gear_remvl_type.. |
| Back to Top | |
| Date: | 10-APR-2007/17:04 |
| Activity: | Ref table updated: lop_psi_event_type |
| Persons Involved: | JPAPPAS |
| Description: | Ref table: lop_psi_event_type. Code deleted: A (Approach). It was determined that this code was not needed. |
| Back to Top | |
| Date: | 10-APR-2007/17:04 |
| Activity: | Ref table updated: lop_gear_remvl_type |
| Persons Involved: | JPAPPAS |
| Description: | Ref table: lop_gear_remvl_type. Codes deleted: 07, 08, 10, 11. It was determined that these codes were duplicates of existing codes and were not needed. |
| Back to Top | |
| Date: | 24-JAN-2007/00:01 |
| Activity: | PSEL behavior code discrepancy |
| Persons Involved: | EFORNEY |
| Description: | Discovered that the definitions of the behavior code on the form do not match the definitions of the behavior codes in the reference code table starting with behavior code 05. The definition for the behavior codes in the reference code table are off by when. For example the definition behavior code 05 on the form is the definition for behavior code 06 in the reference code table ("Feeding on catch") etc. The definition for behavior code 05 in the reference code table 05 is "More than 150 m from gear" which is not even on the form. Checked all PSEL form versions (PS.03.07, PS.03.10.16, PS.04.02, PS.04.06 and PS.04.10) to see what the behavior code definitions say and they are the same on all of them. Most likely the reference code table will need to be adjusted so that the definitions match what is on the form. Notified Karen Sender, Jan Pappas, Kevin Busscher, Joe Arceneaux and John Kelly about this issue by email (Subject: Behavior Code discrepancy) on 01/24/07 at 8:44am. |
| Back to Top | |
| Date: | 16-JAN-2007/17:01 |
| Activity: | Update missing collect_form_vers data in catch table (LL2239) |
| Persons Involved: | JPAPPAS |
| Description: | Adam Bailey reported that 4 records in the Catch table for trip LL2239, Set 5, Page 2 had no data in collect_form_vers. This error has occurred sporadically in the past. I printed out the history records which showed that the lines involved (12, 13, 14, 15) had included some record deletions before the last four records were inserted. I printed a copy of this history for analysis. To resolve the immediate problem, I created and ran a script to update the collect_form_vers column to the correct version (CL.06.02) for the four records in question. |
| Back to Top | |
| Date: | 19-DEC-2006/11:12 |
| Activity: | Correcting misspelled port names |
| Persons Involved: | EFORNEY |
| Description: | Queried the database to find out how many trips existed with misspelled port names so that I can start making corrections to them. For the departure port there were over 160 and for the arrival port almost 140 trips that had misspelled port names. As many of these trips have been approved it would require opening up issues on over 200 trips. Called Jan to get her opinion and she agreed that it would not be necessary to open up issues for these trips but recommended to add notes to the DP Comments for each of these trips. |
| Back to Top | |
| Date: | 16-OCT-2006/00:10 |
| Activity: | Counting hooked/entangled turtles |
| Persons Involved: | JPAPPAS |
| Description: | This message is to clarify how to count hooked and entangled turtles in the observer data set: All turtles that are hooked and/or entangled will have a record in the Catch table, so the Catch table should be used to count these turtles. The Turtles tables will contain MOST turtle records; however, prior to LODS (August 2003), 53 turtles were not entered into the Turtle table because they lacked Biological records (these were unlanded turtles, primarily leatherbacks). The Turtles table can be used to gain detailed information about a specific turtle catch. |
| Back to Top | |
| Date: | 14-APR-2006/08:04 |
| Activity: | New LODS version 2.31 |
| Persons Involved: | KSENDER |
| Description: | Put LODS v. 2.31 on main page link. Updated version info page. |
| Back to Top | |
| Date: | 27-FEB-2006/11:02 |
| Activity: | Database down 10 minutes |
| Persons Involved: | JPAPPAS |
| Description: | Users reported failures during LODS data entry. It was discovered that the PIC database was down. According to PRice, it may have been a leftover process from the failed overnight backup Russell restarted the databases (PIC and DES) and the system was available again within 10 minutes of the report. |
| Back to Top | |
| Date: | 27-FEB-2006/07:02 |
| Activity: | Database down after failed backup |
| Persons Involved: | JPAPPAS |
| Description: | Eric Forney reported "Bad Gateway" when attempting to get to LODS. RPRice said the backup had falled and the databases had not started up automaatically. He manually started the databases. |
| Back to Top | |
| Date: | 03-FEB-2006/03:02 |
| Activity: | Database down 30 minutes |
| Persons Involved: | JPAPPAS |
| Description: | The database had to be taken down for 30 minutes due to an UPS malfuction (the UPS burned and had to be replaced). LODS personnel were kept apprised of the situation. |
| Back to Top | |
| Date: | 24-JAN-2006/22:01 |
| Activity: | Database down - data unrecovered from 24-JAN-2006 6am - 15:30pm |
| Persons Involved: | JPAPPAS |
| Description: | LODS objects inadvertently dropped due to DBA error. LODS tablespace dropped, which included all LODS objects. Data was recovered from backup tape from the previous night (23-JAN-2006). Data entered on 24-JAN-2006 from 6:00 am through 15:30 pm was not recovered and must be re-entered. |
| Back to Top | |
| Date: | 23-JAN-2006/09:01 |
| Activity: | DS_DETER_YN and DH_DETER_YN - Data erroneous in db |
| Persons Involved: | JPAPPAS |
| Description: | Two columns from the bird mitig table, ds_deter_yn and dh_deter_yn, were found to contain erroneous data. These two columns have never been filled in on a collection form, but the field was erroneously defaulting to 'N' in the database. Comments for each column were changed to reflect the fact that the columns themselves should not be used. When time permits, the columns will be eliminated from the database. |
| Back to Top | |
| Date: | 21-DEC-2005/00:12 |
| Activity: | Planned outage - 1.5 hrs - replace hardware |
| Persons Involved: | JPAPPAS |
| Description: | LODS was down from 12:00 - 1:30 pm today to replace kaku (system housing the LODS database). Unfortunately, the replacement system did not work properly due to incorrectly supplied parts; so another down time will have to be scheduled when the proper parts arrive. |
| Back to Top | |
| Date: | 17-DEC-2005/11:12 |
| Activity: | Unable to enter Catch records in LODS |
| Persons Involved: | JBISSON |
| Description: | Jeremy Bisson (debriefer) reported that an observer was unable to enter data into the Catch table although data could be entered in other screens. By accident, a materialized view log connected to the LODS Catch table had been deleted _as a table_, which caused users to not be able to enter records in catch. Tom Kagehiro deleted the log _as a materialized view log_ which then broke off the dependency and once again allowed users to create and update Catch records. |
| Back to Top | |
| Date: | 14-DEC-2005/16:12 |
| Activity: | Changed Activity Log form and table |
| Persons Involved: | JPAPPAS |
| Description: | Changed Activity Type column to Display Item instead of Combo Box due to slower performance with combo boxes. Also increased length of Descrip column from 2k to 4k to accommodate longer explanations of activities. |
| Back to Top | |
| Date: | 14-DEC-2005/00:12 |
| Activity: | LODS testing from home |
| Persons Involved: | EFORNEY |
| Description: | This morning I tested LODS from my home PC to see whether I would experience the same type of slowdown as in the office. Although I did encounter a few occasional slowdowns it was not nearly as significant as those observers and debriefers have been having in the office. I tested LODS using Mozilla Firefox and IE and checked the Trip Specs, Gear Config, Set & Haul, PSI and Catch. Between 6:30am and 6:45am I tested LODS using Mozilla Firefox and encountered the following slowdowns. Set & Haul: Set 4: 6:36am tabbing from End Set weather code to beaufort scale I got a 20 delay in response time. Set 13: 6:40am tabbing from the end haul latitude degrees to minutes I got a 5 second delay in response time. Between 6:45am and 7:15am I tested LODS using IE and encountered the following slowdowns. Gear Config: Set 9: 6:50am tabbing from branch line "No. Strands" to "Color Code" I encountered a 20 second delay in response time. PSI: 6:54am on page 1, line 3 when tabbing from condition code to species low estimate I encountered a 40 second delay in response time. 6:56am on page 1, line 5 when tabbing from page# page to line# I encountered a 20 second delay in response time. Catch Set 3: At 7:05am when arrowing down on page 3, line 14 to line 15 I encountered a 20 second delay in response time At about 7:20am I called a debriefer to check whether the office was experiencing any slowdowns. The debriefer checked the Catch on the same trip and encountered the following slowdowns. When arrowing down there was on average one slowdown per page 3-4 seconds each. When tabbing across there was at least 1 slowdown per line for about 2-3 seconds each. Overall there was a considerable difference between the response time from home and at the office. The slowdowns at home albeit lasting longer were rather infrequent and did not consitute any problem whereas the slowdowns we have been experiencing in the office have been more frequent at times and lasting shorter but have slowed down data entry and readback |
| Back to Top | |
| Date: | 13-DEC-2005/20:12 |
| Activity: | LOP species table updated |
| Persons Involved: | TSWENARTON |
| Description: | Species groupings updated |
| Back to Top | |
| Date: | 13-DEC-2005/15:12 |
| Activity: | Slowness in LODS Activity Log when keying in Activity Type |
| Persons Involved: | JPAPPAS |
| Description: | Eric Forney noticed that, in entering a record into the Activity Log (from the PIRO office), response was delayed when typing into the Activity Type field. Response was normal (fast) when typing into the Description field. JPappas noted that, from PIFSC, although response was not slow, an hour glass appeared after each keystroke entered in the Activity Type column. Again, response was normal when typing in the Description field. Note that the Activity Type item is a combo box and the Description is not. |
| Back to Top | |
| Date: | 13-DEC-2005/00:12 |
| Activity: | LODS slowdown update |
| Persons Involved: | EFORNEY |
| Description: | LODS has continued to slow down during data entry and readback. Sluggishness also encountered in the Activities Log. Today the slowdown has been extremely noticeable making it difficult for observers to enter data. PIRO, however, is also experiencing Internet and email client slowdowns. Am not sure whether these slowdowns are exacerbating the slowdown in LODS. Jan, Eric, PIFSC IT and PIRO IT have been in contact to resolve the LODS slowdown. Jan tested LODS from Russell Price's home the morning of 12/12/05 and also encountered a slowdown. Eric tested LODS from home the evening of 12/12/05 in both IE and Mozilla and encountered no slowdown. LODS response time virtually instantaneous. Since the LODS slowdown is encountered during the day Eric will test LODS from home the morning of 12/15/05. LODS was also pinged from several computers at PIRO as well as Eric's home computer and the response times were within acceptable parameters according to Mark Masters. |
| Back to Top | |
| Date: | 09-DEC-2005/08:12 |
| Activity: | Application Errors |
| Persons Involved: | EFORNEY, KSENDER |
| Description: | Eric: The error message I just reported for the Issues Manager is not confined to the Issues Manager. Jeremy Willson just informed me that he had encountered an error message in LODS yesterday afternoon when updating a record. I went into LODS and tried a create and change a record in one of my test trips and encountered error messages pertaining to inserting and updating records (see attached Word Doc). An observer currently entering data is also encountering these error messages. Karen: Problem was with dsc.dsc_utilities_pkg - had been worked on yesterday. TKagehiro recompiled package and all well. Down time 07:21-08:37. |
| Back to Top | |
| Date: | 30-NOV-2005/07:11 |
| Activity: | Around 0700 hours two debriefers were logged onto LODS and experienced severe sluggishmess. At times when arrowing down records or going from one set to the next it would take 5s-30s to get a response |
| Persons Involved: | EFORNEY |
| Description: | |
| Back to Top | |
| Date: | 16-NOV-2005/00:11 |
| Activity: | Database slow - 5 minute downtime to reset buffer cache size |
| Persons Involved: | JPAPPAS |
| Description: | Eric Forney reported that LODS data entry was slow. The slowdowns appear to occur intermittently. Problem could not be replicated at PIFSC, however, slowdowns were signifcant at PIRO (e.g., 2 minutes to bring up a trip). There have been a large number of users (13-15) entering data today. After consulting with Russell Price and Tom Kagehiro, it was decided to increase buffer cache size since Tom noticed that 1) the system was slow during data inputs and edits 2) buffer cache size had been decreased since moving from mebachi. R. Price increased db_cache_size from 16M to 64M and log_buffer from 180224 to 327680. The latter was increased because we show a large number of times that processes were waiting for space in the redo log buffer. Eric Forney will monitor the system on Monday to see if the slowdowns continue when large numbers of observers are present. |
| Back to Top | |
| Date: | 14-NOV-2005/07:11 |
| Activity: | Report of an unusual error message |
| Persons Involved: | EFORNEY |
| Description: | Eric Siemer reported receiving a "register failk" error message when having LODS open. He's been getting this error message for about a week. The Bluebar reads "asdas". Error message reported to Jan by phone. Screenshot sent to Jan and PIROHelpDesk. Eric Siemer also had additional IE Browser Windows open so it is possible this error message is unrelated to LODS. A Google search indicates this might be a JAVA related problem. |
| Back to Top | |
| Date: | 21-OCT-2005/00:10 |
| Activity: | Specimen type was changed from gonad (female) to just gonad as gonads are collected from female and male specimens |
| Persons Involved: | EFORNEY |
| Description: | |
| Back to Top | |
| Date: | 10-OCT-2005/17:10 |
| Activity: | New version of LODS (v. 2.30) online |
| Persons Involved: | JPAPPAS |
| Description: | A new version of LODS is now online. Major change: Database version changed from Oracle 8.1.7 to Oracle 9i (9.02.05). Minor changes to data entry. |
| Back to Top | |
| Date: | 03-OCT-2005/00:10 |
| Activity: | Economic data notification protocol |
| Persons Involved: | EFORNEY |
| Description: | As per email from Tim Ming from 09/26/05 the economic data notification protocol has changed from emailing Tim Ming and cc'ing Minling Pan for every trip to the following new protocol: 1. If the observer has collected economic information, please DO NOT send me an email letting me know it has come in and that there is a copy in the folder. We will all assume that copies of those economic forms are in the folder waiting for me to pick up every week. 2. If the observer has not collected economic information, please DO send me an email explaining the reason why. As of 10/03/05 the trip checklist item for the economic data "Email Tim Ming and cc Minling Pan about economic data" (display item 62) has been replaced with a new checklist item economic data "Checked economic data. Email Tim Ming & Minling Pan if none collected" (display item 61). Display item 62 is no longer mandatory and display item 61 is mandatory to answer. Both display items with continue to show up in the trip checklist until the new version 1008 goes live at which point only display item 61 will be displayed. |
| Back to Top | |
| Date: | 21-SEP-2005/00:09 |
| Activity: | Column format info on HTML page of website does not appear |
| Persons Involved: | JPAPPAS |
| Description: | Recurring problem of table/column format not displaying on the LODS website. Problem occurs when the LODS Admin form user does not have permission to write/overwrite to the directory on the linux server. Even if permissions are changed (chmod), the file must sometimes be deleted before a new, updated file can be created. Note: The file is created when a data manager presses the Columns button on the Tables screen of the LODS Admin form. If no columns are displayed on the HTML page, then it is probably because of a permissions problem on the app server. |
| Back to Top | |
| Date: | 09-AUG-2005/16:08 |
| Activity: | Added species code (Driftfish - 059) |
| Persons Involved: | JPAPPAS |
| Description: | A species code for Driftfish (Nomeidae, Cubiceps spp.) was added as requested by E. Forney and S. Arceneaus. |
| Back to Top | |
| Date: | 20-JUL-2005/12:07 |
| Activity: | LODS Website unavailable - 10 minutes |
| Persons Involved: | JPAPPAS |
| Description: | Tom Swenarton called to say he was unable to get to the LODS Website. Screen message was "Bad Gateway!...unable to complete lookup for mid1.pic.gov". I talked with Russell Price who said Richard Uyeda had made a change to DNS that didn't take. Richard was able to get things working again within ten minutes. |
| Back to Top | |
| Date: | 13-JUL-2005/00:07 |
| Activity: | Thirdcheck |
| Persons Involved: | EFORNEY |
| Description: | Recently an analysis was completed to determine the necessity of continuing the third check on the longline data. The result was that only about 7% of the trips required minor changes at this stage of the data editing, amounting to 141 inserts, deletions, or updates. Of these 141 changes, 95 of these changes occurred in 7 data fields. Since these changes are not major changes, it was decided to continue with the spot check on the third data check. However, during the spot check, only the 7 data fields where the majority of these changes were found will be checked. These 7 data fields are as follows: SPECIMEN: BIRD_MITIG:DH_AT_NIGHT_YN CATCH:GENDER_ID CATCH:HK_NUM CATCH:TAG_YN GEAR_CFG:SZ-HKS IMAGES:DESCRIP In addition, for trips with protected species hookings or entanglements, all the fields concerning these protected species interactions will still be checked. |
| Back to Top | |
| Date: | 11-JUL-2005/06:07 |
| Activity: | LODS not available (during non-business hours) |
| Persons Involved: | EFORNEY |
| Description: | Eric Forney reported that LODS was not available from PIRO ("Bad Gateway..." message). The error also occurred at the Center. The DHCP server at the Center had gone down over the weekend, causing a number of problems. mid1 server had to be rebooted. LODS was available again by 7:40am. |
| Back to Top | |
| Date: | 06-JUL-2005/11:07 |
| Activity: | LODS down 20 minutes |
| Persons Involved: | JPAPPAS |
| Description: | Observer reported error ORA-4062 "timestamp of xxxx has been changed" when attempting to use the "Dupe Last" button on both the Gear Cfg screen and Bird Mitigation screen. I was able to duplicate the error. Users were asked to logout at lunchtime (11:30am) so that the LODS form could be recompiled. Recompilation solved the problem and users were informed that they could resume work at 11:50am. |
| Back to Top | |
| Date: | 01-JUL-2005/00:07 |
| Activity: | New versions of Catch Log and Gear Cfg now online |
| Persons Involved: | JPAPPAS |
| Description: | Also, new versions of the Catch Log form (CL.05.06) and Gear Cfg form (GC.05.03) are now online. |
| Back to Top | |
| Date: | 01-JUL-2005/00:07 |
| Activity: | New version of LODS (2.21) online |
| Persons Involved: | JPAPPAS |
| Description: | A new version of LODS (2.21) is now online. This version changes some measurement protocols. |
| Back to Top | |
| Date: | 30-JUN-2005/00:06 |
| Activity: | Bird species added to lopadm_species_groupings |
| Persons Involved: | JPAPPAS |
| Description: | Twenty-one bird species were added as requested by DSCR #6; three additional species will be added after necessary research is done to classify them properly. All codes added were in the 600 - 699 range. |
| Back to Top | |
| Date: | 30-JUN-2005/00:06 |
| Activity: | Script grants_to_lop_admin_role.sws modified |
| Persons Involved: | JPAPPAS |
| Description: | Script was modified to allow a LODS administrator to delete from the table lopadm_collect_forms_vers. |
| Back to Top | |
| Date: | 07-JUN-2005/00:06 |
| Activity: | Added 13 observers (trainees) as Oracle users |
| Persons Involved: | JPAPPAS |
| Description: | Thirteen new observers were added as Oracle users as per instructions from Eric Forney. |
| Back to Top | |
| Date: | 22-APR-2005/07:04 |
| Activity: | Unable to access LODS - downtime 3 hours |
| Persons Involved: | EFORNEY |
| Description: | Eric Forney reported a database error when attempting to access the LODS data Entry form: ORA-1422 exact fetch returns too many rows... The problems was 2 rows in the lopadm_tab_vers table were inadvertently marked as Current (only one version of a given table should be marked as current) during the modification of a data table yesterday. The problem was fixed and the database was available by 9:30am. |
| Back to Top | |
| Date: | 21-APR-2005/00:04 |
| Activity: | Database table modified - PS_INTERACT |
| Persons Involved: | JPAPPAS |
| Description: | The GRP_INDIV_IDENTITY column of the PS_INTERACT data table was widened from 2 characters to 3 characters to accommodate a larger number of groups of animals (more than 99) due to increased bird interaction on swordfish trips. The table version is now 10.1. |
| Back to Top | |
| Date: | 28-MAR-2005/00:03 |
| Activity: | Observers begin entering data using offset circle hook code |
| Persons Involved: | JPAPPAS |
| Description: | Due to numerous shallow set trips beginning to arrive, it was decided to allow observers to enter data using code 07 (offset circle hook) as the hook type despite the fact that PIFSC signoff on this change request was not yet received. |
| Back to Top | |
| Date: | 25-MAR-2005/00:03 |
| Activity: | Database down - planned outage - 3 hrs 20 min |
| Persons Involved: | JPAPPAS |
| Description: | The database was down from 6:00am to 9:20am for repair of potentially failing drives. Russell Price notified users of planned outage the day before. |
| Back to Top | |
| Date: | 24-MAR-2005/11:03 |
| Activity: | Species code added (BE - Bryde's Whale) |
| Persons Involved: | JPAPPAS |
| Description: | A new species code (BE- Bryde's Whale) was added to newobs.LOP_MAMMAL_SPECIES and to opdt.ORGANISM_CROSS-REFERENCE table. |
| Back to Top | |
| Date: | 24-MAR-2005/11:03 |
| Activity: | Refcode table updated - LOP_GEAR_ATTACHED_TYPE (U-Unknown) |
| Persons Involved: | JPAPPAS |
| Description: | A code for U (Unknown) was added to the newobs.LOP_GEAR_ATTACHED_TYPE table in both the dev and prod dbs |
| Back to Top | |
| Date: | 24-MAR-2005/00:03 |
| Activity: | Added history tables for several LODS admin tables |
| Persons Involved: | JPAPPAS |
| Description: | History tracking was added to several LODS admin tables: LOPADM_TABS, LOPADM_TAB_VERS, LOPADM_DATA_SYSTEM_VERSIONS, LOPADM_DATA_ISSUES_MGR, LOPADM_SPECIES_GROUPINGS, LOPADM_ROLE_DESCRIPS, LOPADM_VALIDATION_CODES, LOPADM_COLLECT_FORMS_VERS. The names of several of these tables had to be aliased (due to the length of the name) in order to create the history objects. |
| Back to Top | |
| Date: | 22-MAR-2005/00:03 |
| Activity: | Continuing problems with incorrect collection forms versions |
| Persons Involved: | JPAPPAS |
| Description: | Debriefers continue to report that incorrect collection forms versions are entered in the database and need to be modified. IT suggested to E. Forney that a notice be sent to debriefers to remind them to have the collection forms in front of them when they initialize a trip so that these errors do not occur. Once the incorrect form version is entered, then every record from that form will contain the incorrect version. To correct the problem, an update must be made to each incorrect record and to the lop_trip_collect_forms table to insert the correct form version. Bottom line: debriefers need to be extremely careful that the correct form versions are entered when they initialize a trip. |
| Back to Top | |
| Date: | 21-MAR-2005/08:03 |
| Activity: | PIRO Internet interruptions cause database access problems |
| Persons Involved: | JPAPPAS |
| Description: | Tom Swenarton called to say they were only sporadically able to log on to LODS so they were sending the observers home for the day. He later found that the PIRO Internet was going up and down during the day and had caused the disruption of service. I told Tom that a direct line exists between PIRO and PIFSC and that, with the proper configuration on their systems, they should be able to access LODS even when their internet service is down. Tom will be contacting their IT staff about this problem. |
| Back to Top | |
| Date: | 16-MAR-2005/00:03 |
| Activity: | New Offset Circle code 07 available. Measurements TL & DD (sharks) and CK & HG (billfish) eliminatedand |
| Persons Involved: | EFORNEY |
| Description: | |
| Back to Top | |
| Date: | 16-MAR-2005/00:03 |
| Activity: | Catch Event Log version 05.03 available to observers |
| Persons Involved: | EFORNEY |
| Description: | |
| Back to Top | |
| Date: | 16-MAR-2005/00:03 |
| Activity: | Gear Configuration version 05.03 available to observers |
| Persons Involved: | EFORNEY |
| Description: | |
| Back to Top | |
| Date: | 16-MAR-2005/00:03 |
| Activity: | Added 16 observers (trainees) as Oracle users |
| Persons Involved: | JPAPPAS |
| Description: | |
| Back to Top | |
| Date: | 16-MAR-2005/00:03 |
| Activity: | Refcode table updated - LOP_HOOKED_LOC |
| Persons Involved: | JPAPPAS |
| Description: | Code 12 (Carapace) was added to the newobs.lop_hooked_loc table |
| Back to Top | |
| Date: | 04-MAR-2005/11:03 |
| Activity: | Database down |
| Persons Involved: | KSENDER |
| Description: | Mebachi was down this morning until 11:30 a.m. due to bus errors. |
| Back to Top | |
| Date: | 01-MAR-2005/00:03 |
| Activity: | Invalid username or password when accessing LODS |
| Persons Involved: | JPAPPAS |
| Description: | If you receive the error "Invalid username or password" when accessing LODS data entry, it could be that the Oracle database is down. |
| Back to Top | |
| Date: | 01-MAR-2005/00:03 |
| Activity: | Database down - 2 hrs due to hardware failure |
| Persons Involved: | JPAPPAS |
| Description: | Due to a faulty disk drive on mebachi, the database was down when users came to work (outage reported by Eric Forney). Russell Price started the database, but he said that some of the Oracle redo logs were stored on this disk and that the the database would crash again when those logs were accessed. Users were asked to log off the database while Price replaced the drives. The database was restarted by 9:20am and Dawn Golden at PIRO was notified that LODS was again available. |
| Back to Top | |
| Date: | 04-FEB-2005/13:02 |
| Activity: | LODS v. 2.20 release |
| Persons Involved: | KSENDER |
| Description: | Release of LODS v. 2.20, new system v. 2.20, new ias server of mid1, new url ias.pifsc.noaa.gov/lds/lods.html for LODS home page. New release required to migrate from NT servers but also allowed for minor LODS fixes. View LODS version history for details. |
| Back to Top | |
| Date: | 13-DEC-2004/00:12 |
| Activity: | Modified LOP_DE_ROLE |
| Persons Involved: | JPAPPAS |
| Description: | The LOP_DE_ROLE can no longer insert into LOP_TRIPS_V. Both the INSERT and DELETE privileges were revoked for this table. This was done to help resolve the problem of erroneous trips being created by observers when they forget to select their trip number from the pulldown menu. |
| Back to Top | |
| Date: | 22-NOV-2004/12:11 |
| Activity: | Posted new pre-live version 2.13 |
| Persons Involved: | KSENDER |
| Description: | |
| Back to Top | |
| Date: | 28-OCT-2004/08:10 |
| Activity: | Trip Check List |
| Persons Involved: | EFORNEY |
| Description: | Retired all check boxes in the trip check list that pertain to the Vessel Reimbursement Form since the observer program no longer requires this form to be completed. |
| Back to Top | |
| Date: | 21-OCT-2004/00:10 |
| Activity: | Trip Summary won't display; ORA-24347; NULL column |
| Persons Involved: | JPAPPAS |
| Description: | Debriefer R. Kupfer called to say he couldn't display the Trip Summary for Trip #LL1427 after entering 30 sets. After testing, I found that the error ORA-24347 ("Warning of a NULL column in an aggregate function") was displayed on the status bar. The query of the view (lopsum_tripset_v) worked in SQL*Plus. I found that there had been no logbook page numbers entered for any of the sets (this was a null column in the view). Told Rich to insert the logbook page numbers and try the summary again. |
| Back to Top | |
| Date: | 05-OCT-2004/00:10 |
| Activity: | Added 23 observers (trainees) as Oracle users |
| Persons Involved: | JPAPPAS |
| Description: | |
| Back to Top | |
| Date: | 04-OCT-2004/10:10 |
| Activity: | Added S code (Scan Count) to Prot Spec Event Type |
| Persons Involved: | JPAPPAS |
| Description: | An S code (Scan Count) was added to the protected species Event_Types table. The meaning and use of scan count is available in the decription column of the Event_Types reference table. |
| Back to Top | |
| Date: | 01-OCT-2004/00:10 |
| Activity: | Database down for planned outage all day |
| Persons Involved: | JPAPPAS |
| Description: | The Center's Oracle database was down all day for maintenance of the system the database is stored on. |
| Back to Top | |
| Date: | 16-SEP-2004/23:09 |
| Activity: | Data views updated - Species_name columns dropped |
| Persons Involved: | JPappas |
| Description: | The species_name column was dropped from several views and one table. Species_name was dropped because species_common_name serves exactly the same function. The form view versions were also updated. |
| Back to Top | |
| Date: | 13-SEP-2004/06:09 |
| Activity: | New LODS data entry version (v. 2.11) online |
| Persons Involved: | KSENDER |
| Description: | Observers began using LODS v. 2.11 for data entry |
| Back to Top | |
| Date: | 10-SEP-2004/18:09 |
| Activity: | Refcode table updated - LOP_Damage |
| Persons Involved: | JPappas |
| Description: | Two changes were made to the LOP_DAMAGE refcode table that affect damage column data in the Catch table. Beginning with LODS Data System v.2.11, a damage code of UO (Unobserved) is available. Also, the code for damage_id 6001 was changed from NO to ND (meaning No Damaged Observed) because of possible confusion of the meaning of NO. |
| Back to Top | |
| Date: | 10-SEP-2004/18:09 |
| Activity: | Data Updated - Catch.damage_id, damage_code |
| Persons Involved: | JPappas |
| Description: | Updates were made to damage column data in the Catch table after the LOP_DAMAGE reference code table was modified (see other Activity Log entry for details). Legacy data was updated as follows: Pre-LODS v. 0.0 - NULL damage_id changed to UO (these were legacy protected species records where no damage was recorded; see bird, turtle or mammal tables for details on these records.) LODS versions 1.00 thru 2.1: damage_id 6001 was hanged to the id for UO; then NULL damage_ids were changed to 6001 (ND). Damage codes UO and ND entered under Data Entry v. 2.1 will need to be updated since both codes mistakenly went into the database as NULL. |
| Back to Top | |
| Date: | 10-SEP-2004/09:09 |
| Activity: | Meeting at PIRO |
| Persons Involved: | LODS Staff |
| Description: | Discussed creation and resolution of data issues and who should be notified, protocols for correcting certain types of data errors, use of DP_Comments (data processing comments), impending implementation of the new LODS version (2.11) tonight, resolution of damage codes, network downtime scheduled for second week of November |
| Back to Top | |
| Date: | 12-AUG-2004/14:08 |
| Activity: | LODS Data Entry - change Trip Status failure |
| Persons Involved: | JPAPPAS |
| Description: | Debriefer tried to change a trip status from INITIAL to ENTERED and got the message: "A WHEN OTHERS error has occurred in BTN_TRIP_STATUS. Please contact the data manager with this info...". Error actually was caused by a failure of the LOP_VALID package during trip validation that occurs prior to the status change. The underlying table in the LOP_VALID package (LOPVAL_VALIDATION_CODES) had been altered by the DBA (field was lengthened), but the package had not been recompiled and was thus invalid. The error went away once the LOP_VALID package was recompiled. |
| Back to Top | |
| Date: | 12-AUG-2004/14:08 |
| Activity: | LODS Validation - Err Msg field too short |
| Persons Involved: | JPAPPAS |
| Description: | Eric Forney requested that the error message field in the data validation table be lengthened since he has an error message that is longer than allowed. DBA altered the table LOPVAL_VALIDATION_CODES to allow 500 characters for the error message instead of 200. |
| Back to Top | |
| Date: | 10-AUG-2004/00:08 |
| Activity: | LODS Data Entry - Tripnum Dropdown Error |
| Persons Involved: | JPAPPAS |
| Description: | Symptom: The dropdown menu for trip numbers displayed only ALL or NONE instead of the list of trip numbers. The message on the status bar was ORA- 1422 (Exact fetch returns more than requested number of rows). Downtime: approx. 1 hour. Problem was that two rows pertaining to the Observer Manual version in the table LOPADM_COLLECT_FORMS_VERS were marked (by accident) as Default_YN = 'Y'. This caused the trip number dropdown list to fail. Once the collection form versions table was corrected, the problem went away. |
| Back to Top | |
| Date: | 26-JUL-2004/00:07 |
| Activity: | Species - 5 codes added to database tables |
| Persons Involved: | JPAPPAS |
| Description: | Five species were added to the species and species grouping table: 042 - Jack, Cottonmouth; 056 - Escolar, Roudi's; 132 - Manta ray, Giant; 133 - Mobula (Devil ray); 290 - Triggerfish, Pelagic |
| Back to Top | |
| Date: | 14-JUL-2004/00:07 |
| Activity: | Refcode table created - LOP_DECLARED_TRIP_TYPE |
| Persons Involved: | JPAPPAS |
| Description: | The reference code table LOP_DECLARED_TRIP_TYPE was added due to shallow set regulations that went into effect April 2, 2004. Longline vessel operators must declare whether the trip is a shallow set trip or a deep set trip. |
| Back to Top | |
| Date: | 28-JUN-2004/00:06 |
| Activity: | Column additions to TRIPS, SET_ENVIRON tables |
| Persons Involved: | JPAPPAS |
| Description: | Two columns were added to data tables to accommodate swordfish fishery data. In the TRIPS table, the new column is DECLARED_TRIP_TYPE_ID. In the SET_ENVIRON table, the new column is CERTIFICATE_NUM. The new columns will not be used until the next version of the data system (2.10) is implemented. |
| Back to Top | |
| Date: | 28-JUN-2004/00:06 |
| Activity: | LODS Data Entry - Inability to change trip status |
| Persons Involved: | JPAPPAS |
| Description: | Three debriefers reported that they were unable to change a trip's status. The error message was "A WHEN_OTHERS error has occurred in btn_trip_status. Please contact the database manager." It was discovered that several of the validation modules objects were invalid (the LOP_VALID package as well as the LOPVAL... views). These objects were recompiled and the problem was resolved. |
| Back to Top | |
| Date: | 28-JUN-2004/00:06 |
| Activity: | Table version IDs modified |
| Persons Involved: | JPAPPAS |
| Description: | Several IDs in the LOPADM_TAB_VERS table were changed and the sequence populating the ID column was dropped and renamed to LOPADM_TAB_VERS_SEQ to conform to the naming standard. A BRI trigger to automatically populate the ID column was also created. The ID changes should not have any effect on system operation. |
| Back to Top | |
| Date: | 07-JUN-2004/00:06 |
| Activity: | Added 12 observers (trainees) as Oracle users |
| Persons Involved: | JPAPPAS |
| Description: | |
| Back to Top | |
| Date: | 03-MAY-2004/10:05 |
| Activity: | Legacy Data - To-Do List |
| Persons Involved: | JPAPPAS |
| Description: | Here are some data entry tasks that could be done -- as time permits -- to complete legacy (Trips LL0001 thru LL1064 and LL1068) observer data: 1) Enter comments from the Trips collection form into the TRIPS table in trips prior to trip LL0342 2) Enter comments from the Catch Log or PS Tally Log into the CATCH table in trips prior to trip LL0340 3) Enter comments from the Protected Species Interactions and Sightings collection form into the PS_INTERACT table in trips prior to trip LL0342 4) Enter vessel_name, operator_lname and operator_fname_mi into TRIPS in trips prior to trip LL0632 and between trips LL0671 and LL0690. This data was never entered into the Oracle database. 5) Resolve and correct vessel_name, permit_num, operator_lname and operator_fname_mi in TRIPS (all trips, not just legacy trips). Many of these columns have several variations for the names of people and ships. 6) Enter legacy bird specimen data into the SPECIMEN table (see query in the 'LODS Admin Guide, section 'Pending Data Updates' dated 10/22/2003) 7) Enter legacy turtle specimen data into the SPECIMEN table (see query in the 'LODS Admin Guide, section 'Pending Data Updates' dated 10/22/2003). This would be a major job-- to analyze the existing comments for specific info about specimens collected. 6) Convert data from research trips (trip numbers beginning 'EX...') from MS-Access into Oracle and then into LODS 7) Add Observer trips to LODS that were never entered into the database due to technical difficulties on the cruise, etc. Example: Trip LL0324 |
| Back to Top | |
| Date: | 29-APR-2004/00:04 |
| Activity: | LODS Data Update - turtle positions |
| Persons Involved: | JPAPPAS |
| Description: | The captured longitude position (direction) for any turtle record entered prior to trip LL1065 was corrected. The data had been erroneously converted (E was entered as W and W was entered as E) when it was moved from the prior version of the database into LODS. |
| Back to Top | |
| Date: | 13-APR-2004/10:04 |
| Activity: | DB Update - history triggers recompiled |
| Persons Involved: | JPAPPAS |
| Description: | The history triggers for the LODS data tables were recompiled to ensure that history would be recorded for all current columns in the table. The impetus for the recompilation was that it was discovered that collect_form_vers changes were not being recorded in the Catch history table. Also, damage_id was not being recorded. These were the last two columns added to the Catch table, and the history trigger had not been compiled after they were added. To ensure that columns in other tables would be recorded in their history tables, all data table history triggers were recompiled using the script recompile_all_hist_trgs.sql. |
| Back to Top | |
| Date: | 08-APR-2004/07:04 |
| Activity: | LODS down - DB - 45 min |
| Persons Involved: | JPAPPAS |
| Description: | Eric Forney reported that three debriefers had tried to log on to LODS this morning between 6:30am and 7:00am and they got the message "Invalid username and password." When he tried again at 7:15am, he was able to log on. I called Russell Price who said he shut the database down the night before for routine maintenance and he had forgotten to start the database again. He started the database up at about 7:10 this morning. |
| Back to Top | |
| Date: | 08-APR-2004/00:04 |
| Activity: | Data Validation |
| Persons Involved: | EFORNEY, JPAPPAS |
| Description: | The validation checks were finalized for this version of LODS. All trips from LL1065 forward (excluding LL1068 which was entered using MS-Access) will be validated using the existing validations before being marked APPROVED. Also legacy trips (LL0001 through LL1064) can have validation run against them since each validation check now includes an "effective from" version id. |
| Back to Top | |
| Date: | 29-MAR-2004/00:03 |
| Activity: | DB Update - protected species |
| Persons Involved: | JPAPPAS |
| Description: | Protected species final disposition (condition) data formerly stored in the Protected Species Tally table is now available in the Kept/Return column on the Catch Tally form. To accommodate this move, an additional code (I - Injured, available only for protected species records) was added to the column. Legacy data for trips LL0001 through LL1064 and LL1068 has been moved to this column. More detailed information (if available) on the animal's final disposition may be found on the Life History form in the Disposition column. |
| Back to Top | |
| Date: | 26-MAR-2004/00:03 |
| Activity: | Mtg - Protected species disposition |
| Persons Involved: | HL, PIRO Staff |
| Description: | PIC and PIRO staff met to discuss protected species animal disposition, additional validations before approving first round of trips from LODS, change control procedures and versioning |
| Back to Top | |
| Date: | 22-MAR-2004/10:03 |
| Activity: | LODS down - database - 30 min |
| Persons Involved: | JPAPPAS |
| Description: | The PIC Oracle database was down for approx. 30 minutes from 8:30 am to 9:00 am due to an error occurring while writing to the system audit table (see text of error below). Two LODS users were affected. Once the error occurred, additional users were not able to log in to Oracle. The error was reported by DBA Russell Price. The error was not caused by LODS activity. Russell Price corrected the problem which involved the method in which tablespace extents were being allocated on the SYSTEM tablespace and also involved the combination of a system auditing command and the creation of a materialized view that caused the SYSTEM tablespace to run out of space. Russell has altered the way these extents will be allocated in future sessions. We will also be cleaning up the audit log table and changing the audit command that caused the problem. Error message text: unable to allocate extent ... in tablespace SYSTEM...sys.AUD$... |
| Back to Top | |
| Date: | 27-FEB-2004/07:02 |
| Activity: | LODS DE |
| Persons Involved: | KSENDER |
| Description: | Installed LODS v. 2.02 |
| Back to Top | |
| Date: | 26-FEB-2004/00:02 |
| Activity: | LODS DE |
| Persons Involved: | KSENDER |
| Description: | Kevin Busscher and John Buchanan requested change to put species common name back on each catch line. Karen made change and added a catch PRINT function. |
| Back to Top | |
| Date: | 25-FEB-2004/00:02 |
| Activity: | LODS DE |
| Persons Involved: | KSENDER |
| Description: | Release of LODS v. 2.01 |
| Back to Top | |
| Date: | 20-FEB-2004/07:02 |
| Activity: | Data update |
| Persons Involved: | JPAPPAS |
| Description: | All trips having status COMPLETED (124 trips) were changed to status ENTERED to prepare for changeover to the new version of the data entry form. |
| Back to Top | |
| Date: | 19-FEB-2004/02:02 |
| Activity: | LODS down - network - 1 hr |
| Persons Involved: | JPAPPAS |
| Description: | The network was down for approx. one hour while Richard Uyeda assessed some problems at PIC. |
| Back to Top | |
| Date: | 18-FEB-2004/00:02 |
| Activity: | Oracle accounts - new observers |
| Persons Involved: | JPAPPAS |
| Description: | Nineteen observer trainees were given Oracle accounts today. |
| Back to Top | |
| Date: | 17-FEB-2004/09:02 |
| Activity: | LODS down - network - 2 hr |
| Persons Involved: | JPAPPAS |
| Description: | Network problems at PIC caused a 2-hour downtime (approx. 8am to 10:00 am) for LODs data entry via the web. Debriefers could still access the LODS database via SQL*Plus or Crystal Reports. |
| Back to Top | |
| Date: | 02-FEB-2004/09:02 |
| Activity: | LODS down - database - 15 min |
| Persons Involved: | JPAPPAS |
| Description: | Tom Swenarton reported an error (ORA-04031: unable to allocate 4200 bytes of shared memory) while running the Trip Validation program. Karen Sender at the same time was experience "not normal" database behavior. Eric Forney had the four debriefers who were on the system log off, and then Russell Price rebooted the database. |
| Back to Top | |
| Date: | 01-JAN-2004/02:01 |
| Activity: | PSI Table Comment Workaround |
| Persons Involved: | EFORNEY |
| Description: | When the PSI comment check box is unchecked all other PSI Comments memo fields for all other records become disabled and cannot be accessed. Workaround: 1. Temporarily check the comments check box on another record that has no comments. The PSI comments memo fields will become enabled again. If during the course of further editing the PSI comments memo field becomes disabled again uncheck the temporary check box and re-check it. When done editing the PSI make sure to uncheck the temporary check box. or 2. See Eric Forney |
| Back to Top | |
| Date: | 17-DEC-2003/07:12 |
| Activity: | LODS down |
| Persons Involved: | RPRICE, KSENDER |
| Description: | Database instance was down this morning as reported by E. Forney. |
| Back to Top | |
| Date: | 26-NOV-2003/16:11 |
| Activity: | Forms updates |
| Persons Involved: | sarceneaux, Ksender |
| Description: | Discussed removal of No. Hooks hauled, and Set speed data elements form Gear Config. Log. |
| Back to Top | |
| Date: | 25-NOV-2003/15:11 |
| Activity: | LODS DE |
| Persons Involved: | JPAPPAS, KSENDER |
| Description: | Issue with failure of Form Version setting in LODS was resolved. Problem was that there was no default set for PSI and CATCH in LOPADM_COLLECT_FORMS_VERS, the table that lists all the possible versions of the collection forms. This caused these along with GEAR_CFG, BIRD_MITIG, TAG_EVENTS, TURTLES and BIRDS to sometimes not get their form versions set in LOP_TRIP_COLLECT_FORMS and therefore not get the form versions for those form types set in LODS. Problem was resolved by 1. setting a default form version for PSI and CATCH 2. Inserting the missing form versions for the trips where they were missing (trips LL1072, LL1074, LL1102, LL1128, LL1130, LL1131, LL1132, LL1133, LL1135, LL1139, LL1140, LL1143, LL1144) 3. Edited the missing form versions in the LODS data tables. |
| Back to Top | |
| Date: | 31-OCT-2003/00:10 |
| Activity: | Data loaded |
| Persons Involved: | JPAPPAS |
| Description: | The final 23 trips from MS-Access (LL1042, LL1044-LL1064, LL1068) were loaded into the new model. From this point on, all data entry will be done directly into LODS (the Longline Observer Data System) |
| Back to Top | |
| Date: | 22-OCT-2003/00:10 |
| Activity: | Remora attached |
| Persons Involved: | JPAPPAS |
| Description: | A question arose as to whether or not remoras (which are normally caught when the fish they are attached to is caught) should be listed with the hook and float of the hooked fish. It was determined that the hook and float will NOT be entered for the remora; the hook/float info can be put in the notes. If a remora is actually hooked, the hook and float numbers will be entered in the appropriate columns. |
| Back to Top | |
| Date: | 22-OCT-2003/00:10 |
| Activity: | Species Grouping |
| Persons Involved: | JPAPPAS |
| Description: | Species grouping for species 910 (Bony Fish, Other Identified) had been erroneously listed as SHARKS; the species grouping for species 910 was changed to NULL |
| Back to Top | |
| Date: | 16-OCT-2003/11:10 |
| Activity: | Collection Forms |
| Persons Involved: | KSENDER |
| Description: | Catch Form - new form CL.03.10.16 - changed species name for species code 909 to Longnose Lancetfish from Northern Lancetfish. PSI Form - new form PS.03.10.16 - corrected Vessel Activity Codes list per manual. |
| Back to Top | |
| Date: | 23-SEP-2003/00:09 |
| Activity: | LODS FAQ updated |
| Persons Involved: | JPAPPAS |
| Description: | The instructions on how to modify the page/line of a Catch record was incorrect. The instructions should read: "Go to the incorrect line; press Ctrl-Down to open a new blank record; press Shift-F6 to duplicate the record; modify the page/line as necessary; return to the line in error; press the Delete button". The LODS FAQ has been updated. |
| Back to Top | |
| Date: | 23-SEP-2003/00:09 |
| Activity: | LODS DE |
| Persons Involved: | KSENDER |
| Description: | v 1.02 loaded to production. Added Trip Status selections for debriefer. A debriefer can now mark a trip as COMPLETED when an observer has been debriefed and released from data entry. A completed trip can be returned to INITIAL if it is necessary to allow the observer to enter additional data. |
| Back to Top | |
| Date: | 22-SEP-2003/00:09 |
| Activity: | Data issues mgr |
| Persons Involved: | JPAPPAS |
| Description: | The data status of all issues marked as STATUS QUO were modified to read NOT CHANGED. |
| Back to Top | |
| Date: | 19-AUG-2003/00:08 |
| Activity: | Oracle accounts - new observers |
| Persons Involved: | JPAPPAS |
| Description: | Nineteen observer trainees were given Oracle accounts today. |
| Back to Top | |
| Date: | 26-JUN-2003/00:06 |
| Activity: | View format info updated |
| Persons Involved: | JPAPPAS |
| Description: | The Excel spreadsheet containing column descriptions of the Observer longline data views has been updated to reflect the latest changes in the model. The new information is available on the Observer Longline Support and Admin website |
| Back to Top | |
| Date: | 26-JUN-2003/00:06 |
| Activity: | Sample data available in new model format |
| Persons Involved: | JPAPPAS |
| Description: | Sample data (Trips LL0001 through LL1000 and LL1015) have been loaded into tables that mirror the new model. This data is available (for querying only) to current users of Observer Longline data. The data may be queried using Oracle Forms on the Observer Longline Support and Admin website. NOTE: This data is not for reporting purposes. It is to be used for testing purposes only. Please report any errors or difficulties in using the forms. |
| Back to Top | |
| Date: | 25-APR-2003/00:04 |
| Activity: | History tables |
| Persons Involved: | JPAPPAS |
| Description: | Completed history tables and triggers for remaining 3 data tables (billfish_legacy, shark_legacy, tuna_legacy) |
| Back to Top | |
| Date: | 22-APR-2003/00:04 |
| Activity: | Mtg |
| Persons Involved: | HL, PIRO staff |
| Description: | At PIRO; Powerpoint presentation - status of new Observer data system; discussion of contingency plans for system downtime |
| Back to Top | |
| Date: | 21-APR-2003/00:04 |
| Activity: | Mtg |
| Persons Involved: | KSENDER, SARCENEAUX |
| Description: | At HL; reconciliation of data collection forms with data entry screens |
| Back to Top | |
| Date: | 18-APR-2003/00:04 |
| Activity: | Circulars |
| Persons Involved: | JPAPPAS |
| Description: | Added PIAO circulars to Observer support website; some circulars must still be added |
| Back to Top | |
| Date: | 16-APR-2003/00:04 |
| Activity: | E-R Diagrams |
| Persons Involved: | JPAPPAS |
| Description: | Added Entity-Relationship (E-R) Diagrams to Support website |
| Back to Top | |
| Date: | 16-APR-2003/00:04 |
| Activity: | Mtg |
| Persons Involved: | HL, PIRO staff |
| Description: | At HL; small tuna measurements |
| Back to Top | |
| Date: | 09-APR-2003/00:04 |
| Activity: | Users renamed |
| Persons Involved: | JPAPPAS |
| Description: | The following users were renamed to conform to 8-character or less user names. Database privileges were not changed. Passwords were changed. ESANDBERG was changed to ESANDBER JARCENEAUX was changed to SARCENEAUX KBUSSCHER was changed to KBUSSCHE LVANFOSSEN was changed to LVANFOSS |
| Back to Top | |
| Date: | 09-APR-2003/00:04 |
| Activity: | Forms updates |
| Persons Involved: | JPAPPAS |
| Description: | Reftab forms: added 'First Record' and 'Last Record' buttons; added trigger to hide 'Save' button when accessed by non-admin user; added procedure (via stdlib.pll) to prevent insert, update, and delete when user is not authorized; standardized Button Palette of all reftab forms |
| Back to Top | |
| Date: | 08-APR-2003/00:04 |
| Activity: | Data Validation |
| Persons Involved: | JPAPPAS |
| Description: | Created LOP_ERR_CODES table to store data validation checks; now available through the LOP Support form; added preliminary error codes for the TRIPS data table. |
| Back to Top | |
| Date: | 08-APR-2003/00:04 |
| Activity: | Forms updates |
| Persons Involved: | JPAPPAS |
| Description: | Added button to LOP Support application to display LOP 'Draft' data collection forms in .pdf format |
| Back to Top | |
| Date: | 03-APR-2003/00:04 |
| Activity: | Persons table |
| Persons Involved: | TSWENARTON |
| Description: | LOP_PIAO_PERSONS table updated to indicate current personnel and their data roles |
| Back to Top | |
| Date: | 03-APR-2003/00:04 |
| Activity: | Reference tables |
| Persons Involved: | JPAPPAS |
| Description: | LOP reference tables ready for validation by PIAO staff |
| Back to Top | |