Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Trace file C:\ORACLE\diag\rdbms\kesdev2\kesdev2\trace\kesdev2_ora_5064.trc
- Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
- Version 19.3.0.0.0
- Build label: RDBMS_19.3.0.0.0DBRU_WINDOWS.X64_190528
- Windows NT Version V6.2
- ORACLE_HOME = C:\Oracle\product\19.3.0\dbhome_1
- Node name : KES-SDBS61
- CPU : 2 - type 86642 physical cores
- Process Affinity : 0x0000000000000000
- Memory (Avail/Total): Ph:11441M/20478M, Ph+PgF:16527M/25478M
- VM name : VMWare Version (6)
- Instance name: kesdev2
- Redo thread mounted by this instance: 1
- Oracle process number: 66
- Windows thread id: 5064, image: ORACLE.EXE (SHAD)
- *** 2023-04-27T11:54:08.902831+07:00 (BRIS(3))
- *** SESSION ID:(48.31579) 2023-04-27T11:54:08.902831+07:00
- *** CLIENT ID:() 2023-04-27T11:54:08.902831+07:00
- *** SERVICE NAME:(bris) 2023-04-27T11:54:08.902831+07:00
- *** MODULE NAME:(/about/changelog) 2023-04-27T11:54:08.902831+07:00
- *** ACTION NAME:(GET) 2023-04-27T11:54:08.902831+07:00
- *** CLIENT DRIVER:(jdbcthin : 21.1.0.0.0) 2023-04-27T11:54:08.902831+07:00
- *** CONTAINER ID:(3) 2023-04-27T11:54:08.902831+07:00
- dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=1, mask=0x0)
- ----- Error Stack Dump -----
- <error barrier> at 0x0000009DD2DB1ED0 placed dbkda.c@296
- ORA-29263: ошибка протокола HTTP
- ----- Current SQL Statement for this session (sql_id=1d37gxjt4n480) -----
- DECLARE
- V_NUM NUMBER;
- BEGIN
- V_NUM := BRIS.LOGGER_PKG.LOG_QUERY_START();
- BRIS.API_GET_ABOUT_CHANGELOG;
- BRIS.LOGGER_PKG.LOG_QUERY_END(P_IN_ID => V_NUM);
- EXCEPTION
- WHEN BRIS.CONST_PKG.E_DATA_CONFLICT THEN
- ROLLBACK;
- BRIS.RESULTS_PKG.FORM_JSON_ERROR(BRIS.CONST_PKG.CODE_BAD_REQUEST_ERROR, SQLERRM, UTL_HTTP.HTTP_NOT_FOUND);
- WHEN BRIS.CONST_PKG.E_INVALID_PARAMETER THEN
- BRIS.RESULTS_PKG.FORM_JSON_ERROR(BRIS.CONST_PKG.CODE_BAD_REQUEST_ERROR, SQLERRM, UTL_HTTP.HTTP_BAD_REQUEST);
- WHEN BRIS.CONST_PKG.E_INVALID_LOGICAL_BEHAVIOR THEN
- BRIS.RESULTS_PKG.FORM_JSON_ERROR(BRIS.CONST_PKG.CODE_BAD_REQUEST_ERROR, SQLERRM, UTL_HTTP.HTTP_BAD_REQUEST);
- WHEN BRIS.CONST_PKG.E_FORBIDDEN THEN
- BRIS.RESULTS_PKG.FORM_JSON_ERROR(BRIS.CONST_PKG.CODE_FORBIDDEN_ERROR, SQLERRM, UTL_HTTP.HTTP_FORBIDDEN);
- WHEN OTHERS THEN
- BRIS.LOGGER_PKG.ERROR;
- BRIS.RESULTS_PKG.FORM_JSON_SERVER_ERROR;
- END;
- ----- PL/SQL Stack -----
- ----- PL/SQL Call Stack -----
- object line object
- handle number name
- 00007FFAD51449A8 837 package body SYS.UTL_HTTP.READ_TEXT
- 00007FFAD51449A8 1350 package body SYS.UTL_HTTP.READ_TEXT
- 00007FFADD5F8420 551 package body BRIS.HTTP_PKG.GET_FILE_CONTENT
- 00007FFB0E7DC858 36 procedure BRIS.API_GET_ABOUT_CHANGELOG
- 00007FFB206D4528 7 anonymous block
- ----- Call Stack Trace -----
- calling call entry argument values in hex
- location type point (? means dubious value)
- -------------------- -------- -------------------- ----------------------------
- ksedst()+89 CALL??? ksedst1() 000000000 000000001
- 000000000 ? 000000000 ?
- dbkedDefDump()+2289 CALL??? ksedst() 000000000 000000000 ?
- 000000000 ? 000000000 ?
- ksedmp()+329 CALL??? dbkedDefDump() 000000001 000000000
Advertisement