IMPDP Fails With ORA-29913 ORA-31644

Today I was doing an imp datapump when the following error occurred;

ORA-31693: Table data object "XXXX"."XXXXXXXX" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEFETCH callout
ORA-31644: unable to position to block number 363120 in dump file "/xxxx/xxxx/xxxxx/fulldb37.dmp"

Reviewing ML / MOS, I have seen that there were several bugs made with it, but in my case the problem is quite simple, since that making a comparison of the size of the file in origin and destination had a difference of a few bytes. In my case I have made the transfer using a scp, it is rare that a file transfer fails today, but it seems to happen from time to time.

The solution has gone through repeating the file re-send.



Error in Certificate Validation

They report the error below when they try to use a certificate against a secure website (the configuration is in Spanish);


ERROR en línea 1:
ORA-29273: fallo de la solicitud HTTP
ORA-06512: en "SYS.UTL_HTTP", línea 1722
ORA-29024: Fallo de validación de certificado
ORA-06512: en línea 1


In this case the certificate that is used is the correct one, but the database is in a version The problem is causedbecause the url you are trying to access uses TLS, and the database version does not support the lowest level of TLS (1.1). It can solve with an upgrade to


ORA-00600 Error When Precompiling

Today I have installed a test environment for processes in Pro c. When performing the Oracle precompiler phase, this is coventing the sources in Pro c to pure language c the following error appears;


Pro*C/C++: Release - Production on Thu Feb 21 17:08:24 2019

Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved.

System default option values taken from: /xxxxxx/12.1/precomp/admin/pcscfg.cfg

dbgc_init_all failed with ORA-48141
ORA-00600: internal error code, arguments: [17998], [2], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [17998], [2], [], [], [], [], [], [], [], [], [], []

----- Call Stack Trace -----
calling              call     entry                argument values in hex
location             type     point                (? means dubious value)
-------------------- -------- -------------------- ----------------------------
skgudmp()+124        CALL     kohbuh()+1951        FFFFFFFF7FFFB768 ?
                                                   0000F4240 ? 0FFFFFFFF ?
                                                   000000000 ? 000000026 ?
                                                   00000003E ?
kgeriv_int()+216     PTR_CALL skgudmp()            100943900 ? 000002400 ?
                                                   000000800 ? 001FE6788 ?
                                                   FFFFFFFF7EFDB838 ?
                                                   000000000 ?
kgeasi()+176         CALL     kgeriv_int()         100943900 ? 10097C4D8 ?
                                                   00000464E ? 000000000 ?
                                                   000000001 ?
                                                   FFFFFFFF7FFFBA68 ?
pcgini()+1024        CALL     dbgruppm_purge_main  100943900 ? 10097C4D8 ?
                              ()+2079              00000464E ? 000000002 ?
                                                   000000001 ? 000000000 ?
pc2main()+1488       CALL     pcgini()             FFFFFFFF7FFFE588 ?
                                                   FFFFFFFF7FFFDAC0 ?
                                                   1009AA810 ?
                                                   FFFFFFFF7FFFE338 ?
                                                   FFFFFFFF7FFFEE20 ?
                                                   1009481B8 ?
lpmcall()+816        PTR_CALL pc2main()            10091D590 ?
                                                   FFFFFFFF7FFFE300 ?
                                                   000000101 ?
                                                   FFFFFFFF7FFFE498 ?
                                                   1008E05C0 ? 1008CADA0 ?
lpmpmai()+364        CALL     lpmcall()            000000002 ?
                                                   FFFFFFFF7FFFF807 ?
                                                   1008F7580 ? 1808F0E18 ?
                                                   1001CD140 ?
                                                   FFFFFFFF7FFFF0B8 ?
main()+292           CALL     00000001008CB280     FFFFFFFF7FFFF218 ?
                                                   FFFFFFFF7FFFF1E8 ?
                                                   000000002 ?
                                                   FFFFFFFF7FFFF608 ?
                                                   000001A68 ? 000206DAC ?
_start()+300         CALL     main()               000000002 ?
                                                   FFFFFFFF7FFFF608 ?
                                                   FFFFFFFF7FFFF802 ?
                                                   000000000 ? 1008CADA0 ?
                                                   FFFFFFFF7FFFF548 ?

Call stack signature: 0x1d6e42d7f18cb236

The error seems to be inside the database, because it is ora-00600, but in this case it is a problem at the level of physical permissions on directories. This compilation, precompilation and linking phase is being done with a user that is not the owner of the software, which restricts access. A workaround is to give persimmon 777 about the structure of the diagnostic with the owner of the software. Next, show an example;


chmod 777 $ADR_BASE/diag/plsql




Error “Unable to save wallet at”

This morning installing certificates in a old release ( I got the next error



$ orapki wallet create -wallet /sandbox34/shared/certificates  -pwd Sistemaspro
Oracle PKI Tool : Version - Production
Copyright (c) 2004, 2009, Oracle and/or its affiliates. All rights reserved.

Unable to save wallet at /plustes/test/utilidades

After a while of verifying permissions and trying to generate files in this filesystem, which is all right, it came to my mind that it was a problem that had already happened to me on some occasion, and that was because of the password itself. The issue is that there are a series of minimum requirements, but simply putting a substring of numbers and a capital letter is valid. Let’s see the following example;



$ orapki wallet create -wallet /sandbox34/shared/certificates -pwd Sys123456
Oracle PKI Tool : Version - Production
Copyright (c) 2004, 2009, Oracle and/or its affiliates. All rights reserved.




An Old Release Of Oracle (7.3)

Today I had to connect to a machine (which maintains a historical database) ev version 73 to do a review of it, since the machine has suffered an incident.

In my case I started working with versions 6 and 7 of Oracle and the truth is that it took a bit to connect, since the old svrmgrl is used, I leave a screen of what the v $ instance contained in this version.

And another screen with the help that this tool had;


I have to admit that my tear drops when I see it.