Automic Workload Automation

  • Private Community
 View Only
Back to discussions
Expand all | Collapse all

Error on Automation Engine DB Upgrade from 12.1.1 to 12.3.1

  • 1.  Error on Automation Engine DB Upgrade from 12.1.1 to 12.3.1

    Posted Jan 08, 2020 09:24 AM
    Hi,
    I am doing an Automation Engine upgrade from 12.1.1 to 12.3.1.
    I have also upgrade my DB to 19c and my Linux server to Redhat 7.7

    I'm getting this error when I run the DbLoad 

    I do have a ticket open with support but just wondering if anyone else out there may have seen this before.

    20200107/014617.413 - U00003545 UCUDB: Opening database ...
    20200107/014617.413 - U00029112 UCUDB - Length of the DB-History area: 100
    20200107/014617.668 - U00029114 UCUDB - ALTER SESSION: NLS_LANGUAGE=AMERICAN
    20200107/014617.669 - U00029114 UCUDB - ALTER SESSION: NLS_TERRITORY=AMERICA
    20200107/014617.670 - U00029114 UCUDB - ALTER SESSION: NLS_LENGTH_SEMANTICS=CHAR
    20200107/014617.670 - U00029109 UCUDB: Local information from client environment
    20200107/014617.670 - U00003535 DB INFO: 'OCI_NLS_LANGUAGE = AMERICAN'
    20200107/014617.670 - U00003535 DB INFO: 'OCI_NLS_TERRITORY = AMERICA'
    20200107/014617.670 - U00003535 DB INFO: 'OCI_NLS_CHARACTER_SET = WE8MSWIN1252'
    20200107/014617.670 - U00029110 UCUDB - Session parameters:
    ORA-24550: signal received: [si_signo=11] [si_errno=0] [si_code=1] [si_int=0] [si_ptr=(nil)] [si_addr=0x1]
    kpedbg_dmp_stack()+394<-kpeDbgCrash()+204<-kpeDbgSignalHandler()+113<-skgesig_sigactionHandler()+258<-__sighandler()<-_ZN5Trace6LoggenElPcz()+229<-0x0000000000000200
    Segmentation fault (core dumped)

    Thanks.
    JOhn.






  • 2.  RE: Error on Automation Engine DB Upgrade from 12.1.1 to 12.3.1

    Posted Jan 08, 2020 09:51 AM
    Hi.

    Well, not seen before, but it's a segmentation fault. Or in other words, your Oracle client (or a function in its libraries) appears to crash.

    • Does your Oracle client work outside of dbload with the same environment variables, i.e. in the same shell/session?
    • Are you doing anything out of the ordinary, like mixing Oracle shared objects between versions via LD_LIBRARY_PATH?
    • Are you using Oracle libraries from a supported version of the Oracle client?
    • Did you set LD_LIBRARY_PATHS to any Automic component? If so: don't. The only LD_LIBRARY_PATH you should have in your environment when running dbload should be pointing to Oracle libraries and nothing else (I have an article somewhere on these forums explaining this mess).
    • Failing anything else, try a different Oracle client. They are cross-compatible afaik, you can use a V18 client for a V19 db.

    Hth,


  • 3.