Symptom
During a SAP Upgrade the ORA-28000 error is issued, you will find such error in the relevant SAP Upgrade log (see below examples).
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_SQL_EXCEPTION', was
not caught and therefore caused a runtime error.
The reason for the exception is:
ORA-28000: the account is locked
or
TRACE-INFO: 54: [ dbsloci.,00000] *** ERROR => CONNECT failed with sql error '28000'
TRACE-INFO: 55: [ dev trc,00000] set_ocica() -> SQL error code 28000
TRACE-INFO: 56: [ dev trc,00000] >oci_get_errmsg (con=0, rc=28000)
TRACE-INFO: 57: [ dev trc,00000] OCIErrorGet -> SQL error code: 28000
TRACE-INFO: 58: [ dev trc,00000] ORA-28000: the account is locked
TRACE-INFO: 59: TRACE-INFO: 60: [ dev trc,00000] DbSlConnect(con=0) -> orc=0, 99=DBSL_ERR_DB
or
*** ERROR => CONNECT failed with sql error '28000'
set_ocica() -> SQL error code 28000
>oci_get_errmsg (con=0, rc=28000)
OCIErrorGet -> SQL error code: 28000
ORA-28000: the account is locked
Read more...
Environment
- SAP systems with Oracle database
- Not restricted to a product or product version
Product
Keywords
lock, EHP, owner, phase, shadow, connect, instance, abort, prepare, step, preprocessing, SHD, SAPR3SHD, SAPSR3SHD, SAP<SID>SHD, prep, upg, stopped, DBCONNCHKSHD, MAIN_SHDINST/RUN_RSVWSCPY, brtools, ORA-28 , KBA , BC-DB-ORA , Oracle , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , BC-JAS-SF , Startup Framework , BC-DB-ORA-DBA , Database Administration , BC-JAS-ADM-ADM , Administration , BC-UPG-OCS-SPJ , Please use component BC-UPG-TLS-TLJ , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.