Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ALIM | Exor
  • Product Communities
  • AssetWise
  • ALIM | Exor
  • Cancel
ALIM | Exor
ALIM | Exor - Wiki 9107- Error : An error occured while processing record : PL/SQL: numeric or value error:
    • Sign In
    • -Exor - Wiki
      • +ALIM Document Manager
      • An Attempt to Reset Your Password Has Failed
      • +AWLRS
      • +Exor Asset Manager
      • +Exor CIM / FIM
      • +Exor Document Manager
      • +Exor Enquiry Manager
      • +Exor Information Manager
      • +Exor Information Manager TMA Reporting Pack
      • -Exor Maintenance Manager
        • Adding a BOQ causes FRM-40200:Field is protected against update
        • Adding new standard item causes HIG-0169 Database constraint violated CNI_INDEX_P1
        • +Budgets - Exor Maintenance Manager
        • Can't Instruct Defects
        • Cannot amend instructed work orders
        • Changing v2 Asset Type Attributes on MAI1400
        • Complete defect manually when interfaces on
        • Could not create map in locator
        • Create new budgets after financial year start
        • +Cyclic Maintenance - Exor Maintenance Manager
        • Defect details changed after load
        • Defect priority list
        • +Defects - Exor Maintenance Manager
        • Duplicate defects created
        • +E5 Payment Run - Exor Maintenance Manager
        • Erroneous defect repair dates
        • Error during Inspection Loader Part 2
        • Error instructing Work Orders M_MGR-0267
        • Error message ‘REP-271468672: A temporary file cannot be created’ is appearing.
        • Error messages HIG-0530 and HIG-0556 on inspection loading
        • Exor MAI M_MGR-0234 in cyclic work orders
        • Forced to add road group when adding standard item to contract
        • HIG-0067 when query cyclic work orders
        • +Hosting/Accessibility - Exor Maintenance Manager
        • How to find MAP Viewer log files
        • How to restart MapViewer Service
        • Illegal Activity Area Code in inspection by group form
        • In Map, zooming in takes a lot of time
        • Inspection Date less on loading RDI files
        • Inspection Loader 'could not read file content'
        • Inspection upload failure (from MCP to Exor MAI)
        • -Inspections - Exor Maintenance Manager
          • 9107- Error : An error occured while processing record : PL/SQL: numeric or value error:
          • Delete an Inspection batch loaded accidently
          • Failed to create Shape file from Inspection Schedule Generation
          • Insurance Claim Report
          • Loading a file through the Maintenance Inspection Loader fails with PLS:00103:Encountered the symbol "||CHR(10)||" when expecting one of the following
          • ORA-04063 'MAI' package body error
          • Save gri parameters to reuse again for schedule inspection report
        • +Interface - Exor Maintenance Manager
        • Invalid path when running interfaces
        • Loader creates doc assoc record but doesnt move files post load
        • +Loaders - Inspection - Exor Maintenance Manager
        • +Loaders - Inventory - Exor Maintenance Manager
        • +Locator - Exor Maintenance Manager
        • Method to clear older defect at zero cost
        • Missing Financial Code EXORR feeder
        • Missing LOCATION keyword when single quote in filename
        • M_MGR-0090 date raised must be <= todays date
        • Notify field on defects form
        • On loading Work Order Invoice (WI) file an error ‘ORA-06502’ appears
        • On scroll BOQ items error “FRM-41050:You cannot update this record” appears
        • ORA 00001 IC PK violation when processing WC file
        • ORA-01400: cannot insert NULL into ("HIGHWAYS"."BOQ_ITEMS"."BOQ_EST_DIM1")
        • ORA-06502: PL/SQL: numeric or value error: character string buffer too small
        • Prevent budget being selected mid way through financial year
        • +Reference - Inspections - Exor Maintenance Manager
        • Unable to run reports
        • Unknown Module MAI3620
        • +Work Orders - Exor Maintenance Manager
      • +Exor Maintenance Mobile
      • +Exor MapCapture
      • +Exor MapCapture (ESRI)
      • +Exor MCI MapCapture Interface
      • +Exor Network Event Manager
      • +Exor Network Manager
      • +Exor Oracle
      • Exor Problems and Solutions
      • +EXOR product placeholder
      • Exor Public Enquiry Manager API
      • +Exor Schemes Manager
      • +Exor Spatial Manager
      • +Exor Street Gazetteer Manager
      • Exor Streetworks Manager
      • Exor Streetworks Mobile
      • +Exor Structures Manager
      • Exor Structures Mobile
      • +Exor TMA Noticing Manager
      • +Exor TMA Permitting Manager
      • +Exor UKPMS
      • Remove @ from the AWLRS Local Password Policy
      • +Transportation Intelligence Gateway
      • Unable to connect to Power BI dataset
      • +Video Series for Exor
      • Working From Home with Exor
    • +AssetWise ALIM for Transportation
    • How To Import SSL Certificate 11g Weblogic

     
     Questions about this article, topic, or product? Click here. 

    9107- Error : An error occured while processing record : PL/SQL: numeric or value error:

    Product(s): Exor Maintenance Manager
    Version(s): 04.07.00.05
    Environment: N\A
    Area: Inspections
    Subarea: N\A

    Problem Description

     

    We have received a number of failed process' in  process monitor for inspections loaded via the inspection loader. The same error keeps appearing 9107- Error : An error occured while processing record : PL/SQL: numeric or value error: character string buffer too small.

    This only happens for files which contain defects with a photo attached as it appears to be the photo line of the file which keeps having the error.  There have been no changes from our side and I have checked files manually and appear correct.

     

     

    Steps to Resolve

    Maybe your software that produces the files might be generating the fields based on the same value  ( LOCATION AND FILENAME in the D record ) so all ok until filename exceeds  30characters -  as max field length for LOCATION is 30 characters  in the specification,  so fails in load validation when it exceeds this length.

    Suggest smaller filenames or change to code to prevent , or edit when loaded in the error correction screen to continue when happens - form MAI4405. Please check association has taken place linking the photo to the defect - if editing to continue.

    My understanding is that the location field has to be a unique value - as used to store photo information against ( unique key )  guess that's why filename has been used, but fails if filename > 30 characters with error 9107.

    Response back said thanks for your help, as advised issue is caused by the filename exceeding 30 characters.  It appears the random number generated by the android API has increased from 8 digits (as it has been for filenames for the last 3+ years) to a 19 digit number causing the filename to change in length and explains - manually correcting the erroneous files today.

    7000868692, Inspection loader- failed process error

     

     

    • PL/SQL: numeric or value error
    • 9107
    • buffer to small
    • Inspection
    • MAI4405
    • 7000868692
    • Share
    • History
    • More
    • Cancel
    • Clive T Created by Bentley Colleague Clive T
    • When: Thu, Jan 31 2019 10:51 AM
    • Revisions: 1
    • Comments: 0
    Recommended
    Related
    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies