Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the amp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the gotmls domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170
Kegiatan Ternak Ikan Dalam Sangkar Di Tanjung Piandang `Lumpuh’ – Independent

Kegiatan Ternak Ikan Dalam Sangkar Di Tanjung Piandang `Lumpuh’

Reading Time: 2 minutes

PARIT BUNTAR | Kegiatan menternak ikan dalam sangkar  yang diusahakan oleh lebih 20 pengusaha ikan di sini lumpuh apabila kesemua ikan yang diternak mati secara mengejut menyebabkan mereka menanggung kerugian kira-kira RM20 juta.

Kesemua ikan berkualiti tinggi itu termasuk siakap, jenahak, bawal dan ikan merah yang siap untuk dijual ke pasaran tempatan dan luar negara termasuk Singapura dan Thailand didapati mati dalam tempoh singkat dipercayai kekurangan oksigen dalam air laut akibat perubahan kualiti air.

Susulan kejadian itu Pengerusi Jawatankuasa Kemudahan Awam dan Infrastruktur , Pertanian dan Perladangan Negeri Perak, Abdul Yunus Jamhari bersama pegawai-pegawai kanan Jabatan Perikanan  Negeri serta Pegawai Daerah Kerian, Mohd Sabli Bakri telah menemui penternak ikan terbabit untuk mendengar keluhan dan permasalahan mereka.

Menurut Abdul Yunus, pihak  Jabatan Perikanan Negeri Perak telahpun mengambil sampel air dan ikan di lokasi untuk ujian makmal FRI Batu Maung, Pulau Pinang.

“Kita sedang menunggu hasil laporan ujian itu yang diharapkan  akan diketahui dalam masa terdekat ini,” katanya kepada pemberita pada Khamis.

Abdul Yunus juga memberitahu, penternak-penternak ikan terbabit juga telah diminta membuat laporan segera berhubung kos kerugian yang mereka tanggung untuk  diserahkan kepadanya bagi tindakan selanjutnya.

Katanya, satu dialog akan diadakan dengan kesemua penternak ikan terbabit dalam masa terdekat ini untuk mendapatkan segala pandangan berhubung permasalahan yang dihadapi dan langkah terbaik ke arah penyelesaiannya.

Mangenai permintaan para penternak ikan terbabit supaya mereka diberi kawasan baru sebagai kawasan penternakan ikan dalam sangkar, katanya, kerajaan negeri sedang menimbang perkara itu memandangkan kawasan penternakan sedia ada tidak sesuai lagi diteruskan sebagai kawasan penternakan ikan.

Sementara itu seorang pengusaha ikan dalam sangkar, Ng Choo Kwan, 35, berkata,  beliau mengetahui ternakan ikannya mati pada jam 7 malam semalam dan kejadian itu sungguh mengejutkan.

Katanya, susulan kejadian itu beliau mengalami kerugian lebih RM200,000.

“Saya serta rakan-rakan penternak yang terllibat bimbang tentang nasib masa depan kami kerana sudah kehilangan punca pendapatan.

“Saya amat mengharapkan kerajaan negeri Perak dapat membantu meringankan beban masalah kami selain memberikan kami kawasan baharu untuk menternak ikan.

“Paling menyedihkan sudah 7 tahun kami menternak ikan … baru semalam berlakunya kejadian mengejutkan ini, kami sudah kehilangan punca pendapatam.

“Paling dikesalkan ikan-ikan  yang sudah siap untuk dipasarkan tiba-tiba mati secara mengejut,” ujarnya.