Some time ago I got reached by a client with this error to send SMTP emails using GMail service with a wallet.
This is a generic error, in general the string identified the error returned from email service layer.
ORA-29278: SMTP transient error: string
# Error I was facing:
ORA-29278: SMTP transient error: 421 Service not available
Basically it was related to some intermittence on GMail’s service and got back to normal after a while. This is also well documented in this post by Hâvard Kristiansen.
However, I couldn’t use scripts there because of my wallet. Then I found the very useful commands below, that is what I want to share with you:
# Checking for SSL Certificate:
[oracle@grepora-srvr]$ openssl s_client -crlf -quiet -connect smtp.gmail.com:587 -starttls smtp
depth=3 C = US, O = Equifax, OU = Equifax Secure Certificate Authority
depth=2 C = US, O = GeoTrust Inc., CN = GeoTrust Global CA
depth=1 C = US, O = Google Inc, CN = Google Internet Authority G2
depth=0 C = US, ST = California, L = Mountain View, O = Google Inc, CN = smtp.gmail.com
(return:1 means "passed".)
# Testing SMTP on Database (code):
I had faced some occourrences of this error in a 18.104.22.168 database recently.
ORA-07445: exception encountered: core dump [nstimexp()+45] [SIGSEGV] [ADDR:0x58] [PC:0x7F42ABB] [Address not mapped to object] 
After some investigation I found a match to Bug 3934729.
This issue is originally to matched to Bug 6918493, that is a reintroduction of Bug 2752985 but it’s fixed in 22.214.171.124.
However, on upgrading to 126.96.36.199 it’s a hit on Bug 3934729 which is fixed in 188.8.131.52.
Recommended actions are:
– Upgrade databases do 184.108.40.206 or higher. (best solution, but may require more efforts to validate the upgrade).
– Apply Patch 3934729: RANDOM ORA-07445 CORE DUMPS FROM DATABASE AND ORA-3113 FROM APPLICATION
– Set sqlnet.expire_time=0 (workaround)
– Ignore error.
After some research I decided to apply workaround, based on recommended usage of sqlnet.expire_time (Next weeks post is about this parameter :)).
This might be the root cause for the ORA-03135: connection lost contact and the actual value of this parameter on environment was 1, which is a very low value.
So, check which action is more suitable for your environment!
Hope it helps 🙂
Below some additional informations on my situation:
Don’t create so much expectations on this post.
This is because I don’t exactly fixed the issue, but workarounded…
The thing is: This error is caused in catalog database, so the workaround is simple: do a RMAN-nocatalog, I mean, simply don’t connect in catalog to perform the backup.
After completing the backup, I’d suggest you to force a synchronization with command “RESYNC CATALOG“. In worst case, on next execution the implicit resync will fix everything. 🙂
There is no bigger explanations on this, but you can same workaround in MOS Bug 12588237 – RMAN-3002 ORA-1: unique constraint (ckp_u1) violated after dataguard switchover (Doc ID 12588237.8).
And this is it for today!
See you next week!
This is because the error is generated by an unpublished bug 17891564, as per described in MOS ORA-7445 [ocl_lock_get_waitobj_owner] on an Exadata storage cell (Doc ID 1906366.1).
It affects Exadata storage cell with image version between 220.127.116.11.0 and 18.104.22.168.0. The CELLSRV process crash with this error as per:
Cellsrv encountered a fatal signal 11
Errors in file /opt/oracle/cell22.214.171.124.0_LINUX.X64_131014.1/log/diag/asm/cell//trace/svtrc_11711_27.trc (incident=257):
ORA-07445: exception encountered: core dump [ocl_lock_get_waitobj_owner()+26]  [0x000000000]   
Incident details in: /opt/oracle/cell126.96.36.199.0_LINUX.X64_131014.1/log/diag/asm/cell//incident/incdir_257/svtrc_11711_27_i257.trc
The CELLSRV process should auto restart after this error.
While selecting on x$kglob with DBA credentials hanging on:
SQL> select count(*) from sys.x$kglob;
ERROR at line 1:
ORA-00942: a tabela ou view não existe
But with sys it succeed. Ok, let’s grant privilege:
SQL> grant select on sys.x$kglob to dba;
grant select on sys.x$kglob to dba
ERROR at line 1:
ORA-02030: can only select from fixed tables/views
What a hell! I couldn’t grant it any way!
So the MCGayver solution was:
Found the error below?
greporadb> alter table TABLE_TEST modify COLUMN_TEST not null;
alter table TABLE_TEST modify COLUMN_TEST not null
ERROR at line 1:
ORA-02296: cannot enable (MATHEUSDBA.) - null values found
It happen basically because you have null values for this column. Let’s check:
ORA-06512 ORA-48168 ORA-12012 for ADR Job Raising Errors
A database is raising stack below on alertlog:
Errors in file /db/u7011/oracle/admin/MYDB/trace/MYDB_j002_22935.trc:
ORA-12012: error on auto execute of job "SYS"."DRA_REEVALUATE_OPEN_FAILURES"
ORA-48168: the ADR sub-system is not initialized
ORA-06512: at "SYS.DBMS_IR", line 522